Advanced Flight Management Computer System

Project Initiation/Modification proposal for the AEEC
Date Proposed: October 16, 2014
ARINC Project Initiation/Modification (APIM)
1.0
Name of Proposed Project
APIM 14-004
ARINC Characteristic 702A Supplement 4 - Advanced Flight Management
Computer System
1.1
Name of Originator and/or Organization
Ken Jongsma, Honeywell International
2.0
Subcommittee Assignment and Project Support
2.1
Suggested AEEC Group and Chairman
Systems Architectures and Interfaces (SAI), Bob Semar, Chairman
2.2
Support for the activity (as verified)
Airlines: United, Southwest, FedEx
Airframe Manufacturers: Airbus, Boeing
Suppliers: Honeywell, Thales, GE
Others:
2.3
Commitment for Drafting and Meeting Participation (as verified)
Airlines: N/A
Airframe Manufacturers: N/A
Suppliers: N/A
Others: N/A
2.4
Recommended Coordination with other groups
None
3.0
Project Scope (why and when standard is needed)
ARINC 702A currently defines weather uplink and downlink information to the
FMS through the PWI (Predicted Wind Information) message. This message
contains mainly wind information but also one possible ISA deviation. The ARINC
standard also defines a PWM (Predicted Wind Modification) message that can be
used to append wind and temperature information used by the system.
As part of the SESAR 9.1 Initial 4D (I4D) function definition project, a
requirement for improving the aircraft Required Time of Arrival (RTA) to 10 sec
accuracy & 95% reliability was established. To meet this requirement, the need
for improved onboard weather modeling was raised to support the performance
and reliability need.
Page 1 of 4
Updated: March 2012
3.1
Description
The proposed change to ARINC 702A shall be limited to the additional
temperature parameters required to support the improved RTA requirement and
associated error codes. The proposed change ensures compatibility with existing
systems using only wind uplinks by using independent temperature definition.
To support the uplink for up to 10 temperatures, for both climb and descent
segments (no update was deemed necessary for enroute segment that already
contain one temperature by level on waypoints), it is necessary to:
•
•
•
Define new IEIs and content to add temperatures in existing PWI/PWM
uplink messages
Define new IEIs and content to add temperatures request in PWI/PWM
downlink messages
Define associated Failure Codes
Additional detail and justification can be found in the associated whitepaper and
draft change pages, prepared by Honeywell.
3.2
Planned usage of the envisioned specification
Note: New airplane programs must be confirmed by manufacturer prior to
completing this section.
New aircraft developments planned to use this specification
Airbus: (aircraft & date)
Boeing: (aircraft & date)
Other: (manufacturer, aircraft & date)
yes
no
Modification/retrofit requirement
yes ☐ no ☒
Specify: Airlines may opt to update FMS to accommodate change.
Needed for airframe manufacturer or airline project yes ☒ no ☐
Specify: SESAR Very Large Demonstration Project
Mandate/regulatory requirement
yes ☐ no ☒
Program and date:
Is the activity defining/changing an infrastructure standard?
yes ☐ no ☒
Specify: (e.g., ARINC 429)
When is the ARINC standard required?
Immediately
What is driving this date? SESAR Very Large Demonstration projects scheduled
for 2017.
no
Are 18 months (min) available for standardization work? yes
If NO please specify solution: Draft change pages have already been
prepared.
Are Patent(s) involved?
yes ☐ no ☒
If YES please describe, identify patent holder: _________________
Page 2 of 4
Updated: March 2012
3.3
Issues to be worked
None – the proposed change has been verified in multiple SESAR flight trials.
4.0
Benefits
4.1
Basic benefits
Operational enhancements
For equipment standards:
Is this a hardware characteristic?
yes
no ☐
yes
no
Is this a software characteristic?
yes ☒ no ☐
Interchangeable interface definition?
yes ☒ no ☐
Interchangeable function definition?
yes ☒ no ☐
If not fully interchangeable, please explain: _________________
Is this a software interface and protocol standard? yes ☒ no ☐
Specify: _________________
Product offered by more than one supplier
Identify: Thales, Honeywell
4.2
yes ☒ no ☐
Specific project benefits (Describe overall project benefits.)
Definition of message formats for uplink temperatures to support future RTA
requirements.
4.2.1
Benefits for Airlines
Ability to meet I4D RTA accuracy requirements.
4.2.2
Benefits for Airframe Manufacturers
N/A
4.2.3
Benefits for Avionics Equipment Suppliers
Ability to implement temperature uplinks required to meet I4D requirements in a
standardized manner.
5.0
Documents to be Produced and Date of Expected Result
Supplement 4 to ARINC Characteristic 702A: ADVANCED FLIGHT
MANAGEMENT COMPUTER SYSTEM by 4Q 2014.
Page 3 of 4
Updated: March 2012
5.1
Meetings and Expected Document Completion
The following table identifies the number of meetings and proposed meeting days
needed to produce the documents described above.
Activity
Mtgs
Mtg-Days
(Total)
Expected
Start Date
Expected
Completion
Date
Characteristic
702A-4
0
0
5/2014
10/2014
Please note the number of meetings, the number of meeting days, and the
frequency of web conferences to be supported by the IA Staff.
Note:
Meeting not required. Work has already been completed.
6.0
Comments
None
6.1
Expiration Date for the APIM
December 2014
Completed forms should be submitted to the AEEC Executive Secretary.
Page 4 of 4
Updated: March 2012

Download Report