System Profile
...
5008 purpose is to distribute information to owners, to send notices to owners regarding any changes to their aircraft, report hours, report accidents, fill it out in AAIR, notify whether there is safety issue on aircraft.
Good To Know
CAWIS Ext
To address security issues, CAWIS has both internal and external websites. This requires some special consideration when migrating code.
...
2023 CAWIS AAIR Updates:
CAWIS AAIR Updates - 2023-2024
Good
Developer info - running CAWIS
CAWIS Internal - interface not properly displayed. - BSD - Civil Aviation - Confluence (atlassian.net)
CAWIS Links
NOTE : CAWIS has no database links outside of Transport Canada
...
CCARCS | CAWIS pulls aircraft information from CCARCS CAWIS pushes contact data to CCARCS (phone numbers, fax numbers, email addresses) |
NACIS | CAWIS pulls Airworthiness data (AMO, Manufacturer, Distributor along with Principal Maintenance Inspectors (PMIs)) |
AMES | CAWIS pulls AME Licence Numbers |
NAPA | CAWIS pulls type certificates for Airworthiness Directives (ADs) |
DAPLS | CAWIS pulls addresses of pilots |
TC Directory | CAWIS pulls TC user information |
BII | CAWIS pushes Airworthiness Directives (ADs) and Service Difficulty Reports (SDRs) to BII. There also ten canned reports and ad hoc reports Power BII or BII - Civil Aviation's Occurrence Statistics in the Data Warehouse + a suite of BI reports |
Linked folder for ADs to host to the web | development production |
WSDRS and CAWIS were two separate systems. SDRS is now a subsystem of CAWIS holding approximately 2,100,000 records |
Slow / Hanging Reports
| Expand | ||
|---|---|---|
| ||
New reports returning large amounts of data:
were taking too long and sometimes timing out before completing.
The only caveat is that data changes (new or updated records ) won't be reflected in reports until the following day. |
Project Book Report
The Project Book Summary (Release) reports sets the “last print date” to SYSDATE at the time of execution (LAST_PROJECT_BOOK_PRINT_DATE in table TR47_CAWIS_GENERAL_PROPS). Subsequent report will only return data where the issued date is >= LAST_PROJECT_BOOK_PRINT_DATE, or if there is no issue date (NULL - often the case for IN PROGRESS AMOCs)
⚠ Production CAWISP database and CAWIS user⚠
CAWIS is one of the rare application that has access to the schema owner of its objects (CAWIS@CAWISP.WORLD) and as such, one should be very cautious of what he is doing to avoid changing or corrupting objects. While we do have access to such credentials, it should be noted that we do not have permission to use it to modify anything other than data. Structure changes, such as packages, tables, database links and standalone functions, are banned from being done without the DBA group consent.
...
| View file | ||
|---|---|---|
|
How-To and Fixes
AD Document not linking
Check if file properly named
...
| Expand | ||
|---|---|---|
| ||
If the “Last Printed Date” (LAST_PROJECT_BOOK_PRINT_DATE in table TR47_CAWIS_GENERAL_PROPS) gets set to an incorrect date (For instance: Project Book Summary (Release) is executed instead of Project Book Summary (Preview)) it can cause incomplete reports (see note in good to know section above). Users with admin access can change this date through the CAWIS application as follows:
|
Slow / Hanging Reports (158722)
New reports returning large amounts of data were taking far too long, often timing out before completing. Reports were changed to make use of materialized views which reduced time significantly. Reports generally complete in under 5 minutes.
PLANNED OUTAGES
CAWIS can announce planned outages on the login page by performing the following steps:
...
The system will lock out all users (except the ADMIN account) during the specified period. The ADMIN account can log into CAWIS at any point and revise the end date if/when a release is completed early. The Out-of-Service period is displayed at the top of every CAWIS screen during the time period leading up to the planned outage.
Routings
Remove and Replace the old user id who can be retired with another(new) user id (see Task board #269602)
...