DCIT Document Hierarchy

1. DCIT Document Hierarchy Procedures and operational system features effecting multiple organizations End-to-End Detailed system features and interface definitions affecting multiple organizations Systems Integration Document Flight Deck Guidance Detailed aircrew procedures affecting multiple organizations Local procedures(Tower, AOC, Flight Deck) Local systems design and requirements material(Tower, AOC, FAA) Detailed system features and interface definitions affecting individual organizations Detailed procedures affecting individual organizations

2. How do we manage this? • We are already on a path for ONE set of documents for all of Phase 1 • We need baseline documents for any Phase currently in progress • Includes all documents in the hierarchy set • Provides the baseline for trouble-shooting (procedural and system) • Provides the baseline for metrics and reporting • Provides the baseline for anyone wanting to add • We need baseline documents for any future Phase • Includes all documents in the hierarchy set • Provides procedural and system design baseline • Provides a means for metrics and reporting to convert from one Phase to the next • Provides a means for tracking operational and system changes from one Phase to the next • We should really be doing one for the Operational Phase (TDLS) • We will do this by carrying specific document versions, for each Phase • Phase 1: Version 1.x documents. • Phase 2: Version 2.x documents

3. 22-Jan-13 10-Feb-13 4-Mar-13 4-Apr-13 4-Aug-13 SUCCESS CRITERIA Functional and Ops E to E checkout E to E document verification UM79, 80 and CAF Validated by dedicated crew, controller and dispatcher SUCCESS CRITERIA Full Service Validation Validated by technical dispatcher, flight crews and controllers Local interview based data collection Questionnaires SUCCESS CRITERIA Validated by line controllers, pilots and dispatchers Integrated into daily Ops Log Based Statistical Analysis Volpe interviews Questionnaires