OASES Functions and Features Version 6.0 PDF

Maintenance & Engineering Software
Functions & Features Overview

1
Communications Software (Airline Systems) Limited - Copyright © 2016
OASES Maintenance & Engineering System
Functions and Features Overview
DISCLAIMER
© 2016 Communications Software (Airline Systems) Limited. All rights reserved. All trademarks acknowledged
This document is published by Communications Software (Airline Systems) Limited without any warranty. No
part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical,
for any reason without the written permission of Communications Software (Airline Systems) Limited
2
3
Contents
Contents ..................................................................................................................................................................... 4
OASES SYSTEM OVERVIEW ..................................................................................................................................... 11
OASES CORE ............................................................................................................................................................ 12
Information Technology Environment ................................................................................................................. 12
User Interface Features ....................................................................................................................................... 13
Table Exports to Excel® ...................................................................................................................................... 13
Date Entry formats ............................................................................................................................................... 14
Absolute dates ................................................................................................................................................. 14
Relative dates .................................................................................................................................................. 15
Text Entry Memory Feature (“The Squirrel”) ........................................................................................................ 15
The Help System .................................................................................................................................................. 16
CONTINUED AIRWORTHINESS................................................................................................................................. 18
Introduction ......................................................................................................................................................... 18
Data Import and Management ............................................................................................................................. 18
Aircraft Configuration and Build .......................................................................................................................... 19
Component and Assembly Control ...................................................................................................................... 19
Task Card Management ....................................................................................................................................... 20
Packaging Tasks .................................................................................................................................................. 22
Managing the AMP and Revisions ....................................................................................................................... 22
AD/SB and EO Control and Revision .................................................................................................................... 23
Frequency ........................................................................................................................................................ 24
Effectivity ........................................................................................................................................................ 25
4
Workflow Assignment .......................................................................................................................................... 25
EASA Automatic Download .................................................................................................................................. 26
Attachments ........................................................................................................................................................ 26
Tech-Log Manager ............................................................................................................................................... 26
Electronic Operations Systems Feeds ............................................................................................................. 26
Entering Tech-logs........................................................................................................................................... 26
Deferring Defects............................................................................................................................................. 28
Non-ship Based Lives (NSBL) .............................................................................................................................. 29
Repetitive Defect Alerting .................................................................................................................................... 29
System Monitoring............................................................................................................................................... 30
Automatic Reliability Reporting ........................................................................................................................... 31
PLANNING ................................................................................................................................................................ 32
Task Card Database ............................................................................................................................................. 32
Package Analysis ................................................................................................................................................. 34
Forecasting .......................................................................................................................................................... 35
Component Forecasting - Life Limited Parts (LLPs) ........................................................................................... 36
Graphical Planning Tool ....................................................................................................................................... 36
PRODUCTION ........................................................................................................................................................... 38
Introduction ......................................................................................................................................................... 38
Resource Planning ............................................................................................................................................... 38
Shift Planning .................................................................................................................................................. 38
Hangar Planning .............................................................................................................................................. 40
Creating Shop Floor Employee Accounts ........................................................................................................ 41
The Maintenance Workbench .............................................................................................................................. 41
5
Booking on to Multiple Tasks .............................................................................................................................. 43
Recording Defects ............................................................................................................................................... 43
Structural Damage Report ................................................................................................................................... 44
Booking off .......................................................................................................................................................... 44
Electronic Sign-off ............................................................................................................................................... 44
Tracking Work in Progress ................................................................................................................................... 45
Tooling Control .................................................................................................................................................... 46
Standard Tool Control .......................................................................................................................................... 47
RFID Tooling Control ............................................................................................................................................ 47
Closing a Works Order.......................................................................................................................................... 50
Reports ................................................................................................................................................................ 51
LINE MAINTENANCE CONTROL ............................................................................................................................... 52
Overview .............................................................................................................................................................. 52
Integration with Operations ................................................................................................................................. 53
Integration with Inventory Database ................................................................................................................... 53
Integration with Technical Records and Planning Data ...................................................................................... 53
LMC Email Database ............................................................................................................................................ 54
Minimum Equipment List ..................................................................................................................................... 54
Creating and Editing ADD Categories .................................................................................................................. 55
Entering Defects .............................................................................................................................................. 55
Entering Extensions ......................................................................................................................................... 56
ADD Status Report........................................................................................................................................... 57
Planning Line Maintenance ................................................................................................................................. 57
Raising a Works Order ..................................................................................................................................... 57
6
LMC Dashboard ............................................................................................................................................... 58
Line Maintenance Material Requirements ........................................................................................................... 60
Updating OASES with Line Maintenance Accomplishment Data ......................................................................... 60
Overview .............................................................................................................................................................. 62
Quotations ........................................................................................................................................................... 62
Purchasing ........................................................................................................................................................... 62
Stock Control ....................................................................................................................................................... 63
Shortage control .................................................................................................................................................. 63
Part Enquiries ...................................................................................................................................................... 64
Batch & Serial Traceability .................................................................................................................................. 65
Loan Control......................................................................................................................................................... 65
Cores ‘due in’ ........................................................................................................................................................ 66
Vendor Management KPIs ................................................................................................................................... 66
Overview .............................................................................................................................................................. 68
Warranty Agreements .......................................................................................................................................... 69
Warranty Tracking ............................................................................................................................................... 69
Warranty Administration...................................................................................................................................... 70
Warranty Reporting.............................................................................................................................................. 70
COMMERCIAL MODULE ............................................................................................................................................ 71
Invoicing Work Bench .......................................................................................................................................... 72
Tasks and Actions Pane ...................................................................................................................................... 73
Customers and Contracts .................................................................................................................................... 74
Customer Quotes Module .................................................................................................................................... 75
Warranty .............................................................................................................................................................. 75
7
Decision Support.................................................................................................................................................. 76
Fixed Price Agreements................................................................................................................................... 77
End to End Process .............................................................................................................................................. 77
Invoicing Pane ..................................................................................................................................................... 77
Shipping Charges ................................................................................................................................................. 78
REPORTING AND EXPORTING DATA ....................................................................................................................... 80
Reporting ............................................................................................................................................................. 80
Print Reports ........................................................................................................................................................ 80
Exports ................................................................................................................................................................. 81
Database Views ................................................................................................................................................... 82
8
9
System Overview
Figure 1: OASES modules description
10
OASES SYSTEM OVERVIEW
The OASES Maintenance & Engineering system is designed and produced by Communications Software (Airline
Systems) Limited, trading as Commsoft. It is a fully integrated solution, which covers the full spectrum of
activities required by airlines, Maintenance & Repair Organisations (MRO), Continuing Airworthiness Management
Organisations (CAMOs) and spare part stockists.
The solution is designed for use in all the engineering and commercial functions as a single specialist solution.
The illustration on page 7 shows the broad coverage of OASES application across the business.
System Overview
11
OASES CORE
The OASES core module is the ‘backbone’ of the system and is required in all installations of OASES
OASES Core Module

Information Technology Environment
The OASES application runs in a Linux environment and can either be installed locally on a host server or can be
accessed remotely through the Commsoft hosted private cloud, ands accessed anywhere in the world through a
secure Windows® RDP connection.
The application is linked to an industry standard Oracle® database. The use of this type of database allows the
customer to access the data with the aid of the data dictionary if they wish. The data dictionary details a large
number of table views which are available for interrogation using third party reporting packages or bespoke
programs
Individual users can access the application through a client PC connected to the server over a network or via a
Citrix client if required.
Commsoft also has a mobile application which can be used any device which supports HTML5 browsing and
allows limited access to data ‘in the field’ away from the normal desktop access.
12
User Interface Features

OASES Core Module
Figure 2: The main OASES navigator window showing the 'favourites' menu created by the system
The design of the OASES interface is intuitive and easy to learn. This helps users get the most from the system
with the minimum amount of training being required. The application uses a ‘work-bench philosophy for many of
the main system functions reducing the number of screens required for a variety of routine tasks. The starting
point for all transactions is the OASES main navigator screen, which is customisable by the user.
The application automatically creates a ‘favourites’ menu for the user based on their individual use of the
system. The system also allows the user to customise their favourites list by adding options to the list manually.
Users can also customise their screen views based on their individual needs by re-ordering or hiding any
column/s in a table and saving these settings.
Table Exports to Excel®
A user can also export data from any table in the application to an Excel® spreadsheet with a simple right click
command. This will open a drop down menu from where you can choose an number of options for exporting date
from the system
13
OASES Core Module

Figure 3: A 'right click' on any table will automatically launch Microsoft Excel and export the table into the application.
Date Entry formats
Dates may be entered into OASES in a variety of formats to make it as easy and quick as possible.
Absolute dates
For example entering either: 02/06, 0206, 2/jun, 2jun, 02jun
Would all select the 2nd of June of the current year
Entering either: 06/08/xx, 06/08/20xx, 0608xx, 060820xx, 6augxx 6aug20xx, 06augxx or 06aug20xx
Would all select the 6th August of the year 20xx
14
Figure 4: In this example entering 26042013 give the date 26th April 2013
Relative dates
A date can also be entered relative to todays’ date.
For example:
 Entering “T” would give today’s date

OASES Core Module
 Entering T+3 would select the date three days in the future
 Entering T-3 would select the date three days ago
 Entering T+3M would select the date in 3 months’ time
 Entering T–2W would select the date 2 weeks ago
Figure 5: In this example of a relative date entry T+3 will give the date three days in the future
Text Entry Memory Feature (“The Squirrel”)
Text which is entered into a dialogue box on the system is automatically memorised by the system. If the user
then right clicks on the dialogue box for a second time, a list of previous entries and that have been used that day
in the system will be displayed and can be selected.
15
This is extremely useful if you are using long part numbers or repeatedly use the same entries in different areas
of the system.
OASES Core Module

Figure 6: The text entry memory (or squirrel) feature memorises recent entries for re-use
The Help System
The OASES Help Function provides information to assist the user in all areas of the system. It is a browser based
system which can be accessed directly from the application. There is a list of contents and an index, as well as a
built in search function, which assists the users in finding the relevant help for the topic they are researching.
There is also a full glossary of terms used in the application.
16
OASES Core Module
Figure 7: The built in OASES Help System is a browser based facility
17
CONTINUED AIRWORTHINESS
Introduction
All aviation organisations are required to comply with the regulatory requirements which govern their operations.
A fundamental requirement of these regulations is to maintain continued airworthiness through the monitoring
of maintenance activities and operational reliability
OASES provides the basis for ensuring that this can be carried out through the control and recording of these
activities
Data Import and Management Continued Airworthiness
Through the use of a number of tools, OASES allows for the import of data from a variety systems and in a variety
of formats. The system can also import data from propriety file formats such as Excel. This greatly reduces the
need to manually enter data into the system when initially starting to populate it and therefore greatly reduces
both the cost and time required to implement OASES.
Commsoft will also project manage the data transfer on behalf of our clients to ensure that the transition from
the current method of working to being operational with OASES is not put at risk by the use of third party
contractors who are outside of the control of either the airline or Commsoft.
Option DI01 is used to import various types of data into OASES through the use of standard Excel® spreadsheet
imports. Commsoft will provide a set of data templates to allow the import of data to be greatly simplified.
18
Continued Airworthiness
Figure 8: Option DI01 is used to import data from Excel spreadsheets, which are formatted using Commsoft templates
Aircraft Configuration and Build
Commsoft has a large number of ‘aircraft skeleton builds’ covering most popular types and these can be used as
the basis for constructing the full aircraft configuration within the system covering components and assemblies.
These then hold details of all parts fitted and the serial numbers if they are rotable parts. The aircraft
configurations hold the location details to eight ATA identifier level.
The aircraft skeleton can be easily modified to reflect differing configurations within a fleet and easily replicated
if a new aircraft is taken in the fleet
Component and Assembly Control
Component part numbers and serials numbers are held for all identified positions and any empty positions are
assumed to be as fitted from new. If a part is changed into an empty position it will be updated with the relevant
data and this will then be stored for this location.
The system maintains full traceability and only recognised part numbers and serial numbers can be ‘fitted’ to the
aircraft. This ensures that the aircraft build integrity is maintained and no unauthorised parts can be fitted to the
19
aircraft. Alternative parts (where approved) can be used and this information is readily visible in the system to
assist maintenance and inventory staff in meeting demands for parts.
The system fully understands and manages the concept of assemblies and these can be easily built and then
maintained. If an assembly is removed from an aircraft only a single transaction is required within the system to
remove it and all the component parts from the aircraft record. The same is true for the fitting of a new
assembly. This greatly reduces the time and effort required to maintain an accurate record of the aircraft build
status and also reduces the chance of errors occurring due to multiple transactions being required to remove or
install an assembly and its component parts.
Task Card Management
Figure 9: Option WC11 is used to set up task card details
Each task which needs to be accomplished as part of the Approved Maintenance Plan (AMP) for the aircraft is
held in the system under a unique Workcard reference. Information relating to the task is entered into a form
(Option WC11). The effectivity of the workcard can be defined down to sub fleet or individual aircraft tail number
level.
Data which can be associated with the task includes:
 Maintenance Schedule reference

 Description
20
 Zone and sub zone

 Threshold and interval
 Trade
 Number of men required
 Labour hours
 Inspection man hours
 Manufacturers job instruction card number
 Access Panel information
 Revision date
Figure 10: A standard OASES workcard
All materials which are required to accomplish the task can be entered and held in the system and this data can
then be used to pre-load the material each time the card is called up during maintenance.
This pre-load can be automatically transmitted to the relevant warehouse which is associated with the aircraft’s
home base where maintenance is normally performed or to the work station associated with the work order, for
example where a major check is being performed at an MRO.
21
Any documents which are associated with the task such as health and safety data, company procedures or OEM
job instructions can be attached to the workcard record and can then be automatically printed as part of the
check pack. Tally sheets and panel opening and closing cards can also be produced automatically
Packaging Tasks
Once a workcard has been created it can be included as part of a maintenance package. Each task carries its
individual controls and the package is called according to the first-due of any task within it. Once included in a
package, each time the package is included in a works order the card will be included and all the relevant
information will be included and printed as part of the check pack and the material pre-load will also be initiated.
Managing the AMP and Revisions
Once the AMP has been established and made live the tasks will become due according to the hours and cycles
or calendar time set in the workcard. To cater for revisions to the AMP OASES allows you to create an
unapproved version of the AMP whilst at the same time continuing to use the live AMP for all on-going
maintenance planning and forecasting.
An unapproved revision to the AMP can be created by copying the live AMP or any other previous version. The
work cards in the unapproved revision can then be updated, deleted or added to, in order to create the revised
plan.
Whilst the unapproved plan is being worked on it is de-noted to staff that they are working on an unapproved
plan by means of a coloured box being displayed around the AMP revision reference box. The revised plan, once
completed, can be printed in its entirety or just the changes to the AMP can be printed in order for it to be sent to
the relevant authority for approval.
Once the changes have been approved and the decision is made to use this new AMP as the definitive
maintenance plan, it can be made live by a correctly authorised member of staff with a single click of a button.
22
Figure 11: Creating a new revision (the colour de-noting the revision can be selected from a palette)
The old AMP is then archived and cannot be used for operational maintenance purposes from that point
onwards. Any amended tasks which have been called into a works order under the old AMP are highlighted by
the system for review.
AD/SB and EO Control and Revision
The system controls all Airworthiness Directives (AD), Service Bulletins (SB), Engineering Orders (EO) Service
Information Letters (SIL) or any other unscheduled work package that the operator may wish to control.
Accomplishment categories for the work to be controlled can be picked from the drop down list or specific ones
can be created by the user as required. The standard categories provided are as follows:
 Discretionary
 Mandatory
 Optional
 Recommended
The type of work to be controlled can be picked from the drop down list provided. Users can also create their
own categories if they wish. The standard categories are:
 Airworthiness Directive
 Emergency Airworthiness Directive
 Proposed Airworthiness Directive
 Service Bulletin
 Service Information Letter
23
Figure 12: Setting up an AD/SB and inputting basic information
Once the basic data for the task have been completed the detailed information can be added by use of the
additional tabs which are located on the same window.
Frequency
The frequency information can be added for the record according to the specific requirements of the task.
Multiple stages can be added with different intervals if required.
24
Figure 13: Entering Frequency data for a task
The frequency for a task can be set differently for multiple fleets or sub fleets, which allows the same basic
record to control the all of the operator’s aircraft.
Effectivity
The effectivity of the task can be set for either a component or aircraft. It can be auto-allocated for an aircraft
fleet if appropriate, or it can be set at sub fleet or individual aircraft level. If the task is not applicable for a given
aircraft this can be recorded and a reason selected.
v
Figure 14: The effectivity can be set in this case for an aircraft fleet
Workflow Assignment
A workflow can be assigned to a task and this will send email messages to the nominated individuals asking
them to review the item. The system will chase them if no response is forthcoming within a nominated number
of days. Multiple workflows can be set up and assigned as appropriate according to either the fleet concerned or
the type of task being handled
25
Figure 15: Option RC01 allows for multiple workflows to be created for tasks
EASA Automatic Download
OASES can be set-up to automatically download the latest AD information from the EASA website. This includes
both newly published and revised data. This facility also provides an audit trail to show compliance with AD
tracking.
Attachments
Attachments can be added to any task and these can include test documents, digital photographs or scans. If an
AD has been downloaded from the EASA website the official document will be already be attached to the record.
Tech-Log Manager
Introduction
In order to record information relating to the aircraft hours, cycles, fluid uplifts, defects and component changes
information is entered from the tech-log sheets into OASES. This is accomplished using the Tech Log Manager
(option LE33)
Electronic Operations Systems Feeds
The manager can be automatically fed with data from an electronic operations feed to provide information such
as flight and block times, flight numbers etc. If an electronic tech-log (ETL) system is being used then this can
automatically feed additional data such as fluid uplifts, deferred defects and defect rectifications.
If the electronic operations system has the capability to accept a feed from OASES then information regarding
scheduled maintenance periods can be passed to the operations system making it visible to anyone viewing the
fleet status in that system.
Entering Tech-logs
If the sector data is being automatically created in OASES by an operations system feed then the process of
entering tech-logs is simplified as only the additional information regarding defects or component changes and
fluid uplifts needs to be added. If an electronic feed is not being used then each sector needs to be created from
the tech-log page information. This can be simply accomplished by using the tech-log manager.
26
Figure 16: Creating a new sector in Option LE33 and recording the sector details
If the sector information has already been imported from an electronic information source or you wish to update
a sector which has already been created, then a list of the sectors can be displayed and the relevant sector
highlighted and double clicked. This allows the sector data to be displayed and edited as required.
Figure 17: The Tech-log manager records and updates details relating to a sector including defects
If a component change is associated with the defect, then this information can be entered by clicking on the
component change tab. The parts on and off details are then entered and saved to update the aircraft record.
27
The same option can also be used to record any maintenance accomplishments against the incoming tech-log
page. This resets these tasks in the database and records the details of the maintenance carried out.
Deferring Defects
Defects which are raised can be deferred either against a user definable set of categories or against the MEL. An
electronic MEL can be loaded into OASES and used for this purpose. Once the defect has been entered and an
ATA chapter selected, any possible MEL items will be shown for that chapter and can then be selected and used
to defer the defect.
Once defects have been deferred then they can be managed using the carried forward defects reports, which
show the status of all deferred defects on a particular aircraft. This report is accessed by drilling down on an
aircraft in the LM02 Line Maintenance dashboard or by launching the LE50 report.
The report shows all the details associated with a defect and the material status of any parts requisitioned for
the repair. Defects for which parts are available can be easily identified and the planners can schedule the work
during a night-stop or transit stop to rectify and clear the defect.
Figure 18: LE50 Carried Forward Defect report giving details of CFDs on an aircraft
28
Non-ship Based Lives (NSBL)
Certain components on an aircraft may not be controlled in the same way that most components or airframe
items are, i.e. by airframe hours and cycles. A typical example is the APU on an aircraft which may have its own
‘clock’ which records APU hours. In this case OASES can be set up to count these lives separately from the
airframe hours and cycles. This concept is called non-ship-based life (NSBL).
The components to be controlled in this way can be set up in option LE04 and their individual life codes defined.
This allows engines with different power ratings to have different lives according to the actual power rating used
on a particular sector. It also allows APUs, firefighting aircraft with ‘scoop cycles’ and any other unusual
operational characteristics to have their operating data defined and then tracked in OASES.
Once the components are set up in this way then the data related to these items is recorded in the normal way
when entering data in the LE33 tech-log manager. As an example when recording a sector, the engine power
rating is selected if different from the default power rating to record a different engine power setting.
Figure 19: Non-ship based lives are defined in option LE04
Repetitive Defect Alerting
Defect alert levels can be set up in the system against ATA chapters and if the number of defects in a period
exceeds these levels then a system alert is raised. The system can also manage investigations into these alerts
so that they are reported on and a full history is generated.
29
Figure 20: Illustration of the Repetitive Defect workbench
System Monitoring
The systems monitoring functionality in OASES monitors system’s health by analysing technical measurements
and uplifts that are recorded in the system as part of the routine data capture activities either from technical log
or mechanic’s inspections.
The system can monitor such things as oil usage, hydraulic fluid usage and tyre pressures. The user can set up
rules and alerts in the system to monitor the parameters that they wish analyse. As data is entered in the system
as part of the routine activities, the system monitors the readings and compares them against the pre-defined
alert levels and raises alerts if the laid down parameters are exceeded.
If any alerts are registered they can be analysed in the graphical analysis charts which the system automatically
generates
Figure 21 Example of automatically generated graphical analysis of fluid usage
30
Automatic Reliability Reporting
OASES gathers information relating to all aspects of the maintenance operations and uses this information to
automatically generate, in real time, a full reliability report for any fleet.
The reliability report can be generated at any time and is fully up-to-date meaning that there is no ‘lag’ between
what is being reported on and what is happening in the fleet at the time the report is presented.
This facility generally saves large amounts of labour resource which would otherwise be consumed in generating
these reports which would also be out-of-date when completed, due to the time taken to complete them.
The system produces a report covering both the fleet statistics such as utilisation and fleet dispatch reliability as
well as detailed analysis of individual ATA chapters, squawks/defects and by PIREP/MAREP
The reports can be tailored to the individual airlines needs by including or excluding any chapter or sections
using the tick box selection option in the report generator. In addition, customised comments can be entered
against certain sections of the reports.
The reports are fully illustrated with line graphs, bar charts and pie charts as appropriate, and are multi-coloured
to make them easy to read and understand.
Figure 22: A page from a typical fleet reliability and utilisation report automatically generated by OASES
31
PLANNING
An important aspect of any MRO IT system is to plan the scheduled maintenance activities in accordance with
the Maintenance Plan and the life and overhaul limits of the components.
Planning
OASES achieves this by holding all the relevant data and using it to provide informative forecasts of when
maintenance should be carried out and also allowing the planners to see how efficient their plans are.
Task Card Database
Central to the planning function is the Task card database which holds all the tasks which need to be
accomplished in order to comply with the approved maintenance plan for the aircraft. The Task Card Database is
managed through option WC11 and each task is given a unique reference by the system and within this record all
the details relating to the task are held. This includes basic data such as the zone, trade, labour and inspection
hours, plus other data such as whether it is ETOPS critical.
In addition to this a great deal of further information can be recorded against the task. The effectivity can be set
at various levels including fleet, sub fleet and even tail number level.
Any access panels which have to be opened can be associated with the task and the relevant details will then be
taken into account during planning stage, including the additional labour time and also the production of the
associated panel opening and closing card.
32
Planning
Figure 23: Figure 21: Creating or editing a Taskcard in option WC11
Any materials that are required to carry out the task can also be included in the record and this can then be set to
auto-requisition so that if the card is called up in a works-order the relevant materials will be pre-loaded.
Any documents which relate to the task such as OEM task instructions can be associated with the record and
printed when it is included in a work order along with any other local instructions which have been attached as
well.
A task can be set up as an airframe or component task for rotable units. The interval can then be set so that the
task is called up based on hours, cycles or calendar limits and complex relationships can also be set so that the
task is not called if another task is included or another task supersedes it.
With all the data regarding Rotable, Airframe and modification requirements now held in the system all the
maintenance can be forecasted.
Packaging
Most operators will have a maintenance plan that packages the individual tasks into larger checks. These checks
can be created in OASES using the Create/edit package tool (WC13). It is extremely simple to edit a pack by
adding or deleting cards or to create an entirely new check package in the same way.
Once the pack is created it can be made active and the pack will then be called in as maintenance forecast based
on the most restrictive card within the pack. It can be added to a works order with a single click and the entire
33
pack and all its components will be produced and printed or emailed for the maintenance organisation to use to
complete the work.
Figure 24: An example of a Check pack created using option WC13
Planning
Package Analysis
Once a package has been created a package analysis can be carried visually at any time to see the actual due
dates compared to the planned date of the works order. This is presented graphically in a window showing each
task with its details and when it is due compared to the planned date.
Figure 25: The package analysis tools shows when tasks are actually due compared to the planned date within a package
34
Forecasting
Planners need to be able to see the maintenance that is required on the fleet in the future based on expected
flying programme. OASES allows operators to create multiple flying programmes for each fleet and use these to
forecast when maintenance will be due. The forecast tools can then be used to plan the maintenance based on
these programmes. If an aircraft flying programme is changed the forecast can very quickly be re-run to see the
effect this will have
Option TF52 allows you to create a works order for an aircraft and then to select the start and end dates for the
forecast. The forecast is based on the selected flying programme and on the selected items which you wish to
include in the forecast. These can include:
 AMP Tasks
 Acceptable Deferred Defects
 AD/SB activities
 As and when items
The tasks can be grouped by package if required or forecast as individual tasks. Once the forecast has been
displayed the individual maintenance tasks or packages which are due, can be added to the works order by
simply clicking on them and saving the work order. All of the details relating to a task or package can be seen by
using the drill down facilities provided on the screen. Once the planning engineer is happy with the work included
Planning
in the work-order he/she can then pre-load the materials and check their status ready for the work to be carried
out. They can also print the entire package including attachments ready to be sent to the hangar.
A
A
A
A
-
G
Figure 26: The forecasting of maintenance is carried out using Option TF52
35
Component Forecasting - Life Limited Parts (LLPs)
Rotable parts with life limits also need to be tracked and their removal and overhaul planned. As all the part
histories along with their overhaul life limits are known to the system a forecast can also be generated to see the
expected overhaul dates and the removals required.
This can be used to plan these activities along with the airframe activities. By using the TF52 integrated planning
tool all the activities are included in the forecast and can be added to single a work-order.
Alternatively, option TF10 can be used to just see the activities related to LLPs
Planning
Figure 27: Option TF10 can be used to track life limited parts separately
Graphical Planning Tool
The OASES graphical planning tool enables planner to visualise at a glance what maintenance is required across
the fleet and when this will fall due. The type and duration of the maintenance input is shown in an easy to
understand ‘Gantt’ style chart making it easy to view both the short term and long term scheduling of the aircraft
maintenance.
36
This forecast can be run at fleet level or individual aircraft level and the aircraft are displayed on the y-axis, with
time moving across on the x-axis. Boxes shown on the timeline indicate when tasks are due, and the size of the
box indicates the length of that task. If any of the tasks are contained within a works order, then this works order
is shown with links to the tasks contained.
Planning
Figure 28: A graphical view of the long term maintenance across the fleet
It is also possible to create new works orders, add new tasks to the works order as well as add/remove tasks
from existing works orders as in TF52. The plan can then be saved and a printout can be made of the plan to
show all the items on it.
Figure 29: A works order is displayed with its contents described
37
PRODUCTION
Introduction
Once the maintenance work has been planned and released to the hangar floor the work is then controlled using
the Production module of OASES.
The resource planning function can be used to ensure that the correct resources are available to carry out the
work and plan the tasks
The work is controlled under the individual work orders which contain all the tasks which are to be accomplished
during the maintenance.
Production
Resource Planning
The resource planning module is used to control and plan the resources that will be used in the production area
so as to ensure the most efficient use of these resources and to plan and forecast the progress of work
Shift Planning
The new module allows the shift patterns of employees to be defined. It can then use this information to
calculate the amount of man power available on each day.
38
Figure 30:Setting up shift times
The shift times can be entered for the various shifts that are in use over the twenty-four-hour period and these
can be colour coded to identify them. The days on which these shifts are worked can also be defined to take
account of weekends and night shifts.
Production
Figure 31: Assigning days to shifts
39
Figure 32: View of hangar availability
Hangar Planning
Production
Using the existing data available in OASES about Works Orders, Tasks and Estimates with the new man power
data, OASES can now plot each open Works Order on a Gantt chart. This then can then show what work has to be
done at what time and also where you may be short of resources to complete a particular Works Order.
Figure 33: Hangar view - Planned works orders
40
Production
Figure 34: Works order view - Tasks in works order
Creating Shop Floor Employee Accounts
Shop floor staff can have an account created just to book time against for the tasks they undertake. This is done
simply using option SF70 to create them in the system. Once this is done they can book onto a task within a work
order.
The Maintenance Workbench
The OASES Maintenance Workbench is a fully integrated option which allows all the main Shop-floor data
capture functions to be handled in a single option. These tasks are controlled by the selections on the left hand
side of the window.
41
The various functions included in the Workbench are listed below
Taskcards - This allows the user to view the scheduled cards & NRC’s within a single or multiple works orders.
Production
Drill downs on bookings, materials, etc. are supported.
Defect task - This allows the user to create a new defect NRC.
Adhoc defect - This allows the user to create an ‘ad-hoc’ defect
Adhoc task - This allows the user to create an ‘ad-hoc’ task NRC.
Routine task amend/print - This allows the user to amend or re-print an existing routine task.
Non routine task amend/print - This allows the user to amend or re-print an existing non routine task.
Re-print NRC - This allows the user to re-print an NRC.
On/Off - This allows the user to book on or off a scheduled or NRC task. This is a real time booking using the
server clock times.
Manual - This allows the user to record a manual booking (typically from a time sheet) using start & stop times.
Elapsed - This allows the user to record a manual booking using the elapsed time.
Bookings - This allows the user to view bookings.
Once he has booked onto a task the system will then start to allocate his time to this task until he books off when
it is completed.
42
Booking on to Multiple Tasks
An engineer can book on to multiple tasks at the same time if required. This allows the engineer to work on
several tasks and complete them before returning to book off, thus saving time and effort. If this is carried out
then the system will allocate the total elapsed time by pro-rating it using the planned times as the basis for
allocating times against the individual tasks.
Production
Figure 35: The booking-on screen allows an engineer to book onto multiple tasks
Recording Defects
If an engineer discovers a defect during the planned maintenance or inspection they can raise a Non Routine
Card (NRC) in the system to record the defect. Using option SF15 the engineer records the details of his findings.
If the engineer is already booked onto a task the system will automatically assume that the defect is related to
this task. The engineer can then enter details of his finding including the kind of defect and the expected time
required to rectify. He/she can also order any materials that will be required to perform the rectification.
Once the defect has been raised as an NRC it can be tracked along with all of the other planned tasks so an
overall picture of the progress of the entire work package is visible to the managers.
43
Structural Damage Report
A structural damage report can be created and submitted for assessment and if necessary approval of the work
to be carried out. This can include details of the nature of the damage, its precise location on the airframe and
also the proposed work steps to rectify the damage.
Booking off
Once an engineer has completed a task he can book off the task or multiple tasks using options SF07/09. The
system will display the task or tasks he/she is booked onto, and will then allow the engineer to book off the task
Electronic Sign-off
If enabled on the system, an electronic sign-off of defect NRC cards is possible. Each engineer has a pin number
associated with their login and is able to use this to electronically sign NRC cards that are associated with the
defect.
OASES stores defects that have been created for working on an NRC in order that they can then be linked into the
Technical Records database automatically at completion of maintenance (CRS). This includes any component
changes undertaken. These defects can then be worked using NRCs that are generated from OASES.
Production
When the defect becomes deferred or rectified the NRC will be signed off electronically but before this process
concludes all component changes must be entered. The signoff will be electronically generated with all the
defect information and the mechanics signature. This process will also be triggered if the mechanic books off in
SFDC and sets the task status to be one that signifies deferred or rectified.
When the Works Order is closed in OASES the defect, component changes and consumable usage will be written
to tech-records using the sector selected for the CRS. This will then allow any component changes and
consumable usage to be activated in OASES. Finally, any items that cannot be validated will be flagged for review
by technical records staff. This will occur for instance if the part recorded as coming off the aircraft is not the
part recorded in OASES as having been previously the fitted item to that aircraft.
When a task status is set that signifies DEFERRED or CLOSED then the electronic signoff is triggered and the
system will produce a graphical screen report of the NRC. This can be reviewed by the user to confirm that they
are happy with the content exactly as they would do in a paper based system before signing the taskcard. If they
accept the details on the NRC report, then they will be able to continue and electronically signoff the document.
The user will then be asked for authentication. This is used to digitally sign the PDF NRC produced from the
graphical screen report. This digital signature can be viewed to see who signed the document.
In addition to the digital signature an image of the engineer or inspector’s physical signature as held in EA40 –
‘Security Manager’ can be added to the NRC PDF. This will give the appearance of it being signed as if it was a
physical document.
44
Once the NRC has been digitally signed it is not necessary to print it out and sign it physically.
Production
The PDF version of the NRC can hold separate signatures for Engineers and Inspectors. These will be both digital
signatures and copies of scanned physical signatures attached to the PDF in the place of the conventional
signature boxes.
Each time a mechanic or inspector wishes to add their signature to an NRC PDF they will have to supply their
authentication for the digital signing. This will also add their physical signature to the PDF. Each addition of a
signature will create a new revision of the PDF document with the digital signature of the new signatory. Only the
latest of the engineers’ and inspectors’ physical signature will be seen on the PDF copy.
Tracking Work in Progress
A vital part of managing maintenance inputs is to have visibility of the progress of the work and the capability to
compare the planned manpower and materials against the actual manpower and materials expended.
45
OASES allows hangar managers to keep track of the work in progress through the use of several options and
reports which provide a comprehensive status relating to any work-order.
This includes information relating to:
 The number of task completed vs those still open

 Budgeted vs actual labour
 Budgeted vs actual materials
 NRCs raised and closed
 Outstanding task by trade and zone
Production
Figure 36: Option SF15 allows managers to track the progress of the maintenance work in real-time
Tooling Control
An important aspect of any maintenance activity is the control of expensive tools which are required to carry out
the tasks. OASES has a comprehensive tooling control system which allows these tools to be controlled in the
system.
46
There are two methods of tooling control available in OASES A classic method which involves booking out tools
to mechanics and then, returning them in a separate transaction. Alternatively, OASES can use Radio Frequency
Identification (RFID) technology to control tools
Standard Tool Control
With the standard tool control method Engineers can interrogate the system to find the tooling they require and
then book the items which are in stores. Once they have completed the task they can return the tool to store and
it is booked in again and returned in the system.
Production
Figure 37: The tooling control system allow tools to be booked in and out of the stores and allocated to an individual
RFID Tooling Control
If RFID tooling control is in use, then all the tools in the Tool stores are identified with a RFID tag which is
attached to the tool. The mechanics also have an identification badge which identifies them personally and
recognises the mechanic as he enters the tooling stores.
47
Figure 38: RFID encoding a Tool in OASES
The tags can then be read using a handheld RFID scanner using existing OASES options in a similar way to a
barcode scanner. However, to make this even easier for the engineers a portal can be created. The portal is a PC,
setup in the entrance to the tool store, with a large screen, an RFID reader and running the OASES Portal
Production
software.
When an engineer walks past the portal, any tools with attached RFID tags are detected and shown on the large
display screen. A check out of these tools will then be performed in OASES, just as if the user had done this using
the OASES system. As well as detecting the tools it will detect the employee’s badge, also using RFID, and
therefore know who has taken the tools. Using the task bookings in OASES for this engineer it can also associate
these tools with the tasks and therefore the aircraft they are in use on.
48
Figure 39: OASES RFID System scanning for tags

Production
Figure 40: OASES RFID System checking out a tool
When the tool is returned to stores as the mechanic enters the stores with the tool, the tool is automatically
assigned back into the tooling stores stock. As all tools are RFID tagged, they can be located in the hangar at any
time if a tool is missing or required elsewhere.
Very importantly the system greatly reduces the risk of FOD due to tools being left on aircraft or lost and can
greatly reduce the time taken to return an aircraft to service.
49
Closing a Works Order
Figure 41:Option WC34 is used to close a works order and select the inbound sector for the hours and cycles
Once a check or work package has been completed the works order can be closed and the technical records
updated to record all the work that has been accomplished on the aircraft. In order to carry out this task the
Production
Close Works Order and Update Technical Records option WC34, is used. This allows the user to select the works
order that is to be closed and choose the incoming sector which provides the actual hours and cycles at which
the maintenance is recorded. The maintenance end time is also recorded in order to set the start point for any
calendar based items in the same screen. Once these details have been completed the user moves on to record
the actual work completed
Once the basic data has been completed regarding the works order and the hours and cycles from the inbound
sector have been recorded the individual tasks can be closed. If the task has been closed by the engineer work
scheduler then it will be shown as completed in the task selection window which appears now.
If for any reason the task has not been automatically completed it can be manually selected and set to complete.
In addition, an item can also be set to incomplete and the technical records will then show the task was not
accomplished.
50
Figure 42: The individual tasks can be set to complete and saved or marked as incomplete if required
Reports
In addition to the above option of viewing the progress of a work-order, a large number of detailed reports can
also be generated to provide high levels of detailed information right down to individual task card level.
The reports include:
 Budget vs actual cost

 Hours summary
 Daily tasks closed
 Daily NRCs raised
 Daily NRCs closed
 Total tasks closed report
 Task man-hours report
51
LINE MAINTENANCE CONTROL
Overview
OASES controls the short term maintenance requirements for an airline in the Line Maintenance Control (LMC)
module and allows the users to plan and allocate work to the various line stations. The LMC module integrates
with other OASES functions to provide a solution for line maintenance planning and control.
Line Maintenance Control
Figure 43: The LMC module is fully integrated with the Planning Module
52
Integration with Operations
For any LMC module to be effective, it is essential that the flight data is input as close to the arrival time of the
aircraft as possible. This enables defect information to be entered into the system at the point of discovery (or
very soon after) giving planning/line maintenance control the maximum amount of information and time to
decide when and where Acceptable Deferred Defects (ADDs) should be rectified.
Figure 44: Integration with a Flight Operations feed allow automatic entry of flight data
OASES can be interfaced directly with an Operations system, Electronic Tech-log or Flight-bag, allowing the
electronic transfer of flight and delay data, removing manual duplication of data entry and the inevitable errors
this lead to.
Integration with Inventory Database
The LMC module is also fully integrated with the Planning and Materials modules. This allows a Planning/LMC
department to ensure the availability of any materials required for the rectification of a defect in advance of the
due date.
Requirements (Electronic Demands) are created, which automatically reserves available stock and notifies Stores
when and where the parts are required. In the case of a Shortage, OASES immediately notifies purchasing the
date and time materials are required by.
Integration with Technical Records and Planning Data
The OASES system provides the ability to forecast when ADDs must be rectified based on the anticipated
utilisation of an individual Aircraft used in conjunction with the rectification intervals defined in the MEL.
This allows a planning/LMC department to accurately calculate and utilise the maximum available flight time
available prior to defect rectification.
Processing ADD data in tandem with the scheduled maintenance defined in technical records allows a planning
department to easily schedule line maintenance activities as part of a base maintenance visit, as well as
including scheduled maintenance or life limited components replacement activities within a line maintenance
work-schedule.
53

Figure 45: The process workflow for controlling line maintenance and defect rectifications
LMC Email Database
The OASES system produces LMC Worksheets for use by line engineers, detailing all activity required.
Where line maintenance is carried out at various outstations, OASES uses an Email database of LMC contacts
that can be used to quickly automate the process of distribution of line station work requests.
Minimum Equipment List
OASES holds the fleet’s MEL in electronic format within the system which then allows all defects to be controlled
and their rectification planned within the LMC module. The system also allows you to define the various
categories of defect in line with their MEL limitations and hold these in the system.
54
Figure 46: MEL items can be categorised and their limitations defined in option DV15
Creating and Editing ADD Categories
Option DV15 is used to define MEL categories in OASES that are then assigned to ADDs. Typically, categories, A,
B, C and D are defined. Rectification Intervals for Categories B, C and D are defined while Cat A is defined against
individual MEL References in option LM01. (Defect Entry & Rectification Process) Creating and Editing the MEL
Option LM01 is provided to allow the simple definition and maintenance of the MEL in OASES. The option also
provides a report that can be printed or saved as a PDF document and used for reference managing ADDs
Entering Defects
Defect entry facilities have been created to allow ADDs to be entered into OASES either by Line Maintenance
Engineers at the time of discovery or by an LMC or Technical Records Dept.
By assigning the correct MEL Reference to the ADD, OASES forecasts the end date and time of the end of the
Rectification Interval, indicating when the defect must be rectified by.
55

Figure 47: Option LE33 is used to enter Acceptable Deferred Defects
Entering Extensions
Where a defect cannot be rectified within the intervals defined in the MEL, extensions or variations can be
registered in OASES and once approved/agreed can be activated, such that a new due date can be calculated. If a
second or subsequent extension is required, the system allows these to be applied to the defect.
56
Figure 48: Extensions (or variations) to ADDs can be recorded in the system and are applied once they are approved
ADD Status Report
This option produces a report detailing the status of the unresolved ADDs in OASES. This report can be used as a
working document for engineers who are working on outstanding defects. If can also be used for the basis of
daily LMC/Engineering meetings.
The report shows Materials and their status. It also shows information regarding any extensions that have been
approved for the individual ADDs.
Figure 49: The Acceptable Deferred Defects report show the status of all items with any extensions if applied
Planning Line Maintenance
Raising a Works Order
The integrated planning tool is used to forecast the short term maintenance for an aircraft and to schedule a line
maintenance works order.
The option allows the creation of new line maintenance works orders, or the amendment or review of an existing
works order. Once this has been created, each ADD can be assigned to the Works Order, along with any
Scheduled Cards, and Component Change cards.
57
Figure 50: Line maintenance is planned using the integrated planning tool

LMC Dashboard
The LMC Dashboard is used by the Line Maintenance Control team to monitor the status of the fleet on a daily
basis and to provide data to other departments who require this information.
The dashboard provides information on the status of each individual aircraft with this information being drawn
for with in the OASES application and also being fed by both the electronic operations feed (if connected) and the
line maintenance team.
A set of standard parameters can be monitored in the dashboard which includes all ADDs which are active on an
aircraft with any restrictions which these ADDs impose also visible.
Any number of additional parameters that the airline wants to monitor against each aircraft can be added and
these can be set by selecting a simple yes/no answer or by selecting a condition from a drop down list.
If a Line Maintenance Controller or planner wants to find out further information regarding an ADD on a particular
aircraft, they can ‘drill down’ on the item to investigate and see the full details including the material status for
that item.
The dashboard uses colour coding to highlight MEL restrictions on aircraft (coded yellow) and will also highlight
overdue maintenance by coding the aircraft ‘red’ and therefore unserviceable.
58
The dashboard can be configured using the control buttons to show the whole fleet or a particular fleet type and
can also be setup to show the details of all the aircraft based at a particular airport.
The short term line maintenance inputs required for the fleet also can be visualised by using the graphical view in
TF60. This allows the planner or line engineer to see all the planned maintenance activities at a glance, and helps
to make efficient use of resources.
59
Figure 51: The OASES Graphical Planning display can be used to view the short term maintenance planned
Line Maintenance Material Requirements
Materials can then be identified and assigned to each ADD on the Works Order, by simply clicking on the ADD and
then following the OASES Quick Requirement Create procedure.
The status of each Requirement is shown using a Traffic Light style warning system that is already used in the
Stores system. This gives a Planner an instant indication of the status of each ADD.
Clicking on a Requirement or Part number allows you to drill down to see a more detailed analysis of the
Inventory databases.

Figure 52: The status of all materials for line maintenance can be seen at a glance using the traffic light colour coding
Updating OASES with Line Maintenance Accomplishment Data
Option LM34 is used to close a line maintenance works order and update the technical records and to
automatically rectify the Acceptable Deferred Defects. When the line maintenance works order arrives in
technical records, this option is used to close any rectified ADDs.
Any component changes that were required can also be entered at this time. If the ADD was progressed but not
resolved, the status of the ADD is updated, but the ADD remains open, so that it can be allocated to a second or
subsequent Works Order at a later date.
60
INTENIONALLY BLANK
61
MATERIAL MANAGEMENT
Overview
The OASES Materials Management Module is a fully comprehensive inventory and material control system that is
fully integrated with the other OASES modules ensuring consistency of data right across the system and as a
result across the entire organisation which is using the system. This means all parts and materials are visible to
users ensuring the best possible use is made of inventory thereby reducing stockholding and as a result cost.
Material Management
The module ensures the cost effective availability of the materials required for the safe operation of the fleet and
maintenance of aircraft whilst minimising the investment needed to achieve this.
Quotations
OASES has a full quotations module built into it which allows the purchasing department to automatically
request quotations from an agreed list of suppliers for any part. Suppliers can then quote for these parts and the
quotation can then be turned into a purchase order against the selected supplier
Purchasing
The system provides facilities for the management of purchase, repair, loan and service exchange orders for
aircraft parts and services. The system can also handle commercial orders for non-aircraft goods and services if
required.
62
All the required forms including orders, serviceable and unserviceable tags and release documentation can be
produced from OASES. These forms can also be automatically emailed, printed or converted to PDF or
laser/thermal transfer printers as required.
Orders, stock and replenishment levels, batch and serial number histories are automatically up-dated through the
normal use of the system and invoice passing routines provide flexibility, but ensure that payments are only
authorised where they comply with the business rules.
Stock Control
Stock levels are continuously monitored by the system and all costs, component locations and histories are
maintained to support effective business decision making. The system can report on all stock and material
values against specific works orders, stock groups, warehouses etc. The system supports use of multiple
currencies and automatically applies conversions (against a customer controlled currency database) to
seamlessly manage inventory bought or sold in a foreign currency.
The desired stock level at any individual location can be independently set and the system will monitor these and
alert the user when stocks fall below the set minimum level. This will also take account of alternate parts to give
a full view of the current situation so that management of the stock can be optimised across the entire
Material Management
organisation.
A system of colour coding makes it very easy to view the stock situation for any given part or group of parts
where these are needed for a maintenance task. The situation can be monitored across individual warehouses or
across the all warehouses and it can include alternate parts if available.
Figure 53: The stock situation for any given part number can be monitored across warehouses and includes alternate parts
All movements are monitored by the system and may trigger the production of re-ordering or stock transfer alert
reports. Management reports are produced with respect to shelf life control, stocktaking, stock valuation and the
financial analysis of material usage.
Shortage control
The system provides a fully integrated approach to the management of inventory demands and material
requirements are tracked from initial creation by the end user or system function (i.e. automatically from works
order creation) through each stage to completion and reconciliation with the financial accounting system.
63
Automatic shortage management ensures that all outstanding requirements are visible at all times. Any items
that may have been pre-allocated to a planned maintenance input are still visible in the system. If a higher
priority event occurs (AOG) they can be released to satisfy this demand and a new shortage will be automatically
generated. This re-shortage is intelligently routed to the appropriate section giving full details of the current
status of the new shortage to allow maximum time possible to satisfy this new demand.
The system automatically tracks material requirements associated with planned maintenance, modifications and
defects and provides ‘traffic light’ status reports for each item in a works order.
Material Management
Figure 54: The status of parts for a works order can be seen 'at a glance' through the traffic light status of the item
Part Enquiries
A general part enquiry can normally be performed by any user of the system and gives the basic data regarding
any part held in the inventory system. This includes the stock holding and associated serial numbers for the item
if it is a rotable part. For consumables the unit of issue is given and the last movement of stock and also pricing
information can also easily be seen for any part.
The full technical records history of a serialised part can also be seen along with its life limits and current hours /
cycles and any associated strip reports. Serialised parts can be viewed by serial number and their current
64
disposition across warehouses and the fleet can also be viewed. If any orders or repairs have been raised in the
past then these can also be viewed as well as any currently outstanding orders.
Material Management
Figure 55: - Full details regarding part in the inventory can be viewed including its full history if it is a rotable part
Batch & Serial Traceability
OASES maintains full batch and serial number traceability and automatically updates these records as
transactions occur. This provides a full audit trail enabling a user with appropriate system permissions to trace
the origin, usage, repair history and current stock location of all items known to the system. Cost, repair and tear
down report data are also registered against and assist in identifying unreliable components
Loan Control
The system automatically maintains a log of all parts (loaned in or out) through the parts issued and received
facilities. This mechanism allows improved control over this easily neglected and costly aspect of stores control.
The system also understands the concept of multiple ownership of stock
65
Cores ‘due in’
OASES understands that if a rotable part on an aircraft is changed then there is a ‘core’ part that is due to be
added back into the inventory, normally for either repair or overhaul and so the system tracks these items to
ensure that they are not lost or left un-monitored by the system. This ensures that valuable inventory is
conserved and that the stockholding is not depleted as a result of parts being mislaid. The system automatically
generates reports for those parts which require attention in this way and allows the rotable inventory team to
manage the stock by either sending the item for repair or overhaul.
Vendor Management KPIs
OASES has the capability to monitor vendors/suppliers using the data captured by the system with regards to
repair orders. These KPI data is presented for each vendor and can be filtered by date. It will show the average
turnaround time for the vendor
Material Management
Figure 56: Vendors can be monitored by using the OASES option IA01
66
INTENIONALLY BLANK
67
WARRANTY MANAGEMENT
Overview
The Warranty Management Module has been designed to ensure an operator maximizes the amount of warranty
that is claimed on both the aircraft and parts in the inventory. By setting up warranty contract terms in the
OASES system any potential claim can be identified and a claim made for the part as soon as it is booked into
stores in an unserviceable condition.
Warranty Controllers use the integrated Warranty Workbench to monitor the warranty situation and to make Warranty Management
decisions on claims where this is required. All the actions necessary to administer warranty can be carried out in
this single screen. A Warranty Controller can tailor his workbench through a series of filters to customise It to
their particular requirements which may be a set of vendor accounts or perhaps an aircraft fleet for which they
have responsibility.
Use of the Workbench speeds up the administration and ensures all the data necessary to carry out the function
is all available in one place. This allows the controllers to spend more time analysing and improving performance
rather than carrying out basic administration.
The module is designed to provide an operator with an automatic way of identifying and then claiming warranty
on all parts which enter stores as unserviceable items.
68
Warranty Agreements
The Vendor Management team can define in OASES the exact warranty agreements that are in place covering an
aircraft, a vendor, a repair station, or a part / serial number. This allows a great deal of flexibility in defining the
exact warranty terms for each aircraft or component, as well as allowing for contract agreements where groups
of parts are overhauled by a particular contractor.
Manufacturer warranties can also be handled for new aircraft which can be calendar, hours or cycles based. Once
defined in OASES, these rules will then be used to decide if a warranty claim can be made for any part coming
from an aircraft in an unserviceable condition.
Warranty Management
Figure 57: The warranty control dashboard
Warranty Tracking
At the time of booking in the component in an unserviceable state the component records are checked to see if
any potential warranty claim can be made. This can be based on time since new, time since fit, a calendar time,
or a time since overhaul or repair. It can check the number of cycles or hours since new or last overhauled or last
repaired.
69
The potential claims are identified by comparing the component information held in the system against a set of
criteria which have been defined for that part by the Vendor Management team.
When a claim is identified the system automatically marks the repair order in the system as a warranty claim and
advises the stores person of the warranty claim. If the stores person does not want to claim warranty, they must
enter a reason for not doing so. When a warranty is claimed, the warranty order for that component is identified
with a watermark as a ‘warranty claim’. The order paperwork will also have printed on it, details of the reason for
the warranty claim.
Warranty Administration
If the system identifies that a component has more than one potential warranty claim available to it, then the
stores are notified of the potential claims and the part is put on hold pending a decision by the warranty
controllers as to which warranty they wish to claim under.
The warranty controllers are able to see all parts which parts have been booked in unserviceable and where
warranty is applicable in the Warranty Workbench (see example above) and by using a series of filters they can
then identify the parts they are interested in and administer the warranty claims.
Warranty Management
In the event more than one warranty term is a potential source of a claim the system identifies these items, and
refers them to the warranty controller through the Warranty Workbench. The controller can then decide which
claim to make based on the value or likelihood of the claim being successful. Once a decision has been made the
system will create the warranty order and advise Stores to ship the part.
Once a warranty has been claimed the warranty controllers can then monitor the process and update the system
to ensure that the warranty claims are being processed correctly. When the vendor responds to the order the
controllers can update the system. The controllers can add details such as whether the claim has been
successful, if the claim has been partially successful, or if the claim has been denied.
The reasons for a partial acceptance or denial of warranty and any strip reports can also be entered into the
records to provide a full history. All of this data can then be used to provide useful statistics regarding warranty
claims.
Warranty Reporting
By continuously gathering data on the warranty claims and their outcome, the system has the ability to generate
a variety of useful reports which help the operator monitor its performance in successfully claiming warranty.
These reports can then be used to target vendors or repair stations which have a poor record of performance
with regards to warranty claims and drive up the number of successful claims.
A typical report is shown below. These types of reports are used by the controllers to show management the
current situation and the success in claiming warranty and the performance of individual vendors.
70
Warranty Management
Figure 58: An example of a warranty performance report

Warranty Management
71
COMMERCIAL MODULE
The OASES Commercial Module is primarily intended for use by third party maintenance providers who carry out
work for other companies and therefore require a flexible and sophisticated method of managing the process for
invoicing the work in accordance with the contract agreed with the customer.
Commercial Control
The OASES Commercial Module had been designed with this in mind and allows the user to model complex
contracts in the system in a way that means automated invoicing is still possible despite there being many
variables in each contract.
It allows customers to track and invoice for all labour and materials associated with third party work. It also
provides the capability to invoice against complex customer models which can be tailored to match individual
contracts or aircraft packages.
Invoicing Work Bench
The entire Commercial module is built around an invoicing workbench which allows users to interact with the
system and carry out the major tasks required. The workbench is broken down into four main areas. These are:
1. The task and actions pane which contains icons which become live dependent on the available tasks or
actions.
2. The Customers and Contracts pane which allow the user to select the customer or contract on which
they wish to carry out work.
72
3. The Works order pane which allows the user to select the specific customer work-order on which they
wish to work.
4. The Invoice pane which allows the user to select the specific invoice on which they wish to work.
Commercial Management
Figure 59: The Commercial work-bench with the main interface panes
Tasks and Actions Pane
Depending on the selected items on which the user is working and their permissions various task and action
icons will become live in this pane.
These icons allow the user to carry out specific functions such as creating, editing deleting or adding data to a
specific item in the module such as a contract, a works order or an invoice.
Only those items which are valid for the current situation become live and are coloured in. If they are not valid the
icon is greyed out and cannot be selected.
Figure 60: Creating a customer allows the other icons become valid and usable
73
Figure 61: Now a customer has been created in the task pane the other icons become valid and are usable
Customers and Contracts
The Customer and Contracts window allows the user to enter and edit data relating to their customers and to
select the specific customer or contract on which they want to work.
This is also where all the specific contract clauses can be entered into the system in a way that will allow it to
understand the basis for charging and this in turn will drive the invoicing for the work which is carried out.
The system can hold data relating to mark-ups (including tiered mark-ups), times of day, national holiday periods
etc. all of which affect the rates at which work is charged.
Figure 62: Example of the data set-up for a new customer
The system can also be set to handle both minimum and maximum mark-ups dependent on the item and the
customer. It can also be set to charge minimum shipping charges and will handle charging differently for stock
and non-stock items.
74
Once the full details relating to a specific customer or contract are entered in the system any work carried out
under the contract will automatically be invoiced according to these rules.
Figure 63: An example of set-up data for a specific customer relating to their contract
Customer Quotes Module
The Customer Quotes function brings together all elements of the RFQ in a Workbench option. The customer
requirements, i.e. work-scope, can be created from a combination of packages, OOP (Out of Phase) items,
component changes and other ad-hoc tasks, commercial requirements or administrative requests.
OASES holds details of each task including skill, estimated man hours, required materials etc. This is cross
referred to the commercial database within OASES containing contract terms and conditions, customer man hour
rates, material mark-ups, etc. This is all bought together in a quotation which details the full scope & cost of the
maintenance input.
Warranty
In addition, labour and materials covered by a manufacturer’s warranty, can identified. These appear as zero or
reduced value items on the quote, and if the quote is accepted and the maintenance is accomplished, separate
warranty invoices are automatically generated by OASES as required to be sent to the OEM to claim the warranty.
75
Figure 64: An example of a work package and the OASES Quotation for the work
Decision Support
OASES analyses the MRO’s previous experience of accomplishments of each task in the quotation to establish
the average man hours taken to complete this historically against this aircraft type, and also identifies the
current defect rate. The man hour estimate and quote value can be adjusted up or down as required by the MRO.
OASES uses its own man hour estimates & skills to provide the quotation. It is critical is it is well understood
that the OEM man hour estimates are usually low. OASES also revises the estimates based on previous actual
times to ensure the man hours quoted are very accurate. The man hour rates for each skill can be defined as a
standard & overridden at a customer or aircraft level if required. These can be revised on a period basis, e.g.
annually or quarterly in line with company list prices, but OASES retains the full history of contract data.
Material and consumable costs are estimated based on purchase history and adjusted based on contractual
mark-up and handling costs as defined by each customer contract.
Estimated repair costs and handling can be defined in the quote. On production of the finalised invoice, the
actual repair costs and handling costs incurred are calculated.
76
Fixed Price Agreements
OASES can define quotes in terms of Time and Materials but allows both maintenance tasks and materials to be
defined as fixed price items.
End to End Process
OASES provides functionality to manage the life cycle of a maintenance project from receipt of quote to issue of
invoice.
Upon acceptance of the quotation, OASES converts the quote into a live works order at the click of a button,
which builds a work pack and raises requisitions for all required materials. The work pack and supporting
documentation, i.e. check-lists and panel charts can be printed or emailed to the production team.
Invoicing Pane
The invoicing pane is used firstly to select or create the invoice on which the user wants to work and then once a
draft invoice has been created it can be reviewed and edited if required. The system can also divide the invoice
into warranty and non-warranty invoices if this is required by the customer.
The system can handle multiple currencies and also tax regimes depending on the user’s national requirements.
All the caps and minimum charges set in the contract will automatically be imposed by the system when
producing the invoice. The invoice can also be manually edited if required before being finalised.
The invoice is then produced on an individually tailored customer template with the user’s logo etc. included and
all the other relevant data.
77
Figure 65: The invoicing pane is where invoices are created and edited, before being finalised.
Shipping Charges
The commercial module handles freight charges and can apply minimum and maximum charges and also
distinguish between stock parts and parts bought in. It can also apply different rates according to the value of
the part concerned in a tiered manner.
Figure 66: Minimum and maximum freight rates can be applied as well as tiered charges according to value
78
INTENTIONALLY BLANK
79
REPORTING AND EXPORTING DATA
OASES has extensive capabilities to report and export data and also to connect to various proprietary software
packages or systems through the Oracle® table views which are available.
Reporting and Exporting Data

Reporting
Within in each module of OASES there is a reports and Exports menu which provides a selection of standard
reports and exports which have been developed to provide the information for the most common requirements.
Print Reports
Many standard reports can be used directly as print reports which can be submitted to the authorities. These
standard reports can be customised to have the Company logo on them and include reports such as AD/SB
status reports, LLP reports and AMP reports.
In addition to the standard reports, it is a feature of OASES that within any standard table display in the software
that you can ‘right click’ and export the data from the table in a format which is compatible with the Microsoft
office® suite. This allows great flexibility to develop custom reports and to carry out analysis.
80
Figure 67: An example of a selection of print reports avaialble in a module
Exports
OASES also has a series of standard exports which produce comma separated value files (.csv), which can then
be imported and manipulated in Microsoft Excel® etc.
Figure 68: An example of the selection of data exports are available from the Inventory module
81
Database Views
A set of database views have been created within the application and in with the aid of the OASES Data
Dictionary, these views can be used to create a variety of reports or displays.
Because these views are ‘stable’ and we publish the data dictionary customers are able to use the information in
the views to create bespoke reporting solutions or connect proprietary reporting software to OASES to generate
customised reports
View OASES Module Contents

V_ACCESS_BY_WORKCARD_ALL Planning Access panels declared for each
workcard in all AMP revisions
V_ACCESS_BY_WORKCARD_CURRENT Planning Access panels declared for each
workcard in current live AMP
revision

V_ACCESS_EFFECTIVITY_ALL Planning Access panel effectivity
definitions in all AMP revisions.
V_ACCESS_EFFECTIVITY_CURRENT Planning Access panel effectivity
definitions in the current live AMP
revision.
V_ACCESS_PANELS_ALL Planning Access panel descriptions and
labour and inspection manpower
estimates for all AMP revisions
V_ACCESS_PANELS_CURRENT Planning Current live revision access panel
descriptions and labour and
inspection manpower estimates
V_ACCOMPLISHMENT_HISTORY Planning Workcard accomplishments
V_ACCOUNT_LOCATIONS Material This table contains details of all
Management individual locations specified for
all purchase and/or sales
accounts. Some of the fields
shown are present for historical
purposes and are no longer in
common use (for example
TELEX_NUMBER) although they
may have be used by Customers
for their own purposes.
V_ACCOUNTS Material Customer and supplier account
Management details
V_ACCOUNTS_REFERENCES Material Accounts references
Management
V_AD_SB_ACCOMPLISHMENT_CODES Continuing Codes used to classify AD/SB
Airworthiness requirements by the priority
required for their
accomplishment - e.g. mandatory,
optional, recommended, etc.
82
V_AIRCRAFT Continuing Aircraft details

Airworthiness
V_AIRCRAFT_BUILD Continuing Aircraft build skeleton
Airworthiness
V_AIRCRAFT_TYPE_CODES Material Code lookup table for descriptions
Management of aircraft types declared in the
part master table
V_AIRCRAFT_WEIGHT Continuing Aircraft weight details.
Airworthiness
V_AIRPORTS Continuing Airport codes, locations and
Airworthiness descriptions
V_AIRWAY_BILL_REFERENCES Material Airway Bill Reference details.
Management
V_ALTERNATE_PARTS Material Alternate parts.
Management
V_AMP_PLANNING_NOTES_ALL Planning Planners notes relating to VISITS,
PACKAGES and WORKCARDS
V_AMP_PLANNING_NOTES_CURRENT Planning Planners notes relating to VISITS,
PACKAGES and WORKCARDS in
the current live AMP revision

V_AMP_REVISIONS Planning AMP revision details
V_AMP_SECTIONS Planning Codes used to identify various
sections of the AMP
V_AMP_WORKCARD_PROPERTIES Planning Property Code lookup table for
workcard property details
V_BATCHES Material All batches whether in stock or
Management not - to determine stock position
for a batch join to v_rotable_stock
or v_consumable_stock
depending on part_type in
v_part_master
V_BINS Material Warehouse bin definitions.
Management
V_CANCELLED_FLIGHTS Continuing Cancelled flights
Airworthiness
V_CFD_CATEGORIES Continuing Carried forward defect
Airworthiness classifications and the
rectification limits that they
impose
V_CHAPTERS Material Main ATA Chapters
Management
V_COMPONENT_LIFE Continuing Non-ship based life values relating
Airworthiness to components.
V_COMPONENT_MOVEMENT_HIST_LIF Continuing Non-ship based life values relating
E Airworthiness to component movements.
V_COMPONENT_MOVEMENT_HISTORY Continuing Component movement history -
Airworthiness to sort in latest movement first
sequence, ORDER BY
PART_NUMBER,
SERIAL_NUMBER,
83
MOVEMENT_DATE DESC,
DAY_SEQUENCE DESC.
V_COMPONENTS Continuing All components for which the
Airworthiness system has a component
technical record
V_CONDITION_CODES Continuing Component condition codes used
Airworthiness when ordering and receiving
goods to specify the condition
requested/received
V_CONSUMABLE_HISTORY Material Inventory history for consumable
Management parts showing individual
transactions performed by part
number
V_CONSUMABLE_STOCK Material Details of consumable items
Management currently held in stock - these
details can be joined to
V_BATCHES to get complete
details of current inventory
V_CONSUMABLES_BELOW_REORDER Material Parts that are at or below reorder
Management level and the date at which this

occurred.
V_CONTRACT_STOP_RATES Commercial OASES invoicing module contract
stop rates
V_CORROSION_CATEGORIES Continuing Descriptions for corrosion
Airworthiness categories used in defect analysis
V_COST_CODES Commercial OASES invoicing module cost
codes
V_COUNTRIES Commercial Countries.
V_CREDIT_NOTE_HEADER Commercial OASES invoicing module credit
note header
V_CREDIT_WORKS_ORDER_CARDS Commercial Details associated with credited
workcards
V_CREDIT_WORKS_ORDERS Commercial Works orders receiving credit
notes
V_CURRENCY_CODES Commercial CURRENCY codes
V_CURRENCY_RATES Commercial CURRENCY RATES AND
APPLICABLE DATES
V_CUSTOMER_CONTRACT_RATES Commercial OASES invoicing module contract
rates
V_CUSTOMER_CONTRACTS Commercial Customer contract headers
V_CUSTOMS_STATUS_CODES Material Customs status code lookup
Management
V_DEFAULT_LABOUR_RATES Commercial Labour rates for invoicing.
V_DELAY_CODES Continuing Flight Delay Codes
Airworthiness
V_DELAYS Continuing Flight Delays - more than one may
Airworthiness be attributed to a single flight
V_DELIVERY_ADDRESSES Material OASES User organisation internal
Management delivery point addresses
84
V_DELIVERY_NOTE_HEADERS Material Delivery note header details.

Management
V_DELIVERY_NOTE_ITEMS Material Items being delivered on the
Management indicated delivery note.
V_DOCUMENT_EFFECTIVITY_ALL Planning Workcard reference and
attachment document effectivity
as defined in all revisions.
V_DOCUMENT_EFFECTIVITY_CURRENT Planning Workcard reference and
attachment document effectivity
as defined in the current live
revision.
V_DUES_REGISTER Material Register of components either
Management due in (i.e. to be returned to
stock) or due out (i.e. to be
issued).
V_EMPLOYEE_LICENCES Production Licences held by each employee.
An employee may have more than
one licence entry.
V_EMPLOYEES Production Employee details
V_FLEET_ATA_REFERENCES Continuing Full ATA references applicable to
Airworthiness the specified fleet

V_FLEET_NOTES Continuing Fleet notes.
Airworthiness
V_FLEETS Continuing Fleet (aircraft type) definitions
Airworthiness
V_FLIGHT_TYPES Continuing Flight Types
Airworthiness
V_FLIGHTS Continuing ACTUAL FLIGHTS DERIVED AS ALL
Airworthiness SECTORS WHICH HAVE LANDINGS
V_FORECAST Continuing Forecast of maintenance items
Airworthiness derived from current forecast
cache - NOTE THAT THE DETAILS
CONTAINED IN THIS VIEW ARE
ONLY AS UP-TO-DATE AS THE
LATEST CACHED RUN(S) OF THE
FORECAST
V_INVOICE_LINES Commercial Purchase invoice detail lines.
V_INVOICES Commercial Supplier Invoices - header details.
V_JOB_REFERENCES Material JOB references
Management
V_LICENCES Production Licence type definitions
V_MAINTENANCE_REPORTS Continuing Defect and Rectification Reports
Airworthiness
V_MAINTENANCE_SECTORS Continuing Aircraft maintenance sectors
Airworthiness
V_MEASUREMENTS Continuing Individual measurement items
Airworthiness recorded against flights or
maintenance sectors.
85
V_MEL_REFERENCES_ALL Continuing MEL reference detail items -

Airworthiness includes references from all MEL
revisions
V_MEL_REFERENCES_CURRENT Continuing MEL reference detail items -
Airworthiness includes references from only the
current live MEL revision
V_MEL_REVISIONS Continuing MEL Revision details
Airworthiness
V_MOVEMENT_CODES Material Every inventory transaction has
Management an associated movement code
which identifies what action is
being performed (e.g. Issue,
Return to stores, scrap)
V_NON_INFO_DEFECT_COUNTS Continuing Counts of defects which are not
Airworthiness classified as info-only by fleet,
aircraft, ATA chapter and year and
month.

V_NRC_ACCESS_PANELS Planning Access panels required for NRCs.
V_NRC_DOCUMENTS Planning Documents relating to NRCs.
V_NRC_MATERIALS Planning Material requirements for NRCs.
V_ORDER_HEADERS Material Details of orders issued to
Management purchase goods and services,
including purchases, repairs,
service exchanges, loans and non-
stocked items and services
V_ORDER_INVOICES Material Order line invoice details - for
Management order header details join to
V_ORDER_HEADERS - note that
INVOICE_CONTROL_NUMBER,
INVOICE_NUMBER and
INVOICE_SEQUENCE will only be
present if the OASES Invoice
Passing module is in use and not if
the invoice was entered via the
Batch Approval option
V_ORDER_LINES Material Order line details for Purchase,
Management Repair, Service Exchange, Loan
and Non-stock Orders - for order
header details join to
V_ORDER_HEADERS
V_ORDER_RECEIPTS Material Individual receipts into stock
Management against order lines - note that
there may be multiple receipts for
a single order line
V_ORDER_REQT_ALLOC Material List of requirements to which
Management orders are allocated - order lines
may be allocated to more than
one requirement
86
V_ORIGINAL_PURCHASE_VALUES Material Date on which the currency value

Management was converted to local.
V_PACKAGE_NOTES Planning Package notes.
V_PART_MASTER Material Base information for each part
Management number in the system - includes
serialised, batched and non-
stocked parts.
V_PDC_INDEX Continuing Linking data between PDC system
Airworthiness and OASES flight data.
V_PREFERRED_BINS_BY_PART Material This view shows all the
Management warehouse and bin number
combinations designated as
preferred bins for all parts. There
may be many entries per part as
the User is allowed to define a
preferred bin for each part in
each defined warehouse
V_REMOVALS Continuing Component removals
Airworthiness
V_REPETITIVE_DEFECTS Continuing Repetitive defects.
Airworthiness
V_REPORT_EXTENSIONS Continuing Details of extensions granted
Airworthiness against CFD reports
V_REPORT_MAINT_STAGES Continuing Definitions of stages of work
Airworthiness undertaken to rectify defects
V_REPORT_STAGE_EMPLOYEES Production Record of work by an employee
on a stage of the rectification of a
defect (maintenance report)
V_REPORT_TYPES Continuing Report types used to categorise
Airworthiness maintenance reports
V_REQUIREMENT_ACTIONS Planning NRC requirements actions.
V_REQUIREMENT_PICK_HISTORY Material Details of stock picked to satisfy
Management requirements
V_REQUIREMENT_PRIORITY_CODES Material Requirement priority codes
Management
V_REQUIREMENTS Material Inventory requirements
Management
V_ROTABLE_HISTORY Material Inventory history for ROTABLE
Management parts showing individual
transactions performed by part
number and serial number
V_ROTABLE_STOCK Material Details of ROTABLE items
Management currently held in stock - these
details can be joined to
V_BATCHES to get complete
details of current inventory
V_SALES_INVOICE_CATEGORY_HOURS Commercial Cumulative time details for each
time category for each task
invoiced.
87
V_SALES_INVOICE_TIME_CATS Commercial Time classifications used to

calculate labour charges relating
to sales invoices as they were at
the time the invoice was raised.
V_SALES_INVOICES Commercial Sales invoices
V_SALES_INVOICES_CARDS Commercial Tasks carried out for each invoice
V_SALES_INVOICES_MATERIALS Commercial Material costs applied to invoices
V_SCHEDULED_REMOVAL_COUNTS Continuing Counts of scheduled component
Airworthiness Removals by ATA chapter, year
and month.
V_SECTOR_DEFINITIONS Continuing Scheduled sector details including
Airworthiness durations
V_SECTORS Continuing Aircraft activities - including
Airworthiness flights both operated and
cancelled and maintenance
sectors
V_SFDC_BOOKINGS Production Time booked against work-
schedule tasks
V_STOCK_GROUP_CODES Material Code lookup table for descriptions

Management of stock groups declared in the
part master table
V_STRIP_REPORTS Material Strip Reports.
Management
V_SUB_CHAPTERS Continuing ATA Sub-chapter definitions
Airworthiness
V_SUB_FLEETS Planning Sub-fleet definitions.
V_TIME_CATEGORIES Commercial Definitions of charging periods
during the day to which differing
labour rates may be applied.
V_TRADES Planning Trade codes applied to employees
and workcards to determine
which tasks require which type of
knowledge - for example Avionic,
Engine etc.
V_UNITS_OF_MEASURE Material Every part in the inventory
Management module has an associated unit of
measure which represents the
quantity of that part that
determines a single unit for stock-
holding.
V_UNITS_OF_MEASURE_CONVERSION Material Conversion rates to be applied if
Management the purchase unit of measure is
different to that in which the
stock is held in inventory. These
are the default rates that apply
for all parts. If specific parts have
their own specific conversion
rates, these are to be found in
view
88
V_PART_NUMBER_UOM_CONVE
RSION
V_UNSCHEDULED_REMOVAL_COUNTS Continuing Counts of Unscheduled
Airworthiness Component Removals by ATA
chapter, year and month.
V_UOM_CONVERSION_BY_PART Material Conversion rates to be applied if
Management the purchase unit of measure is
different to that in which the
stock is held in inventory. These
are the default rates that apply
for all parts. If specific parts have
their own specific conversion
rates, these are to be found in
view
V_PART_NUMBER_UOM_CONVE
RSION
V_VAT_CODES Commercial VAT rates.
V_VISIT_NOTES Planning Visit notes.
V_VISITS_ALL Planning Visit definitions in all AMP
revisions.
V_VISITS_CURRENT Planning Visit definitions in current live
AMP revision.
V_WAREHOUSE_DISTRIBUTION Material Inventory distribution by
Management warehouse
V_WAREHOUSES Material Warehouse details
Management
V_WARRANTY_CLAIMS Material Warranty claims.
Management
V_WARRANTY_EXCLUSIONS Material Supplier/part/serial exclusions
Management from warranty terms applicability
V_WARRANTY_TERMS Material Warranty terms.
Management
V_WC_AC_EFFECTIVITY_ALL Planning Workcard effectivity definition for
all workcards in all revisions.
V_WC_AC_EFFECTIVITY_CURRENT Planning Workcard effectivity definition for
all workcards in current live
revisions.
V_WORK_SCHEDULE_DEFECTS Planning Workschedule task defect details
V_WORK_SCHEDULE_WORKCARDS Planning Tasks (workcards) contained in
each work-schedule
V_WORK_SCHEDULES Planning Basic details of aircraft work-
schedules
V_WORKCARD_AC_EXCLUSIONS Planning Workcard aircraft exclusions in
NON_AMP databases
V_WORKCARD_ACTIVATIONS_ALL Planning Workcard activation definitions in
all AMP revisions.
V_WORKCARD_ACTIVATIONS_CURRENT Planning Workcard activation definitions in
the current live AMP revision.
89
V_WORKCARD_CALLS_ALL Planning Workcard call workcard

V_WORKCARD_CALLS_CURRENT Planning Workcard call workcard
definitions in the current live AMP
revision.
V_WORKCARD_CANCELS_ALL Planning Workcard cancel workcard
V_WORKCARD_CANCELS_CURRENT Planning Workcard cancel workcard
definitions in current live AMP
revision.
V_WORKCARD_DOCUMENTS_ALL Planning Workcard reference and
attachment documents as defined
in all revisions.
V_WORKCARD_DOCUMENTS_CURRENT Planning Workcard reference and
attachment documents as defined

in the current live revision.
V_WORKCARD_MATERIALS_ALL Planning Workcard material definitions for
all workcards in all revisions.
V_WORKCARD_MATERIALS_CURRENT Planning Workcard material definitions for
all workcards in current live
revisions.
V_WORKCARD_NARRATIVE_ALL Planning Workcard narrative - showing
tasks in all OASES AMP revisions
V_WORKCARD_NARRATIVE_CURRENT Planning Workcard narrative - showing
only tasks in the current OASES
AMP revision
V_WORKCARD_PACKAGES_ALL Planning Workcard Packages as defined in
all revisions.
V_WORKCARD_PACKAGES_CURRENT Planning Workcard Packages as defined in
the current live revision.
V_WORKCARD_PROPERTIES_ALL Planning Properties applicable to each
revision of each workcard - for
details of the workcard join to
V_WORKCARDS_ALL using FLEET,
WORKCARD_NUMBER and
REVISION_ID
V_WORKCARD_PROPERTIES_CURRENT Planning Properties applicable to the
current revision of each workcard
- for details of the workcard join
to V_WORKCARDS_ALL using
FLEET, WORKCARD_NUMBER and
REVISION_ID
V_WORKCARDS_ALL Planning Basic workcard details - showing
tasks in all OASES AMP revisions
V_WORKCARDS_CURRENT Planning Basic workcard details - showing
only tasks in the current OASES
AMP revision
V_WORKS_ORDER_ISSUES_RETURNS Material This view provides details of all
Management inventory issue, return and
90
adjustment transactions
registered against works orders
V_WORKS_ORDERS Planning Works Order details
V_ZONES Planning Codes used to identify various
areas of the aircraft
91
Copyright © Communications Software (Airline Systems) Limited, 2016
The information in this document is the property of Communications Software

(Airline Systems) Limited and may not be copied, or communicated to a third
party, or used for any purpose other than
that for which it is supplied, without the express written consent of

Communications Software (Airline Systems) Limited.
While the content of the document is given in good faith, based on the latest
information available to Communications Software (Airline Systems) Limited,
no warranty or representation is given concerning it. This content does not
establish any contractual or other commitment binding on Communications
Software (Airline Systems) Limited.
92
Communications Software (Airline Systems) Limited

8 The Centre, Church Road, Tiptree, Essex, CO5 0HF United Kingdom
Telephone: +44 (0)1621 817425 Web: www.oases.aero
93

OASES Functions and Features Version 6.0 PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

OASES Functions and Features Version 6.0 PDF

Transféré par

Droits d'auteur :

Formats disponibles

Maintenance & Engineering Software

Functions & Features Overview

OASES Maintenance & Engineering System

Functions and Features Overview

OASES SYSTEM OVERVIEW ..................................................................................................................................... 11

OASES CORE ............................................................................................................................................................ 12

Information Technology Environment ................................................................................................................. 12

User Interface Features ....................................................................................................................................... 13

Table Exports to Excel® ...................................................................................................................................... 13

Date Entry formats ............................................................................................................................................... 14

Absolute dates ................................................................................................................................................. 14

Relative dates .................................................................................................................................................. 15

Text Entry Memory Feature (“The Squirrel”) ........................................................................................................ 15

The Help System .................................................................................................................................................. 16

Data Import and Management ............................................................................................................................. 18

Aircraft Configuration and Build .......................................................................................................................... 19

Component and Assembly Control ...................................................................................................................... 19

Task Card Management ....................................................................................................................................... 20

Packaging Tasks .................................................................................................................................................. 22

Managing the AMP and Revisions ....................................................................................................................... 22

AD/SB and EO Control and Revision .................................................................................................................... 23

Workflow Assignment .......................................................................................................................................... 25

EASA Automatic Download .................................................................................................................................. 26

Tech-Log Manager ............................................................................................................................................... 26

Electronic Operations Systems Feeds ............................................................................................................. 26

Non-ship Based Lives (NSBL) .............................................................................................................................. 29

Repetitive Defect Alerting .................................................................................................................................... 29

Automatic Reliability Reporting ........................................................................................................................... 31

Task Card Database ............................................................................................................................................. 32

Package Analysis ................................................................................................................................................. 34

Component Forecasting - Life Limited Parts (LLPs) ........................................................................................... 36

Graphical Planning Tool ....................................................................................................................................... 36

Resource Planning ............................................................................................................................................... 38

Shift Planning .................................................................................................................................................. 38

Hangar Planning .............................................................................................................................................. 40

Creating Shop Floor Employee Accounts ........................................................................................................ 41

The Maintenance Workbench .............................................................................................................................. 41

Booking on to Multiple Tasks .............................................................................................................................. 43

Recording Defects ............................................................................................................................................... 43

Structural Damage Report ................................................................................................................................... 44

Booking off .......................................................................................................................................................... 44

Electronic Sign-off ............................................................................................................................................... 44

Tracking Work in Progress ................................................................................................................................... 45

Tooling Control .................................................................................................................................................... 46

Standard Tool Control .......................................................................................................................................... 47

RFID Tooling Control ............................................................................................................................................ 47

Closing a Works Order.......................................................................................................................................... 50

LINE MAINTENANCE CONTROL ............................................................................................................................... 52

Integration with Operations ................................................................................................................................. 53

Integration with Inventory Database ................................................................................................................... 53

Integration with Technical Records and Planning Data ...................................................................................... 53

LMC Email Database ............................................................................................................................................ 54

Minimum Equipment List ..................................................................................................................................... 54

Creating and Editing ADD Categories .................................................................................................................. 55

Entering Defects .............................................................................................................................................. 55

Entering Extensions ......................................................................................................................................... 56

ADD Status Report........................................................................................................................................... 57

Planning Line Maintenance ................................................................................................................................. 57

Raising a Works Order ..................................................................................................................................... 57

LMC Dashboard ............................................................................................................................................... 58

Line Maintenance Material Requirements ........................................................................................................... 60

Updating OASES with Line Maintenance Accomplishment Data ......................................................................... 60

Stock Control ....................................................................................................................................................... 63