Complex MRO

Defines and manages the work scope for a complex MRO event: assessing the serialized asset structure, generating maintenance events, configuring and approving the work scope, and establishing the interim order structure that pegs together all shop orders and the work order where costs accumulate.

Manages material demand, pegging, reservation, staging/kitting and issue of parts for the MRO event, including customer-owned versus company-owned material determined by part provisioning rules on the service or heavy maintenance contract.

Plans and schedules the maintenance visit against hangar capacity and resources, assigns technicians and tools to tasks, and executes hangar maintenance including raising and packaging non-routines through to aircraft release.

Manages task sign-off, independent inspection (RII), configuration validation via CMS, and issuance of airworthiness part certificates in accordance with airworthiness regulation codes and ATA Spec2000, to release repaired/overhauled objects as serviceable.

Captures labour time against work/shop order operations via clocking or job-hour reporting, rolls actual labour and machine hours into cost, and accumulates all MRO costs on the work order through the interim order structure for cost control and invoicing.

Manages receipt of customer-owned assets into inventory, execution of the contracted work scope, return dispatch to the customer, and invoicing, using receive orders (purchase order type), dispatch orders (customer order type) and external service orders for subcontracted repair.

Executes the component overhaul shop-floor process through the sequence of disassembly, disposition, repair and assembly shop orders pegged by the interim order structure, with serialized part tracking, disposition discrepancy codes driving repair/external service orders, and task confirmation.

Executes in-house repair of customer-owned units returned to a manufacturer's repair depot, using the IFS Cloud Component Repair Order as the umbrella object that links the customer order, inventory, repair order, part service contract, cost lines and sales lines. The unit is received against a CRO repair line, a work scope and repair order type are selected, technicians execute and test, and the line is signed off, cost and sales lines are generated and transferred to the customer order for invoicing. Units found beyond economic repair exit to scrap or quotation rather than continuing through the repair flow.

Restores returned cores and used assemblies to a defined saleable condition through the IFS Cloud MRO shop order chain, where a disassembly shop order strips the unit, a disposition shop order decides receive or scrap per component and raises repair orders, repair shop orders fix the real parts, and an assembly shop order rebuilds the unit. Refurbishment returns a unit to a serviceable condition, while remanufacturing is the rigorous industrial process of returning a used or non-functional product to like-new or better-than-new condition through a controlled, reproducible process. The output is stock for the exchange pool or for sale, not a repair returned to a named customer.

Covers the arrival of a platform or major end item at a depot and its establishment as a maintainable, serialized record in IFS Cloud. The incoming asset is created or updated as a serial structure in Fleet and Asset Management - either manually, by copying an active template structure, or via the Import Asset CSV load documented for asset induction in repair and overhaul processes - and the induction work order or maintenance order that will carry the visit is raised against it. Ownership, workshop, location and maintenance group are captured on the serial so that customer-owned and government-furnished platforms are segregated from company-owned stock from the first transaction.

Executes the strip and inspect phase of a depot visit through the IFS Cloud Complex Assembly MRO shop order chain. Disassembly shop orders take their material from the work order for the overhaul object or a previous disassembly order and output the components to be disassembled plus the remainder of the overhauled part; disposition shop orders then authorise inspection and disposition of those unknown or uninspected items. Because the real configuration is unknown before teardown, both order types are created against position parts and only resolve to identified real parts as the inspector works the disposition lines.

Defines what work a depot visit will actually contain and controls the additional work discovered after the visit starts. In IFS Cloud the planned scope is assembled by prioritising pending maintenance events against a maintenance opportunity window, and the resulting work scope drives the interim MRO order structure; disposition shop orders are generated either through the initial work scope or through revaluation of that work scope after inspection of disassembled components. On the component repair side, service types both define a work scope and act as the price label for the work performed, with the part service contract as the primary source of price.

Manages the serial-tracked spares that rotate between supplier, stock, the customer, the platform and the repair shop. IFS Cloud provides a native Rotable Part Pool feature that lets segments of inventory be defined as rotables and grouped into company-owned, customer-owned or fixed asset rotable pools, with strict availability control rules that make pooled serials non-plannable, non-reservable and non-transferable until they are manually removed from the pool. For defense sustainment this is the mechanism that keeps government-furnished and customer-owned rotables financially and physically ring-fenced from company stock.

Executes the actual repair of removed components and maintains unbroken serial history through it. In IFS Cloud a repair shop order is an electronic document that authorises the repair or modification of a part; it is created with the Repair shop order type, allocated the part to be repaired, and generated either at the time of dispositioning component serials or at the time an assembled item is received. Serial identity is preserved through the Part Serial Catalog and Fleet and Asset Management history records, including the rename mechanism used when a modification changes the part number of a serial.

Rebuilds the overhaul object and proves it fit to return to service. Assembly shop orders draw material from inventory, disposition orders or repair orders and their expected output is the overhauled object or reassembled component; like the other MRO order types they are created initially for position parts and are assigned real parts once those parts are identified. The as-built serial structure must then reconcile to the template: a serial is only Operational when its configuration conforms to or exceeds the minimum configuration of the template structure, and it cannot be put into operation while Non Operational.

Manages the definition, assignment, execution and compliance recording of modifications - the IFS Cloud construct used to carry what defense operators call technical directives, TCTOs, service bulletins and retrofit campaigns. A modification is defined, then a modification program assigns part numbers and revisions and sets whether it executes at next visit in any workshop, at next interval maintenance, or at a calculated time from operational parameters or a calendar interval. Serial assignment is by revision for all serials or by serial range, and where a modification changes part identity the serial is renamed automatically when the terminating action is performed.

Certifies that a maintained, repaired or overhauled item is serviceable and releases it back to the operator using the IFS Cloud part certificate flow, where approval organisations, authorities, form types and authorised approvers are configured as basic data and only approvals in Approved status are valid for generation. Certificates are generated from maintenance orders, work orders and complex assembly work orders in Work Done, Reported or Finished status, and from CAMRO and CRO shop orders, via the Print Release to Service assistant. Before the form is produced the system validates that all work on the order is completed or cancelled and that there are no overdue maintenance events for the serials in the serial structure, then sets the operational condition of the serial structure to Operational.

Runs depot repair and refurbishment while keeping the work on the servicing side of the FDA remanufacturing boundary. IFS Cloud carries the flow as RMA receipt into the depot, a repair Work Order with a linked repair Shop Order that issues and receives back the same serial, traceable part consumption, QA release via the operational condition change, and MRO shipment back to the customer. The scoping decision - whether the intended activity significantly changes the finished device performance or safety specifications or intended use - is the control point, and it has no standard IFS Cloud object.

Plans, executes and reports generating unit outages across the full event spectrum - planned overhauls and refuelling outages, maintenance outages, and forced events. IFS Cloud carries the outage scope as a Project or Maintenance Event with Work Orders and Work Tasks, the long-lead procurement, the component history on Serial Objects, and the event data needed for availability reporting. Correct event classification and cause coding is what makes the resulting availability statistics defensible.

Manages the second life of a machine after trade-in, end of rental life or end of lease. The unit is appraised against its Serial Object history — hours, meter readings, work order history and damage records — and given a disposition of retail refurbishment, wholesale, parts recovery or scrap. Refurbishment runs as a Work Order or Shop Order that accumulates reconditioning cost onto the unit, after which it is re-certified, published as a used Sales Part with a used-equipment warranty and remarketed.