Você está na página 1de 94

Title:

Modeling Standards

Subject: MRO Standard Solution


Maintenix Version:
Document Version:

v6.8.13 SP2
1.0
th

Created Date:

September 7 , 2011

Last Updated:

July 4, 2012

Reference:

Maintenix Solution Delivery Framework

This document contains valuable trade secrets, proprietary and confidential information of Mxi
Technologies Ltd., protected by national laws and international treaties, the unauthorized
disclosure of which will result in significant damages to Mxi. THIS DOCUMENT MAY NOT BE
COPIED, OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT
WAS PROVIDED, OR TO PERSONS OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY
PROVIDED. This document shall not be reproduced, copied or transmitted in any manner or
provided to third parties. 2011-2012 Mxi Technologies Ltd. All Rights Reserved

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Contents
1

INTRODUCTION .............................................................................................1

1.1
1.2
1.3
1.4

DOCUMENT PURPOSE AND SCOPE .................................................................1


DEFINITIONS AND ABBREVIATIONS ..................................................................2
ASSUMPTIONS ..............................................................................................3
LIMITATIONS/CONSTRAINTS ...........................................................................3

THE BUSINESS CONTEXT ...............................................................................4

2.1
2.2
2.3
2.4
2.5

BUSINESS PROCESSES ..................................................................................4


RECOMMENDED SOLUTION ............................................................................6
MAINTENIX MODULES ....................................................................................6
SUPPORTED MAINTENIX VERSION ...................................................................6
HIGH-LEVEL CONCEPT ...................................................................................6

2.6

2.7
2.8
2.9
2.10
2.11
2.12

2.5.1
MRO-01 Quotations ......................................................................................... 7
2.5.2
MRO-02 Award of Contract ............................................................................. 8
2.5.3
MRO-03 Workscope Loading .......................................................................... 9
2.5.4
MMDF-01 - Part Request Management ........................................................... 13
2.5.5
MRO-10 Part & Tool Provisioning ................................................................. 15
2.5.6
MMDF-02 - Pre-Draw and Issue Inventory ....................................................... 19
2.5.7
HMVP-02 Work Packaging ............................................................................ 20
2.5.8
HMPPC-01 - Workpackage Printing ................................................................. 21
2.5.9
HME-01 Maintenance Execution ................................................................... 24
2.5.10
HME-03 Non-Routine Handling ..................................................................... 25
2.5.11
SMMC-04 Component Shop Work Management .......................................... 28
2.5.12
MRO-12 Engine Shop Management ............................................................. 29
2.5.13
MRO-05 Aircraft Release / Customer Signoff ................................................ 30
2.5.14
MRO-06 Invoice Generation .......................................................................... 31
2.5.15
MRO-07 Part and Tool Dispersal .................................................................. 34
2.5.16
MRO-11 Contract Compliance Monitoring ..................................................... 36
2.5.17
MRO-08 Review of Performance ................................................................... 38
2.5.18
FRMRP-01 Define Stock Levels .................................................................... 39
2.5.19
MEMPH-02 Create Edit Maintenance Requirements .................................... 40
2.5.20
MRO-09 Marketing / Sales Planning ............................................................. 41
2.5.21
MECRM-02 Define and Maintain Allowable Configuration ............................ 42
2.5.22
MRO-12 3rd Party Component Maintenance ................................................... 43
2.5.23
Materials Management ..................................................................................... 45
BASELINE DESIGN .......................................................................................56
2.6.1
Equipment Baseline .......................................................................................... 56
2.6.2
System Baseline ............................................................................................... 57
2.6.3
Materials Baseline ............................................................................................ 59
DATA MIGRATION DESIGN ............................................................................62
2.7.1
Scope of Data Migration ................................................................................... 63
USE CASE IMPACT ......................................................................................65
CUSTOM SOFTWARE/REPORTS ....................................................................66
2.9.1
External Maintenance Adapter (EMA) .............................................................. 66
DATABASE RULES .......................................................................................66
PERFORMANCE CONSIDERATIONS ................................................................66
KNOWN ISSUES ...........................................................................................66
Page i

Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

APPENDIX A

TOOL PROVISIONING REPORT ........................................................67

APPENDIX B

INVOICING SOLUTION ....................................................................69

APPENDIX C

IDENTIFICATION OF MRSP AND VENDOR PRICES ............................85

APPENDIX D

SHOP CONTROLLERS REPORT ......................................................86

APPENDIX E

ORDERED TASK CARD COVER PAGES ...........................................87

Page ii
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

List of Tables and Figures


Table 1- Workscope Loading Configuration Parameters ............................................................... 12
Table 2 - Shop Controller's Report................................................................................................. 86

Figure 1 - High Level MRO Workflow .............................................................................................. 5


Figure 2 - Maintenix Modules ........................................................................................................... 6
Figure 3 Quotations ....................................................................................................................... 7
Figure 4 - Award of Contract ............................................................................................................ 8
Figure 5 - Induct Workpackage ........................................................................................................ 9
Figure 6 - MRO-10 Part and Tool Provisioning .............................................................................. 15
Figure 7 Workpackage Printing ................................................................................................... 22
Figure 8 - HME-03 Non-Routine Handling ..................................................................................... 25
Figure 9 - MRO-05 Aircraft Release / Customer Signoff ............................................................... 30
Figure 10 - MRO-07 Part and Tool Dispersal ................................................................................ 34
Figure 11 - Review of Performance ............................................................................................... 38
Figure 12 - MRO-09 Marketing & Sales Planning .......................................................................... 41
Figure 13 - 3rd Party Component Repair ....................................................................................... 44
Figure 14 - Configuration Parameter Settings ............................................................................... 57
Figure 15 - Invoicing Solution - Tasks - Part 1 ............................................................................... 70
Figure 16 - Invoicing Solution - Tasks - Part 2 ............................................................................... 71
Figure 17 - Invoicing Solution - Tasks - Part 3 ............................................................................... 72
Figure 18 - Invoicing Solution - Labour and Tools ......................................................................... 76
Figure 19 - Invoicing Solution - Parts Provisioning ........................................................................ 79
Figure 20 - Identification of MSRP and Vendor Prices .................................................................. 85
Figure 21 - Ordered Task Card Cover Page .................................................................................. 89

Page iii
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

1 Introduction
1.1 Document Purpose and Scope
This document is intended to describe a recommended solution design, for the key solution distinctions
for an MRO with long-term contracts to support aircraft maintenance. It is intended to help standardize in
Maintenix, across projects using the same version of Maintenix, and those that have common business
processes. This document should provide a sufficient level of details to describe both the business
context and a recommended solution, such that a person familiar with Maintenix can understand the
business issue and be able to implement the solution with more ease. This document will, where feasible,
describe why the recommended solution was chosen over other potential solutions.
For each solution element, the following sections will be described:
Background
A general background to the business problem, from the perspective of an MRO with long-term contracts.
Background: Alternate Flow FMA
If the business problem is different for an MRO offering fleet managed aircraft (FMA) services, this section
will identify the differences.
Background: Alternate Flow Ad Hoc
If the business problem is different for an MRO offering Ad-Hoc services, this section will identify the
differences.
Background: Integrated Airline Solution
If the business problem is different for an organization that is both an Airline and an MRO, and both are
maintained in the same system, this section will identify the differences. This section assumes that the
MRO is one with long-term contracts.
Solution
This section covers the Maintenix solution to the business problem, from the perspective of an MRO with
long-term contracts.
Solution: Alternate Flow FMA
If the Maintenix solution is different for an MRO offering FMA services, this section will identify the
differences.
Solution: Alternate Flow Ad Hoc
If the Maintenix solution is different for an MRO offering Ad-Hoc services, this section will identify the
differences.
Solution: Integrated Airline Solution
If the Maintenix solution is different for an organization that is both an Airline and an MRO, and both are
maintained in the same system, this section will identify the differences. This section assumes that the
MRO is one with long-term contracts.
Standard Configuration
This section summarizes Standard Configuration elements required to support this solution.
Reports
This section summarizes all custom reports that are needed to support this solution, as well as standard
reports that may be modified..
Page 1
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

1.2 Definitions and Abbreviations


Term

Definition

Alert Level

The price level at which client approval should be initiated. For example, the alert
level may be about 20% lower than the cap level, so that the client approval
process doesnt delay maintenance. Applicable to tasks that are T&M with cap.

AOG

Aircraft on Ground. A fault is referred to as an AOG fault if the aircraft is not


allowed to fly until the fault is resolved or preventative measures have been put
into place.

AWR

Additional Work Request. Any amendment to the contract after it was originally
signed. For example, if a contract is signed, then an AD is issued. The MRO will
amend the contract to have the work done in the same visit. AWRs have separate
contracting rules.

BP

Business Process a diagram and/or document that describes the high-level


business activities and workflow for a specific process in the organization.

Cap Level

The price level at which client approval must be received in order for the MRO to
charge for additional work. Applicable to tasks that are T&M with cap.

DB Rules

Database Rules a standard set of SQL queries that validate that data in
Maintenix is correctly set up.

FFP

Firm Fixed Price a method of contracting where the MRO offers to perform a task
for a fixed price, regardless of the actual cost.

FMA

Fleet Managed Aircraft. A vendor that offers FMA services will provide a
comprehensive maintenance offering, including planning, execution, engineering
and materials management.

KPI

Key Performance Indicators. KPIs are used to set and measure aspects of the
business, such as number of AOG part requests or adherence to TAT.

Maintenix

The Maintenix software

SAS

Standard Airline Solution a standard configuration of Maintenix to support midsized airlines. Many elements of this standard solution can be borrowed or
adapted to the Standard MRO Solution.

Standard Offering

No MRO stocks every conceivable part and tool. The parts and tools that are
provided by the MRO are considered part of the Standard Offering. If the client
wants a part or tool that is not a standard offering, it will be individually negotiated.

TAT

Turn Around Time the time between the aircrafts arrival at the MRO, and the
aircrafts departure. Activities are said to affect TAT if they delay the departure of
the aircraft.

T&M

Time and Materials The MRO will charge the client for the full cost of performing
this work, including parts and tools.

T&M with a cap

Time and Materials The MRO requires approval from the client if the work goes
over a predefined cost. If approval is granted, the MRO will charge the client for
the full cost of performing this work, including parts and tools.

Page 2
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

1.3 Assumptions
This Solution Design is based on the following assumptions:
1. Customers provide the scope of work for visits as a list of requirements in a format that can be
converted to Excel or a format that can be used as a starting point for conversion into the XML
message used by the External Maintenance Adapter (EMA). This list would comprise of MPD
item numbers and AD/SB numbers as well as occasionally client EOs and deferred non-routine
tasks.
2. Tools will be modeled as tracked or serialized components, other than personal technician tools,
which will not be tracked.
3. The MRO does not fabricate components. If that is the case, then additional processes and
solution elements will be required.
4. Each heavy maintenance visit uses a unique profit/loss center in finance / account number in
Maintenix. This account number is used to identify shop work and orders that are related to the
visit.
5. Each heavy maintenance visit has a contract that identifies the provisioning arrangements for all
parts and tools that are not normally provided by the MRO that is, parts that are not part of the
Standard Offering. This typically includes rotable parts, and can include rarely used consumables
and tools.
6. This document refers to SAS roles which may differ from those currently used by the customer.
The names of the roles can change without affecting the process flow.
7. Clients will not access Maintenix. Customer Service Representatives (MRO employees) will
record customer approvals and attach customer documents to the relevant location in Maintenix.
If the solution requires clients to access Maintenix, further business processes and solution
elements should be investigated.

1.4 Limitations/Constraints
The element solution design described in this document has the following limitations/constraints:
1. The document does not contain detailed data design elements, and is intended to complement,
rather than replace the Solution Feature Design Document (SFDD) specific to the project
solution.
2. The solution described in this document is based on Maintenix Version v6.8.13 SP2, and may not
be suitable for other versions of Maintenix. The standard will need to be updated and validated for
future versions.
3. The document does not contain detailed use case documentation, but instead tries to identify in
sufficient detail, that a project team could generate the detailed use case documents, for those
SAS use cases that need to be modified and any new use cases that should be created. Where
applicable, if the detailed documentation has been done by a previous project team references
will be provided.
4. The document does not contain detailed documentation on Database Rules, Customizations or
reports. Instead a brief description of what elements would be required for the solution is
provided, such that a project team could develop the appropriate documentation and solution
elements. Where applicable, references to detailed documentation and/or solution elements
previously produced by a project team will be provided.

Page 3
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

5. This solution is designed for an aircraft MRO with long term contracts. For each solution element,
the distinctions required to support an MRO that supports FMA or Ad-Hoc contracts are also
listed, as well as for solutions where the long term contract MRO is associated with an airline
operator.
6. This solution document does not cover Engine MROs. This solution does not cover OEM After
Market support solutions.
7. This solution does not cover line maintenance, only heavy maintenance.

2 The Business Context


There are five high level categories of MROs:

Fleet Managed Aircraft (Where the MRO maintains cradle-to-grave tracking)


Long Term Contract Aircraft (Where the MRO repairs the same aircraft repeatedly, but doesnt
track activity between visits)
AD-Hoc/Spot Market Aircraft
Engine
Component

This solution is focused on MROs with Long Term Contracts. It will also identify the deltas required to
support Fleet Managed and Ad-Hoc MRO solutions.
Most MROs with Long Term Contracts have the following activities that need to be supported by a
Maintenance and Material Management System:

Maintenance Planning & Execution


Induction of Client Aircraft and Contracted Work
Identification of Contract Exceptions
Induction, Handling and issues of MRO and Client materials
Generation of Data to support Invoicing

This document will start with the high level MRO business process, and identify the business background
for each section. In areas where the domain has already been fully or partially covered by SAS, any
differences are marked. In areas where the domain is not covered by SAS, the full solution is covered.

2.1 Business Processes


The following Business Process diagram shows the basic MRO workflow, starting with the quotations
process, and ending with the dispersal of parts and tools, and the generation of the invoice. The
rd
supporting activities planning, contract compliance management, Material Management and 3 Party
Component Maintenance are included accordingly.
In general, the SAS BPs supporting Materials Management, Engineering and Maintenance Execution are
used with minor modifications.

Page 4
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2
MRO-12
3rd Party
Component
Maintenance

MEMPH-02
Create Edit
Maintenance
Requirements

Material
Management

MRO-08
Review of
Performance

MECRM-02
Define and
Maintain
Allowable
Configuration

MRO-09
Marketing / Sales
Planning

FPMRP-01
Define Stock
Levels
Maintenance Execution
SMMC-04
Component Shop
Work
Management

MMDF-01
Part Request
Management
MRO-02
Award of
Contract

MRO-03
Workscope
Loading

MMDF-02
Pre-Draw and
Issue Inventory
MRO-12
Engine Shop
Management

MRO-10
Part & Tool
Provisioning

MRO-01
Quotations

MRO-06
Invoice
Generation

HMPPC-01
Work package
Printing
(Modified)
HMVP-02
Work Packaging

MRO-11
Contract
Compliance
Monitoring

HME-01
Maintenance
Execution

MRO-05
Aircraft Release,
Customer Signoff

HME-03 NonRoutine Handling


(Modified)

MRO-07
Part and Tool
Dispersal

HMPPC-02
Production
Control

Figure 1 - High Level MRO Workflow

This figure shows the workflow for an MRO that does not have information continuity between visits
each time an aircraft visits, it is considered to be a new aircraft. Maintenance activities on previous visits
(recurring faults, deferred maintenance, etc.) are not considered in the new maintenance visit.
The green elements are the feedback loop, which may not be executed for each maintenance visit.

Page 5
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.2 Recommended Solution


The following sections describe the recommended solution design) for the business need described in
this document. The rationale for recommending this solution is described in this section.

2.3 Maintenix Modules


Figure 2 - Maintenix Modules shows the Maintenix modules that are required for this solution. They
have been highlighted with a red border.

Figure 2 - Maintenix Modules

2.4 Supported Maintenix version


This design is supported by 6.8.13 SP2.

2.5 High-level Concept


This document will define the Standard MRO solution, outlining the overall MRO workflow, and identifying
where the Standard MRO Solution differs from the Standard Airline Solution.
For each of these differences, this document will identify the deviations from the SAS
This document has several appendixes, which cover some of the more lengthy topics in more detail,
including the invoicing solution.

Page 6
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.1 MRO-01 Quotations

Figure 3 Quotations

2.5.1.1 MRO Background


Once the Sales department agrees to provide a quotation to a client, the MRO-01 Quotations process is
initiated. The process is cyclical and ends when both the MRO and client mutually agree on content,
duration (TAT) and cost.
The client will provide a list of requirements that they are requesting the MRO perform. The planner in
the MRO will load this list of requirements into Maintenix and identify the tasks that they are not familiar
with. For the unfamiliar tasks, the engineering department at the MRO will research the task and identify
if they can provide an estimate for it. The materials management department will identify all of the rotable
parts and tools that are not part of the MROs standard offering. For each of these items, the proposal will
identify who will provide these parts (usually the client, and therefore at no cost to the MRO). Adding the
additional costs (e.g. hosting of client reps), discounts and other considerations, the MRO will provide a
quotation to the client.
If the client wants a quotation for a slightly different piece of work (for example, the original quote was too
high, additional work is required, or the Turn Around Time was too long), the process will be restarted.
The second iteration will be much faster, as the MRO only needs to update the existing quotation, rather
than start the process from the beginning.

2.5.1.2 Background: Alternate Flow FMA


MROs using a FMA process will not use this process to provide quotes, as theirs is a full-service offering
where the MRO will maintain the full maintenance program.

2.5.1.3 Background: Alternate Flow Ad Hoc


No changes
This is a key process for an Ad Hoc MRO it will be used on a regular basis.

2.5.1.4 Background: Integrated Airlines


No changes

2.5.1.5 Solution
The client requirements will be converted to an XML format. The data on the XML will be loaded into
Maintenix via the External Maintenance Adapter (EMA). This data will be updated as the Engineering
Department updates the requirements, and the sales department confirms with the client about the
provisioning of rotables and non-standard tools.
Page 7
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

When the client asks for an updated quotation, the spreadsheet is updated with the requested changes,
and reloaded. The non-baselined tasks will not need to be sent to engineering unless theres an update
(new version of the AD, for example).
The Quotations will be loaded into a separate Maintenix instance. The quotation process is expected to
generate many unwanted data as the Sales Department negotiate the contract with the client. This data
should not be in the main system. However, this information is available to be analyzed in order to
streamline the quoting process and perhaps improve the business.

2.5.1.6 Solution: Alternate Flow FMA


This solution overview will not cover the quotation process for FMA contracts.

2.5.1.7 Solution: Alternate Flow Ad Hoc


No changes

2.5.1.8 Solution: Integrated Airlines


No changes.

2.5.1.9 Standard Configuration


This process requires that the EMA be used to quickly and efficiently load the workscope.

2.5.1.10 Reports
Several reports will be required to provide the estimated effort, parts and tools required so that the
estimate can be put together. These are very similar to the reports that will be developed to support the
invoicing process, though as each customer has specific requirements for the format and content of these
reports, specific details are therefore outside of the scope of the Standard MRO Solution.

2.5.2 MRO-02 Award of Contract

Figure 4 - Award of Contract

2.5.2.1 Background
From time to time, the scope of the contract that the client agrees to is not exactly the same as the final
version sent by the planning department. Sales will describe all last-minute changes to the Planning
department before the workscope is loaded into the production environment for execution. Furthermore,
there may be additional changes to the workscope that are covered under amendments to the contract
Additional Work Requests, or AWRs. This additional work will be bundled into the same work package for
execution, but will be tracked separately from a contract point of view.

2.5.2.2 Background: Alternate Flow FMA


This step is performed once for the beginning of the contract as such, it can largely be skipped.

Page 8
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.2.3 Background: Alternate Flow Ad Hoc


An Ad Hoc MRO likely has a higher degree of change with each contract additional effort will be
required to identify and incorporate changes.

2.5.2.4 Background: Integrated Airlines


No changes.

2.5.2.5 Solution
The activity of awarding of the contract is done outside Maintenix. Once the client has agreed to send
their aircraft to the MRO, the sales department will contact the relevant departments via email.

2.5.2.6 Solution: Alternate Flow FMA


No changes.

2.5.2.7 Solution: Alternate Flow Ad Hoc


No changes, though the process is more frequent in an Ad Hoc airlines with many short or one-off
contracts.

2.5.2.8 Solution: Integrated Airlines


No changes

2.5.2.9 Standard Configuration


None.

2.5.2.10 Reports
None.

2.5.3 MRO-03 Workscope Loading

Figure 5 - Induct Workpackage

2.5.3.1 Background
Review and Update the Workpackage
Each Client likely has a different format for sending the list of requirements to be performed. The list will
be an extract from the Clients maintenance system, and will likely have a different breakdown of the MPD
Page 9
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

tasks. The MROs maintenance baseline is defined according to the way that the MRO executes the
work, as defined in section 2.5.19 MEMPH-02 Create Edit Maintenance Requirements.
The MRO will map the requested client requirements to the corresponding MRO requirement versions. As
part of this activity, the MRO will identify the provisioning agreements for the Parts and Tools that are not
within the MROs standard offering.
The MRO will ensure that theres a way to prove traceability from the clients list of requirements to the
MROs list of requirements.
Define and Maintain Allowable Configuration
Clients will occasionally ask that new parts (often new versons or modification of existing parts) be
installed on the aircraft. The MRO will need to update the allowable configuration of the aircraft to allow
the new parts to be inducted and installed.
Load Workpackage
The MRO will load the updated and configured workpackage into the MROs maintenance and planning
system.
Identify Additional Tasks (not in Baseline)
The MRO will identify the tasks that it is not familiar with the tasks that it doesnt have a defined list of
parts, tools and labour for.
Research Non-Baselined Tasks
The unfamiliar tasks will need to be reviewed by the MROs engineering department to determine the
labour, parts, tools and duration so that the task can be correctly planned.
Update Non-Baselined Tasks
Once the engineering department has identified the resources required to perform the work, this
information will be loaded into the maintenance and planning system for the specific visit. The
engineering department may chose to add regularly repeated tasks to the maintenance baseline.
Update Baselined Tasks
Depending on the exact nature of the workscope and the contract, the MRO may need to modify the
baselined tasks to meet the needs of the client. Examples include using specific parts, adding specific
contracting rules for individual tasks, or adding inspection requirements.
Schedule Workscope
The MRO will slot the work package into the correct work location and time.

2.5.3.2 Background: Alternate Flow FMA


MROs offering Fleet Management services do not use this workflow. As aircraft managed under an FMA
contract will remain in Maintenix and the maintenance program is maintained in Maintenix, no information
needs to be inducted.

2.5.3.3 Background: Alternate Flow Ad Hoc


No Changes.

2.5.3.4 Background: Integrated Airline


For an integrated solution where the airline and MRO service the same models, the engineering
department will generally have a greater understanding of the ADs and SBs related to the aircraft, making
the process slightly more efficient.
When the MRO services models that are not flown by the airline, the process is unchanged.

Page 10
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.3.5 Solution
Review and Update the Workpackage
This step will be done outside Maintenix. The Client work package (in an excel spreadsheet or similar
tool) will be updated to use the MROs Requirement Naming Convention, and several additional details
will be added. These details wont be known by the client, but are needed by the MRO to load the work
package correctly into Maintenix.

Work Package Name including the name of the part.


o Workpackage Name field
Contracting Rules for each task (T&M, FFP, etc.)
o Task Priority field
Contracting Rules for each part and tool that is not part of the standard offering
o Part Provider field on the Task Definition for Parts
o Outside of Maintenix for Tools
Required Parts, Tools and Labour (unless baselined)
o Standard Parts, Tools and Labour fields
Configuration Slot for Ad-Hoc tasks
o Configuration Slot field
Client Reference Number (to provide traceability between the task in Maintenix and the task
requested by the client, used)
o External Reference Number field
Work Location
o Work Location field
Account Code for Visit
o Account Code previously loaded.

The Client Data will be updated and formatted so that it can be converted into XML (Excel function), for
loading into Maintenix.
In order for Maintenix to identify cap exceedances and required signatures, some elements of the
contract (e.g. alert levels and cap levels) will need to be defined in Maintenix. For each requirement, the
contract rules will be set up (e.g. Is the task T&M, T&M with cap, or FFP).
Define and Maintain Allowable Configuration
Clients will occasionally ask that new parts (often new versions or modification of existing parts) be
installed on the aircraft. The MRO will need to update the allowable configuration of the aircraft to allow
the new parts to be inducted and installed.
Load Workscope
The XML message will be loaded into Maintenix using the External Maintenance Adapter.
Identify Additional Tasks (Not in Baseline)
Once the work package has been loaded into Maintenix, all of the tasks that dont match up with a
baselined task will be defined as ADHOC tasks. The planner will confirm that these are not mistakes in
the data load (typos in the task name or configuration slot), and will send the resulting list to the
Engineering Department for further study.
Research Non-Baselined Tasks
The Engineering Department will review the ADHOC tasks and determine the following:

Required Parts (including quantity required)


Required Tools (including duration)
Required Labour (including skills, and signoffs )
IETM Links (to work instructions)
Page 11

Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Consultation with the client is often required to confirm the work instructions.
The Engineering Department may chose to create baseline tasks for some of these tasks, if the task is
expected to be part of multiple future visits.
Update Non-Baselined Tasks
The Planning or Engineering Department will update the actual tasks with the details.
If this process is being done for a work package that will be reloaded, the customer data will be updated
with these details, so that the next time the work package is created, it will already have these details.
Update Baselined Tasks
The Planning Department may update baselined tasks, including defining IETM links on tasks and
refining the part provider for Parts.
At this point, the Planning Department may update the Work Package and Account Code to set the
contract rules for the visit.
Plan Workscope
The Planning Department will update the duration of the work package based on the feedback from the
Engineering Department. The work package will be scheduled, and the project planning activity will
begin.

2.5.3.6 Solution: Alternate Flow FMA


MROs offering Fleet Management services do not use this workflow. As aircraft managed under an FMA
contract will remain in Maintenix and the maintenance program is maintained in Maintenix, no information
needs to be inducted.

2.5.3.7 Solution: Alternate Flow Ad Hoc


No Changes

2.5.3.8 Solution: Integrated Airline


For an integrated solution where the airline and MRO service the same models, the process will generally
be simplified there will be fewer unknown tasks, and fewer tools that will not be part of the standard
offering.
When the MRO services models that are not flown by the airline, the process is unchanged.

2.5.3.9 Standard Configuration


For each visit, a separate and unique account number will be defined prior to the creation of the aircraft.
The following Configuration Parameters need to be reviewed, based on the method used to generate the
XML.
Table 1- Workscope Loading Configuration Parameters

Name

Description

PROCESS_VALIDATION

If true, the validation for reference in ref table will be


turned on.

PROCESS_VALIDATION_XML

If true, the schema validation for the XML file will be


turned on.

DEFAULT_EMA_REMOVE_REASON Default removal reason when automatically creating


rmvl_part segments.

Page 12
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

A method to convert client lists of requirements, plus parts, tools, labour, traceability to the contract, and
other supporting information to an XML message must be used .

2.5.3.10 Reports
The Engineering Department may request a report to better identify tasks that need to be reviewed. Not
all Ad-Hoc tasks need to be reviewed some may have been previously reviewed, and have had Parts,
Tools and Labour loaded via the EMA. Ad-Hoc tasks without any parts, tools or labour, on the other
hand, are likely candidates for future review.

2.5.4 MMDF-01 - Part Request Management


Area
Material
Requirement
Planning

Applicable Business Process

Description

MMDF-01 Part Request


Management

This process describes how the


material controller monitors
outstanding part requests, and lists the
various options for resolving these
requests.

2.5.4.1 Background
Based on the contract, the MRO will routinely supply a large number of parts to individual visits. The parts
(usually consumables) being discussed in this section are already accounted for in the quotation process
and the (estimated) cost of them is included in the quotation. The list of parts that are routinely supplied
by the MRO are considered to part of the Standard Offering. The Standard Offering does not change
between clients or visits.
Fulfillment of Rotable parts, specialized tools and consumables that are not normally provided by the
MRO is covered by section 2.5.5 MRO-10 Part & Tool Provisioning.
The MRO is responsible for provisioning parts that are part of the Standard Offering. When the part
requirements for an upcoming visit have been confirmed, the Materials organization will confirm that all
parts are available, and will initiate the restocking process as appropriate. Depending on the consistency
of the work, the MRO may not be able to use historical demand as the primary input into stock levels
upcoming work will provide a valuable indicator into the required stock levels.
The purchases made to restock parts in the Standard Offering are not related to the visit these
purchase orders are against a restocking charge code, rather than the visit charge code. When the parts
are issued to the visit, the charge code of the visit will be credited.
If the parts in the Standard Offering arent available when needed for routine, contracted work, the MRO
is responsible for any delays or expenses that may be incurred.
Refer to the SAS BP MMDF-01 Part Request Management for more information.

2.5.4.2 Background: Alternate Flow FMA


No changes.

2.5.4.3 Background: Alternate Flow Ad Hoc


No changes.

2.5.4.4 Background: Integrated Airlines


No changes.

Page 13
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.4.5 Solution
The MROs materials department, working with the sales department, will identify all parts that are part of
the standard offering. These parts will be marked as eligible for auto-reservation. Parts that are not part
of the standard offering will be not be marked as eligible for auto-reservation. Parts will be defined
against the Common Hardware, unless there are assembly-specific part groups.
The MRO is responsible for ensuring that there are enough of these parts on-hand to meet the demand
from the hangars and shops. Maintenance delays due to standard offering parts being out of stock will
likely result in penalties against the MRO.
When the workscope has been loaded and the scheduling has been confirmed, Maintenix autoreservation will automatically reserve all parts that are eligible. If parts eligible for auto reservation cannot
be automatically be reserved (not available or reserved for higher priority tasks), the Material Controller
will manually identify a provisioning strategy to meet the request. Possible strategies include purchasing
new parts, borrowing parts/tools, repairing parts, as well as several other fulfillment strategies.
The Material Controller can refer to the Standard Offering report to identify which parts are part of the
standard offering. For individual parts, this information is available on the Part Details page.
The Part Request Management process is very similar to the SAS Part Request Management process.

2.5.4.6 Solution: Alternate Flow FMA


No changes.

2.5.4.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.4.8 Solution: Integrated Airlines


No changes.

2.5.4.9 Standard Configuration


Part Details: Voltage Field: If true, identifies that the part or tool is normally supplied by the MRO, or if it
will be individually provisioned for each visit.

REF_ENG_UNIT.ENG_UNIT_CD = STANDARD, REF_ENG_UNIT.REF_UNIT_CD =


VOLTAGE, REF_ENG_UNIT.DESC_SDESC = Standard Offering
REF_ENG_UNIT.ENG_UNIT_CD = INDIVIDUAL, REF_ENG_UNIT.REF_UNIT_CD =
VOLTAGE, REF_ENG_UNIT.DESC_SDESC = Individually Provisioned

If the MRO is using the Voltage field for its intended purpose, a different field can be used to track this
information.

2.5.4.10 Reports
Standard Offering Report: A report that identifies if parts are within the MROs standard offering.

Page 14
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.5 MRO-10 Part & Tool Provisioning


2.5.5.1 Background

Figure 6 - MRO-10 Part and Tool Provisioning

Workscope Loading
Refer to the 2.5.3 MRO-03 Workscope Loading section for details about the loading of the workscope,
including the parts and tools required to complete the work.
Identify List of Non-MRO Supplied Tools
The Planner will identify the list of tools that are scheduled to be used in the work package that are not
part of the MROs standard offering.
Consult with Client to Identify Provisioning Arrangements for Tools
The Planner will present the list to the client and
provisioned.

determine how the non-standard tools will be

Customer Sends Tool with Aircraft


In some cases, the client may send the tools with the aircraft. ..
MRO borrows tool on behalf of Client
In other cases, the MRO will borrow the tool on behalf of the client, and pass the costs of the borrow
order on to the client.

Page 15
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Record Decision
Once the client has agreed to the provisioning agreements for all of the tools, this information will be
recorded in the planning system.
Receive Parts and Tools
Over time, the non-standard parts and tools will arrive at the MRO. A large number will likely arrive on the
aircraft. All inventory will be received into the MRO, inspected (unless otherwise specified) and inducted
into the MROs materials system.
Identify List of NON-MRO Supplied (e.g. Rotable) Parts
The Planner will identify the list of parts that are scheduled to be used in the work package that are not
part of the MROs standard offering.
Consult with Client to Identify Provisioning Arrangements for Parts
The Planner will present the list to the client and determine how the non-standard parts will be
provisioned.
Customer Sends Parts with Aircraft
In some cases, the client may send the parts (usually rotables) with the aircraft.
Customer Dropships Part from Vendor
In some cases, the client may pay for a part to be dropshiped from a third party vendor.
MRO Purchases Part on behalf of Client
In other cases, the MRO will purchase the part on behalf of the client, and pass the costs of the purchase
order on to the client.
Record Decision
If the client has agreed how the part will be provisioned for the visit, this information will be recorded in
the planning system.
Customer provides part from stores at MRO
In this case, the client will provide the part from client-owned parts stored at the MRO. If available, this is
normally the first option for provisioning non-standard parts.
Record Decision
If the client has agreed to provide the part via local stores, this information will be recorded in the planning
system.

2.5.5.2 Background: Alternate Flow FMA


An MRO providing FMA services is likely to have a wider selection of standard offerings.

2.5.5.3 Background: Alternate Flow Ad Hoc


No changes.

2.5.5.4 Background: Integrated Airlines


If the MRO and the Airline service the same aircraft models, it is unlikely that the MRO will be missing
tools on a regular basis. Normally, if the MRO is missing tools, they will have significant warning (when
the engineering department adds/updates the JIC) and will provision the tool normally either via
purchase or standing loan offer.

Page 16
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.5.5 Solution
MRO-03 Workscope Loading
Refer to the 2.5.3 MRO-03 Workscope Loading section for details about the loading of the workscope,
including the parts and tools required to complete the work.
Identify List of Non-MRO Supplied Tools
The Planner will identify the list of tools that are scheduled to be used in the work package that are not
part of the MROs standard offering. All tools are defined as being part of the Standard Offering, and the
Planner can run a report to identify the non-standard tools in the work package.
Consult with Client to Identify Provisioning Arrangements
The Planner will present the list to the client and determine how the non-standard tools will be
provisioned. This step is done outside of Maintenix.
Customer Sends Tool with Aircraft
In some cases, the client may send the tools with the aircraft. This step is the result of the previous step,
and is done outside Maintenix.
MRO Borrows Tool on Behalf of the Client
In other cases, the MRO will borrow the tool on behalf of the client, and pass the costs of the borrow
order on to the client. This step is the result of the Consult with Client step, and is done outside
Maintenix.
Record Decision
Once the client has agreed to the provisioning agreements for all of the tools, this information will be
recorded in the planning system.
The planner will create several orders to model the receipt and induction of the inventory:

A dropship borrow order for all the tools arriving on the aircraft
A borrow order for each tool being acquired from a third party

The dropship borrow order will be a zero dollar borrow order, with the client as the receiving organization.
The borrow orders will be linked to the aircraft work package via the account number.
Received Parts and Tools
Over time, the non-standard parts and tools will arrive at the MRO. A large number will likely arrive on the
aircraft. All inventory will be received into the MRO, inspected and inducted into the MROs materials
system.
As the parts being received have previously been defined on an order, the receiving clerk will locate the
associated order and receive the part in the normal SAS fashion.
Identify List of NON-MRO Supplied (e.g. Rotable) Parts
The Planner will identify the list of parts that are scheduled to be used in the work package that are not
part of the MROs standard offering. All parts are defined as part of being part of the Standard Offering,
and the Planner can run a report to identify the non-standard parts in the work package.
Consult with Client to Identify Provisioning Arrangements
The Planner will take the list to the client and work out how the non-standard parts will be provisioned.
This step is done outside of Maintenix.

Page 17
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Customer Sends Parts with Aircraft


In some cases, the client may send the parts with the aircraft. This step is the result of the previous step,
and is done outside Maintenix.
Customer Dropships Part from Vendor
In some cases, the client may dropship the part from a third party vendor. This step is the result of the
Consult with Client step, and is done outside Maintenix.
MRO Purchases Part on behalf of Client
In other cases, the MRO will borrow the part on behalf of the client, and pass the costs of the borrow
order on to the client. This step is the result of the Consult with Client step, and is done outside
Maintenix.
Record Decision
If the client has agreed how the non-standard offering parts and tools will be provisioned for the visit, this
information will be recorded in the planning system.
The planner will create several orders to model the receipt and induction of the inventory:

A pass-through purchase order for each part being purchased on behalf of the client.
A dropship purchase order for all parts arriving on the aircraft.
A dropship purchase order for each part that the client has acquired from a third party
A dropship borrow order to for all tools being provided by the client.
A dropship borrow order for all tools being provided by individual third party vendors.

Part requirements that are being fulfilled from client-owned on-hand stock dont need an associated PO
these will be linked to the work package via manually assigned part requests..
Dropship POs are zero cost purchase orders with the client as the receiving organization.
Dropship BOs are zero cost borrow orders.
Pass-Through Purchase Orders will be identified using the Bill To field.
The Part Provider field for each part requirement will be updated to reflect the method that the part
requirement will be fulfilled.
Customer provides part from stores at MRO
In this case, the client will provide the part from the client parts stored at the MRO. This step is the result
of the Consult with Client step, and is done outside Maintenix. If available, this is normally the first
option for provisioning non-standard parts.

2.5.5.6 Solution: Alternate Flow FMA


No changes.

2.5.5.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.5.8 Solution: Integrated Airlines


No changes.

2.5.5.9 Standard Configuration


The Part Provider reference term must be updated to include all Part Provisioning options. The options
include (but may these may be extended):

Shop (This part request is being fulfilled by an item being repaired in the shops)
Rob (This part request is being fulfilled by a rob)
Page 18

Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Dropship (This part request is being fulfilled by a part being dropshiped from the client)
PassThru (This part request is being fulfilled by a pass-through purchase order)
Normal (This part request is being fulfilled by MRO-owned inventory most consumable part
request are normal)
In Work (The provisioning arrangement for this part request are in discussion)

Each heavy aircraft visit will have a unique account code.


The Bill To field will be expanded to include a value PASSTHRU, which will identify pass-through
purchase orders.

2.5.5.10 Custom Report


Tool Provisioning Report: A report that identifies the provisioning status for all of the tools required on a
work package. This is similar to the Tool tab on the Work Package page in Maintenix, but includes all of
the Borrow orders that share an account code with the aircraft work package and also share tool
numbers.
Refer to Appendix A Tool Provisioning Report for details.

2.5.6 MMDF-02 - Pre-Draw and Issue Inventory


Area

Demand
Management

Applicable Business Process

Description

MMDF-02 Pre-Draw and Issue


Inventory

This process describes how supply


picks the parts off the shelf and issues
them out. It also describes how "predraw" works, in the case where you
want to pick the parts before they need
to be issued.

2.5.6.1 Background
The pre-draw and issue inventory process is the same as the SAS process for parts that are owned by
the MRO.
For parts that are not owned by the MRO, there are several potential differences:
-

The ownership of the inventory item must be confirmed. The Storeroom Clerk personnel must
ensure that the inventory being issued is the correct owner, as well as the correct part.
The window service may be asked to confirm that the part being issued is not over the contracted
cap for the task.
Clients may have inventory on consignment this inventory will generally be earmarked for that
client.

At an MRO, inventory pre-draw covers the storage of customer-owned inventory (usually rotables) that
are delivered to the MRO prior to the aircraft arriving, as well as the pre-draw of the MRO-owned
consumables.

2.5.6.2 Background: Alternate Flow FMA


No changes.

2.5.6.3 Background: Alternate Flow Ad Hoc


No changes.
Page 19
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.6.4 Background: Alternate Flow Integrated Airline Solution


No changes.

2.5.6.5 Solution
The Material Controller and Window Service roles must work together to confirm that the correct inventory
is being reserved and issued to the work.
The Maintenix out of the box Issue Ticket report may be modified to identify if the task is in risk of
exceeding the alert level.

2.5.6.6 Solution: Alternate Flow FMA


No changes.

2.5.6.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.6.8 Solution: Alternate Flow Integrated Airline Solution


No changes.
2.5.6.9 Standard Configuration
MESSAGE_INVENTORY_REQUIRES_CONTROLLED_RESERVATION: If true, all reservations will be
controlled that is, the reserved part must be issued to the request. Substitutions are not allowed. Use
of this configuration parameter needs to be reviewed based on the needs of the MRO.

2.5.6.10 Reports
The Issue Ticket report may be updated to show the remaining approved cap space against the task for
the issued item providing a highlight that approval should be received before the part is installed.
The Issue Ticket report may be updated to highlight issues where the part that is reserved does not
match the part that has been contracted for the task. For example, if the Part Provisioning field for the
part requirement has been set to Dropship, the part being issued should have the same owner as the
aircraft.

2.5.7 HMVP-02 Work Packaging


Area

Applicable Business Process

Description

Heavy
Maintenance
Visit Planning

HMVP-02 Work Packaging

This process describes how a heavy


maintenance work package is put
together.

2.5.7.1 Background
When the MRO signs a contract, all of the contracted tasks have to be identified by their contracting rules
- Firm Fixed Price, Time & Materials and Time & Materials with a Cap, or others as required.
The MRO will organize the clients workscope into a plan for execution. The plan will take into account
the tasks that need to be done, the labour available and the contracted Turn Around Time (TAT).
As the work is executed, and non-routines are identified, the plan will be updated.

2.5.7.2 Background: Alternate Flow FMA


An FMA MRO has a full understanding of the workscope required.
knowledge to refine and reproduce a standard execution plan.

The FMA MRO can use this

Page 20
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.7.3 Background: Alternate Flow Ad Hoc


No changes.

2.5.7.4 Background: Integrated Airlines


No changes.

2.5.7.5 Solution
The MRO will create each work package on an as-required basis. With the high degree of uniqueness
between work packages, using Project Plan templates is generally not productive, though it may be used
for specific long-term contracts.
The MRO solution uses the Task Priority flag to identify the contracting rules for the task. The Task
Priority field contains all contracting rules, including those that are only applicable to faults, etc. As such,
a report is used to identify the Task Priorities that should not be used Above the Commit Line. The EMA
is used to load the Task Priorities for tasks. Task Priorities are defined at the REQ or ADHOC level (
Priorities for JICs can be defined individually).

2.5.7.6 Solution: Alternate Flow FMA


An FMA MRO can use Project Plan templates to organize and maintain work packages.

2.5.7.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.7.8 Solution: Integrated Airlines


No changes.

2.5.7.9 Standard Configuration


The Task Priority reference term will be updated with all of the contracting rules used by the MRO.

2.5.7.10 Reports
None.

2.5.8 HMPPC-01 - Workpackage Printing


Area
Heavy
Maintenance
Production
Planning &
Control

Applicable Business Process

Description

HMPPC-01 Work Package


Printing

This process describes how the job


cards for a work package are printed.
This process is usually done when the
work is outsourced OR the printing
itself is outsourced.

Page 21
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.8.1 Background

Figure 7 Workpackage Printing

Job Card Printing in an MRO will take many forms. The key element is the use of third party work cards.
If the MRO is using third party work cards, they will generally return the the signed cards. If the MRO is
writing the job cards, they will generally return a signed tally sheet.
Printing and distributing the job cards will fall into one of three categories:
[1]
[2]
[3]
[4]

The client sends the physical job cards to the MRO.


The client sends the electronic job cards to the MRO.
The client allows the MRO to access the clients job card system.
The MRO writes the job cards

Each of these solutions poses different business problem to the MRO.


[1] Physical Job Cards
When the client sends the physical job cards, its the clients responsibility to ensure that all job cards are
present, and that they are in the same order as the list of requirements previously sent. The MRO will
handle the physical movement of the job cards, including distribution to the technicians, while providing
traceability back to the electronic records.
[2] Electronic Job Cards
The client sends the electronic job cards to the MRO. The clients responsibility is to provide initial
traceability between the list of requirements and the electronic job cards. The MRO will print the
electronic job cards, distribute them to the technicians and provide traceability.
[3] Access to Clients Systems
The client allows the MRO access to the original source job cards. The MRO retrieves the job cards,
associates them with the electronic records in the MROs systems, prints them and distributes them to the
techs.

Page 22
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

[4] MRO writes the job cards


The MRO writes the job cards, and handles every downstream activity. In this case, the signed job cards
may be retained by the MRO, depending on the contract and the regulations.

2.5.8.2 Background: Alternate Flow FMA


MROs offering FMA operations will likely be in [3] or [4], as is required by the comprehensive nature of an
FMA engagement.
An MRO offering FMA services may offer Electronic Signatures.

2.5.8.3 Background: Alternate Flow Ad Hoc


Ad hoc MRO will likely be in category [1] or [2], depending on the client.

2.5.8.4 Background: Integrated Airlines


No changes. If the MRO services the airlines aircraft, category [4] is applicable.

2.5.8.5 Solution
The SAS BP HMPPC-01 Workpackage Printing procedure is applicable for the Orange steps in Figure
7 Workpackage Printing. The specific changes required for an MRO to support JIC printing are as
follows:
[1] Physical Job Cards
When the MRO loads the work package into Maintenix, there must be a way to define the clients
ordering. Using the EMA, the work package can be loaded in order, which means the Task ID/Barcode
will represent the client-specified order.
A new report will be used, replacing the Print All Job Cards button, to print the task card cover pages in
the client-specified order. See Appendix E Ordered Task Card Cover Pages for details.
The MRO will collate the physical job cards with the cover pages.
[2] Electronic Job Cards
When the MRO loads the work package into Maintenix, there must be a way to define the clients
ordering. Using the EMA, the work package can be loaded in order, which means the Task ID will define
the client-specified order.
A new report will be used, replacing the Print All Job Cards button, to print the task card cover pages in
the client-specified order. The MRO will also print the electronic job cards, and collate the job cards with
the cover pages.
The MRO will collate the physical job cards with the cover pages.
[3] Access to Clients Systems
The client allows the MRO access to the original source job cards. If the MRO has a specific baseline for
the MROs maintenance program, the MRO retrieves the job cards, associates them with the task
definitions in the MROs systems, and prints them according to HMPPC-01.
Otherwise, see option [2].
[4] MRO writes the job cards
The MRO writes the job cards, and associates the JICs with the maintenance baseline.

2.5.8.6 Solution: Alternate Flow FMA


MROs offering FMA operations will likely be in [3] or [4], as is required by the comprehensive nature of an
FMA engagement. Different clients will likely have different processes
Page 23
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.8.7 Solution: Alternate Flow Ad Hoc


Ad hoc MRO will likely be in category [1] or [2], depending on the client.

2.5.8.8 Solution: Integrated Airlines


No changes. If the MRO services the airlines aircraft, category [4] is applicable.

2.5.8.9 Standard Configuration


No changes.

2.5.8.10 Reports
A new report is required a replacement for the Print All Job Cards button.
See Appendix E Ordered Task Card Cover Pages for details.

2.5.9 HME-01 Maintenance Execution


Area

Applicable Business Process

Description

Heavy Maintenance
Execution

HME-01 Heavy Maintenance


Execution

This process describes how work is


completed during heavy
maintenance.

2.5.9.1 Background
Execution of Heavy Maintenance in an MRO is done in a very similar way to an airline, with one
exception. In an MRO, tasks need to be monitored for contract compliance. If a task requires customer
approval to perform, the MRO should defer working on it until a contract agreement is reached.

2.5.9.2 Background: Alternate Flow FMA


No changes.

2.5.9.3 Background: Alternate Flow Ad Hoc


No changes.

2.5.9.4 Background: Integrated Airlines


No changes.

2.5.9.5 Solution
The details of heavy maintenance execution are covered in the HME-01 Heavy Maintenance Execution
business process.

2.5.9.6 Solution: Alternate Flow FMA


No changes.

2.5.9.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.9.8 Solution: Integrated Airlines


No changes.

2.5.9.9 Standard Configuration


All work packages will be set to Collection Required.
Page 24
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.9.10 Reports
No custom reports are required.

2.5.10 HME-03 Non-Routine Handling


Area

Applicable Business Process

Description

Heavy Maintenance
Execution

HME-01 Non-Routine Handling

This process describes how a


technician deals with non-routines
found during work execution.

2.5.10.1 Background

Figure 8 - HME-03 Non-Routine Handling


At an MRO where the contract specifies the contract caps are defined at the task level, when a fault is
raised, or additional effort is required to complete a routine task, a decision has to be made if the
additional work falls within the contract, or if the Customer needs to sign off the additional expense.
Once the customer approval has been granted, the technician can proceed with the correction of the fault.
Record Non-Routine Description
The technician will identify the discrepancy, and record as much as is known about the parts, tools and
labour required to correct the fault. As the work hasnt begun, this is an estimate, based partly on
previous similar faults.

Page 25
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Identification of Cost of Repair


The planner will identify the cost of the repair, based on the sale price for the parts, labour costs and
chargeable tools.
Identification of Contracting Rules for Task
The planner will identify the contracting rules for the task, based on when the task was raised, and what
the technician was doing when the task was raised. For example, if the non-routine was raised during the
execution of a T&M task, the non-routine will likely also be T&M.
Customer Approval Sought
The Planner or Customer Service Representative will contact the Client, and get permission to proceed
with rectification of the fault.
Reject Task
If the client doesnt approve the task, the MRO will not execute the task. The MRO may still charge the
client for the work already done, and the work required to return the aircraft to a serviceable state.
If the aircraft cannot be returned to a serviceable state, the MRO will have to enter into more serious
discussions with the client. At this point, work on the entire work package may be halted.
Record Customer Approval
If the customer approves the work, the MRO will record the customers approval, so that the technician
knows that they can proceed with the task.
Non-Routine Analysis
No changes.
Maintenance Progress Monitoring
No changes.

2.5.10.2 Background: Alternate Flow FMA


FMA contracts tend to give the MRO greater latitude to fix issues without client approval. Approval will
still be required for major issues.

2.5.10.3 Background: Alternate Flow Ad-Hoc


No changes.

2.5.10.4 Background: Integrated Airlines


No changes.

2.5.10.5 Solution
When a fault is raised, the MRO technician must confirm that approval has been granted to complete the
work.
Record Non-Routine Description
The technician will identify the discrepancy, and record as much as is known about the parts, tools and
labour required to correct the fault. As the work hasnt begun, this is an estimate, based partly on
previous similar faults.
The technician will add this information to the Fault Record in Maintenix.
Identification of Cost of Repair
The planner will identify the cost of the repair, based on the sale price for the parts, labour costs and
chargeable tools.
Page 26
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

The summary will be recorded outside of Maintenix.


Identification of Contracting Rules for Task
The planner will identify the contracting rules for the task, based on when the task was raised, and what
the technician was doing when the task was raised. For example, if the non-routine was raised during the
execution of a T&M task, the non-routine will be also be T&M.
The contracting rule for the task will be recorded using the Task Priority field.
Once the contracting rules have been identified, the planner will identify if the cost of the repair, in
conjunction with other non-routines raised against the same parent task will exceed the alert level, or if
this non-routine will affect the Turn Around Time. If the answer is yes to either question, customer
approval will be sought.
A new labour row, Customer Approval, is added to the row in Maintenix.
Customer Approval Sought
The Planner or Customer Service Representative will contact the Client, and get permission to proceed
with rectification of the fault. This activity will take place outside of Maintenix, as the client will not have
access to Maintenix.
Reject Task
If the client does not approve of the repair, and the aircraft can be returned to a serviceable state, the
MRO will either cancel or unassign the task. The task will be cancelled if no work has been done on it,
and the MRO is not expecting to get reimbursed for it. If the MRO has done work, the parts, tools and
labour, as appropriate, will be recorded against the task, and the task will be unassigned.
If the aircraft cannot be returned to a serviceable state if the repair is not done, additional negotiations
(outside of Maintenix) will occur between the MRO and the client until the problem is resolved.
Record Customer Approval
When customer approval has been granted, the approval will be recorded in Maintenix.
The MRO Customer Service Representative will sign the Customer Approval labour row.
Approval in Maintenix allows the technician to know what tasks have been approved, and to allow reports
that identify the tasks that have not received customer approval.
Non-Routine Analysis
No changes.
Maintenance Progress Monitoring
No changes.

2.5.10.6 Solution: Alternate Flow FMA


2.5.10.7 FMA contracts tend to give the MRO greater latitude to fix issues without client
approval. Approval will still be required for major issues.Solution: Alternate
Flow Ad Hoc
No change.

2.5.10.8 Solution: Integrated Airlines


No change.

2.5.10.9 Standard Configuration


This scenario requires a Customer Approval labour row be created.
Page 27
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

2.5.10.10

Mxi Technologies
Maintenix Version v6.8.13 SP2

Reports

Invoice Validation: A report id identifies tasks with a contracting flagging that is either incorrect (Error)
or unlikely (Warn). Each case will be individually and manually reviewed and corrected (if necessary).
For example, if a non-routine is raised as NOCOST, associated tasks will also be NOCOST. Any
associated task thats different will be flagged. If necessary, a special work type will be used to identify
valid exceptions.

2.5.11 SMMC-04 Component Shop Work Management


Area

Applicable Business Process


SMMC-04 Component Shop
Work Management

Shop Maintenance
Control

SMMC-06 Component Shop


Induction
SME-01 Component Shop
Maintenance Execution

Description
This process describes how to
manage and control component
shop maintenance work in the
shops.
This process describes what
happens when a component arrives
at a shop to be repaired.
This process describes how work is
completed in the shops.

2.5.11.1 Background
The Component Shop Work Management area covers the scenario where components are removed from
an aircraft, repaired in an internal shop, and reinstalled on the aircraft.
As the component that was identified as broken during the visit goes through the workflow, customer
approval may be needed at several points:
-

Approval to repair the part (send the part to shops)


Approval of initial estimate (based on external inspection)
Approval of additional work, based on findings.

Items that were contracted to be fixed in the original contract require only the third round of approval.
Other than these issues, the Shop processes outlined in the SAS shop module are effective.

2.5.11.2 Background: Alternate Flow FMA


No changes.

2.5.11.3 Background: Alternate Flow Ad Hoc


No changes.

2.5.11.4 Background: Integrated Airlines


No changes.

2.5.11.5 Solution
The Component Work Shop Management activity includes the following SAS Business Processes. For
each BP, the MRO modifications are identified:
-

SMMC-04 Component Shop Work Management

Include a step to identify all outstanding required customer approvals, and to record said approvals.
Include a flow to handle when the repair is not approved.

Page 28
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

SMMC-06 Component Shop Induction

Include an initial estimate phase, where the shop will perform an inspection and provide an estimate.
Client approval is needed before the shop work can begin.
A labor row called Initial Shop Inspection will be used to record client approval.
-

SME-01 Component Shop Maintenance Execution

If there are any shop findings (SME-01-04), the Shop Controller will assess if client approval is required to
proceed. If client approval is not granted, the shop will cease working on the component.
A labor row called Initial Shop Inspection will be used to record client approval.

2.5.11.6 Solution: Alternate Flow FMA


No changes.

2.5.11.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.11.8 Solution: Integrated Airlines


No changes.

2.5.11.9 Configuration
Creation of a new labor rows:
-

Initial Shop Inspection

Additional Work Types will be added:


-

Expedited: Used when the shop work needs to be expedited


Certificates: Used when the contract calls for additional certificates to be produced.

2.5.11.10

Reports

Refer to Appendix D: Shop Controllers Report for details.

2.5.12 MRO-12 Engine Shop Management


Refer to the Design Modeling Standard Engine Shop document for details about this area of the
MRO workflow.

Page 29
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.13 MRO-05 Aircraft Release / Customer Signoff


2.5.13.1 Background

Figure 9 - MRO-05 Aircraft Release / Customer Signoff


When the work is complete, the MRO will seek customer agreement that they will accept aircraft. Once
customer approval has been granted, the aircraft can be released.
Approval Requested
Once all the work in the work package is complete, the Client Support Representative will contact the
client and request signoff of the work package. Based on the contract, the client may need summaries of
the completed work and the signed job cards.
Complete Work Package
Once approval has been granted, the work package will be completed.
Reconciliation
If approval is not granted, the MRO will need to fix the problem and request approval again.

2.5.13.2 Background: Alternate Flow FMA


Based on the contract, an FMA MRO may not require customer signoff for all maintenance releases.

2.5.13.3 Background: Alternate Flow Ad Hoc


No changes.

2.5.13.4 Background: Integrated Airlines


No changes.

2.5.13.5 Solution
Approval Requested
The Planner will export all required information from Maintenix (based on the terms of the contract), and
will confirm that all job cards have been collected. When the planner is satisfied that all work has been
completed, the client will be contacted to approve release of the aircraft.

Page 30
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Complete Work Package


The planner and Customer Service Representative (an MRO employee, not a client employee) will sign
the work package.
Reconciliation
The MRO will resolve the issues and work towards the release of the aircraft. The exact steps will vary
according to the issue at hand.

2.5.13.6 Solution: Alternate Flow FMA


No changes.

2.5.13.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.13.8 Solution: Integrated Airlines


No changes.

2.5.13.9 Configuration
The labour skill of Customer Service Representative will need to be added. This labour skill will be
defined as the default signoff requirement for aircraft work packages.

2.5.13.10

Reports

Depending on client requirements, one or more custom reports may be required to retrieve and format
specific information from Maintenix to support the client signoff process.

2.5.14 MRO-06 Invoice Generation


2.5.14.1 Background
The process of generating the invoice is done outside Maintenix. Maintenix will provide a wealth of
information to generate the report, via the invoicing reports.
Many of the invoicing reports are the same reports that are used in the Contract Compliance Monitoring.
Invoicing support information to be exported/reported from Maintenix will be determined by the
requirements of the clients AP system. It may require complementary information from other sources as
well. Details would still be project-specific and cannot easily be standardized. Client invoice may include:
-

Labour used in the aircraft work package, by task, duration, skill type and cost per hour that is
over the cap
Chargeable parts used in the aircraft work package, by task, part number, quantity and cost that
are over the cap
Chargeable tools used in the aircraft work package that are over the cap
All related pass-through purchase orders
All related borrow orders
All related exchange orders
All related shop work. Each shop package is an independent package that contains the same
information as the aircraft work package, plus fees for additional serviceability certificates or for
expedited repairs.
All related external repair orders
Additional costs (storage costs, hotel fees for Client representatives, etc.)
Penalties, Discounts and other adjustments.

The Billing Department will validate that the data in Maintenix is correct, including:
-

Hours recorded on tasks, including labour skill


Page 31

Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Parts and Tools, including quantity and tool duration


Costs of Orders
All elements of shop work

The Billing Department will identify additional factors:


-

Penalties and discounts.


Hourly labour costs
Other costs, including hosting of client reps.

When all information has been confirmed, the invoice will be generated and sent to the client.

2.5.14.2 Background: Alternate Flow FMA


Most FMA contracts have a simplified invoicing system dealing mainly with pass-through purchase
orders.

2.5.14.3 Background: Alternate Flow Ad Hoc


No changes.

2.5.14.4 Background: Integrated Airlines


No changes.

2.5.14.5 Solution
The Billing Department will run several reports to identify and summarize the information needed to
provide invoice data for the Billing Department, so they can generate the invoice.
As the method used to generate the invoice is different for every MRO, this solution does not propose a
process to produce a single number for the invoice this billing department will be able to build the
invoice based on the full scope of data, summarized as needed.
For example, the billing department will have all of the labour used, by skill time, task and duration. The
base cost of the labour rate, discounts, apprentice labour and expedited work will be calculated manually
based on the contract and situation at the time.
Similarly, the billing department will be able to identify how to break down complex situations such as
tool borrows that were used for multiple clients and incurred late penalties.

2.5.14.6 Solution: Alternate Flow FMA


MROs that offer FMA services are unlikely to bill on a visit-by-visit basis, though there may be some
additional costs (provisioning of rotables) that are individually incurred. The invoicing solution for FMA
MRO solutions will likely be substantively different than the solution outlined above, and will not be
covered in this document.

2.5.14.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.14.8 Solution: Integrated Airlines


No changes.

2.5.14.9 Standard Configuration


Each piece of information in the invoice solution will be defined as followed:
-

Labour used in the aircraft work package, by task, duration, skill type and cost per hour that is
over the cap
o Standard Method to Record Labour
Chargeable parts used in the aircraft work package, by task, part number, quantity and cost that
are over the cap
Page 32

Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Standard Method to Record Parts


Part Provisioning Flag to identify the provisioning strategy
MSRP cost (or AUP+) value used to identify the cost of the part. See Appendix
CIdentification of MRSP and Vendor Prices for details.
o Customer Approval recorded via Customer Rep labour row
o Account Code used to record cap
Chargeable tools used in the aircraft work package that are over the cap
o Standard Method to Record Tools
o Rental fees recorded on Tools Technical Characteristics (Power)
All related pass-through purchase orders
o Normal Purchase Order
o Associated to Aircraft Work Order by part requests
o Inventory ownership changed on issue
All related borrow orders
o Normal Borrow Orders for true borrow orders
o Normal Borrow Orders associated with Aircraft Work Order via account code
o Dropship Borrow Orders (to model tools loaned from client to MRO) will have zero cost,
and will be associated with the clients organization
All related exchange orders
o Normal Exchange Orders
All related shop work. Each shop package is an independent package that contains the same
information as the aircraft work package, plus fees for additional serviceability certificates or for
expedited repairs.
o Parts, Labour and Tools defined in the normal manner
o Customer Approval recorded via Customer Rep labour row
o Manually created return shipment will be set as the return date
o Shop work linked to Aircraft Work Package via Account Code
All related external repair orders
o Standard method for Repair Orders
Additional costs (storage costs, hotel fees for Client representatives, etc.)
o Tracked outside Maintenix
Penalties, Discounts and other adjustments.
o Tracked outside Maintenix
Expedited Shop Work
o An additional Work Type will be added to identify expedited work.
o Cost of expedition will be tracked outside Maintenix
Shared Tool Borrow Orders
o The primary work order that the tool was borrowed for will lend its account code to the
borrow order.
o When tools are used on tasks, the techs will identify the tool used to ensure that the client
is correctly charged.
o A summary report will identify all tasks that were used on a work package with an
account code other than the one associated with the work order.
o
o
o

2.5.14.10

Reports

Multiple reports will be developed to present and summarize the invoicing data. The exact reports will be
based on the information that the MRO uses to validate and generate the invoice.
In addition to summarizing the data from the visit, these reports will identify contract issues, such as
identifying tasks that have exceeded the cap and dont have client approval.
The Invoicing Reports are very similar to the reports used in 2.5.16 MRO-11 Contract Compliance
Monitoring.

Page 33
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.15 MRO-07 Part and Tool Dispersal

Figure 10 - MRO-07 Part and Tool Dispersal

2.5.15.1 Background
Identification of Parts and Tools to be Returned
When the work package is complete, the parts and tools associated with the work package have to be
dispersed. The Material Controller will identify the following:
-

Tools borrowed from a third party for the visit.


Tools borrowed from the client.
Parts delivered by the client but not used.
Parts purchased in a pass-through purchase order but were not used
Parts (usually only repairable parts) that have been removed from the aircraft.

Return to Vendor
The Material Controller will confirm that all borrowed items are returned to the vendor in a timely manner.
Package and Place in Aircraft
The Material Controller will ensure that all available client owned items are packaged and loaded onto the
client aircraft. This includes unserviceable repairable components removed from the aircraft, as well as
unused serviceable components, plus any tools.
Alert Client
If a client-owned inventory item is not available to be returned on the aircraft (it may be being repaired in
the shop, for example), the Client Representative will alert the client.
Package and Ship to Client
When the parts that werent available when the aircraft left become available to be returned to the client,
the Material Controller will ensure that they are sent in a timely manner.

2.5.15.2 Background: Alternate Flow FMA


An FMA vendor would likely have less parts and tools to disperse, due mainly to the much higher degree
of maintenance predictability and recurrence.
Page 34
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.15.3 Background: Alternate Flow Ad Hoc


No changes.

2.5.15.4 Background: Integrated Airlines


No changes.

2.5.15.5 Solution
Identification of Parts and Tools to be Returned
During the 2.5.5 MRO-10 Part & Tool Provisioning process, the following was done:
-

Borrow Orders from vendors were set up as standard borrow orders


Borrow Orders from the client were set up as dropship borrow orders
Items received from clients were set up as dropship purchase orders

The Material Controller will run the custom Part and Tool Dispersal report that identifies the parts and
tools to be returned. If the task associated with the part was cancelled, the Material Controller will confirm
if the parts are to be returned to the client, or if they should be earmarked or a later maintenance visit.
Return to Vendor
Returning borrowed items to vendors will be done according to the standard SAS procedures.
Package and Place in Aircraft
Returning borrowed and removed repairable items will be done as follows:
-

Packaging done outside of Maintenix


Borrow Orders and Outbound Shipments are completed

Alert Client
If a client-owned part is not available to be returned on the aircraft it may be being repaired in the shop
the Customer Service Representative will contact the client and identify the return date.
The Material Controller will update the scheduled date of the return shipment to the client on the borrow
orders, or the manually created shipment for other items.
Package and Ship to Client
Returning borrowed items to clients will be done according to the standard SAS outbound shipment
procedures.

2.5.15.6 Solution: Alternate Flow FMA


It is unlikely that there will be many parts and tools to be dispersed for an MRO that provides FMA
services, but the basic process is still followed.

2.5.15.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.15.8 Solution: Integrated Airlines


No changes.

2.5.15.9 Standard Configuration


This activity builds upon the standard configuration outlined in the 2.5.5 MRO-10 Part & Tool
Provisioning process.

2.5.15.10

Reports

The Part and Tool Dispersal report is required. This report identifies:
Page 35
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

All tools borrowed for the visit, including the status of the return shipment
All parts delivered for the visit (via PO) that were not used in the visit
All repairable components that were removed from the aircraft

Borrow orders are associated with the work package via the Account Code.
Parts delivered for the visit will be associated with the work package via part requests. The dropship POs
will be built exclusively for a single work package.
Repairable Components removed from the aircraft will be shown by aircraft.
This report will be exportable to Excel, where the Material Controller can filter for open shipments and
parts owned by the client.

2.5.16 MRO-11 Contract Compliance Monitoring


2.5.16.1 Background
From the time the work package is loaded into Maintenix to the time the invoice is finalized, the MRO will
validate that the maintenance and actions taken are in line with the contracted scope of the visit. This
validation has three phases:
Recording Scope and Terms & Conditions
When the Workpackage is originally loaded in section 2.5.3 MRO-03 Workscope Loading, the
contracting rules for each part and task is defined.
When new tasks are added, or non-routine tasks are raised, they will be tagged with the appropriate
contracting rule.
The account code related to the visit will be defined with the Alert Level and the Cap Level for the visit.
Validating Compliance
On a daily basis, the Billing Department, plus other interested individuals, need to identify a significant
amount of information, potentially including:
-

Identification of all tasks with incorrect contract flagging


Identification of tasks that are over the alert level without client approval
Identification of tasks with significant discrepancies from the baselined tasks
Identification of tasks that exceed hard limits (10 hours, $10,000 in parts, etc.)
Identification of tasks that have been rejected or removed by the client.
Identification of parts that are installed that are owned by an incorrect owner
Identification of overdue return shipments
Identification of shop work that is awaiting customer approval

The goal of validating compliance is to identify issues before the aircraft leaves, so that:
-

Customer Approval can be sought and granted before the aircraft leaves
Generation of the Invoice is fast and accurate

Correcting Errors and Approving Exceptions


When the Billing Department identifies issues, they will contact the appropriate people (Crew Leads,
Finance, Material Controllers, etc.) to resolve the issues.

2.5.16.2 Background: Alternate Flow FMA


No changes.

2.5.16.3 Background: Alternate Flow Ad Hoc


No changes.
Page 36
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.16.4 Background: Integrated Airlines


No changes.

2.5.16.5 Solution
From the time the work package is loaded into Maintenix to the time the invoice is finalized, the MRO will
validate that the maintenance and actions taken are in line with the contracted scope of the visit. This
validation has three phases:
Recording Scope and Terms & Conditions
When the Workpackage is originally loaded in section 2.5.3 MRO-03 Workscope Loading, the
contracting rules for each part and task is defined.
When new tasks are added, or non-routine tasks are raised, they will be tagged with the appropriate
contracting rule.
The account code related to the visit will be defined with the Alert Level and the Cap Level for the visit.
Validating Compliance
On a daily basis, the Billing Department, plus other interested individuals, will run various contract
compliance reports. These reports may include:
-

Identification of all tasks with incorrect contract flagging


Identification of tasks that are over the alert level without client approval
Identification of tasks with significant discrepancies from the baselined tasks
Identification of tasks that exceed hard limits (10 hours, $10,000 in parts, etc.)
Identification of tasks that have been rejected or removed by the client.
Identification of parts that are installed that are owned by an incorrect owner
Identification of overdue return shipments
Identification of shop work that is awaiting customer approval

These reports are going to be very similar, if not identical, to the reports that Billings will run when they
prepare the final invoice.
The goal of validating compliance is to identify issues before the aircraft leaves, so that:
-

Customer Approval can be sought and granted before the aircraft leaves
Generation of the Invoice is fast and accurate

This change usually means that the Billings department spends more time validating contract compliance
than generating the invoice.
Correcting Errors and Approving Exceptions
When the Billing Department identifies issues, they will contact the appropriate people (Crew Leads,
Finance, Material Controllers, etc.) to resolve the issues.
Typical issues include: incorrect labour or tool hours, incorrect part quantities, incorrect inventory item
installed, missing customer approval / unauthorized work performed, or missing signed job cards or tally
sheets.
These issues will be resolved in Maintenix when possible. As the data is cleaned up in Maintenix, the
invoicing reports will report correct information with a minimum of data cleanup after extraction.
Correction of errors also sets up the MRO to review and update the Maintenance Baseline when the
average actuals identify that the baseline is incorrect. That is, if a task, on average, is taking 2 hours
longer than the baseline, the engineering department should update the baseline, to allow more accurate
quotations and planning. This can be done in Maintenix on an individual task basis, or via a report for
summaries.

Page 37
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.16.6 Solution: Alternate Flow FMA


No changes

2.5.16.7 Solution: Alternate Flow Ad Hoc


No changes

2.5.16.8 Solution: Integrated Airlines


No changes

2.5.16.9 Standard Configuration


No specific Standard Configuration is required to support this business process. The setup of tasks,
parts, tools and labour skills is defined elsewhere in this document.

2.5.16.10

Reports

Numerous reports will be required to support the Contract Validation process. These reports will be
defined based on the needs of the MRO, based on the terms of the contracts.

2.5.17 MRO-08 Review of Performance

Figure 11 - Review of Performance

2.5.17.1 Background
When a visit has been completed, the Management and QA Department of the MRO may choose to
review the performance of the visit using a number of metrics (KPIs), including:
-

Part / Tool / Labour expenditure actual vs. planned


Scheduled Duration, actual vs. planned
Number of AOG-priority part requests (part requests that, if not filled, will affect Turn Around
Time)
Number of delays due to part and tool availability
Speed of Invoice Generation
Accuracy of Invoice (based on number of successful customer appeals)
Number of Engineering Requests

2.5.17.2 Background: Alternate Flow FMA


No Changes.

2.5.17.3 Background: Alternate Flow Ad Hoc


No Changes

2.5.17.4 Background: Integrated Airlines


No changes.
Page 38
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.17.5 Solution
The MRO will retrieve information from Maintenix via the GUI or custom reports. The details are defined
by the specific needs of the MRO. Many of the KPIs will be validated using a combination of information
from Maintenix and information from other sources. For example, the speed of the invoice generation can
only be done outside of Maintenix, but speed at which the validation reports were last run and identified to
show no errors is a key component to the speed at which the invoice can be released.

2.5.17.6 Solution: Alternate Flow FMA


No Changes

2.5.17.7 Solution: Alternate Flow Ad Hoc


No Changes

2.5.17.8 Solution: Integrated Airlines


No Changes

2.5.17.9 Standard Configuration


There is no specific standard configuration to support this process.

2.5.17.10

Reports

Custom Reports may be developed to retrieve specific information from Maintenix, and to have it
formatted in a specific way.

2.5.18 FRMRP-01 Define Stock Levels


2.5.18.1 Background
Updates to the Stocking Levels (The pre-defined quantity of parts stored at a materials location) at an
MRO will be driven by three business considerations:
-

Historical Patterns: Based on historical usage, some parts have been over provisioned or under
provisioned in the past. It is assumed that historical usage is a valid predictor of future usage
which is reasonable in cases where the MRO has long term contracts.

Predicted Usage: In cases where the MRO has confirmed sales that are not within the normal
range, the Materials department may increase stocks in select items to predict these demands.
This is a valid case when the MRO does not have long term contracts, or, for example, has an
abnormally high number of specific maintenance activities in the sales pipeline.

Changes to the MROs Offerings: When the MRO changes the services that they are offering, the
Materials department will need to review the current materials holdings. If a new aircraft is being
supported, the part and tool requirements will be reviewed, along with the anticipated demand,
and new stock levels will be defined. If maintenance for an existing aircraft is being reduced or
dropped, stock levels will need to be reduced or removed.

The decision making process for updating stock levels is performed by the Materials management, based
on information from Maintenix and from the business.

2.5.18.2 Background: Alternate Flow FMA


No changes

2.5.18.3 Background: Alternate Flow Ad Hoc


No changes
Page 39
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.18.4 Background: Integrated Airlines


No changes

2.5.18.5 Solution
The process in the SAS BP FRMRP-01 Define Stock Levels do not need to be updated.

2.5.18.6 Solution: Alternate Flow FMA


No changes

2.5.18.7 Solution: Alternate Flow Ad Hoc


No changes

2.5.18.8 Solution: Alternate Flow Integrated Airlines


No changes

2.5.18.9 Standard Configuration


No standard configuration settings are required.

2.5.18.10

Reports

No custom reports are required.

2.5.19 MEMPH-02 Create Edit Maintenance Requirements


2.5.19.1 Background
MROs are always looking for efficiencies in the work definition, planning and estimation process. For
many MROs, one aspect of this is to use a Maintenance Baseline.

Reference Documents (REF): Not needed by MROs with long-term contracts


Blocks: Not needed by MROs with long-term contracts
Master Panel Cards (MPC): Used by MROs
Requirements (REQ): Used by all MROs, based on the original REQs
Job Instructions Cards (JIC): Used by MROs, defined using the resources that the MRO uses to
execute the work

MROs have two choices when defining a Maintenance Baseline:


-

Create a general baseline that reflects how the MRO actually executes the work.
Create one or more client-specific maintenance baselines to reflect how the client organizes the
work.

The most efficient way to operate is usually to follow the first option.

2.5.19.2 Background: Alternate Flow (FMA)


An MRO offering Fleet Management services will use a comprehensive maintenance baseline, containing
all MPD tasks, plus all ADs/SBs/SLs, plus all engineering orders. This solution is fully in-line with the SAS
solution.

2.5.19.3 Background: Alternate Flow (Ad-Hoc)


No changes.

Page 40
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.19.4 Background: Integrated to Airline Solution


The hybrid organization will have two maintenance baselines for each model a comprehensive baseline
for their own aircraft, and the simplified baseline (as described above) for the client aircraft.

2.5.19.5 Solution
The MRO creates the general maintenance package, and adjusts the client work package organization to
reflect the MROs practices, while maintaining traceability.
The MRO will baseline the entire MPD of the aircraft, and may baseline some ADs/SBs/SLs, depending
on the frequency they will be contracted to the MRO.
The MRO will put the IETM links on the baseline for the tasks for which the MRO has work instruction
cards. For all other tasks, IETM links will be added to the actual tasks if available.
The MRO will modify the clients tasks to be in-line with the task created from the baselined tasks prior to
loading the tasks into Maintenix. See the section 2.5.3 - MRO-03 Workscope Loading for details.

2.5.19.6 Solution: Alternate Flow FMA


MROs offering FMA solutions will use a full and comprehensive maintenance baseline, including
scheduling, compliance and IETM links.

2.5.19.7 Solution: Alternate Flow Ad Hoc


No changes

2.5.19.8 Solution: Alternate Flow Integrated Airlines


No changes

2.5.19.9 Standard Configuration


No standard configuration changes are required to support this solution element.

2.5.19.10

Reports

No custom reports are required to support this solution element.

2.5.20 MRO-09 Marketing / Sales Planning

Figure 12 - MRO-09 Marketing & Sales Planning

2.5.20.1 Background
On an ongoing basis, the Marketing department will identify trends in the industry what aircraft are
being purchased by prospective clients and what aircraft are being retired. The Marketing department
should be able to provide guidance to when the MRO should modify their standard offering to include new
models and checks, in anticipation of changes in market demand. Modification in the standard offering
Page 41
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

may also include parts pooling arrangements and updates to the capacity and capabilities of the shops.
Modifications to the MROs repair offering will require regulatory approval.
The Sales department will identify and close specific deals for visits. The Sales department will work with
the Planning department to ensure that the MRO has the capacity (hangar space and labour are the main
restrictions) to perform the visits. Upon confirmation of sales, the Materials department will be notified to
ensure that material stocks are sufficient, and so that special tools and parts can be provisioned as
defined by the contract.

2.5.20.2 Background: Alternate Flow FMA


No changes.

2.5.20.3 Background: Alternate Flow Ad Hoc


Ad-Hoc MROs require a greater coordination between the sales department and the materials
department, as the type of aircraft and the type of maintenance may change significantly month to month.

2.5.20.4 Background: Integrated Airlines


No changes.

2.5.20.5 Solution
This step is performed outside of Maintenix.

2.5.20.6 Solution: Alternate Flow FMA


No changes.

2.5.20.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.20.8 Solution: Integrated Airlines


No changes.

2.5.20.9 Configuration
No standard configuration settings are required to support this process.

2.5.20.10

Reports

No custom reports are required to support this process.

2.5.21 MECRM-02 Define and Maintain Allowable Configuration


2.5.21.1 Background
The MRO is not responsible for maintaining the as-maintained configuration of the aircraft they are
working on. The MRO needs to identify the configuration changes performed in the work package, and to
ensure the applicability of installed components and airworthiness of the aircraft, but theres no need for
the MRO to have the full configuration in Maintenix.

2.5.21.2 Background: Alternate Flow - FMA


MROs that provide Fleet Management services need to have a full, comprehensive as-maintained aircraft
configuration, as defined in SAS.

2.5.21.3 Background: Alternate Flow - Ad-Hoc


No change.

Page 42
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

2.5.21.4 Background: Integrated to Airline Solution


In combined operations, the MRO side of the organization does not need to know the configuration details
of the client aircraft to the same level as the Airline side of the organization needs to know the asmaintained configuration of their aircraft. Furthermore, its quite likely that the MRO wont actually know
what components are installed on the aircraft before it arrives which means that theres no ability to
have the same level of detail in the maintenance system.

2.5.21.5 Solution
The aircraft configuration for the MRO will identify the ATA Chapter and Section, and will not contain any
tracked configuration slots. For non-commercial aircraft, the aircraft configuration will only be high level,
broken down by physical zone of the aircraft and, if necessary, specific systems. The MRO does not track
usage on the aircraft.
By breaking up the aircraft into ATA chapters and sections, the JICs will be defined against a meaningful
section of the aircraft, facilitating work assignment.

2.5.21.6 Solution: Alternate Flow FMA


As defined in the SAS, MROs that provide Fleet Management services need to have a comprehensive
aircraft configuration.

2.5.21.7 Solution: Alternate Flow - Ad-Hoc


No change.

2.5.21.8 Solution: Integrated to Airline Solution


In an integrated solution where both sides maintain the same models, the aircraft maintained in the MRO
division will use a different baseline than the airline. The Airlines aircraft will have a full, comprehensive
aircraft configuration, as defined in SAS. The MROs aircraft will have a configuration that identifies the
ATA Chapter and Section (or physical zones for non-commercial aircraft).

2.5.21.9 Standard Configuration


No standard configuration settings are required to support this scenario.

2.5.21.10

Reports

No custom reports are required for to support this scenario.

2.5.22 MRO-12 3rd Party Component Maintenance


2.5.22.1 Background
This solution is for an organization that is not primarily a component maintenance organization, but rather
rd
one where shops primarily support the aircraft maintenance, with extra capacity being devoted to 3 Party
work.
Each component being repaired will have a separate workflow, starting with the induction of the inventory
component and completing with the return of the component and the generation of invoicing.

Page 43
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Figure 13 - 3rd Party Component Repair


Orange steps are optional.

2.5.22.2 Background: Alternate Flow FMA


No changes.

2.5.22.3 Background: Alternate Flow Ad Hoc


No changes.

2.5.22.4 Background: Integrated to Airline Solution


No changes.

2.5.22.5 Solution
The Shop Controller will create a Consignment order. This solution allows the component to be
received, and the work package created. Contracted work and scheduling will be added to the work
package, and the return shipment will be created.
The part will be transferred to the shop, where it will undergo initial inspection. The shop will generate a
quote to repair the component, and the customer will approve the work. The shop work will be executed,
with customer approval sought when appropriate.

Page 44
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

When the component has been repaired, the tech will complete the required certificates, and the item will
be packaged and shipped back to the client. If there are several components going to the same client,
they may be shipped at the same time.
The Shop Controller will monitor the process, and identify and resolve bottlenecks, including getting
customer approval, required parts and tools and labour priority.
rd

Refer to the MRO-12 SC1 3 Party Component Shop use case for details.

2.5.22.6 Solution: Alternate Flow FMA


No changes.

2.5.22.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.22.8 Solution: Alternate Flow Integrated Airlines


No changes

2.5.22.9 Standard Configuration

The clients will be set up as vendors and linked organizations.


The Shop Controller will have permission to create Consignment Orders, and to approve zero
dollar consignment orders.
An account will be set up for each component repair contract (not for each individual repair).

2.5.22.10

Reports

Shop Controllers Report


rd

rd

Most of the activities in the 3 Party Component Repair workflow should be summarized in the 3 Party
Component Repair Report. Refer t o Appendix D Shop Controllers Report for details about this report.

2.5.23 Materials Management


2.5.23.1 Background
In most material management functions, the MRO operates in the same manner as defined in the SAS
solution. The key difference is based on the ownership of inventory as defined by the contract, all of the
non-standard tools will be provisioned in a specific way, and the Materials Management group will ensure
that the correct part is provisioned.
The provisioning, management and issuing of MRO-owned inventory is detailed in the associated SAS
BPs.

2.5.23.2 Background: Alternate Flow FMA


No changes.

2.5.23.3 Background: Alternate Flow Ad Hoc


No changes.

2.5.23.4 Background: Integrated Airlines


No changes.

2.5.23.5 Solution
Materials Management
Page 45
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

The Maintenix materials module allows users to control the materials & tools in support of the execution
of aircraft maintenance. In Maintenix this module is tightly integrated to the maintenance module. The
sections below list the SAS Materials Management Business Processes that are provided with this
concept. These business processes illustrate the airline materials processes in which the Maintenix
solution will be involved.
Demand Management
Area

Applicable Business
Process

Description

MMDF-01 Part Request


Management

This process describes how the material


controller monitors outstanding part requests,
and lists the various options for resolving these
requests.

MMDF-02 Pre-Draw and


Issue Inventory

This process describes how supply picks parts off


the shelf and issues them out. It also describes
how "pre-draw" works, where you want to pick
parts before they need to be issued.

Demand
Management

(1)

MMDF-01 PART REQUEST MANAGEMENT

Auto-reservation
When a Work Package containing Tasks with Part Requirements is scheduled at a specific location,
Maintenix auto-reservation will reserve all available parts for maintenance tasks if the inventory is
available locally in the warehouse. If necessary, users can override the automatic reservation.
Open Part Requests
Material Controllers will monitor open Part Requests for upcoming maintenance and deferred faults using
the Open Part Requests page. This page displays part requests that were not fulfilled by auto-reservation
or have been defined as always requiring manual reservation by a Material Planner.
The Material Controller can choose the method of fulfillment for each open Part Request including
reserve local inventory, reserve remote inventory, reserve on order inventory, purchase inventory or
borrow inventory.

(2)

MMDF-02 PRE-DRAW AND ISSUE INVENTORY

Picking Slips/Issue Tickets


Issue Lists (for Work Packages) or Issue tickets (for new part requirements added to an existing Work
Package) display the current location of the inventory and the work location where the inventory is
needed. These can be printed in advance automatically and the timeframe of when to print is
configurable. The Issue List or Issue Tickets can be used by the Warehouse to pick the parts from their
storage location before the mechanic arrives. Once the inventory is picked, it is held at the issue desk,
and then later issued to the mechanic.
The Warehouse issues parts to maintenance when the mechanic arrives to get the part. The SAS
recommends that the mechanic brings the printed Task Card which contains a list of parts to the
warehouse when picking up parts. The Task Card can then be used by the Warehouse users to identify
the parts needed. Alternately, a custom report could be printed for the Task that lists the part
requirements and part request IDs to identify the inventory needed.
Page 46
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Area

Material
Receipt
QA and
Engineering
Support

(3)

Mxi Technologies
Maintenix Version v6.8.13 SP2

Applicable Business
Process

Description

MMMR-01 Receive
Inventory

This process describes how inventory is received


by the supply department.

MMMR-03 Inventory Put


Away

This process describes how inventory is put away


in the warehouse after it has been received.

MEQAES-03 Inspect As
Serviceable

The process describes how inventory is


inspected and made serviceable before it can be
issued to maintenance.

MMMR-01 RECEIVE INVENTORY

The Receiving group receives parts from a vendor that were purchased repaired, exchanged or are on
consignment, as well as receiving parts that were shipped from another airport.
Waybill/Order Numbers
Physical shipments can be matched with shipments in Maintenix using the Order Number or the Waybill
Number.
Update Inventory Records
As part of the receiving process, the supply clerk will update all applicable inventory information including
quantity, serial number and Shelf Life. For tools that have scheduled maintenance tasks, the supply clerk
will initialize the appropriate tasks with the correct deadlines and complete any previously created work
packages for tools that were sent out for repair.
MRO Serial Number
The MRO owned inventory may have a unique MRO serial number associated to it when an aircraft is
initialized or when a component is received. This is used for batch items as well as rotables. The ICN
(Inventory Control Number) can be used to store this value as a reference for parts that are currently in
inventory. For new parts entering the system, the Maintenix Barcode should be used as it is a unique
identifier for inventory.
Inspection
Unless otherwise specified, all parts received by the MRO from a vendor or client must go through Quality
Control inspection. In Maintenix, all part numbers will be setup to be routed to inspection, except
consigned parts for customers.

(4)

MMMR-03 INVENTORY PUT AWAY

Once items have been received and made serviceable, Maintenix will either create a Put Away
transaction which will indicate what parts need to be moved and to which bin they must be moved to, or
automatic put-aways will be enabled. Once put away, the Warehouse group will record that inventory has
been transferred to its appropriate bin location in the warehouse.
Part Number to Bin mapping
Part Numbers can be mapped to bin locations in Maintenix. If a part number does not have a bin
location mapped, one can be identified and mapped as the standard storage location as needed.

Page 47
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

(5)

Mxi Technologies
Maintenix Version v6.8.13 SP2

MEQAES-03 INSPECT AS SERVICEABLE

At the MRO, all parts received from a vendor must go through a Quality Control inspection. In Maintenix,
all aviation part will be setup to be routed to inspection once received. Received items appear on the To
Be Inspection required tab.
Quarantine
The QA Inspector reviews physical part and paperwork. If an Item does not pass inspection, then the QA
inspector notifies the receiving personnel to put the part into quarantine. In Maintenix, the QA Inspector or
the Receiving group can mark the inventory as Quarantined and identify the reasons. Note that photos
and other documents may be attached to the inventory item to help document the problem. The
Purchasing group will review the Quarantine page to identify and work with the vendor to correct the
problem.
Serviceable Tag
In addition to reviewing the physical part and the received paperwork, the QA Inspector will also review
the Inventory Records in Maintenix to ensure that the Receiving group has entered in all the relevant
information correctly (e.g. serial number, Owner, Quantity). Once the parts pass inspection a serviceable
tag can be printed.

Repair Routing

Area

Repair
Routing

(6)

Applicable Business
Process

Description

MMRR-01 Materials Turn In

This process describes how items are turned


back in to supply. This includes the turn-in of
unserviceable items that have just been
removed, and the turn-in of serviceable items
that were not used by maintenance.

MMRR-02 Repair Routing

This process describes how unserviceable


items are routed to the appropriate repair
facility. This could be an internal shop or an
external repair vendor.

MMRR-03 Vendor
Component Repair

This process describes how repair orders are


created and sent to the vendor. It also
describes the various interactions that occur
between the repair vendor and the customer
before the part is returned.

MMRR-01 MATERIALS TURN IN

In Maintenix, the Turn In page is used to monitor expected turn-ins and to record when parts are actually
turned in from maintenance.
At the MRO, the following parts are physically turned in from maintenance by mechanics:

Unserviceable repairable parts that are MRO-owned

Unserviceable repairable parts that are client-owned


Page 48

Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Unserviceable consumable parts (e.g.: warranty claims)

Serviceable parts that were unused

(7)

MMRR-02 REPAIR ROUTING

At the MRO, Storeroom Clerk will route parts that were turned into the unserviceable store:

If repair can be done locally within the time and price parameters, the part is routed to the shop.
The shop will create the workscope and perform the work. This process is a slight deviation from
SAS MMRR-02.

If repair cannot be done locally, the Material Planner will ask the shop engineers to prepare the
workscope for the external repair; the Material Planner will go through the normal approval
process to create the Repair Order.

If a part is a consigned part, then the Material Planner will communicate with the vendor that a
replacement is required and have the removed item returned.

Each repairable Part Number must be setup in Maintenix to identify if it can be repaired in a shop or must
be sent to a vendor.

(8)

MMRR-03 VENDOR COMPONENT REPAIR

For parts that are identified as needing to be sent to an external vendor to be repaired, the Material
Planner will take the work scope prepared by the shop engineer and prepare the repair order. The part
and the Repair Order are sent to the Shipping section to be shipped to the vendor. Once shipped, the
part will appear on the Out For Repair page where it can be monitored by the Material Planner. The
Vendor will send a quote for the repair and if accepted by the client, the Material Planner can approve the
repair order or convert it to an exchange. If the vendor decides that the part is not worth repairing, the
material planner may ask the vendor to send the part back to the MRO to be scrapped.

Warehouse Management

Area

Warehouse
Management

Applicable Business
Process

Description

MMWM-01 Materials
Shipping

This process describes how inventory is shipped


between airports and how inventory is shipped to
the vendor.

MMWM-02 Inventory Cycle


Counting

This process describes how cycle counting is


performed. It includes counting, recounting and
discrepancy resolution steps.

MMWM-03 Part Number


Initialization

This process describes what happens when a


new part number or a new alternate part number
is discovered.

MMWM-04 Warehouse SetUp

This process describes how a warehouse is


configured.

MMWM-05 Warehouse
Shelf-Life Monitoring

This process describes how the shelf life of


components in the warehouse is monitored.

MMWM-06 Component
Scrapping

This process describes the steps to condemn


and scrap a component.
Page 49

Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

MMWM-07 Surplus Stock


Monitoring

Mxi Technologies
Maintenix Version v6.8.13 SP2

This process describes how extra stock (surplus


and obsolete) can be periodically reviewed and
addressed.

Surplus: Serviceable stock in excess of the quantity needed to meet predicted demand, including a safety
stock level.
Obsolete: Serviceable stock that is not required for any current or future maintenance tasks (ex. For
former fleets, or non applicable parts)
Expired: Consumables close to or beyond their shelf life date.

(9)

MMWM-01 MATERIALS SHIPPING

In Maintenix, shipping functionality is used to create shipments to move inventory from one supply
location to another, or for sending inventory to a vendor.

(10)

MMWM-02 INVENTORY CYCLE COUNTING

Maintenix cycle counting & discrepancy handling functionality are used to periodically count stock in the
warehouse. This involves loading the results in a spreadsheet and uploading to Maintenix. If there are
discrepancies between the loaded count and the expected count, Maintenix provides the ability to force
recounts.

(11)

MMWM-03 PART NUMBER INITIALIZATION

At the MRO, the Material Planner sets up part number attributes.

(12)

MMWM-04 W AREHOUSE SET-UP

In Maintenix, the location hierarchy of a warehouse, including storerooms and bins must be defined. At
the MRO, the Material Planner identifies which store a part number will be stored at. Individual store
personnel will identify the bin or setup a new one when parts arrive at the store.

(13)

MMWM-05 W AREHOUSE SHELF-LIFE MONITORING

In Maintenix, part numbers can be setup to have a shelf life. When received, the shelf life of the inventory
is entered into the system so that it can be monitored when it is in the warehouse and can be properly
dealt with when if it becomes expired.

(14)

MMWM-06 COMPONENT SCRAPPING

At the MRO, there are several scrapping scenarios:


1. Part has reached Shelf Life Expiry (Warehouse marks as condemn)
2. Shop cannot repair part (Shop marks as condemn)
3. External vendor cannot repair a item part is shipped back to MRO (MRO will mark as condemn
after received, or the MRO will return to the client)
Page 50
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Parts awaiting scrap are stored in a separate location (similar to quarantine) until scrap approval is
received. Once the scrapping request is approved, technicians will physically scrap the part. When the
scrapping is recorded in Maintenix, a SCRAP transaction will be generate to remove the item from
financial books.

(15)

MMWM-07 SURPLUS STOCK MONITORING

Surplus stock monitoring functionality in Maintenix is used to find surplus and obsolete stock in the
warehouse. At the MRO, the Material Planner will monitor surplus stock. Surplus items are moved to
another store location to be sold. To look for surplus stock, the Material Controller can use the Obsolete
Inventory, Slow Moving Stock and Surplus Stock pages.
When surplus stock is sold, the inventory in Maintenix is archived with an Archive Reason of SOLD.
Tool Management

Area

Tool
Management

(16)

Applicable Business
Process

Description

MMTM-02 Tool Calibration


Monitoring

This process describes how tool calibrations


are periodically monitored.

MMTM-03 Tool Check-In


and Check-Out

This process describes how technicians can


acquire tools for use in maintenance.

MMTM-02 TOOL CALIBRATION MONITORING

Tools to be calibrated are monitored by Material Controller. Whenever a calibration is due, the shops are
notified so they can prepare the tool and update their upcoming work tool pre-draw list accordingly. At
the same time, the Tool Crib Manager will inform Supply for them to prepare the internal work-order.
Once tools are calibrated (usually externally), they will be returned to the tools room.

(17)

MMTM-03 TOOL CHECK-IN AND CHECK-OUT

Tool check-in/out is performed at the tool room. In Maintenix, the tool room will be setup as a serviceable
store (which is the equivalent of a warehouse). Tool check-out will be done from the tool room.

Page 51
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Finance and Purchasing


The Maintenix finance and purchasing module allows users to purchase materials and perform related
activities required to support aircraft maintenance. The solution described in this document assumes that
Maintenix will be integrated to at finance system. The interaction and division of responsibilities between
these systems is described in the Maintenix Finance User Guide.
The sections below lists the SAS Finance and Purchasing Business Processes that are provided with this
solution. These business processes illustrate the airline finance and purchasing processes in which the
Maintenix solution will be involved.

Material Planning
Area
Material
Requirement
Planning

(18)

Applicable Business Process

Description

FPMRP-01 Define Stock Levels

This process describes how stock


levels are generated.

FPMRP-02 Stock Level


Replenishment

This process describes how stock


levels are monitored, and how
replenishment stock is purchased.

FPMRP-01 DEFINE STOCK LEVELS

Stock Numbers
In Maintenix, Stock Numbers are used to define the rotable and consumables parts that are stocked in
the organization. This includes information like monthly demand, carrying costs, purchase/repair lead
times, service level, economic order quantity and global re-order level / allocation.
In Maintenix, a Part Number can only belong to one and only one Stock Number. Some analysis may be
needed to remap MRO part numbers to ensure they belong to only one Stock Number.
Stock Levels
MROs typically have a single stock level for each stock number. Once Stock Numbers are defined,
Material Controller can setup Stock Levels which are used to define the locations that parts are stocked
at. Each location can have a specific action when a stock low is hit, such as automatically generating a
request to purchase.
With enough history, Maintenix can be used to calculate the values for Stock Levels. In the meantime,
Stock Level values (e.g. Re-Order Levels) will be analyzed outside of Maintenix and any updates will be
entered as needed.

(19)

FPMRP-02 STOCK LEVEL REPLENISHMENT

As parts are issued to maintenance, the on hand quantity will decrease. If the available quantity is lower
than the Re-Order Level, then a Stock Low will be triggered. Material Controllers will monitor Stock Lows
and create a Stock Request as needed. Alternately, Maintenix can be setup to automatically generate
stock requests or purchase requests.

Page 52
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Procurement
Area

Applicable Business Process

Description

FPP-01 Create Purchase-BorrowExchange Order

This process describes how purchase


orders, borrow orders and exchange
orders are created. Aside from certain
pieces of information, the process is the
same for all three. This includes the
creation, authorization and issue of
orders.

FPP-03 Return Borrow-Exchange


Item

This process describes how borrowed


and exchanged items are returned to the
originating vendor.

FPP-04 Receipt Discrepancy


Management

This process describes how


discrepancies encountered during the
receipt process are handled and
resolved.

FPP-05 Return Item To Vendor

This process describes how items are


returned to the vendor. This will result in
either the vendor sending you a
replacement item, or in the vendor
returning your money (possibly in the
form of a credit).

Procurement

(20)

FPP-01 CREATE PURCHASE/BORROW /EXCHANGE ORDER

Purchase Orders
Purchase Orders are created for several reasons:
-

Stock Replenishment a purchase to ensure that the MRO has a sufficient standard stock on
hand to avoid any maintenance delays.
Pass-Through Purchase orders a purchase order on behalf of a client, where the MRO will
purchase and own the item for a short period of time, and will sell it to the client upon installation
on the aircraft.
Dropship Purchase Orders a purchase order is used to model the delivery of parts from the
client, so that the parts can be created and brought through the induction process.

Borrow Orders
Borrow Orders are created for several reasons:
-

Borrowing Tools a borrow order to support borrowing tools from a third party vendor for the
MRO to support special work
Modeling Customer Tool Dropships a borrow order is used to model the delivery of tools from
the clients, so that the tools can be created and brought through the induction process, and
returned in a timely manner to the client.

Repair & Exchange Orders


Repair and Exchange Orders are created to repair parts, both MRO and client parts.

Page 53
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Authorization
All orders have approval workflows, based on the MROs individual policy and procedures.

(21)

FPP-03 RETURN BORROW/EXCHANGE ITEM

Material Controller monitor consigned rotables that have been installed using the To Be Returned
Consignment page, and borrows on the Borrow Returns pages.

(22)

FPP-04 RECEIPT DISCREPANCY MANAGEMENT

Items that are received that have a discrepancy can be put into quarantine by the QA Inspector or
Shipping.
Discrepancy Resolution
The Purchasing Agent communicates with vendor to resolve the problem. In Maintenix, the Purchasing
Agent role has visibility of Quarantine page which lists all the items in Quarantine and the details of the
discrepancies.

(23)

FPP-05 RETURN ITEM TO VENDOR

Received items that have a problem that cannot be resolved can be returned to the vendor. The vendor
will provide a Return Authorization and the item is shipped back to the vendor.
Vendor Management

Area

Vendor
Management

(24)

Applicable Business Process

Description

FPVM-01 Review and Reapprove Existing Vendor

This process describes how existing


vendors are reviewed and reapproved.

FPVM-02 Approve New Vendor

This process describes how new


vendors are verified and approved
before they can be used for purchasing
or repairs.

FPVM-01 REVIEW & RE-APPROVE EXISTING VENDOR

Material Controller periodically (monthly) reviews vendor performance metrics such as discrepancies,
total purchase price, lead time. Maintenix provides a Vendor Reliability Report which can be used to
evaluate the performance of a vendor using criteria such as average number of orders per month,
average value of orders per month, and percentage of on time/late deliveries. Price history can also be
reviewed using the View Vendor Price History functionality. Discrepancies against received shipments
from vendors are captured in Maintenix when the shipment is quarantined.
A custom report would need to be developed to identify for each vendor the number of discrepancies, the
details of the discrepancy and the time it took to fix the discrepancy.
Page 54
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

(25)

Mxi Technologies
Maintenix Version v6.8.13 SP2

FPVM-02 APPROVE NEW VENDOR

Vendors must be setup and approved in Maintenix in order to purchase parts from or have parts repaired
by that vendor.
Material Controllers will create and maintained the vendors in the Maintenix.
Invoice Receipt

Area

Applicable Business Process

Description

Invoice Receipt

FPIR-04 Receive Invoice and


Mark For Payment

This process describes how invoices


are received by finance and marked for
payment.

(26)

FPIR-04 RECEIVE INVOICE AND MARK FOR PAYMENT

When the invoice is received, the details of the transaction are confirmed and the invoice is three-way
matched.
Average Unit Price (AUP)
In Maintenix, upon financial inventory receipt (and select other spots in the workflow) AUP is
automatically recalculated based on the existing quantity and AUP, and the price and quantity of the
newly purchased items.

Finance

Area
Finance

Applicable Business Process

Description

FPF-01 Account Management


and Setup

This process describes how the


finance account structure is
determined and configured.

FPF-02 Report on Financial


Activity

This process describes the different


financial activity reports that can be
generated.

FPF-03 Finance Adapter - Update


Currency Exchange Rate
FPF-04 Finance Adapter - Output
of Inventory Financial Log

These business processes are


documented in the finance adapter
documentation

FPF-05 Finance Adapter - Invoice


Synchronization
FPF-06 Finance Adapter - Orders
Synchronization

Page 55
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

The finance area of the concept contains the following functionality:

Financial accounts used to create the financial accounts that will be debited or credited when
financial transactions are recorded by Maintenix.
o A separate account number is used for each heavy maintenance visit.
Exchange rate synchronization used to update exchange rates in Maintenix to match the
exchange rates used in the finance system.
Finance system integration used to send Maintenix transactions to the finance system. These
transactions are all related to materials costs and include inventory creation/inspection, issuing,
turn-ins, scrapping, quantity adjustments etc.

Note: Labor costs and hours do not raise financial transactions in Maintenix, and are not handled by
the Finance Adapter. Fixed assets registry is not held in Maintenix.

2.5.23.6 Solution: Alternate Flow FMA


No changes.

2.5.23.7 Solution: Alternate Flow Ad Hoc


No changes.

2.5.23.8 Solution: Alternate Flow Integrated Airlines


No changes.

2.5.23.9 Standard Configuration


All clients will be modeled as vendors and linked operators in Maintenix

2.5.23.10

Reports

No custom reports are required to support this scenario.

2.6 Baseline Design


2.6.1 Equipment Baseline
The following section describes the equipment baseline design for the MRO Standard Solution Design.

2.6.1.1 Equipment Configuration


The aircraft configuration baseline for MROs is very simple ATA Chapter and Section, with no tracked
parts. Assemblies will be treated in the same fashion. No tracked parts will be defined. This means that
all component maintenance will be defined on an ad-hoc basis.
MROs that provide FMA services will use a full aircraft configuration baseline.

2.6.1.2 Aircraft Maintenance Program


An MRO that doesnt provide FMA services has several methods to define the maintenance program.
The recommended option is to organize the maintenance baseline according to the way that the MRO
executes the work. When a client ask for a specific piece of work, the Maintenance Planner will ensure
that the client requirements are mapped to the MRO requirements.
Tasks beyond the MDP ADs, SBs, SLs, EOs and deferred defects are defined on an ad-hoc basis,
unless the MRO can identify that the tasks are going to be regularly repeated.
If the MRO has a long-term contract with a stable visit scope, the MRO may create a customer-specific
baseline.

Page 56
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

The aircraft maintenance program has a limited scope. It will cover:


-

MPD tasks, organized in the way that the MRO plans and executes work, for each aircraft
assembly.

These task definitions will identify the following:


-

Standard Parts and Tools required to perform the work


Required labour and Signoffs
Traceability between Requirements and Job Cards
ATA chapter associated with the task definition.
High level work instructions (optional)

The task definitions will not contain:


-

Scheduling rules
IETM links (except when the MRO either writes the work instruction cards)
Detailed work instructions

When a new work package is created, the Planner will update the actual tasks that have been generated
from task definitions with specific data for the visit, including links to the clients work instructions (if
available), client-preferred parts and tools, and updated labour signoffs as required.

2.6.1.3 Component Maintenance Program


Component Maintenance Programs are not covered in this solution.

2.6.2 System Baseline


The following section describes the MRO Standard Solution system baseline design.

2.6.2.1 Configuration Parameters


The configuration parameters that need to be updated to support a MRO solution are as follows.
This list does not identify configuration parameters that need to be updated for every client, e.g.
DB_USERNAME.
Configuration Parameter

MRO Value

FORCE_INSP_REPAIR_RELEASE

FALSE

SHOW_COST

False

AUTO_FAULT_RECURRENCE_DAYS

RELEASE_AOG_FAULT
RELEASE_LOW_SEV_OPEN_FAULT

WARN
WARN

ISSUE_INV_RECEIVED_BY_REQUIRED_AND_AUTH

TRUE

REAUTHORIZE_PO

TRUE

Note
Changed to TRUE if items repaired in MRO shops
need secondary inspection.

This will be turned on for some roles, based on the


MROs internal policies and procedures.
Each visit starts clean, without continuity between
visits.
For FMA MROs, this value will be need to be reevaluated.
For FMA MROs, this value will be ERROR.
For FMA MROs, this value will be ERROR.
If the MRO uses runners (that is, if the techs do not
sign out their own parts), this will have to be set to
FALSE).
POs are often updated, based on customer feedback.

Figure 14 - Configuration Parameter Settings

2.6.2.2 Reference Terms


The following Reference Term updates are required, beyond the SAS updates:
Page 57
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Vendor Type (MSRP) See Appendix C Identification of MRSP and Vendor Prices for details.
Part Provider (As Required)
Task Priority (As Required)
Work Type (As Required)

Additional reference terms will be applied based on the needs of individual MROs.

2.6.2.3 Locations
The location hierarchy required for an MRO will be defined based on the needs of the individual
organization. The location hierarchy will be the same as defined in the SAS, with one exception.
Alternate: Customer Locations
If the MRO has a customer who stores a significant amount of consumables at the MRO, and the
consumables are tracked in Maintenix, the client inventory may be stored at separate customer location
which provides a separation between the MRO owned inventory and the client owned inventory.
The Customer Location will be modeled as a separate supply location, allowing auto-reservation to run for
both MRO owned inventory and client owned inventory.

2.6.2.4 Departments
The Department hierarchy required for an MRO will be defined based on the needs of the individual
organizations. An MRO needs only a simple department structure.

2.6.2.5 Authorities
Authorities are not used in the Standard MRO solution.

2.6.2.6 Organizational Security


As defined by individual client requirements.

2.6.2.7 Roles
For most needs of an MRO, the existing SAS roles can be used, customized to meet the specific needs of
the organization. Examples of typical customizations include Purchase Order approval levels.
MRO Specific Roles
Client Approval: A role used to record customer approval for additional work.
rd

Shop Controller: Needs to be able to create orders to support 3 party component shop work.
Billings: A role used to run invoice reports and validate information.

2.6.2.8 Users
MROs can use the standard SAS guidelines in regards to users.

2.6.2.9 Skills and Licenses


The MRO may define skills and licences in Maintenix. The process for this is the same as in SAS, with
one extension.
The Labour Skills defined on client Job Cards will often be different than the labour skills defined by the
MRO. When the work package is being prepared (prior to being loaded), the Planner will need to validate
that the equivalent labour skills to the client-defined labour skills are defined in the MRO environment,
and that all client skills are mapped.

2.6.2.10 Jobs
The required jobs for the MRO standard solution will be based on the SAS set, with the following
The following jobs will be turned off:
Page 58
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

MX_CORE_ABCRECALCULATION
MX_CORE_AUT_EXP_WARRANTY
MX_CORE_CONVERT_TO_COMPONENT
MX_CORE_DELETE_ORPHANED_FORECASTED_TASKS
MX_CORE_GENERATEFLIGHTPLANFORAIRCRAFT
MX_CORE_GENERATEFORECASTEDTASKS
MX_CORE_REOPEN_PART_REQUEST
MX_CORE_STATUS_BOARD_REFRESH_ASSET_LIST
MX_CORE_STATUS_BOARD_REFRESH_QUERY_DATA
MX_CORE_WARRANTY_EVALUATION

Note: Baseline Synch is turned on, but is turned off for all aircraft. It is only used for Tool Calibration
tasks.
For FMA, Baseline Synch will be enabled for all aircraft.

The job settings will be updated by the project team, based on the exact specifications of the
implementation.

2.6.2.11 Alerts
No custom alerts are required for the MRO Standard Solution.

2.6.3 Materials Baseline


The following section describes the MRO Standard Solution materials baseline design.

2.6.3.1 Parts Numbers


The MRO will use Part Groups, with the preferred part being the part that the MRO normally uses in the
contracts.

2.6.3.2 Stock Numbers


Stock Numbers used to define the parts, rotables and consumables that are stocked including
information like monthly demand, carrying costs, purchase/repair lead times, service level, economic
order quantity and global re-order level/allocation.
The MRO will define stock numbers according to the parts that the MRO prefers to provide, along with the
alternates that the client provides.

2.6.3.3 Vendors / Organizations


Vendors are defined in the standard SAS method each of the clients vendors will be created, along with
approval status. If a vendor is approved by the MRO, its a blanket approval for all activities in the
organization.
The MRO will be designed as the local organization.
Modeling of Clients
Each of the MROs clients will be defined as a vendor and an organization. This will allow each client to
be defined as a non-local owner.

2.6.3.4 Finance
An MRO has two finance needs the ability to identify the cost of operations, and the ability to identify the
amount to bill the client for a visit.

Page 59
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Cost of Operations
An integration (manual or automated) to the MROs finance application will allow the MRO to identify the
cost of operations the actual cost to the MRO of the day-to-day operations.
Invoicing
The invoicing solution is outlined in Appendix B Invoicing Solution - This report shows all of the tools that
have been requested for a selected work package. For each tool, the report shows a variety of
information, including the tools that are currently available that are MRO-owned and client owned, as well
as any orders that have been created to provide this tool.
This report shows the availability of tools when the report is run. It does not attempt to predict the
availability of tools for the scheduled start of the work package or task.
This report can be run as soon as the work package is created in Maintenix. It is expected that it will be
regularly run until all tools required to perform the work package have been received.
Header Section
Name: Name of the Report (Static)
Date Run: Date the report was run.
Work Package: Name of visits Work Package.
Work Package Status: Work Package status.
Aircraft: The Aircraft associated with the visits Work Package.
Owner: The Owner of the aircraft associated with the visits Work Package.
Actual or Scheduled Start Date: Display the Actual Start Date of the visits Work Package if it is nonblank, and set the label to Actual Start Date. Otherwise, display the Scheduled Start Date of the visits
Work Package, setting the label to Scheduled Start Date, which is the default label. The Scheduled Start
Date may be blank.
Actual or Scheduled End Date: Display the Actual End Date of the visits Work Package if it is nonblank, and set the label to Actual End Date. Otherwise, display the Scheduled End Date of the visits
Work Package setting the label to Scheduled End Date, which is the default label. The Scheduled End
Date may be blank.
Report Body
Line No: This field identifies the work package line number for the task
Task Name: This field contains the task name.
Task ID: This field contains the Task ID.
Task Status: This field contains the current status of the task.
Task Contract Status: This field identifies the contract status of the task. The contract status is stored in
the Task Priority field on the actual task. The report will show the value in this field.
Scheduled Date: This field contains the scheduled date of the task.
Tool Description: This field contains the Tool description
Checked Out Tool: This field identifies if the tool has been checked out for this task
Checked Out To: If the tool has been checked out for this task, this field identifies the user to whom the
tool was checked out
Sched. Hours: This column shows the number of hours that the tool is scheduled to be required for.

Page 60
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Available Local: This field identifies how many locally available tools are present. Two numbers will be
displayed (1 of 4), where the first number is the number of tools that are serviceable and arent checked
out, and the second number is the total locally available). The Report Defines Locally Available when
the part is at AMM, the owner is MRO, and is one of the following conditions:

SRV (Ready for Issue)


QUAR (Quarantined)
INSPREQ (Inspection Required)

If the tool is at MRO and is not owned by the MRO or is in one of the following conditions, it will not be
shown as available.

REPREQ (Repair Required)


ARCHIVE (Archived)
CONDEMN (Condemned)
SCRAP (Scrapped)

Client Owned: This field identifies if the client currently has the specified tool at the MRO.
Standard Part: This column identifies if this is a standard tool that is, if the MRO normally supplies this
tool. This information is stored on the Part Voltage Field on the Task details page. The value in this field
(MRO Supplied or Individually Provisioned) will be shown in this column.
Chargeability: This field identifies if the chargeability of the tool that is, if the MRO charges for the
client for the use of this tool. This information is stored on the Current field on the Task details page. The
value in this field will be shown in this column.
Order Code: This column identifies if an associated order has been created to fulfill this tool requirement.
The order is associated in the following manner:
The order contains the same tool number/manufacturer. There may be more than one actual tool on the
borrow order, but that will have no impact on this report
The order contains the same account number, either directly on the order (in the case of borrow orders),
as a misc line (in the case of some purchase orders) or as a Note to Vendor (for some purchase orders,
or where an order is fulfilling needs for several visits).
If an associated order does not exist, this column will be blank.
Note: It is assumed that the same tool will not appear on multiple orders for the same visit.
Order Status: If the tool requirement is linked to an order, this column will show the current status of the
order.
Mockup
Name

Aircraft

Date Run

Owner
Actual or
Scheduled
Start Date
Actual or
Scheduled
End Date

Work
Package
Work
Package
Status

Li
ne
No

Task
Name

Task
ID

Tas
k
Stat
us

Sched
uled
Date

Task
Contr
act
Statu
s

Tool
Descrip
tion

Chec
ked
Out
Tool

Chec
ked
Out
To

Sche
d.
Hours

Availa
ble
Local

Clie
nt
Own
ed

Stand
ard
Part

Charge
able

Order
Code

Order
Statu
s

Page 61
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

PHAS
E
OUT
+
PAIN
T
PHAS
E
OUT
+
PAIN
T
PHAS
E
OUT
+
PAIN
T

Mxi Technologies
Maintenix Version v6.8.13 SP2

T0005
RAL

IN
WO
RK

08APR2011

12-114
(THREA
DED
DRILL)

Decisi
on

PO12017
010

Issue
d

T0005
RAL

IN
WO
RK

08APR2011

12-201038
(HAND
TAP
SET)

Decisi
on

PO12017
016

Recei
ved

T0005
RAL

IN
WO
RK

08APR2011

12-201118
(TAP
SET)

Decisi
on

BO12027
010

Issue
d

Invoicing
Solution
. The invoicing solution is a combination of data retrieved from Maintenix, combined with data that is not
available to Maintenix.
Invoice preparation will be done outside Maintenix.

2.7 Data Migration Design


Data Migration Design is an activity that must be tailored to each client.
On an MRO project data validation takes many different forms. The following is a high level description of
how the data will be validated.
Migration

Configurator before data can be loaded using the Configurator it is validated using the tool
against reference terms and some Maintenix rules. The data must full pass before it can be
loaded.

AMU/Records Induction load - before data can be loaded using Record Induction, AMU
provides validation against reference terms, baseline and Maintenix rules. Then AMU
provides metrics with regards to which data will be successfully loaded into Maintenix.

Post Migration

Databse Rule checks this is a set of SQL statements that checks for certain erroneous data
conditions. These will be run to identify data issues.

Content comparisons to legacy source system once the data is loaded into Maintenix it
should be compared to the source to make sure no data was warped or left behind in the
migration process, so examples of what should be checks are:

Parts catalog

List of Requirements

Actual outstanding tasks per aircraft

Task for task, deadline for deadline


Page 62

Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Usage on components based on part number / serial number

Inventory valuation

Spot checks during User Acceptance Testing data will be used to execute test cases. Users
should be on the lookout for data issues and identify those to the data migration team.

Parallel runs during the parallel runs the system will be used to mimic production. If the
parallel runs are done as closely as possible reflect what will happen in production this
process will quickly expose issues with the most time sensitive data (e.g. daily tasks).

Once data issues are identified there are 3 options to correct the issue
1. Cleanse source systems
2. Modify the extraction method from source systems
3. Modify the transformation method

2.7.1 Scope of Data Migration


Area

Data

Classification

Description

Equipment

Manufacturers

Migrated

Assemblies

Migrated

The complete list of assembly, part, tool


and common hardware manufacturers
will be migrated from legacy systems.
The list of aircraft, engine and APU
assemblies will be migrated from legacy
systems.

Part Definitions
and
Configuration

Migrated and
Configured

The catalogue of aircraft, engine and


APU part numbers will be migrated from
legacy systems.

Tools and
Service
Equipment

Migrated

Tool part numbers will be migrated


from legacy systems. These are always
tracked part numbers. Calibration
requirements for these part numbers
can also be migrated from legacy
systems.

Common
Hardware

Migrated

Common hardware part numbers will be


migrated from legacy system. These
part numbers are either batch or
serialized and can be installed /
consumed by any assembly.

Zones and
Panels

Migrated

Zones and panels for aircraft


assemblies will be migrated from legacy
systems.

Measurements

Configured

Measurements will be migrated from


legacy systems.

Job Cards

Migrated

Job cards will be migrated from external


systems. Job cards will list the labour,

Maintenance

Page 63
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Area

Data

Mxi Technologies
Maintenix Version v6.8.13 SP2

Classification

Description
parts and tools required to accomplish
the work.

Materials

Finance

System

Requirements

Migrated

Requirements will be migrated from


legacy systems. Requirements include
EOs for ADs/SBs, component overhauls,
MPD inspections, etc.

Reference
Documents

Migrated

Reference Documents will be migrated


from legacy systems.

Owners

Configured

The MRO will be defined as a local


owner.

Warehouse
Setup

Migrated

Warehouse setup (stores, bins, docks)


will be migrated from legacy systems.

Stock Numbers

Migrated

Stock numbers will be migrated from


legacy systems. This will include reorder levels, re-order quantities, lead
times, etc.

Vendors

Migrated

Vendors will be migrated from legacy


systems. This will include vendors who
supply parts for purchase / exchange /
borrow and vendors who perform
repairs. All clients who will be providing
part will be defined as vendors.

Currencies

Configured

Currencies will be configured in


Maintenix.

Accounts

Migrated

Financial accounts will be migrated from


legacy systems.

T-Codes

Migrated

T-Codes will be migrated from legacy


systems.

Roles

Configured

SAS roles will be used, with the


modifications identified in this
document. Additional custom roles or
changes to the standard roles will be
done using the Maintenix user interface.

Users

Migrated

Users will be migrated from legacy


system.

Locations

Migrated and
configured

Locations will be migrated from legacy


system.

Departments

Migrated and
configured

Departments will be migrated from


legacy system.

Organizations

Configured

The MRO will be defined as an


organization. Each client will also be
defined as an organization.

Page 64
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Area

Actuals

Mxi Technologies
Maintenix Version v6.8.13 SP2

Data

Classification

Description

Operators

Configured

A single operator will be configured in


to represent the MRO. Each client will
have its own organization.

Configuration
Parameters

Configured

The standard solution will start with the


SAS standard configuration, modified as
described in this document. The Project
Team will make further refinements
based on the needs of the customer.

Jobs

Configured

According to SAS standards, unless


otherwise mentioned.

Reference Terms

Configured

Based on SAS default reference terms,


updated based on the references in this
document.

Printers

Configured

Printers for task cards, issue tickets and


put away tickets will be configured for
MROs.

PO Authorization
Workflows

Migrated

Purchase order authorization workflows


will be migrated from legacy systems.

Task Definition
Authorization
Workflows

Configured

Task definitions authorization workflows


will be configured by the project team.

Aircraft, Engines
and APUs

Migrated

Aircraft, engines and APUs that are


currently at the MRO will be migrated
from legacy systems.

Installed
Components

N/A

Installed components on aircraft,


engines and APUs will not be migrated
from legacy systems.

Loose
Components

Migrated

Loose aircraft, engine and APU


components will be migrated from
legacy systems.

Common
Hardware

Migrated

Common hardware inventory will be


migrated from legacy systems.

Tools

Migrated

Tools and other support equipment will


be migrated from legacy systems.

Open Purchase
Orders

Migrated

Open purchase orders will be migrated


from legacy systems.

Open Work
Packages

Migrated

Open work packages will be migrated


from the legacy systems.

2.8 Use Case Impact


Each project will review the SAS use cases and identify what changes need to be made.
Page 65
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

One MRO Standard Solution use cases is currently available:


-

rd

MRO-12 3 Party Component Maintenance

2.9 Custom Software/Reports


2.9.1 External Maintenance Adapter (EMA)
MRO uses the EMA to load work packages. MROs with long-term contracts work packages average
85% baselined and 15% ad-hoc, though this number varies between organizations. The parts, tools and
labour for the baselined tasks may be updated with specific customer requirements

2.10 Database Rules


The MRO Standard solution will use the standard Database rule (DB) suite. Additional DB rules may be
developed to support aspects of the MRO, based on the needs of the MRO:
Typical DB rules that may be created include:
-

All Part Requests need to have the Part Provider field entered
All REQs and ADHOC tasks need to have the Task Priority field defined
Vendors of type MSRP should never be approved. See Appendix C Identification of MRSP
and Vendor Prices for details.
Parts should have exactly one purchase link to a MSRP-type vendor
Parts that had been made serviceable in the shops X days ago, but hadnt been moved
Customer Owned parts in Quarantine for X days or more
Items that hadnt been turned in for X days since the task was completed / the aircraft left, etc.

Page 66
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Appendix A

Mxi Technologies
Maintenix Version v6.8.13 SP2

Tool Provisioning Report

This report shows all of the tools that have been requested for a selected work package. For each tool,
the report shows a variety of information, including the tools that are currently available that are MROowned and client owned, as well as any orders that have been created to provide this tool.
This report shows the availability of tools when the report is run. It does not attempt to predict the
availability of tools for the scheduled start of the work package or task.
This report can be run as soon as the work package is created in Maintenix. It is expected that it will be
regularly run until all tools required to perform the work package have been received.
Header Section
Name: Name of the Report (Static)
Date Run: Date the report was run.
Work Package: Name of visits Work Package.
Work Package Status: Work Package status.
Aircraft: The Aircraft associated with the visits Work Package.
Owner: The Owner of the aircraft associated with the visits Work Package.
Actual or Scheduled Start Date: Display the Actual Start Date of the visits Work Package if it is nonblank, and set the label to Actual Start Date. Otherwise, display the Scheduled Start Date of the visits
Work Package, setting the label to Scheduled Start Date, which is the default label. The Scheduled Start
Date may be blank.
Actual or Scheduled End Date: Display the Actual End Date of the visits Work Package if it is nonblank, and set the label to Actual End Date. Otherwise, display the Scheduled End Date of the visits
Work Package setting the label to Scheduled End Date, which is the default label. The Scheduled End
Date may be blank.
Report Body
Line No: This field identifies the work package line number for the task
Task Name: This field contains the task name.
Task ID: This field contains the Task ID.
Task Status: This field contains the current status of the task.
Task Contract Status: This field identifies the contract status of the task. The contract status is stored in
the Task Priority field on the actual task. The report will show the value in this field.
Scheduled Date: This field contains the scheduled date of the task.
Tool Description: This field contains the Tool description
Checked Out Tool: This field identifies if the tool has been checked out for this task
Checked Out To: If the tool has been checked out for this task, this field identifies the user to whom the
tool was checked out
Sched. Hours: This column shows the number of hours that the tool is scheduled to be required for.
Available Local: This field identifies how many locally available tools are present. Two numbers will be
displayed (1 of 4), where the first number is the number of tools that are serviceable and arent checked
out, and the second number is the total locally available). The Report Defines Locally Available when
the part is at AMM, the owner is MRO, and is one of the following conditions:

SRV (Ready for Issue)

Page 67
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

QUAR (Quarantined)
INSPREQ (Inspection Required)

If the tool is at MRO and is not owned by the MRO or is in one of the following conditions, it will not be
shown as available.

REPREQ (Repair Required)


ARCHIVE (Archived)
CONDEMN (Condemned)
SCRAP (Scrapped)

Client Owned: This field identifies if the client currently has the specified tool at the MRO.
Standard Part: This column identifies if this is a standard tool that is, if the MRO normally supplies this
tool. This information is stored on the Part Voltage Field on the Task details page. The value in this field
(MRO Supplied or Individually Provisioned) will be shown in this column.
Chargeability: This field identifies if the chargeability of the tool that is, if the MRO charges for the
client for the use of this tool. This information is stored on the Current field on the Task details page. The
value in this field will be shown in this column.
Order Code: This column identifies if an associated order has been created to fulfill this tool requirement.
The order is associated in the following manner:
The order contains the same tool number/manufacturer. There may be more than one actual tool on the
borrow order, but that will have no impact on this report
The order contains the same account number, either directly on the order (in the case of borrow orders),
as a misc line (in the case of some purchase orders) or as a Note to Vendor (for some purchase orders,
or where an order is fulfilling needs for several visits).
If an associated order does not exist, this column will be blank.
Note: It is assumed that the same tool will not appear on multiple orders for the same visit.
Order Status: If the tool requirement is linked to an order, this column will show the current status of the
order.
Mockup
Name

Aircraft

Date Run

Owner
Actual or
Scheduled
Start Date
Actual or
Scheduled
End Date

Work
Package
Work
Package
Status

Li
ne
No

Task
Name

Task
ID

Tas
k
Stat
us

Sched
uled
Date

PHAS
E
OUT
+
PAIN
T

T0005
RAL

IN
WO
RK

08APR2011

Task
Contr
act
Statu
s

Tool
Descrip
tion

Chec
ked
Out
Tool

Chec
ked
Out
To

12-114
(THREA
DED
DRILL)

Sche
d.
Hours

Availa
ble
Local

Clie
nt
Own
ed

Stand
ard
Part

Decisi
on

Charge
able

Order
Code

Order
Statu
s

PO12017
010

Issue
d

Page 68
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

PHAS
E
OUT
+
PAIN
T
PHAS
E
OUT
+
PAIN
T

Mxi Technologies
Maintenix Version v6.8.13 SP2

T0005
RAL

IN
WO
RK

08APR2011

12-201038
(HAND
TAP
SET)

Decisi
on

PO12017
016

Recei
ved

T0005
RAL

IN
WO
RK

08APR2011

12-201118
(TAP
SET)

Decisi
on

BO12027
010

Issue
d

Appendix B

Invoicing Solution

The Invoice Solution is designed to provide a process by which MRO can clearly and accurately prove
that the terms of the contract were fulfilled by providing traceability to the actual activities performed in the
maintenance visit.
One of the key elements of this solution is the introduction of the auditing reports, which will be run on a
daily basis to ensure that the visit is correctly executed and recorded in Maintenix according to the terms
of the contract. Daily execution of the auditing reports will allow the fast and accurate delivery of the
invoice.
The key element of the Workscope Loading process is the definition of the tasks, labour, parts and tools
in each work package. These elements have to be defined to ensure that the client approval is garnered
when necessary, and the client invoice is developed quickly and accurately.
This section identifies how the invoice flags will be set for the tasks, to correctly identify extras.

Tasks Flags
The following figures describe how tasks will be defined in Maintenix to reflect the invoicing rules that
apply to them.

Page 69
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Figure 15 - Invoicing Solution - Tasks - Part 1

Page 70
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Figure 16 - Invoicing Solution - Tasks - Part 2

Page 71
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Figure 17 - Invoicing Solution - Tasks - Part 3

Page 72
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

AIRCRAFT W ORK PACKAGE


The Aircraft Work Package will hold the following information:
-

The Customer Account Code (Control Number). This will be the same number as found on all
Shop Work Packages that are associated with this visit. This information will be stored in the
Doc. Reference field of the Work Package Details.

The Alert Level for the Part Cap will be stored on the Account Code (External Reference field)
associated with the Work Package. This value will be available to all MRO employees, and will be
for reference/reporting purposes only.
o

The Issue ticket may be modified to include this information, as well as the sum of the
parts that have been issued to the task, but Maintenix will not prevent or warn against
issuing parts that are over the cap.

A flag to indicate if the non-routines in this work package are capped at the requirement level, or
at the non-routine level. This information as to how the non-routines are capped will be available
to all MRO employees, and will be for reference/reporting purposes only. This flag will be an
additional Work Type (REQLEV or TASKLEV).

If the Part Cap limits are set by Single Item or Line Item. This will be stored in the Account Code
associated to the work package, or used as an input to the appropriate reports. The Description
field will contain the Type (LINE or SINGLE).The Part and Tool Provisioning Appendix will also
contain this information.

For Shop Work only, a work type for each additional certification required. MRO will add
additional work types, so that each certification can be identified. This will also be stored in the
document attached to the Work Package.

For Shop Work only, a work type (EXPEDITE) that identifies if the shop work package has been
expedited.

CONTRACTED TASKS, W ITH CAP TIME AND MATERIALS (T&M) OVER CAP
Tasks in this category are in the original contract. These tasks have been designated as Time and
Materials, with a cap.
The terms of the T&M with task capping will not be stored in Maintenix. The alert level will be stored as
part of the Account Details, and the identification of what components are provided by the customer, but
the contract terms will not be stored.
Any non routine that exceeds hours cap limit will be T&M, and will need customer signature. These nonroutines must be created in Maintenix from the task, not from the work package.
A flag will be set on the work package level that defines if the non-routines are capped at the requirement
level, or at the non-routine level.
Priority: TMCAP

CONTRACTED TASKS, FIRM FIXED PRICE (FFP)


Tasks in this category are in the original contract. These tasks have been designated as FFP.
The terms (including the price that the customer will be charged) of the FFP task will not be stored in
Maintenix. The provisioning arrangement for all parts and, as well as the rules under which all nonroutine tasks associated with the FFP task will operate will be stored in Maintenix as an attachment.
Any non-routine raised during the execution of a contracted FFP task will be T&M, and will require
customer approval. These non-routines must be created from the task, not from the work package.
Priority: FFP

Page 73
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

CONTRACTED TASKS, ALL T&M


Tasks in this category are in the original contract. These tasks have been designated as T&M.
The terms of the T&M task will not be stored in Maintenix.
Any non-routine task raised from a Time and Materials task will be T&M, and will require customer
approval. These non-routines must be created from the task (on the Task Details page), not from the
work package.
Priority: TM

NON-ROUTINE, T&M
Tasks in this category are raised after the work package is created. These tasks have been designated
as T&M.
These tasks may have been raised from the aircraft logbook. These tasks were not raised during the
execution of a task. These non-routines will be created on the work package (on the Work Package
Details page).
Priority: EXTRATM

NON-ROUTINE, CAPPED T&M OVER CAP


Tasks in this category are raised after the work package is created. These tasks have been designated
as T&M, with a Cap.
These tasks may have been raised from the aircraft logbook. These tasks were not raised during the
execution of a task. These non-routines will be created on the work package.
The terms of the cap are not stored in Maintenix. Alert level is stored in Maintenix.
Priority: EXTRACAP

NON-ROUTINE, NO COST TO THE CLIENT


Tasks in this category are raised after the work package is created. These tasks have been designated
as no cost to the client. These non-routines will be created on the work package.
Priority: NOCOST

AWR T&M
Tasks in this category are AWRs that are time and materials. Customer approval (via a Customer
Support Coordinator signoff of a labour row) is required to perform this task.
Tasks in this category will be raised in Maintenix as a task, not as a fault.
The terms of the T&M task will not be stored in Maintenix.
Any non-routine raised from a Time and Materials task will be T&M, and will require customer approval.
These non-routines must be created from the task, not from the work package.
Priority: AWRTM

AWR FIRM FIXED PRICE


Tasks in this category are AWRs that are firm fixed price. Customer approval (via a Customer Support
Coordinator signoff of a labour row) is required to perform this task.
Tasks in this category will be raised in Maintenix as a task, not as a fault.
The terms of the firm fixed price task will not be stored in Maintenix.

Page 74
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Any non-routine raised from a Firm Fixed Price task will be T&M, and will require customer approval.
These non-routines must be created from the task (Task Details page), not from the work package (Work
Package Details page).
Priority: AWRFFP

Page 75
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Labour and Tool Flags

Figure 18 - Invoicing Solution - Labour and Tools


Page 76
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

STANDARD BID (BORROWED) (INVOICE 0)


This category identifies standard tools that have been borrowed for this visit. As standard tools, it is
expected that MRO will provide these tools, so the leasing cost will not be passed on to the customer.
These type of borrows fall into three categories:
-

Tools that it is not economical to purchase

Tools that are normally stocked, but are currently not available

Tools that have not yet been purchased (Related to a new task/component/activity)

Tools in this category will be received via the normal receipt process in Maintenix, and will be archived
when the visit is complete.
Financial Impact: The Borrow Order should contain the full cost of the borrow, so that the correct values
are stored in the Maintenix transaction log to allow MRO to identify the cost of goods sold.

CHARGABLE (INVOICE = $ PER HOUR)


This category includes special tools that are owned by MRO, and are chargeable by the hour to the client.
Maintenix will not contain the hourly charge rate for these tools.
The time spent using these tools will be tracked in Maintenix using the duration of the Tool requirement.
Note that this value can be edited (with tightly controlled special role-based permissions) after the task is
complete.
Financial Impact: These tools remain property of MRO, so there are no financial transactions associated
with this visit.

LEASED FOR THIS VISIT (INVOICE = PO TOTAL + S&H?)


This category includes special tools that have been leased by MRO for this visit. The client will be
charged for the lease, provided the item is returned promptly.
The Tool lease, including the cost, will not be tracked in Maintenix. The invoicing department will use
Maintenix to identify which tools were leased for the visit
A note may be added to the work package Task Description field to clearly identify which tool leases were
related to the tool requirements in the visit.
Financial Impact: The Borrow Order should contain the full cost of the borrow, so that the correct values
are stored in the Maintenix transaction log to allow MRO to identify the cost of goods sold.

DROPSHIP (NON-STANDARD) (INVOICE = 0 + S&H?)


This category includes non-standard tools that have been supplied by the customer. These tools may be
sent directly to MRO, or shipped on the aircraft.
These tools are non-standard, so the original contract will have identified that the customer will provide
these tools. As the tools are customer-provided, there is no leasing cost or hourly charge, but MRO may
charge the client for the shipping and handling fees, as the tools need to be inspected and stored.
Tools in this category will be received via the normal borrow process in Maintenix, and will be
automatically archived when the visit is complete and the tools are returned to their owner.
Financial: MROs finance department will have to identify how they want to reflect the S&H for dropship
tools. MRO will provide confirmation of the exact method.

Page 77
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

DROPSHIP (STANDARD) (INVOICE = 0, LOAN CHARGED TO MRO)


This category includes standard tools that have been supplied by the customer.
nominally expected to be provided by MRO, but are not available.

These parts are

As these are standard tools, MRO will be charged, by the client, for the loan of these tools.
The terms of this loan will not be tracked in Maintenix.
Tools in this category will be received via the normal receipt process in Maintenix, and will be archived
when the visit is complete.
Financial Impact: The Borrow Order should contain the full cost of the borrow, so that the correct values
are stored in the Maintenix transaction log to allow MRO to identify the cost of goods sold..

STANDARD BID (OWNED) (INVOICE 0)


This category includes standard tools that are normally included in a visit at no cost to the client.
In this category, the tools are available when required.
Financial: These tools remain property of MRO, so there are no financial transactions associated with this
visit.

Part Requirements

Page 78
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Figure 19 - Invoicing Solution - Parts Provisioning

Page 79
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

MRO PROVIDED (INVOICE = MSRP)


Upon award of contract, the provisioning strategy of all parts that are known to be required to complete
the visit will be identified. For many visits, MRO will provide the consumables and expendables, but some
clients will provide the parts (these will be considered dropshipped parts).
AWRs and Non-routines may have part requests that are fulfilled by MRO provided parts.
This category includes parts (usually consumables or expendables) that are provided by MRO and
installed or used during the execution of a task.
These parts are usually stocked by MRO, but in some cases may be purchased for the visit.
These parts will be charged to the customer based on the Manufacturers Suggested Retail Price
(MSRP). If the sum of the parts required to complete a task is over the cap, customer acceptance will be
requested, and the client will be charged for the extra costs.
Finance: These parts will have the normal financial transactions associated with them (mainly - Purchase
/ Issue)
Part Provisioning: NORMAL
Part Ownership: MRO

ROB (INVOICE = 0)
Robbing is a reactive part fulfillment strategy it will never appear in the original contract part fulfillment
strategy. Robs are usually a last choice option, occurring when the original fulfillment option for a part
request is no longer a valid option, and other options are unable to provide the part.
AWRs and Non-routines may have part requests that are fulfilled by robbed parts.
When a part requirement cannot be fulfilled, MRO may rob the part from another aircraft to meet the part
demand.
This has several implications to the invoicing solution:
1) A new part request has to be created for the aircraft that is now missing the part.
2) MRO has to decide how to invoice the part request. Intra-client part robs are out of scope for this
phase.
3) The original part provisioning strategy for the original plane (for example, a purchase order)
should be repointed to the robbed aircraft.
Robs are manually supported in the Standard Solution. The purpose of this invoice flag is to identify to all
concerned parties that a rob has occurred, and that special care must be taken to ensure that client is
correctly invoiced.
Finance: Robbed parts will generally have no financial transactions. In some cases, robbed parts may
be turned in and issued, in which case there will (normally) be off-setting transactions. The repointing of
the original part fulfillment strategy (Purchase Order?) may have financial implications.
Part Provisioning: ROB
Part Ownership: CLIENT

PASS-THROUGH PO (INVOICE = PO TOTAL + S&H?)


During contract negotiation, the client may ask MRO to purchase parts on their behalf, and pass on the
cost of the purchase order to the client as part of the visit invoice. This part fulfillment agreement will be
included in the contract.
AWRs and Non-routines may have part requests that are fulfilled by part purchased pass-through PO.

Page 80
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

MRO must ensure that these parts will be available in time for parts with long lead times, this means
that MRO will issue the purchase orders well before the aircraft arrives.
Pass-Through Purchase Orders will be identified using the Bill-To Field.
These parts are usually not stocked by MRO.
Financial: The parts purchased on the Pass-Through purchase order will be owned by MRO, so there will
be financial transactions on purchase. As these items are tracked as consumables, there will be another
financial transaction on issue. MROs finance department will have to identify how they want to reflect the
S&H for dropship parts. MRO will provide confirmation of the exact method will be provided later.
Part Provisioning: PASSTHRU
Part Ownership: MRO

DROPSHIP (INVOICE = 0 + S&H?)


During contract negotiation, the client may inform MRO that the client will send the parts to MRO to meet
some or all of the part requirements for a visit.
AWRs and Non-routines may have part requests that are fulfilled by dropshipped parts.
These parts are usually rotables, but may be consumables or expendables.
Upon Award of Contract, the dropship will be divided into two categories: Parts that will be delivered on
the aircraft, and parts that will be shipped directly to MRO.
A dropship purchase order will be created for all of the parts that will be delivered on the aircraft.
A dropship purchase order will be created for each of the parts that will be shipped directly to MRO.
These purchase orders will allow the parts to be drawn into Maintenix via the receipt process.
MRO may charge the client an additional fee (over the Purchase Order Total) to cover the cost of
receiving and inspecting the part, and (if applicable) storage of the part. These costs may be stored in
Maintenix, or they may be kept out of Maintenix for information security concerns.
MRO will use a custom script (or scripts) to ensure that the owner of the drop shipped inventory is correct,
and there are no financial transactions associated with the dropship purchase orders.
Tools being drop shipped will always use Borrow Orders, as borrow orders natively support the return to
vendor shipment.
Finance: MROs finance department will have to identify how they want to reflect the S&H for dropship
parts. MRO will provide confirmation of the exact method will be provided later.
Part Provisioning: DROPSHIP
Part Ownership: CLIENT

REMOVED PARTS (INVOICE = 0)


This category includes parts that are removed for various reasons (including removal for access,
troubleshooting and swaps) and for which the part request has been generated in Maintenix. These type
of removals are generally not tracked in Maintenix this is an exception case.
Removed parts are not a provisioning strategy, but are required to ensure that the part requirements that
are being fulfilled by client parts are not charged to the client.
Financial: Removed parts are not expected to be turned in, and will therefore have no financial
transactions.
Part Provisioning: REMOVED
Part Ownership: CLIENT
Page 81
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

SHOP / VENDOR REPAIR (INVOICE = SEPERATE PO)


This category includes parts that are removed for internal shop repairs (Internal Repair Orders) and/or
vendor repairs (External Repair Orders) and for which the part request has been generated in Maintenix.
The contract will identify if the part is going to be removed and repaired and reinstalled. The costs related
to this part are covered by the Shop Work Package, and/or in the Vendor Repair Order.
The Shop or Vendor work will be covered in a different work package. The costs will be tracked
separately in Maintenix, and will be finalized outside of Maintenix. This work package may include
additional costs, such as shipping and handling, customs and storage fees, if applicable.
Financial: The full cost of the parts issued to the Repair Order will be stored in Maintenix, and will appear
in the Financial log.
Part Provisioning: SHOPREPR
Part Ownership: CLIENT

Charge Numbers (Control of Reservation/Issue of Parts)


MRO uses an Alert level for parts that customers that would need representative approval in order to
buy/issue materials if they are above the contracted limit.
Each contract (visit) may have different alert levels for the same part or task. This information will be
defined on the Account Code (see Aircraft Work Package section)
MRO will create a report that identifies the part requirements that have exceeded the part cap alert level
for a specific visit. The Alert Level will be stored in a Maintenix in the Account Code. The Contract
Specific Part and Alert Level will also be stored as an attachment on the Work Package, and will be used
as input parameter for the report.

Control of Purchasing of Parts


When a part is required for a visit and the part is not available, the part will need to be purchased
(Borrows, Exchanges and Purchases all fall into this category).
The purchasing department should have access to the following information when they are about to
purchase a part:
o

o
o
o

The Part and Tool provisioning appendix of the contract, as defined in Part and Tool
Provisioning Appendix section. The key information the purchasing department will
retrieve from the appendix are:
 Did the customer agree to provide this part?
 Are part costs defined on the Job Card or Requirement Level?
 Are parts invoiced as single item or line item?
The sum of the parts and tools reserved or consumed by the task. A customer report, will
be the primary tool for this activity.
When the part is required
All alternates which are applicable

There are three basic scenarios here:


1) The Part is MRO stocked and is MRO supplied.
2) The Part is not MRO stocked and is MRO supplied.
3) The part is not MRO stocked and is not MRO supplied.
For each scenario, the Materials Controller & the Purchasing department will perform the following
activities:
Page 82
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

MRO Stocked / MRO Supplied


1) Materials Controller will review the Contract, identify that this part is a MRO supplied and MRO
stocked part, and the part is currently unavailable.
2) Materials Controller will review the total part cost that have been used or reserved against the
task.
3) Materials Controller will identify when the part is required.
4) Materials Controller will compare the cost of the part (MSRP) vs. the cap. This calculation will
include the contract agreement of having the part cap on the requirement or job card level, as
well as if the parts are invoiced on a single item or line item basis.
5) Materials Controller will identify if there is a replenishment purchase order already in progress
that can be expedited. Identify if a bulk purchase is an option (to get a bulk discount) without
affecting delivery time.
6) If cost (without new part) is over cap, contact customer support for claiming approval unless
already done. If cost with the new part is over cap, contact the customer support for claiming
approval.
7) If customer approval is granted, purchase part (purchasing will include getting RFQ). Additional
parts may be purchased at the same time, as this part is normally supplied by MRO.
8) If customer approval is not granted, proceed accordingly (customer will be charged for expenses
incurred to this point, including part and tool costs).
9) If part cannot be acquired in time, the purchasing officer will notify materials controller that MRO
cant provide, and materials controller will negotiate with customer the options available
(customer to provide or cancel task).

Not MRO Stocked / MRO Supplied


1) Materials Controller will review the Contract, identify that this part is a MRO supplied and not a
MRO stocked part.
2) Materials Controller will review the total part cost that have been used or reserved against the
task.
3) Materials Controller will identify the part is required.
4) Materials Controller will compare the cost of the part (MSRP) vs. the cap. This calculation will
include the contract agreement of having the part cap on the requirement or job card level, as
well as if the parts are invoiced on a single item or line item basis.
5) Get quote for part. Check alternate costs if applicable to get lowest price.
6) If cost (without new part) is over cap, contact customer support for claiming approval unless
already done. If cost with the new component is over cap, contact the customer support for
claiming approval.
7) If customer approval is granted, purchase part for this task
8) If customer approval is not granted, proceed accordingly (customer will be charged for expenses
incurred to this point, including part and tool costs).

Not MRO Stocked / Not MRO Supplied


1) Materials Controller will review the Contract, identify that this part is not a MRO supplied and not
a MRO stocked part.
2) Materials Controller will send part request to Purchasing Officer
3) Purchasing Officer will get quote for component. Check alternate costs if applicable to get lowest
price.
4) Purchasing Officer will contact customer support for claiming approval.
5) If customer approval is granted, purchase part for this task.
6) If customer approval is not granted, proceed accordingly (customer will be charged for expenses
incurred to this point, including part and tool costs).
Page 83
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Assumptions
-

If a task or corrective action requires multiple customer signatures (due to additional problems
found during the execution of the task), MRO will manually track if an additional customer
signature is required, via the attachments that are stored against the task.

When MRO has a contract that states that a certain tool will be borrowed to complete a task, and
the customer will pay for the appropriate amount of the borrow cost, MRO doesnt need to use the
borrowed tool to perform the task.

It is assumed that MRO will train the Billing Department to support the new invoicing process. As
the new Invoicing Solution will move the Billing Departments work from after the work is complete
to a day-to-day monitoring throughout the execution of the work package.

Each visit has a separate account code. This account code will not be reused. The account code
will include the part cap for all tasks with a cap in the visit, and will include the alert cap.

Part and Tool Provisioning Appendix


Every Aircraft and Part Maintenance contract signed by MRO will have a Part and Tool Provisioning
Appendix. This appendix will have a standard format.
-

This appendix, based on the original contract, clearly defines the provisioning agreement for all
rotable parts and special tools that are known to be needed on the work package. Consumables
and Expendables may be indicated in a single line supplied by MRO or supplied by the Client.

If the visit has approved AWRs, the attachment may be updated, or new attachments may be
added (preferred).

The Appendix will be stored in Maintenix (attached to the Work Package), and will be freely
available throughout MRO.

The Appendix will be updated or amended when extra parts and tools are approved by the client,
or if the provisioning strategy is changed.

The Appendix will identify the Alert Levels for the work package.

The Appendix will identify if Part and Tool costs are defined on a Requirement or Job Card level.
That is, if the part cap is defined on the Requirement level, the part and tool costs of all of the
routine (scheduled) job cards and non-routine (non-scheduled) job cards will be totaled, and
compared to the part cap. If the part cap is defined on a Job Card Level, each of the job cards
associated with a particular requirement will have a individual part and tool cap limit (it will be the
same for all job cards under a single requirement).

The Appendix is not expected to identify the serial or batch numbers of parts being provided
(directly or indirectly) by the client

Page 84
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Appendix C

Mxi Technologies
Maintenix Version v6.8.13 SP2

Identification of MRSP and Vendor Prices

The Invoicing Solution will identify the difference between the Sale Price (the MSRP) and the Purchase
Price (the Vendors Sale Price). This distinction must be made in a way that is easily understood by the
users, and is consistent enough to be supported by the Auditing and Invoicing reports.
The method by which the MRO will identify the MSRP will be as follows.

Figure 20 - Identification of MSRP and Vendor Prices

The solution will include the creation of a new 'MSRP' vendor, which identifies the MSRP price for a part.
This vendor will often be the same organization as the original manufacturer of the part, but Maintenix will
contain two entries for the organization. This allows the MSRP price to be identified, as well as the actual
price it costs the MRO to purchase items from the vendor (including bulk discounts, for example). In
Figure 20, Honeywell is the original manufacturer, and appears twice once as a MSRP vendor, the
other as a purchase vendor.
Using the Maintenix Part to Vendor Relationship, the logical flow information is inward for purchases, and
outward for MSRPs.
The following sections describe the elements of Figure 20 in detail.

CONFIGURATION
This section identifies the Part to Manufacturer relationship. This relationship uniquely identifies a part in
the Maintenix configuration.

Page 85
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

SELLING PARTS
This is the data profile for identifying the MSRP price. There will be a maximum of one MSRP vendor
associated with a part. The MSRP vendor will never be approved.

BUYING PARTS
This is the data profile for identifying the Purchase price from vendors. There can be many Purchase
vendors associated with a part.

REPAIRING PARTS
This is the data profile for identifying the Repair price from vendors. There can be many Repair vendors
associated with a part, but in the MRO solution, most will have a single Repair vendor.

EXCHANGING PARTS
This is the data profile for identifying the Exchange price from vendors. There can be many Exchange
vendors associated with a part, but in the MRO solution, most will have a single Exchange vendor.

PRICE
This optional field identifies the current price of this part for the specified service, as identified by the
Vendor Type. This field should always be completed.

VENDOR PART NUMBER


This optional field identifies the vendor part number. This field is used when the vendor sells the same
physical component under a new label/part number. This field will never be used for MSRP vendors, and
is not required for the OEM.
Note: Figure 20 assumes that Honeywell is the manufacturer of the part.

VENDOR
This field identifies the vendor. This is a link to the Vendor record in Maintenix. If the Vendor is type
MSRP, the vendor name should be <MSRP + Vendor Name>.

TYPE
This field, an attribute of the vendor, identifies the type of vendor.

Appendix D

Shop Controllers Report

The Shop Controller needs to be able to identify the work that needs to be done in the shop. Specifically,
the shop controller should be able to identify:
-

Work that is being delayed due to missing parts


Work that is being delayed due to missing tools
Work that is being delayed due to labour shortages
Work that is being delayed due to missing customer approvals
The scheduled (contracted) due date for all work

With this information, the shop controller will be able to identify what work should be done in the shop.
The following report or configurable status board will be developed:
Table 2 - Shop Controller's Report
Serial
Number
(Part
Number

Owner

Work Package
Name

Priority

Workpack
age Status

Customer
Approval

Multiple
Certificates

Scheduled
End Date

Return
Date

Page 86
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

)
2345
(3443)
2475
(6643)
345-983
(753245
)

On-Time
Airlines
Westjet
Tango

Fuel Pump
Overhaul - 39838
Fuel Pump
Overhaul - 98456
Fuel Pump
Overhaul - 45674

Expedit
ed

In Work

Approved

No

Planned

Pending

No

Complete

Rejected

Yes

2011-Dec10
2011-Dec11
2011-Dec13

2011Dec-12
2011Dec-15
2011Dec-19

Note: When running the report, the shop controller will select the shop or shops. The report will show all
parts that are currently at the location(s) specified.
Serial Number (Part Number): The part number and serial number of the component.
Owner: The owner of the component.
Work Package Name: The name of the work package. The name should include the name of the item
and the contract number.
Priority: The priority of the work package, defined as Work Types:
-

Expedited: Expedited priority

Workpackage Status: The current status of the work package:


-

None: No associated work package.


Planned: The work package has not been started. If the scheduled start date is in the past, this
will appear in Red and Bold.
Complete: The work package is complete.
Awaiting Tools: The work package is in work, but it has been delayed with a reason of AWT
(Awaiting Tools).
Awaiting Parts: The work package is in work, but it has been delayed with a reason of AWP
(Awaiting Parts).
Awaiting Labour: The work package is in work, but it has been delayed with a reason of AWL
(Awaiting Labour).
Awaiting Customer Approval: At least one customer signature line has not been signed.
In Work: The work package is in work.

Customer Approval: Identifies the status of the customer signature line.


-

None: No customer signature line.


Approved: All customer signature lines have been signed.
Pending: At least one customer signature line has not been signed.
Rejected: At least one customer signature line has not been signed, the work package is
complete and the part is not serviceable.

Multiple Certificates: Identifies if multiple certificates are required for the component.
Scheduled End Date: Identifies The scheduled end date of the work package. If the scheduled end date
is later than the return date, this will appear in Red and Bold.
Return Date: The date when the component is scheduled to be shipped back to the client.
information is retrieved from the Ship By Date from the outbound shipment.

Appendix E

This

Ordered Task Card Cover Pages

Description

Page 87
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

The purpose of the Ordered Task Card Cover Pages report is to allow the MRO to control the order in
which the task card cover pages will be printed.
This report will always be run in the context of a single work package.
This report will generate the task card cover pages for all of the JICs and ADHOCs in the work package,
ordered by the Task Barcode (i.e. T0002FU0). Task Barcode will always be unique, but may not be
consecutive.
This report has a simple cover page which will be the first page in the report to allow users to identify the
purpose of the print job. The key data in this header section is the Printed On date.
Assumptions
An MRO work package may have 1500 JICs and ADHOCs.
In the MRO solution, workpackages will be loaded using the EMA. This process allows the MRO to
define the order of the Task Barcodes.
If this report is adopted, the Print All Task Cards button will be removed from all users.
At time of printing, work packages will not contain faults
Context / Configuration
This report will be available in drop-down menus.
This report will be visible when the user is on the Work Package Details page. This report will not be run
on shop work packages.
This report will use the work package context automatically when the report is launched no
configuration page will be used.
This report will be generated and stored in PDF format. It will not be available in excel.
Design
Header Section
WorkPackage Name: The name of the work package
Work Location: The work location for the work package.
Start Time: The scheduled start time for the work package. If the MRO expects this report to be run after
the work package has started, this can field show the actual start time if present.
End Time: The scheduled end time for the work package.
Number of JICs and ADHOCs: The number of JICs and AD-HOC tasks in the work package.
Report Generation Time: The date and time the report was generated.
Report Body
The following diagram shows how the report will look when compiled. The header will be as above, and
the body of this report will be made up of the task card cover pages from the tasks in the work package.

Page 88
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

Figure 21 - Ordered Task Card Cover Page

Page 89
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.

Modeling Standards
MRO Standard Solution

Mxi Technologies
Maintenix Version v6.8.13 SP2

General Disclaimer Notice and Government End User Notice:


Information contained in this document is for references purposes only. While all information and/or
comparisons provided are correct to the best of our knowledge at publication, they may contain errors
and are subject to change without notice. Information is provided "as is" without any warranties or
conditions. Mxi assumes no liability and expressly disclaims liability for errors and/or omissions, or
associated costs, losses, claims or damages of any kind, which may result from use or reliance upon
such information.
Mxi, the Mxi logo, Maintenix and other product names are the trademarks or registered trademarks of Mxi
Technologies Ltd. Other company names and trademarks are the property of their respective owners.
This document was developed exclusively at private expense, is a trade secret of Mxi for all purposes of
the Freedom of Information Act or its successor legislation or any other disclosure statute, regulation or
provision; is commercial computer software and/or "restricted computer software" subject to limited
utilization (Restricted Rights); and shall remain proprietary to Mxi or its licensors. Use, duplication or
disclosure by the U.S. Government or any person or entity acting on its behalf is subject to Restricted
Rights and all applicable restrictions for software developed exclusively at private expense as set forth in:
(a) for the DoD, the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013
and/or 252.227-7014, or any successor clauses, and (b) for all government agencies, the Commercial
Computer Software - Restricted Rights clause at FAR 52.227-19 or any successor clause. The U.S.
Government must refrain from changing or removing any insignia or lettering from this document or from
producing copies of document (except one copy of for backup purposes).

Page 90
Mxi Confidential Information. 2011 Mxi Technologies Ltd. All Rights Reserved. THIS DOCUMENT MAY NOT BE COPIED,
OR TRANSMITTED OR TRANSFERRED OUTSIDE OF THE FACILITY TO WHICH IT WAS PROVIDED, OR TO PERSONS
OTHER THAT THOSE TO WHOM IT WAS ORIGINALLY PROVIDED.