U.S. DEPARTMENT OF TRANSPORTATION …...NAS Safety Operational Risk to Air Traffic Control and Pilots – The Safety Risk Management Report is available at: TBD. 6. Recommendations

Distribution: 61MAA Initiated By: AJW-14A

U.S. DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION

Air Traffic Organization Policy ORDER

JO 6162.X

Effective Date:XX/XX/XXXX

SUBJ: Maintenance of Information Display System, Version 4 (IDS-4) 1. Purpose. This handbook provides guidance and prescribes technical standards and tolerances, and procedures applicable to the maintenance and inspection of the Information Display System, Version 4 (IDS-4). It also provides information on special methods and techniques, which 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, General Maintenance Handbook for National Airspace System (NAS) Facilities. 2. Audience. This document requires actions by the Airway Transportation System Specialist (ATSS) at operational facilities with Facility, Service, and Equipment Profile (FSEP) equipment: IDS-4. 3. Cancellation. None. 4. Forms Listing. FAA Forms may be electronically downloaded at http://employees.faa.gov/tools_resources/forms/. 5. Risks. NAS Safety Operational Risk to Air Traffic Control and Pilots – The Safety Risk Management Report is available at: TBD. 6. Recommendations for Improvement. Users are encouraged to submit recommendations for improvement to [email protected].

for Timothy S. McCurdy Acting Director, Safety and Operations Support

10/27/2010 JO 6162.xx

i

Table of Contents Chapter 1. General Information and Requirements

Paragraph Page

100. Purpose of this Order..................................................................................... 1-1 101. Audience ........................................................................................................ 1-1 102. Where Can I Find this Order?........................................................................ 1-1 103. Aircraft Accidents ........................................................................................... 1-1 104. Maintenance and Modification Procedure ..................................................... 1-1 105. Safety ............................................................................................................. 1-2 106. Certification .................................................................................................... 1-2 107.-199. Reserved.

Chapter 2. Technical Characteristics Section 1. General

200. General ........................................................................................................... 2-1 201.-202. Reserved. Section 2. IDS-4

203. IDS-4 Components ................................................................................................... 2-1 204.-299. Reserved.

Chapter 3. General Information and Requirements Section 1. General

300. General ....................................................................................................... 3-1 301. Reserved.

Section 2. IDS-4

302. IDS-4 ........................................................................................................ 3-1 303.-399. Reserved.

Chapter 4. Periodic Maintenance Section 1. General.

400. General .......................................................................................................... 4-1 401.-403. Reserved. Section 2. Performance Checks.

404. Annually .......................................................................................................... 4-1 405.-499. Reserved.

10/27/2010 JO 6162.XX

ii

Table of Contents (Continued)

Chapter 5. Maintenance Procedures Paragraph Page

Section 1. General.

500. General........................................................................................................... 5-1 501. FAA Form Series………………………………………………………………... Section 2. Performance Check Procedures 502. Workstation Clock .......................................................................................... 5-1 503. Workstation Data Display............................................................................... 5-2 504. Workstation Network Statistics ...................................................................... 5-3 505. External Data Interface – Clock ..................................................................... 5-5 506. External Data Interface – DASI...................................................................... 5-6 507. External Data Interface – Ribbon Display Terminal (RDT) (ITWS/TDWR, .

LLWAS-NE++, WSP) 5-7

508. External Data Interface – LLWAS-2 or WME ................................................ 5-8 509. External Data Interface – RVR....................................................................... 5-9 510. External Data Interface – AWIPS/AFOS........................................................ 5-10 511. External Data Interface – FDIO...................................................................... 5-11 512. External Data Interface – AWSS.................................................................... 5-11 513. External Data Interface – ASOS .................................................................... 5-12 514. External Data Interface – WARP ................................................................... 5-13 515. External Data Interface – NOTAM ................................................................. 5-14 516.-599. Reserved. Appendix 1. Certification Requirements Table Page 1 IDS-4 .............................................................................................................. 4

10/27/2010 JO 6162.XX

Chap 1 1-1 Par 100

Chapter 1. General Information and Requirements

100. Purpose of this Order. 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 Information Display System, Version 4 (IDS-4). 101. Audience.

a. This document requires actions by the Airway Transportation System Specialist (ATSS) at operational facilities with Facility, Service, and Equipment Profile (FSEP) equipment: Information Display Information, Version 4 (IDS-4).

b. The ATSS and all administrative personnel must subscribe to the Auto-Notifications Services for electronic library release notifications at http://technet.faa.gov/. Administrative offices can print these documents for local use as required. 102. Where Can I Find this Order?

a. For electronic copies, use the Technical Library website at http://nas.amc.faa.gov’technical_library/index.jsp.

b. The ATSS must keep accurate FSEP records and Logistics Inventory System (LIS) addresses to receive printed copies. Printed copies are mailed to the ATSS at operational facilities with an accurate FSEP record using the LIS mailing address per Order 6000.5D, Facility, Service, and Equipment Profile (FSEP).

c. To update FSEP information, visit this link: https://intranet.faa.gov/faaemployees/org/linebusiness/ato/operations/technical_operations/ajw1/ajw162/ fsep/contacts/.

d. The Periodic Maintenance/Certification Scheduling (PMS) database is maintained by the Office of Primary Responsibility (OPR). The release of this document notifies the field of an update to the Remote Monitoring and Logging System (RMLS) National PMS database. An RMLS template will be available to the field for remote maintenance logging in approximately five working data after release of this document. 103. Aircraft Accidents. When aircraft accidents or incidents occur, Air Traffic Organization Technical Operations personnel are responsible, 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. 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. Maintenance and Modification Procedure.

a. FAA Order 6000.15, this handbook, the applicable equipment instruction book, and other applicable handbooks shall be consulted and used together by the maintenance technician in all duties and activities for the maintenance of MLS facilities and equipment. The three documents shall be considered collectively as the single official source of maintenance policy and direction authorized by Operational Support. References located in the appropriate paragraphs of this handbook entitled Chapter 3, Standards and Tolerances, Chapter 4, Periodic

10/27/2010 JO 6162.X

Chap 1 1-2 Par 104

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 or performance parameter, performance check, maintenance task or maintenance procedure.

b. The latest edition of FAA Order 6032.1, Modification to Ground Facilities, Systems, and Equipment in the National Airspace System, contains comprehensive direction concerning the development, authorization, implementation, and recording of modifications to facilities, systems, and equipment in commissioned status. It supersedes all instructions published in earlier editions of maintenance technical handbooks and related directives. 105. Safety.

a. Personnel shall exercise care while working on electrical system equipment. Personnel shall exercise particular caution when high voltages are present, when inspection plates and dust covers are removed, or when access doors are open exposing internal wiring. Personnel should never work alone on electrical equipment.

WARNING

Contact with ac or dc potentials can result in severe shock, burns, or loss of life. Use local lockout/tagout procedures when energizing, startup, or release of energy can occur. This is necessary to make sure that other personnel cannot start the power source during maintenance. Shock hazards can kill. Such procedures are a requirement from the latest version of Order 3900.19, FAA Occupational Safety and Health Program.

b. All individuals must be thoroughly familiar with general electrical system maintenance procedures and safety practices, prior to working on equipment, to not endanger themselves or others. Ignorance and carelessness are the predominant factors involved in most accidents. Personnel shall pay particular attention to the proper use of the grounding cable prior to working on high-voltage circuits.

c. Personnel shall apply lockout/tagout procedures in accordance with the latest edition of Order 3900.49 when servicing or maintaining equipment. Personnel shall take precautions to prevent activating the engine generators (E/G) while conducting service or repairs. Personnel shall follow the applicable safety and work practices contained in the latest edition of Orders 3900.49, Control of Hazardous Energy During Maintenance, Servicing, and Repair and 6000.15, General Maintenance Handbook for National Airspace System (NAS) Facilities, and pay particular attention to the specific warnings and cautions contained in this handbook and in the equipment instructions. 106. Certification. Refer to the latest edition of Order 6000.15 for general guidance on the certification of NAS systems. Refer to appendix 1 of this handbook for the specific requirements applicable to the certification of the IDS-4 system. The latest version of TI 6030.1, User's Manual for the Maintenance Management System (MMS), provides detailed instruction for making appropriate type entries. 107.-199. Reserved.

10/27/2010 JO 6162.XX

Chap 2 2-1 Par 200

Chapter 2. Technical Characteristics

Section 1. General 200. General. The Information Display System, Version 4 (IDS-4) has been defined as a system that accepts processes, distributes, and displays general-purpose video information in an air traffic control environment. The IDS-4 typically utilizes a dedicated serial network, dedicated External Data Interface (EDI) & System Interface Unit (SIU) equipment, and dedicated workstation computers with dedicated monitors, to provide weather information about the aeronautical environment. The IDS-4 is typically located in the tower cabs, TRACON and other FAA facilities. The IDS-4 collects weather and other aviation-related information from many sources and presents the data in a user-defined screen format. Screen data and menu structure is designed by the IDS-4 Database Administrator for use by all facilities on the IDS-4 network The IDS-4 also provides a communications interface for the collection and display of real-time ASOS data, Automation of Field Operations and Services (AFOS) data, RVR, LLWAS, other IDS-4 system data, Flight Data Input Output (FDIO), and other FAA-designated interfaces. 201.-202. Reserved.

Section 2. IDS-4 203. IDS-4 Components. The IDS-4 collects weather and aviation-related information from many sources and presents the data to the user via workstations. The major level hardware for the IDS-4 consists of an EDI, SIU, Workstations, and Pre-Processors. At least one workstation at every site is designated as the Database Administrator position where software and hardware above the routine workstation configuration may be present. All interconnected IDS-4 computers are connected by an RS-485 serial network using a proprietary protocol from the manufacturer. The IDS-4 is not an Ethernet based system thus Ethernet based network technology and equipment is not used.

a. External Data Interface (EDI) Cabinet.

(1) The EDI provides the hardware and software necessary to interface the IDS-4 to various other data systems.

(2) The data interface may use RS-485, RS232, 20mA Current Loop, or even IRIG-B protocols. (3) The EDI consists of primary and redundant computers with site specific data interfaces and Site

Adaptation Files (SAF). (4) Ancillary components such as a video display, keyboard, etc, will also be present to facilitate

computer functions. (5) The EDI and associated components are designed to be installed in a typical 19” equipment rack.

b. System Interface Unit (SIU).

(1) The SIU provides the hardware and software necessary to interface the IDS-4 to various data systems much like the EDI with site specific data interfaces and Site Adaptation Files (SAF).

(2) These data interface may use RS-485, RS232, 20mA Current Loop, or even IRIG-B protocols. (3) Unlike the EDI, the SIU does not include a redundant computer. (4) Ancillary components such as a video display, keyboard, etc, will also be present to facilitate

computer functions. (5) The SIU is designed to be installed into a 19” equipment rack, but it may alternately be placed on

a desktop for normal operation.

10/27/2010 JO 6162.X

Chap 2 2-2 Par 203

c. Workstations.

(1) Each IDS-4 workstation consists of a workstation computer, monitor, keyboard, 3.5” Floppy Disk Drive (FDD), an RS-232 serial trackball, and a serial data card. The operating software of IDS-4 workstation is DOS 6.22 and it runs the IDS-4 display application.

(2) Data from the EDI/SIU and other workstations is received via an RS-485 serial network using the

SeaLevel serial data cards in the workstations. (3) The IDS-4 software contains all hardware drivers and other components necessary to operate a

workstation on the IDS-4 network. (4) While the workstation are capable of audible alerts, these alerts are only broadcasted through the

built in PC speaker. Sound cards and external load speakers are not supported. (5) IDS-4 does not natively support LCD monitors however many are found to be compatible with

certain software configuration adaptations. Limited touch screen support is available from the IDS-4 software. (6) CD-ROM, USB, and other forms of removable media are not supported in IDS-4 due to software

limitations and age of the system. (7) Workstations can also be used for external data interfaces. When used in this fashion, the

workstation will process the incoming data into the IDS-4 database and disseminates to the rest of the network. d. Pre-Processors.

(1) When a workstation is used to host an EDI interface, then an intermediary computer must be used prior that connection. This intermediary computer is called a Pre-Processor.

(2) The role of the Pre-Processor is to receive the incoming data, format it for transport on the IDS-4

network, and then relay the “processed” data to IDS-4 workstations. (3) Each Pre-processor workstation consists of a workstation computer, 3.5” FDD, and a serial data

card. The operating software of IDS-4 workstation is DOS 6.22 and it runs the IDS-4 display application. (4) Other workstation component such as a monitor, keyboard, and RS-232 serial trackball are

optional and often not present. (5) The Pre-Processor software is site specific for the locations and the types of data interfaces.

c. Database Administrator Workstation.

(1) The IDS-4 operational capabilities of a Database Administrator workstation are the same as a typical IDS-4 workstation.

(2) To accommodate the entry of data files, many facilities have configured the Database

Administrator workstation with dual boot capability. The primary Operating System (OS) will always be set for the DOS partition with the IDS-4 loaded in it. The secondary OS will typically be set for a Windows configuration on the local facility administrative network.

(3) The Windows partition allows for use of removable media, graphics editing software, scanners,

printers, backup of the IDS-4 databases, etc. 204. -299. Reserved.

10/27/2010 JO 6162.XX

Chap 3 Par 300 Page 3-1

Chapter 3. Standards and Tolerances

Section 1. General 300. General.

a. This chapter prescribes the standards and tolerances for the Information Display System, Version 4 (IDS-4), as defined and described in the latest edition of Order 6000.15. Since the IDS-4 receives information from other interfacing systems, and displays this information to the user, there are no measureable parameters with specifically quantifiable ranges of values applicable here. All key performance parameters and/or key inspection elements are identified by an arrow (→) placed to the left of the applicable item.

b. Entries in the reference paragraph column refer to this handbook. A handbook reference is identified by a paragraph number only, for example, 502. 301. Reserved.

Section 2. IDS-4

Tolerance/Limit Parameter ReferenceParagraph

Standard Initial Operating

302. IDS-4. → a. Workstation Clock ......................................

502 Successful Time Display

Verification

±3 Seconds Same as standard

→ b. Workstation Data Display ........................... 503 Current and

Accurate Display of Weather Data

Same as standard Same as standard

→ c. Workstation Network Statistics................... 504 No unacceptable

error level Same as standard Same as standard

d. External Data Interfaces. (1) Clock ........................................... 505 Successful Time

Display Verification

±3 Seconds Same as initial

(2) Digital Altimeter Setting (DASI)............ 506 Exact Data



(3) Ribbon Display Terminal (RBDT) ......... 507 Exact Data



(4) Low-Level Windshear Alert ................... System (LLWAS-2).

508 Exact Data Display

Verification


(5) Runway Visual Range (RVR)................. 509 Exact Data



(6) Advanced Weather Information Pro- ...... cessing System (AWIPS) and Automation of Field Operations and Services (AFOS).

510 Acceptable Zulu Time in Display

Data


10/27/2010 JO 6162.XX

Page 3-2 Chap 3 Par 302

Section 2. IDS-4 (Continued)

Tolerance/Limit Parameter

Reference Paragraph

Standard Initial Operating

(7) Flight Data Input/Output......................... (FDIO).

511

Acceptable Date Display Data

Same as standard

Same as standard

(8) Automated Weather Sensor System........ (AWSS).

512

Exact Data


Same as standard

Same as standard

(9) Automated Surface Observing System ... (ASOS).

513 Exact Data Display

Verification


(10) Weather and Radar Processing System... (WARP).

514 Acceptable Date on Display Data


(11) Notice to Airman (NOTAM) ..................

515 Acceptable Date on Display Data


303.-399. Reserved.

10/27/2010 JO 6162.XX

Chap 4 4-1(4-2 Blank) Par 400

Chapter 4. Periodic Maintenance


a. This chapter establishes all the maintenance activities that are required for IDS-4 systems on a periodic 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, which are necessary to determine whether operation is within established tolerances/limits. The second section identifies other maintenance tasks, which are necessary to prevent deterioration and/or ensure reliable operation. Refer to the latest edition of Order 6000.15, for additional general guidance.

b. The activities and schedules listed below are intended to provide only the minimum maintenance required to keep the equipment in a satisfactory operating condition. Under some conditions, additional maintenance may be required. The schedules reflect the maximum permissible intervals between successive accomplishments to ensure that the performance of the equipment is reliable and within tolerance.

c. Unless otherwise indicated, references such as 502 are to paragraphs within this handbook. References such as "IB" are to the appropriate equipment instruction books. 401 - 403. Reserved.

Section 2. Performance Checks

Reference Paragraph Performance Checks Standards and

Tolerances Maintenance Procedures

404. Annually. a. Workstation Clock................................................................................... 302a 502 b. Workstation Data Display ....................................................................... 302b 503 c. Workstation Network Statistics .............................................................. 302c 504 d. Clock Interface......................................................................................... 302d (1) 505 e. Digital Altimeter Setting (DASI) ............................................................ 302d (2) 506 f. Ribbon Display Terminal (RDT) ............................................................ 302d (3) 507 g. Low-Level Wind Shear Alert System (LLWAS-2)................................ 302d (4) 508 h. Runway Visual Range (RVR) ................................................................. 302d (5) 509 i Advanced Weather Information Processing System (AWIPS) ............ and Automation of Field Operations and Services (AFOS).

302d (6) 510

j Flight Data Input/Output (FDIO) .......................................................... 302d (7) 511 k. Automated Weather Sensor System (AWSS) ........................................ 302d (8) 512 l. Automated Surface Observing System (ASOS)..................................... 302d (9) 513 m. Weather and Radar Processing System (WARP) ................................. 302d (10) 514 n. Notice to Airman (NOTAM) ................................................................... 302d (11) 515 405.-499. Reserved.

10/27/2010 JO 6162.XX

Chap 5 5-1 Par 500

Chapter 5. Maintenance Procedures


a. This chapter establishes the procedures for accomplishing the various essential maintenance activities that are required for IDS-4 on either a periodic or incidental basis. The first section of this chapter describes the procedures to be used in making the performance checks listed in chapter 4, section 1. The second section describes the procedures for doing the tasks listed in chapter 4, section 2, if any. Refer to the latest edition of Order 6000.15 for additional general guidance.

b. Conditions during maintenance activities must duplicate as closely as practicable the conditions

experienced during normal, unattended operation. For example, building thermostats must be at their normal settings, shields must be kept in place as much as possible, outside doors must be closed, etc.

c. External data interfaces to the IDS-4 from FAA certified systems such as RVR, DASI, etc, must be

compared to the associated display of that system. External data interfaces to systems that are not FAA certified such as ASOS, AFOS/AWIPS, etc must be compared to a verified or reliable display of the data from that system. The certification record for the external data interface into the IDS-4 is recorded in the logs at the location where the interface is established into the IDS-4. For example, if a tower has an RVR interface into the IDS-4, then the RVR data displayed on IDS-4 would be compared to an RVR display head collocated at the same tower. Thus, the certification statement for the IDS-4 RVR interface would appear only in the tower logs where the data comparison had occurred. This certification process relies on the constituent system, RVR in this example, to assure certification of that system. The IDS-4 external data interface certification statement is not intended to imply any conditional assessment about the accuracy of the data being received. The IDS-4 external data interface certification statement merely says that what is received by IDS-4 is accurately presented on the IDS-4 displays.

d. Information from local data interfaces into IDS-4 from external systems such as RVR, DASI, etc, will be

viewable on all IDS-4 displays throughout the entire IDS-4 network. However, the IDS-4 is only certified at the facility where it is established. For example, if a satellite tower on an IDS-4 network has a local RVR interface then the IDS-4 is certified only at that tower. Likewise other satellite facilities on an IDS-4 network would certify their IDS-4 at their locations. Thus all locations with IDS-4 displays that can view the data from other satellite towers would not require recertification. It follows that IDS-4 facilities with local data interfaces are required to maintain separate certification status or provide communication when such cannot be achieved.

e. Momentary or temporary service outages experienced due to a constituent system failure does not affect

the certification level of the IDS-4. However, if service restoration requires maintenance to the IDS-4 then certification is required. For example, the certification status of IDS-4 is not affected if the RVR interface experiences an outage because of annual maintenance or a repair activity on the RVR. But, if restoring the RVR data on IDS-4 requires the technician to perform IDS-4 equipment repair or reconfigure the IDS-4 software then IDS-4 certification is required. 501. FAA Form Series. The latest version of Order 6000.15 contains policy, guidance, and detailed instruction for field use of the FAA Form 6000-8 series. The IDS-4 contains no qualifying trend data elements, therefore, the IDS-4 requires no associated Technical Performance Record (TPR) completed as part of regular maintenance.

10/27/2010 JO 6162.XX

Chap 5 5-2 Par 502

Section 2. Performance Check Procedures 502. Workstation Clock.

a. Object. The purpose of this procedure is to verify accurate display of workstation time to be in tolerance as specified in Chapter 3, as compared to a facility time reference.

b. Discussion.

(1) Accurate time setting on the workstations is critical to functionality of the time-out, data expiration, alarm, and alerting functions. Inaccurate time setting on the workstations may render those functions unreliable and thus promote the presentations of data that should not be presented and/or impact the reliability of alarm and alerting functions.

(2) Time on the IDS-4 has two components: the clock interface to the facility time reference and the

separate system synchronization process. (3) The Data Interface Source can be at a workstation, and EDI, or and SIU. For the procedure to verify the

Clock, refer to paragraph 505 below. (4) The system synchronization process is the function of the IDS-4 where the system Time Source

broadcasts time updates to all workstations on the IDS-4 network. This process does not include an automated verification, thus meaning the time source does not guarantee all workstations actually receive the update.

(5) Lack of time updates at a workstation will not result in any visible awareness indicators to the end

user. Thus a workstation can have inaccurate time and there is nothing on the IDS-4 system to detect that situation.

c. Test Equipment Required.

(1) No test tools or equipment is required.

(2) Access to a facility time reference will be needed for comparison purposes.

d. Procedure. Implement this procedure on each IDS-4 workstation used in the Terminals Environment. (1) At the workstation IDS-4 display, check the time indication as seen in the IDS-4 clock. The default

location for the IDS-4 clock is the upper right corner and displayed in the top menu bar. (2) If the time in the IDS-4 clock is out of tolerance as specified in Chapter 3, then reboot the workstation

with a power cycle. (3) If IDS-4 clock time indication is still out of tolerance as specified in Chapter 3, after the reboot then

proceed with corrective action. 503. Workstation Data Display.

a. Object. The purpose of this procedure is to verify accurate display of workstation data when compared to other workstations in the network or known good sources of the data.

b. Discussion.

(1) Accurate display of data on the workstations is critical to reliability of the service to ATC. There are a number of system trouble scenarios where as the IDS-4 will not present a visible aware indication to the end user that the

10/27/2010 JO 6162.XX

Chap 5 5-3 Par 503

displayed data is no longer updating properly. Associated time-outs and data expirations setting can also be impacted in such a way as to continue presentations of data that should not be.

(2) In many case when a workstation is no longer able to receive updates from the network then a red

banner at the bottom of the IDS-4 screen will periodically indicate. Red banner indications should always be associated with corrective actions. A workstation indicating a red banner related to network connectivity should not be certified for operation.


(1) No test tools or equipment is required. (2) Access to another workstation on the IDS-4 network that is known to display accurate data, or

access to a known good source of data presented on the IDS-4 display.

d. Procedure. (1) On any of the data screens at the workstation being checked, select an element of data to compare

against another IDS-4 workstation or known good source of the data. It is recommended that you select a data element on an SIU page that is updated frequently, such as a weather related data element.

(2) Verify the selected data element agrees with the same data element on the comparison. (3) You need only check one or two data elements to establish that the workstation is receiving updates

and that it is also displaying them correctly.

(4) If updates are not being displayed correctly, take corrective repair actions. A workstation not displaying correct data should not be certified for operation.

504. Workstation Network Statistics.

a. Object. The purpose of this procedure is to verify reliability of workstation data reception. b. Discussion.

(1) Accurate display of data on the workstations is critical to reliability of the service to ATC. There are a number of workstation trouble scenarios where as the IDS-4 presents no visible indication to the end user that the displayed data is not always being updated properly.

(2) Workstation communication issues may experience intermittent operations resulting in only some, but

not all, updates to be properly received and updated. (3) Associated time-outs and data expirations setting can also be impacted in such a way as to continue

presentations of data that should not be viewable. (4) In many cases, when a workstation is intermittently receiving updates from the network, a red banner at

the bottom of the IDS-4 screen will be periodically shown. Red banner indications should always be associated with corrective actions. A workstation indicating a red banner related to network connectivity should not be certified for operation.

10/27/2010 JO 6162.XX

Chap 5 5-4 Par 504

(5) Normal operation of an IDS-4 workstation should indicate no statistical errors. The only exception to that statement is for those IDS-4 computers with MB820 motherboards installed. The MB820 motherboards are an End of Life sustainment decision for the IDS-4, but they are not 100% compatible. The MB820 motherboards will indicate errors on both the DIM and PORT statistics at a very low rate. Typical accrual rates are 1 error for every 10,000 or more data packets TX/RX. Thus 100 errors accumulated for 1,000,000 data packets is not unusual and well with acceptability. It is the technician’s discretion to determine when the error accrual rate impacts reliability and thus warrants corrective action.



(2) Access to the workstation under test is required.

d. Procedure. (1) From the top menu bar, select CONFIG. (2) On the CONFIGURATION window, click on the down arrow to the right of STATISTICS.

(3) On the STATISTICS window, observe the line that starts with NETWORK. This line has a box that

will indicate PNET, SNET, ENET, or RNET. Each of these settings is associated with subnets on the IDS-4 network, however; not every workstation will be connected to all three types. Refer to the Site Network Diagram to establish how many network types the workstation under test actually connects to. The statistics for each network type the workstation under test connects to will need to be checked separately.

(4) Starting with the first network type, usually PNET, SNET, or RNET, click the right or left arrows on

the network type. (5) Click the down arrow next to DIM. (When checking the ENT there will be no DIM statistics

available, thus skip to step 8.) (6) In the DIM xNET STATISTICS window observe the Total TX and RX indications. Verify that both

have counts that are increasing. The only thing to take note is that they are both increasing which indicates that network data is being received by the serial network card. If either the TX or RX counts are not increasing, then an error condition exists with the serial network card and corrective action must be taken. You may also observe that the TX and RX indications accrue at different rates, this is normal.

(7) While still in the DIM xNET STATISTICS window, observe the Pkt Size, Pkt Framing, and CRC

error indications. If any indications are present, they may simply be residual indications from prior network trouble issues, click the RESET button to clear the counts. Continue to observe the counters for at least one minute. If no additional errors are indicated, then the PORT operations are reasonably reliable. Click the CLOSE button to return to the previous window.

(8) Click the down arrow next to PORT. (9) In the COMx STATISTICS window observe the LSR Overrun, Parity, and Frame error indications.

If any indications are present, they may simply be residual indications from prior network trouble issues. If so, click the RESET button to clear the counts. Continue to observe for at least one minute. If no additional errors indicate, the DIM operations are reasonably reliable. Click the CLOSE button to return to the previous window.

10/27/2010 JO 6162.XX

Chap 5 5-5 Par 504

(10) Repeat steps 4 thru 9 for each network type until all the network types for the workstation under test have been checked.

(11) A workstation is not reliable if it is indicating unacceptable levels of persistent errors in any of the

checks in this procedure and thus should not be certified for operation.

505. External Data Interface – Clock.

a. Object. The purpose of this procedure is to verify accurate reception and dissemination configuration of time to the IDS-4.

b. Discussion.

(1) The Clock interface in IDS-4 is established at either a workstation, or an EDI cabinet, or an SIU to a facility time reference via an IRIG-B connection over coax cable.

(2) The Clock interface in IDS-4 has only the function of updating time on the EDI, SIU, or the

workstation hosting the interface. (3) Disseminating time updates to networked IDS-4 positions is the responsibility of the workstation

with the Time Source option enabled in its System Configuration. (4) Some IDS-4 networks operate without a physical connection to any facility time reference.

Regardless there will always be a workstation configured as the network Time Source. In those situations it becomes critical to verify the accuracy of the network Time Source workstation’s clock on a regular basis just as though a connection to facility time reference did exist.

(5) Time source interface or update failures at an EDI or SIU are indicated with reverse video in the

clock data fields. Clock interface failures at a workstation with a physical connection to the facility time reference will result in no alert indication.

(6) Workstation network Time Source configuration errors typically result in a red banner indication at

the bottoms of the workstations. c. Test Equipment Required.

(1) No test tools or equipment is required. (2) Access to a display of facility time reference. (3) Access to the workstation designated as the network Time Source.

d. Procedure. Implement only the following steps that apply to your system based on the equipment makeup of your system:

(1) For EDI cabinets, verify that the Time data fields on the Primary and Backup computers are within

tolerance as specified in Chapter 3. Verify the Time data fields are not in reverse video. (2) For SIU computers, verify that the Time data field is within tolerance as specified in Chapter 3.

Verify the Time data fields are not in reverse video.

10/27/2010 JO 6162.XX

Chap 5 5-6 Par 505

(3) For IDS-4 networks without an EDI/SIU, verify that the IDS-4 workstation hosting the Clock interface has display of time data within tolerance as specified in Chapter 3.

(4) For all networks, verify the workstation designated network Time Source has the Time Source option

enabled.

(a) From the top menu bar, select CONFIG.

(b) From the CONFIGURATION window select SYSTEM. Enter password, if prompted.

(c) In the SYSTEM CONFIGURATION window, observe the TIME SOURCE option on the left side, half way down. Verify that a check mark is present to indicate the option is selected. Click on the option if needed.

(d) Click OK to exit the SYSTEM CONFIGURATION window. Click CLOSE to exit the

CONFIGURATION window and return to the IDS-4 display.

(e) If a red banner indicating a Time Source error now appears then take corrective troubleshooting actions.

(5) No further check of Clock interface or time display on additional IDS-4 equipment is required.

(Checking the clock on individual workstations is presented as a separate check.) 506. External Data Interface – DASI.

a. Object. The purpose of this procedure is to verify accurate reception of DASI data from the DASI to the IDS-4.

b. Discussion.

(1) The DASI interface in IDS-4 is established at either a workstation, or an EDI cabinet, or an SIU. (2) The DASI interface in IDS-4 has only the function of disseminating DASI updates to networked IDS-4

positions. (3) Data received from the DASI STU must be formatted as two digits, followed by a colon, followed by

two more digits. (4) The DASI STU may either be a C&G or a DME model. (5) The DASI STU output is in FSK format. The IDS-4 interface to DASI will convert the FSK signal to

either RS232 or RS485 protocol with either an internal ISA PC card or an external converter module. (6) DASI interface or update failures at an EDI or SIU are indicated when the DASI data field is in reverse

video. (7) DASI interface or update failures at a workstation are also indicated with the DASI data field replaced

with “XXXXX”.


10/27/2010 JO 6162.XX

Chap 5 5-7 Par 506

(1) No test tools or equipment is required. (2) Access to a DASI display will be required.

d. Procedure. Implement only the following steps that apply to the system based on the equipment makeup

of the system: (1) For EDI cabinets, verify that the DASI data fields on the Primary and Backup computers are within

tolerance as specified in Chapter 3. Verify the DASI data fields are not in reverse video. (2) For SIU computers, verify that the DASI data field is within tolerance as specified in Chapter 3.

Verify the DASI data fields are not in reverse video. (3) For networks without an EDI/SIU verify that the workstation hosting the DASI interface has display

of DASI data within tolerance as specified in Chapter 3. (4) No further check of DASI data display on IDS-4 equipment is required.

507. External Data Interface – Ribbon Display Terminal (RDT) (ITWS, TDWR, LLWAS-NE++, WSP).

a. Object. The purpose of this procedure is to verify accurate reception of winds data received from the RDT to the IDS-4. The RDT may be referred to as the RBDT in some related documents.

b. Discussion. (1) The RDT interface in IDS-4 is established at either a workstation, or an EDI cabinet, or an SIU.

(2) The RDT interface in IDS-4 has only the function of disseminating RDT updates to networked IDS-

4 positions.

(3) In addition to display of runway winds, the data received from the RDT has the capability to visually alert on IDS-4 during WSA, MBA or when alert limits have been reached.

(4) The RDT source must be an RDT Display head.

(5) For networks without an EDI or SIU to interface to the RDT source, an LLWAS data pre-processor

is used. The LLWAS data pre-processor will then connect between the RDT Display Head and an IDS-4 workstation designated to host the LLWAS RDT interface.

(6) Loss of RDT interface or update failures at an EDI or SIU are indicated when the RDT data field is

in reverse video and blank.

(7) Loss of RDT interface or update failures at a workstation are also indicated when the RDT data field replaced with all X’s.



(2) Access to a RDT display.

10/27/2010 JO 6162.XX

Chap 5 5-8 Par 507

d. Procedure. Implement only the following steps that apply to your system and those based on the equipment makeup of your system:

(1) For EDI cabinets verify that the LLWAS data fields on the Primary and Backup computers are

within tolerance as specified in Chapter 3. Verify the LLWAS data fields are not in reverse video. (2) For SIU computers verify that the LLWAS data field is within tolerance as specified in Chapter 3.

Verify the LLWAS data fields are not in reverse video. (3) For networks without an EDI/SIU verify that the IDS-4 workstation hosting the LLWAS interface

has display of LLWAS data within tolerance as specified in Chapter 3. (4) No further check of LLWAS data display on IDS-4 equipment is required.

508. External Data Interface – LLWAS-2 or WME.

a. Object. The purpose of this procedure is to verify accurate reception of winds data from the LLWAS-2 or WME to the IDS-4.

b. Discussion.

(1) The LLWAS-2 systems, which are connected to IDS-4, no longer provide windshear alerts. These LLWAS-2 systems have been reconfigured with only a single sensor in the runway center field. LLWAS-2 systems which have been reconfigured are also commonly referred to as Wind Measuring Equipment (WME).

(2) The LLWAS-2 or WME interface in IDS-4 is established at either a workstation, or an EDI cabinet, or

an SIU. (3) The LLWAS-2 or WME interface in IDS-4 has only the function of disseminating LLWAS-2 or

WME updates to networked IDS-4 positions. (4) The data received from the LLWAS-2 or WME has only the capability to display the center field

winds and to visually alert on IDS-4 during gusting events. (5) The LLWAS-2 or WME source must be a 6-line tower display or a 1-line TRACON display head. (6) For networks without an EDI or SIU to interface to the LLWAS-2 or WME source, an LLWAS-2

data pre-processor is used. The LLWAS-2 data pre-processor will then connect between and LLWAS-2 or WME display dead and an IDS-4 workstation designated to host the LLWAS-2 or WME interface.

(7) LLWAS-2 or WME interface or update failures at an EDI or SIU are indicated when the LLWAS-2

or WME data field is in reverse video and blank. (8) LLWAS-2 or WME interface or update failures at a workstation are also indicated when the

LLWAS-2 or WME data field replaced with all X’s.


(1) No test tools or equipment is required. (2) Access to an LLWAS-2 or WME display head.

10/27/2010 JO 6162.XX

Chap 5 5-9 Par 508

d. Procedure. Implement only the following steps that apply to your system based on the equipment makeup

of your system: (1) For EDI cabinets, verify that the LLWAS-2 or WME data fields (shown as RDT) on the Primary

and Backup computers are within tolerance as specified in Chapter 3. Verify the LLWAS-2 or WME data fields are not in reverse video.

(2) For SIU computers, verify that the LLWAS-2 or WME data field (shown as RDT) is within

tolerance as specified in Chapter 3. Verify the LLWAS-2 or WME data fields are not in reverse video. (3) For networks without an EDI/SIU, verify that the IDS-4 workstation hosting the LLWAS-2 or

WME interface has display of LLWAS-2 or WME data within tolerance as specified in Chapter 3. (4) No further check of LLWAS-2 or WME data display on IDS-4 equipment is required.

509. External Data Interface – RVR.

a. Object. The purpose of this procedure is to verify accurate reception of runway data from the RVR to the IDS-4.

b. Discussion.

(1) The RVR interface in IDS-4 is established at either a workstation, or an EDI cabinet, or an SIU.

(2) The RVR interface in IDS-4 has only the function of disseminating RVR updates to networked IDS-4 positions.

(3) In addition to display runway visibility, the data received from the RVR has the capability to

visually alert when threshold values have been reached. (4) The RVR source may either be a Teledyne, Tasker 400, Tasker 500, or NG-RVR. (5) On IDS-4 networks without an EDI or SIU to interface to the RVR source, an RVR data pre-

processor may be used. If present, the RVR data pre-processor will then connect between the RVR and an IDS-4 workstation designated to host the RVR interface.

(6) RVR interface or update failures at an EDI or SIU are indicated with the RVR data field is in reverse

video and blank. (7) RVR interface or update failures at an IDS-4 workstation are also indicated with the RVR data field

replaced with all blanks.


(1) No test tools or equipment is required. (2) Access to an RVR display of the following appropriate source for the facility will be required:

Teledyne, Tasker 400, Tasker 500, or NG-RVR.

10/27/2010 JO 6162.XX

Chap 5 5-10 Par 509

d. Procedure. Implement only the following steps that apply to your system based on the equipment makeup of your system:

(1) For EDI cabinets, verify that the RVR data fields on the Primary and Backup computers are within

tolerance as specified in Chapter 3. Verify the RVR data fields are not in reverse video. (2) For SIU computers, verify that the RVR data field is within tolerance as specified in Chapter 3.

Verify the RVR data fields are not in reverse video. (3) For IDS-4 networks without an EDI/SIU, verify that the IDS-4 workstation hosting the RVR

interface has display of RVR data within tolerance as specified in Chapter 3. (4) No further check of RVR data display on IDS-4 equipment is required.

510. External Data Interface – AWIPS/AFOS.

a. Object. The purpose of this procedure is to verify accurate reception of METAR data from a verified/trusted AFOS to the IDS-4.

b. Discussion.

(1) The AFOS interface in IDS-4 is established at a designated IDS-4 workstation.

(2) The AFOS interface in IDS-4 has only the function of disseminating AFOS updates to networked IDS-4 positions.

(3) In addition to display of the weather text, the data received from the AFOS has the capability to

visually alert when updates are received. Individual data types may also be set to expire off the IDS-4 displays after a pre-determined amount of time.

(4) The AFOS source is the NWS AWIPS system. The connectivity to the AFOS is either established

by an IDS-4 workstation local to the NWS office or via a dedicated modem connection to the NWS office. (5) Although the AFOS interface is capable of up to 64 different product types from the NWS, presence

of any single product that is current and within tolerance as specified in Chapter 3, is sufficient to establish the interface is operational.

(6) AFOS interface or update failures at a workstation may be indicated with the AFOS data field

replaced with all X’s.


(1) No test tools or equipment is required. (2) Access to a display of verified/trusted AFOS. Sources to include AWIPS or NWS web site display

of current METAR data, local ASOS, or local AWSS.

d. Procedure.

10/27/2010 JO 6162.XX

Chap 5 5-11 Par 510

(1) Verify that the IDS-4 workstation hosting the AFOS interface has display of an AFOS data product within tolerance as specified in Chapter 3.

(2) No further check of AFOS data display on IDS-4 equipment is required.

511. External Data Interface – FDIO.

a. Object. The purpose of this procedure is to verify accurate reception of FDIO data from a verified FDIO.

b. Discussion.

(1) The FDIO interface in IDS-4 is established at a designated IDS-4 workstation. (2) The FDIO interface in IDS-4 has only the function of disseminating textural FDIO updates to

networked IDS-4 positions. Flight strip and other aircraft flow information are not supported on IDS-4. (3) Individual FDIO data types may be set to expire off the IDS-4 displays after a pre-determined

amount of time. (4) The FDIO source is the FDIO PCRU. The connectivity to the FDIO is established by an IDS-4

workstation local to the PCRU or via a dedicated serial connection. (5) Although the FDIO interface is capable of up to 64 different product types, presence of any single

product that is current and within tolerance as specified in Chapter 3, is sufficient to establish the interface is operational.

(6) FDIO interface or update failures at a workstation may also be indicated with the FDIO data field



(1) No test tools or equipment is required. (2) Access to a display of verified FDIO data.

d. Procedure.

(1) Verify that the IDS-4 workstation hosting the FDIO interface has display of an FDIO data product

within tolerance as specified in Chapter 3. (2) No further check of FDIO data display on IDS-4 equipment is required.

512. External Data Interface – AWSS.

a. Object. The purpose of this procedure is to verify accurate reception of weather data from the AWSS to the IDS-4.

b. Discussion.

(1) The AWSS interface in IDS-4 is established at either a workstation, or an EDI cabinet, or an SIU.

10/27/2010 JO 6162.XX

Chap 5 5-12 Par 512

(2) The AWSS interface in IDS-4 has only the function of disseminating AWSS VDU updates to networked IDS-4 positions. The AWSS OID function is not supported on IDS-4.

(3) In addition to display of the One-Minute screen VDU information, the data received from the AWSS

has the capability to visually alert when the published METAR or SPECI is updated. (4) The AWSS display source is the TDAU or any VDU connected to the TDAU. (5) On IDS-4 networks without an EDI or SIU to interface to the AWSS, an ASOS data pre-processor

will be used. The ASOS data pre-processor will connect between the AWSS and an IDS-4 workstation designated to host the AWSS interface.

(6) AWSS interface or update failures at an EDI or SIU are indicated when the AWSS data field is in

reverse video and blank. (7) AWSS interface or update failures at an IDS-4 workstation are indicated with the AWSS data field



(1) No test tools or equipment is required. (2) Access to the AWSS display from one of the following sources will be required: AWSS OID, VDU,

or TDAU maintenance console.

d. Procedure. Implement only the following steps that apply to the system based on the equipment makeup of the system:

(1) For EDI cabinets, verify that the AWSS data fields on the Primary and Backup computers are

within tolerance as specified in Chapter 3. Verify the AWSS data fields are not in reverse video.

(2) For SIU computers, verify that the AWSS data field is within tolerance as specified in Chapter 3. Verify the AWSS data fields are not in reverse video.

(3) For IDS-4 networks without an EDI/SIU, verify that the IDS-4 workstation hosting the AWSS

interface has display of AWSS data within tolerance as specified in Chapter 3.

(4) No further check of AWSS data display on IDS-4 equipment is required.

513. External Data Interface – ASOS.

a. Object. The purpose of this procedure is to verify accurate reception of weather data from the ASOS to the IDS-4.

b. Discussion.

(1) The ASOS interface in IDS-4 is established at either a workstation, or an EDI cabinet, or an SIU. (2) The ASOS interface in IDS-4 has only the function of disseminating ASOS VDU updates to

networked IDS-4 positions. The ASOS OID function is not supported on IDS-4.

10/27/2010 JO 6162.XX

Chap 5 5-13 Par 513

(3) In addition to display of the One-Minute screen VDU information, the data received from the ASOS has the capability to visually alert when the published METAR or SPECI is updated.

(4) The ASOS source is the ACU or any VDU connected to the ACU. (5) On IDS-4 networks without an EDI or SIU to interface to the ASOS source, an ASOS data pre-

processor will be used. The ASOS data pre-processor will connect between the ASOS and an IDS-4 workstation designated to host the ASOS interface.

(6) ASOS interface or update failures at an EDI or SIU are indicated with the ASOS data field is in

reverse video and blank. (7) ASOS interface or update failures at an IDS-4 workstation are also indicated with the ASOS data

field replaced with all X’s.


(1) No test tools or equipment is required. (2) Access to an ASOS display from one of the following sources will be required: ASOS OID or

VDU.

d. Procedure. Implement only the following steps that apply to the system based on the equipment makeup of the system:

(1) For EDI cabinets, verify that the ASOS data fields on the Primary and Backup computers are within

tolerance as specified in Chapter 3. Verify the ASOS data fields are not in reverse video. (2) For SIU computers, verify that the ASOS data field is within tolerance as specified in Chapter 3.

Verify the ASOS data fields are not in reverse video. (3) For IDS-4 networks without an EDI/SIU, verify that the IDS-4 workstation hosting the ASOS

interface has display of ASOS data within tolerance as specified in Chapter 3. (4) No further check of ASOS data display on IDS-4 equipment is required.

514. External Data Interface – WARP.

a. Object. The purpose of this procedure is to verify accurate reception of WARP data from WARP.

b. Discussion.

(1) The WARP interface in IDS-4 is established at a designated IDS-4 workstation. (2) The WARP interface in IDS-4 has only the function of disseminating WARP updates to networked

IDS-4 positions. (3) In addition to display of the WARP text, the data received from the WARP has the capability to


10/27/2010 JO 6162.XX

Chap 5 5-14 Par 514

(4) The WARP system is located at an ARTCC. The connectivity to the WARP is established by anIDS-4 workstation via a dedicated modem connection to the associated ARTCC.

(5) Although the WARP interface is capable of up to many different texts and graphical product types

from the WARP, presence of any single text product and any single graphic product type that is current and within tolerance as specified in Chapter 3, is sufficient to establish the interface is operational.

(6) WARP interface or update failures at a workstation may also be indicated with the WARP data field



(1) No test tools or equipment is required. (2) Access to the WARP display or known good WARP data for comparison.

d. Procedure.

(1) Verify that the IDS-4 workstation hosting the WARP interface has display of a WARP data product

within tolerance as specified in Chapter 3. (2) No further check of WARP data display on IDS-4 equipment is required.

515. External Data Interface – NOTAM.

a. Object. The purpose of this procedure is to verify accurate reception of NOTAM data from a verified/trusted NOTAM.

b. Discussion.

(1) The NOTAM interface in IDS-4 is established at a designated IDS-4 workstation. (2) The NOTAM interface in IDS-4 has only the function of disseminating NOTAM updates to

networked IDS-4 positions. (3) In addition to display of the NOTAM text, the data received from the NOTAM has the capability to


(4) The connectivity to the NOTAM system is established by an IDS-4 workstation via a dedicated modem

connection to the NOTAM office.

(5) Although the NOTAM interface is capable of up to 64 different product types from the NOTAM, presence of any single product that is current and within tolerance as specified in Chapter 3, is sufficient to establish the interface is operational.

(6) NOTAM interface or update failures at a workstation may also be indicated with the NOTAM data

field replaced with all X’s. c. Test Equipment Required.

10/27/2010 JO 6162.XX

Chap 5 5-15 Par 515

(1) No test tools or equipment is required. (2) Access to a display of verified/trusted AFOS or display of known good NOTAM data for

comparison.

d. Procedure. (1) Verify that the IDS-4 workstation hosting the NOTAM interface has display of an NOTAM data

product within tolerance as specified in Chapter 3. (2) No further check of NOTAM data display on IDS-4 equipment is required.

516.-599. Reserved.

10/27/2010 JO 6162.xx Appendix 1

1

Appendix 1. Certification Requirements

System and Subsystem Certification. System and subsystem certification is event based and relies on independent judgment about the quality and scope of specific advertised services being provided to a user. The purpose of certification is to make a determination about a system or subsystem to place it into or continue it in operation. Event based certification ties this determination to activities affecting the system or subsystem in a way that requires an individual’s assessment.

a. Event Based Certification. ATO personnel with certification authority must make a certification judgment for systems or subsystems when any of the following events occurs, unless exempted:

(1) Commissioning. You must perform the certification prior to placing the system or subsystem into operation for the first time.

(2) A post aircraft accident/incident request from the AFAAR. You must perform the certification prior to restoration.

(3) An adjustment to any certification parameter regardless of final value.

(4) Any scheduled or unscheduled full or reduced service interruption. You must perform the certification after any maintenance activity associated with the interruption, and prior to restoration.

(5) Any maintenance activity that required a reduced equipment interruption. You must perform the certification after the maintenance activity associated with the interruption, and prior to restoration.

(6) In addition to the statements made in previous paragraphs, the following IDS-4 related routine activities require certification of the associated workstation, interface, or IDS-4 system:

(a) Wherever a workstation is relocated from one operational position to a different operational position that is in the terminal environment.

(b) When a spare workstation is placed into operation in the terminal environment.

(c) Reload the system software at a workstation in the terminal environment.

(d) When some or all of the system software is version updated on a workstation in the

terminal environment.

(e) Replacement of a modem or other major component in a serial data interface feed.

10/27/2010 JO 6162.XX Appendix 1

2

(f) Restoration of system data from a backup if external data interface or data propagation abilities are impacted (such as a full database restoration to the entire network).

(g) While the EDI/SIU is not certified, any external data interface hosted by the EDI/SIU is

certified. Thus when an EDI/SIU is replaced, repaired, or if the EDI/SIU software is reloaded then the external data interfaces hosted by that EDI/SIU will need to be certified. This includes the standby roles of the backup or redundant equipment.

b. Activities that Exempt the Certification Requirement. System and subsystem certification is not required following an event if the only action(s) taken is:

(1) Restoration of systems or subsystems by an administrative action, e.g. closing an interruption with no work performed on the equipment.

(2) Restoration of primary or backup power. (3) Restoration of related facilities. (4) Restoration of Telco lines. (5) Restoration of FAA control/monitor lines or intermediate facilities. (6) Auto reset or initialization of systems or subsystems. (7) Manual reset or initialization of systems or subsystems via local or RMM. (8) Power OFF/power ON of systems or subsystems. (9) Changes to the local environment; e.g. HVAC restoration, snow/ice removal,

vegetation/wildlife control. (10) Testing of software. (11) Replacement of connected peripherals; e.g. keyboards, printers, etc. (12) Replacement of bulbs in lighted navigational aids as long as the adjusted parameter

was not out of tolerance or the system was not out of service. (13) RTS after personnel error made by other than Technical Operations personnel. (14) The following IDS-4 related routine activities are typical of those that do not require

certification of the associated workstation, EDI, SIU, or data interface to the IDS-4.

(a) Whenever a workstation is relocated from one operational position to a different operation position therefore the new location is not in the terminal environment.

(b) Performing hard drive defragmentation.

10/27/2010 JO 6162.xx Appendix 1

3

(c) Performing hard drive scandisk repairs.

(d) Performing database repairs for database corruption issues.

(e) After completing database synchronization.

(f) Installation or reconfiguration of a surge suppressor, data cable, or modem to restore

network communications.

(g) Installation of (spare) UPS or replacement of batteries.

(h) Installation or a replacement cooling fan or filter.

(i) Installation of a keyboard or trackball.

(j) Partial restoration of system data from a backup and only if external data interface or data propagation abilities are not impacted.

(15) Changes to the communication parameters associated with a data interface require certification. For example, if the com port or data rate for an RVR interface is changed, then certification is required. However, changes to the presentation/display attributes of received data products do not require certification. For example, text color, font size alert characteristics, etc., are examples of presentation/display attributes that do not require certification.

10/27/2010 JO 6162.XX Appendix 1

4

Appendix 1. Certification Requirements

Table 1. IDS-4

Advertised Service Certification Parameter Reference Paragraph Display Capability (IDS-4 displays used in an AT terminal environment or otherwise involved in aircraft takeoff/landing decision making process).

Workstation Clock Workstation Data Display Workstation Network Statistics

302a 302b 302c

Interface Capability (for each external data interface service at the facility where the interface is established into the IDS-4).

At the facility where the interface is established into the IDS-4, verify the IDS-4 display of external interface data from constituent systems is identical to the display of data on that constituent system.

302d (1) thru 302d (11)

CERTIFICATION BASED ON EVENTS: Events are defined in Order 6000.15 and are provided only as reference data in appendix 1, paragraph 1 of this order. ALLOWABLE EXCEPTION EXAMPLES: Specific Facility Types (DASI, RDT, LLWAS-2/WME, RVR, AWIPS/AFOS, FDIO, AWSS, ASOS, WARP, NOTAM). PERSON RESPONSIBLE FOR CERTIFICATION: ATSS or other (as assigned) with certification authority. CERTIFICATION ENTRIES IN FACILITY MAINTENANCE LOG:

Without Exception: IDS-4 certified

With Exception Example: IDS-4 certified with exception of (display or interface designation)

Removing Exception Example: IDS-4 (display or interface designation) certified

Documents

U.S. DEPARTMENT OF TRANSPORTATION …...NAS Safety Operational Risk to Air Traffic Control and Pilots – The Safety Risk Management Report is available at: TBD. 6. Recommendations