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 Licenses, Private Operating Certificates, etc. . .)
CAWIS does not have the interfaces available to verify these other data types.
CAWIS will allocate a Userid for SDR submissions, to anyone registering with a valid Canadian Aviation document number that is not already in use by another submitter.
Registration url
https://wwwapps.tc.gc.ca/saf-sec-sur/2/cawis-swimn/wsdrs_reg.aspx
The AMO/AOC registration option only allows for 1 userid under a given number, though an organization can ultimately have multiple users.
Subsequent registrations for a given organization need to be done 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
NOTES:
i) you cannot add TC users to any external sdr organization ( only exception is Flight services )
ii) you cannot add a user to more than 1 SDR organization. You will frequently need to create a 2nd userid for some people, otherwise we would remove that user from the 1st account, then add them to the 2nd ( this will not be possible if they have submitted SDRs)
AMO and AOC accounts have completely the same functionality.
The only difference in an AME account is that AME submissions get forwarded to regional Team Lead PMI’s (allocated on TR86) as opposed to a company specific PMI dictacted by the NACIS views.
An AME/AMO/AOC user is sent a confirmation email upon successful self-registration provided that the license number they provide, is verifiable (on AMO_info/AOC_info/AME_info where that number is active) and is not currently in use by another 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.
(Examples: 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).
All non-submitters are encouraged to use the public search facility rather than setting up an account.
Consequently, the requestor will often attempt to register several times, and will create 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. (checks for occurences of M79.organization_id and M79.sequence_nbr 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' (This domain is subject to change in the future due to Shared Services domain issues)
A TC-employee’s CAWIS userid ALWAYS matches 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”.
Add Comment