Radar Vectors
FAA Order Cancelled Issued Oct 6, 2006 AJT-1 151 pages Copy saved Nov 18, 2026

Order 6191.3 Standard Terminal Automation Replacement System (STARS) Maintenance Technical Handbook

This document is cancelled. Cancelled by 6191.3A. Check the official source before relying on it.

Official source ↗ Open PDF

U.S. DEPARTMENT OF TRANSPORTATION

ORDER JO 6191.3

STANDARD TERMINAL AUTOMATION REPLACEMENT SYSTEM

(STARS)

MAINTENANCE TECHNICAL HANDBOOK

FINAL

November 16, 2006

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

DISTRIBUTION: STARS FAA and DoD Operational

and Support Locations

INITIATED BY: Terminal Field Operational

Support, STARS

RECORD OF CHANGES DIRECTIVE NO. JO 6191.3

CHANGE TO BASIC SUPPLEMENT OPTIONAL CHANGE TO BASIC SUPPLEMENT OPTIONAL

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

DETAILED CHANGE HISTORY

Revision Number Date Purpose or Associated Software Release FAA Change Mechanism

(PTR, HDR, DDR, CCD)

Affected Pages/Sections

FINAL 11/16/2006 First Release of Final STARS MHBK

• Change 6191.XX to JO 6191.3

CCD # 25779 All Pages

Page i

FOREWORD

1. PURPOSE.

This handbook provides guidance and prescribes technical standards, tolerances, and procedures applicable to the maintenance and inspection of the Standard Terminal Automation Replacement System (STARS). It also provides information on special methods and techniques that will enable maintenance personnel to achieve optimum performance from the equipment. This information augments information available in instruction books and other handbooks, and complements the latest edition of Order 6000.15.

2. DISTRIBUTION.

This directive is distributed to offices and services within Washington headquarters, the William J. Hughes Technical Center, the Mike Monroney Aeronautical Center, regional Air Traffic Organization (ATO) divisions, Department of Defense (DoD) facilities, and ATO field offices having the following facilities/equipment: STARS. An electronic version of this handbook is available on an Federal Aviation Administration (FAA) Intranet site located at http://nasdoc.faa.gov/ and a DoD accessible website at http://www.dod.tc.faa.gov.

3. CANCELLATION. Not Applicable.

4. EXPLANATION OF CHANGES. Not Applicable.

5. MAINTENANCE AND MODIFICATION PROCEDURE.

a. Order 6000.15, this handbook, the applicable equipment TI Manuals, and other

applicable handbooks shall be consulted and used together by the maintenance technician in all duties and activities for the maintenance of STARS. These documents shall be considered collectively as the single official source of maintenance policy and direction authorized by the Terminal Operations (ATO)-T). References located in the appropriate paragraphs of this handbook titled Chapter 3, Standards and Tolerances; Chapter 4, Periodic Maintenance; and Chapter 5, Maintenance Procedures shall indicate to the user whether this handbook and/or the equipment instruction book shall be consulted for a particular standard, key inspection element, performance parameter, performance check, maintenance task, or maintenance procedure.

b. The latest edition of Order 6032.1b, National Airspace System Modification Program,

contains comprehensive direction concerning the development, authorization, implementation, and recording of modification to facilities, systems, and equipment in commissioned status. It supersedes all instructions published in earlier editions of maintenance technical handbooks and related directives.

6. FORMS LISTING.

In addition to the forms required by Order 6000.15, FAA Form 6000-8, Technical Performance Records (TPRs) are required for numeric values. The TPRs include non-numeric checks for convenience as a checklist tool for PM tracking. STARS provides a reproducible Updated Software Chart and reproducible TPRs in this handbook as identified below:

• Figure 5 – 1. STARS Updated Software Chart

• Figure 5 – 2a. STARS Daily Technical Performance Record

• Figure 5 – 2b. STARS Weekly Technical Performance Record

• Figure 5 – 2c. STARS Monthly Technical Performance Record

• Figure 5 – 2d. STARS Quarterly Technical Performance Record

• Figure 5 – 2e. STARS Semiannual Technical Performance Record

Page ii

• Figure 5 – 2f. STARS As Required Technical Performance Record

• FMA Figure 1 - STARS FMA Daily/Weekly Technical Performance Record

• FMA Figure 2 - STARS FMA Quarterly/Annual Technical Performance Record

7. RECOMMENDATIONS FOR IMPROVEMENT.

This handbook is under configuration management control as defined in the latest edition of Order 1800.8, NAS Configuration Management, and NAS-MD-001, National Airspace System Configuration Management Document. Any changes to the baseline document or requests for deviation from national standards shall be processed through the NAS Change Proposal (NCP) process.

Teri L. Bristol

Director of Terminal Program Operations

Page iii

TABLE OF CONTENTS CHAPTER 1. GENERAL INFORMATION AND REQUIREMENTS … 1 100. Objective … 1 101. Safety … 1 102. Certification … 1 103. Aircraft Accident … 2 104. Coordination … 2 105. Flight Inspection … 3 106. Technical Inspection … 3 107. Periodic Maintenance … 3 108. Test Equipment And Tools For Periodic Maintenance … 3 109. Modification Policy … 3 110. Maintenance And Diagnostic Manuals … 4 111. FAA Forms … 4 112. FAA Orders And Handbooks … 4 113. System Security … 4 114. JumpSTARS Policy … 4 115. – 199. Reserved … 5 CHAPTER 2. TECHNICAL CHARACTERISTICS … 6 200. Purpose … 6 201. System Introduction … 6 202. FSL System Functional Description … 8 203. ESL System Functional Description … 10 204. EASL System Functional Description … 11 205. STARS Block Diagram … 11 206. – 299. Reserved … 11 CHAPTER 3. STANDARDS AND TOLERANCES … 15 300. General … 15 301. FSL NUNIO … 16 302. FSL CGW … 16 303. FSL RDP … 16 304. FSL TCW … 16 305. FSL TDW … 17 306. FSL MCW … 17 307. FSL CDR … 17 308. FSL Standby Resources … 17 309. TSATD FSL Service Certification And Target Parameters … 17 310. STARS FSL Subsystem Certification … 19 311. ESL NUNIO … 19 312. ESL CGW … 20 313. ESL TCW … 20 314. ESL TDW … 20 315. ESL MCW … 20 316. ESL Standby Resources … 21

Page iv

317. TSATD ESL Service Certification … 21 318. STARS ESL Subsystem Certification … 22 319. AIA … 23 320. TSATD EASL Service Certification … 23 321. STARS EASL Subsystem Certification … 24 322. STARS Certification Range/Azimuth Check … 25 323. STARS System Certification Radar Reliability Check And Sensor Performance Parameters … 26 324. GIAFP Service Certification … 29 325. Registration … 29 326. SSS … 29 327. SIM … 29 328. GPW … 30 329. TDW Monitor … 30 330. Sony Data Display Monitor (DDM) Check … 30 331. Firewall/WAN Router Performance Check … 31 332. FSL Software Release Maintenance … 31 333. ESL Software Release Maintenance … 31 334. FSL Software Update … 31 335. ESL Software Update … 32 336. Map Alignment … 32 337. Fixed Target Map … 32 338. GPS System Clock And Synchronization … 32 339. Aural Alarm … 32 340. RTDS Target Display Check … 32 341. Service Level Availability Check … 32 342. ES ARTS Sync Function … 33 343. FS Periodic Certification Test Variable Site Parameter (VSP) … 33 344. ES Background Verification … 33 345. RTDS Data Entry Processing And Display Check … 33 346. Test Target Deviation … 34 347. FSCK File System Checker … 34 348. FSL/ESL Synchronization … 34 349. GPS DAC Value … 34 350 - 399. Reserved … 34 CHAPTER 4. PERIODIC MAINTENANCE … 35 400. General … 35 SECTION 1. PERFORMANCE CHECKS … 36 SUBSECTION 1. FSL PERFORMANCE CHECKS … 36 401. Daily … 36 402. Weekly … 36 403. Biweekly … 36 404. Monthly … 36 405. Quarterly … 36 406. Semiannually … 36

Page v

407. Annually … 37 408. Biannually … 37 409. Triannually … 37 410. As Required … 37 411. – 414. Reserved … 37 SUBSECTION 2. ESL PERFORMANCE CHECKS … 38 415. Daily … 38 416. Weekly … 38 417. Biweekly … 38 418. Monthly … 38 419. Quarterly … 39 420. Semiannually … 39 421. Annually … 39 422. Triannually … 39 423. As Required … 39 424. – 459. Reserved … 39 SECTION 2. OTHER MAINTENANCE TASKS … 40 460. Daily … 40 461. Weekly … 40 462. Biweekly … 40 463. Monthly … 40 464. Bimonthly … 40 465. Quarterly … 40 466. Semiannually … 40 467. Annually … 40 468. Triannually … 41 469. As Required … 41 470. – 499. Reserved … 41 CHAPTER 5. MAINTENANCE PROCEDURES … 42 500. General … 42 501. Technical Performance Record Entries … 42 502. – 509. Reserved … 42 SECTION 1. PERFORMANCE CHECK PROCEDURES … 43 510. STARS FSL/ESL/DRF Subsystem Procedure for Resource Verification Test … 43 511. MCW Icon and System Message Check … 43 512. TSATD FSL Test Target Display Check … 44 513. TSATD ESL/DRF Test Target Display Check … 44 514. TSATD EASL Test Target Display Check … 45 515. General Information Automated Flight Plan (GIAFP) Flight Data Processing Input/Output Check...46 516. STARS FSL Procedure For Performance Verification Of ATC Visual And Aural Alarms … 46 517. Reserved … 49 518. STARS FSL Subsystem Certification Procedure Radar Data Processing and Display Capability....49 519. STARS System Certification Procedure for FSL Back-Up Data Processing System (ESL/DRF) … 50 520. STARS System Certification Range/Azimuth Integrity … 51

Page vi

521. Stars FSL Subsystem Certification Radar Reliability Check Using the RTQC Check Report … 53 522. STARS ESL Procedure For Performance Verification Of ATC Visual And Aural Alarms … 54 523. Reserved … 57 524. STARS ESL Subsystem Certification Procedure - Radar Data Processing and Display Capability. 57 525. STARS EASL Subsystem Certification Procedure for Data Entry and Display Functions … 57 526. STARS EASL Subsystem Certification Procedure - Radar Data Processing / Display Capability....58 527. STARS System Certification Procedure for FSL Back-Up Data Processing System (EASL) … 59 528. Procedure to Run LDDT … 60 529. Procedure to Configure FSL to Utilize the Standby Resources … 62 530. Network Information System Plus (NIS+) Check … 63 531. Procedure to Configure ESL/DRF to Utilize Standby Resources … 65 532. Reserved … 65 533. Registration … 66 534. Reserved … 68 535. Test Target Range/Azimuth Deviation Check … 68 536. Alternative Certification Method Using Registration Analysis … 72 537. Alternative Certification Method Using Visual Checks … 73 538. – 549.

Reserved … 73 SECTION 2. OTHER MAINTENANCE TASKS PROCEDURES … 74 550. FSL Software Release Maintenance … 74 551. ESL Software Release Maintenance … 75 552. FSL Software Update Checks … 76 553. ESL Software Update Checks … 77 554. Firewall/WAN Router Connectivity Performance Check … 78 555. Map Alignment Check … 80 556. Fixed Target Map … 80 557. GPS DAC Value check … 81 558. Blower Fan and Filter Inspection and Cleaning … 82 559. Rack Cabinet Physical Inspection and Cleaning … 82 560. TCW Cabinet Physical Inspection and Cleaning … 83 561. Check Connector Mating … 83 562. TDW Articulating Arm Check … 83 563. TDM HEPA Filter Inspection and Cleaning … 84 564. – 569. Reserved … 84 SECTION 3. SPECIAL MAINTENANCE PROCEDURES … 85 570. FSCK After Interruption Of Power … 85 571. – 598. Reserved … 85 CHAPTER 6. FLIGHT INSPECTION … 93 600. General … 93 601. – 699. Reserved … 93

Page vii

APPENDICES APPENDIX 1. CERTIFICATION REQUIREMENTS … 94 1. General … 94 2. Services … 94 3. Systems … 94 4. Exceptions … 94 5. Transition Phase … 95 6. Future Systems … 95 APPENDIX 2. GLOSSARY OF ACRONYMS AND TERMS … 104 APPENDIX 3. DOCUMENTATION AND FORMS … 110

ATTACHMENT ATTACHMENT 1 - FMA ON STARS MAINTENANCE HANDBOOK … 113

LIST OF FIGURES FIGURE 2 – 1. TRANSITION PHASE … 12 FIGURE 2 – 2. TYPICAL SOS … 13 FIGURE 2 – 3. TYPICAL REMOTE TOWER … 13 FIGURE 2 – 4. REMOTE TOWER WITH LOCAL PRIMARY RADAR … 14 FIGURE 2 – 5. TYPICAL STAND-ALONE TOWER … 14 FIGURE 5 – 1. STARS UPDATED SOFTWARE CHART … 86 FIGURE 5 – 2A. STARS DAILY TECHNICAL PERFORMANCE RECORD … 87 FIGURE 5 – 2B. STARS WEEKLY TECHNICAL PERFORMANCE RECORD … 88 FIGURE 5 – 2C. STARS MONTHLY TECHNICAL PERFORMANCE RECORD … 89 FIGURE 5 – 2D. STARS QUARTERLY TECHNICAL PERFORMANCE RECORD … 90 FIGURE 5 – 2E. STARS SEMIANNUAL TECHNICAL PERFORMANCE RECORD … 91 FIGURE 5 – 2F. STARS AS REQUIRED TECHNICAL PERFORMANCE RECORD … 92

LIST OF TABLES TABLE A1-1. TERMINAL SURVEILLANCE AIRBORNE TARGET DISPLAY (TSATD) SERVICE … 96 TABLE A1-2. GENERAL INFORMATION AIRCRAFT FLIGHT PLANNING (GIAFP) SERVICE … 97 TABLE A1-3. STANDARD TERMINAL AUTOMATION REPLACEMENT SYSTEM (STARS) … 98 TABLE A1-3A. STARS FULL SERVICE LEVEL (FSL) SUBSYSTEM … 99 TABLE A1-3B. STARS EMERGENCY SERVICE LEVEL (ESL) SUBSYSTEM … 100 TABLE A1-3C. STARS EXISTING ARTS SERVICE LEVEL (EASL) SUBSYSTEM … 101 TABLE A1-3D. STARS DIRECT RADAR FEED (DRF) ESL SUBSYSTEM … 102 TABLE A1-4. RADAR TERMINAL DISPLAY SYSTEM (RTDS) … 103 TABLE A2-1. ACRONYMS … 104 TABLE A2-2. TERMS … 108 TABLE A3-1. MAINTENANCE AND DIAGNOSTIC MANUALS … 110 TABLE A3-2. FAA FORMS … 110 TABLE A3-3. FAA ORDERS AND HANDBOOKS … 111

Page viii

102. CERTIFICATION. › d. Certification Statement. The certifying ATSS shall document the…

CHAPTER 1. GENERAL INFORMATION AND REQUIREMENTS

100. OBJECTIVE.

This handbook provides the necessary guidance to be used in conjunction with information available in instruction books and other handbooks for the proper maintenance of Standard Terminal Automation Replacement System (STARS).

101. SAFETY.

Maintenance personnel shall observe all pertinent safety precautions when performing maintenance on the equipment covered in this manual. Refer to the latest edition of Order 6000.15, General Maintenance Handbook for Airway Facilities, for guidance. In addition, maintenance personnel shall comply with all federal and FAA safety regulatory requirements including, but not limited to 29 CFR 1910, OSHA General Industry Standards; 29 CFR 1926, OSHA Safety and Health Regulations for Construction; FAA Order 3900.19B, FAA Occupational Safety and Health Program; FAA-STD-G-2100g, FAA Specifications for Electronic Equipment, General Requirements; and DOT/FAA/CT-03/05 HF-STD-01, Human Factors Design Standard.

102. CERTIFICATION.

Refer to Order 6000.15 for general guidance on the certification of systems, subsystems, and equipment. Refer to Appendix 1, Certification Requirements for the specific certification requirements for STARS.

a. Certification Tables. Each table in Appendix 1 of this handbook lists the certification

levels, associated certification parameters, reference paragraphs, maximum certification intervals, identity of recommended personnel responsible for certification, and the prescribed certification statements to be entered into the facility maintenance log.

b. Certification of Systems. Certification is required for the following service and systems.

1. Terminal Surveillance Airborne Target Display (TSATD) service.

2. General Information Automated Flight Plan (GIAFP) service.

3. STARS system.

(a) Full Service Level (FSL)

(b) Emergency Service Level (ESL)

(c) Existing Automation Service Level (EASL) where EASL is part of the configuration

c. Certification Accomplishment. Certification of the total automation service and the major

subsystems shall be accomplished using the nationally approved procedures prescribed herein. These procedures provide the minimum maintenance tasks and performance checks required for certifying the system. Additional actions may be taken at the discretion of the system/service certified Airway Transportation System Specialist (ATSS). Before additional actions are taken, consideration should be given to the potential impact on ATC operations.

d. Certification Statement. The certifying ATSS shall document the certification by making

the prescribed certification statement from Appendix 1 in the STARS maintenance log.

CHAPTER 1. GENERAL INFORMATION AND REQUIREMENTS › 104. COORDINATION.

e. Levels of Certification. The two levels are the Service Level and the System Level

certification.

1. Service Level. The service level certification encompasses all lower certification levels and indicates that overall service can be used by Air Traffic (AT) for the safe, efficient movement of aircraft within the area covered by the service. As part of the service certification, the certifying ATSS must ensure that certifiable systems and subsystems from the sensor to the display path are performing advertised functions.

2. System Level. The System Level certification verifies that system hardware and software are functioning properly. This level of certification does not include equipment that is not an integral part of the system, such as a sensor. This level of certification also ensures that the correct version of software/firmware is installed on each computer/Local Area Network (LAN) utilized in the system.

f. Certification Following Corrective Maintenance. After corrective maintenance on a Line Replaceable Unit (LRU), the LRU may be returned to the system after verifying that the element functions properly offline. Certification is required only if the failure of the LRU affected a certification parameter found in Appendix 1.

1. The ATSS should determine if the unit is capable of performing its advertised functions.

2. Verify proper operation within the appropriate subsystem using the applicable diagnostics.

3. Return the LRU to the system.

4. Monitor and ensure that the LRU is operating properly in the system.

5. Log the returned element in the facility maintenance log.

g. Certification Responsibility. Certification responsibility is assigned to the appropriate

technical personnel who hold certification credentials granted under the provisions of the latest edition of Order 3400.3, Airway Facilities Maintenance Personnel Certification Program.

103. AIRCRAFT ACCIDENT.

When aircraft accidents or incidents occur, Air Traffic Organization Technical Operations personnel are required, when requested by the Technical Operations Aircraft Accident Representative (AFAAR) through the appropriate control center, to evaluate and document the technical performance of the facilities which may have been involved (for some facilities, it may also be necessary to remove them from service, and to conduct flight inspections). This requires that facility operational data be obtained and recorded in the maintenance log and on technical performance records. These records are official documents, and may be used by an aircraft accident investigation board in the determination of facility operational status at the time of the accident. See the latest edition of Order 8020. 16, “Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting” for detailed guidance on requirements and activities following an aircraft accident/incident.

104. COORDINATION.

Coordination requests shall be made in accordance with the latest edition of Order 6000.15. Those procedures require:

a. Requests for authority to remove equipment from service shall be directed to the

appropriate AF Control Center and include the desired time of shutdown, probable duration, and reason.

109. MODIFICATION POLICY. › a. No modification shall be made to the standard equipment, facilities,…

b. The AF Control Center other appropriate entities, obtain approval or justification for refusal,

and advise the requesting organization or the System Specialist of the results.

c. The System Specialist should confirm the approval for the interruption with AT or AF control

center personnel immediately prior to the shutdown to ensure the approval status has not changed.

105. FLIGHT INSPECTION.

Normal instruction and guidance concerning flight inspection of the basic radar system and associated equipment are contained in the latest edition of Order 8200.1, United States Standard Flight Inspection Manual. For additional information concerning flight inspections, see Chapter 6 of this order.

106. TECHNICAL INSPECTION.

Facility inspections, objectively conducted, are one of the most effective tools for assuring the reliability of the National Airspace System (NAS). See the latest edition of Order 6000.15 and the latest edition of Order 6040.6, Airway Facilities NAS Technical Evaluation Program, for the details on intervals and requirements for formal inspections.

107. PERIODIC MAINTENANCE.

a. Tasks. Chapter 4 of this handbook establishes the tasks and schedules that are required

for the periodic maintenance of STARS. These tasks, as scheduled, are the minimum required for each of the systems to meet minimum performance standards.

b. Maintenance Personnel. Related information useful to maintenance personnel may be

found in the Federal Aviation Administration (FAA) orders and handbooks, maintenance manuals, and diagnostic operating procedures listed in Appendix 3 of this handbook.

c. Configurations.

1. FSL

2. ESL

3. EASL where EASL is part of the configuration

108. TEST EQUIPMENT AND TOOLS FOR PERIODIC MAINTENANCE.

Special tools are required for performing STARS routine maintenance. Tools that are delivered to the site with STARS equipment are listed in Technical Instruction (TI) 6191.400, STARS O & M Manual for the SOS.

109. MODIFICATION POLICY.

a. No modification shall be made to the standard equipment, facilities, software, or procedures

without proper authorization. It is recognized that there will be occasions when certain temporary repairs will be necessary when approved parts are not readily available or a design deficiency is discovered. Under such circumstances, a complete report shall be submitted to the appropriate supervisor. The report shall explain the nature of the problem, describe the changes made, and provide an estimate of when the equipment will be

114. JUMPSTARS POLICY. › a. General. This paragraph provides policy guidance on when to execute…

restored to its original condition. The affected equipment shall be restored to its original condition as soon as possible.

b. Prior Washington headquarters approval is required before region wide or system-wide

modifications are undertaken. Regional offices may grant approval for a temporary modification for testing purposes or for determining the feasibility of a proposed improvement. Refer to the latest edition of National Airspace System Configuration Management, and Order 6032.1, Modification to Ground Facilities, Systems, and Equipment in the National Airspace System, for further information

c. Proposed modifications to improve system performance, increase reliability, minimize

safety hazards, or increase maintenance efficiency may be suggested by any field personnel. Such proposed modifications must be described in detail and submitted through the proper channels per NAS Change Proposal (NCP), FAA form 1800-2.

110. MAINTENANCE AND DIAGNOSTIC MANUALS.

A list of maintenance and diagnostic manuals are referenced in Appendix 3 of this handbook.

111. FAA FORMS.

Appendix 3 of this handbook lists the applicable FAA forms required by this handbook.

112. FAA ORDERS AND HANDBOOKS.

Appendix 3 of this handbook lists the latest edition of orders and handbooks referenced within this handbook. A listing of documents useful to NAS system personnel may be found in the catalog of documentation maintained by the National Airspace System Documentation Facility, found on a Federal Aviation Administration (FAA) Intranet site located at http://nasdoc.faa.gov/ and a DoD accessible website at http://www.dod.tc.faa.gov.

113. SYSTEM SECURITY.

a. Sites are expected to maintain user Identification (ID) and password protection for all

workstations. The dissemination of the root or super-user password should be strictly controlled and shall be changed frequently. Personnel should log on as the root or superuser only when absolutely required to perform some action such as a diagnostic or a Remove and Replace (R&R). The root or super-user is not meant for use in everyday operations. Extreme caution should be used when logged in as root or super-user, because certain commands may take the system down.

b. All personnel who are required to operate the system shall be assigned a separate user ID

and password. Separate user IDs and passwords for each operator allow the use of audit trails to determine who performed what action on the system. Personnel who leave or no longer require access to the system shall have their user IDs and passwords deleted.

114. JUMPSTARS POLICY.

a. General. This paragraph provides policy guidance on when to execute JumpSTARS

procedures. JumpSTARS is a tool that is used to load the Unix operating system on a STARS LRU, and to initialize that LRU in preparation for operational use. The JumpSTARS procedures are contained in TI 6191.484, STARS JumpSTARS Operator’s Manual for the SOS.

b. Background. There are two ways to run JumpSTARS. Easy Spare is run on an isolated

CHAPTER 1. GENERAL INFORMATION AND REQUIREMENTS › 115. – 199. RESERVED.

STARS LRU on a test bench, and JumpSTARS is run on all STARS LRUs connected in its operational configuration.

c. Policy. Airway Facilities policy is that JumpSTARS should be used only as a last resort,

i.e., when all attempts to restore a system-wide failure by first level maintenance and second level engineering support have failed. All coordination and approvals shall be obtained as delineated below.

d. JumpSTARS Procedure. JumpSTARS could interrupt normal operation of the STARS

LRUs for 12 to 48 hours, depending on the number of displays, towers, and LRUs. The following steps shall be completed before running JumpSTARS other than during STARS initial installation:

1. Justification. In the event of a system-wide failure of STARS, and all attempts to restore STARS by first level maintenance and second level engineering support have failed, JUMPSTARS may be used as a last resort.

2. Approval and Coordination.

(a) Notify the System Support Center (SSC) Manager and get approval to run

JumpSTARS.

(b) Notify the associated AT Operations Manager and get approval to run

JumpSTARS.

(c) The Specialist running JumpSTARS shall notify the appropriate AF control center

to begin the coordination for running the JumpSTARS procedures. The Specialist should provide information such as who, what, when, and where to the AF control center.

(d) The AF control center is responsible for coordination with the affected System

Management Office (SMO) and Regional Operations Branch Manager.

3. Execution. Refer to the JumpSTARS Procedures Manual for detailed procedures on configuration and execution of JumpSTARS. The second level engineering support organization should be included in the execution of JumpSTARS.

4. Documentation. Document the coordination activities, approvals, start of JumpSTARS, and completion of JumpSTARS in the maintenance log.

e. Easy Spare Procedure. Easy Spare is performed isolated on a test bench and has no

impact to STARS operation. Easy Spare should be run as part of a replacement or modification to STARS components. There are no approval or coordination requirements to run Easy Spare.

115. – 199. RESERVED.

c. Site Purpose. › 3. SOS Purpose.

Chapter 2. TECHNICAL CHARACTERISTICS

200. PURPOSE.

The paragraphs that follow describe the overall purpose of STARS and the purpose of each STARS site type.

201. SYSTEM INTRODUCTION.

a. System Purpose. STARS provides automation to support Air Traffic Control (ATC) within

the FAA TRACON and DoD air traffic control facilities. STARS ultimately replaces all terminal automation systems previously deployed at these facilities, including the following:

1. Automated Radar Terminal System (ARTS) IIA, ARTS IIE, ARTS IIIA, and ARTS IIIE.

2. En route Automated Radar Terminal System (EARTS), the Navy Radar Air Traffic Control Facility-Direct Altitude and Identification Readout (RATCF-DAIR).

3. Programmable Indicator Display Processor (PIDP) systems and Military Beacon Decoder (TPX-42) systems at DoD air traffic control facilities.

4. Micro-EARTS (DoD only).

5. Digital Bright Radar Indicator Tower Equipment (DBRITE).

b. Site Types.

1. STARS is designed around three basic site types. STARS site types are:

(a) STARS Central Support Complex (SCSC)

(b) Operational Support Facility (OSF)

(c) STARS Operational Site (SOS)

2. In addition to these basic sites, SOS Local Towers (LT), Remote Towers (RT), and standalone towers provide for local ATC operations at airport sites. The system/site roles are established through the design of the STARS system hierarchy structure.

c. Site Purpose.

1. SCSC Purpose. The SCSC facility provides for centralized control of STARS field support and software development. The field support performs Program Technical Report (PTR) analysis and testing, hardware testing/analysis, and configuration management. The software development develops, modifies, and tests software to establish software baselines, resolve existing software problems, add new functionality (incremental upgrades) to the software baseline, and to perform system level adaptation. The SCSC is located at the William J. Hughes Technical Center (WJHTC). An FAA Wide Area Network (WAN) provides for data and software transfer between the SCSC and STARS OSFs.

2. OSF Purpose. Each OSF serves as a support facility for software maintenance to include both site adaptation data and site support for associated SOSs. The purpose of software maintenance is to receive operational site software releases from the SCSC, integrate site adaptation to complete the operational program, and test the entire operational program prior to implementation at an SOS.

3. SOS Purpose. The SOS facilities provide the automation of air traffic data to support ATC within FAA and DoD terminal control areas. Each SOS provides automation to

3. SOS Purpose. › (g) Site Support Subsystem.

support control of air traffic within a designated FAA TRACON or DoD air traffic control facility. The SOS accepts and processes surveillance and other data to provide ATC and system information to air traffic controllers and external systems. Typically, the SOS includes a local tower for local airport traffic control. An SOS site may support one or more RTs as part of the configuration. The SOS may also use RTs to support its facility role. Stand-alone towers provide automation for local airport/air station ATC similar to the RT capabilities but without the need for direct SOS support.

(a) Independent Support. The SOS operates in an independent fashion. The

primary STARS mission can be accomplished without any connection to any of the STARS support facilities. For support purposes, the SOS includes two dial-up circuits for interfacing to the external support sites. The dial-up links are typically used to connect the operational site to the associated OSF site. The dial-up circuits can also be used to establish a connection with the SCSC or any other STARS site subject to security criteria established at each site.

(b) SOS Security. The SOS consists of operational and support subsystems. The

SOS also includes equipment to ensure that computer security is maintained in the FAA networking environment. Router and firewall equipment are provided to authenticate any users who attempt to dial into or out of the SOS and to report any detected breaches.

(c) Operational Support Subsystem. The STARS Support Subsystem (SS)

provides the offline support functions needed to maintain the operational site. The SS typically communicates with the OSF and SCSC. The SS also provides site support such as simulation for testing, training, and the ability to transfer data to OSF or SCSC for analysis, etc.

(d) Data Processing and Display. STARS is a digital radar processing automation

and display system. It is comprised of numerous computers linked with dual redundant LANs that together accomplish the task of accepting radar and Inter- Facility (IFDT) data and displaying ATC related information on the displays for AT personnel. Radar data can be received from both short-range (terminal) and longrange radars. STARS has three service levels: FSL, ESL, and EASL (transition level).

(e) Modem Sharing Unit (MSU). STARS utilizes the MSU as radar data and Inter-

Facility data splitter devices for the automation systems (FSL and ESL). The MSU consists of either a 4-port or 2-port RS-232 line sharing device. Long-range radar data is connected to the input of the 4-port line sharing device. Outputs of the MSUs are fed to primary and alternate FSL Networked Universal Input/Output (NUNIO) and primary and alternate ESL NUNIOs. Inter-Facility data is connected to the input of the 2-port line sharing device. Outputs of the line sharing devices are fed to the primary and alternate FSL NUNIOs.

(f) Line Splitter. Short range radar data is connected to the input of RS-530 line

splitter devices. Outputs from the line splitter are fed to primary and alternate FSL NUNIO devices and primary and alternate ESL NUNIOs.

(g) Site Support Subsystem. The site support subsystem is common to both FSL

and ESL. The components of the site support subsystem are General Purpose Workstations (GPW), Test and Training Simulator Equipment (TTSE), a Site Support Server (SSS), laser printer, and firewall. The GPWs are used for general processing support at the site. The TTSE provides simulation and training to AT

b. FSL is comprised of NUNIOs, Communication Gateway (CGW), Radar Data… › 1. NUNIO CHASSIS.

operation. The Commercially Available Software (CAS) that supports the training task is ATCoach software. The SSS is the central point storage for the operational, utility, and diagnostic software. The firewall provides site access security processing for all transfers over the dial-up lines and WAN router.

202. FSL SYSTEM FUNCTIONAL DESCRIPTION.

a. The operational software that is used in FSL is AutoTrac. The FSL provides beacon

tracking for terminal and tower control areas. Automatic transfer of flight data via Inter- Facility between the FSL and Air Route Traffic Control Centers (ARTCC) and/or TRACON facilities are provided. The FSL provides the following capabilities:

1. Search-only

2. Beacon-only

3. Radar-reinforced beacon target tracking

4. Beacon-radar correlation and tracking

5. Site registration

6. Collimation corrections

7. Conflict Alert (CA)/Mode-C Intruder (MCI) processing

8. Continuous Data Recording (CDR)

9. Automatic failure recovery and reconfiguration

10. Real-Time Quality Control (RTQC)

11. Minimum Safe Altitude Warning (MSAW)

12. Multi-sensor tracking

13. Sensor Mosaic display

14. Inter-Facility and intra-facility hand-offs

15. Remote displays

16. Traffic count

17. Up to 32 digital maps referenced on the DCB. Up to 400 system-wide (memory permitting).

18. Six levels of weather intensity display

19. Select up to 16 sensors

20. Workstation replay events.

b. FSL is comprised of NUNIOs, Communication Gateway (CGW), Radar Data Processor

(RDP), Global Positioning System (GPS), Continuous Data Recorder (CDR), Applications Interface Gateway (AIG), Terminal Control Workstation (TCW), Tower Display Workstation (TDW), a Monitor Control Workstation (MCW), Control and Monitor Display (CMD), and a dual redundant LAN. Functions are described as follows.

1. NUNIO CHASSIS. Each NUNIO chassis enclosure has six NUNIO modules, each of which can support four serial data inputs. Each module converts radar serial data to networked packeted data. It is then sent out to CGWs via the LAN. The NUNIO also provides an interface between Inter-Facility and the CGW.

7. TCW. › (c) The LDB contains

2. CGW. The CGW is capable of accepting digitized radar data from up to 16 terminal and/or long-range radar sensors. The radar data is distributed to the RDPs over the FSL LANs. Dual CGWs provide backup protection in the event that the online CGW fails. The CGW also provides Inter-Facility data transfer between STARS at the TRACON and ARTCC.

3. RDP. The RDP accepts raw radar data from the CGW and processes it into synthetic display images that are distributed to the TCW and TDW displays. The RDP performs all tracking, registration corrections, collimation corrections, CA, MSAW, radar performance monitor, auto hand-offs, auto-associations, auto-acquires, and autodrops. Dual RDPs provide backup protection in the event that the online RDP fails.

4. GPS. The GPS provides the system time that is used in FSL via the RDP. The GPS interfaces with a GPS time code processor module installed in each RDP.

5. CDR. The CDR is used for ATC data recording. CDR consists of two Data Recording Facilities (DRF). The ATC data includes displayed targets, weather, maps, lists, filter limits, display control settings, system messages, change to flight plan data, and user actions. CDR also allows playback of recorded radar data and printout of operator actions. Dual CDR provides backup protection in the event the online CDR fails.

6. AIG. The AIG is the router that provides an interface between STARS and other NAS systems.

7. TCW. The TCW is the display located in the TRACON that the controllers use to provide service to aircraft in the terminal environment. The primary function of the TCW is to display radar data that has been collected by radar sensors and tracked by the RDP. The TCW functionality consists of the following: hand-offs, initiate tracking, terminate tracking, flight plan entry, flight plan edit, digital map display (up to 32), altitude filter limits, auto offset, select configuration, and quick look. The tracked radar data is combined with flight plan data allowing the TCW to present track characteristics with Full Data Blocks (FDB), Minimal Data Blocks (MDB), Limited Data Blocks (LDB), and alternate FDBs to the controllers.

(a) The FDB contains: Present Position Symbol (PPS), Controller Jurisdiction

Indicator (CJI), leader line, Predicted Track Line (PTL), Aircraft Identification (ACID) or Secondary Surveillance Radar (SSR) code, aircraft category, Mode-C flight level/altitude, vertical movement indicator, computed ground speed, destination terminal, assigned flight level/altitude, vertical speed, assigned heading, and a comments field. All FDB tracks have a flight plan. FDBs are represented for any tracks that are: “owned” but not in the hold list, quick looked, in hand-off mode for which a TCW is either the initiator or the receiver, special condition (e.g., general emergency, hi-jack, or radio communications failure), and tracks with unsuppressed MSAW or CA.

(b) The MDB contains: a PPS with a CJI, and a PTL. All MDB tracks have an

associated flight plan. MDBs are represented for any tracks that are “owned” by another controller.

(c) The LDB contains: a leader line, a PTL, an SSR code, a Mode-C flight

level/altitude, and a vertical movement indicator. LDBs are presented for all tracks that do not have an associated flight plan.

b. ESL is comprised of two NUNIO chassis utilizing a crossover service… › 1. NUNIO CHASSIS.

(d) The alternate FDB has a similar characteristic and presentation as the FDB,

except the aircraft type will be displayed in place of the Mode-C flight level/altitude, and the vertical movement indicator.

8. TDW. The TDW runs on the same architecture and has the same radar display characteristic as the TCW, but displays radar data on a high brightness color monitor. The TDWs are located in the local tower cab, remote tower cab, and stand-alone tower cab.

9. MCW. The MCW functions as the central point to monitor and control the system through the FSL LANs. All system status, health, and error messages are displayed at the MCW. The function of the MCW can be obtained at any TCW and TDW that are not assigned airspace by requesting a Monitor and Control Process (MCP) and taking system control via an authorized log-in. The levels of authorization in conjunction with a unique password limit access to MCW functions. The different levels of authorization are log out, monitor, and control.

(a) Log out level indicates that the MCW is logged out. There is no operation or status

available.

(b) Monitor level has viewing only privileges.

(c) Control level has access to functions that affect and operate on STARS equipment

and links to external systems and to functions that affect ATC related operations and features. This level has unrestricted access.

10. CMD. The CMD provides the capability to relinquish MCW function to the TCW and TDW and vice versa.

11. Dual Redundant LANs. The LANs used throughout the various STARS configurations all employ the Ethernet/Fast Ethernet family of LAN technology. The 10- Megabits per second (Mbps) Ethernet and 100-Mbps Fast Ethernet both comply with the Institute of Electrical & Electronic Engineers (IEEE) 802.3 standard. They share the same frame format and protocol and differ only at the physical layer. The FSL contains two independent LANs: online and standby. The LAN functions as a communication pathway between all processors in the system.

203. ESL SYSTEM FUNCTIONAL DESCRIPTION.

a. The operational software used in ESL is TracView. The ESL system provides a backup to

the FSL and EASL during transition. ESL provides the ATC with surveillance position information, aircraft beacon code and beacon filters, altitude and altitude filters, maps, range marks, weather information, and sensor identification. ESL is made operational by controller selection at each display. Targets will continue to be displayed on the controller display in response to a controller’s command to switch from FSL/EASL to ESL. ESL provides the following capabilities: search and beacon target display with no tracking capability, remote displays, display digital maps (up to 32), six levels of weather intensity display, automatic failure recovery, and reconfiguration.

b. ESL is comprised of two NUNIO chassis utilizing a crossover service to two CGWs; one

services LAN A, and the other services LAN B independently. ESL also has one MCW for maintenance monitoring and control, one or more TCWs, and one or more TDWs.

1. NUNIO CHASSIS. Each NUNIO chassis enclosure has six NUNIO modules, each of which can support four serial data inputs. Each module converts radar serial data to networked packet data. It is then sent out to CGWs via the LAN.

2. CGW. The CGW in ESL operates independently from the CGWs in FSL. A CGW is capable of accepting up to 16 channels of digitized radar data from short-range (terminal) and/or long-range radar sensors. The CGW converts the input data into network format; it is then sent to the TCWs and TDWs via the ESL LAN. At remote towers with direct radar feed, redundant CGWs will be provided. A remote CGW is used to provide backup radar data to the remote tower in case of STARS failure at the TRACON.

Chapter 2. TECHNICAL CHARACTERISTICS › 206. – 299. RESERVED.

3. TCW. The primary function of the TCW is to display radar data without tracking capability that has been collected by the ESL CGW through the ESL LANs. TCW presents radar data characteristics in LDBs.

4. TDW. The TDW runs on the same architecture and has the same radar display characteristic as the TCW, presenting radar data on a high brightness color monitor. The TDWs are located in the local tower cab, remote tower cab, and stand-alone tower cab.

5. MCW. The MCW functions as the central point to monitor and control the system. All system error messages are displayed at the MCW. The function of the MCW can be obtained at any TCW and TDW, by configuring it to a MCP and taking system control. DoD sites having two MCWs may use the second MCW as backup for system control.

6. LAN. The ESL LANs operate independently from the FSL LANs; however, they have the same characteristics and functionality.

204. EASL SYSTEM FUNCTIONAL DESCRIPTION.

EASL uses the ARTS IIIA system inputs, via the Automation Interface Adapter (AIA), in conjunction with the STARS hardware to provide ATC operational capabilities, with the added feature of color displays. EASL is used only during the transition phase of deployment. The AIA provides processing to convert the existing automation alphanumeric data into networking package format for transmission to the TCW, and performs the inverse function for data entries emanating from the TCW keyboard. The AIA will be removed after a complete cutover to STARS.

205. STARS BLOCK DIAGRAM.

Respectively, Figure 2-1, Transition Phase; Figure 2-2, Typical SOS; Figure 2-3, Typical Remote Tower; Figure 2-4, Remote Tower with Local Primary Radar; and Figure 2-5, Typical Stand-Alone Tower, in this handbook show the transition states of STARS, typical configuration of SOS, remote tower configuration, and a stand-alone tower configuration.

206. – 299. RESERVED.

Figure 2 – 1. Transition Phase

STARS

Displays

STARS

FSL

Transition

Equipment

STARS Equipment

Existing

Sensor

Inputs

Interfacility

LANs

Existing Automation

System

STARS

Displays

STARS ESL

Comm

Gateway

Sensor

Inputs Interfacility

Automation

Interface

Adapter

LANs

Alphanumerics

Synthetic Targets

Digital Maps

Data Entries

STARS Emergency

Service Capabilities

Existing Automation

System

Existing

Displays

Sensor

Inputs Interfacility Alphanumerics

Broadband Targets

Broadband Maps

Data Entries

EASL and Existing EASL and STARS Displays

STARS

Analog Video

Equipment

New Displays - Position-by-Position ‘‘In-Place’’ replacement of displays with STARS TCWs

allows low risk introduction of equivalent STARS

functionality with fallback to ARTS if needed

EASL = Exisiting Automation (ARTS, IIA, IIIA, IIIE)

STARS ESL

Comm

Gateway

• •

•

• • •

•

•

• •

Figure 2 – 2. Typical SOS

Figure 2 – 3. Typical Remote Tower

TDW

ESL LAN

FSL LAN

T1 LINK

T1 LINK

T1 LINK

SOS

T1 LINK

GPW TTSE SSS PRINTER

WAN ROUTER

FIREWALL

OSF SCSC OCC

SITE SUPPORT SUBSYSTEM

AUTOMATION SUBSYSTEM

SUPPORT LAN

FSL LAN

TCW TDW

MCW CMD

ESL LAN

CGW

CGW NUNIO

MSU

CGW

CGW

GPS

RDP CDR

MSU BACKUP

PRIMARY

RADAR CHANNELS

NUNIO

ARTCC ETMS

AIG

GPS

TDW

ESL LAN

CGW

NUNIO

FSL LAN

OPTIONAL

MSU

BACKUP

PRIMARY RADAR CHANNELS

T1 LINK

T1 LINK

T1 LINK

SOS

T1 LINK

Figure 2 – 4. Remote Tower With Local Primary Radar

RADAR

CHANNELS

BACKUP

PRIMARY

MSU

Figure 2 – 5. Typical Stand-Alone Tower

CGW

NUNIO

TDW

ESL LAN

Chapter 3. STANDARDS AND TOLERANCES

300. GENERAL.

a. This chapter prescribes the standards and tolerances for STARS, as defined and described

b. Definitions of standard, initial, and operating tolerance as used in… › 3. Operating Tolerance.

in the latest edition of Order 6000.15. All key performance parameters and/or key inspection elements are clearly identified by an arrow (→) placed to the left of the applicable item. The paragraphs in this chapter are numbered to enhance the organization and make it easier to use.

b. Definitions of standard, initial, and operating tolerance as used in this handbook are defined

as follows:

1. Standard. The optimum value assigned to an essential system parameter.

2. Initial Tolerance. The maximum deviation from the standard value of the parameter, or the range, which is permissible when the system or equipment is accepted at the time of initial commissioning or after any readjustment, modification, or modernization.

3. Operating Tolerance. The maximum deviation from the standard value of the parameter or the range within which a system or equipment may continue to operate on a commissioned basis without adjustment or corrective maintenance and beyond which remedial action is mandatory.

304. FSL TCW. › d. Network Information System Plus (NIS+) check.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

301. FSL NUNIO.

a. Visually inspect FSL MCW status of

the NUNIO icons.

TI 6191.402 No visual error indication.

Same as standard.

Same as standard.

b. Offline diagnostics. TI 6191.402 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the FSL MCW.

TI 6191.402 Error free operation.

Same as standard.

Same as standard.

302. FSL CGW.

a. Visually inspect FSL MCW status of

the CGW icons.

TI 6191.402 No visual error indication.

Same as standard.

Same as standard.

b. Offline Diagnostics for FSL

Processor.

TI 6191.402 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the FSL MCW.

TI 6191.402 Error free operation.

Same as standard.

Same as standard.

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

303. FSL RDP.

a. Visually inspect FSL MCW status of

the RDP icons.

TI 6191.402 No visual error indication.

Same as standard.

Same as standard.

b. Offline Diagnostics for FSL

Processor.

TI 6191.402 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the FSL MCW.

TI 6191.402 Error free operation.

Same as standard.

Same as standard.

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

304. FSL TCW.

a. Visually inspect FSL MCW status of

the TCW icons.

TI 6191.402 No visual error indication.

Same as standard.

Same as standard.

b. Offline Diagnostics for FSL

Processor.

TI 6191.402 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the FSL MCW.

TI 6191.402 Error free operation.

Same as standard.

Same as standard.

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

309. TSATD FSL SERVICE CERTIFICATION AND TARGET PARAMETERS. › Check icons at the FSL MCW.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

305. FSL TDW.

a. Visually inspect FSL MCW status of

the TDW icons.

TI 6191.402 No visual error indication.

Same as standard.

Same as standard.

b. Offline Diagnostics for FSL

Processor.

TI 6191.402 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the FSL MCW.

TI 6191.402 Error free operation.

Same as standard.

Same as standard.

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

306. FSL MCW.

a. Visually inspect FSL MCW status of

the MCW icons.

TI 6191.402 No visual error indication.

Same as standard.

Same as standard.

b. Offline Diagnostics for FSL

Processor.

TI 6191.402 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the FSL MCW.

TI 6191.402 Error free operation.

Same as standard.

Same as standard.

d. Network Information System plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

307. FSL CDR.

a. Visually inspect FSL MCW status of

the CDR icons.

TI 6191.402 No visual error indication.

Same as standard.

Same as standard.

b. Offline Diagnostics for FSL

Processor.

TI 6191.402 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the FSL MCW.

TI 6191.402 None. Same as standard.

Same as standard.

d. Network Information System plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

308. FSL STANDBY RESOURCES.

a. Configure FSL to utilize the Standby

Resources.

Par. 529 Successful no fault execution.

Same as standard.

Same as standard.

309. TSATD FSL SERVICE CERTIFICATION AND TARGET PARAMETERS.

a. Check icons at the FSL MCW.

Par. 511 Minimum required resources that

Same as standard.

Same as standard.

Chapter 3. STANDARDS AND TOLERANCES › 311. ESL NUNIO.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating can sustain the facility AT operation.

b. Check system messages reported at

the FSL MCW.

Par. 511 Minimum required resources that can sustain the facility AT operation.

Same as standard.

Same as standard.

c. Test Target Display Check.

Par. 512 Applicable PEs/MTI reflectors, PARROT/ CPMEs and Beacon/Search RTQCs are displayed within or on appropriate geo-boxes or adapted map location symbols, or are displayed at expected positions.

Same as standard.

Same as standard.

Target Parameters

1. Beacon PARROT. ATCBI-5/6.

(a) Azimuth. Par. 512 Within ± 1° of standard.

Same as initial.

(b) Range. Par. 512 Within ± ¼ nm of standard.

Same as initial.

2. Mode-S CPME.

(a) Azimuth. Par. 512 Within ± 1° of standard.

Same as initial.

(b) Range. Par. 512 Within ± ¼ nm of standard.

Same as initial.

3. Search PE. Search PE/MTI reflector.

(a) Azimuth. Par. 512 Within ± 1° of standard.

Same as initial.

(b) Range. Par. 512 Within ± ¼ Same as

311. ESL NUNIO. › c. Verify there are no active error or alarm messages reported at the…

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating nm of standard.

initial.

4. Search/Beacon RTQC.

(a) Azimuth. Par. 512 Within ± 1° of standard.

Same as initial.

(b) Range. Par. 512 Within ± ¼ nm of standard.

Same as initial.

310. STARS FSL SUBSYSTEM CERTIFICATION.

a. Software Version Verification. TI 6191.402, Software Status Report

Latest software and adaptation versions are installed and running on all operational processors and modules.

Same as standard.

Same as standard.

b. Resource Verification Test. Par. 510 Minimum required resources that can sustain the facility AT operation pass.

Same as standard.

Same as standard.

c. Performance Verification of air traffic control visual and aural alarms.

1. Using the TCW/TDW. Par. 516 and TI 6191.402

Successful no fault execution.

Same as standard.

Same as standard.

d. Radar Data Processing and Display

Capability.

Par. 518 Data is presented on the display for AT operation.

Same as standard.

Same as standard.

311. ESL NUNIO.

a. Visually inspect ESL MCW status of

the NUNIO icons.

TI 6191.403 No visual error indication.

Same as standard.

Same as standard.

b. Offline Diagnostic. TI 6191.403 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the ESL MCW.

TI 6191.403 Error free operation.

Same as standard.

Same as standard.

315. ESL MCW. › c. Verify there are no active error or alarm messages reported at the…

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

312. ESL CGW.

a. Visually inspect ESL MCW status of

the CGW icons.

TI 6191.403 No visual error

indication.

Same as standard.

Same as standard.

b. Offline Diagnostics. TI 6191.403 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the ESL MCW.

TI 6191.403 Error free operation.

Same as standard.

Same as standard.

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

313. ESL TCW.

a. Visually inspect ESL MCW status of

the TCW icons.

TI 6191.403 No visual error

indication.

Same as standard.

Same as standard.

b. Offline Diagnostics for ESL

Processor.

TI 6191.403 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the ESL MCW.

TI 6191.403 Error free operation.

Same as standard.

Same as standard.

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

314. ESL TDW.

a. Visually inspect ESL MCW status of

the TDW icons.

TI 6191.403 No visual error indication.

Same as standard.

Same as standard.

b. Offline Diagnostics for ESL

Processor.

TI 6191.403 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the ESL MCW.

TI 6191.403 Error free operation.

Same as standard.

Same as standard.

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

315. ESL MCW.

a. Visually inspect ESL MCW status of

the MCW icons.

TI 6191.403 No visual error indication.

Same as standard.

Same as standard.

b. Offline Diagnostics for ESL

Processor.

TI 6191.403 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the ESL MCW.

TI 6191.403 Error free operation.

Same as standard.

Same as standard.

317. TSATD ESL SERVICE CERTIFICATION. › Test Target Display Check.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

316. ESL STANDBY RESOURCES.

a. Configure ESL to utilize the standby

resources.

Par. 531 Successful no fault execution.

Same as standard.

Same as standard.

317. TSATD ESL SERVICE CERTIFICATION. NOTE: The certifying official, using the same ESL checks specified in the following table, must determine that the Direct Radar Feed (DRF), if available, is capable of providing its advertised functions. For DRF checks, ensure that the DRF sensor is selected at the TDW. Then drill down into appropriate towers/radar GUI at ESL MCW for detailed indications.

a. Check icons at the ESL MCW. Par. 511 Minimum required resources that can sustain the facility AT operation.

Same as standard.

Same as standard.

b. Check system messages reported at

the ESL MCW.

Par. 511 and TI 6191.404

Minimum required resources that can sustain the facility AT operation.

Same as standard.

Same as standard.

c. Test Target Display Check. Par. 513 Applicable PEs/MTI reflectors, PARROT/ CPMEs and Beacon/Search RTQCs are displayed within or on appropriate geo-boxes or adapted map location symbols, or are displayed at expected positions.

Same as standard.

Same as standard.

318. STARS ESL SUBSYSTEM CERTIFICATION. › Software Version Verification.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

Target Parameters

1. Beacon PARROT. ATCBI-5/6.

(a) Azimuth. Par. 513 Adapted position.

Within ± 1° (11 ACP) of standard.

Same as initial.

(b) Range. Par. 513 Adapted position.

Within ±1/4 nm of standard.

Same as initial.

2. Mode-CPME.

(a) Azimuth. Par. 513 Adapted position.

Within ± 1° (11 ACP) of standard.

Same as initial.

(b) Range. Par. 513 Adapted position.

Within ±1/4 nm of standard

Same as initial.

3. Search PE. Search PE/MTI reflector.

(a) Azimuth. Par. 513 Adapted position.

Within ± 1° (11 ACP) of standard.

Same as initial.

(b) Range. Par. 513 Adapted position.

Within ±1/4 nm of standard.

Same as initial.

4. Search/Beacon RTQC.

(a) Azimuth. Par. 513 Adapted position.

Within ± 1° (11 ACP) of standard.

Same as initial.

(b) Range. Par. 513 Adapted position.

Within ±1/4 nm of standard

Same as initial.

318. STARS ESL SUBSYSTEM CERTIFICATION. NOTE: The certifying official, using the same ESL checks specified in the following table, must determine that the Direct Radar Feed (DRF), if available, is capable of providing its advertised functions.

a. Software Version Verification. TI 6191.403 Latest software and adaptation versions are

Same as standard.

Same as standard.

320. TSATD EASL SERVICE CERTIFICATION. › Test Target Display Check.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating installed and running on all operational processors and modules.

b. Resource Verification Test. Par. 510 Minimum required resources that can sustain the facility AT operation pass.

Same as standard.

Same as standard.

c. Performance Verification of air traffic control visual and aural alarms.

Par. 522 Successful no fault execution.

Same as standard.

Same as standard.

d. Radar Data Processing and Display

Capability.

Par. 524 Data is presented on the display for AT operation.

Same as standard.

Same as standard.

319. AIA.

a. Visually inspect ESL MCW status of

the AIA icons.

TI 6191.403 No visual error indication.

Same as standard.

Same as standard.

b. Verify there are no active error or

alarm messages reported at the ESL MCW.

TI 6191.403 Error free operation.

Same as standard.

Same as standard.

c. Network Information System Plus (NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

d. Execute Early Display Configuration

Multiplexed Display Buffer Memory (EDCM) Diagnostic Program.

TI 6190.44 Successful no fault execution.

Same as standard.

Same as standard.

e. Execute Online Limited Data Display

Test (LDDT) Program.

Par. 528 Successful no fault execution.

Same as standard.

Same as standard.

320. TSATD EASL SERVICE CERTIFICATION.

a. Test Target Display Check. Par. 514 The display responds and updates according to the input action. PE/MTI reflectors, PARROT/CPME s and Beacon/Search

Same as standard.

Same as standard.

321. STARS EASL SUBSYSTEM CERTIFICATION. › Radar Data Processing and Display Capability.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating RTQCs are displayed within or on appropriate geo-boxes or adapted map location symbols, or are displayed at expected positions.

321. STARS EASL SUBSYSTEM CERTIFICATION.

EASL cannot be certified if ESL is not available.

a. Knowledge that Constituent

Automation System is certified.

ARTS IIIA.

Latest Order 6000.15; Latest Order 6190.6.

Terminal Radar Data Processing (TRDP) ARTS IIIA overall service is certified. ARTS IIIA overall system (except the Data Entry and Display Subsystem (DEDS) display is certified. Remote Tower Alphanumeric Display System (RTADS) overall service is certified. Data is presented on the display for AT operation.

Same as standard.

Same as standard.

b. Data Entry and Display Functions. Par. 525 The display responds and updates according to the input action.

Same as standard.

Same as standard.

c. Radar Data Processing and Display Capability.

Par. 526 Successful no fault execution.

Same as standard.

Same as standard.

322. STARS CERTIFICATION RANGE/AZIMUTH CHECK. › PARROT, PE, CPME and MTI Monitoring at ESL MCW.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

322. STARS CERTIFICATION RANGE/AZIMUTH CHECK.

NOTE 1: All Moving Target Indicator (MTI) reflectors or adapted PEs or beacon Position Adjustable Range Reference Orientation Transponders (PARROT) or Mode-S Calibration Performance Monitoring Equipment (CPME) are used for a normal air traffic control operation and certification. However, it is recognized that there will be occasions when certain equipment will be temporarily degraded. Under these circumstances, use whatever equipment is available (see NOTE 2). NOTE 2: For FS only: If all MTI reflectors and search PEs or beacon PARROTs/Mode S CPMEs are missing or are unreliable for a particular sensor due to known reasons external to STARS or the sensor itself, alternate methods of measuring range/azimuth integrity may be used. Such methods include meeting a registration tolerance of ±2 ACP for azimuth and ±1/8 nm range with a known good sensor (see par. 325, detailed procedure par. 536). If this is not possible, it is permissible to utilize visual checks to determine range/azimuth integrity and reliability (see par. 537). NOTE 3: For DRF checks, ensure that the DRF sensor is selected at the TDW. Then drill down into appropriate TOWERS/RADAR GUI at ESL MCW for detailed indications.

a. PARROT, PE, CPME, MTI, and

RTQC Monitoring at FSL MCW.

1. Beacon PARROT Air Traffic Control Beacon Interrogator Model 5/6 (ATCBI-5/6).

Par. 520 Adapted value. Within ± 4 ACP ± 1/8 nm ≥ 90% reliability of standard.

Same as initial.

2. Mode-S CPME. Par. 520 Adapted value. Within ± 4 ACP ± 1/8 nm ≥ 90% reliability of standard.

Same as initial.

3. Search PE/MTI Reflector. Par. 520 Adapted value. Short-range sensor within ± 6 ACP ± 1/8 nm ≥ 80% reliability of standard. Long-range sensor within ± 4 ACP ± 1/8 nm ≥ 80% reliability of standard.

Same as initial.

b. PARROT, PE, CPME and MTI For ESL and Error free Same as Same as

Search/Beacon RTQC Check Report at FSL MCW. › 2. ARSR-4

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating Monitoring at ESL MCW. DRF, as long as targets are reported within adapted tolerance, there is no error indicated at the ESL MCW.

operation. standard. standard.

323. STARS SYSTEM CERTIFICATION RADAR RELIABILITY CHECK AND SENSOR PERFORMANCE PARAMETERS. NOTE: For beacon-only systems the radar reinforcement rate, SRTQC reliability, and search blip scan measurements do not apply.

a. Search/Beacon RTQC Check Report

at FSL MCW.

Par. 521 TI 6191.402 FS RTQC Check Report.

See Sensor Performance Parameters.

Same as standard.

Same as standard.

Sensor Performance Parameters

1. ASR-9/11

Radar Reinforcement Rate (≥) Note 2, 5 80%

Mode 3/A Validity (≥) Note 1 98%

Mode C Validity (≥) Note 1 97%

Search RTQC Reliability (≥) Note 1, 3 98%

Beacon RTQC Reliability (≥) Note 1, 3 98%

PE Reliability (≥) Note 1, 3, 4 80%

Zero Code (≤<) Note 2 01%

Search Blip/Scan (≥) Note 2 92%

Beacon Blip/Scan (≥) Note 2 90%

Beacon Azimuth Split (≤<) Note 2 01%

Range Split (≤<) Note 2 01%

2. ARSR-4

Radar Reinforcement Rate (≥) Note 2, 5 80%

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

Mode 3/A Validity (≥) Note 1 98%

Mode C Validity (≥) Note 1 97%

Search RTQC Reliability (≥) Note 1, 3 98%

Beacon RTQC Reliability (≥) Note 1, 3 98%

Search/Beacon RTQC Check Report at FSL MCW. › 4. ASR-8

PE Reliability (≥) Note 1, 3, 4 80%

Zero Code (≤) Note 2 0%

Search Blip/Scan (≥) Note 2 92%

Beacon Blip/Scan (≥) Note 2 96%

Beacon Azimuth Split (≤<) Note 2 01%

Range Split (≤<) Note 2 01%

3. ARSR-1/2/3

Radar Reinforcement Rate (≥) Note 2, 5 60%

Mode 3/A Validity (≥) Note 1 98%

Mode C Validity (≥) Note 1 97%

Search RTQC Reliability (≥) Note 1, 3 98%

Beacon RTQC Reliability (≥) Note 1, 3 98%

PE Reliability (≥) Note 1, 3, 4 80%

Zero Code (≤<) Note 2 01%

Search Blip/Scan (≥) Note 2 75%

Beacon Blip/Scan (≥) Note 2 96%

Beacon Azimuth Split (≤<) Note 2 01%

Range Split (≤<) Note 2 01%

4. ASR-8

Radar Reinforcement Rate (≥) Note 2, 5 80%

Mode 3/A Validity (≥) Note 1 95%

Mode C Validity (≥) Note 1 95%

Search RTQC Reliability (≥) Note 1, 3 98%

Beacon RTQC Reliability (≥) Note 1, 3 98%

PE Reliability (≥) Note 1, 3 90%

Zero Code (≤<) Note 2 01%

Search Blip/Scan (≥) Note 2 80%

Beacon Blip/Scan (≥) Note 2 90%

323. › Search/Beacon RTQC at ESL MCW.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

Beacon Azimuth Split (≤<) Note 2 01%

Range Split (≤<) Note 2 01%

5. Other (e.g., RYC-8405, FPS- 67B)

Radar Reinforcement Rate (≥) Note 2, 5 50%

Mode 3/A Validity (≥) Note 1 95%

Mode C Validity (≥) Note 1 95%

Search RTQC Reliability (≥) Note 1, 3 98%

Beacon RTQC Reliability (≥) Note 1, 3 98%

PE Reliability (≥) Note 1, 3 90%

Zero Code (<) Note 2 1%

Search Blip/Scan (≥) Note 2 75%

Beacon Blip/Scan (≥) Note 2 90%

Beacon Azimuth Split (<) Note 2 1%

Range Split (<) Note 2 1%

b. Search/Beacon RTQC at ESL MCW.

NOTE: For DRF check, ensure that the DRF sensor is selected at the TDW. Then drill down into appropriate TOWERS/RADAR GUI at ESL MCW for detailed indications.

For ESL and DRF, as long as RTQC are reported within adapted tolerance, there is no error indicated at the ESL MCW.

Error free operation.

Same as standard.

Same as standard.

NOTE 1: Valid data can be expected when > 5 minutes of data is collected. Always select a 15 minute time period as the FSL MCW RTQC Check Report data collection interval whenever possible. NOTE 2: Valid data can be expected when > 1000 beacon reports/hour are recorded (4 targets for LRR, 2 targets for SRR). However, it is recommended to perform the sensor performance checks during peak traffic periods. For those sensors where the beacon maximum range is greater than the search maximum range, the radar-reinforced rate shall be calculated using only those beacon targets that are within maximum range of the search. NOTE 3: Reliability parameters may exceed 100%. NOTE 4: Use PARROT/PE Report. NOTE 5: For those sensors where the beacon maximum range is greater than the search maximum range, the radar-reinforced rate shall be calculated using only those beacon targets that are within maximum range of the search. STARS uses the adapted PSR range for its calculations.

327. SIM. › c. Verify there are no active error or alarm messages reported at the…

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

324. GIAFP SERVICE CERTIFICATION.

a. FDP Input/Output Check. Par. 515 IFDT connection is established.

Same as standard.

Same as standard.

325. REGISTRATION.

a. Registration. Par. 533 TI 6191.402, <FS Registration and Collimation… > Menu Option

0 ACP 0 nm Azimuth ± 2 ACP Range ±1/8 nm.

Same as initial.

NOTE 1: 1/8 nm = 64/512 nm. Therefore, Registration Recommended Value for Range is from –64 to +64 in the Registration Collimation Report. NOTE 2: 2 ACP = 32/16 ACP. Therefore, Registration Recommended Value for Azimuth is from –32 to +32 in the Registration Collimation Report.

326. SSS.

a. Visual inspection of SSS icon. Visually inspect MCW status of the icons.

No visual error indication.

Same as standard.

Same as standard.

b. Online Diagnostics for SSS

Processor.

TI 6191.403 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the MCW.

Visually inspect FSL MCW system messages.

Error free operation.

Same as standard.

Same as standard.

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

327. SIM.

a. Visual inspection of SIM icon. Visually inspect MCW status of the icons.

No visual error indication.

Same as standard.

Same as standard.

b. Online Diagnostics for SIM

Processor.

TI 6191.403 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the MCW.

Visually inspect FSL MCW system messages.

Error free operation.

Same as standard.

Same as standard.

330. SONY DATA DISPLAY MONITOR (DDM) CHECK. › b. Geometry Alignment in Millimeter (mm) Width x Height.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

328. GPW.

a. Visual inspection of GPW icon. Visually inspect MCW status of the icons.

No visual error indication.

Same as standard.

Same as standard.

b. Online Diagnostics for GPW

Processor.

TI 6191.403 Successful no fault execution.

Same as standard.

Same as standard.

c. Verify there are no active error or alarm messages reported at the MCW.

Visually inspect FSL MCW system messages.

Error free operation.

Same as standard.

Same as standard.

d. Network Information System Plus

(NIS+) check.

Par. 530 Successful no fault execution.

Same as standard.

Same as standard.

329. TDW MONITOR.

a. Video Adjust. TI 6191.400 TI 6191.401 Visually inspect for correct focus, color, & alignment.

Correct focus, color, and alignment.

Same as standard.

Same as standard.

330. SONY DATA DISPLAY MONITOR (DDM) CHECK.

a. Video Alignment (white balance). TI 6191.414

1. Color and Brightness Contrast Maximum.

Manufacturer setting.

0.241 ≤ x ≤ 0.301

0.256 ≤ y ≤ 0.316

43.0≤Y≤47.0

Same as initial.

2. Color and Brightness Contrast Minimum.

Manufacturer setting.

0.241 ≤ x ≤ 0.301

0.256 ≤ y ≤ 0.316

6.0 ≤ Y ≤ 7.0

Same as initial.

b. Geometry Alignment in Millimeter

(mm) Width x Height.

TI 6191.414 Manufacturer setting.

498x498 ± 5 Same as initial.

334. FSL SOFTWARE UPDATE. › a. Verify new software is functioning properly.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

c. Convergence Alignment. TI 6191.414

1. Zone A: the area within the circle whose radius from the center of the CRT to the edge of the picture size.

≤ 0.330 mm. Same as standard.

Same as standard.

2. Zone B: the area outside of zones A and C.

≤ 0.508 mm. Same as standard.

Same as standard.

3. Zone C: the areas within the four right isosceles triangles at the corners of the picture size whose sides are 1 inch.

≤ 0.700 mm. Same as. standard.

Same as standard.

NOTE: Refer to TI 6191.414 Appendix A Chapter 3, Installation Adjustment, Periodic Readjustment and Adjustment, for parameter check after replacing the Cathode Ray Tube.

d. Geometric Distortion at all areas of

the picture size.

TI 6191.414 Manufacturer setting.

Within 1% of picture height at all picture areas

1% of 498 ±5

Same as standard.

e. Focus. Minimum Recognizable

Character Font.

TI 6191.414 Manufacturer setting.

Character size 1.

Same as standard.

331. FIREWALL/WAN ROUTER PERFORMANCE CHECK.

a. Verify that the firewall is properly

configured and functional.

Par. 554 Successful no fault execution, i.e., read ClearText test message file downloaded from support facilities.

Same as standard.

Same as standard.

332. FSL SOFTWARE RELEASE MAINTENANCE.

a. Managing multiple versions of

software.

Par. 550 Successful no fault execution.

Same as standard.

Same as standard.

333. ESL SOFTWARE RELEASE MAINTENANCE.

a. Managing multiple versions of

software.

Par. 551 Successful no fault execution.

Same as standard.

Same as standard.

334. FSL SOFTWARE UPDATE.

a. Verify new software is functioning

properly.

Par. 552 Successful no fault execution.

Same as standard.

Same as standard.

341. SERVICE LEVEL AVAILABILITY CHECK. › a. Back-Up Data Processing System Check for FSL.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating

335. ESL SOFTWARE UPDATE.

a. Verify new software is functioning

properly.

Par. 553 Successful no fault execution.

Same as standard.

Same as standard.

336. MAP ALIGNMENT.

a. Verify map alignment. Par. 555 Maps are adapted correctly.

Same as standard.

Same as standard.

337. FIXED TARGET MAP.

a. Verify the fixed target map. Par. 556 Maps are adapted correctly.

Same as standard.

Same as standard.

338. GPS SYSTEM CLOCK AND SYNCHRONIZATION.

a. FSL MCW system time. TI 6191.402 FS Set Date and Time.

GPS displays and updates UTC on the FSL MCW.

Same as standard.

Same as standard.

b. ESL MCW system time. TI 6191.403 ES Set Date and Time.

GPS displays and updates UTC on the ESL MCW.

Same as standard.

Same as standard.

339. AURAL ALARM.

a. Verify individual speakers at

TCW/TDW.

TI 6191.409 Audible Alarm Test.

Successful no fault execution.

Same as standard.

Same as standard.

340. RTDS TARGET DISPLAY CHECK.

a. FS target display check.

Target reports update and display as expected.

No error reported by qualified observer.

Same as standard.

Same as standard.

b. ES target display check.

Target reports update and display as expected.

No error reported by qualified observer.

Same as standard.

Same as standard.

341. SERVICE LEVEL AVAILABILITY CHECK.

a. Back-Up Data Processing System

Check for FSL. NOTE: The certifying official, using

Par. 519 Successful no fault execution.

Same as standard.

Same as standard.

345. RTDS DATA ENTRY PROCESSING AND DISPLAY CHECK. › b. ESL

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating the same ESL checks specified in this table, must determine that the Direct Radar Feed (DRF), if available, is capable of providing its advertised functions.

b. Back-Up Data Processing System

Check for EASL.

Par. 527 Successful no fault execution.

Same as standard.

Same as standard.

342. ES ARTS SYNC FUNCTION.

a. If EASL and ESL are utilized by AT

personnel for operational use.

TI 6191.403 Enabled. Same as standard.

Same as standard.

b. If EASL is released to AF personnel

for maintenance.

TI 6191.403 Disabled. Same as standard.

Same as standard.

343. FS PERIODIC CERTIFICATION TEST VARIABLE SITE PARAMETER (VSP).

a. VSP interval. TI 6191.402 Up to maximum value.

Same as standard.

Same as standard.

b. If FS Periodic Certification is

providing false errors. NOTE: It is necessary to keep abreast of known or reported periodic certification issues. It may be necessary to contact 2nd level engineering support for further instructions.

TI 6191.402 Set VSP interval to 0.

Same as standard.

Same as standard.

344. ES BACKGROUND VERIFICATION.

a. Verification interval. TI 6191.403 Optionally set to enabled. If enabled, Maximum value may be used.

Same as standard.

Same as standard.

345. RTDS DATA ENTRY PROCESSING AND DISPLAY CHECK.

a. FSL

Tower positions processes FS data entry and display as expected.

No error reported by qualified operator on minimum resources for AT operations.

Same as standard.

Same as standard.

b. ESL Tower positions

No error reported by

Same as Same as

350 - 399. RESERVED. › a. Reserved.

CHAPTER 3. STANDARDS AND TOLERANCES

Tolerance/Limit Parameter Reference Paragraph

Standard

Initial Operating processes ES data entry and display as expected.

qualified operator on minimum resources required for AT operations.

standard. standard.

346. TEST TARGET DEVIATION.

a. Check the range/azimuth deviation

of radar/interrogator test targets.

Par. 535 Successful no fault execution.

Same as standard.

Same as standard.

347. FSCK FILE SYSTEM CHECKER.

a. Check file format on individually

affected LRU.

Par. 570 Successful no fault execution.

Same as standard.

Same as standard.

348. FSL/ESL SYNCHRONIZATION

a. If FSL and ESL are utilized by AT

personnel for operational use or in standby operational use.

TI6191.403 Enabled. Same as standard.

Same as standard.

b. If FSL is released to AF or DoD

radar maintenance for maintenance or in cases of FSL failure.

TI6191.403 Disabled. Same as standard.

Same as standard.

349. GPS DAC VALUE

a. Verify that the DAC value on the

GPS Time Unit

Par. 557 60000 ≥ x ≥ 5000 where ‘x’ is the DAC value from the GPS unit.

Approx. 32000. Same as standard.

350 - 399. RESERVED.

a. Reserved.

Chapter 4. PERIODIC MAINTENANCE

400. GENERAL.

a. This chapter establishes all maintenance activities that are required for STARS equipment

on a periodic, recurring basis, and the schedules for their accomplishment. The chapter is divided into two sections. The first section identifies the performance checks (i.e., tests, measurements, and observations) of normal operating controls and functions for STARS, which are necessary to determine whether operation is within established tolerances/limits. The second section identifies other tasks which are necessary to prevent deterioration and/or ensure reliable operation of STARS.

400. GENERAL. › e. Refer to Order 6191.2, STARS Security Handbook, for STARS security…

b. Order 6000.15 requires that certain routine and general maintenance tasks be completed

on all NAS hardware. Refer to Order 6000.15 for a list of routine maintenance requirements and other maintenance requirements.

c. All test equipment must be maintained in proper operating condition. Refer to paragraph

108 of this handbook for special tools. Refer to the latest edition of Order 6200.4, Test Equipment Management Handbook for further information on test equipment.

d. Refer to Order 6000.15 for the periodic maintenance intervals and their tolerances.

e. Refer to Order 6191.2, STARS Security Handbook, for STARS security periodic intervals

and tolerances.

406. SEMIANNUALLY. › b. FSL CGW: Execute diagnostics and perform all checks.

Section 1. PERFORMANCE CHECKS

Subsection 1. FSL Performance Checks

Performance Checks Reference Paragraph

Standards &

Tolerances

Maintenance

Procedures

401. DAILY.

a. At the FSL MCW, check icons for proper indications. Par. 309a Par. 511

b. At the FSL MCW, check System messages. Par. 309b Par. 511

c. Verify proper test target display on at least one TCW or TDW. Par. 309c Par. 512

d. Check Inter-Facility data transmission. Par. 324 Par. 515

e. Check and optimize registration. Par. 325 Par. 533

402. WEEKLY.

a. Resource Verification Test. Par. 310b Par. 510

b. Performance Verification of air traffic control visual and aural

alarms.

Par. 310c TI 6191.402, Par. 516

c. Verify FSL radar data processing and display capability at least one TCW or TDW.

Par. 310d Par. 518

d. Successful selection of backup data processing system. Par. 341a Par. 519

e. At the FSL MCW, check the Periodic Certification Test

Variable Site Parameter (VSP) interval.

Par. 343 TI 6191.402

f. Check range/azimuth integrity. Par. 322a Par. 520

g. Radar Reliability Check. Par. 323a, FSL; Par. 323b, ESL

Par. 521, FSL

h. RTDS target display check Par. 340a

i. RTDS data entry processing and display check. Par. 345a

403. BIWEEKLY.

a. Reserved.

404. MONTHLY.

a. GPS DAC Value Check. Par. 349 Par. 557

405. QUARTERLY.

a. Verify that system time provided by the GPS is the time

displayed at the FSL MCW. If necessary, synchronize FSL MCW system time with GPS.

Par. 338a TI 6191.402 FS Set Date and Time

b. Configure FSL to utilize the standby resources. Par. 308 Par. 529

406. SEMIANNUALLY.

a. FSL NUNIO: Execute diagnostics and perform checks on all

resources.

Par. 301 TI 6191.402

b. FSL CGW: Execute diagnostics and perform all checks. Par. 302 TI 6191.402

411. – 414. RESERVED. › a. Reserved.

Subsection 1. FSL Performance Checks

Performance Checks Reference Paragraph

Standards &

Tolerances

Maintenance

Procedures

c. FSL RDP: Execute diagnostics and perform all checks. Par. 303 TI 6191.402

d. FSL TCW: Execute diagnostics and perform all checks. Par. 304 TI 6191.402

e. FSL TDW: Execute diagnostics and perform all checks. Par. 305 TI 6191.402

f. FSL MCW: Execute diagnostics and perform all checks. Par. 306 TI 6191.402

g. FSL CDR: Execute diagnostics and perform all checks. Par. 307 TI 6191.402

407. ANNUALLY.

a. Reserved.

408. BIANNUALLY.

a. Reserved.

409. TRIANNUALLY.

a. Reserved.

410. AS REQUIRED.

a. FSL software release maintenance. Par. 332 Par. 550

b. FSL software update. Par. 334 Par. 552

c. Map accuracy. Par. 336 Par. 555

d. Fixed target map. Par. 337 Par. 556

e. Verify individual speakers on each of the TCWs and TDWs. Par. 339 TI 6191.409 Audible Alarm Test

f. Software Version Verification. Par. 310a TI 6191.402

g. Firewall/WAN Router Connectivity Performance Check Par. 331 Par. 554

411. – 414. RESERVED.

a. Reserved.

418. MONTHLY. › a. Reserved.

Subsection 2. ESL Performance Checks

Performance Checks Reference Paragraph

Standards &

Tolerances

Maintenance

Procedures

415. DAILY.

a. At the ESL MCW, check icons for proper indications. Par. 317a Par. 511

b. At the ESL MCW, check System messages. Par. 317b Par. 511

c. Check ESL data entry and display functions. Par. 317c Par. 513

d. Check EASL data entry and display functions. Par. 320 Par. 514

e. While EASL and ESL are utilized by AT personnel for

operational use, verify that the Emergency Services (ES) ARTS Sync function is enabled.

Par. 342a TI 6191.403

f. While ESL is utilized by AT personnel for operational use, and EASL is released to AF personnel for maintenance, verify that the ES ARTS Sync function is disabled.

Par. 342b TI 6191.403

g. Check FSL/ESL synchronization. Par. 348 TI 6191.403

416. WEEKLY.

a. Complete Resource Verification Test. Par. 318b TI 6191.403 and Par. 510

b. Performance Verification of air traffic control visual and aural

alarms.

Par. 318c TI 6191.403 and Par. 522

c. Verify ESL radar data processing and display capability at least one TCW or TDW.

Par. 318d Par. 524

d. Check EASL data entry and display functions. Par. 321b Par. 525

e. While EASL and ESL are utilized by AT personnel for

operational use, verify that the Emergency Services (ES) ARTS Sync function is enabled.

Par. 321c Par. 526

f. At the ESL MCW, verify that Background Verification is enabled.

Par. 344 TI 6191.403

g. While ESL is utilized by AT personnel for operational use, and

EASL is released to AF personnel for maintenance, verify that the ES ARTS Sync function is disabled.

Par. 341b Par. 527

h. Check range/azimuth integrity. Par. 322b TI 6191.403

i. RTDS target display check. Par. 340b

j. RTDS data entry processing and display check. Par. 345b

417. BIWEEKLY.

a. Reserved.

418. MONTHLY.

a. Reserved.

424. – 459. RESERVED. › a. Reserved.

Subsection 2. ESL Performance Checks

Performance Checks Reference Paragraph

Standards &

Tolerances

Maintenance

Procedures

419. QUARTERLY.

a. Execute the EDCM diagnostic. Par. 319b TI 6190.44

b. Execute LDDT. Par. 319c Par. 528

c. Verify that system time is provided by the GPS. If it is not, verify that the ESL MCW system time is synchronized with the EASL system time if applicable. Correct ESL MCW system time as required.

Par. 338b TI 6191.403

d. Configure ESL to utilize the standby resources. Par. 316 Par. 531

420. SEMIANNUALLY.

a. ESL NUNIO: Execute diagnostics and perform all checks. Par. 311 TI 6191.403

b. ESL CGW: Execute diagnostics and perform all checks. Par. 312

c. ESL TCW: Execute diagnostics and perform all checks. Par. 313

d. ESL TDW: Execute diagnostics and perform all checks. Par. 314

e. ESL MCW: Execute diagnostics and perform all checks. Par. 315

f. SSS: Execute diagnostics and perform all checks. Par. 326

g. Test Training and Simulation Equipment (TTSE/SIM):

Execute diagnostics and perform all checks.

Par. 327

h. GPW: Execute diagnostics and perform all checks. Par. 328

421. ANNUALLY.

a. Reserved.

422. TRIANNUALLY.

a. Reserved.

423. AS REQUIRED.

a. ESL software release maintenance. Par. 333 Par. 551

b. ESL software update. Par. 335 Par. 553

c. Map accuracy. Par. 336 Par. 555

d. Fixed target map. Par. 337 Par. 556

e. Software Version Verification. Par. 318a TI 6191.403

424. – 459. RESERVED.

a. Reserved.

467. ANNUALLY. › a. Reserved.

Section 2. OTHER MAINTENANCE TASKS

Performance Checks Reference Paragraph

Standards &

Tolerances

Maintenance

Procedures

460. Daily.

a. Cycle CDR tapes for storage and reuse. Remove and store

currently recording CDR tape for minimum specified time period. Use standby tape drive at each CDR cycle.

Tape stored before reuse for a minimum of 45 days from date removed.

TI 6191.402

b. Clean the DLT/DAT drives if the “Use Cleaning Tape” Light

Emitting Diode (LED) is illuminated.

LED Extinguished.

TI 6191.400

461. Weekly.

a. Switch to standby CDR processor. Standby available. TI 6191.402

462. Biweekly.

a. Reserved.

463. Monthly.

a. Reserved.

464. Bimonthly.

a. Reserved.

465. Quarterly.

a. Clean all TCW and TDW trackballs and keyboards. Manufacturer specifications.

TI 6191.400

b. Check surface of TCW and TDW displays and clean as

required.

Visibly dirt and smudge free surface.

TI 6191.400

c. Visually inspect DDM for correct focus, color and alignment. Par. 330 TI 6191.414

d. Check TDW alignment and align as required. Par. 329 TI 6191.400

e. TDM High Efficiency Particulate Air (HEPA) Filter Inspection

and Cleaning (if applicable)

N/A Par. 563, TI6191.400

466. Semiannually.

a. General Equipment Maintenance

1. Blower Fan and Filter Inspection and Cleaning. 2. Rack Cabinet Physical Inspection and Cleaning. 3. TCW Cabinet Physical Inspection and Cleaning. 4. Check Connector Mating. 5. TDW Articulating Arm Check.

N/A N/A N/A N/A N/A

558 559 560 561 562

467. ANNUALLY.

a. Reserved.

470. – 499. RESERVED. › a. Reserved.

Section 2. OTHER MAINTENANCE TASKS

Performance Checks Reference Paragraph

Standards &

Tolerances

Maintenance

Procedures

468. TRIANNUALLY.

a. Reserved.

469. AS REQUIRED.

a. Backup router configuration file(s) from the Flashcard. N/A STR-STARS- 061 Spare Flashcard Configuration

b. Check the Airway Facilities Technical Network for ATS

Maintenance Alerts applicable to STARS. NOTE: For those without FAA Intranet access, the STARS program screens all Maintenance Alerts for applicability to STARS and E-Mails those affecting STARS to the STARS Operational E-Mail List. Facilities may ensure inclusion on this list by sending E-Mail addresses to 9-ACT- [email protected].

The user must be on the FAA Intranet to access this site:

http://aftechnet.f aa.gov

c. At receipt of a Spare, check firmware version and update as necessary.

Update firmware in accordance with latest STARS SSD release.

TI 6191.400

d. At receipt of a Spare, check JumpSTARS version and level,

i.e., FSL or ESL

Confirm version and level in accordance with latest STARS SSD release.

TI 691.484

e. At receipt of spare, label firmware version and JumpSTARS

version and level, i.e., FSL or ESL.

All spares are accurately labeled.

f. Run File System Check (FSCK) after interruption of power that results in an FSL processor shutdown.

Par. 347 Par. 570

g. Verify that the NIS+ service is functioning properly

NOTE: This check should be performed under the following circumstances: 1. Root password change (rpassmass). 2. Remove and Replace (R & R) (Only necessary on the spared box unless the R&R was performed on the SSS, then perform on all processors). 3. After an event or incident that site deems may impact NIS+ functionality or integrity.

Successful no fault execution.

Par. 530

470. – 499. RESERVED.

a. Reserved.

Chapter 5. MAINTENANCE PROCEDURES › 502. – 509. RESERVED.

Chapter 5. MAINTENANCE PROCEDURES

500. GENERAL.

The first section of this chapter contains the procedures for making the performance checks listed in chapter 4, section 1. Section 2 of this chapter contains the procedures or methods for performing the tasks listed in chapter 4, section 2 of this handbook.

501. TECHNICAL PERFORMANCE RECORD ENTRIES.

Order 6000.15 contains guidance and detailed instructions for Field Utilization of FAA Form 6000 series as applicable to the STARS. Entries shall be made in accordance with the instructions published in Order 6000.15.

502. – 509. RESERVED.

e. Detailed Procedure. Check for proper indications at the appropriate… › 2. Check that the minimum required resources (e.g., NUNIO, CGW/RCGW,…

Section 1. Performance Check Procedures

510. STARS FSL/ESL/DRF SUBSYSTEM PROCEDURE FOR RESOURCE VERIFICATION TEST.

a. Objective. Verify that the minimum required resources that can sustain ATC operations

are present and working properly.

b. Discussion. The STARS system certification requirements are listed in Appendix 1, table

3, of this handbook.

c. Test Equipment Required. Not applicable.

d. Conditions. The certifying official must ensure that the correct versions of software and

adaptation are installed and running on each processor utilized in the system. Refer to paragraph 550 or 551 of this handbook for a suggestion to manage multiple versions of software in the system. A chart should be prepared to show the latest version of each program. This chart should be readily available to the certifying official. Ensure that the checks in paragraph 552 or 553 have been completed for FSL and ESL since the last software update.

e. Detailed Procedures. Perform the Resource Verification test from the FSL or ESL MCW.

Verify that the minimum required resources that can sustain the facility AT operation pass. For DRF checks it is necessary to verify that the minimum required resources that can sustain direct radar feed AT operation pass.

511. MCW ICON AND SYSTEM MESSAGE CHECK.

a. Objective. Verify that the minimum required resources that can sustain ATC operations

are present and working properly.

NOTE: The certifying official, using the ESL checks specified in this paragraph, must determine that the Direct Radar Feed (DRF), if available, is capable of providing its advertised functions. It is necessary to have proper coordination between the certifying official at the TRACON or RAPCON, and the remote tower. If necessary, local and/or regional procedures should be developed to coordinate activities between distant facilities and to convey certification information.

b. Discussion. The TSATD service certification requirements are listed in Appendix 1, table

1, of this handbook. This check applies to FS, ES, and DRF.

c. Test Equipment Required. Not applicable.

d. Conditions. These checks must be made while operational programs are being executed.

e. Detailed Procedure. Check for proper indications at the appropriate FSL and/or ESL

MCW:

1. For DRF checks, ensure that the DRF sensor is selected at the TDW. Then drill down into appropriate TOWERS/RADAR GUI at ESL MCW for detailed indications.

2. Check that the minimum required resources (e.g., NUNIO, CGW/RCGW, RDP, TCW, TDW, and LAN equipment) that can retain air traffic operation are available.

513. TSATD ESL/DRF TEST TARGET DISPLAY CHECK. › a. Objective. Verify the ability of constituent facilities to provide…

3. Check for current failure/alarm report messages on the minimum required resources (e.g., NUNIO, CGW/RCGW, RDP, TCW, TDW, and LAN equipment) that can retain air traffic operation.

512. TSATD FSL TEST TARGET DISPLAY CHECK.

a. Objective. Verify the ability of constituent facilities to provide test target reports at correct

display positions in support of ATC operations.

b. Discussion. The required number of displays to be checked will be determined locally.

However, as a minimum, one TCW or TDW shall be checked. This check should be made on a different position than last executed. The TSATD service certification requirements are listed in Appendix 1, table 1, of this handbook.

c. Test Equipment Required. Fixed target map with test target geo-boxes or symbols

appropriate for all applicable sensors.

d. Conditions. These checks must be made while the FSL operational program is being

executed.

e. Detailed Procedures for FSL.

1. Verify proper data entry and display functions of PE/MTI, PARROT/CPME, and RTQC test targets at required TCW(s) and/or TDW(s). The certifying ATSS may check with AT or may choose to perform the following:

(a) Select single sensor display mode.

(b) Verify primary and/or beacon targets are available at the display.

(c) Select a geographic map that contains fixed target geo-boxes for the selected

sensor. Verify that the correct map is displayed.

(d) Enable RTQC display from the DCB.

(e) Verify that the beacon and search RTQCs are displayed on or within the

appropriate geo-boxes or adapted map location symbols, or not more than 1 degree and 1/4 nm from expected position.

(f) Verify that the PARROT/CPME(s) is displayed on or within the appropriate geo-

boxes or adapted map location symbols, or not more than 1 degree and 1/4 nm from expected position.

(g) Verify that the PE/MTI reflector(s) is displayed on or within the appropriate geo-

boxes or adapted map location symbols, or not more than 1 degree and 1/4 nm from expected position.

2. Repeat this procedure for each available sensor.

3. If accessible, switch the display to multi-radar mode. Verify that the display operates in multi-radar mode.

4. After checking all available sensors, return to normal operations.

513. TSATD ESL/DRF TEST TARGET DISPLAY CHECK.

a. Objective. Verify the ability of constituent facilities to provide test target reports at correct

display positions in support of ATC operations.

514. TSATD EASL TEST TARGET DISPLAY CHECK. › e. Detailed Procedures for EASL.

b. Discussion. The required number of displays to be checked will be determined locally.

However, as a minimum, one TCW or TDW shall be checked. The TSATD service certification requirements are listed in Appendix 1, table 1, of this handbook.

c. Test Equipment Required. Fixed target map with test target geo-boxes or symbols

appropriate for all applicable sensors.

d. Conditions. These checks must be made while the ESL operational program is being

executed.

NOTE: If there is an RT connected to the SOS, and the RT has a direct Local Radar Feed, then this check shall be made on the RT using the direct Radar Feed. This is done by selecting the DRF sensor on the DCB at the TDW.

e. Detailed Procedures for ESL.

1. Verify proper data entry and display functions of PE/MTI, PARROT/CPME, RTQC test targets at all required TCW(s) and/or TDW(s). The certifying ATSS may check with AT or may choose to perform the following:

(a) Select sensor.

(b) Verify that primary and/or beacon targets are available at the display.

(c) Select a geographic map associated with the selected sensor that contains fixed

target geo-boxes or symbols for the selected sensor. Verify the correct map is displayed.

(d) Enable RTQC display from the DCB.

(e) Verify that the beacon and search RTQC(s) is displayed on or within the

appropriate geo-box or not more than 1 degree and 1/4 nm from expected position.

(f) Verify that the PARROT/CPME(s) is displayed on or within the appropriate geo-

box or not more than 1 degree and 1/4 nm from expected position.

(g) Verify that the PE/MTI reflector(s) is displayed on or touching the appropriate map

symbol or not more than 1 degree and 1/4 nm from expected position.

2. Repeat this procedure for each available sensor.

3. After checking all available sensors, return to normal operations.

514. TSATD EASL TEST TARGET DISPLAY CHECK.

a. Objective. Verify the ability of STARS to display test targets at correct display positions in

support of terminal ATC operations.

b. Discussion. The required number of displays to be checked will be determined locally.

However, as a minimum, one TCW or local TDW shall be checked. This check should be made on a different position than last executed. The TSATD service certification requirements are listed in Appendix 1, table 1, of this handbook.

c. Test Equipment Required. Not applicable.

d. Conditions. These checks must be made while EASL operational programs are being

executed.

e. Detailed Procedures for EASL.

516. › b. Discussion. The required number of displays to be checked will be…

1. Verify proper indications at all required TCWs. Ensure that selected display is in EASL mode:

(a) Verify that primary and/or beacon targets are available at the display.

(b) Select a geographic map associated with the selected sensor. Verify that correct

map is displayed.

(c) Verify that PE/MTI reflectors, PARROTs/CPMEs, primary and beacon RTQC are

displayed over the appropriate geographic map symbols and/or expected locations.

(d) Utilize targets of opportunity that are landing to verify that targets and map are

presented correctly on the display.

2. Repeat this procedure for each available sensor.

515. GENERAL INFORMATION AUTOMATED FLIGHT PLAN (GIAFP) FLIGHT DATA PROCESSING INPUT/OUTPUT CHECK.

a. Objective. Verify ability of STARS to communicate with other facilities in support of

terminal air traffic operations.

b. Discussion. The GIAFP certification requirements are listed in Appendix 1, table 2 of this

handbook. Reference IFDT error messages and alarms in TI6191.404 STARS System Message Dictionary.

c. Test Equipment Required. Not applicable.

d. Conditions. These checks must be made while in FSL.

e. Detailed Procedures.

1. At the FSL MCW, drill down into the NUNIO A and B Module 6 status and check the icon associated with the inter-facility line. Verify the module is online. Investigate any red icon indications.

2. At the FSL MCW, drill down from the NAS status icon into the IFDT. Verify the heartbeat is present and check the icons associated with the main and alternate interfacility data transfer lines. Investigate any red icon indications.

3. Verify that Inter-Facility is working properly by checking for absence of IFDT failure messages:

(a) #102 Module 6 Heartbeat: Failed

(b) #277 IFDT Test Failure

516. STARS FSL PROCEDURE FOR PERFORMANCE VERIFICATION OF ATC VISUAL AND AURAL ALARMS.

a. Objective. Verify the ability of FS STARS to process and display aural and visual alarms in

support of terminal air traffic control operations, and verify RTQC recieve status. The alarms include special condition codes and safety alert alarms i.e., MSAW and CA. This check is performed at the MCW and/or display positions with the exception of the RDP safety alert processing, and RTQC receive status. The both of these checks are performed internally in the RDP and is verified only from the MCW.

b. Discussion. The required number of displays to be checked will be determined locally.

However, as a minimum, one TCW/TDW shall be checked. This check should be made on

(e) The following definitions are useful to determine pass/fail… › (5) PROCESSED – Actual number of assertions processed in the PVER…

a different position than last executed. There are various methods that can be used to verify special condition codes and the safety alert alarms. The full PVER, abbreviated PVER, and targets of opportunity, are described here. Any one of these methods will satisfy the certification requirement. However, RDP safety alert processing, and RTQC receive status are only accomplished using the full PVER method so it is necessary to run one full PVER each certification period. Running the full PVER on any one TCW or TDW, remote or local, will suffice for this portion of the check.

1. Full FS PVER: There are three basic processing functions that are tested by the FS PVER. They are special condition codes, safety alert, and RTQC threshold monitoring. The special condition codes and the safety alerts implement aural and visual alarms that are observable at the display position within the first two minutes of the PVER. The RTQC monitoring tests have no display. Once the PVER is requested, the following items provide guidelines on the execution and results analysis of the Full FS PVER;

(a) A successful execution of the PVER is indicated on the PVER test report by an

end of test notification specifying the duration of the test as well as confirmation that the proper indications are displayed. The specialist should inspect the “Test Case Summary” at the bottom of the Performance Verification Test Report to ensure all expected test cases were processed. A discrepancy between these numbers may indicate a problem with the PVER scenario, the execution of the scenario, or the system data processing and display. If this occurs print the report, and retry the scenario. If the discrepancy reoccurs, print the second report and contact the assigned OSF.

(b) If the failures pertain to RTQC receive status (Beacon/Search RTQC, PARROT or

PE), perform the checks specified in paragraphs 401a, 401b, 401c, 402f, and 402g, at minimum, to verify if the RTQC monitoring threshold is performing within standards.

(c) If the failures pertain to special condition codes or safety alert processing it is

acceptable to rerun the PVER scenario and make visual confirmation that the situation displayed is performing as expected. It is permissible to corroborate with AT to determine if system is performing as expected using targets of opportunity. See paragraph 516 b3 for further information.

(d) If the discrepancy reoccurs, print the second report and contact the assigned OSF.

(e) The following definitions are useful to determine pass/fail criteria of the system

performance verification:

(1) ASSERTIONS – Boolean test cases scripted into the scenario that report as

PASS, FAIL and both the expected and actual results of the test case.

(2) ACTUAL – The column that reports the result condition of an assertion.

(3) STATUS – This column only lists the Boolean result of an assertion. The

values are only PASS or FAIL.

(4) EXPECTED – Number of assertions scripted into the PVER scenario and also

the column that specifies the pass condition of an assertion.

(5) PROCESSED – Actual number of assertions processed in the PVER scenario

516. › e. Detailed Procedures for FSL.

(6) REJECTED – This indicates assertions that are rejected due to logic errors,

undefined fixes, aircraft type, timing, etc. Rejections are typically errors with the PVER scenario.

(7) MISSING – The difference between the expected assertions and the actual

number of processed assertion statements.

(8) EXTRA – Any additional assertion statements processed but are not listed in

the scenario.

(9) NOTP – Not present, is used to test or report the absence of special condition

codes.

(10) MISS – Similar to NOTP but used with RTQC assertions.

(11) EXEC – Excessive is used to test or report excessive RTQC.

(12) CURR – Current is used with CA and MSAW assertions and defines the

aircraft situation as being in present violation of separation rules or low altitude parameters, respectively, as opposed to PRED.

(13) PRED – Prediction indicates future CA or MSAW violations unless course,

speed, or altitude is changed to mitigate safety transgressions.

2. Abbreviated FS PVER: The abbreviated FS PVER uses the same scenario as the full FS PVER. It is initiated the same way as the full PVER but is canceled after the special condition code and safety alert processing checks are complete. A full PVER scenario may take up to 20 minutes to complete. However, the special condition code and safety alert processing checks are performed within the first 4 minutes. Premature cancellation of a PVER is performed at the MCW by selecting the CANCEL button on the PVER report window. The report will display the results of the portion of the check conducted up to that point. Once the CANCEL button is selected all other buttons, including the CLOSE button, is temporarily grayed-out. When the CLOSE button returns from the grayed-out state, it is selected for final termination of the PVER. Coordination may be required by the observer and the MCW operator especially if this method is used to check aural and visual alarms at remote tower locations.

3. Targets of opportunity may be used to verify processing and display of special condition codes and safety alert alarms. It is permissible to corroborate with AT to perform this check. Lack of user complaints is an acceptable method of coordination provided that AT is advised to report any issues with visual and aural alarms.

c. Test Equipment Required. ATCoach PVER scenario provided by first-level support. The

TTSE must be online and available and ATCoach must be in ready state on the TTSE.

d. Conditions. The display selected for PVER may not have airspace and only one PVER

may execute at a time including ES PVER. The PVER check includes visual and aural confirmation that the alarms perform as expected. For single display radar towers only, if release of the display impacts AT, then results noted from the report and/or lack of error reports from qualified operators are acceptable. Checks for remote or distant positions may require assistance. If assistance is not available, or if the site is unable to release positions, then targets of opportunity with lack of user complaints is an acceptable method of performing this check.

e. Detailed Procedures for FSL.

518. › a. Objective. Ensure that STARS data processing and display system are…

1. FSL PVER is performed on display positions that do not have airspace. Checking if a display has airspace or no airspace can be done in the following ways:

(a) At the MCW, drill down into the display detailed status window and verify that the

“Equipment State” is in STANDBY.

(b) Use the “FS View Consolidation” report on the MCW. If all the keyboard identifiers

assigned to a TCW/TDW are blank under the TCP column, the position has no airspace.

(c) Observe the System Status Area (SSA) on the TCW/TDW. If consolidation

information on line S is blank, the position has no airspace. “1R CON: 1R” is an example of consolidation information on line S in the SSA.

2. If the chosen position has airspace, the airspace is reassigned using the following commands at a TCW/TDW.

(a) Login any display position if not already logged-in.

(b) Enter the command, <F7 C (sending keyboard) (receiving keyboard) +><Enter>,

where the sending keyboard position is the one selected for PVER.

3. From the TCW/TDW, execute the Performance Verification on the TCW/TDW.

4. The display position will blank momentarily as it transitions into the PVER mode.

5. As the scenario runs, ensure that the following codes are properly identified and displayed.

(a) EM (Emergency) 7700

(b) RF (Radio Failure) 7600

(c) SA (Suspect Aircraft) 1236

(d) HJ (High-jack) 7500

(e) CA (Conflict Alert)

(f) LA/MSAW (Low Altitude)

6. If using the abbreviated method for this check, the specialist may cancel the scenario now by selecting <CANCEL> on the PVER window, then selecting <CLOSE> when that option changes from a grayed-out state.

7. After the test is completed, verify that all beacon and search RTQC test cases have a “PASS” status, all PARROT and PE test cases have a “PASS” status, all Special Code (SPC) test cases have a “PASS” status, and Test Report Summary indicates all test cases “PASS.”

8. At the satisfactory completion of the PVER, return the display to normal operational capability.

517. RESERVED.

518. STARS FSL SUBSYSTEM CERTIFICATION PROCEDURE RADAR DATA PROCESSING AND DISPLAY CAPABILITY.

Continue reading ↓ 120 of 318 passages shown