Attachment 10 - NAS-IR-23040001.pdf

FOR OFFICIAL USE ONLY

Public availability to be determined under 5 USC 552

U. S. Department of Transportation

Federal Aviation Administration

Interface Requirements Document

Operational and Supportability Implementation System (OASIS) to

External Users

NAS–IR–23040001

Revision C

03/26/2025

NAS–IR–23040001

03/26/2025 ii

FOR OFFICIAL USE ONLY

Interface Requirements Document Approval Signature Page

Operational and Supportability Implementation System (OASIS) to External Users

Approval Signatures

NAS

Name Organization Signature Date Signed

Gina Oliver AJW-17 03/26/2025

03/26/2025 iii

Public availability to be determined under 5 USC 552

Revision/Level Date Notes

A December 17, 1999 Initial OASIS CONUS delivery

B August 11, 2014 OASIS Alaska Implementation

C March 26th, 2025 New ICAO Format Implementation, Decommis-sioned Systems Removal, New Interfaces Addi-tions (HUMA, NDP). See SDR-OASIS-013.

Revision History

03/26/2025

FOR OFFICIAL USE ONLY

iv

1 SCOPE

1.1 Summary

1.2 Subsystem Responsibility

2 Applicable Documents

2.1 Government Documents

2.1.1 FAA Specifications

2.1.2 FAA Standards

2.1.3 FAA Orders

2.2 Non-Government Documents

3 Interface Requirements

3.1 General Requirements

3.1.1 Security Requirements

3.1.1.1 Information System Security (ISS)

3.1.1.2 Internet Interface

3.1.1.3 Web Service

3.1.1.4 Non-FAA Connections

3.1.1.5 Personnel Security

3.1.2 OASIS Required External Interfaces

3.1.3 Data Types

3.2 Functional Requirements

3.2.1 General Services Requirements

3.2.2 APs and Message Requirements

3.2.2.1 Identification of Each AP

3.2.2.2 AP Capability Requirements

3.2.2.3 Message Content Requirements

3.2.2.4 Relationship Among Messages

3.2.2.5 Quality of Service (QoS) Requirements

3.2.2.6 Error Handling Requirements

3.2.2.7 Interface Summary Tables

3.2.3 Protocol Implementation

3.2.3.1 Application Layer Services

3.2.3.2 Transport Layer Services

3.2.3.3 Naming and Addressing

3.3 Physical Requirements

3.3.1 Electrical Power and Electronic Requirements

3.3.1.1 Connectors

3.3.1.2 Wire/Cable

3.3.1.3 Grounding

3.3.1.4 Fasteners

3.3.1.5 Electromagnetic Compatibility

4 Quality Assurance Provisions

4.1 Responsibility for Verification

4.2 Special Verification Requirements

Table of Contents

03/26/2025

FOR OFFICIAL USE ONLY

v

4.3 Verification Levels and Methods

4.3.1 Verification Levels

4.3.2 Verification Methods

4.4 VRTM

5 Preparation for Delivery 6 Notes

6.1 Definitions

6.2 Abbreviations and Acronyms

Appendix A. Message Formats A.1 NMR Message Format A.2 Information Unit Format A.3 Acknowledgment Message A.4 QALQ Request A.5 QALQ Cancellation A.6 QALQ Response A.7 INREQ Request A.8 INREQ Cancellation A.9 INREQ Response A.10 ALNOT Request A.11 ALNOT Cancellation A.12 ALNOT Response A.13 Change ETA A.14 Civil Domestic Flight Notification A.15 Flight Plan Closure and Cancellation A.16 Proposed VFR Flight Plan A.17 Proposed IFR Flight Plan A.18 Military Flight Notification A.19 Military Stopover Flight Notification A.20 Military Departure A.21 Military Operations

A.21.1 IR Message A.21.2 IR Cancellation

A.21.3 VR

A.21.4 VR Cancellation Message

A.21.5 MOA

A.21.6 MOA Cancellation

A.22 Mexican Flight Notification A.23 IFR Flight Plan A.24 General Facility A.25 Law Enforcement

A.25.1 NDP LE Contact A.25.2 EPIC Law Enforcement

A.26 ATCSCC

Table of Contents (Continued)

03/26/2025

FOR OFFICIAL USE ONLY

vi

A.26.1 Single Part ATCSCC A.26.2 Multiple Part ATCSCC

A.27 Stereo Flight Plan A.28 Cancellation A.29 ICAO SAR Request A.30 ICAO SAR Cancellation A.31 ICAO SAR Response A.32 ICAO Acknowledgment (ACK) Message A.33 ICAO Reject (REJ) Message A.34 Error Message A.35 ICAO Supplementary Flight Plan (SPL) Message A.36 Proposed ICAO Modification (CHG) Message A.37 Active ICAO Modification (MOD) Message A.38 ICAO Arrival (ARR) Message A.39 ICAO Cancellation (CNL) Message A.40 ICAO Departure (DEP) Message A.41 Proposed ICAO Flight Plan (FPL) Message A.42 ICAO Flight Plan (FPL) Message (Proposed-Inbound) A.43 ICAO Logical Acknowledgment (LAM) Message A.44 ICAO Logical Rejection (LRM) Message

Table of Contents (Continued)

03/26/2025

FOR OFFICIAL USE ONLY

vii

Figure 1–1. End-To-End Communications Figure 3–1. OASIS Interfaces Figure 3–2. Subsystem/Service Interconnectivity

List of Figures

03/26/2025

FOR OFFICIAL USE ONLY

viii

Table 1–1. OASIS Interfaces System Responsibility List Table 1–2. OASIS Communications Subsystem Responsibility List Table 3–1. OASIS to NDP: Core Message Set Table 3–2. OASIS to ATOP: Core Message Set Table 3–3. OASIS to ERAM: Core Message Set Table 3–4. OASIS to OFDPS: Core Message Set Table 3–5. OASIS to FDP2000: Core Message Set Table 3–6. OASIS to Foreign ATC: Core Message Set Table 3–7. OASIS to NAV/Canada: Core Message Set Table 3–8. OASIS to FFSP: Core Message Set Table 3–9. OASIS to NORAD: Core Message Set Table 3–10. OASIS to MBO: Core Message Set Table 3–11. OASIS to ATCSCC: Core Message Set Table 3–12. OASIS to USNS/FNS: Core Message Set Table 3–13. OASIS to WMSCR: Core Message Set Table 3–14. OASIS to WMSCR: Core Message Set Table 4–1. OASIS VRTM

List of Tables

03/26/2025

FOR OFFICIAL USE ONLY

1 SCOPE

This Interface Requirements Document (IRD) provides the requirements for the inter-face between the Operational and Supportability Implementation System (OASIS) and external users.

1.1 Summary

The OASIS is an operational Federal Aviation Administration (FAA) National Airspace System (NAS) system that transmits, receives, processes, and stores alphanumeric (A/N) weather products, graphic weather products, aeronautical data, and flight plan information. This data is used to support weather briefing, pre-flight planning, and in-flight aeronautical decision making as well as search and rescue operations.

The OASIS interfaces with other NAS systems using the FAA Telecommunications Infrastructure (FTI) Operational Internet Protocol (IP) network. Non-NAS systems will also be able to access the OASIS via the FTI Enterprise Security Gateway (ESG) as defined in the Draft FTI Operational IP User Guide.

The OASIS utilizes a hub and spoke network architecture centered at the Anchorage (ZAN) Air Route Traffic Control Center (ARTCC). This hub system, identified as the ANC OASIS Data Center, contains data access points at the ZAN ARTCC to provide a com-mon master database of aeronautical, flight planning, and weather information. The ANC OASIS Data Center equipment provides external communications through the OASIS router via the FTI to the 17 Alaskan Flight Service Stations (FSS) as depicted in Figure 1–1, End-To-End Communications.

Figure 1–1. End-To-End Communications

This IRD lists only those interfaces that are required. Some data for the OASIS is avail-able from multiple sources; where no specific source is required, no interface is listed.

1.2 Subsystem Responsibility

Table 1–1. OASIS Interfaces System Responsibility List

Subsystem/Equipment Common Name Responsible FAA Program Office

AKWeatherCams Alaska Weather Cameras ATO–R

ATCSCC Air Traffic Control Systems Com-mand Center

ATO–W

17 OASIS

FSS

Sites

SDP

ANC

OASIS

Data Center

SDP

FTI

OPIP

03/26/2025

ATOP Advanced Technologies and Oceanic Procedures

ATO–M

EPIC El Paso Intelligence Center ATO–R

ERAM En-Route Automation Modernization ATO–M

OFDPS Offshore Flight Data Processing Sys-tem

ATO–M

FDP2000 Flight Data Processing 2000 ATO–E

Foreign ATC Foreign Air Traffic Control N/A

FFSP Future Flight Service Program ATO–R

MBO Military Base Operation (s) ATO–R

NAV/Canada NAV/Canada

NMR NAS Messaging Replacement ATO–W

NORAD North American Aerospace Defense Command

OASIS Operational and Supportability Implementation System

ATO–R

USNS United States Notice To Air Missions (NOTAM) Service

ATO–M

WMSCR Weather Message Switching Center Replacement

ATO–W

Table 1–2. OASIS Communications Subsystem Responsibility List

Subsystem/Equipment Common Name Responsible FAA Program Office

ASTI Alaska Satellite Telecommunica-tion Infrastructure

ATO–W

FTI FAA Telecommunications Infra-structure

ATO–W

NMR NAS Messaging Replacement ATO–W

Table 1–1. OASIS Interfaces System Responsibility List (Continued)

Subsystem/Equipment Common Name Responsible FAA Program Office

03/26/2025

FOR OFFICIAL USE ONLY

2 APPLICABLE DOCUMENTS

2.1 Government Documents

The following documents, of the exact issue shown, form a part of this IRD to the extent specified. If there is a conflict between the following documents and the content of this IRD, the content of the IRD supersedes all prior documents.

2.1.1 FAA Specifications

2.1.2 FAA Standards

FAA–E–3008 System Specification for OASIS

FAA–G–2100H

May 9, 2005

Specification, Electronic Equipment, General Requirements

FTI

Version 2E March 2012

FAA Telecommunications Infrastructure (FTI) Enterprise Security Gateway Users Guide, Vol-ume II — For Non-NAS Users

NAS–IC–25070002–02

7/12/2010

Interface Control Document Weather Message Switching Center Replacement (WMSCR) to Transmission Control Protocol (TCP)/Internet Protocol (IP)-based User Subsystems

NAS–IC–43010002–01C

April 13, 2016

National Airspace Data Interchange Network (NADIN) Message Switch Network (MSN) to Transmission Control Protocol (TCP)/Internet Protocol (IP) User Subsystems, Interface Con-trol Document

NAS–RD–2012

September 28, 2012

National Airspace System System Requirement Specification

FAA Advisory Circular (AC) 00–62 November 1, 2002

Internet Communications of Aviation Weather and NOTAMs

FAA–C–1217g April 16, 2015

Electrical Work, Interior

FAA–STD–019e December 22, 2005

Lightning and Surge Protection, Grounding, Bonding and Shielding Requirements for Facili-ties and Electronic Equipment

FAA–STD–039c August 14, 2003

Open System Architecture and Protocols

03/26/2025

FOR OFFICIAL USE ONLY

2.1.3 FAA Orders

2.2 Non-Government Documents

Order JO 1370.114 January 4, 2012

Implementation of FAA Telecommunications Infra-structure Services and IS Requirements in the NAS

Order 1370.121B April 25, 2022

FAA Information Security and Privacy: Policy

Order JO 1370.98 April 15, 2007

ATO Information Technology (IT) Infrastructure Requirements for Non-FAA Connectivity

Order 1600.1F November 4, 2021

Personnel Security Program

Order 1600.72A 12/28/05

Contractor and Industrial Security Program

Order 7930.2T November 14, 2023

Notices to Air Missions (NOTAM)

International Civil Aviation Organization (ICAO) DOC 9896, Second Edition

Manual on the Aeronautical Telecommunica-tions Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocols

ICAO Annex 10, Volume II, Seventh Edition July 2016

Aeronautical Telecommunications, Volume II, Communication Procedures Including those with PANS Status

ICAO Annex 10, Volume III, Second Edition July 2007

Aeronautical Telecommunications, Volume III, Communication Systems

National Institute of Standards and Technology (NIST)

NIST SP 800–53A

Revision 4, December 18, 2014

Assessing Security and Privacy Controls in Fed-eral Information Systems and Organizations:

Building Effective Assessment Plans

International Telecommunication Union (ITU) T.50 November 1988

Series T: Terminal Equipment and Protocols for Telematic Services

03/26/2025

FOR OFFICIAL USE ONLY

3 INTERFACE REQUIREMENTS

This section provides the general functional requirements for the interfaces between the OASIS and the user subsystems.

3.1 General Requirements

This section provides a list of the types of messages received from and transmitted to the OASIS and required interfaces.

3.1.1 Security Requirements

3.1.1.1 Information System Security (ISS)

For ISS requirements, the OASIS follows Order 1370.121.

3.1.1.2 Internet Interface

The OASIS Internet interface follows Order 1370.121.

3.1.1.3 Web Service

The web service follows Order 1370.121 and FAA Advisory Circular AC 00–62.

3.1.1.4 Non-FAA Connections

a. All connections to non-FAA systems must have a Memorandum of Under-standing negotiated per Order JO 1370.98.

(OASIS–EXT–001)

b. The external interfaces will follow the moderate controls defined in NIST SP 800–53, specifically the moderate controls SC–1 thru SC–23, if applicable, or appropriate compensating controls.

c. The use of the compensating controls must be documented with sufficient justification.

(OASIS–EXT–002)

3.1.1.5 Personnel Security

For personnel security, the OASIS follows Order 1600.1 and Order 1600.72.

3.1.2 OASIS Required External Interfaces

a. NAS Enterprise Messaging System (NEMS) (paragraph 3.2.2.7.14)

b. NDP (paragraph 3.2.2.7.1)

c. ATCSCC (paragraph 3.2.2.7.11)

d. ATOP (paragraph 3.2.2.7.2)

e. EPIC (paragraph 3.2.2.7.14)

f. ERAM (paragraph 3.2.2.7.3)

g. FDP2000 (paragraph 3.2.2.7.5)

h. Foreign ATC (paragraph 3.2.2.7.6)

03/26/2025

FOR OFFICIAL USE ONLY

i. FFSP (paragraph 3.2.2.7.8)

j. MBO (paragraph 3.2.2.7.10)

k. NAV/Canada (paragraph 3.2.2.7.7)

l. NORAD (paragraph 3.2.2.7.9)

m. OFDPS (paragraph 3.2.2.7.4)

n. USNS/FNS — Candidate and Cancellation NOTAMs (paragraph 3.2.2.7.12)

o. WMSCR — Weather Observations, Pilot Reports (PIREP) (paragraph 3.2.2.7.13)

3.1.3 Data Types

a. Accepted Data from External Sources:

(1) Flight Data

(2) Aircraft Movement Messages

(3) General Messages

(4) Search and Rescue (SAR) Messages

(5) Control Messages

(6) Law Enforcement (LE) data

(7) Two-Way text messages from accepted electronic devices

(8) eSRS messages from accepted electronic devices

b. Transmitted Data to External Sources:

(1) Flight Data

(2) Aircraft Movement Messages

(3) General Messages

(4) SAR Messages

(5) Weather Data

(6) Weather Observation data

(7) PIREP data

(8) NOTAM data

(9) Candidate NOTAM data and NOTAM Cancellations

03/26/2025

FOR OFFICIAL USE ONLY

The specific interfaces are discussed in Figure 3–1, OASIS Interfaces.

3.2 Functional Requirements

This section describes the functional requirements of the OASIS interfaces. It identifies the types of interfaces based on the data listed in section 3.2.2.7, the Application Pro-cesses (AP) for those interfaces and the information transferred between the OASIS and the user subsystems.

The following interfaces are described in this IRD and are supported by OASIS:

a. NMR Subsystem

b. FAA Weather Camera

3.2.1 General Services Requirements

This section lists the required subsystem interfaces that are connected to OASIS via FTI and their message flow. For clarity, all AP message requirements are listed in Appendix A, Message Formats.

3.2.2 APs and Message Requirements

3.2.2.1 Identification of Each AP

See Appendix A, Message Formats for identification of each AP.

3.2.2.2 AP Capability Requirements

The OASIS services are considered essential, as defined in NAS–RD–2012. Availability of this service is equal to or greater than 99.9 percent. The AP exchanges Aeronautical Fixed Telecommunication Network (AFTN)-formatted messages. This IRD imposes no requirements on the processing of the actual AFTN-formatted data.

Figure 3–1. OASIS Interfaces

FTI

OPIP

NMR

WMSCR

ANC OASIS

Data Center USNS/FNS

NEMS

ATCSCC

ATOP

ERAM

FDP2000

Foreign ATC

FFSP

MBO

NAV/Canada

NORAD

OFDPS

Alaska Weather Cams

HWDS

HUMA

AMOC

NDP

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.3 Message Content Requirements

a. Transmission to NMR.

(1) For transmission to an NMR subsystem interface, the OASIS must for-mat an information unit into an NMR message as specified in NAS–IC– 43010002–01. The Additional Data Field (ADF) will not be used.

(OASIS–EXT–003)

(2) The information unit must be transmitted in the text field of an NMR message.

(OASIS–EXT–004)

b. Messages Received from NMR.

(1) A message received from an NMR subsystem interface to the OASIS will be formatted as specified in NAS–IR–4301002, except that ADF will not be present.

(2) An information unit must be extracted from the text field of the NMR message.

(OASIS–EXT–005)

c. Message Text. The text portion of the information units transmitted between the OASIS and the NMR subsystem interfaces may be up to and including 3600 characters in length.

3.2.2.4 Relationship Among Messages

This IRD imposes no explicit relationship among messages. ICAO Doc 9896 defines the relationship between the AFTN messages.

3.2.2.5 Quality of Service (QoS) Requirements

a. This IRD defines the following QoS requirements:

(1) Availability: The availability of the interfaces is a function of the FTI Service Delivery Points (SDP).

(2) Data Integrity: Data integrity is provided by the underlying TCP/IP protocols.

(3) Latency: The latency for message transfer is a function of the FTI ser-vices associated with the FTI SDP’s for the OASIS servers and the user subsystems.

(4) Throughput: Throughput is a function of the FTI services level and the access bandwidth of the OASIS servers and the user subsystem equip-ment.

b. This IRD imposes no explicit requirements on the following QoS parame-ters:

(1) Message Size: The OASIS imposes no requirements on the throughput for incoming messages.

(2) Priority

(3) Urgency

03/26/2025

FOR OFFICIAL USE ONLY

(4) Importance

(5) Expected Bit Error Rate

3.2.2.6 Error Handling Requirements

All error handling for this interface is performed by the underlying TCP/IP protocols.

3.2.2.7 Interface Summary Tables

3.2.2.7.1 NDP Interface Summary Table

When transmitting a flight plan or other flight movement related messages to an external user, the OASIS must transmit a copy of that message to the NDP. A sum-mary of the messages to be transmitted across the NDP interface is shown in Table 3– 1, OASIS to NDP: Core Message Set.

(OASIS–EXT–006)

Table 3–1. OASIS to NDP: Core Message Set

Reference DIRECTION

OASIS NDP

MESSAGE NAME

A.3 Acknowledgment (Roger)

A.17 IFR Flight Plan

A.27 Stereo Flight Plan

A.1 General Message

A.13 Change of ETA

A.15 Flight Plan Cancellation

A.15 Flight Plan Closure

A.4 QALQ Request

A.7 INREQ Request

A.10 ALNOT Request

A.6 QALQ Response

A.9 INREQ Response

A.12 ALNOT Response

A.5 QALQ Cancellation

A.8 INREQ Cancellation

A.11 ALNOT Cancellation

A.29 INCERFA Request

A.29 ALERFA Request

03/26/2025

FOR OFFICIAL USE ONLY

A.29 DESTRESFA Request

A.31 INCERFA Response

A.31 ALERFA Response

A.31 DESTRESFA Response

A.30 INCERFA Cancellation

A.30 ALERFA Cancellation

A.30 DESTRESFA Cancellation

A.14 Civil Domestic Flight Notification

A.22 Mexican Flight Notification

A.18 Military Flight Notification

A.20 Military Departure

A.16 Proposed VFR Flight Plan

A.17 Proposed IFR Flight Plan

A.25 Law Enforcement Contact

A.37 ICAO Supplementary Flight Plan (SPL) Message

A.38 Proposed ICAO Modification (CHG) Message

A.39 Active ICAO Modification (MOD) Message

A.40 ICAO Arrival (ARR) Message

A.41 ICAO Cancellation (CNL) Message

A.42 ICAO Departure (DEP) Message

A.43 Proposed ICAO Flight Plan (FPL) Message

A.44 ICAO Flight Plan (FPL) Message (Proposed-Inbound)

A.34 ICAO Acknowledgment (ACK) Message

A.42 ICAO Logical Acknowledgment (LAM) Message

A.43 ICAO Logical Rejection (LRM) Message

Table 3–1. OASIS to NDP: Core Message Set (Continued)

Reference DIRECTION

OASIS NDP

MESSAGE NAME

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.7.2 ATOP Interface Summary Table

The OASIS must transmit and receive flight movement and control messages to and from ATOP as specified in FAA–E–3008 and acknowledge the receipt of the messages, if required. A summary of the messages to be transmitted across the ATOP interface is shown in Table 3–2, OASIS to ATOP: Core Message Set.

(OASIS–EXT–007)

Table 3–2. OASIS to ATOP: Core Message Set

Reference DIRECTION

OASIS ATOP

MESSAGE NAME

A.1 General Message

A.17 IFR Flight Plan

A.27 STEREO Flight Plan

A.3 Acknowledgment (Roger)

A.34 Error

A.33 ICAO Reject

A.28 Cancellation Message

A.4 QALQ Request

A.7 INREQ Request

A.10 ALNOT Request

A.29 INCERFA Request

A.29 ALERFA Request

A.29 DESTRESFA Request

A.6 QALQ Response

A.9 INREQ Response

A.12 ALNOT Response

A.31 INCERFA Response

A.31 ALERFA Response

A.31 DESTRESFA Response

A.5 QALQ Cancellation

A.8 INREQ Cancellation

A.11 ALNOT Cancellation

A.30 INCERFA Cancellation

A.30 ALERFA Cancellation

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.7.3 ERAM Interface Summary Table

The OASIS must transmit and receive flight movement and control messages to and from ERAM as specified in FAA–E–3008 and acknowledge the receipt of the messages, if required. A summary of the messages to be transmitted across the ERAM interface is shown in Table 3–3, OASIS to ERAM: Core Message Set.

(OASIS–EXT–009)

A.30 DESTRESFA Cancellation

A.21.1 IFR Training Route (IR)

A.21.3 VFR Training Route (VR)

A.21.5 Military Operations Area (MOA)

A.21.2 IR Cancellation

A.21.4 VR Cancellation

A.21.6 MOA Cancellation

A.36 Proposed ICAO Modification (CHG) Message

A.39 ICAO Cancellation (CNL) Message

A.42 ICAO Flight Plan (FPL) Message (Proposed-Inbound)

Table 3–3. OASIS to ERAM: Core Message Set

Reference DIRECTION

OASIS ERAM

MESSAGE NAME

A.1 General Message

A.17 IFR Flight Plan

A.27 Stereo Flight Plan

A.3 Acknowledgment (Roger)

A.32 ICAO Acknowledgment (ACK) Message

A.34 Error

A.33 ICAO Reject

A.28 Cancellation Message

A.4 QALQ Request

A.7 INREQ Request

A.10 ALNOT Request

Table 3–2. OASIS to ATOP: Core Message Set (Continued)

Reference DIRECTION

OASIS ATOP

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.7.4 OFDPS Interface Summary Table

The OASIS must transmit and receive flight movement and control messages to and from OFDPS as specified in FAA–E–3008 and acknowledge the receipt of the messages, if required. A summary of the messages to be transmitted across the OFDPS interface is shown in Table 3–4, OASIS to OFDPS: Core Message Set.

(OASIS–EXT–036)

A.29 INCERFA Request

A.29 ALERFA Request

A.29 DESTRESFA Request

A.6 QALQ Response

A.9 INREQ Response

A.12 ALNOT Response

A.31 INCERFA Response

A.31 ALERFA Response

A.31 DESTRESFA Response

A.5 QALQ Cancellation

A.8 INREQ Cancellation

A.11 ALNOT Cancellation

A.30 INCERFA Cancellation

A.30 ALERFA Cancellation

A.30 DESTRESFA Cancellation

A.21.1 IFR Training Route (IR)

A.21.3 VFR Training Route (VR)

A.21.5 Military Operations Area (MOA)

A.21.2 IR Cancellation

A.21.4 VR Cancellation

A.21.6 MOA Cancellation

A.36 Proposed ICAO Modification (CHG) Message

A.39 ICAO Cancellation (CNL) Message

A.42 ICAO Flight Plan (FPL) Message (Proposed-Inbound)

Table 3–3. OASIS to ERAM: Core Message Set (Continued)

Reference DIRECTION

OASIS ERAM

03/26/2025

FOR OFFICIAL USE ONLY

Table 3–4. OASIS to OFDPS: Core Message Set

Reference DIRECTION

OASIS OFDPS

MESSAGE NAME

A.1 General Message

A.17 IFR Flight Plan

A.27 Stereo Flight Plan

A.3 Acknowledgment (Roger)

A.32 ICAO Acknowledgment (ACK) Message

A.34 Error

A.33 ICAO Reject

A.28 Cancellation Message

A.4 QALQ Request

A.7 INREQ Request

A.10 ALNOT Request

A.29 INCERFA Request

A.29 ALERFA Request

A.29 DESTRESFA Request

A.6 QALQ Response

A.9 INREQ Response

A.12 ALNOT Response

A.31 INCERFA Response

A.31 ALERFA Response

A.31 DESTRESFA Response

A.5 QALQ Cancellation

A.8 INREQ Cancellation

A.11 ALNOT Cancellation

A.30 INCERFA Cancellation

A.30 ALERFA Cancellation

A.30 DESTRESFA Cancellation

A.21.1 IFR Training Route (IR)

A.21.3 VFR Training Route (VR)

A.21.5 Military Operations Area (MOA)

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.7.5 FDP2000 Interface Summary Table

The OASIS must transmit and receive flight movement and control messages to and from FDP2000 as specified in FAA–E–3008 and acknowledge the receipt of the mes-sages, if required. A summary of the messages to be transmitted across the FDP2000 interface is shown in Table 3–5, OASIS to FDP2000: Core Message Set.

(OASIS–EXT–010)

A.21.2 IR Cancellation

A.21.4 VR Cancellation

A.21.6 MOA Cancellation

A.36 Proposed ICAO Modification (CHG) Message

A.39 ICAO Cancellation (CNL) Message

A.42 ICAO Flight Plan (FPL) Message (Proposed-Inbound)

Table 3–5. OASIS to FDP2000: Core Message Set

Reference DIRECTION

OASIS FDP2000

MESSAGE NAME

A.1 General Message

A.17 IFR Flight Plan

A.27 Stereo Flight Plan

A.3 Acknowledgment (Roger)

A.32 ICAO Acknowledgment (ACK) Message

A.34 Error

A.33 ICAO Reject

A.28 Cancellation Message

A.4 QALQ Request

A.7 INREQ Request

A.10 ALNOT Request

A.29 INCERFA Request

A.29 ALERFA Request

A.29 DESTRESFA Request

A.6 QALQ Response

Table 3–4. OASIS to OFDPS: Core Message Set (Continued)

Reference DIRECTION

OASIS OFDPS

03/26/2025

FOR OFFICIAL USE ONLY

A.9 INREQ Response

A.12 ALNOT Response

A.31 INCERFA Response

A.31 ALERFA Response

A.31 DESTRESFA Response

A.5 QALQ Cancellation

A.8 INREQ Cancellation

A.11 ALNOT Cancellation

A.30 INCERFA Cancellation

A.30 ALERFA Cancellation

A.30 DESTRESFA Cancellation

A.21.1 IFR Training Route (IR)

A.21.3 VFR Training Route (VR)

A.21.5 Military Operations Area (MOA)

A.21.2 IR Cancellation

A.21.4 VR Cancellation

A.21.6 MOA Cancellation

A.36 Proposed ICAO Modification (CHG) Message

A.39 ICAO Cancellation (CNL) Message

A.42 ICAO Flight Plan (FPL) Message (Proposed-Inbound)

Table 3–5. OASIS to FDP2000: Core Message Set (Continued)

Reference DIRECTION

OASIS FDP2000

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.7.6 Foreign ATC Interface Summary Table

The OASIS must transmit and receive flight movement messages to and from Foreign ATC systems (except NAV/Canada) as specified in FAA–E–3008 and acknowledge the receipt of the messages, if required. A summary of the messages to be transmitted across the Foreign ATC interface is shown in Table 3–6, OASIS to Foreign ATC: Core Message Set.

(OASIS–EXT–011)

3.2.2.7.7 NAV/Canada Interface Summary Table

The OASIS must transmit and receive flight movement messages to and from the NAV/ Canada system as specified in FAA–E–3008 and acknowledge the receipt of the mes-sages, if required. A summary of the messages to be transmitted across the NAV/Can-ada interface is shown in Table 3–7, OASIS to NAV/Canada: Core Message Set.

(OASIS–EXT–013)

Table 3–6. OASIS to Foreign ATC: Core Message Set

Reference DIRECTION OASIS Foreign

ATC

MESSAGE NAME

A.1 General Message

A.17 IFR Flight Plan

A.42 ICAO Flight Plan (FPL) Message (Proposed-Inbound)

A.40 ICAO Departure (DEP) Message

A.14 Civil Domestic Flight Notification

A.3 Acknowledgment (Roger)

A.32 ICAO Acknowledgment (ACK) Message

A.29 INCERFA Request

A.29 ALERFA Request

A.29 DESTRESFA Request

A.31 INCERFA Response

A.31 ALERFA Response

A.31 DESTRESFA Response

A.30 INCERFA Cancellation

A.30 ALERFA Cancellation

A.30 DESTRESFA Cancellation

03/26/2025

FOR OFFICIAL USE ONLY

Table 3–7. OASIS to NAV/Canada: Core Message Set

Reference DIRECTION

OASIS NAV/

Canada

MESSAGE NAME

A.1 General Message

A.17 IFR Flight Plan

A.14 Civil Domestic Flight Notification

A.15 Flight Plan Cancellation

A.15 Flight Plan Closure

A.13 Change ETA

A.3 Acknowledgment (Roger)

A.29 INCERFA Request

A.29 ALERFA Request

A.29 DESTRESFA Request

A.31 INCERFA Response

A.31 ALERFA Response

A.31 DESTRESFA Response

A.30 INCERFA Cancellation

A.30 ALERFA Cancellation

A.30 DESTRESFA Cancellation

A.35 ICAO Supplementary Flight Plan (SPL) Message

A.36 Proposed ICAO Modification (CHG) Message

A.37 Active ICAO Modification (MOD) Message

A.38 ICAO Arrival (ARR) Message

A.39 ICAO Cancellation (CNL) Message

A.40 ICAO Departure (DEP) Message

A.41 Proposed ICAO Flight Plan (FPL) Message

A.42 ICAO Flight Plan (FPL) Message (Proposed-Inbound)

A.32 ICAO Acknowledgment (ACK) Message

A.33 ICAO Reject (REJ) Message

A.43 ICAO Logical Acknowledgment (LAM) Message

A.44 ICAO Logical Rejection (LRM) Message

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.7.8 FFSP Interface Summary Table

The OASIS must transmit and receive flight movement messages to and from FFSP as specified in FAA–E–3008 and acknowledge the receipt of the messages, if required. A summary of the messages to be transmitted across the FFSP interface is shown in Table 3–8, OASIS to FFSP: Core Message Set.

(OASIS–EXT–014)

Table 3–8. OASIS to FFSP: Core Message Set

Reference DIRECTION

OASIS FS21

MESSAGE NAME

A.1 General Message

A.14 Civil Domestic Flight Notification

A.18 Military Flight Notification

A.20 Military Departure message

A.16 Proposed VFR Flight Plan

A.17 Proposed IFR Flight Plan

A.15 Flight Plan Cancellation

A.15 Flight Plan Closure

A.13 Change ETA

A.3 Acknowledgment (Roger)

A.4 QALQ Request

A.7 INREQ Request

A.10 ALNOT Request

A.6 QALQ Response

A.9 INREQ Response

A.12 ALNOT Response

A.5 QALQ Cancellation

A.8 INREQ Cancellation

A.11 ALNOT Cancellation

A.29 INCERFA Request

A.29 ALERFA Request

A.29 DESTRESFA Request

A.31 INCERFA Response

A.31 ALERFA Response

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.7.9 NORAD Interface Summary Table

The OASIS must transmit Defense Visual Flight Rules (DVFR) Flight Plan messages to NORAD as specified in FAA–E–3008 and acknowledge the receipt of the messages, if required. A summary of the messages to be transmitted across the NORAD interface is shown in Table 3–9, OASIS to NORAD: Core Message Set.

(OASIS–EXT–015)

A.31 DESTRESFA Response

A.30 INCERFA Cancellation

A.30 ALERFA Cancellation

A.30 DESTRESFA Cancellation

A.35 ICAO Supplementary Flight Plan (SPL) Message

A.36 Proposed ICAO Modification (CHG) Message

A.37 Active ICAO Modification (MOD) Message

A.38 ICAO Arrival (ARR) Message

A.39 ICAO Cancellation (CNL) Message

A.40 ICAO Departure (DEP) Message

A.41 Proposed ICAO Flight Plan (FPL) Message

A.42 ICAO Flight Plan (FPL) Message (Proposed-Inbound)

A.43 ICAO Logical Acknowledgment (LAM) Message

A.44 ICAO Logical Rejection (LRM) Message

Table 3–9. OASIS to NORAD: Core Message Set

Reference DIRECTION

OASIS NORAD

MESSAGE NAME

A.1 General Message

A.14 Civil Domestic Flight Notification

A.37 Active ICAO Modification (MOD) Message

A.39 ICAO Cancellation (CNL) Message

A.40 ICAO Departure (DEP) Message

Table 3–8. OASIS to FFSP: Core Message Set (Continued)

Reference DIRECTION

OASIS FS21

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.7.10 MBO Interface Summary Table

The OASIS must transmit and receive flight movement and control messages to and from MBOs as specified in FAA–E–3008 and acknowledge the receipt of the messages, if required. A summary of the messages to be transmitted across the MBO interface is shown in Table 3–10, OASIS to MBO: Core Message Set.

(OASIS–EXT–016)

Table 3–10. OASIS to MBO: Core Message Set

Reference DIRECTION

OASIS MBO

MESSAGE NAME

A.3 Acknowledge (Roger)

A.1 General Message

A.13 Change of ETA

A.15 Flight Plan Cancellation

A.15 Flight Plan Closure

A.4 QALQ Request

A.7 INREQ Request

A.10 ALNOT Request

A.6 QALQ Response

A.9 INREQ Response

A.12 ALNOT Response

A.5 QALQ Cancellation

A.8 INREQ Cancellation

A.11 ALNOT Cancellation

A.29 INCERFA Request

A.29 ALERFA Request

A.29 DESTRESFA Request

A.31 INCERFA Response

A.31 ALERFA Response

A.31 DESTRESFA Response

A.30 INCERFA Cancellation

A.30 ALERFA Cancellation

A.30 DESTRESFA Cancellation

A.14 Civil Domestic Flight Notification

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.7.11 ATCSCC Interface Summary Table

The OASIS must receive ATCSCC data as shown in Table 3–11, OASIS to ATCSCC:

Core Message Set.

(OASIS–EXT–017)

A.18 Military Flight Notification

A.19 Military Stopover Notification

A.20 Military Departure

A.42 ICAO Flight Plan (FPL) Message (Proposed-Inbound)

A.40 ICAO Departure (DEP) Message

A.16 Proposed VFR Flight Plan

A.17 Proposed IFR Flight Plan

A.21.1 Military Operations-IR

A.21.3 Military Operation-VR

A.21.5 Military Operations-MOA

A.21.2 IR Cancellation

A.21.4 VR Cancellation

A.21.6 MOA Cancellation

Table 3–11. OASIS to ATCSCC: Core Message Set

Reference DIRECTION

OASIS ATCSCC

MESSAGE NAME

A.26 ATCSCC MESSAGE

Table 3–10. OASIS to MBO: Core Message Set (Continued)

Reference DIRECTION

OASIS MBO

03/26/2025

FOR OFFICIAL USE ONLY

3.2.2.7.12 USNS/FNS Interface Summary Table

The OASIS must transmit candidate NOTAMs and NOTAM Cancellations to the USNS.

The USNS system is scheduled to be replaced with the Federal NOTAM System (FNS).

A summary of the messages to be transmitted across the USNS interface is shown in Table 3–12, OASIS to USNS/FNS: Core Message Set.

(OASIS–EXT–018)

3.2.2.7.13 WMSCR Interface Summary Table

WMSCR is an FAA NAS subsystem that receives, processes, and stores alphanumeric aviation weather products and disseminates these products to NAS and non-NAS users. NAS–IC–25070002–02 documents the interface between WMSCR and user sys-tems that are required to send data via TCP/IP sockets.

The OASIS must transmit Weather Observation messages to WMSCR. A summary of the messages to be transmitted across the WMSCR interface is shown in Table 3–13, OASIS to WMSCR: Core Message Set.

(OASIS–EXT–020)

3.2.2.7.14 NAS Enterprise Messaging System (NEMS)

OASIS receives weather products including Alaska Weather Camera data via NEMS on the Harris Weather Data Systems (HWDS) data channel. Using the Harris Universal Message Acquisition (HUMA) data channel, OASIS receives eSRS messages from approved GPS devices. In addition, OASIS receives and transmits text messages from SMS and approved satellite communication devices via the HUMA data channel.

3.2.2.7.15 EPIC Interface Summary Table

The OASIS must receive LE addition, deletion, and summary data from EPIC. A sum-mary of the messages to be transmitted across the EPIC interface is shown in Table 3– 14, OASIS to WMSCR: Core Message Set.

(OASIS-EXT-019)

Table 3–12. OASIS to USNS/FNS: Core Message Set

Reference DIRECTION

OASIS USNS

MESSAGE NAME

Unprocessed NOTAM

NOTAM Cancellation

USNS Response Message

Table 3–13. OASIS to WMSCR: Core Message Set

Reference DIRECTION

OASIS WMSCR

MESSAGE NAME

PIREP

METAR, or SPECI

03/26/2025

FOR OFFICIAL USE ONLY

3.2.3 Protocol Implementation

The protocol implementation must be in accordance with the IP Suite, as depicted in Figure 3–2, Subsystem/Service Interconnectivity.

(OASIS–EXT–021)

3.2.3.1 Application Layer Services

This IRD requires that the application layer services must be in accordance with NAS– IC–43010002–01 for interoperability with NMR enhanced services.

(OASIS–EXT–022)

3.2.3.2 Transport Layer Services

This IRD requires that Transport Layer Service must be TCP, in accordance with the latest edition of FAA–STD–039.

(OASIS–EXT–023)

Table 3–14. OASIS to WMSCR: Core Message Set

Reference DIRECTION

OASIS EPIC

MESSAGE NAME

A.1 General Message

A.25.2.1 LE Stolen Addition

A.25.2.2 LE Stolen Deletion

A.25.2.3 LE Stolen Summary

Figure 3–2. Subsystem/Service Interconnectivity

AFTN Messages (Basic Mode)

AFTN Messages via CMHP (Enhanced Mode)

Transport Layer

TCP

Transport Layer

Internetwork Layer

IP IP

Communications Service Internetwork

Layer

Network Interface

Link Layer Link Layer

Ethernet Ethernet Physical Layer

Network Interface

03/26/2025

FOR OFFICIAL USE ONLY

3.2.3.3 Naming and Addressing

The OASIS servers and user subsystems must be in accordance with FAA–STD–039.

(OASIS–EXT–024)

3.3 Physical Requirements

3.3.1 Electrical Power and Electronic Requirements

3.3.1.1 Connectors

The OASIS must be connected to facility critical power.

(OASIS–EXT–025)

3.3.1.2 Wire/Cable

Reference FAA–C–1217 and FAA–STD–019.

3.3.1.3 Grounding

Within the electrical interfaces, grounding complies with FAA–G–2100, section 3.1.1.9 and FAA–STD–019.

3.3.1.4 Fasteners

Reference FAA–G–2100.

3.3.1.5 Electromagnetic Compatibility

This IRD imposes no explicit electromagnetic compatibility requirements.

03/26/2025

FOR OFFICIAL USE ONLY

4 QUALITY ASSURANCE PROVISIONS

The Test and Evaluation process guidelines within the Verification and Validation sec-tion of the System Engineering Manual section 4 is used, and tailored as necessary for the levels and methods of verification identified in the Verification Requirements Trace-ability Matrix (VRTM).

4.1 Responsibility for Verification

The FAA is responsible for the development and implementation of the verification of requirements for each project. The FAA may delegate verification activities to other organizations, independent contractors, and/or the prime project contractor.

4.2 Special Verification Requirements

This IRD imposes no explicit special verification requirements.

4.3 Verification Levels and Methods

The levels and methods of verification appropriate for use in the VRTM are defined in the following paragraphs.

4.3.1 Verification Levels

The three levels of verification are Subsystem, Integration, and Site. All requirements imposed by this IRD are verified at one or more of these three levels:

a. Subsystem-Level. This level of verification is usually accomplished at the contractor’s facility and culminates in the formal acceptance of the contrac-tual end items.

b. Integration-Level. This level of verification is conducted at the FAA Tech-nical Center or at a key site. The verification conducted will determine if the hardware, software, or subsystem to be deployed for site installation will perform in a National Airspace System (NAS) environment and in accor-dance with the NAS system-level operational and functional requirements.

c. Site-Level. This level of verification is usually performed at the designated site. The verification portion of the subsystem installation and checkouts will emphasize the demonstration to the overall system performance require-ments. It includes the demonstration of an end item, subsystem and/or sys-tem, the final acceptance demonstrations, and commissioning activities.

4.3.2 Verification Methods

The following verification methods are to be used at any of the three verification lev-els:

a. Inspection. Inspection is a method of verification to determine compliance without the use of special laboratory equipment, procedures, or services, and consists of non-destructive, static-state examination of the hardware, software, and/or technical data and documentation.

b. Test. Test is a method of verification wherein performance is measured during or after the controlled application of functional and/or environmental

03/26/2025

FOR OFFICIAL USE ONLY

stimuli. Quantitative measurements are analyzed to determine the degree of compliance. The process uses standardized laboratory equipment, proce-dures, and/or services.

c. Demonstration. Demonstration is a method of verification where qualita-tive determination of properties is made for a configuration item, including software and/or the use of technical data and documentation. The items being verified are observed, but not quantitatively measured, in a dynamic state.

d. Analysis. Analysis is a method of verification where hardware and software designs are compared with known scientific and technical principles, proce-dures, and practices to estimate the capability of the proposed design to meet the mission and system requirements.

4.4 VRTM

Each requirement imposed in this IRD is verified in accordance with Table 4–1, OASIS

VRTM.

Table 4–1. OASIS VRTM

A = Analysis D = Demonstration I = Inspection T = Test X = Not Applicable

Verification Level and Method

Requirement Subsection Subsystem Level

Integration Level

Site Level

Remarks

(OASIS–EXT–001) 3.1.1.4a D D D

(OASIS–EXT–002) 3.1.1.4c D D D

(OASIS–EXT–003) 3.2.2.3a(1) D D D

(OASIS–EXT–004) 3.2.2.3b(2) D D D

(OASIS–EXT–005) 3.2.2.3c(2) D D D

(OASIS–EXT–006) 3.2.2.7.1 D D D

(OASIS–EXT–007) 3.2.2.7.2 D D D

(OASIS–EXT–009) 3.2.2.7.3 D D D

(OASIS–EXT–010) 3.2.2.7.4 D D D

(OASIS–EXT–011) 3.2.2.7.5 D D D

(OASIS–EXT–013) 3.2.2.7.7 D D D

(OASIS–EXT–014) 3.2.2.7.8 D D D

(OASIS–EXT–015) 3.2.2.7.9 D D D

(OASIS–EXT–016) 3.2.2.7.10 D D D

(OASIS–EXT–017) 3.2.2.7.11 D D D

03/26/2025

FOR OFFICIAL USE ONLY

(OASIS–EXT–018) 3.2.2.7.12 D D D

(OASIS–EXT–020) 3.2.2.7.13 D D D

(OASIS–EXT–021) 3.2.3 I, T I, T D

(OASIS–EXT–022) 3.2.3.1 T T D

(OASIS–EXT–023) 3.2.3.2 I, T I, T I, D

(OASIS–EXT–024) 3.2.3.3 I, T I, T I, D

(OASIS–EXT–025) 3.3.1.1 I I I

(OASIS–EXT–026) A.1i(5) D D D

(OASIS–EXT–027) A.21.1e D D D

(OASIS–EXT–028) A.21.2e D D D

(OASIS–EXT–029) A.21.2f D D D

(OASIS–EXT–030) A.21.3e D D D

(OASIS–EXT–031) A.21.4e D D D

(OASIS–EXT–032) A.21.4f D D D

(OASIS–EXT–033) A.21.5e D D D

(OASIS–EXT–034) A.21.6e D D D

(OASIS–EXT–035) A.21.6f D D D

(OASIS–EXT–036) 3.2.2.7.4 D D D

(OASIS–EXT–037) A.36i D D D

(OASIS–EXT–038) A.36i D D D

Table 4–1. OASIS VRTM (Continued)

A = Analysis D = Demonstration I = Inspection T = Test X = Not Applicable

Verification Level and Method

Requirement Subsection Subsystem Level

Integration Level

Site Level

Remarks

03/26/2025

FOR OFFICIAL USE ONLY

5 PREPARATION FOR DELIVERY

This IRD imposes no explicit preparations for delivery.

03/26/2025

FOR OFFICIAL USE ONLY

6 NOTES

6.1 Definitions

None.

6.2 Abbreviations and Acronyms

Acronym Definition

A/N Alphanumeric

AC Advisory Circular

ACID Aircraft ID

ADF Additional Data Field

AFSIAG Alaska Flight Services Information Area Group

AFSS Automated Flight Service Station

AFTN Aeronautical Fixed Telecommunication Network

ALERFA Alert Phase

ALNOT Alert Notice

AP Application Processes

ARTCC Air Route Traffic Control Center

ASCII American Standard Code for Information Interchange

ASTI Alaskan Satellite Telecommunication Infrastructure

ATC Air Traffic Control

ATCSCC Air Traffic Control System Command Center

ATN Aeronautical Telecommunications Network

ATO Air Traffic Organization

ATOP Advanced Technologies and Oceanic Procedures

AWP Aviation Weather Processor

CMHP Common Message Handling Protocol

CR Carriage Return

DESTRESFA Distress Phase

DVFR Defense Visual Flight Rules

EOL End of Line

EPIC El Paso Intelligence Center

ERAM En Route Automation Modernization

03/26/2025

FOR OFFICIAL USE ONLY

ESG Enterprise Security Gateway eSRS Enhanced Special Reporting Service

ETA Estimated Time of Arrival

ETC End of Text

FAA Federal Aviation Administration

FDP2000 Flight Data Processing 2000

FFSP Future Flight Service Program

FNS Federal NOTAM System

FS File Separator

FS21 Flight Service for the 21st Century

FSDPS Flight Service Data Processing System

FSS Flight Service Station

FTI FAA Telecommunications Infrastructure

FTP File Transfer Protocol

HTTP Hypertext Transfer Protocol

HUMA Harris Universal Message Acquisition

HWDS Harris Weather Data Systems

IA International Alphabet

IAW In Accordance With

ICAO International Civil Aviation Organization

ICD Interface Control Document

IFR Instrument Flight Rules

INCERFA Uncertainty Phase

INREQ Information Request

IP Internet Protocol

IR IFR Training Route

IRA International Reference Alphabet

IRD Interface Requirements Document

ISS Information System Security

IT Information Technology

ITU International Telecommunication Union

Acronym Definition

03/26/2025

FOR OFFICIAL USE ONLY

LCM LE Contact Message

LE Law Enforcement

LF Line Feed

LOCID Location Identifier

MBO Military Base Operations

METAR Meteorological Aviation Routine Weather Report

MOA Military Operations Area

MSN Message Switched Network

NADIN National Airspace Data Interchange Network

NAS National Airspace System

NEMS NAS Enterprise Messaging System

NDP National Defense Program

NIST National Institute of Standards and Technology

NMR NAS Messaging Replacement

NORAD North American Aerospace Defense Command

NOTAM Notice to Air Missions

OASIS Operational and Supportability Implementation System

OCS Oceanic Computer System

OFDPS Offshore Flight Data Processing System

PIREP Pilot Report

QALQ Information Request to Departure Station

QoS Quality of Service

RT Report Type

SAR Search and Rescue

SDP Service Delivery Point

SOH Start of Header

SPECI Special METAR

STX Start of Text

TCP Transmission Control Protocol

USNS United States NOTAM System

VFR Visual Flight Rules

03/26/2025

FOR OFFICIAL USE ONLY

VR VFR Training Route

VRTM Verification Requirements Traceability Matrix

VT Vertical Tab

WCPO Weather Camera Program Office

WMSCR Weather Message Switching Center Replacement

XHTML Extensible Hypertext Markup Language

XML Extensible Markup Language

ZAN Anchorage ARTCC

03/26/2025

FOR OFFICIAL USE ONLY

APPENDIX A. MESSAGE FORMATS

For transmission to the External Users, OASIS will format an information unit into a message as specified in this appendix. An information unit will be transmitted in the text field of a message. A message received from the External Users by OASIS will be formatted as specified in this appendix. An information unit will be extracted from the text field of the message. Messages transmitted to, or received from, External Users will not exceed 3700 characters in length.

Information exchanged between OASIS and External Users will be encoded in Interna-tional Alphabet (IA5) characters, as defined in ICAO Annex 10, Volume III, paragraph 8.6.1.

A.1 NMR Message Format

The following is the NMR message format:

a. Start of Header.

(1) Start of Header (SOH) character.

(2) Always present.

b. Priority.

(1) Two alpha characters denoting message priority.

(2) Space character.

(3) Always present.

c. Address.

(1) Eight-character ICAO address of destination station.

(2) Additional eight-character alpha addresses may be added with each address preceded by a space character, up to 8 addresses and 80 characters per line.

(3) Maximum of three lines of addresses.

(4) Always present.

d. Alignment.

(1) Each line will be followed by the alignment of Carriage Return (CR);

Line Feed (LF).

START OF HEADER PRIORITY ADDRESS ALIGNMENT END OF ADDRESS INDICATOR

DATE TIME

GROUP

ORIGIN PRIORITY ALARM ADDITIONAL DATA

FIELD

ALIGNMENT

START

OF

TEXT

TEXT

END

OF

TEXT

03/26/2025

FOR OFFICIAL USE ONLY

(2) Always present.

(3) The alignment is inserted between an address and its preceding space.

Note that the final alignment follows immediately after the final address.

e. End of Address Indicator.

(1) File Separator (FS) character.

(2) Following CR, LF of last line of addresses.

(3) Optional.

f. Date Time Group.

(1) Six numerics indicating time of message origination.

(2) Space character.

(3) Always present.

g. Origin.

(1) Eight-character ICAO address of message originator.

(2) Always present.

h. Priority Alarm.

(1) Conditional. Present only for SS priority message.

(2) Five Bell characters.

i. Additional Data Field.

(1) ADF is transparent to NMR.

(2) ADF will conform to ICAO Annex 10 Volume II, paragraph 4.4.15.2.2.6.

(3) When used, first character is a “space” and there will be a limit of 52 characters.

(4) Transmission control characters are not permitted.

(5) If an “SS” message is originated, the priority alarm sequence must precede any additional data, which then is limited to 47 characters.

(OASIS–EXT–026)

j. Alignment.

(1) Alignment of CR, LF follows ORIGIN, PRIORITY ALARM, or ADF as appropriate.

(2) Always present.

k. Start of Text.

(1) Start of Text (STX) character.

(2) Following CR, LF of originator line.

(3) Always present.

03/26/2025

FOR OFFICIAL USE ONLY

l. Text.

(1) The TEXT field will contain an Information Unit as defined in section A.2.

(2) Text drafted in accordance with ICAO Annex 10, Volume II, section 4.4.15.

(3) Maximum 80 characters per line.

(4) Each line separated by End of Line (EOL) (CR CR LF).

(5) Always present.

m. End of Text.

(1) Vertical Tab (VT) character.

(2) End of Text (ETX) character.

(3) Following CR, LF, or EOL of the last line of text.

(4) Always present.

A.2 Information Unit Format

This paragraph describes the format of an information unit to be transmitted in the text field of an NMR message between OASIS and the External Users.

TEXT is a string of 1 to 3600 displayable characters including embedded EOL sequences. If a message requires acknowledgment by a message number, the first line (Number Line) in the TEXT field will have the following format:

Number Line:

where:

a. MSG ORIGIN is a string of 3 alpha characters indicating the origin of the message.

b. MSGNUM is a string of 3 numerics within the range 001 and 999 and indi-cates the number to be used in the acknowledgment.

c. SP is a single American Standard Code for Information Interchange (ASCII) space character.

d. ACK ADDR is a string of alphabetic and space characters, and contains the address(es) needing the acknowledgment.

NOTE

Lines are limited to 69 characters so addresses are aligned.

Addresses are aligned using a carriage return followed by a line feed.

MSG ORIGIN MSGNUM SP ACK ADDR

03/26/2025

FOR OFFICIAL USE ONLY

The following paragraphs describe the format of the information unit text field for the messages identified in tables 3–1 through 3–13.

A.3 Acknowledgment Message

The Acknowledgment message confirms receipt of the message from an addressee.

a. ACK ID is the character string ‘ACP’ or ‘R.’

b. SP is optional. If present, SP is a single ASCII space character.

c. ENTRY ID is either ACID or MSGNUM.

(1) ACID is Aircraft ID and is defined to be 1 alpha character followed by 1 to 6 alphanumeric characters.

(2) MSGNUM is a string of 3 numerics within the range 001 and 999.

d. TEXT is optional. If present, TEXT is a single ASCII space character followed by a single ASCII ‘Z’ character and 2 alpha characters.

e. FILLER is optional. If present, FILLER is a string of characters including embedded EOL sequences. The number of characters between each EOL will not exceed 69 characters.

f. EOL is a string of 2 carriage returns followed by a line feed.

NOTE

The requirement for the OASIS to transmit 95 percent of acknowledgment messages to the External User within 0.5 sec-onds of receipt of a message from the External User has been waived. The OASIS requirement for this capability has been established to be within 3.0 seconds average response time.

A.4 QALQ Request

An Initial Action Domestic SAR message, the QALQ Request, is originated by a site that is the destination of an aircraft, which has been determined to be overdue. The QALQ is the initial message to be sent for a search and rescue procedure. This message does not require acknowledgment.

a. ‘QALQ’ is the actual string of ASCII characters required for a QALQ Message.

b. SP is a single ASCII space character.

c. ACID is Aircraft ID and is defined to be 1 alpha character followed by 1 to 6 alphanumeric characters.

d. TEXT is a string of characters including embedded EOL sequences. The number of characters between each EOL will not exceed 69 characters.

e. EOL is a string of 2 carriage returns followed by a line feed.

ACK ID SP ENTRY ID TEXT FILLER EOL

‘QALQ’ SP ACID SP TEXT EOL

03/26/2025

FOR OFFICIAL USE ONLY

A.5 QALQ Cancellation

The QALQ Cancellation format is the same as the QALQ Request format with ‘CNLD’ as the first four characters in the TEXT field. The QALQ Cancellation is sent by the site that originated the QALQ Request message to notify all recipients of the QALQ that the aircraft has been located. This message does not require acknowledgment.

A.6 QALQ Response

The QALQ Response format is the same as the QALQ Request format with the response in the TEXT field. This message is originated by the site that is the recipient of a QALQ Request. The response to the QALQ Request provides the results or status of the com-munications search. Also, the QALQ Response can provide pertinent information about the missing aircraft, or provides notification to the destination site if the aircraft is located. This message does not require acknowledgment.

A.7 INREQ Request

An Information Request Domestic SAR message, the INREQ Request, is originated by a site that is the destination of an aircraft that has been determined to be overdue. The INREQ Request is a follow-up message to a QALQ message. An INREQ Request is issued when the originating station has had a negative response to a previously issued QALQ for an overdue aircraft. This message requires acknowledgment; therefore, the Number Line is present in the Information Unit as described in section A.2.

a. ‘INREQ’ is the actual string of ASCII characters required for an INREQ Request Message.

b. SP is a single ASCII space character.

c. ACID is Aircraft ID and is defined to be 1 alpha character followed by 1 to 6 alphanumeric characters.

d. TEXT is a string of characters including embedded…