Trajectory Working Session Defining Data Elements Definitions

September 17, 2013

Bob Humbertson, Booz Allen Hamilton

Dawn McConkey, DigitaliBiz

Note from FIXM Office

• The attached file (copied below) contains the proposed milestones for the FIXM v3.0 development.  Item #6 pertains to the data elements that we are looking to receive from your team, and item #14 indicates our initial proposal to begin our weekly Technical Review Meetings (TRMs) regarding the 4DT data elements from your team.  However, upon further internal discussion, we’d like to begin these TRMs on 1 OCT. 

• Would it be possible for your team to have all of your data elements (with definitions and other characteristics) uploaded to our FIXM collaboration tool NLT 30 SEP?  If you’ll need more time to do so I think that would be OK.  However, we’d still want to get the discussions going with the FIXM stakeholders.

2

Draft FIXM v3.0 Schedule

3

Activity Milestone Notes Lead ActioneeConduct v3.0 kickoff 8/29/2013   FAA

Propose Draft v3.0 Development Schedule 9/12/2013   BAHComplete Initial List of v2.0 Lessons Learned 9/19/2013   BAHComplete Initial Triage of Remaining v2.0 DEs 9/20/2013   StakeholdersRelease Draft v2.1 to Internal Stakeholders for Review and Comment

10/4/2013   EU

Submit Initial Scope of 4DT DEs 10/11/2013  Would like 9/30/13 4DT GroupDefine Draft v3.0 Development Process 10/15/2013   BAH, EUPropose Draft v3.0 Development Process for Internal Review and Comment

10/18/2013 To be discussed at the 10/24/13 International TIM

BAH

Define Final v3.0 Development Process 10/31/2013   BAHDefine Final v3.0 Schedule 10/31/2013   BAHDefine Scope for the Three Iterations 10/31/2013   CCBComplete Final v2.1 for Internal Release 10/31/2013   EU

Refine Iteration 1 Scope 11/8/2013   StakeholdersConduct TRMs for Iteration 1 Development 11/12/2013   BAH

Complete Iteration 1 Development 12/20/2013   StakeholdersComplete Iteration 1 Internal Review, Comment, and Update

1/10/2014 Digest iteration 1 comments, sync FIXM elements (CM, LM, DD), etc.

Stakeholders

Refine Iteration 2 Scope 1/17/2014   StakeholdersConduct TRMs for Iteration 2 Development 1/21/2014   BAHComplete Iteration 2 Development 2/21/2014   StakeholdersComplete Iteration 2 Internal Review, Comment, and Update

2/28/2014 Digest iteration 2 comments, sync FIXM elements (CM, LM, DD), etc.

Stakeholders

Draft FIXM v3.0 Schedule (2)21 Host FIXM Developer Virtual Conference 3/5/2014 Meeting to obtain comments

from greater aviation community. Take advantage of initial mini-global test in Feb, and completion of Iteration 1 (4DT)

FAA

22 Refine Iteration 3 Scope 3/7/2014   Stakeholders23 Conduct TRMs for Iteration 3 Development 3/11/2014   BAH24 Complete Iteration 3 Development 4/11/2014   Stakeholders25 Complete Iteration 3 Internal Review, Comment, and 

Update4/18/2014 Digest iteration 3 comments, sync 

FIXM elements (CM, LM, DD), etc.Stakeholders

26 Complete Comprehensive Review, Comment and Update 5/9/2014 Final look by stakeholders of all FIXM artifacts

Stakeholders

27 FIXM v3.0 DD candidate updated per stakeholder feedback & released to CCB

5/23/2014   BAH

28 CCB review feedback due 6/6/2014   CCB29 FIXM v3.0 DD candidate updated per CCB feedback and 

published as final candidate6/13/2014   BAH

30 Publish FIXM v3.0 final candidate model & schema 7/4/2014 Additional week added (versus v2.0)

MIT-LL

31 Freeze v3.0 Model & Schema 7/25/2014 Same time intervals as v2.0 MIT-LL32 Complete v3.0 Final Package internal QA 8/1/2014 BAH33 Deliver final package 8/15/2014 BAH34 Complete ATIEC Booth Manning Schedule  8/15/2014 TASC35 Complete FIXM ATIEC Docs 8/15/2014 Stakeholders36 Participate in ATIEC 2014 8/26/2014 

- 8/28/2014

Stakeholders

37 Conduct FIXM v4.0 Kickoff 8/29/2014 FAA 4

4D PointIdentifies the location and time of a trajectory point

5

4D Trajectory PointA container for information pertinent to single point in a

trajectory.

6

AirspeedThe airspeed of the flight at the 4D Point expressed as either True,

Indicated or Mach airspeed.

7

Barometric SettingIndicates if the altitude is expressed as geometric or barometric.

If barometric, the assumed barometer setting for the 4DT is indicated.

8

Point Range Provides a vertical, lateral or temporal range to a 4D Point when

clearances are provided in the form of: block altitude clearances, offsets for deviations due to weather or assigned speed

9

Prediction SourceIdentifies the source parameters of the predicted point.

10

Reference PointFor 4D Points that are associated with a waypoint on the

expanded route, the reference point provides the expanded route waypoint enabling the 4DT to be linked with the route information.

11

WindIn predicted trajectory, the instantaneous wind vector used at the

4D Point for creating the 4D Trajectory

12

TCP TypeIdentifies the type(s) of trajectory change point (TCP) being

described by the associated 4D Point.

13