This course gives the student an understanding of how to do operational planning of their vehicles and register operational parameter values during operation - values that may trigger interval maintenance, condition based maintenance, modifications or fault reporting. The student will be introduced to predefined queries and history data that is retained in IFS/Vehicle Information Management (IFS/VIM). The attendees will also get a quick tour of an introduction to background jobs aimed to keep the data base healthy.
The estimated time to complete this course is 10 hours.
This course was designed primarily for operation and maintenance managers who are responsible for operational planning and execution of maintenance program and modifications on serialized vehicles. Maintenance personnel executing jobs may find the predefined queries and the history retained in IFS/VIM to be of great value and help when executing daily work.
This chapter introduces you to a simple way of operational planning of serialized vehicles. As the operational plan is linked to a route, this has implications on where the vehicle is and where to execute maintenance tasks that may come up.
Before taking the lessons in this chapter, you should have completed the Manage Serialized Configuration course.
The estimated time to complete this chapter is 1 hour.
This chapter was designed primarily for operational managers being responsible for allocation vehicles according to an operational route schedule. Complex scheduling (like commercial airline operation) requires more advanced planning systems.
This chapter takes you through the different functions for entering operational data on vehicles.
The Operational Logging - Key lesson explains how to enter values on operational parameters that are used in the interval maintenance plan for a vehicle or sub-structure part. You will also learn how to perform a corrective operational logging and an asynchronous operational logging that affects already performed structure changes.
At completion of the Condition Monitoring - Key lesson you will know how to register values on condition codes applied in condition based maintenance. When values exceed defined limits you will see that maintenance tasks are generated.
The Faults and Events - Key lesson gives you an introduction on how to register unplanned (corrective) need for maintenance either on a vehicle or a part. Registration of a fault will immediately generate a maintenance task.
Before taking the lessons in this chapter, you should have completed the Manage Serialized Configuration course.
The estimated time to complete this chapter is 4 hours.
This chapter was designed primarily for product line managers and maintenance staff being responsible for follow-up on vehicle operational status and execution of vehicle maintenance.
This chapter takes you through the different options available for reporting and maintaining flight logs for vehicles. In the aviation industry, all operators use a flight log to record important information pertaining to flights. This format and content of these flight logs vary by operator, but the overall objective is the same. A flight log sheet also referred to as a flight log 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.
Through the lessons in this chapter you will learn how to register a flight log for a vehicle, report information on each flight, record operational disruptions that may have occurred during a flight, report operational loggings (utilization) for a flight, report faults found during a flight, and record condition measurements. In addition you will learn how to void a flight that has been entered incorrectly and manage flight servicing, i.e., service checks performed prior to and after flights, which makes the aircraft ready for service for a predefined time period after the service has been completed. Once all information on a flight log has been entered, you will learn how to close the flight log. There can be instances where information on a closed flight log needs to be corrected. To do these corrections you will learn how to reopen a closed flight log and the different information that can be amended. Finally you will learn how to void a flight log that has been entered incorrectly and move voided flights to an open flight log.
Before taking the lessons in this chapter, you should have completed the Serial Structure course and the Operational Planning course.
The estimated time to complete this chapter is 4 hours.
This chapter was designed primarily for pilots who need to report information about the flight such as takeoff and landing times, deviations and utilization after completion of the flight. In addition, the flight line mechanics need to check the log for any open issues on the aircraft, report actions taken and ensure that all faults are signed off prior to the flight. Crew members need to report information about pre- and post-flight activities and technicians many need to do some reporting, for instance de-icing and measurements results related to daily operations for an aircraft.
This chapter presents the different types of historical information relevant to the Operate Asset process that is generated and retained in IFS/VIM.
Before taking the lessons in this chapter, you should have completed the previous chapters.
The estimated time to complete this chapter is 0.5 hours.
This chapter was designed primarily for product line managers and maintenance staff being responsible for follow-up on vehicle operational status and execution of vehicle maintenance.
IFS/VIM consists of a number of background jobs. Some are aimed to automate Due Calculations and reduce the amount of user intensive processes, while others are used for the shape-up of the database.
Before taking the lessons in this chapter, you should have an overall knowledge of the solution.
The estimated time to complete this chapter is 0.5 hours.
This chapter was designed for maintenance program managers and work planners, and senior technicians who has to monitor the flow of maintenance related information between the different databases in a distributed system environment.