TAB-1 GENERAL
DATA ELEMENT OR BUTTON | DESCRIPTION |
Number | allocated on initial Save |
Parent Project | no longer used - Described in ADD New section |
Revision | Revision Number (corresponds to the Revision number of the AD Publication ) |
Suffix | no longer used - Described in ADD New section |
Project Type | Project Type Becomes unchangeable once the project number is allocated. Values Described in ADD New section  |
Name | Project name, freeform text |
OPI | Office of Primary Interest / Project originator |
OTI | Office of Tertiary Interest / Secondary project contributors/other users with interest in this project |
Details | freeform text - should ultimately contain any Publication number raised by this project |
Reference | freeform text |
SDR_number / ADD | user manually enters SDR numbers that apply to this project (SDR-number must exist on M72) |
SDR REFERENCE | list of SDR numbers |
MANUFACTURER | SDR product manufacturer (determined from Product code on M72, then data is acquired from M73 by SDR-number, product-code match) |
MODEL | SDR product model |
CATI | Continuing Airworthiness Technical Inspector responsible for this Mfg/model - determined by the Personnel code allocated on Y62 table |
Comments | freeform text |
last updated | last update date |
updated by | name of user who last updated this project |
contact | User phone number (CAWIS userid tables are auto-synced against TC Directory) |
Project Summary | freeform text |
Start Date | date project started |
Due date | due date - if left blank the user receives the following warning regarding the project stats report :  |
Percent completed | estimated percentile of project completion |
Priority code | values  HIGH is normally reserved for Emergency ADs |
Status code | values  Note : will not allow a project to be saved as “closed” unless the percentage complete is set to 100% |
Date completed | completion date |
Closing reason | freeform text |
Lessons Learned button | User can enter any Lessons Learned text  |
Question button | User can enter questions for the Project OPI - the OPI receives email notification as well. Tab 2 shows Question history   |
Summary | provides a brief online summary of the project  |
Revise | Create sequential revision to this project. This is only done in instances where a Revision to the Airworthiness Directive published from the original project is being revised |
Comprehensive report | provides details of all aspects of this project online  |
SAVE | SAVE project |
BACK | go back without SAVE |
TAB-2 APPLICABILITY
DATA ELEMENT OR BUTTON | DESCRIPTION |
TYPE | mfg/model Product Type (A/E/P/F/S/Q) |
MANUFACTURER | PRODUCT MANUFACTURER |
MODEL | PRODUCT MODEL |
TYPE CERTIFICATE | TATC - TYPE APPROVAL -OR- TYPE CERTIFICATE assigned to this Mfg/model on Y62 |
PRIM | PRIMARY ? Identifies the Primary Mfg/model that concerns this project |
ADD | Add more Product/Mfg/models to the applicability of this project. Mfg/models can also be acquired by entering a specific aircraft tail mark at this point  |
REMOVE | remove any unwanted models from this project |
JASC1 | Assign JASC/ATA code to this project (JASC code identifies the specific problem area/system of the aircraft)  |
JASC2 | assign a 2nd JASC code |
JASC3 | assign a 3rd JASC code |
TAB-3 ATTACHMENTS
DATA ELEMENT OR BUTTON | DESCRIPTION |
CHECKBOX | Select document for action (remove or view) |
TITLE | Title/Description/Summary of document contents |
FILENAME | filename of document |
RDIMS | RDIMS number and link |
ENTRY DATE | date of entry |
OPI/OTI ONLY | restrict access to the OPI/OTIs for this project only |
ADD | Add another attachment - or - RDIMS document  Due to security issues, the following attachment types are NOT permitted CER, CSH , EXE ,INS , JS , MCF , MDB , HTM , HTML |
REMOVE | remove any attachment from this project |
OPEN DOCUMENT(S) | highlight any number of documents with the clickbox, then Open documents |
OPEN RDIMS DOCUMENT(S) | highlight any number of RDIMS documents with the clickbox, then retrieve docs from RDIMS |
TAB-4 BF NOTIFICATIONS
DATA ELEMENT OR BUTTON | DESCRIPTION |
CHECKBOX | Select BF for action (remove or view) |
WHAT | Description of BF task (freeform text) aka: Outstanding Actions (M11) |
WHO | responsible individual (freeform text) |
BF DATE | expected BF date ( This will send email notification to the OPI once this date has been passed without a completion date) |
COMPLETION DATE | actual completion date |
ADD | ADD a new outstanding task  |
modify | modify details of outstanding tasks |
remove | remove outstanding task |
TAB-5 LINKS
DATA ELEMENT OR BUTTON | DESCRIPTION |
CHECKBOX | Select for action (remove or view) |
NUMBER | Linked project numbers |
NAME | Subject/Name of linked project |
START DATE | Start Date of linked project |
PRIORITY | Linked project priority |
OPI | OPI of linked project |
ADD | ADD another project link to this project  |
REMOVE | remove a linked Project from this list |
LINK TO NEW PROJECT | Create a NEW project, with the current project we are working on, linked into it |
CORRECTIVE ACTION - COUNTRY | Country of the AD created by this project (allocated, routed and published on the Corrective action tab) Note: always Canada |
ENGLISH | Link to English copy of AD |
FRENCH | Link to French copy of AD |
AD Number | Airworthiness Directive Number |
Linked AMOCs | any Alternate Means of Compliance documents (AMOC) later linked to this AD and Project |
TAB-6 CORRECTIVE ACTION
DATA ELEMENT OR BUTTON | DESCRIPTION |
NOTES | freeform text |
CHECKBOX | Select for action (remove or modify) |
TYPE | Publication type - values  |
RDIMS NO | link to document in RDIMS |
EMERG | Was this issued as an Emergency AD? |
CIRC STAGE | Circulation Stage (AKA Routing Stage)  |
STATUS | Publication Status  |
PUB? | Has this item been published ? |
ADD | add another publication item to this project |
MODIFY | begin the routing stage  |
REMOVE | remove this publication/RDIMS link from the project |
Routing stage
-or-
GENERATE - opens a DOCX file containing a standard TC AD template. The User fills in the AD document and uploads it RDIMS
ROUTE - opens a routing template to circulate the AD document for review by CAW (managers, Chief, engineers, inspectors, publications unit )
BUTTON | DESCRIPTION |
|---|---|
BACK | go back without initiating routing |
NOTIFY NEXT | Notify next reviewer |
INSERT NEW | Insert a new recipient |
VIEW | view routing recipient and enter comments, if desired previous route = show previous recipient next route = show next recipient  |
REMOVE | remove routing recipient |
RESTART ROUTING | restart the routing process, if necessary |
SHOW ALL STAGES | see below - Displays ALL stages of the routing process |
Notify Next
the blue arrow indicates what point of the routing process has been reached
INFORMATION PROGRAMS
Through the routing process, the document is passed to the Information programs section
DATA ELEMENT OR BUTTON | DESCRIPTION |
VIEW | view IP record |
MODIFY | modify IP record |
REMOVE | delete IP record |
print IP record | |
SELECT | identify IP record for action |
NUMBER | Publication number (usually an AD number -or- an SDR number for a feedback article ) |
TYPE | Publication type - values |
PROJECT NO | Project number that originated this publication |
PROJECT NAME | Name of project |
ORIGINATOR | OPI user |
STAGE | Publication routing stage  |
NAME AND DESIGNATOR | Name and designator (from A32 table) of the current person in the routing (and an indication of overdue conditions, where warranted) |
RDIMS NO | RDIMS number for this publication |
SENT | sent to publications date |
RETURNED | returned by publications ? Can find no occurrences of data in this column |
Modify mode
TAB-1 GENERAL INFO
DATA ELEMENT OR BUTTON | DESCRIPTION |
PUBLICATION NO | Publication number - Usually the AD number -or- SDR number for Feedback article |
REV/ED | Revision number ? |
ENTRY DATE | Entry date that project/publication was passed to Information Programs (aka Publications Unit) |
ISSUE DATE | Date of publication/distribution |
STATUS | status of publication/distribution - values  |
EMERGENCY | is this an emergency AD ? ( distribute ASAP, short compliance time for operator ) |
COORDINATOR | Primary coordinator in Publications unit |
ALTERNATE COORDINATOR(S) | Any secondary coordinators in Publications unit |
RDIMS NO ENGLISH | link to English version |
RDIME NO FRENCH | link to French version |
LAST REVIEWED BY | last user reviewed |
LAST REVIEWED DATE | date |
PROJECT NO | Project number that produced this document |
PUBLICATION TYPE | Publication type |
ORIGINATOR OPI | Project OPI |
PRIORITY | Project priority - values  |
NAME | Project name |
TRACKING SHEET | Generate printable tracking sheet |
PTS PROJECT | Go to PTS project |
QUESTION | Go to PTS project (did take user to Question submission for project #20190002 in ACC region) |
SUMMARY | Go to PTS project (did not produce summary on project #20190002 in ACC region) |
TAB-2 ATTACHMENTS
DATA ELEMENT OR BUTTON | DESCRIPTION |
SELECT BUTTON | select attachment row for action |
TITLE | Title of attachment - freeform text |
FILENAME | Filename of attachment |
RDIMS | RDIMS number/link |
DATE ENTERED | date attachment entered |
ADD | ADD new attachment |
REMOVE | Remove existing attachment |
TAB-3 ROUTING AND DISTRIBUTION
at this point, the project is pointed to the PRINT AND DISTRIBUTION part of the task (“show active stage”)
The “show all stages” function reveals the full routing, if it needs to be reviewed. Routing can still be modified at this point.
DATA ELEMENT OR BUTTON | DESCRIPTION |
ACT | select routing row for action. This button is only activated by the EDIT Routing button at the bottom |
SENT TO | person publication sent-to for review |
SENT TO (DATE) | date sent |
BF DATE | due date |
RETURNED | actual returned date |
COMMENT | comments - freeform text |
EDIT ROUTING | ADD or Remove users from this routing |
printed, signed and retained in Hard copy
0 Comments