The OASES CORE module provides all elements required for the operation and support of the OASES system
At the heart of the OASES system is the Core Module, to which the individual functional modules can be added.
The OASES Core provides the essential system components that allow operation and integration of OASES functional modules. This includes the Oracle database, the navigator functionality, the built-in help system and also the security manager which controls access rights and privileges.
OASES functional modules are designed to plug in to the CORE and provide a flexible and cost-effective framework that allows users to ‘design’ the perfect system and configuration for their operation. The CORE includes all database, operating systems, interfaces and applications required to operate OASES.
Administrators can easily manage user accounts, associated rights and security permissions and can redesign and re-label user menus. Security groups (roles) and policies can also be defined and offer flexible control for granting, rescinding or amending user or role permissions.
The OASES Navigator allows users to move easily to any function and these can be automatically included in a user-specific ‘favourites’ menu. OASES remembers session entries in all input fields making recall of part numbers, registrations etc. very easy and intuitive.
All relevant changes to the database are written to a transaction log containing details of the change, user ID, date, time and location making audit of the system quick and simple.
The Continuing Airworthiness Module provides the necessary tools to efficiently manage continuing airworthiness processes, giving you confidence that your organisation is complying with regulatory obligations.
The Continuing Airworthiness Module provides the necessary tools to efficiently manage continuing airworthiness processes, giving you confidence that your organisation is complying with regulatory obligations.
OASES maintains and reports reliability statistics at a fleet level and automatically generates graphical reports for utilisation, in-service and maintenance defects, despatch reliability, component removals and open defects. The OASES user may easily define additional defect classifications e.g. ‘cabin defects’ and the system then automatically collects and reports statistics for these. The report function also offers full ATA and component removal analysis enabling detailed interrogation of the high-level data.
OASES maintains a model of each aircraft that defines all significant component locations. Specific part/serial numbers are then installed and monitored or the system will manage ‘empty’ component locations but will assume installation as part of the original build of the aircraft.
Each component location comprises an 8-character ATA identifier and description which together with position and zone indicators give unique identification and control of all monitored components and systems.
This model may be used as a standard fleet template that can be easily modified to reflect configuration variance within the fleet.
Users may define repetitive defect alert windows against a 4 character ATA descriptor. OASES monitors all removals and automatically raises a Repetitive Defect Investigation should 3 events occur. Once an alert has been raised by the system the reliability engineers can track it and if necessary request an investigation.
Component assemblies may be defined to any required depth and OASES understands that removal of any master/sub component requires all sub-assemblies are also removed e.g. this allows a complete engine assembly to be removed as a single transaction. The component life forecasting mechanisms will call for the master component to be removed based on controls for any of its installed sub-assemblies.
Approved Maintenance Plan (AMP)
OASES maintains all tasks within the Approved Maintenance Programme (AMP) and ensures only those contained in the current approved revision are issued to a works order. Changes to the AMP may be developed within the system, and once approved, may be updated instantly to the new revision.
The system can also generate a full AMP report which can be submitted to the local authorities for approval and a 'differences' report can also be generated in order to speed up the approval process.
The system maintains elapsed life data for all components including time since new, since fit, since overhaul and since repair. This data is easily accessible and can also be displayed for any given historical date. All maintenance and modification tasks are linked directly to the airframe, location or component as appropriate. Various component removal alert levels may be defined against each ATA sub-system and OASES will report the current actual alert rate considering all events
This facility allows elegant and easy control of all AD, SB, EO, SIL, AOT etc. Each entity may be defined by the user and complex relationships can be modelled. Documents can be defined as superseding or mandating others and the reverse relationships are automatically set. Multiple paragraphs can be created in a document record and the paragraphs can be set to run in parallel or in sequence. Completion of all task steps within a related SB will automatically record compliance with a controlling AD.
Each record is held centrally and may be effective across multiple fleets, aircraft and components. A work flow sequence may be defined against each type of document and the system can intelligently route each stage depending on fleet type. A full AD/SB compliance statement can be generated at fleet or aircraft level.
OASES can be configured for automatic download of AD source documentation (EASA) and provides an easily auditable record of all transmittals generated in this way.
The PLANNING MODULE predicts when all maintenance tasks, modifications and defect limitations will become due, allowing planners to easily integrate these into works orders and can then automatically generate the work package documentation and material pre-loads.
Each individual task that is required by the maintenance plan is tracked in the OASES system. The type of task can be defined along with labour time and numbers required, trade, multi-stage thresholds and intervals. All relationships between this and other tasks can be easily defined, including accomplishment, activation, calling, cancellation, “do not perform with” and “previously accomplished by” which allows management of spin-off tasks. Task intervals may be hours, cycles, days or date based. In addition the user may define a non-ship based life against a component or component location e.g. engine thrust cycles. The system also allows different fleets to have separate life control restrictions i.e. fleet A controls APU by hours, fleet B by cycles, or either can be controlled by more than one life type.
Manufacturer Job Instructions
Any manufacturer job instructions of an appropriate format and their revisions may be automatically imported and associated with the task. When the task is called to a works order the system automatically attaches and prints the job instructions with the work card and references the attachment in the narrative. Other automatic attachments can include any local documentation or other information which may be associated with a user-definable workcard property. These are easily referenced to the central task record and can be printed and/or referenced in the task narrative automatically.
Manufacturer’s job instruction documentation can be automatically linked to task cards allowing them to be
printed as part of a package
Maintenance Check Packages
Individual tasks can be packaged as required and the package will appear in the forecast according to the most restrictive task contained within it. Yield management tools are provided to allow review of each package. A package appearing in the forecast can be scheduled into a works order with a single click and/or expanded to view individual task details including schedule reference, last done, time remaining etc. Other items can be added to the same works order if additional work is required to be carried out at the same time.
Any task which is generated by an airworthiness directive or a service bulletin can be entered into and tracked by the planning system. Inspections or modifications which are required will be viewable in the aircraft maintenance forecast and can then be included in a works order.
Once a group of tasks or a package has been generated and included in a works order the planner can then produce a workpack which can be distributed to the department or organisation carrying out the maintenance either electronically as a PDF or printed to hard copy and physically forwarded.
All relevant access panels can also be derived automatically for each task in the works order. Various control methodologies are then available to manage these.
Any electronic document can be attached to an OASES task so that it can be printed as part of a pack or referenced in the system. In this way the system makes it simple to produce comprehensive documentation to support maintenance activities
The Production Module tracks the progress of tasks within any works order in real time as they are worked through the hangar/MRO facility and reports budget vs actual labour expended, defects raised, task status and all materials issued or returned.
The resource planning functionality all users to plan hangar resources required to carry out maintenance on an aircraft. This includes detailed staffing availability planning, Works Order planning at a hangar level down to individual task level. Each task can be planned based on available resources on that day; showing the planner when the maintenance will be completed and the aircraft can be released back into service.
It can also be used when a Works Order is actively being worked on in the hangar, showing what has been completed, what remains to be done and if the maintenance is going to be completed on time.
All work cards may be bar-coded providing a simple and reliable method for work in progress data capture. Employees may be identified using a variety of techniques and allows operation of the system in the hangar without the need of a keyboard. As each task, workcard, operation or activity is performed, the information is captured by scanning or by direct entry into a tablet or PC. The information collected includes job number, employee number, materials used, start and finish times, etc enabling fast and efficient analysis of the task’s progress.
OASES’ defect control configuration options offer a flexible approach for the management of defects as they are discovered. All findings are tracked against the originating inspection or task and the system provides a full set of displays, reports and standardised exports for managers to monitor progress.
All labour expended or committed is collated by OASES and provides a real-time view of the current status of the works order. The system supports separation of inspection and labour hour estimates and compares the budgeted position with the actual current position. Managers can easily assimilate the impact of defects and other disruptions to the plan and can take remedial action at the earliest possible point in time.
Task Status Classifactions
Users can easily setup multiple codes enabling detailed analysis and tracking of individual tasks within a works order. The works order closure function understands these codes and is able to automatically determine the completion status date and time for each task.
All issues to and returns from the works order are tracked and reported. The system monitors the current works order status and prevents issues to the works order after the planned closure date. The system also monitors rotable issues to a works order and can be configured to prompt for the return of the off-core.
All mechanic times can be reported for both base maintenance tasks and defect rectification activities and can be reported as an individual’s experience log. In addition, employee experience can be reported using definable defect stage status codes
Multiple Task Tracking
Once the work package has been printed at either the hangar, MRO or line station, employees can log on to each task individually or against multiple tasks if more efficient. The management reporting systems annotate each task in the real-time displays to show multiple allocations and total time is apportioned pro-rata according to the estimated labour/inspection times against each task.
Timely, accurate information is key to the effective management of the works order and OASES provides full visibility of all open, suspended and closed tasks. Employee booking histories allow analysis and identification of best practice and assist in identifying training needs.
Together, these facilities provide high visibility to managers of changes to the plan, defects raised and their implications and any events likely to prevent planned return to service. Defects become visible at the earliest possible stage allowing early management intervention and mitigation of costs and service disruption events.
The Line Maintenance Control Module accepts suitable data feeds from EFB, ETL, e-enabled aircraft and electronic operations systems, enabling effective control of short-term maintenance planning, aircraft defects and the materials required to support rectification.
Electronic Data Integration
The system offers a flexible framework allowing data to be exported and imported. Exported data can be presented to external systems (EFB, ETL etc.) in real-time as it originates from within OASES. Generally, data imports are scheduled according to the capabilities of the external system (i.e. five minute intervals). Numerous formats are supported including web-services, XML and CSV. Typically, customers would begin by importing aircraft type and registration, flight no, origin and destination airports, flight and block times, duration, fluid uplifts and APU data.
Defect information can 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 Carried Forward Defects (CFDs) should be rectified.
Using the system short term planners and managers can forecast on a single screen all short term scheduled activities, component removals and defect rectifications required.
Due times can be calculated against user-defined aircraft utilization models allowing” what-if” scenarios to be considered. 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.
From this combined work forecast the system automatically produces and emails an LMC worksheet to the appropriate station, detailing all maintenance and rectification activities to be performed.
The MEL is held electronically in the system and as defects are reported they are categorised and controlled directly against the appropriate MEL control. This again significantly reduces the opportunity for error and time and date stamps transactions to provide easy audit and review.
Processing CFD data in tandem with the activities defined in the maintenance schedule allows the Planning department, to easily schedule line maintenance activities as part of a base maintenance visit.
The OASES system provides close integration between the planning and material control functions, ensuring the availability of any materials required for the rectification of a defect in advance of the due date.
As requirements (electronic requisitions) are created, the system intelligently routes these depending upon rules set by the organisation. For example, if stock is available it can either be automatically reserved or, if required immediately, a picking notification will be automatically forwarded to the relevant warehouse location. If not available, or if the value of the request exceeds any pre-set limit, the system will automatically email the relevant buyer or manager advising them of the requirement.
The originator of the requirement is able to view the full details of their request including actions taken by Purchasing giving the current status and expected date of delivery.
Full access to defect history of the aircraft is easily available to all employees with appropriate system permissions. This data can be filtered by ATA system(s), CFD category, date range etc. to aid in identification of problems and the operator can easily drill-down to the source information from the same view.
The Material Management Module controls all material within the organisation ensuring that it is available when required but is efficiently used and replenished or repaired when required. All stock is visible in the system at all times allowing the most cost effective use of stock at all locations.
Order control encompasses purchasing, repair, loan and service exchange for both aircraft parts and non-aircraft goods. The system can create a request for quotation whcih can be sent out to vendors. When the vendors have responded the quotation can then be turned into an order against the winning vendor.
Orders can be placed in multiple currencies and shipping detials can be added fro mthe system to enure delivery of the parts to the location where they are required.
If the Planning depatment create a works order which requires parts to carry out the work, then the Purchasing depertment is automatically notiifed of any shortages by the system and can create an order to fulfill the requimrement.
When items are received the accounts department is advised and can authorise payment or the system automatically passes items for payment based on the organisation’s business rules.
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.
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
Full visibility and history is available for all items in the inventory. Stock levels can be set and monitored so that re-ordering is automatically notified to purchasing. The system can handle multiple warehouses and can include alternate parts when considering re-order levels. The systems show stock in each location to allow efficient routing of parts to meet requirements.
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.
The system can handle multiple ownership of parts in order to deal with consignment parts or power by the hour agreements where part ownership is retianed by the vendor.
The system 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
Loans and Exchanges
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 handles exchanged items.
RFID Tool Control
The RFID tooling functionality in OASES allows an aircraft maintenance organisation to control all its aircraft tooling using RFID technology. This allows for faster and more accurate control for the issuing and receipt of tools and avoids tools which are out-of-date or unserviceable from being used to maintain aircraft.
OASES can be used to individually control each tool using a unique identifier which is contained within an RFID tag which is attached to the tool or to individual parts of a tool kit. Each individual technician/mechanic has a unique RFID identification tag which can either be attached to his/her normal employee ID badge or to a dedicated badge. This tag identifies the employee to the system and is used to associate tools to the employee when they go to the tool store.
The Commercial Management Module 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.
The module has the capability to model complex contract structures including multiple labour rates, mark-ups with the possibility to set caps if required. Different material categories can be subject to differing mark-ups and this can be set down to aircraft level.
Default labour rates can be set but they can be over-ridden by a customer contract or for a particular aircraft work package. Labour rates can be tiered to take account of fixed prices for certain work and varied according to time of day or for week-end / holiday periods. All charges can be over-ridden if required and when authorised. Effective dates can be set-up for labour charges to cover work over long term contracts and time categories can be used to cover out of hours work or off base support. Labour charges can be rounded according to the company’s policy in this area.
Material charges can be set for stock items or can be varied if the material is associated with a particular contract. Mark-up percentages can be varied according to the value of the materials and can also be capped if required.
Freight and Service Charges
Freight charges can also be handled by the system. Default minima and maxima can also be set.
Service charges can be set-up with cost codes to cover routine tasks such as cleaning and servicing of aircraft if required, rather than be charged for at hourly rates.
The system can differentiate between warranty and chargeable work and manage these activities alongside each other.
The system can be set up to work with different tax regimes and has a full model for European VAT calculations built into it.
Invoices and Credit Notes
Invoices are finalised and then issued and a record of the invoice is then held in the system. Invoices can subsequently be amended if required, but a copy of the original is retained by the system. Credit notes can also be issued by the system against a customer’s account.
The system has extensive reporting capabilities built in to allow detailed analysis of the business to be carried out. Examples of reporting include the following:
◾Invoice value by customer and date range
◾Invoice value by A/C type or registration
◾Work in Progress (WIP)
◾Reconciliation of stock movements
◾Accrued cost of sales
◾Actual cost of sales
The Warranty 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 un-serviceable condition.
Warranty Controllers use the integrated Warranty Workbench to monitor the warranty situation and to make 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 has 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 analyzing and improving performance rather than carrying out basic administration.
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 un-serviceable condition.
At the time of booking in the component in an un-serviceable 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.
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.
Once the system is setup it will identify each warranty claim that can be made and then either automatically raise a warranty order or refer the case to the warranty team for a decision.
In the event more than one warranty term is a potential source of a warranty 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.
The warranty controllers can also enter data relating to their warranty claims as it becomes available, such as whether the warranty is granted or denied.
They can also enter strip reports and other information to build a full history for a particular part.
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.