1) EXTERNAL REGISTRATIONS
In CAWIS, a valid Canadian Aviation Document number is deemed to be either
SDR User Type 1 - An AME number (Aircraft Maintenance Engineer)
SDR User Type 2 - An AMO number (Approved Maintenance Organization)
SDR User Type 3 - An AOC number (Air Operating Certificate)
Although other valid document types exist (Pilot LicensesLicense, Private Operating CertificatesCertificate, etc. . .)
CAWIS does not have the interfaces available to verify these other data types.
CAWIS will allocate a an active Userid for SDR submissions, to anyone registering with a valid Canadian Aviation document number that is not already in use by another submitter.
...
The AMO/AOC registration option only allows for registration of 1 userid under a given number , though an organization can ultimately have using the public registration page. However, these organizations can ultimately be assigned multiple users.
Subsequent registrations for a given organization need to be done allocated by either
i) User #1 – the first person to register with that number is deemed “SDR manager” for that company – or
ii) Anyone else within that Organization where the Manager flag is set to “Yes” – or
iii) by a Continuing Airworthiness user, normally the Technical Inspectors in the SDR section, or the CAWIS Business manager
important:
i) you cannot add TC users to a External SDR organization ( the only exception is Flight services )
ii) you cannot add a specific user to more than 1 SDR organization. You will frequently need to create a 2nd userid for some people for a 2nd use (an example being an AMO account and a TCH account for a single individual).
Alternately, we could possibly remove that user from the 1st account, then add them to the 2nd ( though this is not possible if they have submitted SDRs)
AMO and AOC accounts have completely the same functionality.
AME accounts have the same functionality as AMO/AOC, the only difference being that AME submissions get forwarded to regional Team Lead PMI’s (allocated on TR86) as opposed to a company specific PMI dictated by the NACIS views.
Example of TR86 data
...
An AME/AMO/AOC user is sent a confirmation email upon successful self-registration provided that the license number they provide, is verifiable on CAWIS tables AMO_info/AOC_info/AME_info (which are refreshed daily - DBMS jobs 181,182,183) The AME/AMO/AOC number MUST be “active” and not currently allocated to an existing user.
All Other (types 4,5,6) registration types are sent to the WSDRS email inbox for management review. No confirmation email is sent to the requestor. This is handled manually by SDR manager decision.
Sample email received by WSDRS inbox for “other” type registrant
...
(Examples of Other-type registrations: media outlets, Flight Training Units, Law offices, research companies, insurance companies, foreign operators with no AOC number, Aircraft owners mistaking this subsystem for a place to enter an AAIR after an EDM).
Most non-submitters are encouraged to use the public search facility rather than setting up an account.
Public search facility
...
Frequently, the requestor will attempt to register several times, and creating multiple redundant Userids in the process. When this occurs, simply change the password to "DELETE" on any duplicate accounts, and the overnight job will perform an auto-deletion, if no reports have been submitted from these accounts. (It checks for occurrences of M79.organization_id and M79.sequence_nbr tied to records on M72)
2) TC INTERNAL REGISTRATIONS
A TC account is defined as a Userid that exists on TC_directory – and/or - has an email address domain of 'tc.gc.ca' (Note: This domain is subject to change in the future, due to Shared Services domain issues)
A TC-employee’s CAWIS userid must ALWAYS match their network login.
TC userids are auto-synced against TC_directory_client every night, keeping contact and addressing info up to date. (for example if an entire branch, like Aircraft Certification, changes locale, we don’t need to update addressing on dozens of individual Userids)
New WSDRS userids for TC personnel should NEVER be manually created in CAWIS/WSDRS - a Userid will be deactivated overnight if it has a "tc.gc.ca" email domain and is not found on TC directory.
For example. when assigning a new user to the TC-Flight services organization (50049450), you need to select the person from the existing users already in CAWIS, not create a new id. (note: Flight Services always requires special case handling for its accounts)
All TC employee Userids are already resident in CAWIS. If a person is not found, that userid will likely be imported during the next overnight sync, provided that TC Access control has allocated the account.(Procedure: CLEANSE_CAWIS_DATA) Another way to verify a new user, is to put the person’s name in the Send-to field of an email, then click “check names”.
Note: PMI registration has been deactivated on the external website, and replaced with a contact email for access. These Userid’s have usually been setup automatically before the requestor asks for access.
Adding a TC user to an internal organization
Step 1 - go into edit mode on an existing user for that organization, click ADD TO ACCOUNT
...
Step 2 - Search for and acquire the user you’re looking for, select them then fill out the form
...