National Traffic Management Log (NTML) Overview

1
National Traffic Management Log (NTML) Overview

• CDM Brief
• March 5, 2003

2
Why NTML? An Overview

• Improved Log Entry Communication
• Between TM, Controllers, Users
• Single Point of Data Entry for NAS TM Messages
• Collect NAS Causal Data
• Key missing element for NAS operational analysis
• Integration with ETMS, OPSNET, OIS, ESIS, ERIDS,
  FSM, Outage DB, SUA . . . .
• Movement towards a decision support tool

3
Program Challenges

• Network bandwidth
• Integration of two independent networks
  (ETMS/ADTN)
• Integration across different types of facilities
• Wide range of locally developed software used in
  individual facility TMUs
• Need for additional hardware (Linux PCs)

4
NTML User Workgroup

• TM User Team (TUT) Working Group (WG)
• First WG established under the TUT Committee
• Regularly scheduled meetings and OTEs
• Biweekly telecons
• Joint Management / NATCA membership
• Focal point for operational development
  priorities
• End User Feedback
• Workshops and Ad Hoc local user meetings
• Formal and informal user feedback (Application /
  Web Site)
• Bring SMEs into WG meetings

5
Deployment Strategy/Timetable

• Tier 1 Six west Centers
• Focus on DCC 11 22 and associated facilities
• Version 3.0 successfully completed on Dec 12,
  2002
• Tier 2 Continue movement East and Southeast
• DCC 12/24/16 and associated facilities
• Targeted for March 31, 2003
• Tier 3 Add remaining facilities (Northeast)
• Version 3.1 - ESIS / MyEntries/Output mappings
  (April 03)
• Version 3.2 - View/Log filters current only
  (Summer 03)
• Version 3.3 - SWAP / SIA (Winter 03)

6
(No Transcript)
7
Program Enhancements in Tier 1 (Version 3.0
Dec 02)

• Improved look/feel
• User interfaces (GUIs)
• Template redesign
• Menu redesign
• Template redesign
• RSTNs, GS, Free form, Delay, Runway
• Pending box and view dialog improvements

8
Program Enhancements in Tier 2 (Version 3.1 -
April 03)

• ESIS Database Table Access (Link between TMU
  operational areas)
• Ability to save and recall entries
• Enhanced views, pending, and interfaces
• Revised output mappings (Reduce size of log)
• OIS integration (single point of entry)

9
Program Enhancements in Tier 2 (Version 3.2 -
Summer 03)

• ESIS Database Table Access (Link between TMU
  operational areas)
• Ability to save and recall entries
• Enhanced views, pending, and interfaces
• Revised output mappings (Reduce size of log)
• OIS integration (single point of entry)

10
Program Enhancements in Tier 3(Version 3.3
Winter 03)

• Status Information Area (SIA) (TMU heads-up
  display)
• SVR WX (SWAP/RERTE/RTE closure status)
• Smart use of ETMS Parse-able advisories
• ERIDS (link between TMU, OPS Sup, and TMU)
• Make data available to airlines via web site
  (Spring 2K IOU)

11
NTML Planned NTML Data Flows
ATT-220