Common use of Database Maintenance Clause in Contracts

Database Maintenance. The applications programming group is responsible for the Database maintenance of the Worldflight System. The loading, updating, and validation of the data entered into the Worldflight database is the responsibility of the user groups that the applications support. Database maintenance does include, file sizing, and the repair of corrupted data that was caused due to programming errors. The Worldflight system supports communications with other systems with both real-time and batch traffic. Worldflight provides real-time feeds to the following systems; Acars—uplinks, CFT—Corporate Flight Times, CMS—Crew Management (NWA), Cargo, MSG—TTY traffic, Sceptre—Aircraft Maintenance (NWA), Ramp/Fids—Gate Managemnet, Worldspan—Reservations / Common use, and ODB—Operations Database. Worldflight has the following batch feeds out; Stats—statistics, Mapper—Fuel Usage (NWA only), Worldspan—Microfiche. Worldflight is updated by the following systems; Acars—downlinks, MSG—TTY traffic, Sceptre—Aircraft Maintenance, Worldspan—Pass/Bag information, and ODB—Operations Database. Batch file feeds into Worldflight; Schedules—Airflight System, Aircraft Performance Data (via TSO). Enhancement requests are requests for new funtionality, or requests for cosmetic changes with the functionality remaining the same. These requests will require a Computer Service Request (CSR), and need to be submitted to the Operations Automation group for evaluation and priority assignment. The following will be measured and available on request; System Availability/Outages, Transaction Response Time, and Reliability of Outgoing Feed. N/A (See Appendix L1A) 37 ▇▇▇▇▇▇▇▇ ▇▇▇ Worldflight Products/Services System Availability—This measurement is the availability of the hardware and software within the Building J computer center. Outages of the various pieces affecting Worldflight availability are cumulative—that is, an outage to a communications front-end (that affects Worldflight users) is counted as a Worldflight availability outage. This measurement is not the end-to-end availability to the agent or customer at a terminal in the field. Future monitoring tools may provide an end-to-end measurement. Transaction Response Time—This measurement is the mainframe existence time of selected Worldflight transactions. This measurement is not the end-to-end availability to the agent or customer at a terminal in the field. Future monitoring tools may provide an end-to-end measurement. The selected transactions are those transactions within Flifo and Weight and Balance which are interactively used by the customer. Capacity planning has the list of transactions. Note that a future refinement of the response time goal is to measure the response time during periods of stress, such as bad-weather-related massive flight diversions. It is particularly important to have quick response times during these stress situations. The selected Flifo and Weight and Balance transactions are the appropriate transactions to be measured during stress times. Outgoing Feed—This measurement is the reliability of the daily feed to Stats. After Stats receives the Worldflight feed, the Stats IMPACT job is run. Note that the IMPACT completion is already being measured—when IMPACT does not complete by 6am, a severity 2 Info/Man record is generated. While measuring IMPACT completion is only an indirect measure of Worldflight outgoing feed reliability, IMPACT completion is chosen as the measure for 4thquarter 1996 because a direct measurement is not in place. Future refinements of the "outgoing feed reliability' goal will be to measure directly the completion of multiple Worldflight feeds.

Database Maintenance. The applications programming group is responsible for the Database maintenance of the Worldflight System. The loading, updating, and validation of the data entered into the Worldflight database is the responsibility of the user groups that the applications support. Database maintenance does include, file sizing, and the repair of corrupted data that was caused due to programming errors. The Worldflight system supports communications with other systems with both real-time and batch traffic. Worldflight provides real-time feeds to the following systems; Acars—Acars - uplinks, CFT—CFT - Corporate Flight Times, CMS—CMS - Crew Management (NWA), Cargo, MSG—MSG - TTY traffic, Sceptre—Sceptre - Aircraft Maintenance (NWA), Ramp/Fids—Fids - Gate Managemnet, Worldspan—Worldspan - Reservations / Common use, and ODB—ODB - Operations Database. Worldflight has the following batch feeds out; Stats—Stats - statistics, Mapper—Mapper - Fuel Usage (NWA only), Worldspan—Worldspan - Microfiche. Worldflight is updated by the following systems; Acars—Acars - downlinks, MSG—MSG - TTY traffic, Sceptre—Sceptre - Aircraft Maintenance, Worldspan—Worldspan - Pass/Bag information, and ODB—ODB - Operations Database. Batch file feeds into Worldflight; Schedules—Schedules - Airflight System, Aircraft Performance Data (via TSO). Enhancement requests are requests for new funtionality, or requests for cosmetic changes with the functionality remaining the same. These requests will require a Computer Service Request (CSR), and need to be submitted to the Operations Automation group for evaluation and priority assignment. The following will be measured and available on request; System Availability/Outages, Transaction Response Time, and Reliability of Outgoing Feed. N/A Northwest will provide the Worldflight products and services specified herein to Pinnacle during the term of this Agreement at no cost. (See Appendix L1A) 37 ▇▇▇▇▇▇▇▇ ▇▇▇ Worldflight Products/Services System Availability—Availability - This measurement is the availability of the hardware and software within the Building J computer center. Outages of the various pieces affecting Worldflight availability are cumulative—cumulative - that is, an outage to a communications front-end (that affects Worldflight users) is counted as a Worldflight availability outage. This measurement is not the end-to-end availability to the agent or customer at a terminal in the field. Future monitoring tools may provide an end-to-end measurement. Transaction Response Time—Time - This measurement is the mainframe existence time of selected Worldflight transactions. This measurement is not the end-to-end availability to the agent or customer at a terminal in the field. Future monitoring tools may provide an end-to-end measurement. The selected transactions are those transactions within Flifo and Weight and Balance which are interactively used by the customer. Capacity planning has the list of transactions. Note that a future refinement of the response time goal is to measure the response time during periods of stress, such as bad-weather-related massive flight diversions. It is particularly important to have quick response times during these stress situations. The selected Flifo and Weight and Balance transactions are the appropriate transactions to be measured during stress times. Outgoing Feed—Feed - This measurement is the reliability of the daily feed to Stats. After Stats receives the Worldflight feed, the Stats IMPACT job is run. Note that the IMPACT completion is already being measured—measured - when IMPACT does not complete by 6am, a severity 2 Info/Man record is generated. While measuring IMPACT completion is only an indirect measure of Worldflight outgoing feed reliability, IMPACT completion is chosen as the measure for 4thquarter 1996 because a direct measurement is not in place. Future refinements of the "‘outgoing feed reliability' ’ goal will be to measure directly the completion of multiple Worldflight feeds.