ACARS_Product_Description.docx

PRODUCT DESCRIPTION (PD)

Aircraft Software Update for Implementation of Changes to C-5M Aircraft Communications Addressing and Reporting System (ACARS)

AFLCMC/WLS (Galaxy Division) Air Force Life Cycle Management Center Robins AFB, GA

Basic Date: 08/28/13

For Official Use Only For Official Use Only

Revision Record

Table of Contents

3.4.1 Program Management 10

3.4.2 Business Management 10

3.4.2.1 Collaboration with Government C-5 Software Integration Laboratory 11

3.5 Data Management 11

3.5.1 Data Rights 11

3.6 Formal Qualification Testing (FQT) Capability 12

3.7 Communication Management Function 12

Product Description This Product Description (PD) outlines the software product and supporting product deliverables for Aircraft Communications Addressing and Reporting System (ACARS) for C-5M aircraft.

The product deliverable shall be a C-5M compatible aircraft Operational Flight Program (OFP) with supporting certification artifacts and documentation.

The product shall comply with all C-5M certifications as found in section 3.1 prior to final acceptance.

Applicable Documents The documents listed below are incorporated into this product description. Compliance is required in order to support product certification prior to final acceptance.

Military Standards (MIL-STD) MIL-STD-882E, Department of Defense Standard Practice For System Safety, 11-May-12 International Standards Organization (ISO) Joint Aviation Authorities (JAA) Leaflet 10, Airworthiness and Operational Approval For Precision RNAV Operations In Designated European Airspace Other Government Documents AFI 33-200, Information Assurance (IA) Management, 15 October 2010 AFI 33-210, Air Force Certification and Accreditation (C&A) Program (AFCAP), 23 December 2008 ASC/CC Memo, ASC Guidance Memorandum on Information Assurance (IA) Certification and Accreditation (C&A) Requirements for Platform IT (PIT), 25 April 2010 AFI 63-1301, w/change 1, Assurance of Communications, Navigation, Surveillance/Air Traffic Management and Navigation Safety Performance, 02 August 2006 Air Force Policy Directive (AFPD) 33-2, Information Assurance (IA) Program, 03 August 2011 DoD Directive 5220.22-M, National Industrial Security Program Operations Manual, 01 February 2006 DoD Directive 8500.01, IA, 23 April 2007 DoD Instruction 8500.2, IA Implementation, 06 Feb 2003 DoD Instruction 8510.01, DoD Information Assurance Certification and Accreditation Process (DIACAP), 28 Nov 2007 MIL-HDBK-516B, Airworthiness Certification Criteria, 29-Feb-08 USAF Airworthiness Bulletin (AWB)-007, 5 May 2011 USAF Airworthiness Bulletin (AWB)-013A, 29 June 2011 Standard Message Set (SMS) 3.2, ACARS SMS for Mobility Air Forces Aircraft, 2-August-12

Commercial Engineering Standards and Guidelines AC 20-130A, Airworthiness Approval of Navigation or Flight Management Systems Integrating Multiple Navigation Sensors, 14-Jun-95 AC 90-91H, North American Route Program (NRP), 30-Jul-04 DO-178B Software Considerations in Airborne Systems and Equipment Certification, 01 December 1992 ARINC 622, ATS Data Link Applications over ACARS Air-Ground Network, 12-October-2001 ARINC 702A-3, Advanced Flight Management Computer Systems, 15-December-2006

C-5M Aircraft Communications Addressing and Reporting System (ACARS) Operational Flight Program The contractor shall deliver ACARS software that is compatible for integration into C-5M. This software shall be compatible with C-5M software baseline 4.0 and meet requirements defined in the Air Mobility Command (AMC) SMS 3.2. Delivery of this software shall be on CD/DVD media format and identified with a Government Computer Program Identification Number. CDRL B00E DI-IPSC-81429A/T Software Transition Plan (STRP); CDRL C00C DI-MCCR-80700 Computer Software Product End Items- SW Licenses

Information Assurance (IA) The contractor shall integrate Information Assurance (IA) and IA risk management into their overall systems engineering, acquisition, test and evaluation, and risk management processes in accordance with AFI33-210 Air Force Certification and Accreditation (C&A) Program (AFCAP).

IA and system security requirements for the product must be identified, traceable and documented as part of a product life cycle systems engineering process in accordance with DoDI 8500.2 or NIST SP 800-53. IA for product integration shall include the incorporation of technical and non-technical requirements to protect C5-M IT systems and data from unauthorized access and exploitation.

The contractor shall provide an analysis of IA impacts to the existing C-5M baseline as a result of the product introduction per the Government approved IMS. The IA impact analysis shall be delivered in a scientific and technical report. The impact analysis shall include the entire software chain (e.g. maintenance). Product maintenance activities include on aircraft software updates as well as process related activities for software product development and transfer.

Boundary diagrams for interfaces on the aircraft affected by the product as well as boundary diagrams illustrating the data transfer mechanisms/controls between prime contractor and subcontractors for software products and data transfer shall be provided.

The description of mechanisms and controls for software product/data transfer shall provide sufficient insight to show that the software product/data are not vulnerable to malicious code or erroneous data injected by an outside party. A follow-up detailed analysis of IA impacts stemming from the product along with recommended controls shall be identified no later than CDR.

The contractor shall provide the Government a product IA Test Plan that will result in accreditation of the C-5M aircraft-based information technology system to comply with Information Assurance policies and criteria and shall be identified per the Government approved IMS.

The contractor shall provide supporting product documentation via the contract CDRLs and Data Accession List that enables the Government to obtain IA certification of the final software product. ACARS software product IA modification assessments shall be performed, updated and delivered in a supporting scientific and technical report that identifies the IA modification’s overview, posture, and impacts. CDRL A004 DI-ADMN-81453/A Data Accession List; CDRL A006 DI-MISC-80711A/T Scientific and Technical Reports; CDRL C002 DI-MGMT-81845 Information Assurance (IA) Design Review Information Package (DRIP); CDRL C007 DI-MGMT-81844/T Information Assurance (IA) Test Plan

Airworthiness The contractor shall deliver product support documentation via the contract CDRLs and DAL that demonstrates adherence to Air Force airworthiness criteria using data generated throughout the product development activities. The contractor shall not create any data that are unique to the demonstration of airworthiness.

A System Safety Risk Assessment shall be provided as part of the product support deliverables and delivered as a scientific and technical report.

Development of product support documentation for airworthiness shall require contractor participation in External Certification Working Groups with the Government to define and review the airworthiness certification criteria to ensure that the product support deliverables are acceptable.

A modification risk assessment for the software product shall be provided as part of the supporting product documentation. The risk assessment shall include an analysis of the functional areas of the modification, detailed description of the modification, and a recommended report-ability determination in accordance with USAF Airworthiness Bulletin (AWB)-007.

Preliminary product support data flowing to and from the Government shall be exchanged with the Government using a method agreed upon by the Certification Working Group Airworthiness Certification Plan (AWCP) and shall contain the central location which product artifact data are stored.

An Airworthiness Certification Criteria/Compliance Report and Airworthiness Specification for the product shall be updated for inclusion in a consolidated deliverable document under C-5M software baseline 4.0. CDRL A004 DI-ADMN-81453/A Data Accession List; CDRL A006 DI-MISC-80711A/T Scientific and Technical Reports; CDRL C003 DI-SESS-81766 Airworthiness Specification; CDRL C004 DI-SESS-81768 Airworthiness Certification Criteria Report

CNS/ATM

The contractor shall provide supporting product artifacts via the contract CDRLs and DAL that enables the Government to obtain CNS/ATM certification of the final software product. Product support documentation for this area shall include an Required Navigational Performance (RNP) impact analysis delivered in the form of a scientific and technical report. The impact analysis shall include an appendix of tailored CNS/ATM matrices for those areas impacted by the product (e.g. data link matrices). CDRL A004 DI-ADMN-81453/A Data Accession List; CDRL A006 DI-MISC-80711A/T Scientific and Technical Reports

Interoperability The contractor shall provide supporting product artifacts via the contract CDRLs and DAL that enables the Government to obtain Joint Test Interoperability Certification (JTIC) of the final software product. Impacts to Interoperability shall be documented in the form of a scientific and technical report. CDRL A004 DI-ADMN-81453/A Data Accession List; CDRL A006 DI-MISC-80711A/T Scientific and Technical Reports

Product Baseline Management The contractor shall conduct joint reviews with the Government that identify and resolve product requirements at risk. The reviews shall be supported by the most economical and logistically feasible means available to the Government. A product design review schedule for the conduct of formal product review milestones to include a Systems Requirements Review (SRR), Software Requirements Analysis Review (SRAR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR), Functional Configuration Audit (FCA)/ Physical Configuration Audit (PCA)’s, and others shall be developed in concert with the Government. The Government defined entry/exit criteria and acceptance/rejection criteria for each formal product review shall be as defined in Appendix A.

The contractor shall support Flight Station Working Groups (FSWGs) conducted by the Government early in the product development schedule to enable product users to assess early product design concepts and provide feedback. All FSWG collected requirements shall be fully known and included in the final product design presented to the Government as part of the CDR and Verification Review Council (VRC). The contractor shall update and deliver the Human Engineering Design Approach Document -Operator and the Human Engineering Design Approach Document –Maintenance. CDRL A001, DI-ADMN-81505/T, Report, Record of Meeting; CDRL A002 DI-ADMN-81249A Conference Agenda: CDRL A00A DI-MGMT-81861, Integrated Program Management Report; CDRL C001 DI-SESS-81757A/T, Design Review Information Package (DRIP); CDRL C006 DI-HFAC-80746C/T, Human Engineering Design Approach Document-Operator; CDRL C00E DI-HFAC-80747B/T Human Engineering Design Approach Document-Maintainer

Software Product Design The contractor shall initiate, track, document and deliver updates to the product support documentation to the Government (e.g. Software Product Specifications (SPS), Software Requirements Specifications (SRS), Interface Requirements Specification (IRS), System/Subsystem Specification (SSS), Interface Control Document (ICD). The Government shall be notified if the ACARS software product updates do not affect the documents noted below.

All product changes required to implement SMS 3.2 shall be defined to the lower level product requirements, design and code to be evaluated/analyzed/verified.

The product support package deliverables shall include the following updates:

a. Update impacts and/or changes to the System/ Software Engineering Environment (S/SEE) requirements including test

b. Update the C-5M System Safety Hazard Analysis with the ACARS software update

c. Update Air Vehicle Specification requirements within DOORS™

d. Update Mission Processing Specification requirements within DOORS™

e. Update Integration Specifications requirements within DOORS™

f. Update Critical Item Development Specification Components

g. Update SRS for Communication Management Function (CMF) Computer Software Configuration Item (CSCI) within DOORS™

h. Update System/Subsystem Design Description

i. Update Software Design Documents

j. Update SPS

k. Deliver updated Software Version Descriptions

l. Update IRS

m. Update Human Engineering Design Approach Document HEDAD-O

n. Update the product ICD Input/Output (I/O) database that shall as a minimum, contain all digital data bus I/O, analog I/O, discrete I/O, spare I/O, provisional I/O, and power information along with signal characteristics information required to successfully integrate ACARS with existing C-5M systems. CDRL C006 DI-HFAC-80746C/T, Human Engineering Design Approach Document-Operator; CDRL A004 DI-ADMN-81453/A Data Accession List; CDRL A006 DI-MISC-80711A/T Scientific and Technical Reports; CDRL B002 DI-IPSC-81433A/T Software Requirements Specification; CDRL B003 DI-IPSC-81431A/T System/Subsystem Specification; CDRL B006 DI-IPSC-81434A/T Interface Requirements Specification; CDRL B007 DI-CMAN-81248A/T Interface Control Document; CDRL B008 DI-IPSC-81431A System Specification; CDRL B009 DI-IPSC-81431A System Specification CDRL C005 DI-SAFT-80101B/T SYSTEM SAFETY HAZARD ANALYSIS REPORT (SSHA); CDRL C00H DI-IPSC-81435A Software Design Description

Implement, Integrate, and Update System regression and verification tests for the product shall be developed and/or updated to a fidelity that supports integration and certification of ACARS software changes into the C-5M. CDRL C008 DI-QCIC-81536A Test Information Sheet (TIS) –VTIS; CDRL C009 DI-QCIC-81536A/T Test Information Sheet (TIS) –ITIS; CDRL C00A DI-QCIC-81536A/T Test Information Sheet (TIS) -Regression Test

Quality Assurance The contractor shall document and implement their Software Quality Program in order to deliver a product that includes software product sustainment.

Product Configuration Verification

A product Configuration Verification and Audit shall be accomplished to verify that the end product and supporting product documentation package meets the Government requirements. The contractor shall support/host the final product system level FCA and PCA and System Verification Review (SVR), with Government participation and approval for all noncompliance of product requirements. The product and supporting deliverables shall include all CDRLs noted in the Appendix B. CDRL C001 DI-SESS-81757A/T, Design Review Information Package (DRIP); CDRL C006 DI-HFAC-80746C/T, Human Engineering Design Approach Document-Operator; CDRL B001 DI-IPSC-81441A/T Software Product Specification; CDRL B004 DI-IPSC-81442A/T Software Version Description; CDRL B00E DI-IPSC-81429A/T Software Transition Plan (STRP); CDRL C002 DI-MGMT-81845 Information Assurance (IA) Design Review Information Package (DRIP); CDRL C003 DI-SESS-81766 Airworthiness Specification; CDRL C004 DI-SESS-81768 Airworthiness Certification Criteria Report; CDRL C005 DI-SAFT-80101B/T SYSTEM SAFETY HAZARD ANALYSIS REPORT (SSHA); CDRL C007 DI-MGMT-81844/T Information Assurance (IA) Test Plan; CDRL C008 DI-QCIC-81536A Test Information Sheet (TIS) –VTIS; CDRL C009 DI-QCIC-81536A/T Test Information Sheet (TIS) –IT IS; CDRL C00A DI-QCIC-81536A/T Test Information Sheet (TIS) -Regression Test; C00B DI-IPSC-81488 Computer Software Product-Source Code; CDRL C00C DI-MCCR-80700 Computer Software Product End Items- SW Licenses; CDRL C00D DI-MCCR-80700 Computer Software Product End Items-Toolsets; CDRL C00F DI-SESS-81646 Configuration Audit Plan

ACARS Program and Business Management

Program Management

a. The contractor shall establish, update and provide to the Government an IMS for product delivery. A Post-Contract Award Kickoff Meeting shall be accomplished within 45 days after contract award. The contractor shall address cost planning, project schedule, planned development activities, planned test activities, test venues, and risk management at the contract kick-off meeting. Agenda and Meeting minutes shall be created and delivered. CDRL A00A DI-MGMT-81861, Integrated Program Management Report

b. A record of contract obligations and disbursements financial execution by Contract Line Item Number (CLIN) using standard cost performance reports shall be delivered.

1. A status report reflecting the project financial overview shall be provided No Later Than (NLT) 90 calendar days after contract award. The financial overview shall show the projected spend plan for labor and material on one chart and projected travel on another chart. The financial overview charts shall contain all subcontractor cost data. The charts shall plot, by month, the actual expenditures against the baseline plan. The charts shall plot from initial award amounts showing any possible changes as a result of contract modifications. The project shall be tracked including notification of any schedule changes.

2. Any possible financial or technical changes that may impact the planned completion per the schedule and cost information shall be reported to the Government. The financial or technical changes shall either be integrated into or be as attachment(s) to the Contract Funds Status Report.

Semi-annual Program Management Reviews shall be conducted and/or supported. The first meeting shall be scheduled approximately 180 days following contract award; subsequent reviews will be held semi-annually. CDRL A003 DI-ADMN-81468/T Contract Funds Status; CDRL A005 DI-ADMN-80368A/T Status Report

Business Management

Collaboration with Government C-5 Software Integration Laboratory The contractor shall be responsible for ensuring that the product is compatible with the C-5 SIL environment at Robins AFB. All required commercial and noncommercial toolsets shall be identified and if applicable licensed and delivered to the Government.

The Government will provide updated procedures, files, and data associated with the Aircraft Modifiable Interface (AMI) database to the contractor. The modified AMI shall be integrated into the C-5M OFP builds for testing as appropriate. The contractor will not be held liable for any impacts arising from late deliveries or deficient products provided by the Government team. The contractor shall participate in joint technical interchange meetings for the exchange of data and information to support this task as identified in the Government approved program schedule.

The collaborating teams shall jointly present requirements, design, and test details at joint reviews. CDRL C00D DI-MCCR-80700 Computer Software Product End Items-Toolsets; CDRL B00E DI-IPSC-81429A/T Software Transition Plan (STRP)

Data Management In order to support delivery and certification of the final product, the contractor shall implement and retain a data management program for generating, acquiring, identifying product data, providing status, planning and controlling technical and management data and related information for product support deliverables. The contractor shall mark all deliverable technical documents, data, and information appropriately before primary distribution is accomplished (reference Department of Defense Directive 5230.24). The contractor shall generate a list of data created as part of this PD effort and make such data available for delivery to the Government via the DAL. Appropriate markings for data rights shall be identified for all items on the DAL.

Data Rights s data rights as set forth within the contract. Procurement and use of proprietary contractor/subcontractor technical data not previously delivered to the Government that are required for execution of this contract shall be the responsibility of the contractor. Certain data rights regarding The Government intends to exercise it C-5M computer software, computer software documentation and technical data have been previously negotiated under a Specially Negotiated License Agreement (SNLA) SLA-13-C5-001. Computer software, computer software documentation and technical data modified as part of the ACARS product development that are included within the SNLA shall be delivered with the level of data rights defined within the SNLA.

All product and specification documents modified under this program that are not part of the SNLA, shall be delivered with no less than Government Purpose Rights. All new requirements documents developed using program funds shall be delivered with Unlimited Rights. Those areas developed with mixed funding shall be delivered with Government Purpose Rights (Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.227-7014 (Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation) DFARS clauses 252.227.72 (Rights in Computer Software and Computer Software documentation) and DFARS clause 252.227-7014 (Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation)).

Formal Qualification Testing (FQT) Capability Although execution of a full FQT will not be performed as part of this program, a full Communication Management Function (CMF) FQT capability shall be developed and delivered to support testing of the product. The FQT capability shall meet the testing requirement of DO-178B and Mil-STD 882E. All supporting work products including test scripts and associated test procedures to accomplish a full CMF FQT as well as new or modified requirements from the ACARS software product update shall be delivered to the Government with the appropriate level of rights per the DFARS. CDRL C007 DI-MGMT-81844/T Information Assurance (IA) Test Plan; CDRL C008 DI-QCIC-81536A Test Information Sheet (TIS) –VTIS; CDRL C009 DI-QCIC-81536A/T Test Information Sheet (TIS) –ITIS; CDRL C00A DI-QCIC-81536A/T Test Information Sheet (TIS) -Regression Test

CMF Source Code A complete CMF source code product baseline and an associated license, if applicable, shall be delivered to the Government as an engineering technical reference for the sole purpose of C-5M engineering sustainment.

FILE NUMBER: FD2060-13-31352

Appendix A: Entrance/Exit Criteria

Established SSS sections 3 and 4 updated, reviewed, and available

Established lower level requirements and design available

Presentation complete and available Action items generated from review are reviewed and approved

Minutes from review are captured

Agenda complete and available

Major action items generated from review are reviewed and approved. Major Action items must be resolved no later than 90 days for close of meeting.

Presentation complete and available

Appendix B: SMS 3.2 image1.emf

(FOUO) ACARS SMS ver 3.2.pdf

For Official Use Only Version 3.2

Aircraft Communications Addressing and Reporting System (ACARS) Standard Message Set (SMS)

For

Mobility Air Forces (MAF) Aircraft

As of 2 August 2012

Approved by:

2/1/2013

X MICHAEL S. MAREK

Signed by: MAREK.MICHAEL.S.1094292219

MICHAEL S. MAREK, GS-13, DAFC

MAF C2 Core Services Program Manager

OPR: HQ AMC/A6OC

Table of Contents

Contents

1 Scope

1.1 Purpose

1.2 ACARS Overview

1.3 Message Set Parameters

1.4 Office of Primary Responsibility (OPR)

2 Applicable Documents

2.1 Government Documents

2.2 Non-Government Documents

3 Downlink Message Specifications

3.1 Request for Initialization Data

3.2 Out, Off, On, In (OOOI) Report

3.3 Summary Report

3.4 Position Data

3.5 Free Text

3.6 Flight Plan Request

3.7 Request for Weather Data

3.8 Weather (PIREP) Report

3.9 Cargo Report

3.10 Air Evacuation Report

3.11 Tanker Air Refueling Report

3.12 Receiver Air Refueling Report

3.13 Engine Report

3.14 Flight Plan Report

3.15 Response for Flight Plan Uplink

3.16 Air Drop Report

3.17 In-Range/Ramp Services Report

3.18 Emergency Report

3.19 Wind Data Request

3.20 Structural Data

3.21 Waypoint List Report

3.22 Disconnect

3.23 Reject

4 Uplink Message Specifications

4.1 Initialization Message

4.2 Free Text

4.3 Weather (PIREP) Request

4.4 Air Evac Load Message

4.5 Flight Plan Route

4.6 Position Report Request

4.7 Weather Report

4.8 Wind Data Response

4.9 Structural Report Request

4.10 Cargo Report Request

4.11 Summary Message Report Request

4.12 Flight Plan Report Request

4.13 Waypoint List Request

4.14 Engine Report Request

APPENDIX 1: IEI and IMI List

Downlink IEI (With Associated IMI) Uplink IEI (With Associated IMI)

APPENDIX 2: Changes From 3.01

Page 1 For Official Use Only Version 3.2

1 Scope

1.1 Purpose

The purpose of this requirements specification is to standardize the Air Mobility Command (AMC) Airline Operational Control (AOC) Aircraft Communications Addressing and Reporting System (ACARS) data link message set.

This standard is intended to provide both avionics vendors and ground system developers a specific depiction of ACARS messaging with sufficient detail to avoid ambiguities inherent with multiple vendor approaches to ACARS fielding and differences across various aircraft platform reporting capabilities.

Avionics vendors should incorporate this standard to the greatest extent possible; however, it is understood that not all aircraft platforms will permit the development of each message contained in this standard.

1.2 ACARS Overview

The Aircraft Communications Addressing and Reporting System (ACARS) is an unclassified, un-encrypted data link message system which allows command and control (C2) agencies using airline operational control (AOC) messages and air traffic controllers using air traffic services (ATS) messages to communicate directly with individual aircraft in all phases of flight.

AMC utilizes Inmarsat Aero-I Satellite Communications Data Link (SATCOM DL), Very High Frequency Data Link Mode 2 (VDLM2), and High Frequency Data Link (HFDL) for sending and receiving AOC messages from mobility aircraft. With ACARS AOC, aircraft operate as integral parts of an airline’s C2 and management systems.

ACARS is dependent upon a global enterprise comprised of aircraft avionics subsystems, commercial communications services (Inmarsat, HF, VHF), Data Link Service Provider proprietary global ground networks, air traffic service facility subsystems, and each air carrier’s C2 and management subsystems.

The Airlines Electronic Engineering Committee (AEEC) defines equipment and protocols used on the air/ground channel within their documentation.

Page 2 For Official Use Only Version 3.2

1.3 Message Set Parameters

1.3.1 For vendors, individual ACARS messages which cannot be implemented in whole due to aircraft limitations may either be required to provide estimates to enable development of the message or simply omit the message entirely for that aircraft platform. The government aircraft program office pertaining to implementation of this standard message set will provide a copy of all levied vendor ACARS-related documentation to the OPRs listed in paragraph 1.4.

1.3.2 When individual ACARS messages are implemented only in part due to aircraft limitations, or when the aircraft design inherently prohibits single or multiple field element reporting within a given message, vendors should develop the message in full as depicted in this standard and institute null values for those elements which cannot be implemented.

1.3.3 Message construct begins with an ARINC 702A-3 like format by using Imbedded Message

Identifiers (IMI) and Imbedded Element Identifiers (IEI). However, it is not necessary to adhere to IMI and/or IEI relationships or definitions as listed in 702A-3. It is only necessary to be consistent in IMI and IEI definitions as depicted in this standard. A complete listing of IMIs and IEIs found in this standard are maintained in APPENDIX 1 to this document.

1.3.4 Each IEI is preceded by a "/" and data elements within each IEI are separated by a comma, unless otherwise specified. Missing or omitted IEI data elements will be preceded by a comma for those IEIs containing more than one data element. For IEIs with only one data element and that element is omitted, no IEI label or comma is necessary.

1.3.5 Ground C2 systems and avionics vendors should develop to this standard in its entirety and permit null values in all fields with the exception of:

Aircraft Registration Number (ACARS Address)

Call Sign

Mission Number (EXCEPTION: Crew entry of Mission Number on 3.1 Request For Initialization Data is optional)

Date/Time (avionics-generated, for downlinks only)

Message Identification Number (MIN)

Message Reference Number (MRN) to be used for uplinks and downlinks to correlate a response message

Message Set Version Number (for all downlink messages only)

Mandatory UPLINK IEIs are identified in Section 4

1.3.6 To the greatest extent possible for both avionics vendors and C2 system developers, automation is desired for populating field elements.

1.3.7 ACARS data is American Standard Code for Information Interchange (ASCII) character based and consists only of non-control characters of the ISO 5 character set.

1.3.8 Free text elements must not permit use of comma and "/", as these are delimiters between elements.

1.3.9 There are no spaces between data elements. Spaces are only allowed in free text or pre-formatted messages such as the weather data uplink.

Page 3 For Official Use Only Version 3.2

1.3.10 Each message (downlink and uplink) will embed a 4-character 16-bit Cyclic Redundancy Check calculated with the first character of the IMI and ending with the fifth to last character of text. The last 4 characters are the embedded CRC.

1.3.11 The elements in the MR IEI shall consist of a Message Identification Number (MIN) followed by an optional Message Reference Number (MRN) in format: NNN,NNN. The MIN for each downlink message shall be sequentially assigned beginning with zero thru 999. The MRN shall be used to correlate a downlink response to an uplink message or an uplink response to a downlink message. The MRN shall echo the MIN of the associated message.

1.3.12 All time references are in GMT.

1.4 Office of Primary Responsibility (OPR)

1.4.1 HQ AMC/A6OC, Data Link and Aviation Services Management Office is OPR for operational

ACARS data link services, message set specification, and this document.

1.4.2 HQ AMC/A3CS is OPR for Mobility Enterprise Information Services (MEIS) interface requirements.

1.4.3 HQ AMC/A3RP is OPR for platform requirements.

1.4.4 HQ AMC/A5QS is OPR for platform interface development.

1.4.5 HQ AMC/A6CI, Engineering Section is OPR for MEIS interface development and operational support.

2 Applicable Documents

2.1 Government Documents

The following documents form a part of this specification to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this specification, the contents of this specification shall be considered a superseding requirement:

Aircraft Communications Addressing and Reporting System (ACARS) Concept of Employment (CONEMP) and Standardized Message Set, Version 1.3, 1 March 2010.

2.2 Non-Government Documents

The following documents form a part of this specification to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this specification, the contents of this specification shall be considered a superseding requirement:

Air/Ground Character-Oriented Protocol Specification, ARINC Specification 618-6, June 16, 2006

Datalink Ground System and Interface Specification, ARINC Specification 620-6, November 15, Advanced Flight Management Computer System, ARINC Characteristic 702A-3, December 15, Page 4 For Official Use Only Version 3.2

3 Downlink Message Specifications

3.1 Request for Initialization Data

IMI: REQINI

Message Description: Crew manually establishes AOC Link Connectivity with ground system via this message. Ground system will respond by automatically generating and sending the Initialization Uplink Message with matching sortie details of Aircraft Registration Number, Call Sign and Mission Number.

Field Definitions:

IEI

SEQ

ID

Field Name

Length (F/V)

Char

(A/N/AN)

Max

Scale Units Range

ID 1

Aircraft Registration Number (ACARS Address with fleet ID) F AN 6

2 Call Sign V AN 7

Mission Number (optional) F AN 12

DC 1 Avionics-Generated Date F N 8 DDMMYYYY

2 Avionics-Generated GMT F N 6 HHMMSS

MR 1

Message Identification Number V N 3

0 - 999

Message Reference

FB 1 Fuel On Board V N 4 0.1 Klbs 0 - 9999

VR 1 Message Set Version # V N 3 0.1

30 - 999

CRC F AN 4

Example: REQINI/ID00177A,RCH858,AVR20X8A1220/DC09082010,160318/MR0,/FB1309/VR30CRCX

Standard Business Rule(s): It is desired that Aircraft Registration Number (ACARS Address), Call Sign and Mission Number (when entered by crew) match between this downlink and the corresponding Initialization Message uplink. If any or all of this information does not match, the airborne system will automatically generate a REJINI reject message. Ground system receipt of a REJINI message shall drive an alert notification to the user.

3.2 Out, Off, On, In (OOOI) Report

IMI: OOI

Message Description: When key events occur, the airborne system will automatically send the following messages:

Block Out, defined as initial aircraft movement under its own power Takeoff, defined as aircraft weight off wheels (airborne) Landing, defined as aircraft on the ground after having been airborne and ground speed prohibiting takeoff (no touch and go reporting) Block In, defined as final stop in assigned parking spot

Page 5 For Official Use Only Version 3.2

3 Mission Number F AN 12

DC 1

Avionics-Generated Date F N 8 DDMMYYYY

GMT F N 6 HHMMSS

Above is common to all OOOI message types (OUT, OFF, ON, IN).

OT

1 Block Out Day/Time F N 6 DDHHMM

First Engine Start Day/Time (Only the OOOI OUT and SUMMARY Reports will display this value.) F N 6 DDHHMM

First Engine Start Fuel On Board (Only the OOOI OUT and SUMMARY Reports will display this value.) F N 4 0.1 Klbs 0000 - 9999

CG 1 Center of Gravity V N 4 0.1 % 0 - 9999

Center of Gravity Limits (Lower) V N 4 0.1 % 0 - 9999

(Upper) V N 4 0.1 % 0 - 9999

OF 1 Takeoff Day/Time F N 6 DDHHMM

ON 1 Landing Day/Time F N 6 DDHHMM

Page 6 For Official Use Only Version 3.2

IN 1 Block In Day/Time F N 6 DDHHMM

Last Engine Shut Down Day/Time (Only the OOOI IN and

Example:

OOI/ID66156A,E66156,PLW04164A221/DC09082010,162354/MR5,/OT091623,091601,1336/CG0026,0

021,0030/FB1309/VR30CRCX

Standard Business Rule(s): May include the ability for a manual IN report for ERO conditions which will not generate the automatic summary report.

3.3 Summary Report

IMI: SUM

Message Description: Immediately after generation of an automatic Block In Report or in response to a Summary Message Report Request uplink, the airborne system will automatically send the Summary Report. The Summary Report provides: First Engine Start Day/Time with FOB, Last Engine Shut Down Day/Time with FOB, Latest Sortie Block Out Day/Time and FOB, Latest Take-off Day/Time and FOB, Latest Landing Day/Time with FOB and Latest Block In Day/Time and FOB.

SM 1

First Engine Start Day/Time (Only the OOOI OUT and

Page 7 For Official Use Only Version 3.2

First Engine Start Fuel On Board (Only the OOOI OUT and display this value.) V N 4 0.1 Klbs 0 - 9999

Last Engine Shut Down Day/Time (Only the OOOI IN and

Latest Block Out Day/Time F N 6 DDHHMM

Latest Block Out Fuel On Board V N 4 0.1 Klbs 0 - 9999

Latest Take-Off Day/Time F N 6 DDHHMM

Latest Take off Fuel On

8 Latest Landing Day/Time F N 6 DDHHMM

Latest Landing Fuel On

10 Latest Block In Day/Time F N 6 DDHHMM

Latest Block In Fuel On

SUM/ID77189A,RCH7189,AVYN85120209/DC09082010,164444/MR36,/SM090816,1250,091643,09082

6,1230,090832,1170,091639,201,091644,182/VR30CRCX

3.4 Position Data

IMI: POS

Message Description: This downlink is normally transmitted automatically, but can be manually initiated, and provides aircraft position information to ground system. Position Reports also include weather information along the planned route of flight that can be routed automatically into the applicable weather models.

Page 8 For Official Use Only Version 3.2

ET 1

ETA (TO Destination) Day/Time Group F N 6 DDHHMM

PS 1

Current Position Lat/Long F AN 13

2 Time at Current Position F N

6 HHMMSS

3 Current MSL Altitude V N 3 100 Ft 0 - 999

TO Waypoint (Navaid, Fix, Airport, Lat/Long) V AN 13

5 ETA (TO Waypoint) F N 6 DDHHMM

NEXT Waypoint

7 Static Air Temperature

Directional F A 1 "P" or "M"

Temp V N 2 1 Celsius 0 - 99

8 Actual Wind

Direction F N 3 Deg 001 - 360

Magnitude V N 3 Kts 0 - 300

Current Speed (MACH and/or TAS)

MACH F N 4 .001 Mach “M”000 - 999

TAS V N 4 Kts “T”0 - 999

POS/ID44136A,MOOSE80,ABR06Z8X0210/DC09082010,175547/MR24,/ET090247/PSN30142E065062, 175547,240,DAVER,090146,N29080E064250,M14,088010,M862/CG021,011,034/FB893/VR30CRCX

Standard Business Rule(s): Position Report default mode is waypoint position reporting enabled.

3.5 Free Text

IMI: FTX

Message Description: Free Text provides the aircrew the capability to share information with a ground user via an e-mail like capability.

Page 9 For Official Use Only Version 3.2

FX 1 Free Text V AN 256 A…Z, 0…9, ".", " ", "(", ")", FTX/ID77172A,RCH413,PJM105271211/DC09082010,192242/MR22,/FXCAN YOU SEND FUEL FOR

NEXT LEG/FB123/VR30CRCX

3.6 Flight Plan Request

IMI: REQFPN

Message Description: The Flight Plan request message enables the crew to request an active, secondary or provisional flight plan for the current sortie. Adherence to FPEIs IAW ARINC 702A-3 is required. Requests for follow-on flight plans for next sortie or mission are simple free text requests to the C2 controller.

RP

RA

RM

Flight Plan Request Type

"RP" – ACTIVE

"RA" – SECONDARY

“RM” – MODIFICATION

(USE ARINC 702A-3

FPEIs)

REQFPN/ID77172A,RCH413,PJM105271211/DC09082010,192242/MR22/RM/FB123/VR30CRCX

Page 10 For Official Use Only Version 3.2

3.7 Request for Weather Data

IMI: REQWXR

Message Description: The aircrew can request Air Refueling, Air Drop, Terminal Area Forecast (TAF) and Enroute weather information from the weather forecaster. Additionally, crews can request or cancel hourly TAF reports.

WX 1

Weather for Day/Time Group (ETA at ARCP for Air Refuel, ETA at CARP for Air Drop, ETA at Destination for TAF) F N 6 DDHHMM

2 Weather Request Type F N 1

"0" - AIR REFUEL, "1" -

AIR DROP, "2" - TAF, "3" –

ENROUTE, “4” – Hourly TAF, “5” – Cancel Hourly

TAF

3 Airfield (for TAF) ICAO V AN 4 A…Z, 0…9

4 AR Track ID (for AR) V AN 7 A…Z, 0…9

5 AR Track Direction V A 2

N, S, W, E, NW, NE, SW

or SE

6 ARCP Lat/Long (for AR) F AN 13

7 AR Altitude V N 3 100 Ft 0 - 999

8 DZ Code Name (for AD) V AN 7

9 PI Lat/Long (for AD) F AN 13

10 PI Altitude (for AD) V N 3 100 Ft 0 - 999

PI Surface Winds (for

AD)

Direction F N 3 1 Deg 001 - 360

Magnitude V N 3 1 Kts 0 - 300

12 PI Ceiling (for AD) V N 3 100 Ft 0 - 999

13 PI Visibility (for AD) V N 3 1 Miles 0 - 999

14 AD Altitude V N 3 100 Ft 0 - 999

Page 11 For Official Use Only Version 3.2

REQWXR/ID88190A,RCH109,AAM197008218/DC10082010,160315/MR22,/WX101715,2,FJDG,,,,,,,,,,,/F

B563/VR30CRCX

3.8 Weather (PIREP) Report

IMI: RESWXR (If in response to an uplink request) or WXR (If crew initiated)

Message Description: When an aircrew experiences significant weather that has not been forecast, they can manually submit a Pilot Report (PIREP), or they may send the PIREP in response to an uplink request for the PIREP (REQWXR).

LL 1

PI 1 Actual Wind

2 Current MSL Altitude F N 3 100 Ft 0 - 999

3 Static Air Temperature

Temp V N 2 1 Celsius 0 - 99

4 Icing Type F N 1

"0" - NONE, "1" - MIX, "2" -

CLEAR, "3" - RIME

5 Ice Amount F N 1

"0" - NONE, "1" - TRACE,

"2" - LIGHT, "3" - MOD, "4"

- SEVERE

6 Turbulence Condition F N 1

"0" - NONE, "1" - LIGHT,

"2" - MOD, "3" - SEVERE,

"4" - EXTREME

7 Clouds F N 1

"0" - NONE, "1" - IN, "2" -

ABOVE, "3" - BELOW

RESWXR/ID00185A,RCH123,AMRA77462223/DC10082010,090451/MR22,/LLN26385E063397/PI12312

,260,M17,0,0,0,0/FXGOOD FLYING/FB1453/VR30CRCX

Page 12 For Official Use Only Version 3.2

3.9 Cargo Report

IMI: CRG

Message Description: The Cargo Report is used as a summary of the cargo and passengers on-loaded and off-loaded.

ETA at Destination

CR 1 Number of Crew V N 2 1 - 99

Number of AE Crewmembers V N 2 1 - 99

3 Total Number of PAX V N 3 0 - 999

4 Number of PAX Off V N 3 0 - 999

Number of PAX Through V N 3 0 - 999

Number of Seats Released V N 3 0 - 999

7 Number of DV V N 3 0 - 999

8 Highest DV Code F N 1 1 - 7

CD 1

Total On Board Cargo Weight V N 4 0.1 Klbs 0001 - 9999

Total Off-load Cargo

Number of On Board Pallets V N 2 0 - 50

Number of Off-load Pallets V N 2 0 - 50

Rolling Stock V N 2 0 - 99

Number of On-load Rolling Stock V N 2

0 - 99

Number of Human Remains On Board V N 3 0 - 999

HZ 1 Hazmat Code V N 2 0.1 00 - 99

2 Net Explosive Weight V N 4 0.1 Klbs 0001 - 9999

ML 1 Registered Mail Weight V N 4 0.1 Klbs 0001 - 9999

2 Registered Mail Pieces V N 4 0 - 9999

Signature Service

Page 13 For Official Use Only Version 3.2

Pieces V N 4 0 - 9999

Guard Required? F A 1 "Y", “N”

Courier Material? F A 1 "Y", “N”

OP 1 ACFT Operating Weight V N 6 0.1 Klbs 0 - 999999

2 ACFT Configuration V AN 5

A…Z, 0…9 (Ex. AE1)

ACFT Configuration Weight (crew weight + PAX seating pallets + armor, etc.) V N 4 0.1 Klbs 0 - 9999

Total ACFT Operating Weight (operating weight + configuration weight) V N 4 0.1 Klbs 0 - 9999

5 PAX Weight V N 5

Lbs 0 - 99999

Baggage Weight (zero if baggage weight is included in PAX weight) V N 5

Lbs 0 - 99999

Total Payload Weight (total weight of all cargo, PAX, baggage, mail, etc.) V N 6 0.1 Klbs 0 - 999999

ACFT Gross Weight (sum of total ACFT operating weight, total payload weight and current fuel weight) V N 6 0.1 Klbs 0 - 999999

A…Z, 0…9, ".", " ", "(", CRG/ID70042A,RCH122,AMRA77439219/DC10082010,032102/MR22,/ET080613/CR3,0,0,0,0,0,0,/CD5 15,515,13,13,0,0,0/ HZ,/ML,,,,,/OP4796,,,,2185,997,,/CG170,009,023/FB1263/VR30CRCX

Standard Business Rule(s): For ETA at destination, populate default per flight plan but allow an over-write. For weights, enable Kg entry but display and transmit as lbs.

3.10 Air Evacuation Report

IMI: EVC

Message Description: The Air Evacuation Report provides the aircrew the capability to report the results of Air Evacuation movements including number and types of patients onloaded/offloaded.

Page 14 For Official Use Only Version 3.2

AE 1

Patients V N 3 0 - 999

Number of Outbound Patients Next Station V N 3 0 - 999

Litters V N 3 0 - 999

Litters V N 3 0 - 999

Litters V N 3

Litters Next Station V N 3 0 - 999

Number of Ambulatory Patients On Board V N 3 0 - 999

Number of Ambulatory Patients Off-load V N 3 0 - 999

Patients On-load V N 3

Ambulatory Patients Next Station V N 3 0 - 999

Attendants V N 3 0 - 999

Attendants V N 3 0 - 999

Attendants V N 3

Attendants Next Station V N 3 0 - 999

Released V N 3 0 - 999

MP 1

Number of Urgent Patients Outbound Next Station V N 2 0 - 99

Number of Priority

Number of Special

Page 15 For Official Use Only Version 3.2

EVC/ID33115A,RCH450,7DNGK11MR212/DC10082010,205256/MR22,/ET010230/AE0,0,33,0,13,13,13, 0,20,20,20,0,8,0,0,8,27/MP0,6,0/FB883/VR30CRCX

3.11 Tanker Air Refueling Report

IMI: TRF

Message Description: The Tanker Air Refueling Report provides the aircrew the capability to report the status of tanker aerial refueling events.

0 – 999

TR 1

Takeoff Day/Time Group

GMT F N 6 DDHHMM

2 Total Fuel Issued V N 4 0.1 Klbs 0 - 9999

3 Fuel Grade V AN 5 ex. JP8, JPTS

AR Event Data (1-20 events with all the following data):

4 Event Type F N 1

"0" - ONLOAD, "1" -

OFFLOAD

Refueling Area/Track ID and Direction V AN 10 A…Z, 0…9

6 ARCP Lat/Long F AN 13

7 Begin AR Time F N 6 DDHHMM

8 End AR Time F N 6 DDHHMM

End AR Position (Lat/Long, navaid, fix, waypoint) V AN 13

10 End AR Fuel On Board V N 4 0.1 Klbs 0 - 9999

Command of Receiver Aircraft V AN 3

12 Receiver Aircraft MDS V AN 6 A…Z, 0…9

13 Receiver Tail Number V AN 8 A…Z, 0…9

14 Fuel Quantity Issued F N 4 0.1 Klbs 0000 - 9999

15 Receiver Call Sign V AN 7 A…Z, 0…9

Receiver Home Station

ICAO V AN 4 A…Z, 0…9

Page 16 For Official Use Only Version 3.2

TRF/ID71469S,FUELR40,AJUM75206223/DC11082010,005302/MR22,/TR111020,0334,JP8,1,318E,N2 6385E063397,111145,111202,N26385E063397,1280,AMC,C017A,044135,0334,RCH026,KDOV/FXALL

GOOD/FB1263/VR30CRCX

Standard Business Rule(s): SEQ ID 4 through 16 of the TR IEI shall be separated by comma. A period shall be encoded after SEQ ID 16 for multiple AR Event Data.

3.12 Receiver Air Refueling Report

IMI: RRF

Message Description: The Receiver Air Refueling Report provides the aircrew the capability to report the status of a receiver aerial refueling event. The aircrew may use free text to report the status of an unsuccessful aerial refueling event.

RZ 1

Refueling Area/Track ID and Direction V AN 10 A…Z, 0…9

2 ARCP Lat/Long F AN 13

3 AR Control Time F N 6 DDHHMM

4 Begin AR Time F N 6 DDHHMM

5 Fuel Quantity Received V N 4 0.1 Klbs 0 - 9999

End AR Position waypoint) V AN 13 A…Z, 0…9

7 End AR Time F N 6 DDHHMM

Page 17 For Official Use Only Version 3.2

RRF/ID44135A,RCH026,AJUM75206223/DC11082010,005302/MR23,/RZ318E,N26385E063397,111230

,111235,0324,318,111249/FB1663/VR30CRCX

3.13 Engine Report

IMI: ENG

Message Description: The Engine Report provides engine trending Information in an expeditious manner. Upon receipt of a valid Engine Report Request uplink (i.e., REQENG), the airborne system will automatically send separate and consecutive engine reports, one for each engine.

FOR THIS MESSAGE ONLY, VENDORS MAY IMPLEMENT A VERSION OF THIS MESSAGE MOST

APTLY SUITED TO THEIR PARTICULAR PLATFORM PARAMETERS AS WELL AS TRIGGERS

WHICH WILL GENERATE THE REPORT. Below table is example only.

PC 1 AC Pack - Cabin F A 1 "N" or "Y"

2 AC Pack - Cargo F A 1 "N" or "Y"

EN 1 Engine Model Number V AN 15 A…Z, 0…9, "-"

2 Engine Data (1,2,3,4) F N 1 "1", "2", "3", "4"

Power Level Angle, Thrust/Power Lever Angle or Power Control Lever V N 2 Deg 0 - 90

4 N1/NG V N 4 0.1 % RPM 0 - 1100

5 N2/NP V N 4 0.1 % RPM 0 - 1100

6 EGT/TIT V N 4 1 Celsius 0 - 1000

7 Torque

Level V N 5 1 Inch Lbs 0 - 25000

8 Oil Press V N 4 0.1 Psid 0 - 3000

9 Oil Temp

Temp V N 4 0.1 Celsius 0 - 4000

10 Fuel Flow (FF) V N 5 1 PPH 0 - 24000

Fuel Flow Performance Deviation

Directional

"P" or "M"

Percent Deviation V N 2 %FF Dev 0 - 99

Page 18 For Official Use Only Version 3.2

Throttle Vibration (if present) V N 4

"1", "2", "3" and/or "4", representing applicable engine number(s) with a throttle vibration indication

Average Engine Pressure Ratio V N 3 0.01 0 - 999

14 Average Fan Speed V N 3 0.1 0 - 999

ENG/ID44135A,RCH026,AJUM75206223/DC11082010,005302/MR23,/PCY,Y/ENTF33-PW-

102,1,995,1700,P12,,770,698/VR30CRCX

Standard Business Rule(s): The default state (at power-up) shall be engine automatic reporting “disabled.” The C2 system (via the Engine Report Request uplink message) will be able to toggle automatic reporting on, off, or request a one-time report. Once reports have been “enabled,” besides reporting at pre-established triggers as determined by the vendor, reports should be generated whenever an engine fault is detected. Additionally, a ground maintenance procedure shall easily allow the default state to be changed to enable automatic engine trend reporting should there be a future need for fleet-wide data capture. Once the default setting has been changed, it will remain changed through power cycles until ground maintenance procedure changes the default state again.

3.14 Flight Plan Report

IMI: FPN

Message Description: Both the aircrew and AMC C2 controller can trigger the Computer Flight Plan downlink of the aircrew’s active, secondary or modification flight plan. An AMC C2 controller can trigger this message by sending a Request for Flight Plan Data uplink message and the airborne system will automatically generate the flight plan downlink.

RA

RM 1 Flight Plan Type

"RA" – SECONDARY

“RM” – MODIFICATION

See ARINC 702A-3

Page 19 For Official Use Only Version 3.2

(See ARINC Standard 702A-3 for flight plan message specification.)

3.15 Response for Flight Plan Uplink

IMI: RESFPN

Message Description: The Flight Plan Response Message allows the aircrew to accept or reject the AMC C2 controller-provided computer flight plan.