This chapter covers the following topics:
Oracle Complex Maintenance, Repair, and Overhaul (CMRO) is an integrated, web-enabled, software application suite designed for complex equipment maintenance organizations. It supports typical maintenance processes such as scheduled and unscheduled maintenance visits, component monitoring, job scheduling and routing, labor time collection, cost collection, inventory management, and maintenance document management.
You can view maintenance practice improvement opportunities, and opportunities to improve fleet readiness. The application provides models for electromechanical systems and defines rules for assembling units. You can record unit-specific information, enabling quick access to the maintenance history of a product component. It provides maintenance organizations a means to reduce operational costs, and thereby to yield improved profitability.
Oracle CMRO enables maintenance organizations to meet customer expectations, and draw maximum benefit by improving the operational readiness of equipment. Key features include:
Oracle Supply Chain Planning, Oracle Complex Maintenance, Repair and Overhaul Process Guide
Auto Visit Forecasting and Packaging, Oracle Complex Maintenance, Repair and Overhaul Process Guide
Aircraft Maintenance Planning, Oracle Complex Maintenance, Repair and Overhaul Process Guide
Complex Assembly Maintenance, Oracle Complex Maintenance, Repair and Overhaul Process Guide
Component Maintenance, Oracle Complex Maintenance, Repair and Overhaul Process Guide
Visit Work Planning, Oracle Complex Maintenance, Repair and Overhaul Process Guide
Fleet Associations and Simulations, Oracle Complex Maintenance, Repair and Overhaul Process Guide
Non Routine Analysis and Maintenance Requirement Profiles, Oracle Complex Maintenance, Repair and Overhaul Process Guide
Service Bulletin Effectivity, Oracle Complex Maintenance, Repair and Overhaul Process Guide
Oracle Projects Integration Enhancements, Oracle Complex Maintenance, Repair and Overhaul Process Guide
FAA Compliance Reports, Oracle Complex Maintenance Repair and Overhaul User's Guide
Oracle CMRO includes intelligent processing and direct input to Oracle Value Chain Planning (VCP) suite of products. This integration enables a more complete and intelligent processing of forecasted, planned, and consumed materials.
Currently, the CMRO Unit Maintenance Plan contains the instance-specific maintenance needs projected out into the future. This instance-specific maintenance plan includes the material and resource demand needed to keep the units serviceable, and the time frame in which this demand will be required.
See Oracle Supply Chain Planning, Overview of CMRO Features, Oracle Complex Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
The automated visit forecasting process is a tool for the maintenance planners to group maintenance requirements together to support both a rough-cut visit plan and an operational maintenance plan (Primary Plan), based on a maintenance organization. This enables the planner to approach the plan and focus on the exceptions for both short and long term planning. This feature is used primarily for heavy maintenance such as letter checks and modifications. It is typically used to forecast 12-18 months into the future.
See Auto Visit Forecasting and Packaging, Overview of CMRO Features, Oracle Complex Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
The Aircraft Maintenance Planning workbench improves the scheduling and accomplishment of maintenance requirements for unit configurations for aircraft, but also for engines and APUs for both line and base maintenance. This workbench enables users to search for requirements that are due through a new version of the current UMP search capability. Users can then identify opportunities in which to schedule the maintenance to existing or new visits, while taking flight schedules, organizational scheduling and fleet downtime into consideration.
See Aircraft Maintenance Planning, Overview of CMRO Features, Oracle Complex Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
The workbench can be used for any complex assembly, where tracking maintenance at the configuration position for the subcomponent is required in the execution process. The workbench enables users to search for both repair demand for complex assemblies from ASCP (or another source system), and locate assemblies requiring repair both on and off wing.
See Complex Assembly Maintenance, Overview of CMRO Features, Oracle Complex Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
In addition to the complex assembly workbench, the component maintenance workbench expands the planning functionality for an operation. Users can search and plan for component maintenance, both serialized and non-serialized. This workbench provides the ability to search for repair demand for components from ASCP (or another source system), and locate components requiring repair that are in an unserviceable inventory.
See Component Maintenance, Overview of CMRO Features, Oracle Complex Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
CMRO's existing visit work package (VWP) functionality has been enhanced to support the introduction of the ASCP functionality throughout CMRO. Enhancements were made to several existing UIs and new UIs were created.
See Visit Work Planning, Overview of CMRO Features, Oracle Complex Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
See Fleet Associations and Simulations, Oracle Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
CMRO includes tools to analyze the historical occurrence of non-routine maintenance, and to create non-routine planning factors and estimates which can be applied during the maintenance planning process. Non-routine history can be evaluated in the Oracle Demantra application based on the associated maintenance requirement, aircraft, fleet, and program type of maintenance accomplished. The output can then be applied within CMRO by creating maintenance requirement profiles.
These profiles enable the creation of non-routine estimates for an MR based on the Program Type and operating organization in which it would be accomplished. For example, an MR that occurs in an A-Check may generate different non-routines than in a C-Check, depending on the operating organization.
See Non Routine Analysis and Maintenance Requirement Profiles, Overview of CMRO Features, Oracle Complex Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
CMRO includes functionality to cover more completely the detailed scenarios that are involved in planning, performing, and proving compliance with Service Bulletins, Service Letters, and Airworthiness Directives. These types of maintenance requirements can have a complex relationship between each other, the aircraft or assembly configurations, and the history involved. As a solution to this complex network of allowed parts, required maintenance, and historic life, CMRO includes the following functionality such as effectivity triggers and service bulletin rules.
See Service Bulletin Effectivity, Overview of CMRO Features, Oracle Complex Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
The Oracle Production Scheduling (PS) integration has been optimized to enable CMRO engineering definitions to direct the visit structure and work order relationships, while still maintaining the power of the PS engine. This enables the complete optimization and visibility of CMRO visits, work orders, resource requirements, and material requirements within the PS tool. Some of the highlights of this integration are:
The CMRO Work Breakdown Structure (WBS) can be defined as a template for a visit, then adjusted specifically for each instance of the visit.
This WBS definition gives further direction to the PS engine as to the order, precedence, and dependency among work orders.
Visit stages are passed and used within the PS engine and are also visible in the UI.
Non-routine (NR) estimates defined in CMRO are used to plan accurately for a visit before the actual NRs exist in the visit.
Alternate item information is passed to PS to enable the scheduling engine to optimize the completion schedule.
PS scheduled dates are passed back to CMRO Visit Work Package for comparison and adjustment against the visit planned dates, as necessary.
The Oracle Projects integration was enhanced to include functionality such as the ability to define the cost hierarchy for project tasks, add visits to parent projects, synchronize visit and project tasks dates, and define service types.
See Projects Integration Enhancements, Overview of CMRO Features, Oracle Complex Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
The key features of the CMRO Fleet Maintenance Program are:
Maintenance requirements creation enable maintenance personnel to create maintenance requirements with attributes uniquely defining the requirement.
Maintenance routes association by attaching appropriate routes created in the Route Management module to the maintenance requirements.
Maintenance documents association by attaching the appropriate documents from the Document Index to the maintenance requirements.
Effectivity definition enabling personnel to be automatically notified regarding the maintenance requirements applicable to certain physical units within the database.
Interval and threshold definition enabling a schedule to be set that counts down until the maintenance requirement is due for a unit.
Maintenance requirements and dependent relationships management enabling the use of group relationships for non-complicated parent child components where the parent maintenance requirement accomplishment includes the children.
Affected items listing providing a comprehensive view of the items that are covered by a maintenance requirement's effectivity.
The key features of the CRMO Document Index module are:
Receipt and registration of documents.
Upload and revision of electronic documents.
Document subscription control through supplier information recording and subscription status tracking.
Document revision control ensuring current and accurate information.
Document status lookup enabling document version verifications from multiple levels during maintenance operations.
Document Distribution Control ensuring authorization of a person (who requests a document) to receive a document.
The integration between CMRO and Enigma 3C is to provide a ready-to-use solution for MRO service providers to provide the maintenance technicians with a set of tools that connect CMRO's extensive back office functionality for configuration management, engineering and maintenance planning with Enigma's flexible and easy to use documentation centric maintenance execution system, in a wireless or disconnected environment.
This combination of the two products supports the maintenance technicians in efficiently executing all their maintenance tasks, achieving highest level of quality by providing the right information in the right place at the right time in a most user-friendly form.
See Integration of Oracle CMRO and Enigma 3C for more information regarding this integration.
The key features of the Master Configuration module are:
Assembly tree structure representing the positions of tracked or required components that make up a complex assembly.
Assembly qualification by identifying the components required to meet a certain specification.
Tracked parts positioning.
Definition of parent-child relationships between components in an assembly.
Configuration templates for unit configuration modeling the general characteristics of a fleet unit.
Cost rollup structure enabling the division of maintenance cost by the modules of an assembly.
Definition of alternate parts allowable for each component position in an assembly.
Definition of position ratios to use in counter updates between positions in a master configuration hierarchy.
Maintenance document association to master configuration positions.
The key features of the Unit Configuration module are:
Unit composition providing information on the hierarchical positions of parts within a unit.
Physical location tracking of parts.
Recording of child unit installation and removal on or from parent assemblies.
Recording of utilization or age of parts in an assembly based on different parameters related to the usage of parts and events that affect the parts.
Utilization population from parent to child units enabling the determination of component aging as a result of the attachment to other parts, or parent units, that gain utilization.
Unit maintenance history tracking through all previously accomplished maintenance requirement records.
Equipment ownership history tracking enabling the analysis of impact on business procedures due to ownership changes.
Temporary parts identification enabling the assignment of temporary serial numbers to parts in an acquired unit.
The key features of the Product Classification module are:
Hierarchy-based product classification creation and maintenance.
Maintenance requirements and documents association to any level in the product classification using a tree-based hierarchy to reduce the administration necessary when adding a new product to a maintenance program.
Logical Product grouping across multiple levels.
Primary and supplementary classification support that enables part and unit grouping from multiple viewpoints.
The key features of the Unit Maintenance Plan module are:
Utilization forecast maintenance that provides the utilization forecast in terms of the applicable time based unit of measures for each unit in the fleet.
Serviceable time unit of measure (UOM) of units viewing for the parent unit and all child units expressed in terms of the appropriate UOM, such as hours, cycles, mileage, and so on.
Repetitive maintenance requirement modeling over a user-defined period providing the UOM remaining for each occurrence of a maintenance requirement.
Due date calculation of maintenance requirements based on utilization forecasts and maintenance frequencies in the absence of a specified fixed due date.
Association of maintenance requirement groups to a visit.
The key features of the Material Marshalling module are:
Search units and associated visits, and view the progress and status of each visit.
View the material requirements of a visit. This view organizes the material requirements by their association within the associated configuration and positions of the visit.
Issue the required materials from other subinventories when the visit subinventory and locator cannot accommodate the material requirement of a work order.
The key features of the CMRO Planning module are:
Assessment of a maintenance base's workload capacity analysis of available labor by skill, available tooling and machinery, available materials and the location's capabilities, such as the list of units and requirements that the location can support, balanced against known workloads.
Visit creation to group together events for long and short-term capacity planning and to facilitate scheduling to a maintenance base.
Definition of visit resource requirements based on the unit, man hour requirements by skill, required tooling, required materials, duration and required completion times of the maintenance requirements and routes for the visit.
Visit appointment creation based on maintenance base resource forecasting and visit requirements.
Resource balancing capacity versus workload requirements for scheduling purposes and efficiency assurance.
Resource leveling on different simulation plans enabling the identification of the best resource capacity plan.
The key features of the Administration module are:
Departmental work shift schedule definition enabling maintenance planners to select shift schedules for the departmental workers who perform the inspections and repairs.
Calculating spaces and space unavailability.
Eight reports are available for use. Reports can be printed, exported, and viewed online.
See Projects Integration Enhancements, Overview of CMRO Features, Oracle Complex Maintenance, Repair and Overhaul Process Guide for more information regarding this feature.
The key features of the CMRO Production Planning module are:
Job creation from visit tasks for Scheduled, Unscheduled, and Convenience maintenance.
Service request creation to track reported problems.
Operations to non-routine jobs creation for work definition and tracking.
Job maintenance through status, completion, and start and end date adjustments of the schedule.
Operation maintenance by addition, removal, material and resource requirement updates, cost capture, and resource assignment review.
Quality maintenance using Route Management.
The key features of the Outside Processing module are:
Assign production jobs for third-party service.
Add or remove production jobs to an existing OSP work order.
Determine how and when the parts will be shipped to the supplier.
Create and approve purchase orders.
Create purchase requisitions for an OSP order.
Receive shipments for an OSP order.
Use the CMRO Home page to quickly access the menus to efficiently manage the maintenance, repair and overhaul of your complex, high-valued assets. You can access the following menus and their respective tabs from the CMRO Home page:
Engineering
Document Index
Route Management
Fleet Management Program
Reliability
Configuration
Master Configuration
Unit Configuration
Product Classification
Supplier Warranty
Planning
Unit Maintenance Planning
Visit Work Package
Planning Workbench
Fleet Forecasting
Component Maintenance
Assembly Maintenance
Auto Visit Planning
Administration
Approvals
Workflow
Department Location
Spaces
Space Availability
Reliability
Vendor Sourcing
Reports
WBS Rules
Visit Types
Utilization History
CMRO Analytics
Maintenance Requirement Status Reports
Execution
Production Planning
Outside Processing
Service History
Material Transactions
The Minimum Equipment List and Configuration Deviation List functionality identifies equipment, as opposed to structural items that can be inoperative or missing on aircraft, but still enables the aircraft to maintain airworthiness. This includes items such as radios, seats, lights, air conditioning, heaters, and indicators. These items, called provisos, can be inoperative under certain conditions. Limitations may be required as how the aircraft is operated. For example, there may be limitations regarding ice conditions, night flights, or altitude limits. When non-routine maintenance requirements are discovered during inspections, you can create a service request and determine if the requirement should be deferred to subsequent visits using MEL or CDL instructions.
An MEL addresses defective equipment, and a CDL addresses missing parts in an aircraft. This functionality includes:
Definition of the lists is based on Air Transport Association of America (ATA) specification codes.
MEL and CDL instructions are associated to a product classification. The applicable ATA codes are defined, along with the corresponding repair times, installed quantities and minimum required quantities. These ATA codes and minimum quantities are used to identify the eligibility of MEL and CDL deferrals for the unit, based on the ATA code definitions in corresponding master configurations.
Issues can be logged by a pilot, crew member, or technician, and flagged as a potential MEL or CDL item.
The system automatically identifies applicable MEL and CDL instructions based on the associated configuration position.
Maintenance requirements are deferred against associated MEL and CDL instructions.
When a requirement is deferred against the MEL or CDL, applicable Maintenance and Operation (M) and (O) procedures are automatically added to the maintenance visit. These procedures are defined in engineering as maintenance requirements, and the applicability is determined based on effectivity definitions and defined ATA codes.
See: Minimum Equipment List (MEL) and Configuration Deviation List (CDL) Setup
Oracle CMRO uses modules from other Oracle applications.
Organizations perform maintenance operations on an electromechanical system to maximize the service life of that asset. Maintenance operations require that the service life of a system, or the components comprising it, be measured. Timers and counters become important here. Car odometers, for example, are counters. Meters used to record the operating hours of power plants on aircraft and boats are timers. Maintenance is typically performed periodically, based on elapsed operating time. Oracle CMRO meets these needs through its integration with the Oracle Counters application.
Oracle CMRO user uses an Oracle Counters instance to represent a timer when defining models for system configurations. The service life of a component is measured according to the nature of that component's role, and service life measurements are selected by failure mode analysis. Calendar time is of interest because of possible corrosive conditions resulting in damage over time. Counter instances are sufficiently flexible, and Oracle CMRO users can define the counters using the appropriate unit of measurement associated with a component.
Maintenance organizations gain many advantages by modeling a template for electromechanical system assemblies and individual fleet units. After an Oracle CMRO user completes the definition of a master configuration, a framework then exists that describes the general characteristics of the system including the engineering rules for assembly. The user can then create a unit configuration.
Oracle CMRO invokes the Installed Base methods to populate the database with a transaction representing the as-operated or unit configuration of an electromechanical system.
Maintenance organizations can greatly improve operational efficiency by planning their material requirements. The Master Configuration module of Oracle CMRO provides a template for the structure of an electromechanical system, and lists the components that are allowable in the different positions of a system configuration. The Unit Configuration module describes the as-installed configuration of a specific fleet unit. This helps organizations predict to approximate the material requirement to maintain the operational readiness of fleet units.
Oracle CMRO user uses instances of Oracle Inventory when defining the allowable parts in a master configuration for an electromechanical system, and when describing the components in a unit configuration.
Oracle CMRO uses the setup from Route Management and the system profile options in Oracle Quality, to enable maintenance organizations to capture quality elements for operations, jobs, deferrals, scrap management, and capture counter value snapshots. This functionality provides maintenance facilities the flexible integration required to maintain reliable products. Oracle CMRO provides seeded plan templates for routes, operations, job deferrals, MRB dispositions and counter reading capture. These templates can be used as-is or adjusted with additional quality elements, except the counter reading template which is used by CMRO in the background and cannot be changed.
Oracle CMRO integrates with Oracle Advanced Planning and Scheduling (APS) applications for supply chain management. Advanced Supply Chain Planning (ASCP), is used to schedule required materials from maintenance visits. Available to Promise (ATP), is used for material availability inquiries, as well as scheduling through ASCP. Oracle Demantra Demand Planning is used to create material demand from three sources: global demand from forecasted requirements in the Unit Maintenance Plan module; scheduled demand from requirements scheduled to maintenance visits; and historical non-routine (and routine) demand from the maintenance performed at specific facilities. Additionally, Oracle APS Inventory Optimization (IO) application is required for complete supply chain planning.
Oracle CMRO integrates with Oracle Purchasing to set up buyers, approvals, purchasing options, receiving options, financial options, and open accounting periods. Oracle Purchasing is directly integrated with CMRO's OSP module and enables the creation of purchase requisitions or purchase orders when required for outside vendor services.
Oracle CMRO integrates with Oracle Projects to define a cost hierarchy for project tasks, add visits to parent projects and synchronize visit and project task dates. In addition, services types are defined in Oracle Projects, and are used in CMRO to identify routine and non-routine maintenance activities.
Oracle Warehouse Management provides maintenance organizations, the functionality to control their inventory by status or condition and associate subinventories with a department.
Oracle CMRO integrates with Oracle Order Management to set up processing constraints and create customers. Oracle Order Management is directly integrated with the CMRO Outside Service Processing module and enables the creation of service orders with shipping lines for shipping and receiving items when required for outside vendor services.
Oracle CMRO uses the same work order system as Oracle Enterprise Asset Management (eAM). It also uses the Oracle eAM functionality to complete operations. Oracle CMRO benefits from the integration of Oracle eAM with Oracle Costing.
Oracle Support provides Oracle CMRO with the functionality to create and update service requirements in a maintenance organization. The association of a service request to a visit task and production job enables the maintenance organization to track the service difficulty (non-routine) to the associated progress or resolution performed by the maintenance personnel.
The integration of Oracle CMRO and Enigma 3C delivers the functionality to manage entire maintenance operations from configuration management and engineering to maintenance planning and execution for a maintenance organization.
Enigma 3C delivers a dynamic service index of maintenance, parts and diagnostic information, that captures the operational expertise and connects to vital corporate systems to manage and optimize the service and support workflow.