Equipment Categories, Structure and Time-Dependent Data (Part 2)

📌 KEY POINTS
✅ Equipment Category (config) determines the number range, field selection group (mandatory/optional/hidden fields) and relevant views (PM data, sales data, fleet data) for equipment created under it.
✅ Good category design separates equipment by functional domain (production machinery, fleet vehicles, IT hardware, tools) since each domain needs different mandatory fields and planning groups.
✅ Equipment can be installed at a functional location (where) and/or superior/subordinate to other equipment (what it's made of) — both hierarchies can exist simultaneously.
✅ Time-dependent fields (functional location assignment, cost center, superior equipment) use validity periods, not overwrites, so history queries reflect the correct configuration at a past date.
⚠️ Changing equipment category after go-live is restricted and can require data migration — get category design right at blueprint stage.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 covered equipment master basics. Now category design and structure.

━━━━━━━━━━━━━━━━━━━━
▶ 1. EQUIPMENT CATEGORY

• Number range, field selection, views — set at blueprint, hard to change later.

━━━━━━━━━━━━━━━━━━━━
▶ 2. LOCATION-BASED HIERARCHY

• Installed at a functional location = "where."

━━━━━━━━━━━━━━━━━━━━
▶ 3. EQUIPMENT-BASED HIERARCHY

• Superior/subordinate = "what it's made of."

━━━━━━━━━━━━━━━━━━━━
▶ 4. TIME-DEPENDENT DATA

• Validity periods on location/cost center/superior assignments.

━━━━━━━━━━━━━━━━━━━━
▶ 5. TROUBLESHOOTING

• Manual field edits (instead of install/dismantle) break history.

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

1. Review equipment category field selection and number range.
2. Install equipment at a location and note the validity period created.
3. Query history for a past date and confirm it reflects the correct configuration.

✅ CHECKPOINT: a history report for a past date shows exactly where the equipment was and who was responsible then.

A fleet management team needs to track engines that are periodically removed from one truck and installed on another for overhaul rotation. The design team models trucks as Functional Locations and engines as Equipment with a dedicated category and number range, using installation/dismantling actions each time an engine moves. Six months after go-live, a warranty dispute requires proving which truck an engine was installed on during a specific failure date; because time-dependent installation history was correctly maintained, the team retrieves an accurate historical record instead of relying on unreliable manual logs.

• Changing equipment category after go-live without understanding the migration and number range implications.
• Manually editing the functional location field on equipment instead of using proper installation/dismantling actions, which breaks time-dependent history.
• Designing too few equipment categories, forcing unrelated asset types to share field selection rules that do not fit all of them.
• Ignoring superior/subordinate equipment structuring, leading to spare parts and failure data being recorded at too coarse a level.
• Failing to reconcile serial numbers before creating new equipment, resulting in duplicate records for the same physical asset.

• Design equipment categories around distinct business domains with genuinely different field and process needs, not arbitrarily.
• Always use installation and dismantling actions to change equipment location, never direct field edits.
• Use superior/subordinate equipment relationships to reflect meaningful sub-assembly structures needed for spares and failure analysis.
• Periodically audit equipment records for duplicate serial numbers before creating new master records.
• Document category-to-number-range mapping clearly so support teams understand why certain fields are mandatory for certain equipment types.

Expect questions on the purpose of equipment category configuration and its downstream effects on number ranges and field selection, as well as scenario questions asking you to design an equipment/functional location structure for a given asset type. Strong answers reference time-dependent installation history and explain why it matters for accurate cost and failure reporting.