Digital Application List on Maintenacne and Reliability Function.
Below are the typical SAP and available legacy applications arround the RCM (Reliability Centered Maintenance) functional unit.
- SAP for Managing Work Order Workflow
- SAP for Managing Asset Master Data
- Apps for Handling Inspection Execution Result
- Apps for Handling Turn Around Execution Result
- Apps for Handling Inspection Execution Result
- Apps for Handling Condition Monitoring Execution - Result
- Apps for handling Corrective Maintenance Execution Result
- Apps for creating long term maintenance plan (10 year)
- Apps for Handling Basic of Care (Daily checks to keep equipment condition)
- Apps for Analytics
- Apps for Predictive Analytics
- Apps for Managing management of change
- Apps for Handling the root cause analysis from any incident/failure
- Dashboard to create an insight about RCM from all these apps
note:each organization might have different ecosystem but generally above apps are the common surroundings.
Domain Segregation
among these 14 apps, it can be categorized into following *bounded context.
| Bounded Context | Primary Responsibility | System-of-Record | Integration Pattern |
|---|---|---|---|
| WorkOrder Orchestration | WO lifecycle, dispatch, SLA | SAP or WorkOrder service | Sync API (commands) + Events |
| Asset Master | Asset hierarchy, BOM, master data | SAP | ACL / Replicated read model |
| Inspection Execution | Field inspection capture, offline sync, evidence storage | Inspection service | Mobile offline sync + Events |
| Turnaround Management | Plan & execute turnarounds (long-running) | Turnaround service | Saga (events + commands) |
| Condition Monitoring / Telemetry | Telemetry ingest, alarms, thresholds | Telemetry platform (TSDB) | Event streaming (Kafka/IoT hub) |
| Corrective Maintenance | Corrective job capture, parts, closure | Corrective service | Events + API to WorkOrder |
| Maintenance Planning | Long-term maintenance strategy & 10-year plans | Planning service | API + Batch exports |
| Basic Operations & Care (BOC) | Daily checks, operator rounds | BOC service | Offline-capable mobile + Events |
| Predictive Maintenance | ML models, predictions, RUL | Prediction service + model store | Event stream -> model -> events/API |
| Analytics & Dashboard | Aggregated KPIs, dashboards, reports | Analytics DW | Event -> ETL -> DW |
| Change Management (MOC) | MOC requests, approvals, implementation tracking | MOC service | API + Events |
| Root Cause Analysis (RCA) | Failure investigation, causal trees | RCA service | API + Events / link artifacts |
| RCM Dashboard / Insight Hub | Composite insights pulled from analytics & events | Composite read models | Read models fed from events/analytics |
Domain Interaction
once the domain has been draw and determined by the business user and technical team, it is important to also determine the domain interaction strategy.
ideally, each domain should not communicate directly. There should be an additional layer which orchestrate the domain communication or usually called as a middleware/enterprise service bus(ESB).
this layer will orchestrate the integration process. Performing ETL, payload encirhment and handling the rollback or any alternate scenario (if needed).
Why the integration is not handled directly on the domain?
technically the integration can be handled and orchestrated on the domain itself. However on the reality, this will increase the complexity of the domain causing overhead on the domain system maintenance as it will cause function overlapping between origin domain and target domain.
Digital apps on same domain should only focus to execute all functionality belong to these domain only.
