As-Is process for Outage Fixing

The below As-Is process mapping depicts any typical outage fixing scenario complying with
CPL policy (10% CPL tolerance limit) unless stated otherwise by CPM.The process of
Outage fixing begins right after the entry of Op data.
Compare the
schedule of OTRFC
& User version.

No Schedule
pattern
change
Observed?

Yes
Try fixing
review
period
Outage

Perform
Inventory
True up

Schedule
pattern
change No
Observed?

Yes
Investigate on the root
cause of shift in
dates/change in events
by comparing with
OTRFC Export schedule
sheet
 Limiting Threshold Existing Start/End
Part Logic CPL’s Dates

Apply CPL on the Eliminate/Modif Calibrate

Apply CPL on the threshold part y already on the
Limiting part counting on the existing CPLs Start/End
either to push it repair –replace to suit the dates to
in the subsequent hrs/starts limits to be parts flow align with
event or to have in line with the parts status. the
it removed in the flow status of PARTS required
prior events IN-OUT template. schedule

Schedule Challenge the inputs

pattern Yes provided by CPM and
change re-validate the
Observed? Inventory file/Op
data.

No
Resolv
ed

The above flowchart gives a broad outline focussing on the outage fixing. The bottlenecks
lies in examining the root cause of the issue and applying CPL/dates on a Trial and error
basis. Improvising in this regard would help in streamlining the process.

This flowchart identifies the above four areas viz, Limiting parts, Threshold logic, Existing
CPL’s & Start/End dates to be focussed upon. Further discussion will bring about other areas
of concern.