PM / EAMintermediate

Equipment Installation, Dismantling, and Time-Segmented History at Functional Locations (Part 3)

Key takeaway

Learn how installing and dismantling equipment at functional locations creates time-based history records, why this matters for maintenance history and cost tracking, and how to configure and troubleshoot the process correctly.

Explanation

📌 KEY POINTS
✅ Installing equipment at a functional location creates a time-segmented usage history record; dismantling closes that segment with an end date.
✅ This lets you answer two different questions accurately: "what happened at this location over its life" (location-centric) and "what happened to this specific equipment" (equipment-centric, for warranty/serial-level failure analysis).
✅ The "history requirement" flag on equipment category customizing determines whether install/remove is logged with full time-stamped history or treated as a simple field overwrite.
✅ Most rotating and serialized equipment (pumps, motors, transformers, vehicles) should use history-relevant categories.
⚠️ The most common runtime issue is "orphaned" equipment — installed at a new location without first dismantling from the old one, causing overlapping history and double-counted costs.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 covered categories and structure. Now installation mechanics and history.

━━━━━━━━━━━━━━━━━━━━
▶ 1. INSTALL/DISMANTLE

Opens/closes time segments; use the proper action, not a field edit.

━━━━━━━━━━━━━━━━━━━━
▶ 2. TWO VIEWS OF HISTORY

Location-centric vs equipment-centric.

━━━━━━━━━━━━━━━━━━━━
▶ 3. HISTORY-RELEVANT CATEGORIES

Config flag decides if time-stamped history is even tracked.

━━━━━━━━━━━━━━━━━━━━
▶ 4. INTEGRATION

Orders/notifications reference installation dates for correct reporting.

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

Overlapping segments = missed dismantle step.

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

Dismantle the equipment currently at a location.
Install the replacement equipment at that location.
Run the usage list/history report to confirm segments don't overlap.

✅ CHECKPOINT: the history report shows clean, non-overlapping time segments for the location and the equipment.

Code example

ABAP Code

===== SEQUENCE (correct) =====1 Dismantle Pump-A from Location X (closes its history segment)2 Save3 Install Pump-B at Location X (opens a new history segment) ===== WHAT BREAKS IT =====Installing Pump-B without dismantling Pump-A first → both show "installed" → overlapping segments → duplicate cost postings, wrong MTBF ===== REPORTS =====Usage list / installation history report — audit for overlapping or orphaned records

Real project scenario

A water utility tracks pumps installed at pump station functional locations. During a plant turnaround, a pump is removed for overhaul and a spare pump (different equipment number) is installed temporarily. The maintenance planner failed to dismantle the original pump equipment record before installing the spare, causing both pumps to show as 'installed' at the same functional location simultaneously. This produced duplicate cost postings on a subsequent breakdown notification and confused the equipment-based MTBF (mean time between failures) report used by the reliability team. The support consultant had to review the usage list history for the functional location, identify the overlapping segments, manually correct the installation/dismantle dates, and coach planners on the correct sequence: dismantle first, save, then install replacement.

Common mistakes

Installing replacement equipment without first dismantling the previous unit, causing overlapping history segments
Assuming history is automatically history-relevant for all equipment categories without checking category customizing
Backdating installation dates incorrectly, which can conflict with existing notification or order dates tied to the location
Ignoring the usage list/history report when investigating cost or MTBF discrepancies
Treating functional location fields and equipment fields as interchangeable when reporting, without checking which object actually carries the time-relevant data

Best practices

Always dismantle equipment before installing a replacement at the same functional location
Verify the equipment category's history-relevant setting for any object type used in reliability reporting
Use the usage list/installation history report periodically to audit for overlapping or orphaned records
Coordinate installation/dismantle timing with notification and order creation to avoid cost misattribution
Document the correction procedure for support teams so backdating is handled consistently and audit trails remain clear

Interview angle

Interviewers assess whether candidates understand the difference between functional-location-centric and equipment-centric history, and why time-segmentation matters for reliability metrics like MTBF/MTTR. Be ready to explain what happens operationally if dismantle is skipped, and how you would investigate and correct overlapping installation history in a live system without deleting audit-relevant records improperly.

Practice this lesson

Quick check

1. A water utility installed a spare pump at a location without dismantling the original pump first. What is the correct sequence to avoid this?

2. A technician needs to know exactly when a piece of equipment was installed at and dismantled from various functional locations over its lifetime. Which equipment master feature provides this chronological information?

3. When equipment is installed at a functional location and later dismantled and reinstalled at a different functional location, how does the system typically handle the historical assignment data?

Interview questions

1. A maintenance-heavy turnaround project uses equipment counters to trigger overhaul work orders, and these orders need to settle costs to a WBS element in a project. How would you configure the equipment category and counter setup to support this PS integration cleanly?

Answer it in your own words first, then compare.

2. A leasing company has a fleet of forklifts where usage-hour counters must trigger both PM maintenance orders and periodic FI cost postings for lease accrual once a threshold is reached, and equipment category settings must control whether an asset master record is automatically created at equipment creation. How would you design the equipment category and counter setup to support this FI integration?