EAM 303 · INTEGRATION PATTERNS
How can Enterprise Asset Management execute differently?
Choose a pattern from the outcome, required control, execution evidence, and financial treatment—not familiarity with one template.
- 01
Reactive maintenance
A maintenance request starts a controlled phase-based response to restore an asset after an issue.
Design implication: Best where screening, approval, planning buckets, and phase visibility matter.
- 02
Corrective maintenance
A planner creates and releases an order to repair a known defect using classic status-driven processing.
Design implication: Straightforward planned repair execution.
- 03
Emergency maintenance
Urgent work is executed and reported with minimal delay while preserving labor, material, and history.
Design implication: Optimizes response speed with retrospective control.
- 04
Preventive maintenance
Maintenance plans schedule recurring work from time, performance, strategy, or counter rules.
Design implication: Reduces avoidable failure and standardizes recurring work.
- 05
Shutdown or turnaround
Many orders are coordinated within a common outage window, often with PS or higher-level scheduling.
Design implication: Controls dependencies, shared resources, and outage duration.
- 06
Capital upgrade integration
A project governs capital scope and budget while maintenance orders execute against technical objects.
Design implication: Connects physical work to the B2A accounting outcome.
SELECTION TEST
Decide with the same questions
What is delivered, who accepts it, and who owns the result?
Which object controls dates, work, materials, services, confirmations, status, and change?
Where do cost and revenue collect, how are they recognized or settled, and what reconciles?
Translate an approved pattern into controls, integrations, settings, and proof.