WORKSHOP ON DEVELOPMENT & CERTIFICATION PROCEDURES FOR CNS/ATM SYSTEMS. 17 July 2017

Transcription

1 WORKSHOP ON DEVELOPMENT & CERTIFICATION PROCEDURES FOR CNS/ATM SYSTEMS 17 July 2017

2 systems and services (1/5) Benchmarking Market survey: features vs. needs, total cost of ownership ANSP: how is the system operated, issues faced during acceptance and transition, etc Could be used to pre-qualify certain suppliers using transparent criteria and careful evaluation Draft the tender document based on your regime and procedures Acceptance (factory and onsite, initial and upgrades) and safety assessment of changes Certification and surveillance, including safety assessment of changes Re-use acceptance tests/certification basis with caution Some suppliers have a basis ready (product policy) could be reused but must be carefully complemented in the local operational context Certification basis: subject to MOU between CAA, could be reused but must be carefully complemented in the national regulatory framework ICAO TCB can assist (CAPS) In any case, responsibility rests with State authority or the organization authorized by the State (ANSP) following the accepted procedures CNS/ATM systems Flight inspections 2

3 systems and services (2/5) Procurement strategy Various possibilities : Is a grouped procurement with other ANSP opportune? Feasible? Collaboration with suppliers for joint development & production? Proof-of-concept method, prior to award of procurement? Competitive process Weighted criteria Best value for money Life cycle cost considerations Users club 3

4 systems and services (3/5) Include applicable standards for the system/services purchased standards in the background (selection)/maintenance in the foreground (may have a cost) ICAO SARPS and their latest amendments, guidance material (manuals etc) National regulations, standards, means of compliance and their latest amendments Compliance = weighted criterion in the selection Require detailed evidences of initial compliance of the design in the technical offer Standards User requirements Require the contribution of the vendor to the safety assessment process Design assurance, Service Level agreements, hazard registers, etc Agree on responsibility of ANSP (integrator) and supplier Manage the buying unit of ANSP as a safety interface to the ATS provider (Safety Management Manual) 4

5 systems and services (4/5) Describe expected contributions to training process should NOT rely only on supplier's syllabus (not competency-based) but also considers new operating procedures developed by a pioneer team Describe expected contributions to Validation &Verification (V & V) process conducted by the ANSP V&V should NOT rely only on suppliers s standard tests but also include free tests (FAT/SAT/shadow/ghosting/live trials) with traceability to user requirements Depending on complexity, consider supplier s on-site support during transition Maintenance: Inspection of faults and escalation process corrections/changes management Contract wise (costs), use metrics based on impact analysis of the change Liability and Intellectual Property Rights 5

6 systems and services (5/5) Executing the contract Pay respect to the contractual terms and conditions Check standards compliance in the V&V process (sampling possible) Safety assessment Include list of system failures in your Hazard identification (as hazards/causes/conditions) Derive safety requirements (SHEL model) and apportion relevant requirements to the supplier Collect evidences from supplier Buy-in from users Readiness of maintenance staff Contingency planning during phasing in of new system/service Big bang approach or incremental phasing in of new system/service Train ATSEP on procedures to maintain continuously the ALOS while operating a CNS/ATM system delivered by industry (change of software, hardware, to the dataset, SOP, OEM documentation) Depending on criticity certain tasks may fully involve the supplier s onsite support These practices can also help exporting States to guide their industry as to what to develop 6