Overview

see also (I have not gone through all of the documents in these links yet)
CAWIS 5008 FILE MAINTENANCE
CAWIS (AAIR) ANNUAL AIRWORTHINESS INFORMATION REPORTING

• TC login uses the TC login ID but the password is not the same.

• For TC Login, the same credential works on both CAWIS internal and external. 

• I have provided access for the TC Login option on CAWIS development and acceptance to all members of the maintenance team. 

• Maintenance team have access to CAWIS prod for maintenance purposes only (Only for work related to tasks submitted by the client. No changes can be made without approval from the client)

• AAIR does not use our TC Login credentials.

• AAIR login is unlocked on CAWIS external for development and acceptance.

  • The same AAIR credentials work on both CAWIS external and internal

  • AAIR login is currently purposely locked on prod per work that Hiren and I collaborated on in March 2023

  • See also https://dev.azure.com/transport-canada/DSD-CIVAV%20Support/_boards/board/t/AAIR/Backlog%20items

• AAIR login is locked on all CAWIS internal instances (development, acceptance and production).  

  • See Subtask 301363 https://dev.azure.com/transport-canada/DSD-CIVAV%20Support/_boards/board/t/AAIR/Backlog%20items

  • Should the option for AAIR login be displayed on CAWIS internal?

Business Rules:

• AIRCRAFT CANNOT BE SALE REPORTED OR INVALID ADDRESS       

• THE AIRCRAFT CANNOT BE A MEMBER OF A FLEET                 

• THE AIRCRAFT CANNOT BE LISTED AS OUT-OF-SERVICE           

• THE AIRCRAFT CANNOT HAVE HOURS ALREADY RECORDED FOR THE REPORTING PERIOD (CURRENT YEAR - 1) 

• THE AIRCRAFT CANNOT BE LISTED WITH A YEAR OF MANUFACTURE EQUAL TO THE CURRENT YEAR

• THE AIRCRAFT CANNOT BE ULTRALIGHT/ADVANCED ULTRALIGHT     

• THE AIRCRAFT CANNOT BE DEREGISTERED

Backups of development and acceptance code deployed to servers

...

AAIR Accounts on development and acceptance:

Developers

• Developers (currently Noreen and Dean) have individual AAIR accounts on development and acceptance.

  • Alain also has an account on development.

  • Additional accounts can be created - see the instructions in this document.

Shared accounts

• Sylvie created several accounts for different scenarios on acceptance.
  

• The following shared accounts are applicable on both development and acceptance:

  • On development, the email address for these shared accounts is set to our shared CAWIS development mailbox.

    • The email box address is cawis-dev-swimn@tc.gc.ca

Configuration:

See: