This activity is used to register the actual usage of serials. Loggings are based on a start and a finish date, and the defined operational parameters for the part. The system allows operational loggings for events that have occurred provided that the operational loggings are sequential.
It is also possible to report operational loggings (utilization) for a flight directly on a flight log. For operational loggings on a flight, the combination of part number, serial number and operational parameter (if the operational parameter is not found higher up in the selected structure) will be displayed automatically in the operational log information. This allows logging of operational parameters for an entire structure at once, without having to define all operational parameters at the highest level. Further, you can report different values for the same operational parameter on different items within the structure. To know how the structure of the vehicle looks at the time of reporting operational loggings, the structure will be built based on the Take Off Date on the flight. If the takeoff time is changed on the flight, the structure will be built once again based on the new time entered.
When operational loggings are performed, the system checks whether any structural changes (replacements, disconnects, connects) have been performed in the time interval between the operational logging date and time and the current date and time. This ensures that the operational values are spread on the correct serial structure as they were at logging time. Note: When a zero operational logging is performed to a particular serial structure, no new record will be created in the serial operational log history for the zero value that is saved.
Example: An operational event was carried out on 05JAN20, but the operational logging was not performed on the same day. On 07JAN20, the engine of the serial structure was replaced by another engine. Then the operational logging was performed on 08JAN20 (after the replacement). The operational values are required to be spread out on the engine (and its structure) that was replaced on 07JAN00 and not on the structure as it is today.
The two parameters OPER_LOG_MAND_EVENTS and OPER_LOG_SEV_EVENTS defined as Object Properties are used to control the requirements for operational events when performing an operational logging. OPER_LOG_MAND_EVENTS parameter is used to specify that an operational event should be entered for an operational logging. This parameter can have the values Warning, Mandatory or No Requirements, and will control the way in which you will be notified if an operational event is not entered during the operational logging. Observe the following:
OPER_LOG_SEV_EVENTS parameter specifies that multiple operational loggings can be done for a given operational event. This parameter can have the values Warning, Not Allowed or No Requirements. The usage of these values are similar to that of OPER_LOG_MAND_EVENTS parameter. If the value is Warning, a warning message is displayed. For Not Allowed, an error message is displayed, and nothing will be done when the value is No Requirements.
If you are up to date with reporting all finished maintenance events, while at the same time you are not up to date with reporting operational loggings, you may need special handling. When an event is finished the current operational parameter values (for the finish date of the event) or the values you have entered manually are stored on the finished event. When you perform an operational logging later on, the values you enter will be validated against the latest performed event. If the values, you enter on the operational logging is higher than the values of the previous performed maintenance or lower than the values of the next performed maintenance an error message will be displayed. If all operational parameter values entered on the finished events (that are between the previous operational logging and the one just been logged), have the same operational parameter values as the previous operational logging enable the Auto Adjust Subsequent Completed Mx Event option in the Report Operational Logging page.
When operations have been logged by enabling the Auto Adjust Subsequent Completed Mx Event option, the information used for calculating the next due date is updated automatically. Refer the Operational Log document for further details.
If you end up in a deadlock, not being able to perform an operational logging, and not being able to adjust the parameter values for a finished maintenance event, operational parameter values can be changed for a finished maintenance event in the Maintenance Event Completion Information/Operational Parameter page. To change values, click the Change Operational Values command for the relevant record. The command is only enabled for maintenance events in status Finished. Enter the new values you want in the Value After Overhaul, Value After Repair and Value Total fields. Note: The new values entered here are required to be greater than or equal to the previous log value for the serials and smaller than or equal to the next log value of the serial.
To report operational logging for a serial:
To report operational loggings for a flight:
Note: You cannot enter operational loggings on an earlier date than the date for the previous archiving. If you need to enter loggings on an earlier date than this, you need to restore the archived operational loggings back until the date that the loggings have to be performed.