Radar Vectors
FAA Order Cancelled Issued Nov 20, 1999 AJW-162 126 pages Copy saved Nov 18, 2026

Order 6040.15D National Airspace Performance Reporting System

This document is cancelled. It may have been replaced. Check the official source before relying on it.

Official source ↗ Open PDF

Text read by OCR from a scanned file. Check the original, as some words may be misread.

ORDER 6040.15D

ORDER 6040.15D

Includes Change 1 March 28, 2003

NATIONAL AIRSPACE PERFORMANCE REPORTING SYSTEM

March 28, 2003

U.S. DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION

Distribution: A-W(AF/AT/FS/AS)-2; A-X(AF/AT/FS/AS)-3; A-Y(DE/AY)-1; A-Z(ATC-200/300)-2; A-FAT/FAF-0(STD) Initiated By: AOP-200

RECORD OF CHANGES

RECORD OF CHANGES

DIRECTIVE NO.

CHANGE

CHANGE

6040.15D

Includes Change 1 March 28, 2003

SUPPLEMENTS

SUPPLEMENTS TO OPTIONAL BASIC

FAA FORM 1320-5 (6-80) USE PREVIOUS EDITION

TO BASIC

OPTIONAL

11/20/99 6040.15D

FOREWARD

The National Airspace System (NAS) is an intricate system which includes more than 45,000 facilities. To better manage this complex system, Federal Aviation Administration (FAA) management personnel require current and accurate data that reflect the condition of the NAS and its effects on the safe movement of air traffic. This document will provide for this data and serve as the sole source of definition, procedures, and requirements for reporting interruptions to operational facilities and services in the NAS.

TO BASIC

TRomas Gassert Thomas Gassert

Program Director for NAS Operations, AOP-1

Page i (and ii)

11/20/99

TABLE OF CONTENTS

CHAPTER 1. GENERAL

SECTION 1. INTRODUCTION

100. Purpose 101. Distribution 102. Cancellation 103. Effective Date 104. Background 105. Explanation of Changes 106. Definition of Terms 107. Forms and Reports 108.-111. Reserved

SECTION 2. SYSTEM DESCRIPTION

SECTION 2. SYSTEM DESCRIPTION

112. Reporting Requirements 113. Scope 114.-121. Reserved

SECTION 3. RESPONSIBILITIES

122. Responsibilities of Air Traffic System Manager

6040.15D

Page No. 1-1

1-1

1-1 1-1 1-1 1-1 1-1 1-1 1-2 1-8 1-8

1-9

1-9 1-9 1-9

1-10

1-10 1-10

Responsibilities of Air Traffic System Manager and NAS Operations Program

SECTION 3. RESPONSIBILITIES

123. 124. Responsibilities of NAS Operations Program

1-10 1-10

Responsibilities of the Regional Air Traffic and Airway Facilities Divisions

125. 126. Responsibilities of the Regional Airway Facilities Divisions 127. Responsibilities of the Regional Air Traffic Divisions

1-11 1-11

Responsibilities of the AT Facility Managers Air Traffic at All Air Traffic

128. Control Facilities

1-11 1-11

Responsibilities of the AF System Management Office Managers

129. 130.-199. Reserved

CHAPTER 2. FACILITY AND SERVICE REPORTING

CHAPTER 2. FACILITY AND SERVICE REPORTING

SECTION 1. GENERAL REPORTING REQUIREMENTS

200. Introduction 201. Events to be Reported 202. Major Equipment Swapout 203. Mobile Facilities 204. Facility, Service, and Equipment Profile Status Codes 205. Reportable Cause codes

1-12

2-1

2-1

SECTION 1. GENERAL REPORTING REQUIREMENTS

2-1 2-2 2-4 2-5 2-5 2-6 2-13

Status Code “F”, Temporarily Out-of-Service Evaluation Criteria

206. 207.-209. Reserved

Page iii

6040.15D Chg. 1

SECTION 2. SPECIFIC REPORTING REQUIREMENTS

210. Categories of Facilities and Services 211. Automation Reporting 212. Communication Reporting 213. Navigational Aids Reporting 214. Surveillance Reporting 215. Weather Reporting 216. Power Facility and Service Reporting 217. Remote Maintenance Monitoring 218. Log of Corrective Maintenance 219. Additional Log Interrupt Report (LIR) Requirements 220.-299. Reserved

CHAPTER 3. REPORTABLE FACILITIES/SERVICES/EQUIPMENT

CHAPTER 3. REPORTABLE FACILITIES/SERVICES/EQUIPMENT

SECTION 1. FACILITIES AND SERVICES TO BE REPORTED

300. General 301. Reportable Facilities and Services 302.-310. Reserved

SECTION 2. REDUCED OPERATION REPORTING

311. Reduced Facility/Service Operation 312.-315. Reserved

03/28/03

SECTION 2. REDUCED OPERATION REPORTING

2-14

2-14 2-14 2-20 2-24 2-26 2-31 2-34 2-34 2-35 2-36 2-36

3-1

3-1

3-1 3-1 3-4

3-4

3-4 3-5

3-6

SECTION 3. UNIQUE AUTOMATION REPORTING REQUIREMENTS

316. General 317.-399. Reserved

CHAPTER 4. FACILITY POWER AND SUPPORT SYSTEMS

400. General 401. Enhanced Interruption Reporting 402. Applicable Categories and Codes 403. Facility Power and Support Systems Reporting in MMS 404.-450. Reserved

CHAPTER 5. ANALYSIS OF FACILITY/SERVICE PERFORMANCE

CHAPTER 5. ANALYSIS OF FACILITY/SERVICE PERFORMANCE

500. General 501. Analysis of Performance 502. Facility and Service Performance Indicators

3-6 3-6

4-1

4-1 4-1 4-1 4-9 4-11

5-1

5-1 5-1 5-1 5-3

En Route and Terminal Communications Performance Indicators

503. 504. Telco Line Performance Indicators

5-4 5-4

National Airspace System Performance Analysis System (NASPAS)

505. 506.-599. Reserved

Page iv

11/20/99

APPENDIX 1. REFERENCE GUIDES (2 Pages)

APPENDIX 1. REFERENCE GUIDES (2 Pages)

Figure 1-1. Facility/Service Interruption Reference Guide Figure 1-2. Associated/Related Service Reference Guide

APPENDIX 2.1 EXAMPLES OF REPORTING INCIDENTS (23 Pages)

Figure 2-1. ARTCC En Route Communication Services Figure 2-2. ATCT Terminal Services Figure 2-3. Satellite Tower Terminal Services Figure 2-4. ARTCC En Route Services

APPENDIX 2.1 EXAMPLES OF REPORTING INCIDENTS (23 Pages)

6040.15D

1

1 2

1

20 21 22 23

1

APPENDIX 3. SUMMARY OF NASPAS PERFORMANCE REPORTS (1 Page)

APPENDIX 4. GLOSSARY (5 Pages)

1

Page v (andvi)

11/20/99 6040.15D

CHAPTER 1. GENERAL

SECTION 1. INTRODUCTION

100. PURPOSE. This order sets forth requirements and procedures for reporting interruptions to facilities and services in the National Airspace System (NAS). It requires that interruptions be reported in a uniform manner using standard definitions, criteria, procedures, and terminology. The National Airspace Performance Reporting System (NAPRS) serves as a timely and accurate performance information system for use in determining and evaluating the operating condition of NAS facilities/services and the movement of air traffic.

SECTION 1. INTRODUCTION

101. DISTRIBUTION. This order is distributed to division level in Airway Facilities and Air Traffic Airspace Management in Washington headquarters; to branch level in the regional Airway Facilities and Air Traffic divisions; to selected Air Traffic field offices, and to all Airway Facilities field offices with a standard distribution.

102. CANCELLATION. Order 6040.15C, National Airspace Performance Reporting System, dated December 23, 1991.

103. EFFECTIVE DATE.

104. BACKGROUND. Variations in interpretation of definitions and requirements continue to cause minor problems in the facility/service interruption reporting process. New facilities and services have been added to the National Airspace System (NAS) environment, which have been implemented through the Capital Investment Plan (CIP) process. Additionally, there is a renewed interest in the performance level of all existing facilities. This revision addresses these problems and establishes new requirements to enhance and ensure the continued accuracy and usefulness of the NAPRS database.

105. EXPLANATION OF CHANGES. Most changes result from new facility and service reporting requirements, further clarification of current reporting requirements, incorporation of requirements identified in action notices, memoranda, General Notices (GENOT), and recommendations from the field intended to improve the accuracy of NAPRS. The most significant changes are outlined below. Each facility/service acronym which follows is listed alphabetically in Appendix 4, Glossary.

a. Interruption reporting requirements for Mode S Data Link (MODES) facilities have been revised, included is the introduction of MODES Secondary Radar Service (MSEC) and MODES Data Service (MDAT) reporting.

b. All references to “daily" and “non daily" interruption reporting have been removed from the directive.

c. Introduction of a one digit supplemental cause code. This code used in conjunction with the standard two digit cause code will more clearly identify the cause of interruption.

d. Introduction of enhanced reporting requirements for interruptions caused by Facility Power and Support Systems (FPS). FPS systems are identified as Engine Generators (EG), Power Conditioning Systems (PCS), air conditioning systems, power distribution panels, etc.

e. Bright Radar Indicator Tower Equipment (BRITE) has been added to the list of facilities applicable for full interruption reporting.

Chap 1 1-1

6040.15D Chg. 1 03/28/03

f. A reference guide has been added (Appendix 1, Reference Guides) which will assist in locating specific paragraphs related to facilities or services within the directive.

g. Redundant equipment/channel reportable equipment (RE) reporting has been removed (formerly 6040.15C, paragraph 305).

h. Removed all reference to NASPIX.

i. Removal of Display Channel Complex (DCC) equipment and replaced with Display Channel Complex Rehost (DCCR) equipment.

k. Added reporting requirements for the following new equipment: Display System Replacement (DSR), Micro En Route Automated Radar Tracking System (MEART), Precision Runway Monitor (PRM), Satellite Communications Network (SACOM), Standard Terminal Automation Replacement System (STARS), Engine Generator (SX), Terminal Radar Video Switching System (TRVSS), Voice Switching and Control System Emergency Access Radio System (VEARS), VSCS Training and Backup Switch (VTABS), and Wind Measuring Equipment (WME).

1. Added reporting requirements for the following new services: Airport Surface Detection Equipment Service (ASDES) and Weather Message Switching Center Replacement (WMSCR) Data Service (WDAT).

m. Deletion of former Chapters 5 and 6; and former Appendices 1, 4 and 6.

n. Global change from Air Traffic Management (ATM) to Air Traffic Operations (ATO).

o. Removed natural disaster reporting from status code “G” and included in the reporting requirements under status code “F".

p. Additional Reduced Service (RS) Reporting has been removed (formerly 6040.15C, paragraph 312).

q. Added Paragraph 206, Status Code “F”, Temporarily Out-of-Service Evaluation Criteria.

r. Added Paragraph 217, Remote Maintenance Monitoring.

s. Added Paragraph 218, Log of Corrective Maintenance (LCM).

t. Added Paragraph 219, Additional Log Interrupt Report (LIR) Requirements.

106. DEFINITION OF TERMS. Definitions given in this paragraph are intended to explain the various terms being used in NAPRS. In addition, a glossary (Appendix 4, Glossary) has been provided for acronyms and abbreviations commonly used in NAPRS.

a. Associated Facility/Service Interruption. An interruption to an associated facility/service that actually failed or was initially interrupted.

b. Cause Code. A cause code is a two-digit code with the addition of new supplemental codes which closely describes the type of facility or service interruption. Detailed information concerning cause codes is contained in paragraph 205 of this order.

1-2 Chap 1 Par 105

1-2 Chap 1 Par 105

03/28/03 6040.15D Chg. 1

c. Center Radar Automated Radar Terminal System (ARTS) Processing (CENRAP). A software/hardware modification that provides backup alphanumeric information using target data received by the ARTS equipment via the en route automation computer system through the existing Interfacility Data Service (IDAT) (NAS/ARTS) interface. An azimuth pulse generator provides display sweep if needed. Interruption reporting of the Terminal Automated Radar Service (TARS) is required during CENRAP operation. (See paragraph 211b(6) for TARS reporting requirements.)

d. CENRAP Processing Plus. A computer program developed to provide a back-up system for airport surveillance radar in the event of a terminal secondary radar system failure. The program uses a combination of Air Route Traffic Control Center Radar and terminal airport processing and presentation of data on the ARTS IIE or IIIA displays.

e. Commissioned. A facility, system, subsystem, or equipment is commissioned when it has been formally accepted and placed into operational use or service in the NAS, and its controlling Airway Facilities (AF) System Management Office (SMO) has assumed formal maintenance responsibility.

f. Commissioning. The formal exercise of incorporating a new facility, system, subsystem, or equipment into the NAS. This term has legal and budgetary significance and is used to justify logistic and operational support as an FAA obligation under public law.

g. Coordinated Universal Time (UTC). UTC has replaced Greenwich Mean Time (GMT) as the accepted standard for clock time in many countries. It is also the time provided in the worldwide time signal broadcasts used in aviation.

h. Facility. Generally, any installation of equipment designated to aid in the navigation, communication, or control of air traffic. Specifically, the term denotes the total electronic equipment, power generation, or distribution systems and any structure used to house, support, and/or protect these equipment and systems. A facility may include a number of systems, subsystems, or equipment; e.g., a long-range radar facility, or a single system, subsystem, or equipment, such as an isolated Radio Communications Link Repeater (RCLR) facility.

i. Facility/Service Operational Time. The time from facility/service restoration until the time the facility/service is released by appropriate Air Traffic (AT) personnel or until the next interruption occurs (i.e. the time period in which the facility/service is available to Air Traffic for use in the NAS).

j. Facility/Service Available but Not in Use. The period of time from when the facility/service is operationally available until it is accepted for operational use; i.e., AT decides not to use the facility/service due to existing condition. (See paragraph 201of this order for reporting procedures.)

k. Facility/Service Deteriorated but Usable and Not Released by AT. The time when a facility/service has deteriorated to below standards until that time when the appropriate AT personnel release the facility/service for maintenance. Certification may or may not have been partially or fully removed. Application of guidance for this condition may be found in the latest editions of Order 7210.3, Facility Operation and Administration, and Order 6000.15, General Maintenance Handbook for Airway Facilities. These incidents shall be reported as unscheduled interruptions at the time AT releases the facility/service for maintenance. In addition, a reduced facility/service operation may result if the criteria as specified under paragraph 106t of this order are met. (See paragraphs 201and 311 of this order for reporting requirements.)

1. Frequency. A simplex channel of air/ground communications utilizing the same frequency for transmission and reception.

m. Hardware. In computer applications and elsewhere, the term hardware refers to the physical equipment or devices used to perform simple or complex functions. This term must be qualified by using an appropriate restrictive modifier to convey a specific identification or meaning.

Par 106 Chap 1 1-3

6040.15D Chg. 1 03/28/03

n. Incident. A single occurrence relating to an interruption.

o. Interruption. A break in continuity, the loss, or unavailability, of a facility/service regardless of duration. p. May. MAY means an action is permitted.

q. Monthly. A reporting interval meaning one calendar month.

r. Outage. The loss of facility/service for 1 minute or more.

s. Periodic. An occurrence or recurrence at regular intervals.

t. Personnel Error. Any interruption of a facility/service caused by human error.

u. Reduced Facility/Service Operation. When a facility or service is in use but is not capable of fulfilling its complete intended mission and Air Traffic personnel declare an operational impact; such as, the necessity to combine positions, delay of air traffic, and/or loss of essential Air Traffic Control (ATC) functions. Reduced facility/service operation is not limited to automation services. The "RS" code is used for both reduction of service and reduction of facility operation. (See paragraph 311 of this order for reporting procedures.)

v. Reimbursable. Reimbursable means that the FAA maintains equipment/facilities which are not owned by the FAA and receives a reimbursement for this service.

w. Related Facility/Service Interruption. An interruption of a facility/service caused or necessitated by an interruption of another facility/service. (See paragraph 201d; Appendix 2, Examples of Reporting Incidents, for reporting procedures and examples.)

x. Repair Time. The actual time spent repairing the equipment (includes testing, troubleshooting, monitoring of equipment while at the site and parts replacement time). This shall not include delayed restoration, administrative, travel or logistics time.

y. Report Date/Time of an Interruption. When referring to an interruption incident, the report date/time will always be the time when the interruption first occurred. If interruption time is not available, the time when the FAA is first made aware is to be used. All times shall be entered as UTC.

z. Report Period. Report periods identifying the time interval of reporting may vary with the particular reporting system. Detailed information concerning each report period is contained in paragraph 200 of this order.

aa. Reportable Facility. Any commissioned facility, including reimbursable facilities, for which reporting of interruptions has been designated. Reportable facilities are those listed in the Facility, Service, and Equipment Profiles (FSEP) status code of D, E or G, and responsibility codes of A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, S, T, U, V, W, X, Y, Z. Reportable facility types are identified in paragraph 301 of this order. Additionally, facilities that are status code C and have a responsibility code listed above, are reportable when in Operation Readiness Demonstration (ORD) status.

bb. Reportable Service. Any service for which reporting of interruptions has been designated, per paragraph 301b. of this order. All reportable services shall be entered in the FSEP using the status codes Y or Z and the responsibility code which would be indicative of the remote site of the service. Reportable services provided to and/or from a military facility shall have a responsibility code of either I, R, or 9.

cc. Restoration. Restoration includes all activities required to return a service/facility to operational status following a facility or service interruption. Chap 1 1-4 Par 106

03/28/03 6040.15D Chg. 1

dd. Scheduled Interruption. A term used to indicate that a facility or service interruption was coordinated for a predetermined period of time with prior approval from the facilities manager, assistant facilities manager, or other appropriate AT personnel. This coordination is required for the following maintenance activities listed in subparagraphs below. Also, scheduled interruptions can only be terminated by facility/service restoration, initiating unscheduled outages, or by decommissioning. If during a scheduled interruption, an out-of-tolerance condition is discovered and it becomes obvious that an extension will be required to complete the facility restoration, AT should be notified as early as possible and a request made to extend the scheduled interruption. If the request is denied and the interruption continues past the original scheduled restoration time, the scheduled interruption will end and an unscheduled interruption will begin at the end of the scheduled interruption time. In cases where the request is granted, but restoration activities close prior to the end of the approved extension (for example, parts must be ordered, administrative decision to no longer work on it because of other priorities) the scheduled outage will end at the time the facility restoration work is halted and an unscheduled outage will begin.

(1) Scheduled Corrective. An interruption of a facility/service for required corrective maintenance. It is a planned action to correct a facility/service performance deterioration and applies only when the facility/service is operating within hardware/software operational requirements (tolerances/limits) prior to the scheduled interruption.

(2) Scheduled Routine. An interruption of a facility/service for planned maintenance activities and includes activities such as:

(a) Periodic maintenance per directive.

(b) Planned hardware modifications, improvement, projects, and associated testing.

(c) Software program updates and associated testing; i.e., new version/level, chart update, and national patch release.

(d) Flight inspections.

(e) Planned administrative; i.e., evaluations, military activities, certification exams, training, etc.

ee. Service. Service is the end product which is delivered to a user (AT personnel, the aviation public, or military) that results from an appropriate combination of systems, subsystems, equipment, and facilities. Pictorial diagrams of the interrelated facilities and services are provided in Appendix 2. Two examples are:

(1) A chain of facilities consisting of an Air Route Surveillance Radar (ARSR), Common Digitizer (CD), Radar Microwave Link Terminals/Radio Communications Link Terminals (RMLT/RCLT), Radar Microwave Link Repeater/Radio Communications Link Repeater (RMLR/RCLR), and associated Air Route Traffic Control Center (ARTCC) equipment provides AT personnel with en route Radar Digitized Data (RDAT).

(2) A Remote Tower Radar Display Service (RTRDS) is the combination of an Airport Surveillance Radar (ASR), Air Traffic Control Radar Beacon (ATCRB), transmission media, Bright Radar Indicator Tower Equipment (BRITE), and associated terminal equipment to provide radar information to AT personnel at satellite tower locations.

Chap 1 Par 106 1-5

6040.15D Chg 1 03/28/03

ff. Service Fault Location. The location of the inoperable segment of a chain of facilities and/or equipment causing a service interruption. Three service fault locations are designated as follows:

(1) Control Site. The control site (service fault location "C"), such as an airport traffic control tower (ATCT), is the controlling point of the service. The control site encompasses all necessary control, decoding, display, or other ancillary equipment associated with the control point of the particular service, exclusive of link terminals.

(2) Line or Link. That portion in a chain of facilities which provides the point-to-point media transmission between the control and remote site. Included in this portion are FAA (service fault location "F") or leased telephone company (TELCO) (service fault location "T") transmission lines, link terminals, modems, and link repeaters. All code 61 and 81 interruptions shall have a service fault "T".

(3) Remote Site. A remote site (service fault location "S"), such as a remote center air/ground communication (RCAG) facility, is the remote end of a service. A remote site encompasses all transmitting, receiving, control, and ancillary equipment associated with the remote end of a particular service, exclusive of link terminals. In the case of Flight Data Entry and Printout (FDAT) and Interfacility Data Services (IDAT), the terminal facility (ATCT, and/or Terminal Radar Approach Control (TRACON) facility) is considered the remote site for the ARTCC. For the RTRDS, the remote tower alphanumerics display service (RTADS), and in some cases, the Terminal Radar (TRAD) and Terminal Secondary Radar (TSEC), the remote site will include the equipment from the radar site up to the last point of transmission to the satellite tower location, exclusive of link terminals.

gg. Shall. SHALL means that an action is mandatory.

hh. Shall Not. SHALL NOT means that an action is prohibited.

ii. Should. SHOULD means that an action is desirable but not mandatory.

jj. Software. Software is a computer-oriented trade term which includes all instructions, diagrams, and step-by-step routines, exclusive of the hardware, required to utilize computer capabilities. Software outages shall be reported against service only.

kk. Supplemental Cause Code. The supplemental cause code is a separate field from the standard cause code. It is a single digit field that, used in conjunction with the standard cause code, will more accurately identify the cause of a facility or service interruption.

ll. Total Scheduled Interruption Time. The following definitions of total scheduled interruption time shall be used.

(1) Facility Reporting. Time begins when the facility is released by appropriate personnel (AT, military) and ends when the facility is restored by appropriate AF personnel.

(2) Service Reporting. Time begins when the service is released by appropriate personnel (AT, military) and ends when the service is restored and accepted by the user (AT, military, etc.) regardless of whether the service is to be used at the time of acceptance. For example, an en route communication (ECOM) frequency that was restored and AT accepted the service but did not require its use is considered to be back in operation.

Chap 1 1-6 Par 106

03/28/03 6040.15D Chg 1

mm. Total Unscheduled Interruption Time. The following definitions of total unscheduled interruption time shall be used. When applicable, the time from a computer printout may be used for the start time of an unscheduled interruption.

(1) Facility Reporting. Time begins with initial FAA awareness of the interruption and ends when the facility is restored by appropriate AF personnel.

(2) Service Reporting. Time begins with initial FAA awareness of the interruption and ends when the service is restored and accepted by the user (AT, military, etc.) regardless of whether the service is to be used at the time of acceptance.

nn. Umbrella Service. A hierarchical service which supports numerous underlying facilities and services. Normally, when an interrupted umbrella service is reported, interruption reports are not required for the underlying services if the umbrella service is reported as a full interruption. Each umbrella service is identified in Chapter 2 of this order.

Umbrella Service Service Under the Umbrella

AWPS AWPTE/AWPTW CFAD FDAT/IDAT FSSPS FSSAS NADS NAMS VSCSS ECOM

AWPS AWPTE/AWPTW CFAD FDAT/IDAT FSSPS FSSAS NADS NAMS VSCSS ECOM

oo. Unmonitored Facility. A facility that has no remote monitoring capabilities.

pp. Unscheduled Interruption. An unscheduled interruption is:

(1) Any unanticipated interruption regardless of duration of a facility or service.

(2) Any out-of-tolerance/out-of-limit condition which results in the removal of a facility/service from the NAS.

(3) A facility that is reported out-of-tolerance by flight inspection.

(4) A hardware out-of-tolerance/out-of-limit condition which results from an equipment failure and/or malfunction and which prevents the restoration of a facility/service following a scheduled interruption. For this situation, the unscheduled interruption shall start immediately following the end of the original scheduled shutdown or the end of any approved extension which is granted to a scheduled shutdown.

(5) A software out-of-tolerance (specification) condition which prevents the restoration of a facility/service following a scheduled interruption. The unscheduled interruption shall start immediately following the end of the original scheduled shutdown or the end of any approved extension(s).

qq. User. AT personnel, military personnel, or the aviation public.

rr. Will. WILL indicates a presumption that action is to be taken.

Chap 1 1-7 Par 106

6040.15D 11/20/99

107. FORMS AND REPORTS.

a. Form Listing. FAA Form 6040-3, Facility and Service Outage Report. (RIS: AF 6040-48). Refer to NSN 0052-00-687-4001 when ordering FAA Form 6040-3. The unit of issue is a pad (50 sheets). FAA Form 6040-3 shall still be required until such time that paper logs are gone and the site has fully implemented automated logging capabilities

b. Reports Listings. Information relating to description and format, preparation responsibility, source of data, and frequency of the following reports can be found in Appendix 3, Summary of NASPAS Performance Reports. Chapter 5, Analysis of Facility/Service Performance, supports the requirements of these reports.

(1) Facility and Service Detail Listing (RIS: AF 6040-12).

(2) Facility and Service Outage Report by Location Identifier (RIS: AF 6040-19).

(3) Air Navigation and Air Traffic Control Facility Performance and Availability (RIS: AF 6040-20).

(4) Facility and Service Outage Report Summary Data by Region/ARTCC (RIS: AF 6040-21).

(5) Facility and Service Outage Report - Regional Rank Order Listing (RIS: AF 6040-41A).

(6) Facility and Service Outage Report, ARTCC Associated Facilities and Services (RIS: AF 6040-50).

108. - 111. Reserved.

1-8 Chap 1

1-8 Chap 1

11/20/99 6040.15D

SECTION 2. SYSTEM DESCRIPTION

112. REPORTING REQUIREMENTS. This directive serves as a primary source of reporting requirements and procedures and describes Office of Air Traffic Operations (ATO), Director of Airway Facilities (AAF), and NAS Operations Program (AOP) responsibilities at all organizational levels for reporting and monitoring the operating status of the NAS. Changes to, or any additional reporting requirements, are subject to the following conditions:

SECTION 2. SYSTEM DESCRIPTION

a. Other reporting systems relating to performance of facilities in the NAS or the movement of air traffic are prohibited, unless coordinated with ATO and AOP and included as part of the Maintenance Management System (MMS).

b. Headquarters imposed reporting requirements or any changes to existing requirements contained in this order cannot be implemented and included as part of NAPRS without prior concurrence of ATO and AOP.

c. Regional, SMO, or facility imposed reporting requirements and/or increased frequency of reporting is at the discretion of each region, SMO, or facility. However, all requirements and procedures shall be included as a supplement to this order and shall be coordinated with AOP and ATO. Additionally, coordination will be required with the regional Management Systems, Resource Management, Budget, and Financial and Management Resource divisions should regional, SMO, or facility imposed reporting requirements indicate the need for regional data processing resources.

d. Regional supplements (e.g., orders, letters, notices) regarding clarification of information contained in this order shall be coordinated with AOP and ATO prior to implementation.

1 13. SCOPE. This order affects virtually all aspects of FAA. Specific requirements and responsibilities of the individual offices are spelled out in the body of this order.

114.-121. Reserved.

Chap 1 1-9

6040.15D 11/20/99

SECTION 3. RESPONSIBILITIES 122. RESPONSIBILITIES OF AIR TRAFFIC OPERATIONS (ATO). ATO is responsible for: a. Defining additional reporting requirements or criteria for NAS performance reports that best serve the Administrator or the Administrator's staff. These shall be coordinated with AOP prior to implementation if amendments to this order would be required. b. Providing direction to all regional AT divisions to ensure that reporting procedures and content of reports are consistent and adequate among the regions. 123. RESPONSIBILITIES OF AIR TRAFFIC OPERATIONS (ATO) AND NAS OPERATIONS PROGRAM (AOP). ATO and AOP are jointly responsible for: a. Providing guidance to the regional offices for defining national facility and service interruption reporting criteria. b. Taking appropriate action to ensure that reporting procedures are consistent among all regions. c. Analyzing service performance. 124. RESPONSIBILITIES OF NAS OPERATIONS PROGRAM (AOP). AOP is responsible for: a. Providing for overall program management of NAPRS. The office with primary responsibility for this order is AOP-200. b. Daily production of NAS performance report and other materials for briefing appropriate managers and staff on the status of the NAS. c. Updating the national interruption data bases residing on the headquarters Maintenance Processor Subsystem (MPS). The office of primary responsibility is AOP-200. d. Analyzing overall facility/service performance. The office of primary responsibility is AOP-200.

e. Providing guidance to the regional AF divisions to ensure that reporting procedures are consistent among all regions. The office of primary responsibility is AOP-200. 125. RESPONSIBILITIES OF THE REGIONAL AIR TRAFFIC (AT) AND AIRWAY FACILITIES (AF) DIVISIONS. The regional AT and AF division are jointly responsible for: a. Ensuring that reporting procedures are consistently followed throughout the region and providing necessary feedback to AF and AT field offices. b. Analyzing regional facility/service performance. c. Establishing a facility/service improvement plan based upon analysis of the performance data. d.Ensuring that areas of joint responsibility and compliance with requirements as specified within this order are strictly adhered to at all facilities throughout the region.

1-10 Chap 1

1-10 Chap 1

11/20/99 6040.15D

126. RESPONSIBILITIES OF THE REGIONAL AIRWAY FACILITIES (AF) DIVISIONS. The regional AF divisions are responsible for:

a. Establishing a system for analyzing the performance of regional facilities and services.

b. Designating a NAPRS point-of-contact who is responsible for coordinating all interruption data within the region, and interfacing with AOP-200.

c. Ensuring that facility and service reporting procedures are consistently followed throughout the region and providing necessary feedback to AF SMOs.

d. Ensuring that all interruption data is processed and transmitted for the inclusion into the national data base update.

127. RESPONSIBILITIES OF THE REGIONAL AIR TRAFFIC (AT) DIVISIONS. Regional AT divisions are responsible for providing guidance and any necessary assistance to AT facilities to ensure that all reporting procedures and report content are consistent and adequate among facilities in the regions.

128. RESPONSIBILITIES OF THE AIR TRAFFIC (AT) FACILITY MANAGERS AT ALL AIR TRAFFIC CONTROL (ATC) FACILITIES. AT facility managers at all ATC facilities are responsible for establishing procedures for:

a. Ensuring that all interruptions are promptly reported to the appropriate AF personnel and identifying those interruptions which contributed to or caused air traffic delays.

b. Ensuring that equipment-caused delay reports have been coordinated with and agreed to by both AT and AF, and that they are entered into OPSNET.

c. Providing information to appropriate AF personnel on changes in category II/III runway sites.

d. Ensuring that all appropriate personnel are aware of and comply with requirements as specified in this order.

e. Providing final acceptance for the use/usability of a service, when notified of availability for use by appropriate AF personnel.

129. RESPONSIBILITIES OF THE AF SYSTEM MANAGEMENT OFFICE (SMO) AND SYSTEM SERVICE CENTER (SSC) MANAGERS. The AF SMO/SSC managers are responsible for:

a. Ensuring that interruption reports for facilities and services within their jurisdiction have been coordinated with and agreed to by both AT and AF, and entered into Maintenance Management System (MMS) via Log Interrupt Reports (LIR) screens.

b. Ensuring that interruptions that are reportable, as defined in this order, are entered into MMS as soon as possible after the start of that reportable occurrence.

c. Ensuring that any corrections and/or added information to previously reported interruptions are entered as soon as noted.

Chap 1 1-11

6040.15D 11/20/99

d. Ensuring that facility and service reporting procedures are consistently followed throughout the SMO and providing necessary feedback to SMO/SSC offices.

e. Ensuring that all interruption data are reviewed for accuracy and completeness prior to the execution of the monthly national data base update. This should include weekly execution and reconciliation of the MMS Facility/Service Outage reports (R60403).

f. Formalizing the review process in accordance with current orders and guidelines.

130.-199. Reserved.

1-12 Chap1

1-12 Chap1

11/20/99 6040.15D

CHAPTER 2. FACILITY AND SERVICE REPORTING

SECTION 1. GENERAL REPORTING REQUIREMENTS

200. INTRODUCTION. This section contains general requirements for reporting facility and service interruptions and defines the reporting periods for both. Reportable facility and service types are identified in paragraphs 301 of this order. (See Appendix 2, Examples of Reporting Incidents, of this order for examples of reporting incidents.)

SECTION 1. GENERAL REPORTING REQUIREMENTS

a. Timely Reporting. Interruptions that are reportable are required to be entered into MMS as close as possible to the start of the reportable occurrence.

b. Reporting Times. All times shall be entered as UTC.

c. Reporting Transmission. All interruptions are required to be entered into MMS. Interruptions are automatically transferred to the headquarters MPS shortly after they are entered into MMS at each MPS.

d. Reportable Interruptions. All interruptions, 1 minute or more in duration, to facilities and services listed in paragraphs 30la and 301b shall be reported. Facilities and services identified with an (#) shall report all unscheduled interruptions regardless of duration.

e. Interruption Data Accuracy/Completeness. All interruptions shall be reviewed for accuracy consistent with established editing criteria and this order. Information on interruptions shall be of sufficient quality and quantity to ensure that a complete understanding of the interruption may be acquired.

f. Facility Performance Reporting. Facility performance is measured by recording individual facility interruptions. For example, the interruption of an ARSR at a long-range radar site would require an ARSR facility report. No report would be necessary for an ATCRB or CD even though a loss of signal input was experienced by these facilities. However, the appropriate services provided by these facilities would be reported as a related interruption. (See Appendix 1, Reference Guides, and Appendix 2, Examples of Reporting Incidents.)

g. Service Performance Reporting. Service performance is measured in terms of the END PRODUCT from a combination of facilities and/or equipment as opposed to individual facility performance. For example, the RDAT may include the net performance result of the ARSR, CD, RCL, and ancillary equipment at the ARTCC and radar sites. The loss of any portion of this chain of facilities and equipment may result in an RDAT service interruption. This includes military services.

h. Service Location Identifiers. General instructions for service location identifiers are contained in Order 6000.5, Facilities, Service, and Equipment Profile (FSEP). Specific instructions regarding service location identifiers, the use of suffixes, and identification of control and remote fields in the FSEP are provided in the appropriate paragraphs of this chapter where service reporting procedures are addressed. In addition to these instructions, the city and state location for reportable services shall always be the location of the remote field identifier used in the FSEP.

Chap 2 2-1

6040.15D Chg 1 03/28/03

i. Corrections and/or Added Information. Any action that requires a change to a previously reported interruption shall be coordinated with the responsible Systems Management Office (SMO) manager or designee, as appropriate.

(1). Reporting Period. Defined as the calendar month that the outage occurs in, from the 1at day of the month until the last day of the same month.

(2). Timely Corrections. Corrections made or information added to LIRs shall be made prior to the cut-off date. (Cut-off date is 10 days after the end of the reporting period.)

(3) Late Corrections. Due to software design, changes to LIR data after the 10th day of the month following a reporting period cannot be accepted into the National Outage Data Base (NODB) without direct intervention by AOP-200. Notification of late changes must be submitted to AOP-200, via Memorandum from Division Manager, AXX-400, through the regional NAPRS coordinator.

j. Multiple Facility/Service Entries. The basic design of MMS will allow those facility/service interruptions that are associated or related to the facility/service being reported to be identified in the same LIR. All problems encountered during recovery of related/associated services shall be identified. (See the MMS user's guide, Appendix 1, Reference Guides, and Appendix 2, Examples of Reporting Incidents, for logging procedures for associated/related entries.)

k. Report content. Content and format instructions for reporting facility and service interruptions are found in the MMS user's guide.

1. Facility, Service, and Equipment Profile (FSEP). Procedures for updating the FSEP are found in Order 6000.5. Outage reports are reconciled with the FSEP records on a monthly basis, therefore, any update to the FSEP must be completed by the last working day of the reporting month. FSEP records, as they appear on the last day of the month, are reflective for the entire month's period.

201. EVENTS TO BE REPORTED.

a. Commissioning/Decommissioning of NAS Facilities. The commissioning or decommissioning of a facility/service that is NAPRS reportable shall be reported using the Facility Commissioning/Decommissioning (LFC) report in MMS. These reports shall be identified as nationally reportable (reportability code ‘N" in MMS). In addition, the following entries shall be made to the FSEP for commissioned or decommissioned facilities:

(1) Newly Commissioned Facilities and Services. In concert with Order 6000.5, newly commissioned facilities and services shall be reported immediately upon commissioning. Reportable facilities and services must be commissioned before interruption reporting results can be accepted into NAPRS. The FSEP shall be updated in a timely manner even if telephone coordination between the field and regional office is required.

(2) Decommissioned Facilities and Services. Facilities and/or services shall be reportable through the date of decommissioning. The facility/service shall remain in the FSEP in a commissioned status for 1 month to allow the updating of the national outage data base.

Chap 2 2-2 Par 200

03/28/03 6040.15D Chg 1

b. Interruptions to Facilities or Services. Facility and/or service interruptions that meet criteria of this directive shall be reported. The duration of the LIR event shall be an indication of the entire time the facility or service was unavailable. The interruption time shall continue, regardless of use of a back-up, until operation of the primary facility is restored.

c. Associated Facility/Service Interruptions. An interruption to a facility/service that actually failed or was initially interrupted (see Appendix 1, Reference Guides). A facility unable to perform its intended mission as a result of a failure of a nonreportable service related component (control, line/link, or software) or a personnel error external to the site shall result in an interruption report for the service only if a service exists. A loss of availability of a facility that occurs internal to the site, including personnel errors, shall result in an interruption report for the facility and the affected services. An associated facility/service interruption will have the same cause code as the primary facility or service interruption entered on the NAPRS/MMS report.

d. Related Facility/Service Interruptions. A facility or service interruption which is a direct result of an interruption of another facility or service shall use the related facility interruption definition (see Appendix 1, Reference Guides). It will have the related cause code (68/88) entered on the NAPRS/MMS report.

e. Facility/Service Available but Not in Use. If the restoration times for the facility and service are different, both times shall be identified in the report.

f. Continued Use of Deteriorated but Usable Facilities/Services. It is recognized that AT officials may choose to continue use of deteriorated but usable facilities/services (see paragraph 106j of this order). These incidents shall be reported as unscheduled service interruptions when AT releases the service. The time between initial awareness and the time of release may be reported as a reduced service report. (See paragraph 31 lof this order for reduced facility/service operation reporting requirements.)

Military Service Interruptions. All services provided to the military shall be reported. Services provided to FAA from military-owned/maintained facilities shall be reportable.

h. Nonoperational Facility/Service Interruptions. Uniess specified otherwise, all interruptions shall be reported even though the facility is not being called upon for operational use. Terminal (tower) locations which provide less than 24-hour service shall not report the published downtime as a scheduled interruption. If maintenance requiring downtime is performed, or a facility/service is made unavailable, or a loss of service occurs during the published downtime, a scheduled or unscheduled interruption, as appropriate, shall be reported. Some examples of types to be reported are as follows:

(1) An approach lighting system (ALS) that is shut down for routine maintenance during the daylight hours.

(2) A second instrument landing system (ILS) that, because of wind direction, is not in operational use but is shutdown for equipment modification or maintenance.

(3) An ARTS II location has published hours of operation from 0600 to 2200 and is closed after 2200 until the next morning. Unscheduled and scheduled interruptions that occur during the hours of 2200-0600 are reportable.

Chap 2 Par 201 2-3

6040.15D Chg 1 03/28/03

i. Unmonitored Facility Interruptions. An unscheduled interruption shall be reported with the appropriate code whenever restoration is made to an unmonitored facility. The actual restoration time shall be used if the total interruption time cannot be determined (air traffic, pilot reports (PIREPS), etc.). A minimum interruption time of 1 minute shall be used if restoration is less than 1 minute. For example, a specialist found an outer marker shut down upon arrival for routine maintenance. After restoration, no reason could be established as to why it failed or what time the original shutdown occurred. The marker has no remote monitoring feature, and since the cause and time of interruption could not be determined, a cause code 87 would be used with the restoration time required to restore the facility.

j. Interruption and Notices to Airmen (NOTAM) Relationships. Although a relationship may exist between interruptions and NOTAMs, Airmen's Advisories (AIRAD), etc., there is no mandatory requirement that each NOTAM be accompanied by a corresponding report of interruption or that NOTAM times correspond to interruption time.

k. Locally Bypassed Monitors. An interruption report shall be required whenever a facility's automatic shutdown capability is not maintained and the facility is unattended. In most cases, the loss of this capability requires decertification and removal from the NAS with AT concurrence.

1. EPROM Changes. When a NAS system requires an EPROM change that is directed by an EEM or other authority that produces a modification to the system, a code 62 shall be utilized against the facility. (Example code 62 - EPROM map change for XYZ BRITE.) When an EPROM change is a periodic or requested change, that does not produce a modification to the system, a code 64 shall be used. (Example code 64 - DOD operating system change for XYZ ARSR-4.)

202. MAJOR EQUIPMENT SWAPOUT. Major equipment swapout is defined as a physical change or replacement to a commissioned facility which requires a change to the model number in the FSEP. There are times when a commissioned facility (which has an FSEP status code of “D") and its replacement facility (which has a FSEP status code of“C") may coexist. See FSEP Order 6000.5 for additional guidance.

Chap 2 2-4 Par 201

03/28/03 6040.15D Chg1

203. Reserved. Guidance for Mobile Facilities is now contained in 6000.5

204. FACILITY, SERVICE, AND EQUIPMENT PROFILE (FSEP) STATUS CODES. Status codes E, F, G, Y, and Z were created to support NAPRS requirements. See FSEP Order 6000.5 for guidance with status codes.

Chap 2 Par 202 2-5

6040.15D Chg 1 03/28/03

205. REPORTABLE CAUSE CODES. Consistency in assigning appropriate cause codes to all interruptions is necessary in order to provide accurate data for future analyses. The following guidelines shall be used:

a. Only one cause code shall be used for the entire duration of a scheduled or unscheduled interruption and this shall be the true cause or reason for the interruption. If an unscheduled incident initially appears to be hardware but is later found to be software, cause code 86 would be used since the true cause of the interruption was software. When two or more scheduled activities occur simultaneously, report the principal activity under the proper cause code and explain in the remarks the activities that were performed. If a scheduled interruption is followed by an unscheduled interruption, both shall be reported separately and explained under remarks. An unscheduled interruption shall not be terminated until the facility/service is returned to service or decommissioned.

b. All codes, especially cause code 87, shall be changed to the appropriate code whenever the true cause for the unscheduled interruption is determined. This will require procedures for follow-up investigation and review by the appropriate personnel together with updating the existing data in a timely manner. Corrections to previously reported and closed interruptions shall be made, but require coordination with appropriate personnel.

Chap 2 2-6 Par 204

03/28/03 6040.15D Chg 1

c. The following cause codes, with the addition of supplemental cause codes, shall be used to most closely describe the reason for the facility or service interruption:

NOTE: Supplemental cause code shall be entered on the LIR in the field identified as “SC".

(1) Scheduled Cause Codes:

Code Description

60 Periodic Maintenance (PM). An interruption of a facility or service for planned maintenance activities. This includes performance checks, adjustments, calibration, cleaning, and painting. This cause code shall be used for maintenance to FAA lines (all types), electronics systems/components, or plants and structures. This does not include periodic software activities (See cause code 66). (See also Chapter 4 for Facility Power and Support Systems reporting requirements.)

Supplemental Cause Codes: 0 Periodic Maintenance F Facility Power and Support Systems

61 Non-FAA Lines/Circuits. An interruption of a control, communication, or data transmission line (TELCO, military, FAA scheduled line runs, etc.)

Supplemental Cause Codes: 0 Equipment 1 Line/Circuit 2 Satellite 3 Power 4 Military

62 Improvements. An interruption for relocation, replacement, modification, (including military), special projects and construction at or near the facility location. This code includes firmware changes which are issued as modifications. (See also Chapter 4 for Facility Power and Support Systems reporting requirements.)

Supplemental Cause Codes: 0 Modification 1 Improvement (an interruption of 14 days or less) 2 Relocation (an interruption of 14 days or less) 3 Long Term Improvement/Relocation 4 Construction F Facility Power and Support Systems

Chap 2 Par 205 2-7

6040.15D 11/20/99

63 Flight Inspection. An interruption for airborne inspection of the radiated characteristics of a facility by flight inspection personnel.

Supplemental Cause Codes: 0 Scheduled 1 Post Aircraft Accident 2 Special

64 Administrative. A facility/service interruption because of administrative requirements such as special tests, Department of Defense activities, formal facility inspections, training, performance/certification examinations, and key site testing at en route and terminal automation facilities. (See also Chapter 4 for Facility Power and Support Systems reporting requirements.)

Supplemental Cause Codes: 0 Special Tests 1 DOD Activities 2 Facility Inspections 3 Training 4 Performance Examinations 5 Key Site Testing 6 Administrative F Facility Power and Support Systems

65 Corrective Maintenance. A planned action to correct a deterioration of facility/service performance. This code applies only when facilities/services are operating within specified requirements (operational) prior to the corrective activity and includes troubleshooting and snow removal, grass cutting, etc. (See also Chapter 4 for Facility Power and Support Systems reporting requirements.)

Supplemental Cause Codes: 0 Troubleshooting/Repair 1 Snow/Ice Removal 2 Vegetation Control 9 Other F Facility Power and Support Systems

66 Software. An interruption because of software or program activity. This includes operational program/patch testing and data base testing activities, or a planned action to correct a deterioration of service performance. This code applies to activities or actions to remove a patch from the system, add a local patch to the system, and to correct or improve the adapted data base. Use this code only when the software is operating within specifications prior to corrective activities.

Supplemental Cause Codes: 0 Testing

2-8 Chap 2

2-8 Chap 2

11/20/99 6040.15D

1 New Program/Database Load 2 Corrective Software Maintenance

Reserved.

Related. This code will be used when a facility or service fails to perform its intended function as a result of an interruption of another facility or service.

Supplemental Cause Codes: 0 Caused by a Facility Interruption 1 Caused by a Service Interruption

1 New Program/Database Load 2 Corrective Software Maintenance

Other. This code will be used only if the interruption cannot be associated with any other scheduled code category.

Supplemental Cause Codes: 9 Other

(2) Unscheduled Cause Codes:

Code Description

Equipment. Any failure or malfunction of electronic or lighting systems (including firmware), FAA lines or links (all types), FAA electrical distribution systems or structure items which cause an interruption of the facility or service. (See also Chapter 4 for Facility Power and Support System reporting requirements.)

Supplemental Cause Codes: 0 Antenna System 1 Transmission Line/Connector 2 Fuse/Circuit Breaker 3 Power Supply 4 Equipment Part Failure 5 FAA Control/Monitor Line 6 Physical Storage Medium of Software 7 Unable to Determine Cause (Equipment Only) 8 Intermittent Errors 9 Auto Reset F Facility Power and Support Systems

Non-FAA Lines/Circuits. An interruption caused by loss of control, communications, or data transmission, including degradation of performance, where repairs are required (TELCO, military, etc.). This code is to be used for TELCO personnel errors while working on leased circuits. It is also used when TELCO equipment is affected by a power failure and FAA equipment continues to perform its mission by use of standby power.

Chap 2 2-9

6040.15D 11/20/99

Supplemental Cause Codes: 0 Equipment 1 Line/Circuit 2 Satellite 3 Power 4 Military 5 Cable Cut 6 Environmental Causes 7 Unknown 8 Personnel Error 9 Other

82 Prime Power. Any facility or service interruption caused by prime power services shall use this code. Power services may be commercial, FAA, military, or sponsor supplied. This code applies to all power reiated interruptions and includes fluctuations, surges, transients, or complete loss of power. Equipment failures (circuit breakers, printed circuit cards, associated switchgear, etc.) that occur as a direct result of prime power shall use this code. This code shall be used for all facility/service interruptions resulting from the loss of commercial power. (See also Chapter 4 for Facility Power and Support Systems reporting requirements.)

Supplemental Cause Codes: F Facility Power and Support Systems

83 Standby Power. An interruption caused by loss of standby power when it is serving the facility as a back-up to the normal prime power, or a failure of standby powerplants, including associated standby power switchgear, to assume the load upon transfer. This includes fluctuations, surges, running out of fuel, battery discharge before commercial power is restored, and transients caused by standby power. For the purpose of reporting interruptions, standby powerplants, power switchgear, uninterruptible power source (UPS), power conditioning system (PCS), and batteries are considered standby power. Failures of equipment operating within tolerance that occur as a direct result of standby power shall use this code. This code shall be used for all facility/service interruptions resulting from loss of standby power. (See also Chapter 4 for Facility Power and Support Systems reporting requirements.)

Supplemental Cause Codes: F Facility Power and Support Systems

84 Interference Conditions. Any condition, regardless of intensity, caused by atmospheric changes, or other factors which are detected by the equipment. Examples: false targets due to anomalous propagation; interference, regardless of length of time, sources, or severity, believed to be caused by military electronic countermeasures (ECM) operations; path fade; radio frequency interference (RFI), intentional interference; solar activity, temperature inversion; distortions of signal patterns caused by anomalous

2-10 Chap 2

2-10 Chap 2

11/20/99 6040.15D

condition. This code is not to be used to describe the loss of non-FAA (or leased) lines/circuits.

Supplemental Cause Codes: 0 Anomalous Propagation 1 ECM/ECCM/Chaff 2 Path Fade 3 RFI/Intentional Interference 4 Solar Activity 9 Other

85 Nature/Weather Effects. Transient environmental conditions which cause a facility/service interruption. Examples: snowdrifts affecting monitor operations, ice buildup on antennas, weather damage, and lightning.

Supplemental Cause Codes: 0 Snow 1 Ice 2 Wind/Tornado/Hurricane 3 Lightning Strike 4 Flood 5 Rain 6 Temperature Extremes/Variations 7 Birds/Animals/Insects 8 Earthquake/Volcanic event 9 Fire

86 Software. Unscheduled interruptions caused by operational or control software. This code should be used only if it is reasonably certain that software programming was the cause and will be used only in conjunction with service reporting.

Supplemental Cause Codes: 0 Operational Program Abort 1 Operational Program Hang 2 I/O Lockout 3 Monitor/Control Software 4 Other software problem 5 Instruction Set

87 Unknown. This code shall be used for those situations where the cause of the interruption is not specifically known or no logical explanation for the problem can be given. Do not use this code if it is reasonably certain that the problem is either equipment, software, weather, power, or commercial lines. The most likely cause of the interruption need not be known to make this determination. This code may be used in the interim period before the exact cause is known. Once a final determination has been made this cause code shall be changed. Some examples are:

Chap 2 2-11

6040.15D Chg 1 03/28/03

(a) Trouble calls where the specialist arrives at the site and the facility is normal and no problem is found.

(b) A trouble call where the specialist arrives at the site and the facility is not operating normally, but returns to normal operation (self-corrected) prior to the start of troubleshooting.

Supplemental Cause Code: 0 Unknown

88 Related. This code shall be used when a facility or service fails to perform its intended function as a result of an interruption of another facility or service.

Supplemental Cause Codes: 0Caused by a Facility Interruption 1 Caused by a Service Interruption

89 Other. This code shall be used only if the interruption cannot be associated with any other unscheduled cause code. Unscheduled interruptions directly caused by AOS restoration activities, program implementation or key site testing should be coded 89. All personnel errors, with the exception of those related to leased circuits, shall be entered using this code.

Supplemental Cause Codes: 0 AOS Restoration Activities 1 Key Site Testing 2 Program Implementation 3 Vandalism 4 Personnel Error – Airport Activities (airport ops, Fixed Base Operations (FBO), etc.) 5 Personnel Error – AF 6 Personnel Error - AT 7 Personnel Error – Other FAA Organization (not AT/AF) 8 Personnel Error -NON-FAA 9 Other

Chap 2 2-12 Par 205

03/28/03 6040.15D Chg 1

206. STATUS CODE “F", TEMPORARILY OUT-OF-SERVICE EVALUATION CRITERIA. In the past, there have been outages on equipment for extended periods of time, that have been due to circumstances beyond anyone's control. This includes facilities out-of-service that have been destroyed by or made unavailable due to natural disasters (outside of the regular cycle of weather patterns for the local area) or man-made disasters (facility fires, vandalism, bombings, etc.). Status code "F" also includes facilities that are waiting to be decommissioned and that decommissioning is foreseen to be greater than 60 days in the future. In order to provide relief for these events, the following criteria have been established. These criteria must be strictly adhered to before any facility can be placed into status “F”. Once approved, status code “F” interruptions will not be captured in the National Outage Data Base (NODB).

a. An evaluation criteria shall be made in writing, by the AXX-400 manager or designee, and forwarded to AOP-200, with the facility and ident of the equipment clearly stated in the request. This request shall include:

(1) Qualifying event and description of the extenuating circumstances surrounding the event.

(2) Affected facility or facilities and their ident(s). Affected service or services and their ident(s).

(3) A detailed explanation delineating the non-operation of the equipment.

(4) The impact of the operation of the NAS due to the loss of the equipment.

(5) What action is being taken to restore the equipment.

(6) Estimation of restoration time (only events that are forecasted to last greater than 30 days shall be processed).

(7) Event shall be closed out, in writing, by the AXX-400 manager or designee when the facility has been restored. Notice of closure of event shall also be forwarded to Headquarters, within 5 days, for completion of processing.

b. The above criteria will be evaluated on a case-by-case basis. Headquarters shall be notified of the event as soon as possible after the start for the status code change date.

207.-209. Reserved.

Chap 2 Par 206 2-13

6040.15D Chg 1 03/28/03

SECTION 2. SPECIFIC REPORTING REQUIREMENTS

SECTION 2. SPECIFIC REPORTING REQUIREMENTS

210. CATEGORIES OF FACILITIES AND SERVICES. All facilities and services are placed in groups according to their type, e.g., Automation, Communication, Surveillance etc. The following is a list of these categories (including paragraph number for reference):

a. Automation Facilities/Services, paragraph 211 (CCCH, DARC, ARTS, TARS, FDAT, etc.)

b. Communication Facilities/Services, paragraph 212 (RCAG, ECOM, RCO, etc.)

c. Navigation and Landing Facilities/Services, paragraph 213 (GS, TACR, NDB, etc.)

d. Surveillance Facilities/Services, paragraph 214 (ASR, BRITE, MODES, TRAD, etc.)

e. Weather Facilities/Services, paragraph 215 (AWP, NXRAD, TDWR, etc.)

f. Power Facility and Service Reporting, paragraph 216 (PCS, PCSS, SX)

211. AUTOMATION REPORTING. Reporting of all automation interruptions requires joint AT and AF coordination and agreement prior to entering the data into MMS.

a. En Route Automation Reporting. All interruptions shall be reportable for a 24-hour day regardless of published non-operational hours. Unscheduled software interruption (operational program aborts, etc.) are not to be reported against the facility (CCCH, DARC, etc.) but shall be reported under the appropriate service (CFAD, CRAD, DRAD, etc.)

(1) Central Computer Complex Host (CCCH), Composite Flight Data Processing Service (CFAD), Composite Radar Data Processing Service (CRAD), Center TRACON Automation System (CTAS), Display System Replacement (DSR), Flight Data Input/Output Center (FDIOC), and User Request Evaluation Tool (URET) Reporting.

(a) CCCH Reporting. The CCCH facility processes flight data and radar data at an ARTCC. A CCCH facility interruption is defined as a loss of the CCCH equipment's capability to fully process all of the flight data and/or radar data required by the operational program. All CCCH-caused interruptions and startovers are to be reported regardless of whether a service interruption resulted. For NAPRS reporting purposes, the peripheral adapter module replacement items (PAMRI) are considered elements of the CCCH facility.

(b) CFAD Reporting. CFAD service covers all the flight data processing (FDP) capability within an ARTCC. A CFAD service interruption is defined as the loss of operationally acceptable FDP capability within the ARTCC. CFAD is considered an umbrella service. Individual Interfacility Data Service (IDAT) and Flight Data Entry and Printout Service (FDAT) reports are not required when a full CFAD interruption is reported. A full CFAD interruption will generate a full related CRAD interruption.

(c) CRAD Reporting. CRAD service is the processing and display of Radar Data Processing (RDP) from all radars serving the ARTCC. A CRAD service interruption is defined as the loss of operationally acceptable digitized radar data from the CCCH or DSR systems regardless of cause. A CRAD service interruption shall be reported even though DARC is serving as a primary system for RDP (See DARC reporting paragraph 21 1a(2)(a) of this order).

Chap 2 2-14 Par 210

03/28/03 6040.15D Chg 1

(d) CTAS Reporting. CTAS can host one of two major operational capabilities: Traffic Management Advisor (TMA) and passive Final Approach Spacing Tool (pFAST). CTAS provides computer automation to enhance the arrival/departure throughput and efficiency of air traffic operations in the extended terminal airspace surrounding major airports.

1 TMA sites: TMA is connected to the CCCH through the HNL and provides Traffic Management Coordinators (TMCs) with a tool to coordinate the arrival traffic flow by graphically depicting the traffic demand and arrival schedules to the adapted airport. Full TMA capability consists of Timeline Graphic User Interface (TGUI), Plan view Graphic User Interface (PGUI) and Meter List. Full (FL) and Reduced Facility/Service (RS) reports will be required for this facility. Loss of all capabilities, (TGUI, PGUI and Meter List) shall constitute a FL outage report. See paragraph 311 for RS reporting.

(e) DSR Reporting. The DSR is a distributed processing display system providing both CCCH processed and DARC processed data to controllers positions via two independent bi-directional data pathways. The two pathways are the Local Communications Network (LCN) supporting CCCH data display/exchange and the Backup Communications Network (BCN) supporting DARC data display/ exchange. Both networks provide Radar Data Processing products to common DSR R positions. The LCN also provides CCCH generated flight plan and flight (non-radar) data, a component of CFAD service, to DSR A and D positions. A DSR interruption is defined as the loss of the DSR system capability to fully distribute, process, and display the HOST/DARC data.

(f) FDIOC Reporting. FDIOC provides an interface between an air traffic controller and the ARTCC computer. A full FDIOC interruption is defined as the complete loss of flight data from both the Printer Control Unit (PCU) and the Central Control Unit (CCU). A complete failure of this system shall result in full FDAT service interruptions and may have impact on AT resulting in a CFAD reduced facility/service (RS) interruption.

(g) URET Reporting. URET Core Capability Limited Deployment (CCLD) system is an initial conflict probe capability to be used as an advisory tool by the controllers at ARTCC's for strategic planning and clearance decision-making. It also provides enhanced electronic flight plan information to the DSR D-position monitor. FL and RS reports shall be required for this facility. Since the URET data will be displayed on the DSR console, loss of the enhanced flight plan information shall be reported as a RS against the CFAD service. Loss of both capabilities, conflict probe and enhanced flight plan information, constitutes a FL outage against the URET facility and a RS shall be entered against the CFAD service. Loss of either capability, but not both, shall require a RS against the URET facility.

(2) Direct Access Radar Channel (DARC), DARC Radar Data Processing Service (DRAD) Reporting.

(a) DARC Reporting. The DARC facility processes the radar data provided from remote sites, completely bypassing the CCCH, but is fed to the DSR for processing and display. A DARC interruption is defined as a loss of the DARC systems capability to fully process and display the required data. All DARC-caused interruptions and startovers are to be reported regardless of whether a service interruption resulted. Software related DARC interruptions shall be reported as an interruption to the DRAD service.

(b) DRAD Reporting. A DRAD service interruption is defined as the loss of the radar data processing functions of the DARC system resulting in the loss of operationally acceptable digitized radar. A DRAD service interruption shall be reported when DARC reporting is required.

Chap 2 Par 211 2-15

6040.15D Chg 1 03/28/03

(3) En Route Automated Radar Tracking System (EARTS), Micro En Route Automated Radar Tracking System (MEART) and En Route Terminal Automated Radar Service (ETARS) Reporting. Control services provided by CERAP (San Juan) and other en route facilities utilizing ARTS equipment (Anchorage and Honolulu) shall report facility interruptions as EARTS/MEART and service interruptions as ETARS. The reporting criteria used for ARTS and TARS, paragraphs 21 1b(1) & (6), will apply to EARTS/MEART and ETARS.

(4) Oceanic Display and Planning System (ODAPS), Composite Oceanic Display and Planning Service (CODAP) Reporting.

(a) ODAPS Reporting. The ODAPS facility processes and displays oceanic flight data at selected ARTCC facilities. A full ODAPS interruption is defined as a complete loss of the capability of the ODAPS equipment to process and display oceanic flight data.

(b) CODAP Reporting. CODAP service covers all oceanic flight data processing and display through extrapolation of flight plan information. A complete loss of this service shall be reported as a full interruption. All software interruptions shall be reported against the CODAP service. Reduced facility/service (RS) reporting requirements are applicable for the CODAP service. An example of reduced facility/service reporting may be the loss of the oceanic display channel function.

(5) Offshore Flight Data Processing System (OFDPS), Composite Offshore Flight Data Service (COFAD) Reporting.

(a) OFDPS Reporting. The OFDPS facility processes offshore flight data at selected facilities. An OFDPS interruption is defined as a complete loss of the OFDPS equipment's' capability to process flight data. Only the ZHN-OFDPS facility is reportable. Reportable equipment requirements are applicable. The OFDPS facility will provide flight data to several remote towers. This data shall be identified as FDAT services. See FDAT reporting for additional reporting requirements. When ZOA-ODAPS and ZHN-OFDPS are fully operational, flight data information will be transmitted between each site. These data shall be identified as an IDAT service. (See IDAT reporting, paragraph 21 1c(3)(b), for additional reporting requirements.)

(b) COFAD Reporting. COFAD service covers all offshore flight data processing within the OFDPS. A complete interruption of this service shall be reported as a full interruption. All software interruptions shall be reported against the COFAD service. The COFAD service shall exist only for the ZHN-OFDPS.

b. Terminal Automation Reporting.

(1) Automated Radar Terminal System (ARTS) Reporting. ARTS facility reporting shall cover the complete loss of usable alphanumerics caused by interruptions of the ARTS equipment located in the control facility. All interruptions are reportable for a 24-hour day regardless of published non-operational hours. The control and remote location field in the FSEP for ARTS and TARS shall carry the same identifier as the ARTS facility. Software interruptions shall be reported under the TARS service only.

(2) Standard Terminal Automation Replacement System (STARS). STARS consists of dual Full Service (FS) processors and dual Emergency Service (ES) processors. This provides multiple redundancy for the system. STARS equipment is capable of processing multiple Airport Surveillance Radar (ASR) and Air Route Surveillance Radar (ARSR) inputs. Most STARS locations will process at least one ASR and one ARSR. Full (FL) and Reduced Service (RS) reports will be required for this facility. Loss of both FS and ES capability constitutes a Full outage. Loss of either FS or ES capability shall require a Reduced Service report against the TARS. Loss of any component that eliminates redundancy in either the FS or ES string shall require a Reduced Service report against the TARS.

Chap 2 2-16 Par 211

6040.15D Chg 1 03/28/03

(3) Flight Data Input/Output Remote (FDIOR) Reporting. FDIOR provides direct interface between a remote air traffic control (ATC) facility and an ARTCC. A full FDIOR interruption exists when a Remote Control Unit (RCU) is inoperative; when all Replacement Alphanumerics Keyboards (RANK) are not available for input; or when all of the Flight Strip Printers (FSP) are not available for output. Component failures that do not constitute a full interruption but create an impact on air traffic shall be reported as a reduced facility/service interruption.

(4) Radar Beacon Data Processor Equipment (RBDPE) Reporting. RBDPE facility reporting shall cover the complete loss of usable numerics caused by interruptions of the RBDPE equipment located in the control facility. For reporting purposes, do not include the numeric generation conversion equipment (NGCE) as part of RBDPE. Interruptions attributed to NGCE will be reported under TARS. All interruptions are reportable for a 24-hour day regardless of published non-operational hours.

(5) Remote Tower Alphanumeric Display Service (RTADS) Reporting. RTADS interruption reports are required during the loss of usable alphanumerics at satellite towers, regardless of the type of remoting. All interruptions caused by a TARS/ARTS interruption are reportable for a 24-hour day regardless of published non-operational hours. The location identifier for RTADS is the identifier of the terminal where the service is provided. The control and remote location field in the FSEP shall carry the terminal and radar site identifier, respectively. A reduced service (RS) RTADS service interruption shall be reported when in CENRAP operation (CENRAP shall be indicated as back-up). CENRAP operation shall be indicated on the LIR remarks/comment screen.

(6) Terminal Automated Radar Service (TARS) Reporting. TARS interruption reports are required during the loss of usable alphanumerics on all operational positions used for air traffic control at automated radar terminal facilities equipped with ARTS. At terminals equipped with RBDPE (TPX-42), TARS interruptions will be reported for a loss of usable alphanumerics on all operational positions. All interruptions are reportable for a 24-hour day regardless of published non-operational hours. A reduced service (RS) TARS service interruption shall be reported when in CENRAP operation (CENRAP shall be indicated as back-up). CENRAP operation shall be indicated on the LIR remarks/comment screen.

(7) CTAS Reporting. CTAS can host one of two major operational capabilities: Traffic Management Advisor (TMA) and passive Final Approach Spacing Tool (pFAST). CTAS provides computer automation to enhance the arrival/departure throughput and efficiency of air traffic operations in the extended terminal airspace surrounding major airports.

1 pFAST sites: Full pFAST capability consists of Timeline Graphic User Interface (TGUI), Plan view Graphic User Interface (PGUI) and Runway/Sequence Data Block information. Full (FL) and Reduced Facility/Service (RS) reports will be required for this facility. Loss of all capabilities, (TGUI, PGUI and Runway/Sequence Data Block information) shall constitute a FL outage report. See paragraph 311 for RS reporting.

Chap 2 Par 211 2-17

6040.15D Chg 1 03/28/03

c. Other Automation Reporting.

(1) Automated Flight Service Station (AFSS), Flight Service Data Processing System (FSDPS), Flight Service Station Automated Service (FSSAS), Flight Service Station Processing Service (FSSPS) Reporting.

(a) AFSS Reporting. A full AFSS interruption is defined as the failure of the Flight Service Data Processing System (Model 1 Full Capacity) and the capability to display processed data (automation equipment only).

(b) FSDPS Reporting. A full FSDPS interruption is defined as the loss of the capability to fully process all flight data required by the operational program due to a failure in one or more of the hardware or software elements (ARTCC equipment only).

(c) FSSAS Reporting. The FSSAS is the transfer and display of flight service data at each AFSS facility. Each FSSAS will be assigned the identifier of the AFSS facility. There will be an FSSAS for each FSDPS to AFSS configuration. A complete loss of the ability to transfer or display flight service data at an AFSS facility, including hardware/software elements at either the FSDPS or AFSS, shall be reported as a full FSSAS interruption. FSSAS interruption reports shall not be made if the cause of the interruption requires a full FSSPS report. ARTCC is the control facility for the FSSAS service.

(d) FSSPS Reporting. The FSSPS is the processed data provided to and displayed on the AFSS equipment. A full FSSPS interruption is the loss of displayed data to all AFSS facilities associated with the failure of a single FSDPS. FSSPS is considered an umbrella service. Individual FSSAS reports are not required when a full FSSPS interruption is reported.

Chap 2 2-17a (and 2-17b) Par 211

(This page intentionally left blank)

6040.15D 11/20/99

(2) Enhanced Traffic Management System (ETMS) Service Reporting. An ETMS service interruption is defined as the complete loss of all service data. Specifically this is identified as: loss of all flight data processing at the Enhanced Traffic Management computer complex; loss of data due to transmission difficulties; or loss of processing or display capability at an individual traffic management unit (TMU). TMU operations personnel have the responsibility of reporting loss of service to appropriate AF personnel. Interruptions of any flight data processing, transmitting, or display shall be reported against the appropriate ETMS service. Transmission of data may be via earth station to satellite facilities, or via leased lines. Each ETMS service shall be identified by the TMU/ARTCC or TRACON identifier.

(3) Flight Data Entry and Printout Service (FDAT), Interfacility Data Service (IDAT) Reporting.

(a) FDAT Reporting. FDAT service is the flight data processing/transfer capability existing between an ARTCC facility and a single remote FDIOR facility, inclusively. An FDAT interruption is defined as the loss of operationally acceptable flight data capability from the ARTCC to and including the remote FDIOR. CCCH/FDIOR interface problems that affect selective FDIOR sites will be reported under the appropriate FDAT service. FDAT reporting is assigned to the ARTCC. The FDAT service will be identified by the same location identifier as the remote FDIOR facility. Military-owned and maintained FDIOR sites will be reported utilizing the FDAT service report.

(b) IDAT Reporting.

1 IDAT service is the interfacility data information interchange capability existing between the ARTCC CCCH and the individually associated interfacility data system (IFDS) sites; i.e., TRACON/ARTS, traffic management computer complex (TMCC) facility, or another ARTCC facility, inclusively. An IDAT service interruption is defined as the loss of operationally acceptable data communications capability from the ARTCC to the remote site. An IDAT service is not reportable when the ARTS facility is out of service unless hardware/software malfunction in the ARTS is directly related to the failure of the data communications capability.

2 IDAT reporting is assigned to the ARTCC. The location identifier will be that of the ARTS facility for ARTS/ARTCC IFDS installations. For ARTCC/ARTCC IFDS sites, the basic identifier will be that of the geographically most eastern ARTCC, with appropriate suffixes added in inverse alphabetical order when the most eastern ARTCC has interfacility data to more than one ARTCC; e.g., the IDAT service between Atlanta and Memphis, Houston and Indianapolis ARTCCs would be identified as ZTL, ZTLZ and ZTLY. The geographically most eastern center will be considered the reporting ARTCC. The reporting ARTCC will be identified as the control location in the FSEP. For TMCC/ARTCC IFDS sites, the ARTCC will be considered the reporting site for the service. For TMCC/NY TRACON IFDS sites, the NY TRACON will be considered the reporting site for the service. In addition, the ARTCC/NY TRACON sites shall use its basic identifier and any appropriate suffix, if required, for the services between the ARTCC/NY TRACON and TMCC facilities.

NOTE: When IDAT and FDAT services are multiplexed on the same data circuit, a loss of the data circuit shall cause an interruption to each service. These services must be reported in MMS, entering the IDAT service on the initial LIR screen and the remaining service(s) on the associated/related screen. In addition, the IDAT line number must be added to the appropriate

2-18 Chap 2

2-18 Chap 2

11/20/99 6040.15D

screen if leased circuits caused the interruption. If a backup was used to prevent or shorten the service interruption, appropriate backup information must be added.

(4) Maintenance Processor Subsystem (MPS), MPS Service (MPSS) Reporting.

(a) MPS Reporting. The MPS is defined as the Tandem hardware platform that provides the operational environment for the Tandem Guardian Operating System (OS), the MMS, and the Interim Monitor and Control Software (IMCS). A full MPS interruption is defined as a hardware failure of such magnitude that the MMS and IMCS applications are not operational and providing intended functions and services.

(b) MPSS Reporting. The MPSS is defined as the combination of MMS and IMCS applications being up and running under the current OS. All functionality of both applications must be available. A full MPSS interruption is defined as loss of both MMS and IMCS or the OS. Reduced facility/service reporting requirements are applicable for the MPSS. An example of reduced facility/service reporting is the loss of MMS or IMCS.

(5) National Data Interchange Network (NADIN), NADIN Switch Service (NADS), NADIN Message Transfer Service (NAMS), NADIN Data Interchange Service (NDAT) Reporting. This section provides guidelines for reporting scheduied and unscheduled interruptions to NADIN services and facilities.

(a) NADIN Reporting. A NADIN facility consists of equipment located at the switching centers at Atlanta, Georgia (ATL), or Salt Lake City, Utah (STL), or equipment comprising the concentrator at each ARTCC. This equipment processes, controls, and transfers data among the switching center and various terminals in and external to the ARTCC. A NADIN facility full interruption is defined as the complete loss of capability to process, control, and transfer data at either switching center or at a constituent concentrator (ARTCC). NADIN facility reporting responsibility is assigned to each individual switching center and ARTCC (concentrator).

(b) NADS Service Reporting. NADS covers all message data processing at the NADIN switching center. A full NADS interruption is defined as a complete loss of operationally acceptable message data processing capability between a switching center and all its constituent concentrators. There will be one NADS service for each NADIN switching center. NADS is considered an umbrella service. Individual NAMS reports are not required when a full NADS service interruption is reported.

(c) NAMS Reporting. NAMS covers the transfer of message data between the NADIN switching center to a NADIN concentrator. A full NAMS interruption is defined as a complete loss of the message data transfer capability to a NADIN concentrator. Failure of the NADIN Concentrator to complete the data transfer constitutes full NAMS interruption reporting. The start time of the interruption shall be the time at which the NADIN switch declares the concentrator is in isolation. NAMS interruption reporting is a function of the NADIN switching center. A separate NAMS shall be established for each switching center to concentrator configuration. Each NAMS will be identified by the concentrator's identifier. Reporting responsibility is assigned to the associated NADIN switching center. The use of dial backup lines to the concentrators can be used to backup the NAMS service from the switching centers.

(d) NDAT Reporting. NDAT service is the data interchange capability between the two NADIN switching centers. An NDAT service interruption is defined as a complete loss of this data

Chap 2 2-19

6040.15D Chg1 03/28/03

interchange capability. An NDAT interruption will be reported as the result of a failure or out-of-tolerance condition of all data lines connecting the facilities which causes a degradation of the system beyond acceptable use. NDAT reporting is assigned to the ATL switching center. ATL switching center shall make an appropriate NDAT entry in the FSEP indicating ATL as the control site. Dial backup lines can be used to backup the NDAT service between switching centers.

(6) Central Flow Control Service (CFCS) Reporting. CFCS is the service provided by the TMCC. All service interruptions of the TMCC are reportable. The reporting responsibility for CFCS is assigned to the Air Traffic Control System Command Center (ATCSCC) in Herndon, VA. CFCS is supported by several IDAT services. (See paragraph 21 1c(3)(b) for IDAT reporting requirements.)

212. COMMUNICATION REPORTING.

a. En Route Communication Reporting.

(1) Backup Emergency Communications (BUEC), BUEC Service (BUECS) Reporting.

(a) BUEC Reporting. BUEC is a backup air-to-ground radio communications facility, generally remotely located, serving an ARTCC's control area. Report only interruptions that pertain directly to the BUEC facility. Interruptions caused by interference and FAA or TELCO line/link failures shall not be reported as BUEC interruptions but shall be reported for the BUECS (service) affected. A full BUEC interruption is the complete loss of ability to transmit or receive at a single BUEC location.

(b) Sustained Backup Emergency Communications. Sustained BUEC has been identified in the Facility, Service and Equipment Profile (FSEP) with a facility identification code under BUEC. The sustained BUEC code is 41BC. A sustained BUEC full interruption is the complete loss of ability to transmit and/or receive voice communications or the degradation of the equipment to the point where service is unusable on a single frequency.

(c) BUECS Reporting. BUECS is the air-to-ground radio communications service provided by a single BUEC site to an ARTCC facility. The BUECS consists of communication equipment at the BUEC site and associated selecting equipment at the ARTCC facility. A full BUECS interruption shall be reported when a system is completely unavailable for service (e.g., loss of all communication equipment at a BUEC site, a complete loss of capability to select a BUEC site, or the loss of all lines to a BUEC site). In the event of any BUECS component failures that do not constitute a full interruption, a reduced facility/service (RS) report shall be made. Whenever possible, the remarks field shall contain, at a minimum, the AT sector affected and the identifier of the controlling ARTCC facility. Reporting responsibility is assigned to the controlling ARTCC facility. BUECS entries in the FSEP shall be made by the controlling ARTCC using its cost center, identifier of the BUEC site, and indicating the ARTCC as the control facility.

(2) Remote Center Air/Ground Communications Facility (RCAG), En Route Communications Service (ECOM) Reporting. ECOM and RCAG interruptions shall be reported when one or more frequencies are out of service. A frequency is out of service when the transmit or receive function or both are inoperable or when performance is degraded to the point where the service is unusable. Continuation of service by use of standby equipment, with the same frequency, located at the same RCAG facility does not constitute an interruption. ECOM services, from adjacent RCAG facilities with common frequencies, will not be considered a backup for another ECOM service.

Chap 2 2-20 Par 211

11/20/99 6040.15D

(a) ECOM Reporting. ECOM reports provide the en route air/ground communication service picture as seen by the ARTCC. An ECOM report shall be required even when backup communications equipment (BUEC, RML/RCL, selective signaling (SS-I), etc.) is used to prevent or reduce the duration of the service interruption. The ECOM location identifier will be the same as the remote RCAG site. ECOM interruption reports are required even when an appropriate backup system is used.

(b) RCAG Reporting. Report only interruptions that pertain directly to the RCAG facility. Any equipment, lines, or other components on the FAA side of the demarcation point is reportable as part of the RCAG facility. Interruptions caused by interference and FAA or TELCO line/link failures shall not be reported as RCAG interruptions but shall be reported by the ARTCC as ECOM service interruptions.

(3) Voice Switching and Control System (VSCS), Voice Switching and Control System Service (VSCSS) Reporting, VSCS Emergency Access Radio System (VEARS), VSCS Training and Backup Switch (VTABS) Reporting: The VSCS provides ARTCC facilities with three types of voice communications; radio (air-to-ground), interphone, and intercom.

(a) VSCS Reporting. VSCS equipent failures which result in the loss of all ECOM services shall be reported as a full VSCS interruption. Any hardware failure which does not constitute a full interruption and creates an impact on AT operations shall be reported as a reduced facility/service (RS)VSCSS interruption.

(b) VSCSS Reporting. A full VSCSS interruption is defined as the inability to provide airto-ground communications to the controller. A reduced facility/service VSCSS report is required for the loss of one or more, but not all, air-to-ground services. The loss of any interphone capability shall be reported as reduced facility/service (RS) VSCSS interruption. Interruptions caused by software failures shall be reported as a VSCSS interruption. VSCSS is considered an umbrella service, individual ECOM reports are not required when a full VSCSS interruption is reported.

(c) VSCS Emergency Access Radio System (VEARS) Reporting. VEARS provides access to emergency back-up communications from the Air Traffic Controller position to a specific Remote Center Air/Ground Communication (RCAG) facility radio(s). VEARS equipment failures which result in the loss of all voice communications shall be reported as a full interruption against the facility. Any VEARS hardware failure which result in the inability to operate in the standby configuration shall be reported as a full interruption against the facility. Any VEARS hardware failure which does not constitute a full interruption, but creates an impact on Air Traffic operations, shall be reported as a reduced facility/service interruption against the facility.

(d) VSCS Training and Backup Switch (VTABS) Reporting. VTABS allows for access to air-to-ground and ground-to-ground communications resources independently of VSCS in the event of a catastrophic failure of the VSCS, loss of power sources, or planned/unplanned maintenance activities that necessitate taking the VSCS out of service. VTABS is configured in a hot-standby mode to the VSCS. VTABS equipment failures which result in the loss of all ECOM services shall be reported as a full interruption. Any hardware failure which does not constitute a full interruption and creates an impact on AT operations shall be reported as a reduced equipment outage. Any hardware failure which does not constitute a full interruption and creates an impact on providing communications capability in the Dynamic Simulation (DYSIM) laboratory shall be reported as a reduced equipment outage.

Chap 2 2-21

6040.15D 11/20/99

b. Terminal Communication Reporting.

(1) Remote Transmitter/Receiver (RTR) Reporting. Interruptions shall be reported when one or more frequencies are out of service. Report only interruptions that pertain directly to the RTR facility. A frequency is out of service when the transmit or receive function, or both, is inoperable or when performance is degraded to the point where service is unusable.

(2) Terminal Communications Service (TCOM) Reporting. Individual air/ground frequency interruptions at airports shall be reported as TCOM service interruptions. A frequency is out of service when the transmit or receive function, or both, is inoperable or when performance is degraded to a point where the service is unusable at the control facility. The use of service fault location and remarks will be used to identify the facility or equipment that caused the interruption. The TCOM service shall be identified by the remote facility's or family of facilities' ident. A “family" of RTR facilities is one or more RTR facilities at a single geographic location supporting one control facility. Each RTR facility within the “family" must have the same basic three letter identifier. A TCOM service shall be established at the control facility for each "family" of RTR facilities. Idents for multiple TCOM services for a single geographic location shall be distinguished by use of a suffix in addition to the basic three letter identifier. A TCOM report shall be required even when backup communications equipment is used to prevent or reduce the duration of the service interruption.

(3) Terminal Voice Switch (TVS). TVS facilities provide switching between communication devices at Air Traffic Control Tower (ATCT), Terminal Radar Approach Control (TRACON), Automated Flight Service Station (AFSS), and Flight Service Station (FSS) facilities. Equipment types identified under the TVS heading are Small Tower Voice Switch, Enhanced Terminal Voice Switch and Rapid Deployment Voice Switch. All interruptions to these equipment shall be reported as TVS facility interruptions. The inability of the equipment to transmit and/or receive voice communications at all positions shall constitute a full TVS interruption. Any TVS component failure which does not constitute a full interruption, but creates an impact to Air Traffic operations shall be reported as a reduced facility/service (RS) interruption against the TVS. In addition, if any TVS component failures cause the loss of a reportable service (i.e. Terminal Communications, FSS Communications) then the affected services shall be reported as a full interruption.

c. Other Communication Reporting.

(1) Automatic Terminal Information System (ATIS) Reporting. The ATIS provides a continuous broadcast of the latest terminal information to NAS users. ATIS is comprised of recording equipment usually located at the tower, land line, and a transmitter (usually collocated at a RTR site). A full interruption report is required when the ATIS is unable to provide a continuous broadcast of updated information. (2) Fiber Optics Transmission System (FOTS) Reporting. The FOTS converts information for fiber optics transmission and then reconverts the information back to the original form at the output destination. The loss of all FOTS capabilities shall require full interruption reporting. Reduced facility/service reporting shall be used to indicate the system's inability to transmit information on one or more, but not all, FOTS circuits.

(3) Ground Air Transmit/Receive Facility (GATR) Reporting. Interruptions shall be reported whenever one or more frequencies are out of service. A frequency is out of service when the transmit or receive function, or both, is inoperable or when performance is degraded to the point where service is unusable. Report only interruptions that pertain directly to the GATR. Interruptions caused by

Continue reading ↓ 120 of 292 passages shown