The alarms generally indicate when an MRO interim order cannot be started because one or more supply interim orders are late. Alarms also are generated when the top-level disassembly order delays the start of one or more component interim orders, as well as when the top level assembly order cannot be finished on time. Alarms can be evaluated for the maintenance, repair, and overhaul (MRO) interim order structure in the Alarms tab.
On the disassembly side of an order structure, the alarm indicates that a disassembly or disposition order cannot be started because the supply date of its parent interim order is on or after the start date of the interim order itself. Note that a disassembly order date change will impact only the next interim order in the chain (either a disassembly or disposition interim order). It cannot impact more deeply nested disassembly and disposition interim orders or repair or assembly interim orders. Similarly, a disposition order date change can impact only the next interim order in the chain (either a repair order or an assembly order). It cannot impact assembly or repair interim orders further up the chain.
On the assembly side of an order structure, an alarm indicates that an assembly or repair interim order cannot start because a supplying disposition, repair or assembly order has a supply date after the start date of the interim order in question. A date change to a repair or assembly interim order will impact the assembly order that order feeds. It cannot affect other assembly orders further up the chain.
The interim order structure being evaluated cannot be in a Canceled or Closed state.
Optionally, you can use the command Resolve Alarm to set the state of an alarm to Resolved. Usually, you will do this after taking manual action such as expediting an order, or taking material reserved for other orders to satisfy the interim order in question. If you do set the alarm to Resolved, your user ID and the date will be recorded.