Nas Ird 11013400

NAS-IRD-11013400
Revision -
May 22, 2017
Surveillance to ATC Automation System

All Purpose Structured Eurocontrol Surveillance
Information Exchange (ASTERIX)
Interface Requirements Document (IRD),
Developed by Surveillance Interface Modernization
(SIM) Program
NAS-IRD-11013400, Revision –
May 22, 2017
Federal Aviation Administration
600 Independence Avenue, SW
Washington, D.C. 20591

NAS-IRD-11013400
Revision -
May 22, 2017
Interface Requirements Document (IRD)

Surveillance Interface Modernization (SIM)
Approval Signatures
Name Organization Signature Date
Robert Nichols AJM-23, Surveillance
and Broadcast Services
Malcolm Andrews AJM-31,

Communication,
Information and
Network Program
Steve Reynolds AJM-21, Air Traffic
Management Program
Amee Patel AJM-25, En Route and
Oceanic 2nd Level
Engineering
Tony DelaVega AJW-14, National Airway
Systems Engineering
(NASE)
Kimberly Gill ANG-B1,NAS
Requirements and
Interface Management
Group
Page ii of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Revision Record
REVISION DESCRIPTION DATE ENTERED BY

Number
- Baseline release 05-22-17 P. Kilfoile
Page iii of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Table of Contents
1 Scope ..................................................................................................................................................... 1
1.1 Summary ....................................................................................................................................... 2

1.2 Subsystem Responsibility List ....................................................................................................... 3
2 Applicable Documents .......................................................................................................................... 5
2.1 Government Documents............................................................................................................... 5

2.2 Non-Government Documents....................................................................................................... 6
2.3 Document Sources ........................................................................................................................ 7
2.3.1 Electronic Industries Alliance Documents............................................................................. 7
2.3.2 ISO/IEC Documents ............................................................................................................... 7
2.3.3 IEEE/ANSI Documents ........................................................................................................... 7
2.3.4 IETF Standard (RFC) Documents ........................................................................................... 8
2.3.5 EUROCONTROL Documents .................................................................................................. 8
3 Interface Requirements ........................................................................................................................ 9
3.1 General Requirements .................................................................................................................. 9

3.1.1 Security Requirements ........................................................................................................ 10
3.2 Functional Requirements ............................................................................................................ 10
3.2.1 Functional Design Requirements ........................................................................................ 10
3.2.2 Application Processes and Message Requirements............................................................ 11
3.2.3 Protocol Implementation .................................................................................................... 31
3.3 Physical Requirements / Characteristics ..................................................................................... 38
3.3.1 Electrical Power and Electronic Characteristics .................................................................. 38
4 Quality Assurance Provisions .............................................................................................................. 41
4.1 Responsibility for Verification ..................................................................................................... 41

4.2 Special Verification Requirements .............................................................................................. 41
4.3 Verification Requirements Traceability Matrix ........................................................................... 41
5 Preparation for Delivery ..................................................................................................................... 43
6 Notes ................................................................................................................................................... 44
6.1 Definitions ................................................................................................................................... 44

6.2 Abbreviations and Acronyms ...................................................................................................... 48
Page iv of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Appendix A – General ASTERIX Message Formats ...................................................................................... 52
A.1 Message Structure ............................................................................................................................ 52

A.1.1 General .......................................................................................................................................... 52
A.1.2 Data Field Formats ......................................................................................................................... 53
Appendix B – System Specific Architecture ................................................................................................ 54
Appendix C – Verification Requirements Traceability Matrix..................................................................... 60
Appendix D – Verification Requirements System Applicability Matrix....................................................... 81
List of Figures
Figure 1-1 – SIM Multicast Architecture ....................................................................................................... 2
Figure 3-1 – OSI 7 Layer Model ................................................................................................................... 32
Figure 3-2– Presentation Layer Data Unit................................................................................................... 33
Figure 3-3– Surveillance and Automation Interfaces (On-Airport)............................................................. 37
Figure 3-4 – Surveillance and Automation Interfaces (Off-Airport) ........................................................... 37
Figure A-1 – ASTERIX Data Block Structure ................................................................................................. 52
Figure B-1 – ASR-9 On Airport Configuration.............................................................................................. 55
Figure B-2 – ASR-9 Off-Airport Configuration ............................................................................................. 56
Figure B-3 – ASR-9 Consolidated TRACON Configuration ........................................................................... 58
Figure B-4 – ERAM Off-Airport Configuration............................................................................................. 59
List of Tables
Table 1-1 – Subsystem Responsibility List .................................................................................................... 3
Table 3-1 – ASTERIX Category Provider and User ....................................................................................... 10
Table 3-2 – Data Streams ............................................................................................................................ 12
Table 3-3 – Cat048 User Application Profile and Construction .................................................................. 16
Table 3-4 – Cat034 Sector Crossing UAP..................................................................................................... 19
Table 3-5 – Cat034 North Marker UAP ....................................................................................................... 21
Table 3-6 – Cat034 Jamming Strobe UAP ................................................................................................... 23
Table 3-7 – Cat008 Start Of Picture (SOP) UAP ........................................................................................... 24
Table 3-8 – Cat008 Sequence of Polar Vectors UAP ................................................................................... 26
Table 3-9 – Cat008 End Of Picture (EOP) UAP ............................................................................................ 28
Page v of 93
NAS-IRD-11013400
Revision -
May 22, 2017
1 Scope
The Surveillance Interface Modernization (SIM) Program will modernize the interfaces between FAA
Surveillance radar and Automation systems for Terminal, En Route, and Oceanic Air Traffic Control (ATC)
operations. The improved interconnectivity will result in less downtime, fewer errors, and improved
aircraft surveillance information delivered to the air traffic automation systems, including a more accurate
target position from the radar (if available) resulting in more accurate controller display data. Modern
radars generate several categories of surveillance data, such as unique aircraft identification, more precise
range/azimuth data, trajectory, and tracking data which cannot be transmitted in the current CD-2
message due to insufficient capacity and inherent Common Digitizer Model-2 (CD-2) data structure
limitations. The SIM Program will facilitate the transition to the Next Generation (NextGen) environment
by incorporating the internationally accepted All-Purpose Structured Eurocontrol Radar Information
Exchange (ASTERIX) data format and using Internet Protocol (IP) communications.
SIM data transport improvements are achieved by converting the radar and automation systems from the
current serial interfaces to a robust, scalable, state-of-the-art IP data distribution model over a secure
network provided by FAA Telecommunications Infrastructure (FTI) services. Upgrading from serial to IP
data transmission networks will simplify circuit management, defend and mitigate cyber security threats,
be scalable for future customers, and provide direct performance metrics.
SIM data format improvements are achieved by using ASTERIX data architecture over the IP network.
ASTERIX data formats will enable radars to provide the additional data fields needed by automation to
improve tracker, display, and safety logic performance in the future. This format will allow the
transmission of radar data, such as International Civil Aviation Organization (ICAO) codes and Time of
Day, from the Surveillance Systems to the ATC Automation Systems.
Access to additional radar data will enable future performance enhancements for ATC Automation
Systems, and will allow, in the long-term, a more robust support of future operational improvements and
the enhancement of future facilities capabilities. Additionally, it will provide improved independent and
backup radar capabilities when Automatic Dependent Surveillance - Broadcast (ADS-B) surveillance
becomes the primary source of aircraft position reporting. ASTERIX messages carry additional data
elements to better support the increased demands of modern ATC Automation Systems, including
enhancements to fusion tracking. The more extensive data format will provide the 24-bit aircraft address,
a timestamp associated with the aircraft position, Mode S data link access to aircraft sensors, and
additional positional resolution bits, which provide a more accurate determination of an aircraft’s
location.
Simplifying the radar data transmission architecture to distribute available radar system data, to both the
National Airspace System (NAS) and non-NAS Systems, will provide an effective and efficient method to
improve information flow from radar to automation systems. Additionally, information security measures
can be applied more consistently.
The Maintenance and Control (M&C) requirements pertain to the remoting of the existing radar systems'
maintenance terminal for status and control at Terminal Radar Approach Control (TRACON) or Air Route
Traffic Control Center (ARTCC). The Surveillance System’s M&C function for status and control of the
radar will use IP. Existing Surveillance System’s that use IP for M&C may retain their current design. The
M&C function is not part of the Remote Maintenance Monitor System (RMMS) function.
Page 1 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
The enhanced capabilities resulting from the SIM Program will reduce the maintenance overhead costs of
legacy systems, reduce costs for the implementation of future systems, provide for better fusion of
surveillance data, and enable future capabilities.
1.1 Summary
The Interface Requirements Document (IRD), prepared with guidance from FAA-STD-025f, provides the
design requirements for the interface between the Surveillance Systems and ATC Automation Systems to
support the transmission of ASTERIX data through the IP based Network. Changes in the interface require
coordination among all recipients.
The set of ASTERIX data fields provided by a surveillance system is provided on two redundant Local Area
Network (LAN) interfaces. Figure 1-1 depicts the general architecture of the interface between
Surveillance, Communications and ATC Automation Systems.
The Surveillance Broadcast Service (SBS) will continue to use the SBS System private network for the
supporting delivery of Automatic Dependent Surveillance – Broadcast (ADS-B), ADS-Rebroadcast (ADS-R),
Traffic Information Services - Broadcast (TIS-B), and Flight Information Services - Broadcast (FIS-B)
Services. The SBS System will continue to provide ATC Automation Systems in accordance with the SBS
SDP ICD (NAS-IC-8253001-01). For the purpose of SIM, the SBS System will receive Surveillance Data from
the FTI OPIP network or the SBS System private network.
Figure 1-1 – SIM Multicast Architecture

NOTE:
Page 2 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
• In this document, “shall” indicates a mandatory requirement.

• In this document, “may” and "should" indicates a desirable but not mandatory function or
characteristic.
• In this document, text denoted by “Note” is explanatory and editorial and is not part of the
interface requirements.
• Appendix D contains a Verification Requirements System Applicability Matrix to clearly define
which System each requirement is allocated.
1.2 Subsystem Responsibility List

The following subsystems are affected by this IRD:
Table 1-1 – Subsystem Responsibility List
Responsible
Program
Subsystem Name Office
FTI FAA Telecommunications AJM-31
Infrastructure
STARS Standard Terminal Automation AJM-211
Replacement System
ERAM En Route Automation AJM-213
Modernization
MicroEARTS Micro En Route Automated AJM-252
Radar Tracking System
ATOP Advanced Technologies and AJM-252
Oceanic Procedures
WAM Wide Area Multilateration AJM-232
ASDE-X Airport Surface Detection AJW-148
Equipment – Model X
ASSC Airport Surface Surveillance AJM-232
Capability
CTD Common Terminal Digitizer AJW-147
SBS Surveillance and Broadcast AJM-232
Services
ASR-9 Airport Surveillance Radar – AJW-146
Model 9
ASR-11 Airport Surveillance Radar – AJW-147
Model 11
Page 3 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Responsible
Program
Subsystem Name Office
ATCBI-6(M) Air Traffic Control Beacon AJW-147
Interrogator – Model 6 (Mode 4)
Mode S Mode Select Secondary AJW-145
Surveillance Radar
CARSR Common Air Route Surveillance AJW-142
Radar
ARSR-4 Air Route Surveillance Radar – AJW-142
Model 4
Page 4 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
2 Applicable Documents
The following documents form a part of this IRD to the extent specified herein. In the event of conflict
between the documents referenced herein and the contents of this IRD, this IRD will be considered the
superseding requirement.
2.1 Government Documents

Ref No Number Description
1 Code of Federal Regulations, Class A Digital Devices for Unintentional Radiators, October
Title 47 Part 15 8, 2015
2 DTFA01-02-D-03006 FAA Telecommunications Services Description (FTSD)
3 FAA-C1217 Electric Work, Interior Standards, February 26, 1996
4 FAA-G-2100h Electronic Equipment General Requirements, May 9, 2005
5 Federal Aviation Administration Handbook: National
FAA-HDBK-004 Airspace System (NAS) Internet Protocol Suite , September 4,
1997
6 Implementation of Federal Aviation Administration (FAA)
FAA Order 1370.114 Telecommunications Infrastructure (FTI) Services and
Information Security Requirements
7 National Airspace System (NAS) Internet Protocol (IP)
FAA JO 1370.117
Addressing Policy
8 U.S. Department of Transportation, Federal Aviation
Administration, Standard, Lightning and Surge Protection,
FAA-STD-019E
Grounding, Bonding and Shielding Requirements for
Facilities and Electronic Equipment, December 2005
9 FAA-STD-025f US Department of Transportation, Federal Aviation
Administration Standard, Preparation of Interface
Documentation, November 30, 2007
10 U.S. Department of Transportation, Federal Aviation
Administration, Standard Practice, National Airspace System
FAA-STD-039C
(NAS) Open System Architecture and Protocols, August 14,
2003
11 National Airspace System (NAS) Naming and Addressing
FAA-STD-042B
Structure for Ground-To-Ground Communication
12 Surveillance to ATC Automation System All-Purpose
Structured Eurocontrol Surveillance Information Exchange
NAS-ICD-11013400
(ASTERIX) Interface Control Document (ICD) Developed by
the SIM Program, currently in draft status
13 NAS-IC-8253001-01 Surveillance and Broadcast Services (SBS) Service Delivery
Point (SDP) to ATC Automation and Service Monitoring User
Page 5 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Ref No Number Description

Subsystems Interface Control Document (ICD), v3.8, dated
September 16, 2015
14 Maintenance of Electrical Power and Control Cables, May 8,
Order 6950.22
2014
15 FAA William J Hughes Technical Center Test and Evaluation
VVSPT-A2-PDD-013
Handbook, Version 3.0, September 24, 2013
2.2 Non-Government Documents

Ref No Name/Number Description
1 ANSI/IEEE Standard 1100- Recommended Practice for Powering and Grounding
2005 Electronic Equipment
2 EUROCONTROL Part 1, EUROCONTROL Specification for Surveillance Data Exchange
ASTERIX - Part 1 All Purpose Structured EUROCONTROL Surveillance
Information Exchange (ASTERIX), EUROCONTROL-SPEC-0149,
Edition 2.3 dated November 12, 2015
3 EUROCONTROL ASTERIX EUROCONTROL Specification for Surveillance Data Exchange
Cat008, Weather Information ASTERIX Part 3 Category 008 Monoradar Derived Weather
Information, EUROCONTROL-SPEC-0149-3, Edition 1.2 dated
August 24, 2014
4 EUROCONTROL ASTERIX EUROCONTROL STANDARD DOCUMENT FOR SURVEILLANCE
Cat034, Service Messages DATA EXCHANGE Part 2b Transmission of Monoradar Service
Messages, SUR.ET1.ST05.2000-STD-02b-01, Edition 1.27
dated May 2007
6 EUROCONTROL ASTERIX EUROCONTROL STANDARD DOCUMENT FOR SURVEILLANCE
Cat048, Target Reports DATA EXCHANGE Part 4 : Category 048 Transmission of
Monoradar Target Reports, SUR.ET1.ST05.2000-STD-04-01,
Edition 1.21 dated July 2012
7 EUROCONTROL ASTERIX ASTERIX CATEGORY 253 SPECIFICATION, Issue 8.0 dated
Category 253 Specification December 2014
8 IEEE 802.3 CSMA/CD Access Method (Ethernet), December 26, 2008
9 IETF RFC-768 User Datagram Protocol
10 IETF RFC-791 Internet Protocol Version 4 (IPv4) Specification
11 IETF RFC-826 Ethernet Address Resolution Protocol
12 IETF RFC-922 Broadcasting Internet Datagrams in the Presence of Subnets
Page 6 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Ref No Name/Number Description

13 IETF RFC-950 Internet Standard Subnetting Procedure
14 IETF RFC-1122 Requirements for Internet Hosts - Communication Layers
15 IETF RFC-1123 Requirements for Internet Hosts - Application and Support
16 IETF RFC-2236 Internet Group Management Protocol, Version 2
17 IETF RFC-2460 Internet Protocol Version 6 (IPv6) Specification
18 IETF RFC-2464 Transmission of IPv6 Packets over Ethernet Networks
19 IETF RFC-4271 A Border Gateway Protocol 4 (BGP-4)
20 IETF RFC-4291 IPv6 Addressing Architecture
21 IETF RFC-4443 Internet Control Message Protocol (ICMPv6) for the Internet
Protocol Version 6 (IPv6) Specification
22 IETF RFC-4601 Protocol Independent Multicast – Sparse Mode (PIM-SM):
Protocol Specification
23 NEC NFPA 70 National Electrical Code and Handbook
24 Commercial Building Cabling for Telecommunication

TIA/EIA-568-C
Products and Services
2.3 Document Sources

2.3.1 Electronic Industries Alliance Documents
Copies of Electronic Industries Alliance (EIA) standards may be obtained from the Electronic Industries
Alliance, Technology Strategy and Standards Department, 2500 Wilson Boulevard, Arlington, VA 22201-
3834, or by calling (703) 907-7500, or through their web site at http://www.ecianow.org/.
2.3.2 ISO/IEC Documents
Copies of International Standards Organization (ISO)/International Electrotechnical Commission (IEC)
documents may be obtained from American National Standards Institute, 11 West 42nd Street, 13th Floor,
New York City, NY 10036. Telephone: (212) 642-4900, Telefax: (212) 398-0023,
Email: info@ansi.org
Web sites: http://www.ansi.org or http://www.iso.org
2.3.3 IEEE/ANSI Documents
Copies of Institute of Electrical and Electronics Engineers (IEEE)/American National Standards Institute
(ANSI) documents may be obtained from IEEE Computer Service, 445 Hoes Lane, P.O. Box 1331,
Piscataway, NJ 08855-1331, or by calling (800) 701-4333 (in the U.S. and Canada), or (732) 981-0060
Page 7 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
(outside of the U.S. and Canada), or through their standards web site at:
http://www.ieee.org/web/standards/home/index.html
2.3.4 IETF Standard (RFC) Documents
Copies of the Internet Engineering Task Force (IETF) Standard (RFC) documents may be obtained through
the web site: http://www.rfc-editor.org/rfc-index2.html
2.3.5 EUROCONTROL Documents
Copies of EUROCONTROL documents may be obtained through the web site:
http://www.eurocontrol.int/services/specifications-documents
Page 8 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
3 Interface Requirements
3.1 General Requirements
This IRD provides the requirement for the Surveillance System interface to ATC Automation System, a
system to system interface using the transmission of ASTERIX Data using Internet Protocol (IP). See:
http://www.eurocontrol.int/asterix. Therefore, no human system interface requirements are made
herein.
The interface provides a fully redundant physical link between the Surveillance System to ATC Automation
System as illustrated in Figure 1-1.
The design provides for the following:
• A one-way interface from the Surveillance System to the ATC Automation System for Target,
Weather and Status Reports. The Surveillance data is provided on two redundant LAN interfaces.
• A two-way interface is used for the exchange of Monitor and Control (M&C) data between the
Surveillance System and the remote M&C subsystem of the Surveillance System.
The points of demarcation are the Surveillance System ports and the ATC Automation ports connected via
a Communications System. The Surveillance System provides IP/ASTERIX Surveillance data over the
diverse paths in the Communications System to the ATC Automation Systems.
The Communications System will be provided by either the FTI Communications Service (off-airport) or
on-airport communications system from the Surveillance System to the ATC Automation System.
Representative interface diagrams are depicted in Figure 3-3 and Figure 3-4. These figures show the
interfaces for on-airport and off-airport configurations. Both configurations will provide the same number
of connections at the Surveillance System and the ATC Automation System. The point of demarcation for
the FTI Communications Service will be a Service Delivery Point (SDP) while the point of demarcation for
an on-airport communications system will be a Multi- Service Platform (MSP) device. FTI Communications
will provide redundant avoided paths between the Surveillance System and ATC Automation System. This
MSP could be a router, mux, modem, switch or Longport depending on the communication medium used
at that site and the Surveillance System. If ATC Automation System is receiving data from an ASR-9, the
point of demarcation will be the Digital Remote Surveillance Communication Interface Processor (SCIP)
Replacement (DRSR) for an on-airport configuration, but continue to be a SDP for an off-airport
configuration. These configurations are illustrated in Appendix B.
The Surveillance System will interface to the Communications System through redundant LAN interface.
The Surveillance System's online operational channel will send identical data on both LAN interfaces to
the ATC Automation system via the Communication System. The Surveillance System's standby channel
will not send any data.
[IRD0001] ASTERIX messages shall be in accordance with the EUROCONTROL Specification for Surveillance
Data Exchange - Part 1 All Purpose Structured EUROCONTROL Surveillance Information Exchange
(ASTERIX), EUROCONTROL-SPEC-0149, Edition 2.3 dated 11/12/2015.
[IRD0002] Surveillance Target Reports shall be formatted as ASTERIX Cat048 Monoradar Target Reports
in accordance with SUR.ET1.ST05.2000-STD-04-01, Edition 1.21, July 2012.
[IRD0003] Service Messages shall be formatted as ASTERIX Cat034 Monoradar Service Messages in
accordance with SUR.ET1.ST05.2000-STD-02b-01, Edition 1.27, May 2007.
Page 9 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
[IRD0004] Weather Reports shall be formatted as ASTERIX Cat008 Monoradar Derived Weather
Information in accordance with EUROCONTROL-SPEC-0149-3, Edition 1.2, 08/24/2014.
3.1.1 Security Requirements
Operational data sent to/received from the FTI SDP and/or MSP is protected with IP Security to provide
mutual peer entity authentication and payload integrity and confidentiality. The interface between the
FTI SDP and/or MSP and the sending/receiving system is within a physically secured government facility
staffed by cleared personnel. Protection for the interface is provided through physical and personnel
security measures.
SIM upgrades are applied to Authorized Systems in the NAS. Updates to Security compliance for the SIM
upgrade will be the responsibility of each system.
The Security Requirements are specified within the SIM Final Program Requirements Document (fPRD).
Origin authenticity, integrity, and confidentiality protection of packets between the Surveillance System
and the ATC Automation System is not required for existing FAA communications (i.e. dedicated fiber or
copper field cable) approved for interconnection of NAS assets.
3.2 Functional Requirements
3.2.1 Functional Design Requirements
Refer to the SIM fPRD for functional design requirements.
Table 3-1 summarizes the data flow between the Surveillance System and the ATC Automation System.
Table 3-1 – ASTERIX Category Provider and User
Page 10 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Source System Data Category Destination

Format
System Exchange System
Surveillance Beacon, ASTERIX 048 ATC Automation
System Search, Beacon System
and Search
RTQC
Surveillance Sector ASTERIX 034 ATC Automation
System Crossings, System
North Marker,
Jamming
Strobes
Surveillance Weather ASTERIX 008 ATC Automation

System* System**
Surveillance Status/Control ASTERIX/IP 253 or existing M&C

System to Remote or Interface Data (Surveillance
Terminals and existing/IP Format Remote
Control Panels Subsystem)
M&C Status/Control 253 or existing Surveillance
ASTERIX/IP
(Surveillance from Remote Interface Data System
or
Remote Terminals and Format
existing/IP
Subsystem) Control Panels
* – WAM, ATCBI-6(M) and Mode S En Route do not provide weather data
** – SBS does not process weather data
3.2.2 Application Processes and Message Requirements
The Surveillance Systems have one or more applications that provide for the transmission of the
Surveillance Data to the receiving system via the FTI SDP and/or MSP. The ATC Automation System has
one or more applications that receive those Surveillance Data. The details of each Surveillance and ATC
Automation Systems’ application is within their respective System Design documents.
3.2.2.1 Identification of Each Application Process
[IRD0005] The Surveillance System's destination multicast address shall be site adaptable for each Data
Stream in Table 3-2 on each redundant LAN interface.
[IRD0006] The Surveillance System's transport layer port shall be site adaptable, see Table 3-2.
[IRD0007] The ATC Automation System's transport layer port shall be site adaptable, see Table 3-2.
Across Surveillance Systems, the transport layer port number for all Data Streams will be the same. These
port numbers will be identified in the Surveillance to ATC Automation System All-Purpose Structured
Eurocontrol Surveillance Information Exchange (ASTERIX) Interface Control Document (ICD) Developed by
the SIM Program, NAS-ICD-11013400. IP and IP Multicast Address assignments will be in accordance with
Section 3.2.3.3.
Page 11 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Table 3-2 – Data Streams

Data Streams ASTERIX Category Red Core Network Blue Core Network
(Protocol)
Multicast Port Multicast Port
Address Address
Target Report Cat048 (UDP) Address A Port X Address F Port Y
(Combined and SSR
Only)
Target Report Cat048 (UDP) Address B Port X Address G Port Y
(uncorrelated PSR
Only)
Target Report Cat048 (UDP) Address C Port X Address H Port Y
(correlated PSR
Only)
Service Message Cat034 (UDP) Address D Port X Address I Port Y
Weather Reports Cat008 (UDP) Address E Port X Address J Port Y
3.2.2.2 Application Process Capability Requirements

The Surveillance and ATC Automation Systems application processes are still held to their respective
accuracy, throughput, latency and availability requirements. The details of each Surveillance and ATC
Automation Systems’ application is within their respective System Design documents.
The Communications System interconnects the various Surveillance Systems with a high-availability
redundant IP network. FTI will provide Customer Premise Equipment (CPE) at the Surveillance and ATC
Automation System. CPE is any FTI equipment that supports FTI services at the Surveillance or ATC
Automation System facility. The FTI Communications Service receives/sends messages from/to the
Surveillance System and the Automation System. The FTI Communications Service then transports the
messages and distributes them to their intended destinations. The FTI Communications Service maintains
multicast Access Control Lists (ACLs) identifying authorized Surveillance data subscribers and authorized
receiving ATC Automation Systems.
[IRD0008] The FTI Communications Service shall own the CPE at the Surveillance Systems facility.
[IRD0009] The FTI Communications Service shall own the CPE at the ATC Automation Systems facility.
[IRD0010] The FTI Communications Service shall maintain the CPE at the Surveillance Systems facility.
[IRD0011] The FTI Communications Service shall maintain the CPE at the ATC Automation Systems facility.
[IRD0012] The Communications System shall only pass incoming data with approved source IP addresses,
destination IP addresses, protocols and port numbers.
[IRD0013] The Communications System shall log occurrences of unapproved source IP addresses,
destination IP addresses, protocols and port numbers.
[IRD0014] The Communications System shall block incoming Transmission Control Protocol (TCP)
connection attempts from unapproved IP addresses and port numbers.
Page 12 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
[IRD0015] The Communications System shall log incoming TCP connection attempts from unapproved IP
addresses and port numbers.
3.2.2.3 Message Content Requirements
The Surveillance System outputs and the ATC Automation System receives and processes Surveillance
Data in accordance with Section 3.1.
The M&C message content utilizes IP format and is detailed in the Surveillance Systems respective System
Design documents.
The following requirements apply to all categories of ASTERIX identified in this IRD.
[IRD0016] The Surveillance System shall generate an ASTERIX Data Block with a site adaptable maximum
size up to 1494 bytes.
Note: The max packet size is 1500 bytes. This requirement is for the Application Layer and the
Presentation Layer adds 6 bytes for the Sequence Number and CRC-32.
[IRD0017] The Surveillance System shall default the ASTERIX Data Block maximum size to 506 bytes.
[IRD0018] The Surveillance System shall set all spare bits to zero in the ASTERIX Record.
[IRD0019] The Surveillance System shall determine the Data Item applicability for an ASTERIX Record as
described in Table 3-3 through Table 3-9.
[IRD0020] The Surveillance System shall populate Category 048 ASTERIX messages in accordance with
Table 3-3.
Table 3-4 through Table 3-6.
Table 3-7 through Table 3-9.
[IRD0023] The ATC Automation System shall receive the Category 048 ASTERIX messages in accordance
with Table 3-3.
with Table 3-4 through Table 3-6.
with Table 3-7 through Table 3-9.
[IRD0026] The Surveillance System shall transmit ‘compulsory’ Data Items in every ASTERIX Record, except
where noted in the Surveillance to ATC Automation System ASTERIX ICD Developed by the SIM Program,
NAS-ICD-11013400.
[IRD0027] The Surveillance System shall transmit ‘compulsory if available’ Data Items in an ASTERIX
Record when data is available for transmission.
[IRD0028] The Surveillance System shall be adaptable for transmission of each ‘optional’ Data Items in an
ASTERIX Record.
[IRD0029] The Surveillance System shall be adaptable for transmission of each subfield in the Special
Purpose Field of the Category 048 ASTERIX message.
Page 13 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
[IRD0030] The Surveillance System shall be adaptable for transmission of each subfield in the Special
Purpose Field of the Category 034 ASTERIX message.
[IRD0031] The Surveillance System shall default ‘optional’ Data Items to disabled, except where noted in
the Surveillance to ATC Automation System ASTERIX ICD Developed by the SIM Program, NAS-ICD-
11013400.
[IRD0032] The Surveillance System shall exclude ‘not used’ Data Items from an ASTERIX Record.
[IRD0033] The Surveillance System shall use True North as Local Geographical North for all Surveillance
Data using an azimuth reference.
[IRD0034] If available, the Surveillance System shall populate I034/050 COM Subfield Bit 8 (NOGO) based
on the overall system summary state (i.e. radar released to maintenance).
[IRD0035] If available, the Surveillance System shall populate I034/SP Summary Fault field based on the
overall system summary status.
[IRD0036] The Surveillance System shall transmit I034/120 (3D_Position of Data Source) with North
Marker Service Messages at Surveillance System startup and every UTC half hour in accordance with Table
3-4 through Table 3-6.
[IRD0037] The Surveillance System shall populate I034/120 (3D_Position of Data Source) with the
surveyed position of the radar at the height of the beacon antenna in accordance with Table 3-4 through
Table 3-6.
[IRD0038] The Surveillance System shall transmit I034/050 (System Configuration and Status) with Sector
0 or the sector after a change in accordance with Table 3-4 through Table 3-6.
[IRD0039] The Surveillance System shall transmit I034/060 (System Processing Mode) with Sector 0 or the
sector after a change in accordance with Table 3-4 through Table 3-6.
[IRD0040] The Surveillance System shall limit I008/120 Total Number of Items Constituting One Weather
Picture to a maximum of 4000 Vectors.
[IRD0041] The Surveillance System shall format M&C messages as ASTERIX Cat253 Radar Station Monitor
and Control Information, in accordance with the EUROCONTROL ASTERIX Category 253 Specification, Issue
8.0, December 2014, or existing protocol over TCP/IP.
[IRD0042] The Surveillance System M&C messages maximum packet size shall be 1500 bytes.
[IRD0043] The Surveillance System shall prioritize the order of message transmission using the following
prioritization:
1. Cat034 Service Messages
2. Cat048 Target Reports
3. Cat008 Weather Reports
4. M&C Messages
[IRD0044] The ATC Automation System shall parse all Data Items identified in the Field Specification
(FSPEC) of each ASTERIX Record which is compliant with ASTERIX Category’s UAP.
ASTERIX messages are allocated to a Standard User Application Profile (UAP) consisting of Data Fields.
Data Fields within an ASTERIX message are associated with a Field Reference Number (FRN) and are
populated with Data Items. The UAP can be considered a control table attached to the message
Page 14 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
assembly/disassembly program resident in the processing system. Some Data Items are compulsory while
others are optional. At transmission time, not all the Data Fields (Data Items) need be output.
The following tables define the Standard Data Items for ASTERIX Categories 048, 034 and 008. Each Data
Item is defined as Compulsory (C), Compulsory if Available (C/A), Optional (O) or Not Used (X) which are
defined in Section 6.1.
Page 15 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
3.2.2.3.1 UAP and Standard Data Items – Category 048 (Target Report)
Category 048 Target Reports transmitted to end users will be formatted as defined in the following sections.
Table 3-3 – Cat048 User Application Profile and Construction
FRN Data Item Description Criteria for Inclusion:
Ref. No. Compulsory: (C)
Compulsory if Available: C/A
Optional: (O)
Not Used (X)
ASR-8 ASR-8 ASR-9/ ASR-9/ ASR-9/ ASR-11 ASR-11 ATCBI- Mode S WAM CARSR/ CARSR / ARSR-4 /
CTD CTD ATCBI- SLEP’d unSLEP’d KACY- KACY- 6(M) VR Mode S ATCBI-6(M) ATCBI-6(M)
ATCBI- Mode S 5 or IBI Mode S Mode S 1 3
5
1 I048/010 Data Source Identifier C C C C C C C C C C C C C
2 I048/140 Time-of-Day C C C C C C C C C C C C C
3 I048/020 Target Report Descriptor C C C C C C C C C C C C C
4 I048/040 Measured Position in C C C C C C C C C C C C C

Slant Polar Coordinates
5 I048/070 Mode-3/A Code in Octal C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A
Representation
6 I048/090 Flight Level in Binary C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A
Representation
7 I048/130 Radar Plot C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A
Characteristics
8 I048/220 Aircraft Address X C/A X C/A X X C/A C/A C/A C/A C/A C/A C/A
9 I048/240 Aircraft Identification X X X X X X O O X O X X X
10 I048/250 Mode-S MB Data X X X X X X O O X X X X X
Page 16 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Optional: (O)
Not Used (X)
5
11 I048/161 Track Number X X X C/A X C/A C/A C/A C/A X C/A C/A C/A
12 I048/042 Calculated Position in X X X X X X X X X X X X X

Cartesian Coordinates
13 I048/200 Calculated Track X X X X X O O O X X O O O
Velocity in Polar
Representation
14 I048/170 Track Status X X X C/A X C/A C/A C/A C/A C/A C/A C/A C/A
15 I048/210 Track Quality X X X O X X X X O X O O O
16 I048/030 Warning/Error C/A C/A C/A C/A C/A C/A C/A C/A C/A X C/A C/A C/A
Conditions
17 I048/080 Mode-3/A Code O O X O X O O O O O O O O
Confidence Indicator
18 I048/100 Mode C Code and O O X O X O O O O O O O O
19 I048/110 Height Measured by 3D X X X X X O O O X X O O O
Radar
20 I048/120 Radial Doppler Speed X X O O O X X X X X O O O
21 I048/230 Communications/ ACAS X X X X X X O O X O X X X

Capability and Flight
Status
22 I048/260 ACAS Resolution X X X X X X O O X X X X X
Advisory Report
Page 17 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Optional: (O)
Not Used (X)
5
23 I048/055 Mode-1 Code in Octal X X X X X X X O X X X X X
Representation
24 I048/050 Mode-2 Code in Octal C/A C/A C/A C/A C/A C/A C/A C/A C/A X C/A C/A C/A
Representation
25 I048/065 Mode-1 Code X X X X X X X O X X O O O
26 I048/060 Mode-2 Code O O X O X O O O O X O O O
27 I048/SP Special Purpose O O O O O O O X O O O O O
28 I048/RE Reserved Expansion X X X X X X X X X X X X X
Page 18 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
3.2.2.3.2 UAP and Standard Data Items – Category 034 (Service Messages)
Table 3-4 – Cat034 Sector Crossing UAP
Optional: (O)
Not Used (X)
ASR-8 ASR-8 ASR-9/ ASR-9/ ASR-9/ ASR-11 ASR-11 ATCBI- Mode S WAM CARSR/ CARSR ARSR-4 /
CTD CTD ATCBI-5 SLEP’d unSLEP’d 6(M) VR Mode S / ATCBI-
KACY-1 KACY-
ATCBI-5 Mode S or IBI Mode S Mode S ATCBI- 6(M)
3
6(M)
1 I034/010 Data Source C C C C C C C C C C C C C
Identifier
2 I034/000 Message Type C C C C C C C C C C C C C
4 I034/020 Sector C C C C C C C C C C C C C
Number
5 I034/041 Antenna X X X X X X X X X X X X X
Rotation
Period
6 I034/050 System C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A
Configuration
and Status
7 I034/060 System C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A
Processing
Mode
8 I034/070 Message X X X X X X X O O X X X X
Count Values
9 I034/100 Generic Polar X X X X X X X X X X X X X
Window
10 I034/110 Data Filter X X X X X X X X X X X X X
Page 19 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Optional: (O)
Not Used (X)
KACY-1 KACY-
3
6(M)
11 I034/120 3D-Position of X X X X X X X X X X X X X
Data Source
12 I034/090 Collimation X X X X X X X X X X X X X
Error
13 RE-Data Reserved X X X X X X X X X X X X X
Item Expansion
Field
14 SP-Data Special O O O O O O O O O O O O O
Item Purpose Field
Page 20 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Table 3-5 – Cat034 North Marker UAP

Optional: (O)
Not Used (X)
KACY-1 KACY-
3
6(M)
1 I034/010 Data Source C C C C C C C C C C C C C
Identifier
2 I034/000 Message Type C C C C C C C C C C C C C
4 I034/020 Sector X X X X X X X X X X X X X
Number
5 I034/041 Antenna X X X X X X X X X X X X X
Rotation
Period
6 I034/050 System X X X X X X X X X X X X X
Configuration
and Status
7 I034/060 System X X X X X X X X X X X X X
Processing
Mode
8 I034/070 Message X X X X X X X X X X X X X
Count Values
9 I034/100 Generic Polar X X X X X X X X X X X X X
Window
10 I034/110 Data Filter X X X X X X X X X X X X X
Page 21 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Optional: (O)
Not Used (X)
KACY-1 KACY-
3
6(M)
11 I034/120 3D-Position of C/A C/A C/A C/A C/A C/A C/A C/A C/A X C/A C/A C/A
Data Source
12 I034/090 Collimation X X O O X X X O X X C/A C/A C/A
Error
13 RE-Data Reserved X X X X X X X X X X X X X
Item Expansion
Field
14 SP-Data Special X X X X X X X X X X X X X
Item Purpose Field
Page 22 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Table 3-6 – Cat034 Jamming Strobe UAP

Optional: (O)
Not Used (X)
ATCBI- CARSR/ CARSR / ARSR-4 /
6(M) Mode S ATCBI-6(M) ATCBI-6(M)
1 I034/010 Data Source C C C C
Identifier
2 I034/000 Message Type C C C C
3 I034/030 Time-of-Day X C C C
4 I034/020 Sector Number X X X X
5 I034/041 Antenna X X X X
Rotation
Period
6 I034/050 System X X X X
Configuration
and Status
7 I034/060 System X X X X
Processing
Mode
8 I034/070 Message X X X X
Count Values
9 I034/100 Generic Polar C C C C
Window
10 I034/110 Data Filter X X X X
11 I034/120 3D-Position of X X X X
Data Source
12 I034/090 Collimation X X X X
Error
13 RE-Data Item Reserved X X X X
Expansion
Field
14 SP-Data Item Special X C/A C/A C/A
Purpose Field
Page 23 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
3.2.2.3.3 UAP and Standard Data Items – Category 008 (Monoradar-Derived Weather Information)
Table 3-7 – Cat008 Start Of Picture (SOP) UAP
Optional: (O)
Not Used (X)
ASR-8 ASR-8 ASR-9/ ASR-9/ ASR-9/ ASR-11 ASR-11 CARSR/ CARSR / ARSR-4 /
CTD CTD ATCBI- SLEP’d unSLEP’ KACY- KACY- Mode S ATCBI-6(M) ATCBI-6(M)
ATCBI- Mode S 5 or IBI Mode S d Mode S 1 3
5
1 I008/010 Data Source C C C C C C C C C C
Identifier
2 I008/000 Message Type C C C C C C C C C C
3 I008/020 Vector X X X X X X X X X X
Qualifier
4 I008/036 Sequence of X X X X X X X X X X
Cartesian
Vectors in SPF
Notation
Polar Vectors
in SPF
Notation
6 I008/040 Contour X X X X X X X X X X
Identifier
Contour Points
in SPF
Notation
8 I008/090 Time of Day C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A
9 I008/100 Processing C C C C C C C C C C
Status
Page 24 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Optional: (O)
Not Used (X)
5
10 I008/110 Station X X X X X X X O O O
Configuration
Status
11 I008/120 Total Number X X X X X X X X X X
of Items
Constituting
One Weather
Picture
Weather
Vectors in SPF
Notation
13 I008/RE Reserved X X X X X X X X X X
Expansion
Field
14 I008/SP Special X X X X X X X X X X
Purpose Field
Page 25 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Table 3-8 – Cat008 Sequence of Polar Vectors UAP

Optional: (O)
Not Used (X)
5
Identifier
3 I008/020 Vector C C C C C C C C C C
Qualifier
Cartesian
Vectors in SPF
Notation
5 I008/034 Sequence of C C C C C C C C C C
Polar Vectors
in SPF
Notation
Identifier
Contour Points
in SPF
Notation
8 I008/090 Time of Day X X X X X X X X X X
9 I008/100 Processing X X X X X X X X X X
Status
10 I008/110 Station X X X X X X X X X X
Configuration
Status
Page 26 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Optional: (O)
Not Used (X)
5
11 I008/120 Total Number X X X X X X X X X X
of Items
Constituting
One Weather
Picture
Weather
Vectors in SPF
Notation
Expansion
Field
Purpose Field
Page 27 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Table 3-9 – Cat008 End Of Picture (EOP) UAP

Optional: (O)
Not Used (X)
5
Identifier
3 I008/020 Vector X X X X X X X X X X
Qualifier
Cartesian
Vectors in SPF
Notation
Polar Vectors
in SPF
Notation
Identifier
Contour Points
in SPF
Notation
8 I008/090 Time of Day C/A C/A C/A C/A C/A C/A C/A C/A C/A C/A
9 I008/100 Processing X X X X X X X X X X
Status
10 I008/110 Station X X X X X X X O O O
Configuration
Status
Page 28 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Optional: (O)
Not Used (X)
5
11 I008/120 Total Number C C C C C C C C C C
of Items
Constituting
One Weather
Picture
Weather
Vectors in SPF
Notation
Expansion
Field
Purpose Field
Page 29 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
3.2.2.4 Relationship among Messages

[IRD0045] The Surveillance System shall package Cat048 ASTERIX Records of the same Data Stream as
identified in Table 3-2 into the same IP packet.
[IRD0046] The Surveillance System shall package Cat008 ASTERIX Records into the same IP packet.
[IRD0047] The Surveillance System shall include a single Cat034 ASTERIX Record per IP packet.
[IRD0048] The Surveillance System ASTERIX Data Block packing period shall ensure that the Surveillance
System latency is met.
[IRD0049] The Surveillance System shall transmit Sector Crossing messages within a Sector after the event
occurs, three sigma.
[IRD0050] The Surveillance System shall transmit North Marker messages within a Sector after the event
occurs, three sigma.
[IRD0051] The Surveillance System shall output 32 Sector Crossing messages per antenna scan.
[IRD0052] The Surveillance System shall output a Sector Crossing message every 11.25˚ with Sector 0
occurring at True North.
[IRD0053] The Surveillance System Sector Crossing timestamp shall be the time at which the antenna has
crossed the azimuth defining the beginning of the sector.
[IRD0054] The Surveillance System shall output Weather Reports containing a full weather picture within
4 scans of completion of a weather integration cycle.
3.2.2.5 Quality of Service Requirements
The Quality of Service requirements, including accuracy, throughput, latency and availability requirements
are specified within the SIM fPRD.
3.2.2.6 Error Handling Requirements
As receiving systems could host an array of applications with different error handling needs, the following
represent requirements of the application error handling for processed Data Units.
[IRD0055] The ATC Automation System shall validate that the Data Source Identifier in each ASTERIX
Record matches the adapted Data Source Identifier for the Surveillance System.
[IRD0056] The ATC Automation System shall detect degradation in Surveillance Data latency using ASTERIX
Records that contain a valid Time of Day Data Item.
[IRD0057] The ATC Automation System shall discard duplicate packets detected using the Sequence
Number embedded in the Data Unit.
[IRD0058] The ATC Automation System shall report discontinuity in Sequence numbers in the monitoring
of the Surveillance Data not attributed to Surveillance System channel reconfiguration or ATC Automation
cold/warm starts.
Note: The Surveillance system does not need to synchronize Sequence Numbers between
channels. The Source IP address will be different between Surveillance System channels.
Discontinuity in sequence numbers can either be from missing or out of order packets.
Page 30 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
[IRD0059] The ATC Automation System shall validate ASTERIX Records using the CRC-32 embedded in the
Data Unit.
[IRD0060] The ATC Automation System shall validate ASTERIX Records using the Length contained in the
ASTERIX Data Block.
[IRD0061] The ATC Automation System shall validate the contents of the ‘Compulsory’ Data Item in an
ASTERIX Record.
[IRD0062] The ATC Automation System shall discard invalid ASTERIX Records.
[IRD0063] The ATC Automation System shall report discarded ASTERIX Records in the monitoring of the
Surveillance Data.
[IRD0064] The ATC Automation System shall process ASTERIX Records that contain ‘Not Used’ Data
Items.
3.2.2.7 Interface Summary Table
Table 3-1 in Section 3.2 summarizes the data flow between the Surveillance System and the ATC
Automation System.
3.2.3 Protocol Implementation
The NAS IP-Based network, also referred to as Communications System, consists of LAN/Wide Area
Network (WAN) connectivity to Surveillance Systems, Automation Systems, and M&C Systems and
provides IP Services per FAA-STD-039C standard titled: “National Airspace System (NAS) Open System
Architecture and Protocols.” The communications protocols allow computers from different vendors,
using different operating systems, to exchange data. This data transfer is accomplished over data
networks using various protocols. The complete set of protocols necessary for such communication is
referred to as a protocol suite. This IRD references requirements to the Open Systems Interconnection
(OSI) 7-layer model.
Page 31 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Figure 3-1 – OSI 7 Layer Model

3.2.3.1 Application Layer Service
An ASTERIX Record encodes the information of a single Radar Target, a single Radar Service Message, or
a group of Radar Weather Vectors. A unique SIC/SAC is assigned to each Surveillance System and is utilized
in all ASTERIX Records sent by the Surveillance System.
The ASTERIX Data Block supports the packing of multiple ASTERIX Records of the same type per ASTERIX
construction rules in the Eurocontrol document Part 1 All Purpose Structured EUROCONTROL Surveillance
Information Exchange (ASTERIX), EUROCONTROL-SPEC-0149, Edition 2.3 dated 11/12/2015. The Data
Unit will only contain one ASTERIX Data Block.
[IRD0065] The Surveillance System shall have a site adaptable SIC code.
[IRD0066] The Surveillance System shall have a site adaptable SAC code.
[IRD0067] The Surveillance System Time of Day for a Target Report shall be the time when the antenna is
pointed at the calculated target centroid azimuth.
[IRD0068] The Surveillance System Time of Day for a North Marker shall be the time that the boresight of
the antenna beam is pointed at True North.
[IRD0069] The Surveillance System Sector 0 Crossing message shall signal the time that the boresight of
the antenna beam is pointed at True North.
[IRD0070] The Surveillance System Time of Day for a Sector Crossing message shall be the time that the
boresight of the antenna beam crosses a sector boundary, every 11.25 degrees.
Page 32 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
[IRD0071] The Surveillance System Time of Day for a SOP Weather Report shall be the time that the
boresight of the antenna beam is pointed at True North at the start of the first scan of the weather
integration cycle.
[IRD0072] The Surveillance System Time of Day for a EOP Weather Reports shall be the time that the
boresight of the antenna beam is pointed at True North at the end of the last scan of the weather
integration cycle.
[IRD0073] The ATC Automation System shall be capable of parsing the entire ASTERIX Record which is
compliant with ASTERIX Category’s UAP.
[IRD0074] The ATC Automation System shall parse each Data Item indicated by the ASTERIX Category’s
UAP.
[IRD0075] The ATC Automation System shall be coded such that valid ASTERIX formatted messages will
not cause a fault in the automation system.
Note: This condition can occur if the radar software has been upgraded and the new software
reports a FRN that the UAP designates as 'not used' for that radar type.
[IRD0076] When recording Surveillance Data messages, the ATC Automation System shall record all Data
Items in the ASTERIX Record even if the Data Item is not used.
3.2.3.1.1 Presentation Layer
Each ASTERIX Data Block is preceded by a 2 byte unsigned sequence number and followed by a 4 byte
CRC-32 as illustrated in Figure 3-2. The sequence number is independently incremented for each port and
wraps to zero after counting to 65535.
Data Unit
(Presentation Layer)
Sequence Application Element

Number (one ASTERIX CRC-32
(2 bytes) Data Block) (4 bytes)
Transmission Order
Figure 3-2– Presentation Layer Data Unit

The Data Unit serves the following functions:
• Applies a unique number to each packet for determining if packets are lost between the
Surveillance System and ATC Automation System.
• Provides error detection of the application elements that may occur in transmission between the
Surveillance System and ATC Automation System.
[IRD0077] The Surveillance System shall encapsulate ASTERIX Data Blocks as shown in Figure 3-2.
[IRD0078] The Surveillance System shall send the same Data Unit to two separate LAN interfaces.
[IRD0079] The ATC Automation System shall monitor the availability of the two separate LAN interfaces
for each Surveillance System.
Page 33 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
3.2.3.1.1.1 Packet Sequence Number

[IRD0080] The Surveillance System shall maintain a 2-byte unsigned Sequence Number independently for
each Data Stream.
[IRD0081] The Surveillance System shall increment Sequence Numbers by 1 independently for each Data
Stream.
[IRD0082] The Surveillance System shall assign the Sequence Number for each Data Stream to the next
ASTERIX Data Block in line for transmission.
[IRD0083] The Surveillance System shall wrap the Sequence Number to 0 following Sequence Number
65535.
3.2.3.1.1.2 CRC-32
[IRD0084] The Surveillance System shall transmit a 4 byte CRC-32 with each ASTERIX Data Block as
illustrated in Figure 3-2.
[IRD0085] The Surveillance System shall compute the CRC-32 as outlined in the Surveillance to ATC
Automation System ASTERIX ICD Developed by the SIM Program, NAS-ICD-11013400.
[IRD0086] The ATC Automation System shall decode the CRC-32 as outlined in the Surveillance to ATC
Automation System ASTERIX ICD Developed by the SIM Program, NAS-ICD-11013400.
3.2.3.2 Transport Layer Services
[IRD0087] The Surveillance System shall send UDP multicast Data Units.
[IRD0088] The ATC Automation System shall receive multicast Data Units.
[IRD0089] The Surveillance M&C System shall utilize TCP/IP protocol.
[IRD0090] The Communications System shall implement all transport layer protocols in accordance with
IETF RFC 1122 and RFC 1123.
[IRD0091] The Communications System shall implement all network layer protocols in accordance with
IETF RFC 1122 and RFC 1123.
[IRD0092] The Surveillance System shall implement UDP for the transport layer in accordance with IETF
RFC 768 for ASTERIX Categories 048, 034 and 008.
[IRD0093] The Surveillance System shall support IP Version 4 as a configuration item for the network layer
in accordance with IETF RFC 791.
[IRD0094] The Communications System shall support IP Version 4 as a configuration item for the network
layer in accordance with IETF RFC 791.
[IRD0095] The ATC Automation System shall support IP Version 4 as a configuration item for the network
layer in accordance with IETF RFC 791.
The identified IP Version 6 requirements are applicable to new hardware added and the software for that
new hardware to the existing platforms as part of the SIM Program.
[IRD0096] The Surveillance System's hardware shall be IP Version 6 capable as a configuration item for
the network layer in accordance with IETF RFC 2460, as well as IETF RFC 2464, 4291, and 4443.
Page 34 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
[IRD0097] The Communication System's hardware shall be IP Version 6 capable as a configuration item
for the network layer in accordance with IETF RFC 2460, as well as IETF RFC 2464, 4291, and 4443.
[IRD0098] The ATC Automation System's hardware shall be IP Version 6 capable as a configuration item
for the network layer in accordance with IETF RFC 2460, as well as IETF RFC 2464, 4291, and 4443.
[IRD0099] The Surveillance System shall implement Address Resolution Protocol (ARP) in accordance with
IETF RFC 826.
[IRD0100] The Communications System shall implement Address Resolution Protocol (ARP) in accordance
with IETF RFC 826.
[IRD0101] The ATC Automation System shall implement Address Resolution Protocol (ARP) in accordance
with IETF RFC 826.
[IRD0102] The Communications System shall support IETF RFC 922, broadcasting internet datagrams.
[IRD0103] The Surveillance System shall support the Protocol Independent Multicast (PIM) – Sparse Mode
as defined in RFC 4601.
[IRD0104] The Communications System shall support the Protocol Independent Multicast (PIM) – Sparse
Mode as defined in RFC 4601.
[IRD0105] The ATC Automation System shall support the Protocol Independent Multicast (PIM) – Sparse
Mode as defined in RFC 4601.
[IRD0106] The Communications System shall support IETF RFC 950, internet standard subnetting
procedure.
[IRD0107] The Surveillance System shall implement transport layer protocol in accordance with FAA-STD-
39C and FAA-STD-042B with guidance of FAA-HDBK-004.
[IRD0108] The Communications System shall implement transport layer protocol in accordance with FAA-
STD-39C and FAA-STD-042B with guidance of FAA-HDBK-004.
[IRD0109] The ATC Automation System shall implement transport layer protocol in accordance with FAA-
STD-39C and FAA-STD-042B with guidance of FAA-HDBK-004.
[IRD0110] The ATC Automation System shall be capable of sending multicast join requests to the network
of the FTI Communications Service.
[IRD0111] The ATC Automation System shall be capable of receiving multicast data from the
Communications System MSP without issuing multicast join requests.
[IRD0112] The Surveillance System shall support IETF RFC 2236, Internet Group Management Protocol,
Version 2.
[IRD0113] The Communications System shall support IETF RFC 2236, Internet Group Management
Protocol, Version 2.
[IRD0114] The ATC Automation System shall support IETF RFC 2236, Internet Group Management
Protocol, Version 2.
[IRD0115] The Surveillance System shall support IETF RFC 4271, A Border Gateway Protocol 4 (BGP-4).
Page 35 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
[IRD0116] The Communications System shall support IETF RFC 4271, A Border Gateway Protocol 4 (BGP-
4).
[IRD0117] The ATC Automation System shall support IETF RFC 4271, A Border Gateway Protocol 4 (BGP-
4).
3.2.3.3 Naming and Addressing
The Surveillance Data listed in Table 3-1 will be provided across the FAA Communications Service. Figure
3-3 and Figure 3-4 illustrate the fully redundant interface between the Surveillance and ATC Automation
Systems.
Only one of the Surveillance System channels will be on-line at any given time and only the on-line channel
will transmit data. It will transmit UDP multicast data to both MSPs (Figure 3-3) or FTI SDPs (Figure 3-4)
using separate IP addresses but the same port numbers. Identical data will be received at each MSP or
FTI SDP at the ATC Automation System.
Surveillance System M&C data will be transmitted over the Communications System using TCP/IP
protocol. Each Platform will define this TCP/IP interface. Surveillance Systems can choose to use ASTERIX
Category 253 as well as specify the implementation for sending data over the redundant networks.
GPS Clock
ATC Facility ‘N’
Surveillance System ‘N’
Switch
Channel FTI SDP A FTI SDP A FTI SDP B

A IP/AX
MONITOR
and
CONTROL
(M&C)
Switch
Channel FTI SDP B

B IP/AX
MULTICAST MULTICAST
FTI OPIP Network FTI OPIP Network
Red Core Blue Core
GPS Clock
FTI SDP A FTI SDP B
AUTOMATION
MSP
MSP INPUT A
Switch
Channel IP/AX (router/mux/

(router/mux/ IP/AX IP/AX
modem)
A modem)
MONITOR
and
AUTOMATION
MONITOR
CONTROL AND SYSTEM
(M&C) CONTROL
(M&C)
Switch
Channel IP/AX MSP IP/AX AUTOMATION

(router/mux/ MSP
B INPUT B
modem) (router/mux/
modem)
IP/AX
ON-AIRPORT
COMMUNICATION
Surveillance System ‘1’ SYSTEM TRACON
Page 36 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Figure 3-3– Surveillance and Automation Interfaces (On-Airport)

Note: refer to Appendix B for any unique System configurations.
Surveillance System ‘N’ ATC Facility ‘N’

Switch
GPS Channel FTI SDP A IP/AX AUTOMATION

Clock A IP/AX FTI SDP A
INPUT A
MONITOR
and
CONTROL
(M&C) IP/AX AUTOMATION
FTI SDP B
INPUT B
Switch
Channel FTI SDP B

B IP/AX
MULTICAST MULTICAST
GPS
FTI OPIP FTI OPIP
Clock
Network Network
Surveillance ARTCC / TRACON / RAPCON
System ‘1’ Blue Core Red Core
FTI SDP A IP/AX AUTOMATION

Switch
Channel IP/AX FTI SDP A

(Automation) INPUT A
A (Radar)
MONITOR
MONITOR AND
and CONTROL
CONTROL (M&C)
(M&C)
FTI SDP B AUTOMATION

Switch
Channel FTI SDP B

(Automation)
IP/AX INPUT B
B (Radar)
IP/AX
AUTOMATION
OFF-AIRPORT SYSTEM
COMMUNICATION
SYSTEM
Figure 3-4 – Surveillance and Automation Interfaces (Off-Airport)

Note: refer to Appendix B for any unique system configurations.
[IRD0118] The Communications System shall provide dual redundant paths between each Surveillance
System and each ATC Automation System.
[IRD0119] The Communications System shall maintain physical diversity for the dual redundant paths
between each Surveillance System and each ATC Automation System for locations that have physical
diversity.
[IRD0120] The Surveillance System shall utilize unique IP addresses (includes source and multicast)
compliant with FAA JO 1370.117, NAS IP Addressing Policy.
[IRD0121] The ATC Automation System shall utilize unique IP addresses (includes source and multicast)
compliant with FAA JO 1370.117, NAS IP Addressing Policy.
[IRD0122] The Surveillance M&C System shall utilize a unique IP address compliant with FAA JO 1370.117,
NAS IP Addressing Policy.
Page 37 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
3.3 Physical Requirements / Characteristics

The physical requirements for the new hardware added to the existing platforms as part of the SIM
Program are described below.
3.3.1 Electrical Power and Electronic Characteristics
[IRD0123] Electrical connection requirements for the Ethernet interfaces shall be as specified in IEEE
802.3u.
3.3.1.1 Connectors
[IRD0124] The Ethernet LAN cables at the ATC Automation System Demarcation shall be terminated with
8 position, 8 contact modular connectors (8P8C aka RJ-45).
[IRD0125] The Ethernet LAN cables at the Surveillance System Demarcation shall be terminated with 8
position, 8 contact modular connectors (8P8C aka RJ-45).
[IRD0126] Ethernet LAN connectors shall be wired per TIA/EIA-568-C.
[IRD0127] Ethernet LAN cables shall be terminated with category 5e compliant terminations.
[IRD0128] The Surveillance System shall provide 2 Ethernet cables to connect to the Communications
System, one per FTI SDP or MSP.
[IRD0129] The Communications System at the Surveillance System shall provide 2 Ethernet sockets per
FTI SDP.
Note: This includes one connection for Surveillance Data and one for expansion.
[IRD0130] The Communications System at the Surveillance System shall provide 2 Ethernet sockets per
MSP.
Note: This includes one connection for Surveillance Data and one for expansion.
[IRD0131] The Communications System at the ATC Automation System facility shall provide 8 Ethernet
sockets per FTI SDP.
Note: This accounts for up to four on-airport MSP connections, one Surveillance M&C, up to two
ATC Automation System connections and one for expansion.
[IRD0132] The ATC Automation System shall provide a minimum of 2 Ethernet sockets to connect to the
FTI Communications SDPs, a minimum of one per FTI SDP.
[IRD0133] The ATC Automation System shall provide a minimum of 2 Ethernet sockets to connect each
on-airport Communication System’s MSPs, a minimum of one per MSP.
[IRD0134] The Communications System at the ATC Automation System shall provide 4 Ethernet sockets
per MSP.
[IRD0135] For ATC Automation Systems receiving Surveillance Data from on-airport Surveillance Systems,
the ATC Automation System shall be capable of interfacing with up to 3 on-airport Communications
Systems.
3.3.1.2 Wire/Cable
[IRD0136] All cables located in the plenum area shall be plenum rated.
Page 38 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
[IRD0137] The LAN cable provided to the Surveillance System and the ATC Automation System
demarcation shall be 8 wire, 4 pair, 100 ohm, 24 AWG, Unshielded Twisted Pair (UTP).
[IRD0138] All cabling shall be Cat 5e conforming to the specifications of IEEE-802.3u.
[IRD0139] Each individual LAN cable shall be less than or equal to 295 feet in length.
[IRD0140] The total length including any patch cords shall be less than or equal to 328 feet.
[IRD0141] If the Surveillance System and the ATC Automation System are directly connected (DTE to DTE),
then a cross over cable shall be required to connect the two.
[IRD0142] In the event a cross over cable is used, the wires shall be crossed at the RJ-45 connector nearest
the Surveillance System.
[IRD0143] Crossover cables shall be wired per TIA/EIA-568-C.
[IRD0144] Equipment cables shall be in accordance with NFPA 70, National Electric Code; FAA-C1217,
Electric Work, Interior standards; and FAA Order 6950.22, Maintenance of Electrical Power and Control
Cables.
3.3.1.3 Grounding
[IRD0145] The Surveillance System equipment shall adhere to FAA-STD-019E, Lightning and Surge
Protection, Grounding, Bonding and Shielding Requirements for Facilities and Equipment. (Note: only
applies to newly installed equipment as part of SIM program.)
[IRD0146] The Communication System’s equipment shall adhere to FAA-STD-019E, Lightning and Surge
[IRD0147] The ATC Automation System equipment shall adhere to FAA-STD-019E, Lightning and Surge
[IRD0148] The Surveillance System shall adhere to American National Standards Institute/Institute of
Electrical and Electronics Engineers (ANSI/IEEE) Standard 1100-2005, Recommended Practice for
Powering and Grounding Electrical Equipment. (Note: only applies to newly installed equipment as part
of SIM program.)
[IRD0149] The Communications System shall adhere to American National Standards Institute/Institute of
of SIM program.)
[IRD0150] The ATC Automation System shall adhere to American National Standards Institute/Institute of
of SIM program.)
3.3.1.4 Fasteners
[IRD0151] Fasteners shall be in accordance with FAA-G-2100H, Section 3.3.1.5.3.
Page 39 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
3.3.1.5 Electromagnetic Compatibility

[IRD0152] Electromagnetic emission and susceptibility of the equipment shall be in accordance with Code
of Federal Regulations Title 47 Part 15, for Class A digital devices for unintentional radiators.
Page 40 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
4 Quality Assurance Provisions

Developmental Test (DT) will be completed by the organization that is responsible for implementing the
modifications to support SIM in each system. The purpose of DT is to demonstrate that all interface
requirements have been met, and to verify that the system is fully integrated and stable and has no
adverse effect on the rest of the NAS.
Operational Test (OT) will be conducted by ANG-E55 with SLE assistance as needed. As all systems will
not be developed and ready for testing at the same time, multiple OT test events will be required. OT
will consist of End-to-End testing, from antenna to glass. Multiple automation / surveillance
configurations will be tested using live systems and simulated data at the William J. Hughes Technical
Center (Atlantic City), Mike Monroney Aeronautical Center (Oklahoma City), and selected field locations.
ANG-E55 will be responsible for developing a TEMP, OT Test Plan, OT Test Procedures, and an OT Test
Report.
Site Acceptance Test (SAT) will commence with the completion of the System Support Modification (SSM)
for both the Surveillance and ATC Automation Systems. The SIM Program Office will coordinate with the
affected SLE and Service Area Organizations to manage the solution implementation into the individual
sites. A SIM team will assist in conducting each SAT. The purpose of the SAT is to verify that the SIM
modification is correctly connected and functioning as a complete system design. The SAT includes quality
assurance, hardware inspection and conduct of SAT procedures.
4.1 Responsibility for Verification
[IRD0153] Each Systems Program Office shall be responsible for conducting DT for the verification of
interface requirements for each project.
The System Responsible Program Office may delegate verification activities to other FAA organizations,
independent contractors, and/or the major prime contractor.
[IRD0154] The FAA shall be responsible for conducting OT for the verification of interface requirements
for each project.
[IRD0155] The FAA Implementation Team shall be responsible for conducting SAT for the verification of
interface requirements for each deployment.
[IRD0156] The Surveillance Systems shall be responsible for implementing the verification of requirements
in accordance with Section 4.3.
[IRD0157] The Communication Systems shall be responsible for implementing the verification of
requirements in accordance with Section 4.3.
[IRD0158] The ATC Automation Systems shall be responsible for implementing the verification of
requirements in accordance with Section 4.3.
4.2 Special Verification Requirements
This Section is not applicable for this IRD.
4.3 Verification Requirements Traceability Matrix
Verification methods are: Analysis (A), Demonstration (D), Inspection (I), and Test (T), as defined below:
Page 41 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Analysis: This is a method in which hardware or software designs are compared with known scientific and
technical principles, procedures, and practices to estimate the capability of the proposed design to meet
the mission and system requirements.
Demonstration: This is a method in which qualitative 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.
Inspection: This method is used to determine compliance without using special laboratory equipment,
procedures, or services and consists of nondestructive static-state examination of hardware, software,
and/or technical data and documentation.
Test: This is a method in which performance is measured during or after the controlled application of
functional and/or environmental stimuli. Quantitative measurements are analyzed to determine the
degree of compliance. The process uses standardized laboratory equipment, procedures, and/or services.
Appendix C contains the VRTM which provides additional clarification on the verification methods, how
each requirement is to be verification and at what stage the verification will occur. Appendix D contains
a Requirement Applicability Matrix which allocates each requirement to each of the systems.
Page 42 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
5 Preparation for Delivery

This Section is not applicable for this IRD.
Page 43 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
6 Notes
6.1 Definitions
Term Definition
Access Control Lists A method to filter network traffic by controlling
whether routed packets are forwarded or blocked
at the router's interfaces.
ASTERIX Data Block Unit of information seen by the application as a
discrete entity by its contents. A Data Block
contains one or more Record(s) containing data of
the same Category.
ASTERIX Data Category Classification of the data in order to permit
interalia (among other things) an easy
identification.
ASTERIX Data Item The smallest unit of information in each Data
Category.
ASTERIX Record A collection of transmitted Data Fields of the same
Category preceded by a Field Specification field,
signaling the presence/absence of the various
Data Fields.
ATC Automation System (FAA and DoD) The system which receives and processes target
reports, service messages and/or weather from
the Surveillance system. This includes STARS,
ERAM, ATOP, MicroEARTS, ASDE-X, ASSC and SBS.
Communications System The system responsible for providing the interface
between the Surveillance and Automation
Systems. This includes both FTI Communications
Service and on-airport Communications System.
Compulsory The Surveillance System must provide unless
there is an exception noted in the Data Item
details. The ATC Automation System uses these
fields and must correctly record and parse them.
Compulsory when Available The Surveillance System must provide the Data
Item when data is available. The ATC Automation
System may or may not use these fields, but must
correctly record and parse them.
Data Field Physical implementation for the purpose of
communication of Data Item(s), it is associated
with a unique Field Reference Number. Ref.
EUROCONTROL Part 1, ASTERIX Section 3.1.4
Page 44 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Term Definition
Data Stream Specific sub-message types of ASTERIX data types.
Data Unit A Presentation Layer element that serves the
following functions:
• Delimit application elements or to
aggregate for transmission elements of
like type
• Identify application elements
• Provide error detection of the application
elements that may occur in transmission
between the Surveillance System and ATC
Automation
Field Reference Number (FRN) The number assigned Data Item that indicates an
items location in the UAP.
Field Specification (FSPEC) A table of contents, in the form of a bit sequence,
where every individual bit signals the presence (bit
set to one) or absence (bit set to zero) of a well-
defined Data Field assigned to it.
Local Geographical North The term “local geographical north” as used in the
ASTERIX EUROCONTROL documents is defined as
True North.
Not Used The Surveillance System cannot currently provide
the Data Item or will not provide. The ATC
Automation System does not use these fields, but
must correctly record and parse them. Receipt of
these fields does not make the ASTERIX Record
invalid.
Off-Airport Communications System Used by a Surveillance System that outputs
Surveillance Data to the FTI Communications
Service SDP for transmission across the FTI OPIP
network to remote facilities. ATC Automation
Systems receiving data from this configuration will
receive Surveillance Data from multiple
Surveillance Systems from a single set of FTI SDPs.
Page 45 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Term Definition
On-Airport Communications System Used by a Surveillance System that outputs
Surveillance Data to MSPs for transmission across
dedicated field cable. These communication
systems are located on or near the local airport.
The ATC Automation Systems receiving data from
this configuration will receive Surveillance Data
from Surveillance Systems via their own dedicated
MSPs. This is also applicable to the ASR-9
configuration where Surveillance Data is delivered
to ATC Automation Systems via (aggregated)
DRSRs as depicted in Appendix B. Note that
Surveillance Data provided to ATC Automation
Systems via an On-airport Communications
System will (in general) also be provided to the
Off-airport Communication System for delivery to
other (remote) facilities.
Optional The Surveillance System may be capable of
producing Data Item but controlled by the
Surveillance System's adaptation. When enabled,
the Surveillance System must provide the Data
Item when data is available. When disabled, the
Surveillance System does not provide the Data
Item. The ATC Automation System may or may not
use these fields, but must correctly record and
parse them.
Service Delivery Point (SDP) The point of demarcation between a Surveillance
or ATC Automation System and the OPIP Network.
It is also the delivery point for all FTI services at
that site.
Service message A message that conveys data describing the
current state of the originating system. May
include antenna position, system identification,
system equipment status, fault or error
conditions, etc.
Surveillance Data Data containing information comprising any
combination of surveillance targets, surveillance
system status, surveillance system control
commands, or any other data element that might
be transferred between equipment connected to
the NAS surveillance network.
Surveillance Data Latency The difference between time of receipt of the Data
Unit and Time of Day in the ASTERIX Record.
Page 46 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Term Definition
Surveillance System The system responsible for outputting target
reports, service messages and/or weather. This
includes ASR-8 (ATCBI-5/Mode S with CTD), ASR-9
(ATCBI-5/Mode S), ASR-11, ATCBI-6(M), CARSR,
Mode S En Route and WAM. The Monitor and
Control (M&C) for each system is part of the
Surveillance System.
Target Report A message that conveys information related to a
surveillance detection of an object, typically aloft
(e.g., a target report would indicate a radar has
detected an aircraft).
Time of Day Cat048
• Target - the time when the antenna is
pointed at the calculated centroid
azimuth
Cat034
• North Marker – Time that the boresight of
the antenna beam is pointed at True
North
• Sector Crossing – Time that the boresight
of the antenna beam is pointed for a
Sector crossing, every 11.25 degrees
Cat008
• SOP – Time that the boresight of the
antenna beam is pointed at True North in
the first scan of the weather capture
• EOP – Time that the boresight of the
antenna beam is pointed at True North at
the end of the last scan of the weather
capture
User Application Profile (UAP) The mechanism for assigning Data Items to Data
Fields, and containing all necessary information
which needs to be standardized for the successful
encoding and decoding of the messages.
Page 47 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
6.2 Abbreviations and Acronyms

ACAS Airborne Collision Avoidance System
ACL Access Control List
ADS-B Automatic Dependent Surveillance - Broadcast
ADS-R Automatic Dependent Surveillance – Rebroadcast
aka also known as
ANSI American National Standards Institute
ARP Address Resolution Protocol
ARSR Air Route Surveillance Radar
ARTCC Air Route Traffic Control Center
ASDE-X Airport Surface Detection Equipment Model X
ASR Airport Surveillance Radar
ASSC Airport Surface Surveillance Capability
ASTERIX All Purpose Structured EUROCONTROL Interface Exchange
ATC Air Traffic Control
ATCBI Air Traffic Control Beacon Interrogator
ATOP Advanced Technologies and Oceanic Procedures
AWG American Wire Gauge
AX ASTERIX
BGP-4 Border Gateway Protocol version 4
CARSR Common Air Route Surveillance Radar
Cat Category
CD Collision Detection
CD-2 Common Digitizer Model-2
CDRL Contract Data Requirements List
COM Communications
CPE Customer Premise Equipment
CRC Cyclic Redundancy Check
CSMA Carrier Sense Multiple Access
CTD Common Terminal Digitizer
DCE Data Communications Equipment
Page 48 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
DHS Department of Homeland Security

DoD Department of Defense
DRSR Digital Remote SCIP Replacement
DT Developmental Test
DTE Data Transmitting Equipment
EIA Electronic Industries Alliance
EOP End of Picture
ERAM En Route Automation Modernization
FAA Federal Aviation Administration
FIS-B Flight Information Services - Broadcast
fPRD Final Program Requirements Document
FRN Field Reference Number
FSPEC Field Specification
FTI FAA Telecommunications Infrastructure
FX Field Extension
GPS Global Positioning System
IBI Interim Beacon Initiative
ICAO International Civil Aviation Organization
ICD Interface Control Document
Internet Control Message Protocol for the Internet Protocol
ICMPv6 Version 6 Specification
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronic Engineers
IETF Internet Engineering Task Force
IP Internet Protocol
IPv4 Internet Protocol Version 4
IPv6 Internet Protocol Version 6
IRD Interface Requirements Document
ISO International Organization for Standardization
JO Job Order
LAN Local Area Network
Page 49 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
LEN Length
LSB Least Significant Bit
M&C Monitor and Control
MB Message, Comm B
MicroEARTS Micro-En Route Automated Radar Tracking System
Mode S Mode Select
MSP Multi-Service Platform
NAS National Airspace System
NASE National Airway Systems Engineering
Nbr Number
NEC National Electric Code
NextGen Next Generation
NFPA National Fire Protection Agency
NOGO No Go
OPIP Operations Internet Protocol
OSI Open System Interconnection
OT Operational Test
Para Paragraph
PIM Protocol Independent Multicast
PIM-SM Protocol Independent Multicast – Sparse Mode
PSR Primary Surveillance Radar
RAPCON Radar Approach Control
Ref Reference
RFC Request for Comment
RMMS Remote Monitoring Maintenance System
Rqt Requirement
RTQC Real Time Quality Control
SAC System Area Code
SAT Site Acceptance Testing
SBS Surveillance Broadcast Service
SCIP Surveillance Communication Interface Processor
Page 50 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
SDP Service Delivery Point

SIC System Identification Code
SIM Surveillance Interface Modernization
SLE Second Level Engineering
SLEP Service Life Extension Program
SOP Start of Picture
SOW Statement of Work
SPF Standard Precision Format
SSM System Support Modification
SSR Secondary Surveillance Radar
STARS Standard Terminal Automation Replacement
STD Standard
TCP Transmission Control Protocol
TEMP Test and Evaluation Master Plan
TIA Telecommunications Industry Association
TIS-B Traffic Information Services - Broadcast
TRACON Terminal Radar Approach Control
UAP User Application Profile
UDP User Data Protocol
UTC Coordinated Universal Time
UTP Unshielded Twisted Pair
VR Virtual Radar
WAM Wide Area Multilateration
WAN Wide Area Network
VRTM Verification Requirements Traceability Matrix
WJHTC William J Hughes Technical Center
Page 51 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Appendix A – General ASTERIX Message Formats

A.1 Message Structure
The ASTERIX Data Block contains the ASTERIX Data Category (Cat) and Length Indicator (LEN) fields and
one or more ASTERIX records (FSPEC and the specified Field Reference Numbers (FRN)) of the same Report
type (e.g., Radar Target Report).
A.1.1 General
The application data to be transferred consists of an ASTERIX Data Block which includes:
(1) A one-Byte field (Cat) indicating the Data Category for records in this Data Block
(2) A two-Byte field (LEN) indicating the total length (in Bytes) of the ASTERIX Data Block, including
this field, Data Category field, and all the Records.
(3) One or more Record(s) containing data of the same Data Category
Surveillance Systems will implement the packing of multiple ASTERIX Records in one ASTERIX Data Block
as long as:
• The size of the Data Unit (header included with Payload (ASTERIX Data Block)) doesn’t exceed the
maximum application layer size limit. The maximum application layer site limit is a site adaptable
parameter with a default setting of 512 bytes.
• The packing period ensures that the Surveillance System latency is met.
A depiction of the ASTERIX Data Block structure is provided in the Figure A-1. Each Record is of variable
length, but aligned on a Byte boundary.
Figure A-1 – ASTERIX Data Block Structure
Page 52 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
A.1.2 Data Field Formats

To achieve transmission efficiency, contents of the Data Blocks are packed efficiently. This is achieved by
sequencing of Data Fields within a Record. Ordered Field Sequencing is the standard method applied in
Record composition. This structure is defined as follows:
(1) The leading part of the Record is a variable length field FSPEC. The FSPEC is a table of contents in
the form of a bit sequence, where every individual bit signals the presence or absence of a well-
defined Data Field assigned to it.
(2) The FSPEC is immediately followed by a variable number of contiguous Data Fields in the order of
increasing FRN.
The relationship between the FSPEC bits, Data Fields and Data Items is established in the User Application
Profile (UAP).
The minimum length of the FSPEC is one Byte, which allows the composition of Records consisting of any
combination of Data Fields with FRNs from one up to and including seven. When Data Fields with FRNs
greater that seven have to be transmitted, the FSPEC extension mechanism is used. This is achieved by
assigning a special meaning to the Least Significant Bit (LSB) of the FSPEC Byte. The LSB, called the Field
Extension (FX) bit, when set to one, signals the continuation of the FSPEC field with at least one further
Byte, until finally a Byte is provided with the FX bit set to zero.
Page 53 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Appendix B – System Specific Architecture
Page 54 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
GPS Clock
Switch
Channel FTI SDP A FTI SDP A FTI SDP B
A IP/AX
MONITOR
and
CONTROL
(M&C)
Switch
Channel FTI SDP B
B IP/AX
MULTICAST MULTICAST
FTI OPIP Network FTI OPIP Network
Red Core Blue Core
GPS Clock
FTI SDP A FTI SDP B
ASR-9 Surveillance
System - Local
Internal IP/AX
Internal
ASR-9
ASR-9
DCE Format AUTOMATION
Format
Switch
Channel Network DCE IP/AX INPUT A

(on-airport Comm
A Extender Network
Extender
System)
MONITOR
and
MONITOR and
CONTROL
(M&C) CONTROL (M&C) DRSR
AUTOMATION
IP/AX INPUT B
Switch
Channel DCE
Network DCE
B Internal Internal Network
Extender
ASR-9 ASR-9 Extender
Format Format
SURVEILLANCE AUTOMATION
SYSTEM ASR-9 Remote SYSTEM
TRACON
Figure B-1 – ASR-9 On Airport Configuration
Page 55 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Surveillance System ‘N’ ATC Facility ‘N’
Switch
GPS Channel FTI SDP A
Clock A IP/AX IP/AX AUTOMATION
FTI SDP A
INPUT A
MONITOR
and
CONTROL
(M&C)
IP/AX AUTOMATION
FTI SDP B
Switch
Channel FTI SDP B INPUT B

B IP/AX
MULTICAST MULTICAST
GPS Clock
FTI OPIP FTI OPIP
Network Network
Blue Core Red Core TRACON
AUTOMATION SYSTEM
Internal
ASR-9
Format
Switch
CHANNEL FTI SDP A FTI SDP A AUTOMATION

A (Radar) (Automation) IP/ASTERIX INPUT A
Internal ASR-9
MONITOR
and Format MONITOR and
CONTROL CONTROL (M&C)
DRSR
(M&C)
Switch
CHANNEL FTI SDP B FTI SDP B AUTOMATION

B (Radar) (Automation) INPUT B
Internal IP/ASTERIX
ASR-9 Internal ASR-9
Format Format ASR-9
Surveillance
ASR-9 Surveillance FAA System - Remote
Telecommunications
System - Local Service
Figure B-2 – ASR-9 Off-Airport Configuration
Page 56 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
GPS Clock
Switch
Channel FTI SDP A
A IP/AX
Switch
Channel FTI SDP B
FTI SDP A FTI SDP B
B IP/AX
MULTICAST
FTI OPIP Network
SDP
ASR-9 A&B
Red Core
ARTCC/TRACON/RAPCON
ASR-9
SDP AUTOMATION
A&B FTI SDP A
INPUT A
MULTICAST
FTI OPIP Network AUTOMATION
SDP FTI SDP B
ASR-9 INPUT B
A&B
Blue Core
AUTOMATION
SYSTEM
SDP
ASR-9 A&B
SDP
A&B DRSR 1
SDP
A&B DRSR 2
SWITCH
SDP
ASR-9 A&B
SDP DRSR 3
IP/AX
A&B
Internal ASR-9 Format IP/AX
SDP DRSR 4
A&B
SDP DRSR 5
A&B
DCE On-Airport Communications System DCE

DRSR
ASR-9 Network Network
Extenders Internal ASR-9 Format Extenders
MULTIPLE (5) OFF-AIRPORT ASR-9

WITH ONE (1) ON-AIRPORT ASR-9
COMMUNICATION SYSTEM
Page 57 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Figure B-3 – ASR-9 Consolidated TRACON Configuration
Surveillance System ‘N’ ARTCC ‘N’
Switch
GPS Channel FTI SDP A IP/AX RFW A1
Clock A IP/AX FTI SDP A
IP/AX
RFW A2
MONITOR
and
RFW B1
CONTROL
(M&C)
IP/AX
FTI SDP B RFW B2
Switch
Channel FTI SDP B IP/AX

B IP/AX
MULTICAST MULTICAST
GPS
FTI OPIP FTI OPIP
Clock
Network Network
Surveillance ARTCC ‘1’
System ‘1’ Blue Core Red Core
ERAM Channel A
FTI SDP A
IP/AX
Switch
Channel IP/AX FTI SDP A (Automation) RFW A1

A (Radar)
IP/
AX RFW A2
MONITOR
MONITOR AND
and CONTROL
CONTROL (M&C)
(M&C)
AX RFW B1
IP/
Switch
Channel FTI SDP B RFW B2

B (Radar) FTI SDP B
IP/AX
IP/AX (Automation)
ERAM Channel B
AUTOMATION
FAA SYSTEM
Telecommunications
Service
Page 58 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Figure B-4 – ERAM Off-Airport Configuration
Page 59 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Appendix C – Verification Requirements Traceability Matrix

The following information pertaining to the VRTM is taken from the FAA/WJHTC Test and Evaluation
Handbook, Version 3.0.
Each program requirement contained in the VRTM is assigned one or more of the following test
verification method(s):
• Demonstration (D): Verification that is accomplished by operation, adjustment, or
reconfiguration of items performing their designed functions under specific scenarios. The items
may be instrumented and quantitative limits of performance monitored, but only observational
data rather than actual performance data is required to be recorded for verification.
Demonstration is often used to verify compliance with requirements in servicing, reliability,
maintainability, transportability, and human factors engineering.
• Test (T): Verification that is accomplished, with or without instrumentation, through systematic
exercising of the application item under appropriate conditions with the collection, analysis, and
evaluation of quantitative data.
• Analysis (A): Verification that is accomplished through use of one or more of the following
analysis techniques to prove that an item meets specified requirements:
a. Mathematical representation such as math models, algorithms, and equations
b. Charts
c. Graphs
d. Circuit diagrams
e. Data reduction/recording
f. Representative data (may include data collected from previous or other equipment and
system verifications)
• Inspection (I): Verification that is accomplished by a visual examination of the item, reviewing
descriptive documentation, and comparing the appropriate characteristics with predetermined
standards to determine conformance to requirements without the use of laboratory equipment
or procedures. Examples of verification by inspection are:
a. Visual analysis of the item under test, such as displays, cables, and processors.
b. Reviewing descriptive documentation such as Contract Data Requirements List (CDRL)
items, vendor data, and engineering drawings.
c. Comparing the appropriate characteristics with a predetermined or reference standard
such as FAA standards, other standards, and SOWs.
The VRTM that follows contains 3 test events:
• DT – Performed by 2nd Level Engineering.

• OT – ANG-E55
• SAT – Performed by Installation team and/or 2nd Level Engineering
Page 60 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

All Purpose Structured Eurocontrol Surveillance Information Exchange (ASTERIX)
Interface Requirements Document (IRD), Developed by Surveillance Interface Modernization (SIM) Program
NAS-IRD-11013400 Version -, May 22, 2017
IRD Rqt Verification Method

Shall Ref. Nbr. IRD Requirement Text
Para.
DT OT SAT
3.1 IRD0001 ASTERIX messages shall be in accordance with the EUROCONTROL T - _
Specification for Surveillance Data Exchange - Part 1 All Purpose Structured
EUROCONTROL Surveillance Information Exchange (ASTERIX), EUROCONTROL-
SPEC-0149, Edition 2.3 dated 11/12/2015.
3.1 IRD0002 Surveillance Target Reports shall be formatted as ASTERIX Cat048 Monoradar T - -
Target Reports in accordance with SUR.ET1.ST05.2000-STD-04-01, Edition
1.21, July 2012.
3.1 IRD0003 Service Messages shall be formatted as ASTERIX Cat034 Monoradar Service T - -
Messages in accordance with SUR.ET1.ST05.2000-STD-02b-01, Edition 1.27,
May 2007.
3.1 IRD0004 Weather Reports shall be formatted as ASTERIX Cat008 Monoradar Derived T - -
Weather Information in accordance with EUROCONTROL-SPEC-0149-3, Edition
1.2, 08/24/2014.
3.2.2.1 IRD0005 The Surveillance System's destination multicast address shall be site T I -
adaptable for each Data Stream in Table 3-2 on each redundant LAN interface.
3.2.2.1 IRD0006 The Surveillance System's transport layer port shall be site adaptable, see Table T I -
3-2.
3.2.2.1 IRD0007 The ATC Automation System's transport layer port shall be site adaptable, see T I -
Table 3-2.
Page 61 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.2.2 IRD0008 The FTI Communications Service shall own the CPE at the Surveillance Systems - I -
facility.
3.2.2.2 IRD0009 The FTI Communications Service shall own the CPE at the ATC Automation - I -
Systems facility.
3.2.2.2 IRD0010 The FTI Communications Service shall maintain the CPE at the Surveillance - I -
Systems facility.
3.2.2.2 IRD0011 The FTI Communications Service shall maintain the CPE at the ATC - I -
Automation Systems facility.
3.2.2.2 IRD0012 The Communications System shall only pass incoming data with approved T D D
source IP addresses, destination IP addresses, protocols and port numbers.
3.2.2.2 IRD0013 The Communications System shall log occurrences of unapproved source IP T D D
addresses, destination IP addresses, protocols and port numbers.
3.2.2.2 IRD0014 The Communications System shall block incoming Transmission Control T D D
Protocol (TCP) connection attempts from unapproved IP addresses and port
numbers.
3.2.2.2 IRD0015 The Communications System shall log incoming TCP connection attempts T D D
from unapproved IP addresses and port numbers.
Page 62 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.2.3 IRD0016 The Surveillance System shall generate an ASTERIX Data Block with a site T - -
adaptable maximum size up to 1494 bytes.
Note: The max packet size is 1500 bytes. This requirement is for the
Application Layer and the Presentation Layer adds 6 bytes for the Sequence
Number and CRC-32.
3.2.2.3 IRD0017 The Surveillance System shall default the ASTERIX Data Block maximum size to T - -
506 bytes.
3.2.2.3 IRD0018 The Surveillance System shall set all spare bits to zero in the ASTERIX Record. T T -
3.2.2.3 IRD0019 The Surveillance System shall determine the Data Item applicability for an T T -
ASTERIX Record as described in Table 3-3 through Table 3-9.
3.2.2.3 IRD0020 The Surveillance System shall populate Category 048 ASTERIX messages in T T -
accordance with Table 3-3.
accordance with Table 3-4 through Table 3-6.
3.2.2.3 IRD0023 The ATC Automation System shall receive the Category 048 ASTERIX messages T T -
in accordance with Table 3-3.
in accordance with Table 3-4 through Table 3-6.
Page 63 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
in accordance with Table 3-7 through Table 3-9.
3.2.2.3 IRD0026 The Surveillance System shall transmit ‘compulsory’ Data Items in every T T -
ASTERIX Record, except where noted in the Surveillance to ATC Automation
System ASTERIX ICD Developed by the SIM Program, NAS-ICD-11013400.
3.2.2.3 IRD0027 The Surveillance System shall transmit ‘compulsory if available’ Data Items in T - -
an ASTERIX Record when data is available for transmission.
3.2.2.3 IRD0028 The Surveillance System shall be adaptable for transmission of each ‘optional’ T - -
Data Items in an ASTERIX Record.
3.2.2.3 IRD0029 The Surveillance System shall be adaptable for transmission of each subfield in T - -
the Special Purpose Field of the Category 048 ASTERIX message.
3.2.2.3 IRD0030 The Surveillance System shall be adaptable for transmission of each subfield in T - -
the Special Purpose Field of the Category 034 ASTERIX message.
3.2.2.3 IRD0031 The Surveillance System shall default ‘optional’ Data Items to disabled, except T - -
where noted in the Surveillance to ATC Automation System ASTERIX ICD
Developed by the SIM Program, NAS-ICD-11013400.
3.2.2.3 IRD0032 The Surveillance System shall exclude ‘not used’ Data Items from an ASTERIX T - -
Record.
Page 64 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.2.3 IRD0033 The Surveillance System shall use True North as Local Geographical North for T - D
all Surveillance Data using an azimuth reference.
3.2.2.3 IRD0034 If available, the Surveillance System shall populate I034/050 COM Subfield Bit T - -
8 (NOGO) based on the overall system summary state (i.e. radar released to
maintenance).
3.2.2.3 IRD0035 If available, the Surveillance System shall populate I034/SP Summary Fault field T - -
based on the overall system summary status.
3.2.2.3 IRD0036 The Surveillance System shall transmit I034/120 (3D_Position of Data Source) T - -
with North Marker Service Messages at Surveillance System startup and every
UTC half hour in accordance with Table 3-4 through Table 3-6.
3.2.2.3 IRD0037 The Surveillance System shall populate I034/120 (3D_Position of Data Source) T - -
with the surveyed position of the radar at the height of the beacon antenna in
3.2.2.3 IRD0038 The Surveillance System shall transmit I034/050 (System Configuration and T - -
Status) with Sector 0 or the sector after a change in accordance with Table 3-4
through Table 3-6.
3.2.2.3 IRD0039 The Surveillance System shall transmit I034/060 (System Processing Mode) T - -
with Sector 0 or the sector after a change in accordance with Table 3-4
through Table 3-6.
Page 65 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.2.3 IRD0040 The Surveillance System shall limit I008/120 Total Number of Items T - -
Constituting One Weather Picture to a maximum of 4000 Vectors.
3.2.2.3 IRD0041 The Surveillance System shall format M&C messages as ASTERIX Cat253 Radar T - -
Station Monitor and Control Information, in accordance with the
EUROCONTROL ASTERIX Category 253 Specification, Issue 8.0, December
2014, or existing protocol over TCP/IP.
3.2.2.3 IRD0042 The Surveillance System M&C messages maximum packet size shall be 1500 T - -
bytes.
3.2.2.3 IRD0043 The Surveillance System shall prioritize the order of message transmission T T -
using the following prioritization:
1. Cat034 Service Messages
2. Cat048 Target Reports
3. Cat008 Weather Reports
4. M&C Messages
3.2.2.3 IRD0044 The ATC Automation System shall parse all Data Items identified in the Field T D -
Specification (FSPEC) of each ASTERIX Record which is compliant with ASTERIX
Category’s UAP.
3.2.2.4 IRD0045 The Surveillance System shall package Cat048 ASTERIX Records of the same T D -
Data Stream as identified in Table 3-2 into the same IP packet.
Page 66 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.2.4 IRD0046 The Surveillance System shall package Cat008 ASTERIX Records into the same T D -
IP packet.
3.2.2.4 IRD0047 The Surveillance System shall include a single Cat034 ASTERIX Record per IP T D -
packet.
3.2.2.4 IRD0048 The Surveillance System ASTERIX Data Block packing period shall ensure that T D -
the Surveillance System latency is met.
3.2.2.4 IRD0049 The Surveillance System shall transmit Sector Crossing messages within a T D -
Sector after the event occurs, three sigma.
3.2.2.4 IRD0050 The Surveillance System shall transmit North Marker messages within a Sector T D -
after the event occurs, three sigma.
3.2.2.4 IRD0051 The Surveillance System shall output 32 Sector Crossing messages per T T -
antenna scan.
3.2.2.4 IRD0052 The Surveillance System shall output a Sector Crossing message every 11.25˚ T T -
with Sector 0 occurring at True North.
3.2.2.4 IRD0053 The Surveillance System Sector Crossing timestamp shall be the time at which T T -
the antenna has crossed the azimuth defining the beginning of the sector.
3.2.2.4 IRD0054 The Surveillance System shall output Weather Reports containing a full T T -
weather picture within 4 scans of completion of a weather integration cycle.
Page 67 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.2.6 IRD0055 The ATC Automation System shall validate that the Data Source Identifier in T T -
each ASTERIX Record matches the adapted Data Source Identifier for the
Surveillance System.
3.2.2.6 IRD0056 The ATC Automation System shall detect degradation in Surveillance Data T T -
latency using ASTERIX Records that contain a valid Time of Day Data Item.
3.2.2.6 IRD0057 The ATC Automation System shall discard duplicate packets detected using T T -
the Sequence Number embedded in the Data Unit.
3.2.2.6 IRD0058 The ATC Automation System shall report discontinuity in Sequence numbers in T T -
the monitoring of the Surveillance Data not attributed to Surveillance System
channel reconfiguration or ATC Automation cold/warm starts.
Note: The Surveillance system does not need to synchronize Sequence
Numbers between channels. The Source IP address will be different between
Surveillance System channels. Discontinuity in sequence numbers can either
be from missing or out of order packets.
3.2.2.6 IRD0059 The ATC Automation System shall validate ASTERIX Records using the CRC-32 T - -
embedded in the Data Unit.
3.2.2.6 IRD0060 The ATC Automation System shall validate ASTERIX Records using the Length T - -
contained in the ASTERIX Data Block.
3.2.2.6 IRD0061 The ATC Automation System shall validate the contents of the ‘Compulsory’ T - -
Data Item in an ASTERIX Record.
3.2.2.6 IRD0062 The ATC Automation System shall discard invalid ASTERIX Records. T D -
Page 68 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.2.6 IRD0063 The ATC Automation System shall report discarded ASTERIX Records in the T D -
monitoring of the Surveillance Data.
3.2.2.6 IRD0064 The ATC Automation System shall process ASTERIX Records that contain ‘Not T D -
Used’ Data Items.
3.2.3.1 IRD0065 The Surveillance System shall have a site adaptable SIC code. T - -
3.2.3.1 IRD0066 The Surveillance System shall have a site adaptable SAC code. T - -
3.2.3.1 IRD0067 The Surveillance System Time of Day for a Target Report shall be the time T T -
when the antenna is pointed at the calculated target centroid azimuth.
3.2.3.1 IRD0068 The Surveillance System Time of Day for a North Marker shall be the time that T T -
the boresight of the antenna beam is pointed at True North.
3.2.3.1 IRD0069 The Surveillance System Sector 0 Crossing message shall signal the time that T T -
the boresight of the antenna beam is pointed at True North.
3.2.3.1 IRD0070 The Surveillance System Time of Day for a Sector Crossing message shall be T T -
the time that the boresight of the antenna beam crosses a sector boundary,
every 11.25 degrees.
3.2.3.1 IRD0071 The Surveillance System Time of Day for a SOP Weather Report shall be the T D -
time that the boresight of the antenna beam is pointed at True North at the
start of the first scan of the weather integration cycle.
Page 69 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.3.1 IRD0072 The Surveillance System Time of Day for a EOP Weather Reports shall be the T D -
time that the boresight of the antenna beam is pointed at True North at the
end of the last scan of the weather integration cycle.
3.2.3.1 IRD0073 The ATC Automation System shall be capable of parsing the entire ASTERIX T D -
Record which is compliant with ASTERIX Category’s UAP.
3.2.3.1 IRD0074 The ATC Automation System shall parse each Data Item indicated by the T D -
ASTERIX Category’s UAP.
3.2.3.1 IRD0075 The ATC Automation System shall be coded such that valid ASTERIX formatted T - -
messages will not cause a fault in the automation system. Note: This
condition can occur if the radar software has been upgraded and the new
software reports a FRN that the UAP designates as 'not used' for that radar
type.
3.2.3.1 IRD0076 When recording Surveillance Data messages, the ATC Automation System T D -
shall record all Data Items in the ASTERIX Record even if the Data Item is not
used.
3.2.3.1.1 IRD0077 The Surveillance System shall encapsulate ASTERIX Data Blocks as shown in T - -
Figure 3-2.
3.2.3.1.1 IRD0078 The Surveillance System shall send the same Data Unit to two separate LAN T - -
interfaces.
3.2.3.1.1 IRD0079 The ATC Automation System shall monitor the availability of the two separate T - -
LAN interfaces for each Surveillance System.
Page 70 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.3.1.1.1 IRD0080 The Surveillance System shall maintain a 2-byte unsigned Sequence Number T - -
independently for each Data Stream.
3.2.3.1.1.1 IRD0081 The Surveillance System shall increment Sequence Numbers by 1 T - -
independently for each Data Stream.
3.2.3.1.1.1 IRD0082 The Surveillance System shall assign the Sequence Number for each Data T - -
Stream to the next ASTERIX Data Block in line for transmission.
3.2.3.1.1.1 IRD0083 The Surveillance System shall wrap the Sequence Number to 0 following T - -
Sequence Number 65535.
3.2.3.1.1.2 IRD0084 The Surveillance System shall transmit a 4 byte CRC-32 with each ASTERIX T - -
Data Block as illustrated in Figure 3-2.
3.2.3.1.1.2 IRD0085 The Surveillance System shall compute the CRC-32 as outlined in the T - -
Surveillance to ATC Automation System ASTERIX ICD Developed by the SIM
Program, NAS-ICD-11013400.
3.2.3.1.1.2 IRD0086 The ATC Automation System shall decode the CRC-32 as outlined in the T - -
Surveillance to ATC Automation System ASTERIX ICD Developed by the SIM
Program, NAS-ICD-11013400.
3.2.3.2 IRD0087 The Surveillance System shall send UDP multicast Data Units. T - -
3.2.3.2 IRD0088 The ATC Automation System shall receive multicast Data Units. T - -
3.2.3.2 IRD0089 The Surveillance M&C System shall utilize TCP/IP protocol. I I -
Page 71 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.3.2 IRD0090 The Communications System shall implement all transport layer protocols in I - -
accordance with IETF RFC 1122 and RFC 1123.
3.2.3.2 IRD0091 The Communications System shall implement all network layer protocols in I - -
accordance with IETF RFC 1122 and RFC 1123.
3.2.3.2 IRD0092 The Surveillance System shall implement UDP for the transport layer in I - -
accordance with IETF RFC 768 for ASTERIX Categories 048, 034 and 008.
3.2.3.2 IRD0093 The Surveillance System shall support IP Version 4 as a configuration item for I - -
the network layer in accordance with IETF RFC 791.
3.2.3.2 IRD0094 The Communications System shall support IP Version 4 as a configuration item I - -
for the network layer in accordance with IETF RFC 791.
3.2.3.2 IRD0095 The ATC Automation System shall support IP Version 4 as a configuration item I - -
for the network layer in accordance with IETF RFC 791.
3.2.3.2 IRD0096 The Surveillance System's hardware shall be IP Version 6 capable as a I - -
configuration item for the network layer in accordance with IETF RFC 2460, as
well as IETF RFC 2464, 4291, and 4443.
3.2.3.2 IRD0097 The Communication System's hardware shall be IP Version 6 capable as a I - -
Page 72 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.3.2 IRD0098 The ATC Automation System's hardware shall be IP Version 6 capable as a I - -
3.2.3.2 IRD0099 The Surveillance System shall implement Address Resolution Protocol (ARP) in T - -
accordance with IETF RFC 826.
3.2.3.2 IRD0100 The Communications System shall implement Address Resolution Protocol T - -
(ARP) in accordance with IETF RFC 826.
3.2.3.2 IRD0101 The ATC Automation System shall implement Address Resolution Protocol T - -
(ARP) in accordance with IETF RFC 826.
3.2.3.2 IRD0102 The Communications System shall support IETF RFC 922, broadcasting I - -
internet datagrams.
3.2.3.2 IRD0103 The Surveillance System shall support the Protocol Independent Multicast I - -
(PIM) – Sparse Mode as defined in RFC 4601.
3.2.3.2 IRD0104 The Communications System shall support the Protocol Independent I - -
Multicast (PIM) – Sparse Mode as defined in RFC 4601.
3.2.3.2 IRD0105 The ATC Automation System shall support the Protocol Independent Multicast I - -
(PIM) – Sparse Mode as defined in RFC 4601.
3.2.3.2 IRD0106 The Communications System shall support IETF RFC 950, internet standard I - -
subnetting procedure.
Page 73 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.3.2 IRD0107 The Surveillance System shall implement transport layer protocol in I - -
accordance with FAA-STD-39C and FAA-STD-042B with guidance of FAA-HDBK-
004.
3.2.3.2 IRD0108 The Communications System shall implement transport layer protocol in I - -
004.
3.2.3.2 IRD0109 The ATC Automation System shall implement transport layer protocol in T - -
004.
3.2.3.2 IRD0110 The ATC Automation System shall be capable of sending multicast join T D D
requests to the network of the FTI Communications Service.
3.2.3.2 IRD0111 The ATC Automation System shall be capable of receiving multicast data from T D D
the Communications System MSP without issuing multicast join requests.
3.2.3.2 IRD0112 The Surveillance System shall support IETF RFC 2236, Internet Group I - -
Management Protocol, Version 2.
3.2.3.2 IRD0113 The Communications System shall support IETF RFC 2236, Internet Group I - -
3.2.3.2 IRD0114 The ATC Automation System shall support IETF RFC 2236, Internet Group I - -
3.2.3.2 IRD0115 The Surveillance System shall support IETF RFC 4271, A Border Gateway I - -
Protocol 4 (BGP-4).
Page 74 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.2.3.2 IRD0116 The Communications System shall support IETF RFC 4271, A Border Gateway I - -
Protocol 4 (BGP-4).
3.2.3.2 IRD0117 The ATC Automation System shall support IETF RFC 4271, A Border Gateway I - -
Protocol 4 (BGP-4).
3.2.3.3 IRD0118 The Communications System shall provide dual redundant paths between I - -
each Surveillance System and each ATC Automation System.
3.2.3.3 IRD0119 The Communications System shall maintain physical diversity for the dual I - -
redundant paths between each Surveillance System and each ATC Automation
System for locations that have physical diversity.
3.2.3.3 IRD0120 The Surveillance System shall utilize unique IP addresses (includes source and I - -
multicast) compliant with FAA JO 1370.117, NAS IP Addressing Policy.
3.2.3.3 IRD0121 The ATC Automation System shall utilize unique IP addresses (includes source I - -
and multicast) compliant with FAA JO 1370.117, NAS IP Addressing Policy.
3.2.3.3 IRD0122 The Surveillance M&C System shall utilize a unique IP address compliant with I - -
FAA JO 1370.117, NAS IP Addressing Policy.
3.3.1 IRD0123 Electrical connection requirements for the Ethernet interfaces shall be as I - -
specified in IEEE 802.3u.
3.3.1.1 IRD0124 The Ethernet LAN cables at the ATC Automation System Demarcation shall be I - I
terminated with 8 position, 8 contact modular connectors (8P8C aka RJ-45).
Page 75 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.3.1.1 IRD0125 The Ethernet LAN cables at the Surveillance System Demarcation shall be I - I
terminated with 8 position, 8 contact modular connectors (8P8C aka RJ-45).
3.3.1.1 IRD0126 Ethernet LAN connectors shall be wired per TIA/EIA-568-C. I - I
3.3.1.1 IRD0127 Ethernet LAN cables shall be terminated with category 5e compliant I - I
terminations.
3.3.1.1 IRD0128 The Surveillance System shall provide 2 Ethernet cables to connect to the I - I
Communications System, one per FTI SDP or MSP.
3.3.1.1 IRD0129 The Communications System at the Surveillance System shall provide 2 I - I
Ethernet sockets per FTI SDP.
Note: This includes one connection for Surveillance Data and one for
expansion.
3.3.1.1 IRD0130 The Communications System at the Surveillance System shall provide 2 I - I
Ethernet sockets per MSP.
Note: This includes one connection for Surveillance Data and one for
expansion.
3.3.1.1 IRD0131 The Communications System at the ATC Automation System facility shall I - I
provide 8 Ethernet sockets per FTI SDP.
Note: This accounts for up to four on-airport MSP connections, one
Surveillance M&C, up to two ATC Automation System connections and one for
expansion.
Page 76 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.3.1.1 IRD0132 The ATC Automation System shall provide a minimum of 2 Ethernet sockets to I - I
connect to the FTI Communications SDPs, a minimum of one per FTI SDP.
3.3.1.1 IRD0133 The ATC Automation System shall provide a minimum of 2 Ethernet sockets to I - I
connect each on-airport Communication System’s MSPs, a minimum of one
per MSP.
3.3.1.1 IRD0134 The Communications System at the ATC Automation System shall provide 4 I - I
Ethernet sockets per MSP.
3.3.1.1 IRD0135 For ATC Automation Systems receiving Surveillance Data from on-airport I - I
Surveillance Systems, the ATC Automation System shall be capable of
interfacing with up to 3 on-airport Communications Systems.
3.3.1.2 IRD0136 All cables located in the plenum area shall be plenum rated. I - I
3.3.1.2 IRD0137 The LAN cable provided to the Surveillance System and the ATC Automation I - I
System demarcation shall be 8 wire, 4 pair, 100 ohm, 24 AWG, Unshielded
Twisted Pair (UTP).
3.3.1.2 IRD0138 All cabling shall be Cat 5e conforming to the specifications of IEEE-802.3u. I - I
3.3.1.2 IRD0139 Each individual LAN cable shall be less than or equal to 295 feet in length. I - I
3.3.1.2 IRD0140 The total length including any patch cords shall be less than or equal to 328 I - I
feet.
3.3.1.2 IRD0141 If the Surveillance System and the ATC Automation System are directly I - I
connected (DTE to DTE), then a cross over cable shall be required to connect
the two.
Page 77 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.3.1.2 IRD0142 In the event a cross over cable is used, the wires shall be crossed at the RJ-45 I - I
connector nearest the Surveillance System.
3.3.1.2 IRD0143 Crossover cables shall be wired per TIA/EIA-568-C. I - I
3.3.1.2 IRD0144 Equipment cables shall be in accordance with NFPA 70, National Electric Code; I - I
FAA-C1217, Electric Work, Interior standards; and FAA Order 6950.22,
Maintenance of Electrical Power and Control Cables.
3.3.1.3 IRD0145 The Surveillance System equipment shall adhere to FAA-STD-019E, Lightning I - I
and Surge Protection, Grounding, Bonding and Shielding Requirements for
Facilities and Equipment. (Note: only applies to newly installed equipment as
part of SIM program.)
3.3.1.3 IRD0146 The Communication System’s equipment shall adhere to FAA-STD-019E, I - I
Lightning and Surge Protection, Grounding, Bonding and Shielding
Requirements for Facilities and Equipment. (Note: only applies to newly
installed equipment as part of SIM program.)
3.3.1.3 IRD0147 The ATC Automation System equipment shall adhere to FAA-STD-019E, I - I
Lightning and Surge Protection, Grounding, Bonding and Shielding
Requirements for Facilities and Equipment. (Note: only applies to newly
installed equipment as part of SIM program.)
Page 78 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
3.3.1.3 IRD0148 The Surveillance System shall adhere to American National Standards I - I
Institute/Institute of Electrical and Electronics Engineers (ANSI/IEEE) Standard
1100-2005, Recommended Practice for Powering and Grounding Electrical
Equipment. (Note: only applies to newly installed equipment as part of SIM
program.)
3.3.1.3 IRD0149 The Communications System shall adhere to American National Standards I - I
program.)
3.3.1.3 IRD0150 The ATC Automation System shall adhere to American National Standards I - I
program.)
3.3.1.4 IRD0151 Fasteners shall be in accordance with FAA-G-2100H, Section 3.3.1.5.3. I - I
3.3.1.5 IRD0152 Electromagnetic emission and susceptibility of the equipment shall be in I - I
accordance with Code of Federal Regulations Title 47 Part 15, for Class A
digital devices for unintentional radiators.
4.1 IRD0153 Each Systems Program Office shall be responsible for conducting DT for the I - -
verification of interface requirements for each project..
Page 79 of 93
NAS-IRD-11013400
Revision -
May 22, 2017


Para.
DT OT SAT
4.1 IRD0154 The FAA shall be responsible for conducting OT for the verification of interface - I -
requirements for each project.
4.1 IRD0155 The FAA Implementation Team shall be responsible for conducting SAT for the - - I
verification of interface requirements for each deployment.
4.1 IRD0156 The Surveillance Systems shall be responsible for implementing the I I -
verification of requirements in accordance with Section 4.3.
4.1 IRD0157 The Communication Systems shall be responsible for implementing the I I -
4.1 IRD0158 The ATC Automation Systems shall be responsible for implementing the I I -
Page 80 of 93
NAS-IRD-11013400
Revision -
May 22, 2017
Appendix D – Verification Requirements System Applicability Matrix

Shall Ref Surveillance Automation Communication
Nbr
ASR-8 ASR-9 ASR-11 ARSR-4 CARSR ACTBI-6 WAM Mode S STARS ERAM MicroEARTS ATOP ASDE-X ASSC SBS FTI Comm On-Airport
w/ Service Comm
CTD System
IRD0001 X X X X X X X X X X X X X X X
IRD0004 X X X X X X* X* X* X X X X
IRD0005 X X X X X X X X
IRD0007 X X X X X X X
IRD0008 X
IRD0009 X
IRD0010 X
IRD0011 X
IRD0012 X X
Page 81 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
IRD0013 X X
IRD0014 X X
IRD0015 X X
IRD0022 X X X X X X* X* X*
IRD0025 X X X X
Page 82 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
Page 83 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
Page 84 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
Page 85 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
Page 86 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
IRD0090 X X
Page 87 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
IRD0091 X X
IRD0094 X X
IRD0097 X X
IRD0100 X X
IRD0102 X X
Page 88 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
IRD0104 X X
IRD0106 X X
IRD0108 X X
IRD0113 X X
IRD0116 X X
Page 89 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
IRD0118 X X
IRD0119 X X
IRD0123 X X X X X X X X X X X X X X X X X
IRD0129 X
Page 90 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
IRD0130 X
IRD0131 X
IRD0134 X
Page 91 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
IRD0146 X X
IRD0149 X
IRD0154
IRD0155
Page 92 of 93
NAS-IRD-11013400
Revision -
May 22, 2017

Nbr
w/ Service Comm
CTD System
IRD0157 X X
* - These requirements are only applicable to these systems when they are the dissemination point.
IRD0154 and IRD0155 are not allocated to any of the Systems, but the responsibility of the SIM Program Office.
Page 93 of 93

Nas Ird 11013400

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nas Ird 11013400

Uploaded by

Copyright:

Available Formats

NAS-IRD-11013400

Surveillance to ATC Automation System

May 22, 2017

Federal Aviation Administration

600 Independence Avenue, SW

Washington, D.C. 20591

Interface Requirements Document (IRD)

Malcolm Andrews AJM-31,

REVISION DESCRIPTION DATE ENTERED BY

- Baseline release 05-22-17 P. Kilfoile

1.1 Summary ....................................................................................................................................... 2

2.1 Government Documents............................................................................................................... 5

3.1 General Requirements .................................................................................................................. 9

4.1 Responsibility for Verification ..................................................................................................... 41

6.1 Definitions ................................................................................................................................... 44

Appendix A – General ASTERIX Message Formats ...................................................................................... 52

A.1 Message Structure ............................................................................................................................ 52

Appendix C – Verification Requirements Traceability Matrix..................................................................... 60

Appendix D – Verification Requirements System Applicability Matrix....................................................... 81

Figure 1-1 – SIM Multicast Architecture

• In this document, “shall” indicates a mandatory requirement.

1.2 Subsystem Responsibility List

2.1 Government Documents

Ref No Number Description

2.2 Non-Government Documents

8 IEEE 802.3 CSMA/CD Access Method (Ethernet), December 26, 2008

9 IETF RFC-768 User Datagram Protocol

10 IETF RFC-791 Internet Protocol Version 4 (IPv4) Specification

11 IETF RFC-826 Ethernet Address Resolution Protocol

12 IETF RFC-922 Broadcasting Internet Datagrams in the Presence of Subnets

Ref No Name/Number Description

14 IETF RFC-1122 Requirements for Internet Hosts - Communication Layers

15 IETF RFC-1123 Requirements for Internet Hosts - Application and Support

16 IETF RFC-2236 Internet Group Management Protocol, Version 2

17 IETF RFC-2460 Internet Protocol Version 6 (IPv6) Specification

18 IETF RFC-2464 Transmission of IPv6 Packets over Ethernet Networks

19 IETF RFC-4271 A Border Gateway Protocol 4 (BGP-4)

20 IETF RFC-4291 IPv6 Addressing Architecture

23 NEC NFPA 70 National Electrical Code and Handbook

24 Commercial Building Cabling for Telecommunication

2.3 Document Sources

Source System Data Category Destination

Surveillance Weather ASTERIX 008 ATC Automation

Surveillance Status/Control ASTERIX/IP 253 or existing M&C

Table 3-2 – Data Streams

3.2.2.2 Application Process Capability Requirements

3 I048/020 Target Report Descriptor C C C C C C C C C C C C C

4 I048/040 Measured Position in C C C C C C C C C C C C C

9 I048/240 Aircraft Identification X X X X X X O O X O X X X

10 I048/250 Mode-S MB Data X X X X X X O O X X X X X

FRN Data Item Description Criteria for Inclusion:

12 I048/042 Calculated Position in X X X X X X X X X X X X X

15 I048/210 Track Quality X X X O X X X X O X O O O

21 I048/230 Communications/ ACAS X X X X X X O O X O X X X

FRN Data Item Description Criteria for Inclusion:

28 I048/RE Reserved Expansion X X X X X X X X X X X X X

FRN Data Item Description Criteria for Inclusion:

Table 3-5 – Cat034 North Marker UAP

FRN Data Item Description Criteria for Inclusion:

Table 3-6 – Cat034 Jamming Strobe UAP

FRN Data Item Description Criteria for Inclusion:

Table 3-8 – Cat008 Sequence of Polar Vectors UAP