Trials Management PlanIssued: August 12, 2013
Data Communications Implementation Team (DCIT)
Departure Clearance Service (DCL) Trials
Phase 1
Trials Management Plan
Issued
August 12, 2013
Support Contact Information Page 1 of 34
Trials Management PlanIssued: August 12, 2013
DOCUMENT REVISION RECORD
Rev. / Date / Author / Change Summary0 / 8/12/13 / Sean St. John / Issued
Support Contact Information Page 1 of 34
Trials Management PlanIssued: August 12, 2013
TABLE OF CONTENTS
1INTRODUCTION
1.1Scope
2TRIALS OPERATION
2.1Operations Management Working Group (OMWG)
2.2Limited Trial Operations
2.2.1Flight Coordination and Participation
2.2.2Operations Management Working Group (OMWG)
2.3Normal (Full) Trials Operations
2.3.1Flight Coordination and Participation
2.3.2Operations Management Working Group (OMWG)
3SCHEDULED OUTAGES
3.1DTAP Navigation Database Update Procedures
3.2Software Patches and Configuration Updates
3.2.1Overview
3.2.2WJHTC Patch Testing Procedures
3.2.3Site Specific Test Procedures
3.2.3.1Site Patch Functional and Interoperability Testing
3.2.3.2Site Acceptance Testing
3.2.4DTAP Certification
4DTAP CERTIFICATION
5TRIALS ISSUE IDENTIFICATION AND RESOLUTION PROCESS
6SHAREPOINT
6.1DCL Operations Tracking
6.2DCL Operations Issue Tracking
6.3DCIT Action Tracker
7TRIALS DATA COLLECTION
7.1Health Monitoring
7.2Benefits Analysis
7.3Airline Survey
8NEW AIRLINE PARTICIPATION
9GLOSSARY
10APPENDIX A
10.1DTAP Navigation Database Update Procedures
10.1.1Introduction
10.1.2Monthly Steps
10.1.2.1Coded Instrument Flight Procedures (CIFP) Published
10.1.2.2Thales Data Preparation & Test
10.1.2.3WJHTC Data File Validation Test
10.1.2.4Coordination and Notification
10.1.2.5Field Installation of Database files
10.1.2.6Issue Resolution
10.1.2.7Delivery of Data and Reports
TABLE OF CONTENTS (continued)
11Appendix B
11.1Site Specific Test Plan Example
12Appendix C
12.1Trials Issue Identification and Resolution Process
12.1.1Process Objective
12.1.2Process Requirements
12.1.3Assumptions and Dependencies
12.1.4Definitions
12.2Process Flow
12.3Procedure
12.3.1Stakeholders
12.3.1.1FAA Tower Supervisor
12.3.1.2Trials Participant
12.3.1.3Trials Lead
12.3.1.4Trials Program Manager (PM)
12.3.1.5Ops Management Working Group (OMWG)
12.3.1.6Help Desk
12.3.1.7Airline Operations Center (AOC)
12.3.1.8Controller
12.3.1.9FAA Tech
12.3.2Inputs
12.3.2.1Issue
12.3.2.2Prioritization
12.3.3Outputs
12.3.3.1Help Desk Call Log
12.3.3.2SharePoint Issue
12.3.3.3Resolution and Restart Plan
12.3.4Procedures
LIST OF FIGURES
1Harris Secure Access SSL VPN Instant Virtual Extranet Welcome Screen
2Sample SharePoint DCL Operations Summary Page
3Sample DCIT SharePoint Issue Tracking Page
4Sample DCIT Working Groups Action Items Page
528 and 56 Day Product Schedule
6Harris Team Responsibility Flow Chart
7DCL Trails Issue Resolution Process Flow
LIST OF TABLES
1FAA SOW Requirements Outline
2Step Instruction Table
Table of Contents Page 1 of 34
Trials Management PlanIssued: August 12, 2013
1INTRODUCTION
This document describes the operational procedures for the Data Communications Program (DCP) Departure Clearance (DCL) Trials activities. The DCL Trials support pre-operational 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 sitesfor participating aircraft.
1.1Scope
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 1 of 34
Trials Management PlanIssued: August 12, 2013
2TRIALS 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 eachis ready, and the system is stable for their use.
The participating airlines at each site are as follows:
- Memphis ATCT:FedExExpress
- Newark ATCT:United Parcel Service, FedExExpress, UnitedAirlines, 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.1Operations 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
2.2Limited 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 full-trials operation.
2.2.1Flight 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:
- or
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 SharePointsite.
2.2.2Operations Management Working Group (OMWG)
Duringlimited trial operations, theOMWG 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.3Normal (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.
2.3.1Flight 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 bechosen 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.2Operations 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 analysiswhen requested.
Trials Operation Page 1 of 34
Trials Management PlanIssued: August 12, 2013
3SCHEDULED 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.1DTAP 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
Thedetailedprocedures to perform this update are located in Appendix A.
3.2Software 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 productionsystem.
3.2.1Overview
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.2WJHTC 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.3Site Specific Test Procedures
For each software patch or configuration update, a sitespecific 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 sitespecific acceptance testing. SeeAppendix B for an example Site Specific Test Plan.
3.2.3.1Site 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.2Site 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.4DTAP Certification
After SAT is completed and approved, the DTAP must be re-certified using the certification procedures located in Section 4.
Scheduled Outages Page 1 of 34
Trials Management PlanIssued: August 12, 2013
4DTAP 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 1 of 34
Trials Management PlanIssued: August 12, 2013
5TRIALS 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 FAATrials 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