Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

System Profile

System Full Name

Civil Aviation Issues Reporting System

Business Administrator(s)

Sarah Lamarche , Geneviève Bourgeois

Business Owner(s)

Sarah Lamarche , Geneviève Bourgeois

Director

Angèle Saumur

Subject Matter Expert

Mike Clark

Division

NTARS Code

CA07

Source Location

data, documentation and source code is backed up at
\ncras22\CSSG Release\CSSG Staging\CAIRS\PROD [C254090]

Source Code Location

http://ncras479:8080/tfs/CivAv/Cairs-Ssqac_Internal/_versionControl

http://ncras479:8080/tfs/CivAv/CAIRS-SSQAC/_versionControl

Technology Assessment

Platform Type

Web (Internal)

Database Platform and Version

Oracle 11g

Development Language and Framework

.NET

Operating System and Version

Windows Server 2016

Additional Dependencies

Authentication

Environment Access Information

ENV

UNC

WWWFILES

URL

DB

DEV

CAIRSD

PREACC

PREACC_CA

ACC

CAIRSA

PROD

http://tcapps.tc.gc.ca/Saf-Sec-Sur/2/cairs-ssqac/; https://etp.tc.gc.ca/truepass/cairs_ssqac

CAIRSP

TRAINING

CAIRST

System Overview

<--->The Civil Aviation Issues Reporting System (CAIRS) provides Transport Canada employees with a means to
raise issues (concerns, complaints, compliments, and suggestions for improvement), and identify hazards to
management. External stakeholders may also raise issues with Transport Canada through CAIRS.
As a basis for a reporting culture, CAIRS seeks to address issues quickly and at the lowest possible level
before a need to resort to a formal redress process exists. It does not prevent a stakeholder or employee from using any other established redress mechanism or reporting system.

CAIRS was formally decommissioned April 2022. (SMGS Change number 254090, PBIs 132507, 132508)

All data, documentation and source code is backed up at :
\ncras22\CSSG Release\CSSG Staging\CAIRS\PROD [C254090]

Good To Know

...

ATTACHMENTS

CAIRS User Guide

How-To and Fixes

<Sub-sections should describe how to address known support request, including any scripts, instructions / steps, etc… >