The AVES OSM module is used to manage the operational schedule. The operational schedule is the only flight database in AVES shared by all modules and subsystems, with the exception of the AVES Scheduler module. A schedule created in the AVES Scheduler module can be uploaded to the operational schedule when published in the AVES Scheduler. Flights can also be loadedto the operational schedule via import functions. Deployment of the AVES Scheduler module is optional.Small airlines and charter operators can also use OSM to create and maintain all flights directly in the operational database. AVES OSM provides the functionality for handling a single flight as well as a series of flights. The OSM GUI is nearly the same as the AVES Scheduler GUI with the only difference being that the type and reason for each modification of flight data have to be specified. In addition, AVES OSM enables the creation of complete documentation for all significant changes in the schedule following publication