CDTI Subgroup (SC-186, WG-1 SG) Status

1. CDTI Subgroup (SC-186, WG-1 SG)Status Sethu Rathinam Randy Bone Jonathan Hammer (Presented to SC-147)

2. Status • CDTI Subgroup was re-activated in Winter 2003 • Meetings in Oct 2003, Jan 2004, March 2004 • Teleconferences between meetings • At least one, more planned • Support from several organizations, including Govt. and Industry • Boeing, Rockwell Collins, Honeywell, MITRE, NASA, GarminAT, UPS, Delta/ALPA, … (not a full list)

3. Status • CDTI scope • All traffic (from different sensors) on the same display • Includes TCAS traffic • Also ADS-B and TIS-B traffic • “TCAS only” displays not prohibited by ASAS MOPS • Naturally “TCAS only” display will be required to meet the TCAS MOPS

4. CDTI Requirements: Overview Application Description & Tech Requirements Selected Applications (RTCA,…) Pre Y2000, informal More Formal, post Y2000 Draft CDTI Appendix (not included in ASA MASPS) (WG-4, WG-1) CDTI MOPS draft (June 2001) (WG-1) ASA MASPS (WG-1/WG-4) Draft: Consensus Needed Derive Reqs, New text required Existing, may need changes Other Guidance And Requirements Feedback as required ASAS MOPS CDTI (WG-1) STP, ASSAP (WG-4) Sethu Rathinam, 28 Apr 2004

5. CDTI MOPS Requirements Process • Collect existing documents to derive/copy CDTI requirements • Perform review • Survey related industry (standards, designs, regulatory) documents and activity • Create issues list for CDTI, collect major and minor issues • Discussion of issues, general consensus on direction and scope • Create detailed issue papers • Discuss issue papers, capture all relevant information (decisions, consensus, disagreements, …)

6. CDTI MOPS Requirements Process • Make writing assignments from mature issue papers • If non-issue or minor issue, writing assignments start early • Disagreements  Surveys, lab evaluations, … • May result in consensus conclusion • Disagreement may continue (state this in a note on the MOPS) • Review written draft material in group, refine • Capture the essence of requirements in group meeting (framework, external requirements) • Prefer no writing “as a group” – assignments will be for 1-3 people, to be reviewed in group meetings or telecons • Merge with ASSAP and STP documentation as ASAS MOPS • Review with WG-4 • [Rest of RTCA Process: Final draft, editorial committee, final version, send out for vote, …]

7. CDTI: Issues • Several issues remain to be discussed relating to TCAS • CDTI will have no effect on how TCAS guidance is displayed (no changes) • CDTI will have no effect on TCAS aural alerts • Needs group discussion with SC-147 in case exceptions are needed • CDTI will display traffic from TCAS sensor in addition to ADS-B and TIS-B sensors • Display “fusion” issues remain to be worked out • Help and participation from SC-147 is solicited • Work on issue papers has begun • Should TCAS position or other position information be used for display purposes? • What criteria should be used to choose the position information? • How should “combined” symbols be displayed when data from traffic is received from more than one source (in addition to TCAS) under no alert, TA and RA situations? • How should the ASAS architecture accommodate TCAS under standard conditions and under various ASSAP failure modes? • Hybrid surveillance (ICAO definition) will have no impact on CDTI • Transparent to the pilots

8. CDTI: Issues • Several other CDTI related issues remain to be worked out • We are in the process of identifying and documenting issues in issue papers • Input is solicited from SC-147 on issues of common issues interest, relating to TCAS being displayed on CDTI

9. SC-186 Relevant Contact Information • Sethu Rathinam [CDTI SG of WG-1] srrathin@rockwellcollins.com • Randy Bone [WG-1 including CDTI] bone@mitre.org • Jonathan Hammer [WG-4 including ASSAP] jhammer@mitre.org