Asset hierarchy: Flat vs nested structure in resource management

[neha_architect]

I’m curious how other plants have structured their asset hierarchy in FactoryTalk MES 10.0 resource management. We’re currently using a flat structure - all equipment assets are direct children of their production lines with no intermediate grouping. This keeps things simple for operators but we’re having issues with maintenance task assignment and downtime reporting.

Our maintenance team wants to group assets by system type (electrical, mechanical, hydraulic) so they can assign preventive maintenance tasks to entire groups. Meanwhile, production wants to keep the current flat view because nested hierarchies make it harder to find specific equipment during shift handovers.

For those running nested hierarchies - how deep do you go? Do you structure by physical location, functional system, or maintenance responsibility? And how does that affect your downtime rollup reporting when a sub-component fails but impacts the parent line?

[ritu_arch]

From an operator perspective, nested hierarchies are frustrating during troubleshooting. When a machine goes down, I need to log the downtime quickly - not click through three levels of menus to find the right asset. We compromised by using a shallow nested structure (just two levels) and adding custom quick-access buttons on the HMI for frequently-used assets.

[sarah_master]

I’ve implemented both approaches across different clients. Flat hierarchies are easier for day-to-day operations but become problematic as your asset count grows. We had one plant with 450+ assets in a flat structure and finding the right equipment became a real pain. They eventually switched to a nested structure organized by ISA-95 equipment hierarchy standard - Site → Area → Line → Work Cell → Unit. The key is to keep it no more than 4-5 levels deep or navigation becomes cumbersome.

[mark427]

We use a three-level nested structure: Plant → Line → Equipment System → Individual Asset. This works well for maintenance planning because we can assign PM tasks at the Equipment System level and they cascade down. For example, our “Hydraulic System” group includes pumps, valves, and cylinders - one PM task assignment covers all components. The downside is that operators need more training to navigate the hierarchy during production.

[dan_specialist]

Downtime rollup is configurable but not automatic by default. You need to enable the “Propagate Child Downtime” setting for each parent resource. Be careful though - if you enable this for high-level parents, a single component failure could incorrectly show an entire production line as down when only one subsystem is affected. We use selective propagation: enable it for critical path equipment but not for redundant systems.

[luismanager]

This discussion highlights the classic trade-off between operational simplicity and organizational complexity. After working with resource hierarchies across 15+ MES implementations, I’ve developed some principles that balance both needs.

Flat vs Nested - The Real Question:

The debate isn’t really about flat vs nested - it’s about how you define your operational boundaries. Flat hierarchies work great when:

• Your asset count is under 100-150 items per production area
• Equipment is relatively independent (failures don’t cascade)
• Maintenance is reactive rather than systematic
• Operators need speed over structure

Nested hierarchies become necessary when:

• You have 200+ assets and need logical grouping for navigation
• Maintenance follows systematic programs (PM, PdM) applied to equipment classes
• You need to track relationships between parent systems and child components
• Regulatory compliance requires traceability of maintenance across equipment groups

Maintenance Task Assignment Considerations:

Susan’s three-level structure (Plant → Line → Equipment System → Asset) is solid for maintenance, but here’s what often gets overlooked: task inheritance vs task assignment.

In FT MES, you can assign maintenance tasks at any hierarchy level, but the execution behavior differs:

• Direct assignment (flat): Task targets specific asset, clear ownership, but requires duplicate tasks for similar equipment
• Inherited assignment (nested): Task assigned to parent group, automatically creates child tasks, but can create confusion about which specific asset needs work

We typically use a hybrid approach: assign PM tasks at the equipment system level (e.g., “Hydraulic System Monthly Inspection”) but let technicians select specific child assets during execution. This gives maintenance planning efficiency while preserving execution clarity.

Downtime Reporting Reality:

Mike’s concern about downtime rollup is valid and often misunderstood. Here’s how it actually works in FT MES 10.0:

1. Default behavior: Child downtime does NOT automatically roll up to parents
2. Configurable propagation: You can enable “Propagate Child Downtime” per parent resource
3. Rollup logic: When enabled, parent shows aggregate downtime duration from all children
4. OEE impact: Parent OEE calculation can include or exclude child downtime based on configuration

The critical decision is: Do you want downtime reported at the failure point or at the production impact point?

Example scenario: Conveyor motor fails on Line 3

• Flat hierarchy: Downtime logged directly to “Line 3” - simple but loses detail about which component failed
• Nested hierarchy: Downtime logged to “Conveyor Motor” (child), optionally propagates to “Material Handling System” (parent), optionally propagates to “Line 3” (top level)

For reporting, nested gives you both detail and aggregation. You can analyze: “Which component types cause most downtime?” (look at child level) and “Which lines have most downtime?” (look at propagated parent level).

Practical Recommendation:

Use a shallow nested structure with role-based views:

Structure (2-3 levels maximum):

• Level 1: Production Line (e.g., “Assembly Line 3”)
• Level 2: Equipment Group by function (e.g., “Welding Station”, “Material Handling”, “Quality Inspection”)
• Level 3: Individual Assets (e.g., “Welder-03-A”, “Conveyor-03-B”)

Views (customized by user role):

• Operators: See flat list of Level 3 assets for their assigned line only (filtered view hides hierarchy)
• Maintenance: See full nested structure organized by equipment type for PM assignment
• Management: See Level 1 and Level 2 with rolled-up metrics for performance dashboards

FT MES supports custom views through the Resource Explorer configuration. You can create multiple view templates and assign them to different user roles. This way operators get their simple flat list while maintenance gets the grouping structure they need.

Configuration Tips:

1. Enable quick search: Configure the Resource Explorer to show a search box at the top - operators can type asset ID and jump directly without navigating hierarchy

2. Use functional location codes: Assign standardized location codes (e.g., “L3-WS-02” for Line 3, Welding Station, Position 02) that work in both flat and nested views

3. Create favorite lists: Let operators build custom “My Equipment” lists of frequently-accessed assets that bypass the hierarchy entirely

4. Configure selective downtime propagation: Enable propagation only for critical path equipment where child failure truly stops the parent. Leave it disabled for redundant systems or parallel equipment.

5. Implement dual reporting: Configure downtime reports with both detail view (shows individual asset failures) and summary view (shows line-level aggregates). Different stakeholders need different perspectives.

The bottom line: Don’t force an either/or choice. FT MES is flexible enough to support both operational simplicity (through views and shortcuts) and organizational structure (through hierarchy) simultaneously. The key is thoughtful configuration that serves multiple user needs rather than optimizing for just one group.