Identify unplanned maintenance requirements
How identify unplanned maintenance requirements are reshaped as AGI capability advances.
The bottom line
About 35% of the work in Identify unplanned maintenance requirements is information-shaped and increasingly AI-deliverable, with the rest a hybrid of judgment and hands-on work. The automation frontier runs straight through the middle of this role.
Why: With no child occupations seeded, the score relies on the APQC lens 'Maintain productive assets' and the process description. The lens roots this work in physical machinery and infrastructure domains, which generally push the digital score low. However, the specific action of 'identifying' requirements focuses on the diagnostic, observational, and ticketing phase rather than physical repair execution, representing a hybrid mix of hands-on inspection and system logging.
grounded in the economy graph · digital scalar 0.35 · hybrid
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
How the work flows
Trigger: An asset operator observes abnormal behavior, or an automated monitoring system flags a fault code or unexpected failure.
- Detect asset malfunction or automated fault code
- Secure or isolate the affected asset to ensure safety
- Perform an initial diagnostic assessment of the issue
- Classify the severity and operational impact of the fault
- Log the unplanned maintenance requirement into the asset management system
- Generate an urgent or non-routine maintenance request
Outcome: The specific maintenance requirement is documented, evaluated for operational impact, and submitted as an actionable work request.