FLEET AAIR - DATA MAINTENANCE

Current Status - FLEET/CLIENT associations are NOT automatically maintained. Many aircraft change ownership over a given year, and its not unusual for the fleet files to be in need of dozens of revisions.

An aircraft erroneously left within an incorrect fleet will be unable to submit an AAIR via the web until that data is corrected.

Background

Late 1980’s through 2010

Fleet AAIR submission was Created at the outset of the AAIR program to allow larger carriers to submit their AAIR data via spreadsheet or Word Document, rather than fill out dozens of paper forms.

This method of submission is embedded in Chapter 501 of the regulations for AAIR submission

https://tc.canada.ca/en/corporate-services/acts-regulations/list-regulations/canadian-aviation-regulations-sor-96-433/standards/chapter-501-annual-airworthiness-information-report-canadian-aviation-regulations-cars#toc_501_01

During this period, regional users maintained Aircraft/Fleet membership manually and sent a hardcopy mail reminder, with a list of aircraft to the operators each year then entered the data received into CAIS ( the mainframe predecessor to CAWIS)

CAWIS early 2000’s

CAWIS adopted the same functionality as the old mainframe system.

Fleets are defined by a record on Y59, by a matching fleet number on Y02.

It was agreed that regional users would continue to manually maintain their own fleets and that fleet operators would not be permitted to do their own web submissions

2010

All FLEET maintenance and data entry was taken over by the Publications unit at NCR

Mid-2010’s – CAWIS/WCAG redesign

CAWIS was enhanced to gather all AAIR data for each FLEET into a single PDF for annual emailing to each Fleet owner. (Annual Fleet notification )

It was also requested that fleet maintenance be automated to add/remove aircraft for existing fleets.

A FLEET CONTROL TABLE was created within the Z980_Term_conversion table, defined like so

TERM_TYPE_CD = “FLEET”

FROM_TXT     = CLIENT_ID

TO_TXT       = FLEET_NUMBER

The control table allows automation to be performed, by either bringing into a fleet, or removing from a fleet, any aircraft found to be owned by the client_ids tied to each fleet number

(NOTE: a Fleet number can have ANY number of client_ids associated to it)

These routines were part of the overnight batch job.

Issues :

The Publications unit does not have an online interface to ADD/REMOVE client_ids/fleet ids from the control table. Thus any group of aircraft removed from a fleet having a matching Client-id, simply get re-added overnight

Note: Publications occasionally have submitters, that just want 1 or 2 aircraft removed from their fleet only for a few days in order to perform their own web submissions. Fleet automation does not allow for this.

Adding aircraft for a new client to an existing fleet, would simply see them removed from that fleet overnight unless the the Z980 control table was updated with the new client_id associated to that fleet number

There existed no report which would tell them how far “out of sync”, each fleet had become.

So the “fleet automation” routine was discontinued (commented out of the overnight job)

A suggestion that it only be invoked one time each month, was also rejected.

[ER] RECOMMENDATIONS

1 The Fleet maintenance report needs to be available from the CAWIS REPORTS menu -or- the Fleet AAIR menu, (showing which aircraft need to be removed from fleets and which need to be added) This report can be generated using the Z980 control table (client-id/fleet number associations)

2  The FLEET CONTROL TABLE (Z980 where TERM_TYPE_CD = “FLEET”) needs to be updateable by the users (Publications unit) It should be added as an ADMIN function on the Fleet maintenance menu, allowing the user to add/remove fleet/client relationships - There have been many instances where CCARCS alters a client_id for a large company -or- creates a new client_id for another company Owned by the client of an existing fleet, and Z980 needed to be modified on the back end.

The FLEET AAIR MODIFY PAGE

Mostly behaves as discussed under Create NEW (CREATE NEW )

Open