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.
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.
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, hours used, the competence of the personnel repairing 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.
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:
The following data can be defined when setting up basic data for flight logs: