Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Unplanned Assignment Interruption Duration measures the time an assignment is halted because an unplanned equipment failure leaves no spare unit available. UAID starts when the failure is recorded by Operations or telematics and ends at the first productive move on the interrupted assignment after a swap or a repair.
Here ‘assignment’ refers to the job instruction.
TIC Description
Further Detail
O
UAID is different than just asset downtime, which is tracked under CHE Downtime. It is focused on assignment downtime.
While UAID is a single KPI, it can be reported using the following standard outputs (similar to how GMPH can be calculated for a vessel visit or across a period of time):
UAID.event: Time from failure notification (from Ops or telematics) until the assignment performs its first productive move after resumption (with a replacement unit or the repaired unit).
UAID.period (aggregate): Sum of UAID.event over the reporting window (vessel, week, month).
UAID.asset-attributed (diagnostic): Attribute each UAID.event to the root-cause asset for bad-actor analysis. Use only for engineering dashboards, not benchmarking.
Purpose
Prioritize Corrective and Preventive Maintenance by impact severity (how long operations were blocked by maintenance).
Scope Limits
Asset level: CHE Downtime runs from the time the failure is recorded to the time Maintenance declares the unit available for use.
Assignment level: UAID runs from the time the failure is recorded to the first productive move on the interrupted assignment after a swap or a repair. If a spare takes over immediately and there is no gap, do not create a UAID event. If the assignment is canceled or abandoned, end UAID at the time of cancellation and record the resumption mode as canceled.
Terminal wide interruptions: Events such as power loss, IT outage, labor action, or severe weather are not UAID. Track these under System or Terminal Interruption.
Start / End rules (close the ambiguity)
Start: timestamp of failure notification (Ops/telematics) that prevents the assigned unit from continuing productive work.
End: timestamp of first productive movement by either a replacement or the repaired unit on that same assignment.
Do NOT end UAID at “new CHE assigned” or “asset marked available”; end only at productive movement.
Special cases
Immediate swap (no interruption): if replacement performs a productive move without a gap, UAID = 0, while CHE Downtime > 0 may still accrue on the failed unit.
Multi-asset assignments: If one of multiple required units fails and the work cannot continue at target cycle, UAID counts the lost interval until normal productive cycle resumes.
Operator faults: Recommend exclude from UAID (track as “Operator-caused Interruption”); if you choose to include, tag and report separately to keep Maintenance prioritization clean.
Why this matters
Maintenance queues should weight defects by UAID minutes × criticality (assignment type, vessel phase, customer priority) to guide PM/CM focus
Filter:
Vessel / Berth / CHE
Split:
Shift / date
Data Points
Assignment ID = TOS|@|jobinstruction|@|order|@|id TOS|@|jobinstruction|@|order|@|dispatched|status
Failure status (duration): TOS|@|jobinstruction|@|order|@|CHE|fault|duration|value
First productive move after failure (timestamp) TOS|@|jobinstruction|@|order|@|type TOS|@|jobinstruction|@|order|@|dispatched|status TOS|@|jobinstruction|@|order|@|end|time