SC 214/WG 78 Tracing and Validation

1. Jim Dieudonne kayaking down his street in North Carolina today SC 214/WG 78Tracing and Validation John Gonda/Fred Picard

2. Objectives of Today’s Discussion • Review Tracing Resources • Update required trace status and VA assignments • ORs • Irs • SRs/PRs • Review some Tracing Results • ORs • IRs • SR/PRs • Discuss DOORS • Disposition of tracing materials until entry into DOORS • Timing of tracing completion and actions

3. Closing the Loop – Global StandardsRTCA – EUROCAE Joint Development Environment Review & Revision Technology Independent & Portable Service Definition Operational Service Definition Operational Safety Analysis Operational Performance Analysis Validation and Tracing Global Safety & Performance Requirement Definition Interoperability Requirement Definition- ATN - FANS Accommodation Operational Services and Environment Definition (OSED)

4. SC 214 Tracing Resources • Operational Requirements • John Gonda • Ron Tornese • Brent Blackwell • Ed Brestle • SRs and PRs • Kathy Devito, Wim Brondsema • IRs • Fred Picard, Thierry Lelievre, Pascal Rohaut • DOORS • Tonyia Bellina

5. SC 214/WG 78 Requirement Tracing Guidelines Required by both the SC 214/WG 78 CSG and VSG • ORs to ORs • Operating Method (OM) Tables to OM Tables • Section to Section • ORs to sections where ORs do not exist • Safety Requirements (SRs) to SRs • Performance Requirements (PRs) to PRs • Interoperability Requirements (IRs) to IRs

6. Agreement • Fred agreed to do the SC214/WG78 trace between the Mixed Interop and FANS Interop. • This was identified at the last Langen meeting • The hidden trace between ICAO 9705 and Draft 9880 is complete • and contained in the version 9880 Fred maintains • The message trace already completed by Ron Tornese and Paul Debenedittis is recommended as a candidate for a validation activity

7. SC 214/WG78 Tracing Requirements VSG-VA2 VSG-VA1 VSG-VA5 VSG-VA3 VSG-VA4 VSG-VA10 VSG-VA11 VSG-VA6

8. Internal Validation Activities

9. Internal Validation Activities (cont)

10. Internal Validation Activities (cont)

11. Data Comm DOORS Modules • Create Modules • Clean – Remove extraneous formatting and paragraph • Apply – Style Template • Import into DOORS • Create Link Modules (Relationships) and Links (Tracing) • Create Documents – Export • Program Requirements • Engineering Management Reports - Requirements Metrics, Status etc • Manage Change – Data Comm DOORS Change Management

12. Creating Modules/Link Modules/Links Unlimited number of linked modules and captured links.

13. Data Comm DOORSRelationships of Modules = Links (Tracing)

14. Rejected (Status) 1.) Collect input/comments from all Subject Matter Experts/Reviewers 4.) DOORS Attributes Updated 5.) DOORS Module Updated Approved Changes Pending (Status) Approved Pending Rejected 3.) Bugzilla Coordination of Review (auto email notification) 2.) “DCP DOORS Change Request Form” “DDCR” entered into attributes Data Comm DOORS Change Management

15. Future Activity • Complete Templates for VAs • Complete Tracing for CSG and VSG by Next Plenary • Start migration into DOORS

16. Backups

17. Data Comm Avionics Capability vs Implementation Target Meets All NextGen OIs Planned Existing FANS 2

18. Closing the Loop - Capability vs Equipage Existing Planned

19. SC 214/WG 78 Direction of Trace

20. DCP Requirements Tracing Flow MITRE OI SE DO-306/ED-122 DO-258A/ED-100A DO-305/ED-154 Vendor One way trace SPR FANS-1/A– ATN Interop ATN Interop LM/OKC/DCNS Build FPR ESSD/WSSD/DCNSD ??????? New ATOP Build SSSs/SRSs/IRDs 214 Aircraft

21. Objective • Do one set of traces to suit the needs of the following: • SC214/WG78 • FAA DCP • FAA AVS • Others • Does not include Data Comm Program specification traces such as SSD to SC 214 etc • Use Excel to do the basic work • Intent is to port over to DOORs at the appropriate time

22. RTCA SC 214/EUROCAE WG 78 SPR Status • Draft Version H (incl ATN/FANS Interops) posted on a public website http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/techops/atc_comms_services/sc214/ • OEMs are building the SW applications • Configuration control has been instituted • Validation of the SPR is underway • Oceanic/Domestic Integration target - Version I • Green/Grey cover documents planned by December 2011

23. Closing the Loop with 4D Trajectory Data Communications

24. Closing the Loop on Interoperability DO-280B/ED-110B ATN Baseline 1 Continental Services DO-258A/ED-100A FANS 1/A+ Continental and Oceanic Services DO/ED-YYY ATN Advanced Continental & Oceanic Services Air INTEROP Req. ED-110B ED-100A DO/ED-YYY ATN INTEROP Ground INTEROP Req. ED-154 DO-305 ED-110B ED-100A DO/ED-YYY FANS INTEROP DO/ED-YYY DO - 280 / ED - 110 FANS 1 / A + ATN Advanced ATN Baseline 1 Oceanic Services Continental & Continental Services Oceanic Services

25. Closing the Loop on Equipage CNS Data Collection Carrier Model Serial # Tail # Date of Mfg. #1 CDTI? EFVS? FANS? GPS? HUD? Equipage TAP/ CDA? ASAS? RNAV? RNP? Capability Etc. Confidence Building Equipage Analysis By tail number Detailed User Feedback Service For Equipage

26. Closing the Loop – FMS Software Migration to NextGen Communications

27. Closing the Loop for NAS Users • Data Communications Software Applications • Context Management (CM - Log On) • Controller Pilot Data Link Communications (CPDLC) • Automatic Dependent Surveillance – Contract (ADS-C) • Flight Information Services (D-FIS) • New Operating Methods • Integration between navigation and communication functions for route auto load, position reporting and intent downlink • Improved use of Human Machine Interface for Requests • Trajectory based, closed loop operations • No major hardware replacement • If aircraft has capable CMU, radio and FMS • Maximize existing avionics through software upgrades