Designing and Configuring Functional Location Hierarchies (Part 2)

📌 KEY POINTS
✅ The structure indicator's edit mask determines both the maximum hierarchy depth and how intuitively users can read the identifier — get this right at blueprint since changing it later needs a migration.
✅ Balance granularity (enough levels for meaningful maintenance/cost reporting) against maintainability (not so many levels that data entry becomes burdensome) — the right depth depends on the client's reporting needs.
✅ The "superior functional location" field is what the system uses to inherit fields and roll up reporting — distinct from the label's textual hierarchy, which can diverge if not carefully maintained.
✅ Reference structures/templates let you rapidly create a full hierarchy for a new line by copying an existing template, reducing manual creation time for repeated similar assets.
⚠️ Mixing organizational/responsibility groupings into the physical hierarchy is a common design smell causing reporting ambiguity between "where" and "who is responsible."

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced functional locations. Now designing the hierarchy itself.

━━━━━━━━━━━━━━━━━━━━
▶ 1. STRUCTURE INDICATOR / EDIT MASK

• Character allocation per level; separators.

━━━━━━━━━━━━━━━━━━━━
▶ 2. GRANULARITY VS MAINTAINABILITY

• Enough levels for reporting, not so many it's burdensome.

━━━━━━━━━━━━━━━━━━━━
▶ 3. SUPERIOR FIELD VS LABEL

• The real structural link vs the readable text.

━━━━━━━━━━━━━━━━━━━━
▶ 4. REFERENCE STRUCTURES

• Templates for repeated similar assets (e.g. identical production lines).

━━━━━━━━━━━━━━━━━━━━
▶ 5. SIGN-OFF DISCIPLINE

• Structure indicator/depth decisions need explicit client sign-off.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Define the edit mask with plant-area-unit-position levels.
2. Build a reference structure template for one line.
3. Copy the template to create the next 11 identical lines.

✅ CHECKPOINT: all 12 lines have consistent depth and naming, enabling cross-plant benchmarking.

A manufacturing client with twelve nearly identical packaging lines across two plants asked for functional locations to be created individually by plant engineers as needed, with no standard template. Within a year, the structure had inconsistent depth - some lines had five levels down to individual sensor positions, others had only two levels - making cross-plant benchmarking impossible. The consultant proposed a reference structure representing a standard packaging line template with four fixed levels, then used it to recreate and remap the inconsistent structures plant by plant during a scheduled downtime window, with careful reassignment of existing notification and order history to the corrected locations. This retrofit took several weeks but was substantially cheaper than continuing to operate a structure that could never support the reliability KPIs the client wanted.

• Designing structure indicators with insufficient character length, forcing awkward abbreviations once the client scales to more plants or units.
• Mixing organizational/responsibility groupings into the physical hierarchy, causing reporting ambiguity between 'where' and 'who is responsible.'
• Allowing hierarchy depth to vary inconsistently across similar assets, which breaks apples-to-apples benchmarking.
• Relying on the label text to represent hierarchy while neglecting to correctly set the superior functional location field.
• Underestimating the migration effort required to change structure indicators after significant transactional history has accumulated.

• Get explicit client sign-off on structure indicator and hierarchy depth during design phase, since changes later are costly.
• Use reference structures/templates when creating multiple similar hierarchies to enforce consistency.
• Keep the functional location hierarchy strictly physical/spatial; represent organizational responsibility elsewhere.
• Periodically audit hierarchies for depth and naming consistency across plants, especially after decentralized creation by multiple engineers.
• Document the mapping between edit mask segments and business meaning (e.g., which characters represent plant vs. area) so future consultants can maintain it correctly.

Interviewers assessing intermediate-level design skills often present a scenario with several similar production lines and ask how you would structure the functional location hierarchy, including how many levels you would use and why. Strong answers reference the trade-off between granularity and maintainability, the role of reference structures for scaling similar assets, and the risk of changing structure indicators later - showing you think about long-term reporting consequences, not just initial setup.