Trials Management Plan
Issued: August 12, 2013
Data Communications Implementation Team
(DCIT)
Departure Clearance Service (DCL) Trials
Phase 1
Trials Management Plan
Issued
August 12, 2013
Trials Management Plan
Issued: August 12, 2013
Help Desk
1-877-384-NOCC (6622)
Option 3, then Option 1
DCL Service ID
EWR: FTIH-DC-041021
MEM: FTIH-DC-041020
Support Contact Information  Page 1 of 34
Trials Management Plan
Issued: August 12, 2013
DOCUMENT REVISION RECORD
Rev.
0
Date
8/12/13
Author
Sean St. John
Change Summary
Issued
Revision Record  Page 2 of 34
Trials Management Plan
Issued: August 12, 2013
TABLE OF CONTENTS
1
1.1
2
2.1
2.2
2.2.1
2.2.2
2.3
2.3.1
2.3.2
3
3.1
3.2
3.2.1
3.2.2
3.2.3
3.2.3.1
3.2.3.2
3.2.4
4
5
6
6.1
6.2
6.3
7
7.1
7.2
7.3
8
9
10
10.1
10.1.1
10.1.2
10.1.2.1
10.1.2.2
10.1.2.3
10.1.2.4
10.1.2.5
10.1.2.6
10.1.2.7
INTRODUCTION ...............................................................................................5
Scope .................................................................................................................5
TRIALS OPERATION .......................................................................................6
Operations Management Working Group (OMWG) ..........................................6
Limited Trial Operations .....................................................................................7
Flight Coordination and Participation .................................................................7
Operations Management Working Group (OMWG) ..........................................7
Normal (Full) Trials Operations..........................................................................7
Flight Coordination and Participation .................................................................8
Operations Management Working Group (OMWG) ..........................................8
SCHEDULED OUTAGES..................................................................................9
DTAP Navigation Database Update Procedures...............................................9
Software Patches and Configuration Updates...................................................9
Overview ......................................................................................................... 10
WJHTC Patch Testing Procedures ................................................................. 10
Site Specific Test Procedures......................................................................... 10
Site Patch Functional and Interoperability Testing ......................................... 11
Site Acceptance Testing ................................................................................. 11
DTAP Certification .......................................................................................... 11
DTAP CERTIFICATION ................................................................................. 12
TRIALS ISSUE IDENTIFICATION AND RESOLUTION PROCESS ............. 13
SHAREPOINT ................................................................................................ 14
DCL Operations Tracking ............................................................................... 15
DCL Operations Issue Tracking ..................................................................... 16
DCIT Action Tracker ....................................................................................... 17
TRIALS DATA COLLECTION ....................................................................... 18
Health Monitoring ............................................................................................ 18
Benefits Analysis ............................................................................................ 18
Airline Survey .................................................................................................. 18
NEW AIRLINE PARTICIPATION ................................................................... 19
GLOSSARY .................................................................................................... 20
APPENDIX A .................................................................................................. 22
DTAP Navigation Database Update Procedures............................................ 22
Introduction ..................................................................................................... 22
Monthly Steps ................................................................................................. 22
Coded Instrument Flight Procedures (CIFP) Published ................................. 22
Thales Data Preparation & Test ..................................................................... 22
WJHTC Data File Validation Test ................................................................... 23
Coordination and Notification.......................................................................... 23
Field Installation of Database files .................................................................. 23
Issue Resolution ............................................................................................. 24
Delivery of Data and Reports.......................................................................... 24
Table of Contents  Page 3 of 34
Trials Management Plan
Issued: August 12, 2013
TABLE OF CONTENTS (continued)
11
11.1
12
12.1
12.1.1
12.1.2
12.1.3
12.1.4
12.2
12.3
12.3.1
12.3.1.1
12.3.1.2
12.3.1.3
12.3.1.4
12.3.1.5
12.3.1.6
12.3.1.7
12.3.1.8
12.3.1.9
12.3.2
12.3.2.1
12.3.2.2
12.3.3
12.3.3.1
12.3.3.2
12.3.3.3
12.3.4
Appendix B .................................................................................................... 27
Site Specific Test Plan Example ..................................................................... 27
Appendix C .................................................................................................... 28
Trials Issue Identification and Resolution Process ......................................... 28
Process Objective ........................................................................................... 28
Process Requirements ................................................................................... 28
Assumptions and Dependencies .................................................................... 28
Definitions ....................................................................................................... 29
Process Flow .................................................................................................. 30
Procedure ....................................................................................................... 31
Stakeholders ................................................................................................... 31
FAA Tower Supervisor .................................................................................... 31
Trials Participant ............................................................................................. 31
Trials Lead ...................................................................................................... 31
Trials Program Manager (PM) ........................................................................ 31
Ops Management Working Group (OMWG) .................................................. 31
Help Desk ....................................................................................................... 31
Airline Operations Center (AOC) .................................................................... 31
Controller ........................................................................................................ 32
FAA Tech ........................................................................................................ 32
Inputs .............................................................................................................. 32
Issue ............................................................................................................... 32
Prioritization .................................................................................................... 32
Outputs ........................................................................................................... 32
Help Desk Call Log ......................................................................................... 32
SharePoint Issue ............................................................................................ 32
Resolution and Restart Plan ........................................................................... 32
Procedures...................................................................................................... 33
LIST OF FIGURES
1
2
3
4
5
6
7
Harris Secure Access SSL VPN Instant Virtual Extranet Welcome Screen ... 14
Sample SharePoint DCL Operations Summary Page .................................... 15
Sample DCIT SharePoint Issue Tracking Page ............................................. 16
Sample DCIT Working Groups Action Items Page ......................................... 17
28 and 56 Day Product Schedule ................................................................... 25
Harris Team Responsibility Flow Chart .......................................................... 26
DCL Trails Issue Resolution Process Flow .................................................... 30
LIST OF TABLES
1
2
FAA SOW Requirements Outline ................................................................... 28
Step Instruction Table ..................................................................................... 33
Table of Contents  Page 4 of 34
Trials Management Plan
1
Issued: August 12, 2013
INTRODUCTION
This document describes the operational procedures for the Data Communications
Program (DCP) Departure Clearance (DCL) Trials activities. The DCL Trials support preoperational demonstrations of key aspects of the tower controller-pilot data link
communication (CPDLC) services in field trials. The DCL Trials will validate the concept
of operation for the delivery of departure clearances and revised departure clearances
through advanced automation and CPDLC. The trials will ensure procedures and training
plans are appropriate, and will provide airspace users an opportunity to experience the
benefits associated with Data Comm services. Operational trials will evaluate
requirements in support of the fully-compliant automation system development and
deployment.
The DCL service provides automated assistance for requesting and delivering initial, and
revised departure clearances. DCL provides CPDLC messages for the following: Flight
plan route, initial and requested altitude, and departure frequency. When DCL is provided
through the use of CPDLC, this information is exchanged using CPDLC messaging. For
the trials, the messages will be selected from those already used in Future Air Navigation
Services (FANS) equipped aircraft. The CPDLC message elements are defined in RTCA
DO-258A that current FANS avionics already support. The DCL service is designed for
use in surface operations and replaces the existing Pre-Departure Clearance (PDC) at
trial sites for participating aircraft.
1.1
Scope
This document describes the management procedures for the DCL Trials, and was
created to merge all procedural information into a single document. These procedures
will cover activities that the FAA and contractors perform, but not cover the internal
procedures of the individual contractors. The audience for this document is the Data
Comm Integration Team (DCIT).
Introduction  Page 5 of 34
Trials Management Plan
2
Issued: August 12, 2013
TRIALS OPERATION
Trials are conducted in two stages for each participating Air Traffic Control Tower
(ATCT), and each Airline. First will be limited trials to help train staff and get the ATCT or
Airline comfortable with the DCL procedures as they join into the program at varying
times. Full trials will start once the ATCT and the new airline are comfortable that each is
ready, and the system is stable for their use.
The participating airlines at each site are as follows:

Memphis ATCT: FedEx Express

Newark ATCT: United Parcel Service, FedEx Express, United Airlines, British
Airways, Lufthansa Airlines, and Scandinavian Airlines
Note: These are the participating Airlines as of the creation date of this document.
Participating airlines may change as trials progress.
2.1
Operations Management Working Group (OMWG)
The OMWG is composed of all the stakeholders in the DCL Trials including the FAA,
participating airlines, service providers, Harris, and other industry partners. It is held
every Tuesday during the life of the DCL Trials, and is managed by the DCL Trials Lead.
The primary function of the OMWG is to state the results of flights over the preceding
period, identify operational issues, and task out resolution for the issues. This is done via
the following basic format:

Quick and up-to-date stats
– Basically, last week’s statistics, thru Friday, available on a Tuesday

Ops around the room
– Operational leads from ATC, aircrew, and Dispatch report/drive
discussions; minimal non-operations input
–
Gauge operational health of the system
–
Advise problems for joint resolution (near-term and more permanent
fixes)

Review of implementation date(s) for previously agreed-upon problem
resolutions

Review flights planned for the upcoming period

Current Baseline documents (end-end, System Integration Description
Document (SIDD), Flight Deck), and planned updates (content and
update schedule)

Meeting records should go out the day of the telecon
Trials Operation  Page 6 of 34
Trials Management Plan
2.2
Issued: August 12, 2013
Limited Trial Operations
The goal of limited trials is to help train staff, get the ATCT and Airline comfortable with
the DCL procedures, and to work through any early issues to ensure a successful fulltrials operation.
2.2.1
Flight Coordination and Participation
During limited trials, flights are pre-scheduled before participating, to ensure the proper
coordination and training is in place. These flights will be coordinated via email and DCIT
SharePoint and will typically be scheduled during the week in which they will participate.
The Airline Operation Center (AOC) will send an email for the planned flights to one of
the following distribution lists depending on Trial site:

DCL_MEM_Notify@harris.com or DCL_EWR_NOTIFY@harris.com
The flights will then be uploaded by Harris to the Flight Tracker on the DCIT SharePoint
(See section 6) for official record keeping and common repository.
As these DCL flights are completed, completion status will be sent out to the same
distribution lists noted above, by the AOC. In addition, the AOC and/or the Tower should
also send any applicable comments on any of these flights to the distribution list.
All completed flights and comments will then be inputted by Harris to the Flight Tracker
on the DCIT SharePoint site.
2.2.2
Operations Management Working Group (OMWG)
During limited trial operations, the OMWG should discuss the planned DCL flights
operations, and ensure the planned operation for the flight will progress the trial towards
Normal Trials Operations by balancing the type of messages sent, aircraft used, etc. The
OMWG should also discuss the previously completed flights and any new issues. Lastly,
the OMWG should continue to status the currently open issues impacting DCL operations
and progress.
2.3
Normal (Full) Trials Operations
The goal of Normal Trials Operations is to get a sufficient mix of flights participating in the
trials to provide a good basis of evaluation for Data Comm.
Trials Operation  Page 7 of 34
Trials Management Plan
2.3.1
Issued: August 12, 2013
Flight Coordination and Participation
During Full Trial Operations, flights can participate 24/7 and pre-coordination is not
required. The Airline will notify participation by filing the participating flight as FRC DCL in
the remarks of the flight plan. The airlines will select the participating flights as they
choose within their fleet. Participating flights will be chosen from those that are equipped
and the pilots that are trained.
Unlike the limited trials, there will be no daily tracking of flights and their completion
status. However, if there are any issues, or if the AOC or Tower wants to send specific
comments on any particular flight, they should do so by sending to the distribution list
below:

2.3.2
DCIT@Harris.com
Operations Management Working Group (OMWG)
While flights are not planned out in advance, the OMWG will discuss the DCL Operations
outlook and any issues that occur during full trials. There will be an agenda item for each
weekly meeting to discuss the week’s flights. Flight information will be provided by Harris
via log analysis when requested.
Trials Operation  Page 8 of 34
Trials Management Plan
3
Issued: August 12, 2013
SCHEDULED OUTAGES
Scheduled outages consist of planned events. The two common planned events are
DTAP Navigation Database updates and Software/Configuration updates. Scheduled
outages will be discussed in advance at the DCIT and OMWG meetings with Advisories
being sent as the outage approaches.

Planned starts/stops
–
Dates identified at Operations Management telecons
–
“Go” indication for all starts/stops provided by each Operation Authority a few
days prior to target date
–
Notifications done as part of Operations Management telecon records (always
sent day of telecon)
–
Distribution under the direction of the FAA Trials Lead
–
Operations Authorities are responsible for distributing required info within their
respective organization
3.1
DTAP Navigation Database Update Procedures
DTAP requires a Data Base (DB) update for its navigational data on a periodic basis. The
data is available every 28 days and requires manual interaction to update it. When this
update occurs DTAP will be offline and DCL trials will have an outage, in which no DCL
flights can participate. The goal is to perform this update during low traffic to allow for
minimal impact to the trials.
DCL Trial participants will be notified via an Advisory before DTAP is taken offline to
perform this update. DCL Trials will be unavailable for a period of 2 hours while this
occurs. The current planned outage times for each participating ATCT are as follows:

MEM: 2:00 to 4:00 AM local time

ERW: 1:00 to 3:00 AM local time
The detailed procedures to perform this update are located in APPENDIX A.
3.2
Software Patches and Configuration Updates
Software patches and configuration updates are considered scheduled outages and will
be planned and tested before they are applied to the production system.
Scheduled Outages  Page 9 of 34
Trials Management Plan
3.2.1
Issued: August 12, 2013
Overview
This process starts at the point where a patch or configuration is already scheduled for
delivery from Thales to the William J. Hughes Technical Center (WJHTC). Once
delivered to the William J. Hughes Technical Center (WJHTC), it will go through
regression testing to ensure no major issues exist before sending to the site. Once
delivered to the site, it goes through functional and interoperability testing before Site
Acceptance Testing (SAT). During SAT, the patch will be put through a small set of
operational test procedures to prove to the local facility and other stakeholders that it
works. Once the patch is approved through SAT, the DTAP gets re-certified and is
operational.
Once the patch or configuration update gets to the site and starts to undergo testing, the
DTAP, and thus the DCL Trials, will be down for a period of time. DCL Trials participant
will be notified via Advisory when this downtime is expected. Duration of outage is
approximately four hours for a configuration update, and about one week for a software
patch depending on the complexity of the patch, and if any issues are uncovered during
testing.
3.2.2
WJHTC Patch Testing Procedures
New patches are developed by Thales using their development process and, when they
are ready, will be given to the FAA for regression testing at the Tech Center. All patches
must be tested at the Tech Center before being deployed to the field.
The testing team at the Data Comm lab will test the new software build against the
Problem Tracking Reports (PTR) using WJHTC-developed testing procedures to ensure
the new build does not interfere with previous requirements. Once regression testing is
completed, the testing team will perform Validation and Verification testing on the new
software build to ensure that it meets the requirements for the new build.
Detailed procedures for WJHTC Patch and Configuration testing are maintained at the
WJHTC and are entitled, DATA Communications (Data Comm) Trial Automation Platform
(DTAP) TEST PROCEDURES.
3.2.3
Site Specific Test Procedures
For each software patch or configuration update, a site specific test procedure will be
developed and customized for each site receiving the new patch or update. This
procedure will detail how the site will go about performing the required testing to ensure
the patch, or update, is suitable for site use. These test procedures will include functional
and interoperability testing, and the site specific acceptance testing. See Appendix B for
an example Site Specific Test Plan.
Scheduled Outages  Page 10 of 34
Trials Management Plan
3.2.3.1
Issued: August 12, 2013
Site Patch Functional and Interoperability Testing
Once the site receives the Approved Patch from the WJHTC, they will perform local
Functional and Interoperability testing per the site specific test plan. This consists of
testing with bench avionics located at the WJHTC, and live assets to ensure interfaces
between the DTAP and other systems such as FDIO, HADDS, and the Communication
Service Providers, using test procedures developed by WJHTC.
The Functional and Interoperability tests are centered on eight test areas as well as
testing of the new requirements delivered in the new software build:
 Aircraft Logon - to demonstrate when aircraft logons are accepted and when they
are rejected,
 Downlink Clearance Request (DM25) - to demonstrate the DTAP responses to
the DM25 under different conditions,
 Initial Clearances (Cleared as Filed (CAF), UM79 Initial, UM80) - to demonstrate
creation of uplinks and display of the CAF initial clearance in the aircraft avionics,
 Revised Clearances (UM79, and UM80) - to demonstrate creation of uplinks and
display of the revised clearance in the aircraft avionics,
 Route Content - to demonstrate creation of DCL route information using various
forms of route element specification,
 Downlink Responses - to demonstrate DTAP reaction to the various pilot
responses to DCLs,
 Connection Termination - to demonstrate actions upon termination of the
connection,
 Non-nominal Conditions - to demonstrate actions in response to error and failure
conditions,
 AOC Dispatch Copy – to demonstrate copy still received as expected.
3.2.3.2 Site Acceptance Testing
Once the patch has complete functional and interoperability testing, the site must conduct
a Site Acceptance Test (SAT) with the new software.
Following the completion of the Functionality and Interoperability testing, the new
Software Build will run through operational test scenarios using live assets on site. The
operational test scenarios will cover all eight test areas, covered in functional and
interoperability, to demonstrate to the operational readiness of the software to site.
Operational test scenarios will vary by site to ensure that operations are tailored
specifically to the each location (e.g., use of Coded Departure Routes at Newark).
3.2.4
DTAP Certification
After SAT is completed and approved, the DTAP must be re-certified using the
certification procedures located in Section 4.
Scheduled Outages  Page 11 of 34
Trials Management Plan
4
Issued: August 12, 2013
DTAP CERTIFICATION
DTAP certification is required when there is a configuration or software change to the
DTAP system. Certification is not needed in the event of a power outage or other event
that does not change the software or configuration.
The local FAA Tech Operations field technician performs the DTAP Re-certification
procedure outlined below.
1) Confirm all DTAP nodes are ONLINE and interfaces are connected;
2) FAA Representative files test flight plan;
3) Confirm test flight plan is promptly received and displayed on DTAP Controllers
Screen’s “proposed list”;
4) Controller prepares the DCL;
5) FAA NJ TECH AVIONICS Logs on to DTAP;
6) Confirm FAA NJ TECH center AVIONICS logged on and CPDLC connected to
DTAP successfully;
7) FAA NJ TECH center AVIONICS sends a Clearance Request (DM25);
8) DTAP automatically sent a departure clearance (DCL);
9) FAA NJ TECH center AVIONICS received the DCL and sent a WILCO to DTAP;
10) DTAP received the WILCO and moved the Aircraft to JHMI’s “completed list”
11) DTAP Certification Complete
DTAP Certification  Page 12 of 34
Trials Management Plan
5
Issued: August 12, 2013
TRIALS ISSUE IDENTIFICATION AND RESOLUTION PROCESS
This process is used to assist in issue resolution for the DCL Trials. An issue may consist
of anything that a trials participant feels isn’t working properly. An issue may result in an
outage, or simply a question being answered to clarify how something works.
There is a single Help Desk number that is used for all participants to call for any issue,
and is manned 24/7/365. Once the Help Desk is called, a trouble ticket is opened and the
appropriate people are notified. The trouble ticket will be categorized by the FAA Trials
Lead, based on how critical the issue is, and if an actual outage has occurred.
Depending on the initial assessment of the issue, response time will vary. Critical issues
will be addressed immediately by the Help Desk.

Unplanned stops
–
Operations Authorities should contact FAA Trials Lead as soon as possible
–
FAA Trials Lead ensures information gets to all Operations Authorities, for
communication within their organizations
–
FAA Trials Lead will ensure correct planning of the restart, and coordination with
all Operations Authorities
–
Direct communication between Operational Entities (e.g., Tower and AOC, or
Tower and flights) will happen as dictated by the situation. Results need to be
communicated to the FAA Trials Lead for statistics coordination, etc.
–
Operations Authorities are responsible for distributing required info within their
organization
See Appendix C for the detailed Trials Issue Identification and Resolution Process.
Help Desk
1-877-384-NOCC (6622)
Option 3, then Option 1
DCL Service ID
EWR: FTIH-DC-041021
MEM: FTIH-DC-041020
Trials Issue Identification and Resolution Process  Page 13 of 34
Trials Management Plan
6
Issued: August 12, 2013
SHAREPOINT
SharePoint is the official CM repository that is being used for the trials. It is used to store
and CM procedures, configuration, and data. It is being maintained by Harris, and is
hosted on their extranet.
Information in this tool is organized by trial site.
To access the web accessible CM Tool, please use the following link:
1) Open an internet browser (i.e., Internet Explorer) and type, or paste in the
following URL https://vpn.harris.com/external/gcsd
Figure 1. Harris Secure Access SSL VPN Instant Virtual Extranet Welcome Screen
2) Log in with your username and password. The password that has been provided
will need to be changed at first logon. You will be prompted to change the
password.
3) Once this is accepted, it will proceed to launch and eventually bring you to a
page with the DCIT link to the DataComm SharePoint site.
4) SharePoint – DCIT (Note: In the special case of the Nav DataBase Procedure
located in Section 3, the Harris internal DCIS SharePoint is used, however, all
other usage will be on DCIT.)
SharePoint  Page 14 of 34
Trials Management Plan
6.1
Issued: August 12, 2013
DCL Operations Tracking
The SharePoint Completed Ops page provides a summary of the completed DCL
operations at each trial site and provides a count of the messages exchanged. The data
will be entered as operations are completed by the DCIS contractors.
Figure 2. Sample SharePoint DCL Operations Summary Page
SharePoint  Page 15 of 34
Trials Management Plan
6.2
Issued: August 12, 2013
DCL Operations Issue Tracking
As issues are identified during DCL Operations, they will be tracked until the resolution is
in place on the DCIT SharePoint issue tracking page. The issues are listed on the site by
their date, but can also be sorted by the stakeholder for the issue.
Figure 3. Sample DCIT SharePoint Issue Tracking Page
SharePoint  Page 16 of 34
Trials Management Plan
6.3
Issued: August 12, 2013
DCIT Action Tracker
In addition to tracking DCL operations, the SharePoint site tracks the Action Items
assigned to the DCIT Working Groups during the DCIT Plenary meetings.
Figure 4. Sample DCIT Working Groups Action Items Page
SharePoint  Page 17 of 34
Trials Management Plan
7
7.1
Issued: August 12, 2013
TRIALS DATA COLLECTION
Health Monitoring
The objectives of health monitoring during DCL trials are:
 Ensure that the trials systems and procedures are meeting trials aims

Ensure that changes in usage levels are quickly understood, as a means of
capturing lessons and potential problems



Ensure that problems are identified and resolved quickly

This is not the same as
– Benefits tracking
– Officially reported statistics
– These two items need more time to create and approve
Ensure that resolutions meet the intended purpose, and do not create new problems
Give visibility to operational parties, and trials management, referencing how their
contribution is working for them and the trials
The Health Monitoring Statistics that will be collected for DCL are:
 Number of eligible flights



Proportion of eligible flights that logged-on

Proportion of eligible flights that received one or more revised DCLs, and
what type of revisions were made



Proportion of flight clearances statused: wilco, unabled, or standby
7.2
Proportion of eligible flights that requested a DCL
Proportion of eligible flights that received an initial DCL clearance, and type of
initial clearance received
Round trip times (clearance to wilco)
Number of logged-on flights that received a DCL via voice instead of datalink
Benefits Analysis
TBD – Awaiting outcome from FAA benefits Analysis Group
7.3
Airline Survey
A survey was developed by the DCIT for Pilots, Controllers, and dispatchers. This survey
can be found online at https://www.surveymonkey.com/s/DCLPilotSurvey
Trials Data Collection  Page 18 of 34
Trials Management Plan
8
Issued: August 12, 2013
NEW AIRLINE PARTICIPATION
This process is used as new airlines express interest to join the DCL trials. This will allow
the DCIT to make sure all interested airlines get consistent and complete information
about the trials, and to ensure nothing is overlooked.
1) Airline approaches FAA and conveys that they are interested in participating. FAA
(DCL Trials Lead) collects airline info and passes on to the OMWG.
2) The DCL trials lead sends the airline the New Airline Participation Document which
provides basic information on the DCL Trials and what is expected of the new
airline if they choose to participate.
3) The DCL Trials Lead schedules a TELCON with the airline to have an initial
discussion on participation and where/when that particular airline could fit into the
trials. Discuss which aircraft they could bring to the program and on which cycles.
The DCL Trials Lead will advertise the time and location of the meeting to the
OMWG. This meeting should include at minimal:
a. DCL Trials Lead
b. FAA Flight Standards
c.
Interested Airline Rep(s)
4) Develop and Sign Memorandum of Understanding (MOU).
5) Work with airline to modify their flight deck and dispatch procedures as needed to
support the trials.
6) Perform some initial testing with airline. This should include, at minimum, doing a
test logon and sending a test message.
7) Perform airline training for flight deck and AOC.
8) Airline obtains safety approval for operations.
9) Participate in limited trials as determined between the OMWG and the Airline.
10) Participate in full trials when the airline, trials lead, and ATCT agree all are ready.
New Airline Participation  Page 19 of 34
Trials Management Plan
9
Issued: August 12, 2013
GLOSSARY
Acronym
ACARS
AOC
AFN
ARTCC
AS
ATC
ATCT
ATM
ATN
CC
CPDLC
CSP
D-ATIS
Data Comm
DCIT
DCL
DCP
DT
DTAP
ERAM
FAA
FANS
FANS-1/A+
FDIO
FDP
FMS
FNTB
FO
FOC
FP
FTI
HADDS
ICAO
ICD
IP
IRD
MOE
MOP
MOS
NAS
Description
Aircraft Communications Addressing and Reporting System
Airline Operations Center/Aeronautical Operational Control
ATS Facilities Notifications
Air Route Traffic Control Center
Applications Systems
Air Traffic Control
Air Traffic Control Tower
Air Traffic Management
Aeronautical Telecommunication Network
Dispatch Message
Controller Pilot Data Link Communications
Communications Service Provider
Digital Automatic Terminal Information Service
Data Communications
Data Comm Integration Team
Departure Clearance
Data Comm Program
Developmental Testing
Data Comm Trials Automation Platform
En Route Automation Modernization
Federal Aviation Administration’s
Future Air Navigation Services
FANS Version 1+/A
Flight Data Input/Output
Flight Data Processing
Flight Management System
FTI National Test Bed
Flight Object
Flight Operations Center
Flight Plan
FAA Telecommunications Infrastructure
Host ATM Data Distribution System
International Civil Aviation Organization
Interface Control Document
Internet Protocol
Interface Requirements Document
Measures of Effectiveness
Measures of Performance
Measures of Suitability
National Airspace System
Glossary  Page 20 of 34
Trials Management Plan
Acronym
NESG
OPS
PDC
PTR
RTCA
SC-214
TDLS
VDL
VRTM
VHF
WJHTC
Issued: August 12, 2013
Description
National Enterprise Security Gateway
Operations
Pre-Departure Clearance
Program Trouble Report
RTCA, Inc. (formerly Radio Technical Commission for Aeronautics)
Special Committee 214
Tower Data Link Services
VHF Digital Link
Verification Requirements Traceability Matrix
Very High Frequency
William J. Hughes Technical Center
Glossary  Page 21 of 34
Trials Management Plan
10
Issued: August 12, 2013
APPENDIX A
10.1 DTAP Navigation Database Update Procedures
10.1.1
Introduction
DTAP requires a Data Base update for its navigational data on a periodic basis. The data
is available every 28 days, on AIRAC cycle, and requires manual interaction to update it.
This Navigation Database Update Process details the procedure to be followed when
performing the download of the Coded Instrument Flight Procedures (CIFP) data and the
retrieval of the Data Comm Trials Automation Platform (DTAP) log file.
10.1.2
Monthly Steps
10.1.2.1 Coded Instrument Flight Procedures (CIFP) Published
New Coded Instrument Flight Procedures (CIFP) are effective every 28 days in
accordance with standard AIRAC cycles, and published no later than 16 days prior to
effective date.

Harris downloads CIFP data from https://faacharts.faa.gov/
– Account > View Download Products
– Select applicable cycle date product and download

Harris downloads CIFP data to CM tool 16 days (or sooner) prior to effective date.
– CIFP Data will uploaded to the following link on the DCIS SharePoint:
/<Site>/Nav Database/<Cycle Date>/CIFP Data
10.1.2.2 Thales Data Preparation & Test




Thales downloads CIFP data from DCIS SharePoint: /<Site>/Nav Database/<Cycle
Date>/CIFP Data
DTAP Update files prepared by Thales engineers using current baseline of site
configuration
– Use Data PReperation (DPR) conversion tool on the FAA ARINC 424 database
file to produce two files of interest to the DTAP DATASET;
Create detailed issue report of any database inconsistencies or errors when
preparing for DTAP
Thales posts report and DTAP files to Harris CM Tool and Notifies WJHTC & Harris
– Report and DTAP Files should be uploaded the following link on the DCIS
SharePoint: /<Site>/Nav Database/<Cycle Date>/DTAP Files
Appendix A  Page 22 of 34
Trials Management Plan
Issued: August 12, 2013
10.1.2.3 WJHTC Data File Validation Test


WJHTC Downloads files from DCIS SharePoint.
WJHTC validates DTAP files load correctly & test DTAP according to WJHTC
approved procedures
 WJHTC notifies Thales of any issues/inconsistencies
Note: Data is considered tested OK and ready to install if not notified

(if required): Thales-WJHTC Issue Resolution
– Thales & WJHTC work to resolve any issues found during WJHTC testing of
database
– Create detailed issue report of any issues or errors during validation and testing
– Final tested data files and report posted to Harris CM Tool
Final Data Ready 2 Business Days Prior to Effective Date
10.1.2.4 Coordination and Notification
1) DCIS coordinates with ATC and operators to determine best time to take down DCL
Service at each trial location for Database Update with minimal operational impact.
2) Harris schedules local FAA Tech Ops & Harris field technician to conduct database
update
3) Email notifications sent to stakeholders notifying of projected down time of DTAP
4) Local FAA Tech Ops notifies AOCC of DTAP maintenance
5) Coordination of DTAP re-certification (aircraft/WJHTC and flight plan)
10.1.2.5 Field Installation of Database files
1) DCIS Dispatches Harris Field Technicians
2) Harris Field Technician downloads data from CM Tool. Data is located at DCIS
SharePoint : /<Site>/Nav Database/<Cycle Date>/DTAP where <Site> refers to
DTAP Location (e.g., MEM or EWR).
3) Harris Field Technician updates DTAP
a) Run Data PReperation (DPR) distribution tool to deploy the new DATASET on
the DTAP platform;
b) Run Data PReperation (DPR) “handle new dataset” tool to put the new
DATASET in use for DTAP platform;
c) After the new DATASET is ready to be used by DTAP, the platform is to be
restarted “cold”.
d) Confirm all nodes are ONLINE and all interfaces are connected to DTAP
4) Local FAA Tech Ops field technician performs DTAP Re-certification
5) Local FAA Tech Ops notifies AOCC DTAP maintenance complete
6) Harris Field Technician loads DTAP Log Files & Field Report to CM Tool
Appendix A  Page 23 of 34
Trials Management Plan
Issued: August 12, 2013
10.1.2.6 Issue Resolution

In the event that a DTAP maintenance procedure is unsuccessful, please follow
standard DTAP notification procedures as shown in Section 5.
10.1.2.7 Delivery of Data and Reports

Harris DCIS engineers will deliver required DTAP log files and associated reports to
FAA and local facility.
Appendix A  Page 24 of 34
Trials Management Plan
Issued: August 12, 2013
Figure 5. 28 and 56 Day Product Schedule
Appendix A  Page 25 of 34
Trials Management Plan
Issued: August 12, 2013
THALES
HARRIS
Coordinate with FAA Tech Ops, and Harris Field Technicians for Database Update and Recertification
Download CIFP
Data
Deliver to FAA
Upload CIFP Data
to CM Tool
Download CIFP Data
from CM Tool
Convert CIFP Data to DTAP Compatible Files
Issue Resolution
Upload DTAP Files
to CM Tool
WJHTC
Download DTAP
Files from CM Tool
DTAP Files Validation and Test
HARRIS FIELD
TECHNICIAN
Upload DTAP Files
to CM Tool
Download DTAP
Files from CM Tool
Update DTAP and
Download Logs
Upload Logs and
Report to CM Tool
T-16
Days
T-9
Days
Figure 6. Harris Team Responsibility Flow Chart
Appendix A  Page 26 of 34
T-2
Days
Effective Date
Trials Management Plan
11
Issued: August 12, 2013
Appendix B
11.1 Site Specific Test Plan Example
TBD
Appendix B  Page 27 of 34
Trials Management Plan
12
Issued: August 12, 2013
Appendix C
12.1 Trials Issue Identification and Resolution Process
This process is needed to assist in Issue Resolution for the DCL Trials. This process
consists of a DCL Trials Participant identifying a problem, and notifying the appropriate
contact to ensure the issue is resolved based on criticality.
12.1.1
Process Objective
The following are objectives of this process:

PO-1: To assist Trial Participants in the resolution of issues found during Trial
Operations.

PO-2: To ensure the proper parties are notified when an issue occurs.

PO-3: To ensure appropriate action is taken so that future incidents can be reduced
or prevented.

PO-4: To ensure a consistent process for issue resolution.
12.1.2
Process Requirements
Requirements outlined per FAA Statement of Work (SOW):
Table 1. FAA SOW Requirements Outline
ID
Description
PR-1 < Summary of business requirement>
Type
<Functional or
Operational>
Reference
<Person or Document
req originated from>
PR-2
PR-3
PR-4
12.1.3
Assumptions and Dependencies
The following assumptions and dependencies apply to this process:

AD-1: The Site Operation Notification List contains all the appropriate parties who
need to be notified when an issue occurs, including the participating AOC and
Tower personnel.
Appendix C  Page 28 of 34
Trials Management Plan
12.1.4
Issued: August 12, 2013
Definitions
The following definitions apply to this process document:
Air Traffic Control Tower (ATCT): The airport tower where DCL Trials are conducted.
Airline Operations Center (AOC): The Operation Center of the participating airline.
Ops Management Working Group (OMWG): The working group of DCL Trials
participants and stakeholders responsible for coordinating the trials and working issues.
DCL Trials Automation Platform (DTAP): The automation platform developed by
Thales to simulate TDLS functions for the DCL Trials.
Site Operational Notification List: The list of contacts that must be notified when a
Trials issue occurs.
Appendix C  Page 29 of 34
Trials Management Plan
Issued: August 12, 2013
12.2 Process Flow
DCL Trials Issue Resolution Process Flow
OMWG
Phase 1/1
Trials PM
Discuss at next
schedule OMWG.
Tower
Supervisor
Trials Lead
Schedule emergency
OMWG for next day.
Supervisor calls Call
Center at 1-877-384NOCC
A trials
participant
identifies an
issue and notifies
the appropriate
Supervisor.
Trials lead calls
Supervisor to
discuss issue
and agree on
classification of
Minor or Major.
Issue is logged
into SharePoint
and sends
notification to
Site Operational
Notification List.
Classification
Stop DCL Trial
Operations and
Notify Trials PM.
Logs issue details
and calls trials lead or
alternate
AOC
Call
Center
Discuss issue
and document
plan to fix and
restart trials
opration.
Controll
er
Stop filing FP as
“FRC/DCL”
FAA
Tech
Go to voice
operations.
Figure 7. DCL Trails Issue Resolution Process Flow
Appendix C  Page 30 of 34
Trials Management Plan
Issued: August 12, 2013
12.3 Procedure
12.3.1
Stakeholders
The following stakeholders are involved in this process:
12.3.1.1 FAA Tower Supervisor
The FAA Tower Supervisor is initially responsible for coordinating the issue with the
person who identifies it. The Tower Supervisor will be the one making the initial call to the
Help Desk and coordinating the issue with the Trials Lead.
12.3.1.2 Trials Participant
This consists of any person or group involved in the operation of the DCL Trials that may
discover an issue in the system. This may consist of the Controller, Pilot, AOC, Tech
Ops, or other parties involved.
12.3.1.3 Trials Lead
The Trials Lead is responsible for coordinating the issue with the Tower Supervisor and
determining if the issue is major or minor. They are also responsible for contacting the
Trials PM if needed, and logging the issue into SharePoint. The Trials Lead is
responsible for seeing the issue through to its resolution.
12.3.1.4 Trials Program Manager (PM)
The Trial PM is responsible for coordinating an emergency OMWG when a major issue
occurs.
12.3.1.5 Ops Management Working Group (OMWG)
The OMWG is responsible for discussing and documenting the issues identified, and
agreeing to a resolution and Trials re-start plan.
12.3.1.6 Help Desk
The Help Desk is responsible for documenting the initial call and then notifying the Trials
Lead or alternate.
12.3.1.7 Airline Operations Center (AOC)
The AOC is responsible for notifying the Tower Supervisor upon discovery of any issues
with the DCL Trials. The AOC also has the responsibility to stop filing FPs as “FRC/DCL”
when they are notified of an issue that stops DCL Trials Operations.
Appendix C  Page 31 of 34
Trials Management Plan
Issued: August 12, 2013
12.3.1.8 Controller
The Controller is responsible for notifying the Tower Supervisor upon discovery of any
issues with the DCL trials. The controller also has the responsibility to switch to voice
operations if they are notified of an issue that stops DCL Trials Operation.
12.3.1.9 FAA Tech
The FAA Tech is responsible for notifying the Tower Supervisor upon discovery of any
issues with the DCL Trials. The FAA Tech also has the responsibility to assist in the
resolution of any issues that are discovered.
12.3.2
Inputs
12.3.2.1 Issue
This is any problem that is identified by a DCL Trials Participant.
12.3.2.2 Prioritization
This is the classification of the identified issue as determined by the DCL Trials Lead. The
prioritization is then used to guide the Trials Lead on how to proceed with resolving the
issue. The two possible prioritization values are Major and Minor.
12.3.3
Outputs
12.3.3.1 Help Desk Call Log
This is the log from the Help Desk which documents the issue details.
12.3.3.2 SharePoint Issue
When an issue is identified it is logged into SharePoint and updated as resolution
progress is made.
12.3.3.3 Resolution and Restart Plan
This is the plan that outlines the resolution of the issue, and states the agreement for how
and when to restart Trials Operation. This document is produced by the OMWG.
Appendix C  Page 32 of 34
Trials Management Plan
12.3.4
Issued: August 12, 2013
Procedures
Table 2. Step Instruction Table
Step
Description
Identification and Notification
A trials participant identifies an issue that affects the trials operations and
calls the Help Desk at 877-384-6622, option 3, then option1, and provide
the Site Service ID: FTIH-DC-041021 (EWR) or FTIH-DC-041020 (MEM). If
the issue involves a DCL flight, the following minimal information should be
provided to the Help Desk: date, time, registration, flight ID, and the
1
problem description.
The Help Desk opens a ticket and calls the DCL Trials Lead, or identified
alternate, and forwards the details of the issue to them. If the issue is
2
network related, the Call Center will resolve it.
The DCL Trials Lead contacts the Issue Identifier and discusses the issue.
They determine if the issue is Major or Minor. If unsure, they can escalate
to others for assistance in the determination. If an unscheduled stop has
3
already occurred, then the issue is considered Major.
Minor Issue
If the Issue Identifier and the DCL Trials Lead agree that the issue is Minor
and Trials can continue, then the DCL Trials Lead logs the issue into
SharePoint and sends notification to the Site Operational Notification List at
DCL_MEM_Notify@harris.com or DCL_EWR_NOTIFY@harris.com.
4
The issue is then discussed at the next scheduled OMWG meeting.
Major Issue
If the issue is deemed Major and Trials Operation is not already stopped,
then the DCL Trials Lead stops it by contacting the appropriate ATCT Site
Supervisor. An Advisory is then issued and notifications are made as
necessary through either phone calls and/or emails to appropriate
5
stakeholder parties.
The DCL Trials Lead logs the issue into SharePoint, and sends notification
to the appropriate Site Operational Notification List:
6
DCL_MEM_Notify@harris.com or DCL_EWR_NOTIFY@harris.com
Appendix C  Page 33 of 34
Owner
Issue
Identifier
Input
Output
Issue
Help Desk
Help Desk Ticket
Trials Lead
Trials Lead
Prioritization
Trials Lead
Prioritization
Trials Lead
SharePoint Issue
SharePoint Issue
Trials Management Plan
Issued: August 12, 2013
Table 2. Step Instruction Table
Step
Description
AOC stops filing flight plans w/ "FRC/DCL" and the tower stops using
7
DTAP and switches to voice operations.
The DCL Trials Lead calls an unscheduled meeting of the OMWG to
discuss the Major issue. If possible, the meeting should be scheduled for
8
the same day, or at the latest, the next day.
Issue Resolution
Discuss Issue at the OMWG and agree on Resolution and Re-Start
options. OMWG documents plan.
9
DCL Program Manager coordinates fix and Re-Start date per agreed-to,
10
documented plan.
11
DCL Program Manager logs Resolution into SharePoint.
12
Trials Re-Start.
Appendix C  Page 34 of 34
Owner
AOC and
Controller
Input
Output
DCL PM
Document
Resolution and
Re-Start Plan
Notes
Notes