Operate Asset

The Operate Asset process is made up of the following sub processes: Plan Daily Operations, Make Operational Entry and Manage Flight Logs. Following is a description of each sub process.

Plan Daily Operations

An operational budget enables you to forecast and plan the use and maintenance of your vehicle. This budget is based on your traffic budget. By complementing the approved operational budget with information from an operational schedule, you can obtain an operational schedule for all vehicles in your fleet. You can also assign crew and special optional equipment to the operational schedule. Note: The operational budget is optional.

Make Operational Entry

This sub process handles all the different types of reporting from operating a fleet of serials (vehicles). Operational information per serial includes entering operational parameter measurements per serial, faults and events entries, and registration of condition measurements. To register operation information on a serial, the operational status of the serial must be set to either In Operation or Out Of Operation. 

Operational log data, e.g., time in use, distance traveled, or number of operations or cycles, can be entered on the vehicle or on serials. The data is spread to all serials underneath in the structure at the time the data is entered. Reasonableness controls are performed, and deviations are flagged. It is possible to look at the history of the executed measurements and the results. Operational parameters measured are a result of the operational parameters indicated for the serial's maintenance group. In case you want to remove an operational parameter for a serial or add a new one, this must be done for the serials maintenance group. This also affects other serials connected to this maintenance group.

A freely chosen number of condition limits can be observed for components with a serial state. When a condition measurement is outside the defined warning and/or danger and/or change limits, a pending task will be created to perform the corrective task. The application is also capable of receiving condition data from equipment installed in operational gear. This must be fitted in each case.

A fault or event might be registered by the person who discovered it during operation. The fault is registered as outstanding and distributed as a task in the workshop by the planner. A fault already repaired upon discovery during another fault repair or by inspection in the workshop can also be entered, provided that sign off requirements are not connected to the function breakdown of the fault. When registering faults that already are repaired, you must specify the date of the repair, a description of the work, the resource group and man-hours used to repair the fault and what was really discovered, a complete functional breakdown and the workshop where the fault was repaired. If another outstanding fault with the same functional breakdown is already registered, the system issues a warning, which enables the possibility to abort the saving.

Manage Flight Logs

In the Aviation industry, all operators use a flight log to record important information pertaining to flights. The format and content of these flight logs vary by operator, but the overall objective is the same. A flight log or flight log sheet is traditionally a paper document that is pulled from a preprinted stack, where each sheet is numbered by sequence, and where all flights and actions through one day is recorded on the same flight log sheet.

The flight log is defined for a valid vehicle and all the flights that have been completed within a day should be logged in the flight log, usually by the Pilot. Flight logs are status-enabled. Valid statuses are Open, Closed, Voided and Amendment. The following activities can be performed when managing flight logs in the system:

• Create basic data for flight logs.
• Report a flight log against a vehicle, i.e., aircraft.
• Report information on the flight itself such as takeoff and landing times, deviations, crew, departure location, arrival location, block off and block on.
• Report operational loggings (utilization) after completion of the flight.
• Void a flight that has, for instance, been entered incorrectly.
• Report any faults found during a flight or as part of line maintenance activities.
• Report the actions that were taken for the vehicle to operate without the fault being signed off.
• Void a fault action that has, for instance, been entered incorrectly.
• Update the list of operational parameters for a serial on a flight.
• Perform a structure change (i.e., replace a serial, install or remove a part or serial, rob a serial or swap serials) to the structure of the vehicle on the flight log.
• Perform quick reporting of a pending fault task.
• Recalculate a fault deferral.
• Delete a fault deferral.
• Report pre- and post- flight servicing activities on a flight or in general on a flight log. Flight servicing refers to the service checks performed prior to and after flights which makes the aircraft ready for operation for a predefined time period after the service has been completed.
• Void flight servicing activities that have, for instance, been entered incorrectly.
• Report information on the flight and in-flight crew members that worked on a flight. Information such as the role, training level of crew members and the type of operational tasks performed during the flight can be reported.
• Void crew information that has, for instance, been entered incorrectly.
• Report condition measurement results related to daily operations on the aircraft.
• Close the flight log.
• Amend the flight log. When changes are required to be made to a closed flight log.
• Void a flight log that has, for instance, been entered incorrectly.
• Move voided flight from a closed or voided flight log to another open flight log.
• View and analyze historical flight log information.

The following data can be defined when setting up basic data for flight logs:

• Reasons why the aircraft may have been deviated from its original route or delayed.
• The cause for canceling a flight.
• The valid types of flight servicing to be entered when reporting flight servicing information.
• Operator designators per owner organization. Designators are codes used to identify an airline for commercial purposes such as reservations, timetables, tickets, tariffs, air waybills and in airline interline telecommunications. Examples of operator designators are BA for British Airways and SK for Scandinavian Airlines. The predefined operator information will be used when automatically generating operational plan IDs for a flight log.
• The number of days voided and closed flight logs relevant to an owner organization should remain in the Flight Log page. For a period of time, both voided and closed flight logs can be important information to view together with open logs for a vehicle. But after awhile this information is not as relevant and can be moved into history. Once the number of days defined in basic data is reached, the voided and closed flight logs will be moved to history through a background job. If number of days is not defined, 0 (zero) is taken as the default value and the voided and closed flight logs will be moved to history as soon as the background job is executed.
• Training levels for flight crew members.
• The type of flight times, e.g., night flying time and instrument flying time, for a crew member.
• The types of operational tasks, e.g., navigation flight and transportation flight, that can be performed during a flight.