j'b -2 -- t, q3j'b / -- " -2 4 t, q3 % terminal doppler weather radar (tdwr) build 56...

$: j'b -2 -- t, Q3j'b / -- " -2 4 t, Q3 % Terminal Doppler Weather Radar (TDWR) Build 56 Q3 T&E) Integration 0 Radarne' Martinez R \ * R Atlantic City International A~rport, N.J. 08405$
j ' b /

-- 4 -2 " t, Q3 %

Terminal Doppler Weather Radar (TDWR) Build 56

Q3 T&E) Integration

% 0

Radarne' Martinez

R \

R * Atlantic City International A~rport, N.J. 08405

b Q3 4 e9 @

U S DepamentofTransp~tabon

DOTIFAA Federal AviationAdminimt~Uon

cT-TN94159 4A Techn~cal Center N9 Atlanbc C~ty A~rport. NJ08405

DOTlFAA Terminal doppler weather D CT-TM94159 radar (TDWR) build 58 / operational test and 4 evaluation (OT&E), C integration and OT&E

sponsorship e interest of 'mrnent !reof.

TECHNICAL CENTER

iorse Irers' :Onsidered

Twchnicol Roper? Documontation pop.

I. Report No.

DOT/FAA/CT-TN94/59 4. 11tI. ond Subrl?l. Terminal Doppler Weather Radar (TDWR) Build 5B Operational Test and Evaluation (OT&E) Integration and OT&E Operational Test Plan

I U. S. Department of Transportation I I

2 . Ge..rnn.n, Acc.sa,o. No. 3. R.cnpa.nt's Cotoloq No. 1 5. R.port Dot.

March 1995 6. P.v{ormonq O~qe.,z.t,~~ Cede

'. A"h""'Radame' Martinez , ACW-200; Steven Viveiros , SAIC; Donne Wedge, SAIC; Peter Guthlein, DI

9. P.rfermtnq Orqmtratnon Nom. m d ~ddr...

U.S. Department of Transportation Federal Aviation Administration FAA Technical Center Atlantic City International Airport, NJ 08405

I . Spon~er~nq Aq.ney N.n. end Addr-sl

8. P.rlormanq O,qongxorlon Regerr N o .

DOT/FAA/CT-TN94/59

10. Work Unor no. ITRAIS)

I I. Controct or G ~ ~ ~ , NO.

13. TIP. of Repert end P..,o~ cor...d

The Terminal Doppler Weather Radar (TDWR) Build 5B Enhancement Operational Test and Evaluation (OT&E) Integration and OT&E Operational Test Plan provides the overall philosophy and approach to Build 5B OT&E testing, and identifies OT&E objectives, responsibilities, and resources.

Federal- Aviation ~dministration FAA Technical Center Atlantic City International Airport, NJ 08405

The TDWR Build 5B Enhancement provides connectivity to the Low Level Wind Shear Alert System (LLWAS) I11 to display LLWAS I11 data along with TDWR hazardous weather data on TDWR Geographic Situation Displays (GSD) and Ribbon Display Terminals (RDT).

14. s ~ ~ . ~ ~ ~ ~ ~ A~.~.~ cod.

The TDWR Build 5B OT&E is scheduled to occur at the TDWR sites in Denver, CO, November and December 1994, and in Orlando, FL, spring 1995.

I . Su..l.m.n,..* Not..

17. Key We.4~

Terminal Doppler Weather Radar (TDWR) Build 5B Operational Test and Evaluation (OT&E) Low Level Wind Shear Alert System

18. D i s t r i b h ~ S e e - n t

Document is on file at the Technical Center Library, Atlantic City International Airport, NJ 08405

I Unclassified

Form DOT F 1700.7 (8-72) R . ~ n & c t l m of cwmplwtd p y w w h r i x d

Unclassified 6 0

TABLE OF CONTENTS

Executive Summary . . . . . . . . . . . . . . . . . . . . . . v

1 . INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 Background . . . . . . . . . . . . . . . . . . . . . . 1 1.2 Testphilosophy . . . . . . . . . . . . . . . . . . . . 2 1.3 Purpose of Test Plan . . . . . . . . . . . . . . . . . 6 1.4 Scope of Test Plan . . . . . . . . . . . . . . . . . . 6 1.5 Document Overview/Organization . . . . . . . . . . . . 6

2 . DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.1 Referenced Documents . . . . . . . . . . . . . . . . . 7 2.2 Background Documents . . . . . . . . . . . . . . . . . 7

3 . SYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . 9 3.1 SystemOverview . . . . . . . . . . . . . . . . . . . . 9 3.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . 12

4 . TEST PROGRAM DESCRIPTION . . . . . . . . . . . . . . . . . . 17 4.1 Approachandconcept . . . . . . . . . . . . . . . . 17 4.2 TestEnvironment . . . . . . . . . . . . . . . . . 18 4.3 OT&E Integration Test Descriptions . . . . . . . . . 20 4.4 OT&E Operational Test Descriptions . . . . . . . . . 22

5 . TESTMANAGEMENT . . . . . . . . . . . . . . . . . . . . . . 25 5.1 Roles and Responsibilities . . . . . . . . . . . . . . 25 5.2 Training . . . . . . . . . . . . . . . . . . . . . . . 28 5.3 Test Conduct . . . . . . . . . . . . . . . . . . . . . 28 5.4 TestReports . . . . . . . . . . . . . . . . . . . . . 29 5.5 Schedules and Personnel Requirements . . . . . . . . . 31

6 . ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . 34 APPENDIX

A . Test Verification Requirements Traceability Matrix B . Test Schedule

iii

LIST OF ILLUSTRATIONS

Figure

1.2-1

3.1.2-1

3.2-1

3.2.1-1

3.2.2-1

3.2.3-1

3.2.4-1

4.1.2-1

FAA OT&E Test Philosophy

HWCI/CSCI Diagram

TDWR External Interfaces

TDWR--LLWAS I1 Interface

TDWR--LLWAS I11 Interface

TDWR--MPS and TDWR--MDT Interfaces

TDWR--TCCC Interface

TDWR Build 5B OT&E Flow

LIST OF TABLES

Table

5.5.2-1 TDWR OT&E Integration and OT&E Operational Test Support Personnel

Page

3

10

12

13

14

15

16

19

Page

33

EXECUTIVE SUMMARY

This document presents the Terminal Doppler Weather Radar (TDWR) Build 5B Operational Test and Evaluation (OT&E) Operational and OT&E Integration Test Plan. This test plan is written in accordance with FAA-STD-024a and FAA Order 1810.48, and provides the overall philosophy and approach to TDWR Build 5B OT&E testing. Plus, this test plan identifies OT&E objectives, responsibilities, and resources.

TDWR Build 5B further enhances Build 5A by adding an interface to the Low Level Wind Shear Alert System Phase I11 (LLWAS 111) to display LLWAS I1 and/or LLWAS I11 wind products along with TDWR hazardous weather data on TDWR Geographical Situation Displays (GSD) and Ribbon Display Terminals (RDT). Other Build 5B enhancements include:

1. TDWR/LLWAS I11 Integration Algorithm,

2. Microburst Shear Integration Algorithm (MSIA),

3. 15-day archiving and archive data playback,

4. Microburst Detection Algorithm (MDA) parameter changes,

5. Programmable alarm timeouts,

6. Enhanced Base Data Display (BDD) capabilities, and

7 . Upgraded operating systems (0s) for the Harris (Harris OS 6.1) and SUN work stations (SunOS 4.1.3~1).

TDWR Build 5B OT&E is scheduled to occur at the TDWR site in Denver, CO, from August to September 1994. Additional OT&E will be conducted in Orlando, FL, during spring 1995 to thoroughly evaluate the effectiveness of the MDA parameter changes, MSIA, and TDWR/LLWAS I11 Integration Algorithm. After successful completion of Build 5B OT&E, the Build 58 enhancements will be installed at an LLWAS I1 site to verify that Build 5A functionality has not been degraded.

1. INTRODUCTION.

The Terminal Doppler Weather Radar (TDWR) is one project of the National Airspace System (NAS) Plan, whose overall goal is the modernization and improvement of the government systems supporting aviation commerce in the United States. In the end-state of the NAS Plan, the TDWR will send weather product information to air traffic control (ATC) computers at the Tower Control Computer Complex (TCCC). Also, in the end-state, a mechanism will be provided to transmit TDWR hazardous weather information directly to pilots. The end-users of TDWR outputs are local, approach, and departure controllers, their supervisors, and pilots. In the interim NAS, the TDWR product information will be displayed to air traffic specialists; i.e., controllers and controllers' supervisors.

The Build 5 enhancement is intended to enable the TDWR to further meet the goals of the NAS Plan. This will be accomplished by interfacing the TDWR to the Low Level Wind Shear Alert System (LLWAS) and by improving existing TDWR functionality.

The Build 5 enhancement for the TDWR is being implemented in two stages: Build 5A and Build 5B. Build 5B includes all Build 5A enhancements plus several other enhancements, identified in section 1.1. This test plan addresses only that functionality included in Build 5B. In addition, this test plan has been tailored to address only those Operational Test and Evaluation (OT&E) Integration, OT&E Operational, and NAS-SS-1000 requirements not previously verified during baseline and Build 5A OT&E. However, some of the aforementioned requirements will be reverified to ensure baseline performance has not been degraded by the Build 5B enhancements.

OT&E Integration and OT&E Operational testing has been completed on the baseline TDWR system, as well as the Build 5A enhancement. All NAS-SS-1000 requirements successfully verified during previous OT&E will be identified as such in the Test Verification Requirements Traceability Matrix (TVRTM) included in appendix A. Some of these requirements will be verified again to ensure that the baseline system performance has not been degraded.

1.1 BACKGROUND.

Build 5B will provide an interface to the LLWAS Phase I1 (LLWAS 11) and Phase I11 (LLWAS 111). LLWAS I1 consists of six sensors and a computer system to process wind information. LLWAS I11 consists of up to 29 sensors and a computer system to process wind information. Build 5B will accept LLWAS I1 or LLWAS I11 Center Field Wind (CFW) and runway threshold winds and display them on the TDWR Display Functional Unit (DFU) which is composed of a Geographical Situation Display (GSD) and up to eight Ribbon Display Terminals (RDT). Other Build 5B functionalities include:

a. TDWR/LLWAS I11 Integration Algorithm;

b. Microburst Shear Integration Algorithm (MSIA);

c. 15-Day archiving and archive data playback;

d. Microburst Detection ~lgorithm (MDA) parameter changes;

1. Minimum divergence segments of 4, 2. Minimum alarm segments of 5, 3. Minimum alarm delta v of 10 m/s, 4. Minimum storm top altitude of 1.5 km, 5. Minimum storm cell area of 2 mi2, 6. Storm overlap test (dry cell), 7. Storm centroid distance of 3 km;

e. Programmable alarm timeouts;

f. Enhanced Base Data Display (BDD) capabilities;

g. Upgraded operating systems (0s) for the Harris (Harris OS 6.1) and SUN work stations (SunOS 4.1.3~1).

1.2 TEST PHILOSOPHY.

The Federal Aviation Administration (FAA) conducts OT&E in accordance with FAA Order 1810.4B to evaluate the subsystem operational effectiveness and suitability including compatibility, interoperability, degraded operations, survivability, maintainability, and supportability. OT&E also identifies deficiencies in NAS hardware, software, human performance factors, and/or operational concepts. OT&E consists of three phases: Integration, Operational, and Shakedown. Only OT&E Integration and OT&E Operational phases will be addressed in this test plan. OT&E Shakedown activities will be addressed in the AOS-230 TDWR Build 5B OT&E Shakedown Test Plan. Division of responsibilities for FAA OT&E Integration and OT&E Operational testing are illustrated in figure 1.2-1. Since Build 5B is an enhancement to the TDWR baseline system, only those blocks not shadowed will be evaluated.

1.2.1 OT&E Integration.

OT&E Integration consists of testing NAS System End-to-End performance, specifically, NAS-SS-1000, volume I system level and volumes I1 through V subsystem level requirements as identified in the TDWR Test and Evaluation Master Plan (TEMP) Verification Requirements Traceability Matrix (VRTM). This testing establishes NAS baseline performance (end-to-end) or verifies that previously existing NAS performance has not been degraded. To the greatest extent possible the subsystem will test in a NAS system equivalent environment.

OT&E Integration will be conducted at the Denver, CO, TDWR site (DVX) will address and evaluate the readiness of the system for integration and transition into the field. In addition, this activity will evaluate the system performance in critical test areas, test the limits of system performance, and provide operational performance benchmarks.

The OT&E Integration effort is conducted with the following objectives:

a. Verify the TDWR's capability to properly interface and function with the associated NAS subsystems, including hardware, software, operational, and maintenance activities;

b. Ensure the detection of interface design problems;

c. Minimize site problems by comprehensive integration testing and evaluation;

d. Verify the requirements of the NAS System Specification.

1.2.2 OT&E ODerational Testinq.

OT&E Operational testing is to verify the operational effectiveness and suitability of the equipment with user's participation. Aspects of this testing are as follows:

a. Reliability and availability;

b. Degraded operations and operational utilization scenarios;

c. Stress and NAS loading testing of all interoperable subsystems;

d. Human factors;

f. Weather Detection Performance.

OT&E Operational testing employs system users to assess operational suitability and effectiveness of the subsystem in the NAS environment. Testing will be conducted at DVX in accordance with established OT&E requirements. This testing will evaluate system functions, data entry and display devices, Human Engineering, Computer-Human Interface, training, training documentation for ATC operations, systems maintenance, and support operations. Test will be structured in a building block fashion starting with an evaluation of basic functions and operations, and progressing to evaluations during complex integrated operations.

The OT&E Operational test objectives are:

a. Verification and validation of the operational requirements;

b. Evaluation and determination of the effect of the segment under test on the operational mission;

c. Identification and evaluation of the safety factors involved during transition and determination that transition can be achieved safely;

d. Evaluation of the subsystem's operations and maintenance with respect to the variations in site configuration and adaptation;

e. Assessment of the subsystem's capability to support current and future modifications.

1.2.2.1 Reliability and Availability.

OT&E will be conducted to verify that Build 5B does not degrade diagnostics accuracy, Mean Time Between Failure (MTBF), and Mean Time Between Critical Failure (MTBCF).

1.2.2.2 Deqraded Operations.

This test is conducted to determine the acceptability of the resultant operational degradation when failures are induced in the system. This includes validation of shutdown procedures, startup procedures, degraded operations procedures, and operational impact of the data preservation function upon recovery.

1.2.2.3 Stress and NAS Loadinq.

This test estimates the levels of stress and NAS loading provided by the operational environment.

1.2.2.4 Human Factors.

This test estimates the degree of accommodation to which the interaction of personnel with the system in the operational environment is needed. Test and evaluation (T&E) should explore such factors as the physical interaction of personnel with a system, interactions with procedures, workloads, and operational environments.

1.2.2.5 Site Adaptation.

This test ensures that site data unique to each applicable NAS facility has been correctly developed, updated, and installed in the system.

1.3 PURPOSE OF TEST PLAN.

The purpose of this plan is to ensure that comprehensive OT&E Integration and OT&E Operational testing is conducted. This plan describes the test program, identifies organizational responsibilities, and provides a basis for the development of OT&E Integration and OT&E Operational test procedures.

1.4 SCOPE OF TEST PLAN.

This plan provides for comprehensive testing of the Build 5B enhancement to the current TDWR system to ensure it satisfies user and NAS requirements. It describes the OT&E Integration and OT&E Operational test processes for ensuring this enhancement meets applicable subsystem/system requirements allocated in NAS-SS-1000, volumes I, 111, and V.

This paragraph describes each section of the test plan.

Section 1: Introduction. This section provides an introduction to the TDWR Build 5B OT&E Integration and OT&E Operational Test Plan. In addition, it provides the purpose and scope of the test plan.

Section 2: Documents. All documents directly referenced in the plan and all other documents related to this plan are listed in this section.

Section 3: System Description. This section provides a brief system overview including a block diagram. It also identifies the current and future interfaces.

Section 4: Test Program Description. This section describes the OT&E approach and concept, test environment, and test descriptions.

Section 5: Test Management. This section defines the roles and responsibilities, training, test conduct, test reports, schedules, and personnel resource requirements.

Section 6: Acronyms and Abbreviations. All acronyms and abbreviations used throughout this document will be listed in this section.

Appendix A: This appendix is a detailed TVRTM.

Appendix B: A detailed Build 5B Test Schedule is presented in this appendix.

2. DOCUMENTS.

This section lists the documentation and reference materials which relate to the contents of this plan.

2.1 REFERENCED DOCUMENTS.

FAA-E-2806/1 TDWR Specification, November 12, 1992, with Specification Change Notice (SCN) 1, January 2, 1993.

NAS-SS-1000 NAS System Specification, Volume I, Functional and Performance Requirements for the National Airspace System General, October 1992.

NAS-SS-1000 NAS System Specification, Volume 111, Functional and Performance Requirements for the Ground-to-Air Element, February 1993.

NAS-SS-1000 NAS System Specification, Volume V, Functional and Performance Requirements for the National Airspace System Maintenance and Operations Support Element, October 1992.

NAS-IR-31023105 LLWAS Phase I1 to TDWR Interface Requirements Part 2, Rev. A Document (IRD) . NAS-IR-31023105 LLWAS Phase I11 to TDWR IRD, December 7, 1993 Part 1, Rev. C

NAS-IC-31055103-00 TDWR Remote Monitoring Subsystem (RMS)/Maintenance Processor Subsystem (MPS) Interface Control Document (ICD) .

NAS-IC-31055104-00 TDWR/Maintenance Data Terminal (MDT) ICD.

NAS-IC-31052201-00 TDWR/Tower Control Computer Complex (TCCC) ICD.

FAA-STD-024a Preparation of Test and Evaluation Documentation, August 17, 1987.

No. 1810.4B FAA NAS Test and Evaluation Policy, October 22, 1992.

2.2 BACKGROUND DOCUMENTS.

TDWR TEMP TDWR Build 5 Enhancement Test and Evaluation Master Plan (TEMP), November 1993.

NAS-MD-110 Test and Evaluation (T&E) Terms and Definitions for the NAS, March 27, 1987.

NAS-MD-790 Remote Maintenance Monitoring System Interface Control Document Maintenance Processor Subsystem to Remote Monitoring Subsystem Concentrators, June 10. 1986.

NAS-MD-793 Remote Maintenance Monitoring System Functional Requirements for the Remote Monitoring Subsystem (RMS), June 10, 1986.

D001-Bld5-2 TDWR Contractor's Master Test Plan (CMTP) ~uild 5 Addendum, January 12, 1993.

B022-Bld5-1A Build 5 Software Requirements Specification Radar Product Generation (RPG) Software, CSCI-2 CGG551591, Revision A, November 19, 1992.

B022-Bld5-2B Build 5 Software Requirements Specification RMS software, CSCI-3 CGG551592, Revision B, June 30, 1993.

B022-Bld5-3B Build 5 Software Requirements Specification Display Computer (DPL) Software, CSCI-4 CGG551594, Revision B, June 24, 1993.

3. SYSTEM DESCRIPTION.

The primary goal of the TDWR is to enhance the safety of air travel through the timely detection and reporting of hazardous wind shear in and near the terminal approach and departure zones of an airport. Specific sources of hazardous wind shear to be detected are microbursts and gust fronts. The secondary goal of the TDWR is to improve the management of air traffic in the terminal area through the forecast of gust front induced wind shifts at the airport, as well as detection of precipitation.

3.1 SYSTEM OVERVIEW.

3.1.1 Eauipment Description.

The TDWR can be functionally divided into three subsystems: Radar Data Acquisition (RDA), Radar Product Generation/Remote Monitoring Subsystem (RPG/RMS) , and the DFU.

The RDA function performs the radar data collection, detection, signal processing, clutter suppression, control monitoring, and error detection subfunctions for the TDWR system. The RDA consists of the Antenna Group (ANT) which includes the Radome, Pedestal Assembly, Tower Assembly, Reflector Assembly, Servo Control Unit (SCU), and Moving Target Simulator (MTS). The RDA also includes the microwave pallet and redundant Transmitters (XMT), Receiver/Exciters (REX), and Digital Signal Processors (DSP) . The RPG/RMS functions process moment/dwell data from the RDA, exchange control and status signals with the RDA, transmit data to the DFU, and provide the interfaces to LLWAS II/III, RMMS/MDT, and TCCC.

The DFU equipment consists of a GSD for viewing weather products, and from zero to eight alphanumeric RDT for viewing alert messages. GSD capabilities also include range scale selection, recentering of displayed products, selection of runway configuration, and archiving of weather products.

3.1.2 EuUi~ment Architecture.

The TDWR system is configured into Hardware Configuration Items (HWCI) and Computer Software Configuration Items (CSCI). A TDWR HWCI and CSCI block diagram is included in figure 3.1.2-1.

The software consists of operational and nonoperational software. Operational software consists of operating systems (which are Commercial-Off-the-shelf (COTS) products), application software Computer Software Configuration Item(s) (CSCI), and firmware CSCIs. The commercial operating systems are VRTX-32 Operating System (CSCI-7) for the 68020 single board computers, the Data Processing Operating System (CSCI-10) for the RPG/RMS, and the Display System Operating System (CSCI-11) for the DFU. Nonoperational software which is not part of TDWR site installations consists of the Software Development Tools (CSCI -5) and the Test Tools Library (CSCI - 6) . The HWCIs consist of the following:

Antenna Group (ANT) HWCI-1 Transmitter (XMT) HWCI - 2 Receiver-Exciter (REX) HWCI-3 Digital Signal Processor (DSP) HWCI -4 Radar Product Generator/Remote Monitoring Subsystem (RPG/RMS) HWCI - 5 Display Functional Unit (DFU) HWCI-6 Special Test Equipment (SPT) HWCI-7 Program Support Facility (PSF) HWCI-8

The CSCIs consist of the following:

A. Operational Software

1. Application Software

a. Digital Signal Processor (DSP) CSCI-1 b. Radar Product Generator (RPG) CSCI-2 c. Remote Monitoring Subsystem (FNS) CSCI-3 d. Display Computer (DPL) CSCI-4 e. Antenna Control (ANT) CSCI-8 (Firmware) f. Transmitter Control (XMT) CSCI-9 (Firmware)

2. Operating Systems

a. VRTX-32 Operating System (VTX) CSCI-7 b. Data Processing Operating System (DPO) CSCI-10 c. Display System Operating System (UNIX-UNX) CSCI-11

B. Nonoperational Software

1. Software Development Tools (SDT) CSCI-5 2. Test Tools Library (TTL) CSCI-6

3.2 INTERFACES.

Build 5B will provide external interfaces to LLWAS II/III, Remote Maintenance Monitoring Subsystem (RMMS), Maintenance Data Terminal (MDT), and Tower Computer Control Complex (TCCC). These interfaces are shown in figure 3.2-1.

i I

Display Rmtimd Unit Towar Sibmtim and R i m 'IRACON Siluaticm uul

1 - i Displays k i n Displays i

i j i !

FIGURE 3.2-1. TDWR EXTERNAL INTERFACES

12

3.2.1 LLWAS 11.

The TDWR to LLWAS I1 communications interface will consist of a primary and backup interface, and is described in NAS-IR-31023105, Part 2, Revision A. The primary interface will connect the TDWR RPG to the LLWAS Tower Display port on the LLWAS processor. The backup interface will connect the TDWR Tower GSD to the LLWAS Spare port on the LLWAS processor. In the event of a primary interface failure, the switch-over from primary to backup will occur automatically. Both interfaces will operate at 1200 bits per second (bps). Figure 3.2.1-1 presents the TDWR--LLWAS I1 interface. Note: TE stands for transmission equipment.

FIGURE 3.2.1 -1. TDWR--LLWAS II INTERFACE

3.2.2 LLWAS 111.

The TDWR to LLWAS I11 communications interface will consist of a primary and backup interface, and is described in NAS-IR-31023105, Part 1, Revision C. The primary interface will connect the TDWR RPG to the LLWAS processor. The backup interface will connect the TDWR Tower GSD to the LLWAS processor. In the event of a TDWR failure, the switchover from primary to backup will occur after active runways are configured using the LLWAS keypad. The GSD operator will then acknowledge the switchover to the backup link via a GSD menu indicating that TDWR is nonoperational. Both interfaces will operate at 9600 bps. Figure 3.2.2-1 presents the TDWR--LLWAS I11 interface. Note: TE stands for transmission equipment.

I 1 TDWR

FIGURE 3.2.2-1. TDWR--LLWAS Ill INTERFACE

3.2.3 Remote Maintenance Monitorina Subsystem (RMMS).

The TDWR RPG/RMS provides the following interfaces:

a. RMMS: The RMMS utilizes the Maintenance Processor Subsystem (MPS) to remotely control and monitor the TDWR. This interface is described in NAS-MD-790 and NAS-MD-793.

b. MDT: The MDT is located at the TDWR site in the Concrete Masonry Unit (CMU) and is used to locally control and monitor the TDWR. This interface can operate at 1200, 2400, 4800, and 9600 bps.

These interfaces are presented in figure 3.2.3-1. Note: TE stands for transmission equipment.

FIGURE 3.2.3-1. TDWR - MPS AND TDWR - MDT INTERFACES

-'-!

MDT MI'S 4 b I T

4

R / I M i I S

I I

MDT 4 )

3.2.4 Tower Control Computer Complex (TCCC).

The TDWR interfaces to TCCC which provides for transmission of products, equipment status, TDWR modes, and receipt of commands. When the TCCC becomes available, it will provide data to appropriate ATC facilities. It operates at 9600 bps and is described in NAS-IR- 22013105, Revision E. This interface is presented in figure 3.2.4-1.

FIGURE 3.2.4-1. TDWR - TCCC INTERFACE

4. TEST PROGRAM DESCRIPTION.

4.1 APPROACH AND CONCEPT.

In order to determine the operability of the TDWR Build 5B enhancement with the NAS environment, OT&E Integration and OT&E Operational testing requires that the TDWR be installed in an operational environment with operational support. An operational environment refers to the configuration into which the TDWR must be integrated. For this reason, both live and/or simulated interfacing subsystems and equipment will be used. Air Traffic (AT) and Airways Facilities (AF) field site personnel will also be requested to participate in test efforts. These test efforts will include providing support in writing and executing the detailed test procedures that will be generated by ACW-200 to verify the requirements identified for testing. TDWR OT&E Integration and OT&E Operational testing will be performed using all interfaces available and appropriate to the TDWR system.

4.1.1 Operational Issues/Test Requirements Summary.

The following are issues related to the Build 5B enhancement:

a. LLWAS I11 wind information is accurately displayed on the GSDs and RDTs.

b. The MDA parameter changes increase the Probability of Detection (POD) and reduce the False Alarm Ratio (FAR).

c. The MSIA reduces overwarnings due to TDWR-generated microburst alerts.

d. The TDWR/LLWAS 111 ~ntegration Algorithm generates more accurate Microburst Alerts (MBA) and Wind Shear Alerts (WSA) than either stand-alone system.

e. TDWR--LLWAS I11 link status is reported accurately to the MPS and MDT.

f. The performance of baseline Build 5A has not been degraded using Build 5B enhancements.

g. Archiving, programmable alarm timeouts, and enhanced base data display capabilities have been included in CSCI-4 Software Userst Manual.

All NAS-SS-1000 requirements related to TDWR have been included in the TVRTM in appendix A. The specific Build 5B requirements which will be tested during Build 5B OT&E are identified. Previously verified NAS requirements, which will not be fully tested during Build 5B OT&E, are also identified.

4.1.2 Preliminam Activities Leadins to Testing.

Prior to OT&E Integration and OT&E Operational testing, ACW-200 shall prepare the Build 5B OT&E Integration and OT&E Operational test procedures. In addition, the Build 5B enhancement will have successfully undergone extensive Development Test and Evaluation (DT&E). This testing is conducted by the prime contractor and witnessed by the FAA. Finally, the prime contractor will install the Build 5B enhancement and successfully complete the Build 5B Interface Test at the TDWR site in Denver. The OT&E Integration and OT&E Operational test flow diagram is provided in figure 4.1.2-1.

4.1.3 Planninq Considerations and Limitations.

Build 5B OT&E test conduct is contingent upon the completion of the LLWAS I11 to TDWR software being developed by LORAL. In addition, the testing of the TDWR--MPS interface described in paragraph 4.3.2.1 will be contingent upon the availability of the appropriate software.

4.2 TEST ENVIRONMENT.

The following paragraphs will describe the test facilities where the OT&E testing described in this plan will be conducted.

4.2.1 Test Location.

The Build 5B enhancement OT&E Integration and OT&E Operational testing will be conducted at Denver. Weather data will be collected at both Denver and Orlando sites.

4.2.2 Test Confiquration.

The DVX TDWR is a typical site installation including all HWCIs (except HWCI-8) and all CSCIs (except CSCI-5 and CSCI-6) identified in paragraph 3.1.2. The CSCIs that were modified for Build 5B include CSCIs-2, 3, and 4. The only hardware addition for Build 5B is the portable archive data recorder (ADR) which connects to the DFU, (HWCI-6).

The TDWR Special Test Equipment (HWCI-7), Base Data Recorder (BDR) and BDD, will be utilized to record and playback TDWR base data.

4.2.3 Environmental Conditions.

A lack of convective weather during the scheduled test period could impact the validity of the weather performance test results. Should favorable test weather not occur, testing may have to be extended or moved to another site.

4.2.4 Test Analysis and Tools.

The TDWR Special Test Equipment will be used to record and playback data. More detailed information regarding test equipment may be found the TDWR Test Procedures.

4.2.5 Pass/Fail Criteria.

Pass/Fail criteria for each test will be included in the TDWR Test Procedures.

4.3 OT&E INTEGRATION TEST DESCRIPTIONS.

4.3.1 TDWR--LLWAS I11 Interface Test.

4.3.1.1 Test Objectives.

This test will verify that LLWAS I11 Center Field Wind (CFW), threshold winds, and Microburst/Wind Shear Alerts are accurately displayed on the TDWR GSDs and RDTs.

The following TVRTM requirements will be verified under this test:

4.3.1.2 Test A~proach.

This test will utilize the LLWAS I11 playback function to play back a known LLWAS I11 weather scenario. The TDWR GSDs and RDTs will be monitored to verify the LLWAS I11 data was properly displayed. This test will performed for both primary (LLWAS I11 to RPG) and backup (LLWAS I11 to GSD) links.

4.3.2 TDWR--RMS/MPS Interface Test.


The objective of this test is to verify that the TDWR--MPS and the TDWR--MDT interfaces exist and are functional. ACN-loOD, with assistance from ACW-200~, will conduct Build 5 OT&E Integration to verify NAS-SS-1000, Volume V requirements for the TDWR--MPS and TDWR--MDT interfaces after the baseline Interim Monitor and Control Software (IMCS) module has been completed and tested. The Build 5B modifications to the TDWR--MDT interface will be verified during OT&E Operational testing.

TVRTM requirement 3054 will be verified under this test

4.3.2.2 Test Approach.

The system MDT will be used to control and monitor TDWR throughout Build 5B OT&E Integration and OT&E Operational testing. During OT&E Operational Degraded Operations scenarios, the LLWAS--RPG and LLWAS--DFU communications performance parameters will be verified using the system MDT.

4.3.3 TDWR--TCCC Interface Test.

The TDWR--TCCC interface was tested during Build 5B DT&E using a TCCC simulator. This test verified that TDWR transmitted graphic and alphanumeric products to the TCCC simulator. ACN-300, with assistance from ACW-200D, will perform OT&E Integration when the TCCC becomes available.

4.4 OT&E OPERATIONAL TEST DESCRIPTIONS.

4.4.1 System Reliability/Availability Test.


System operation will be monitored to verify that diagnostic accuracy, MTBF, and MTBCF are achievable in an operational environment. This data will be used to support the data collected during baseline OT&E Operational testing, as well as verify that the Build 5B enhancement has not degraded TDWR system reliability/availability.


During Build 5B OThE test conduct, all TDWR system failures will be recorded and classified as critical or noncritical. For system reliability tests, the TDWR will be run in a "hands-off" mode and it will be verified that any failures of interrelated NAS subsystems do not affect TDWR reliability. Diagnostics will be performed in event of a failure and all diagnostic results will be recorded. In the event of critical failure, system downtime will also be recorded.

4.4.2 Deqraded O~erations Test.


This test is conducted to determine the acceptability of the resultant operational degradation when failures are induced into the NAS system. Operational scenarios will be used to verify TDWR response to TDWR-- LLWAS I11 failure modes.


This test will verify that the TDWR responds properly during the following scenarios:

a. TDWR and LLWAS I11 operational,

b. TDWR operational and LLWAS I11 nonoperational,

c. TDWR nonoperational and LLWAS I11 operational, and

d. TDWR and LLWAS I11 nonoperational.

4.4.3 Stress and NAS Loadinq Test.


This test will demonstrate the TDWR response to stress and NAS loading provided by a weather scenario test tape operational environment.


This test will stress the TDWR by utilizing all available interfaces during periods of hazardous weather activity. This test will involve playback of a weather scenario test tape with runways mapped to all lines of all RDTs. The LLWAS switchover override option will also be enabled to more closely simulate a live operational environment. In the event significant hazardous weather activity occurs during the test period, this test will be conducted using a live operational environment.

4.4.4 Human Factors Evaluation.


This test estimates the degree to which the interaction of personnel with the system in the operational environment is accommodated. OT&E will explore such factors as the physical interaction of personnel with the TDWR. In particular, the following will be evaluated:

a. The archive data recording and playback procedures;

b. The programmable alarm timeouts;

c. The switch over to the LLWAS--TDWR backup link procedures;

d. The RDT response upon failure of the GSD;

e. The changes to the display of graphics and alphanumerics due to the MSIA and TDWR--LLWAS I11 Integration Algorithm.

TVRTM requirement 3055 will be verified during this test.


ACW-200D will monitor and observe tower and Terminal Radar Approach Control (TRACON) controllers and supervisors while using the LLWAS III/TDWR data. A questionnaire will be used to evaluate Build 5B function useability.

4.4.5 Site-Ada~tation Verification.


This test ensures that site data unique to each applicable NAS facility has been correctly developed, updated, and installed in the system.


Site parameters will be selected at random and compared against the Site Survey Reports. If necessary, site set-up utilities will be used

to verify these parameters. AOS-230 will assist in the generation of detailed test procedures, and will assist in test conduct.

4.4.6 Weather Performance Evaluation.


The objective of this test is to verify the TDWR meets operational suitability and reliability requirements in relation to its ability to detect hazardous weather.

The following TVRTM requirements will be verified under this test:


A meteorologist from the National Severe Storms Laboratory (NSSL) will conduct a weather performance evaluation. In particular, the performance of the MDA parameter changes, MSIA, and TDWR--LLWAS I11 Integration Algorithm will be evaluated.

4.4.7 TDWR--LLWAS I1 Verification.


This test will ensure that the introduction of the Build 5B enhancement does not degrade LLWAS I1 performance.


The Build 5B enhancements will be installed at an LLWAS I1 site. Then, it will be verified that LLWAS I1 CFW and runway mapped sensor winds are accurately displayed on the TDWR GSDs and RDTs.

5. TEST MANAGEMENT.

5.1 ROLES AND RESPONSIBILITIES.

The following paragraphs shall describe the various organizations and personnel that will manage, conduct, and support the testing.

5.1.1 Test Manaqement Orqanization.

5.1.1.1 Proqram Manaqer, ANR-500.

The Program Manager (PM) is responsible for management of the program. In particular, the PM has responsibilities for the OT&E Integration and OT&E Operational test effort as described in FAA Order 1810.4B. Specifically, the PM:

a. Manages the overall T&E program;

b. Arranges with the Associate Program Manager for Test (APMT) for T&E support, coordination, and monitoring;

c. Reviews and approves OT&E Integration and OT&E Operational test requirements, plans, procedures, and reports;

d. Monitors OT&E Integration and OT&E Operational Tests.

5.1.1.2 Technical Officer, ANR-900.

The Technical Officer is responsible for the technical direction of the TDWR program. Specific responsibilities include:

a. System Design;

b. Design Qualification Test and Evaluation;

c. Air Traffic Controllers Build 5B Enhancement Training;

d. Implementation;

e. Maintenance and Logistics Support.

5.1.1.3 APMT, ACW-200.

The APMT is responsible for management of the OT&E Integration and OT&E Operational test effort. In particular, the APMT has responsibilities for the OThE Integration and OT&E Operational test effort as described in FAA Order 1810.4B. Specifically, the APMT:

a. Supports the development of test policy and test standards;

b. Acts as an agent of the PM to manage the T&E program. This includes establishing test schedules, coordination of tests,

ensuring that all test requirements are satisfied, and that tests are performed in accordance with approved procedures;

c. Coordinates with performing organizations and monitors OT&E activities;

d. Prepares OT&E Integration and OT&E Operational test requirements;

e. Prepares OT&E Integration and OT&E Operational test plans, procedures, and reports;

f. Directs and conducts OT&E Integration and OT&E Operational tests.

5.1.2 Other Participatinq Orqanizations.

5.1.2.1 Operation Support Service, AOS-230.

This organization identifies and develops OT&E Shakedown requirements. In addition, they are responsible for conducting OT&E Shakedown testing. They provide assistance and support during the OT&E Integration and OT&E Operational test effort by reviewing the OT&E Integration and OT&E Operational Test Plan, Test Procedures, and Test Reports. They also monitor OT&E Integration and OT&E Operational tests and optionally participate in OT&E Integration and OT&E Operational test conduct.

5.1.2.2 Air Traffic Plans and Reauirements Service, ATR-120.

This organization provides operational expertise and planning for conducting and analyzing tests. They provide assistance and support during the OT&E Integration and OT&E Operational test effort by reviewing the OT&E Integration and OT&E Operational Test Plan and Test Procedures. They also provide personnel for conducting and/or monitoring OT&E Integration and OT&E Operational tests.

5.1.2.3 Reqional Airway Facilities Division, AF.

This organization supports the APMT in the development of OT&E test requirements. In addition, they provide coordination support for test activities.

5.1.2.4 Office of Independent Operational Test and Evaluation Oversiqht, ATQ-1.

This organization performs an IOT&E oversight mission which includes: (1) independent assessment of system operational effectiveness and suitability; (2) verification that systems are satisfactorily tested and evaluated in a realistic operational environment; and (3) verification that technical and operational risks have been

sufficiently mitigated to warrant production, deployment, or commissioning.

5.1.2.5 Maintenance Automation Proqram Office, ANA-700.

This organization is responsible for providing the IMCS and conducting confidence testing.

5.1.2.6 Enqineerinq, Test, and Evaluation Service, ACN-100.

This organization provides assistance and support during the OT&E Integration and OT&E Operational test effort by preparing and executing the RMS/MPS test procedures. They will then provide ACW-200 with a test report for inclusion into the OT&E Integration and OT&E Operational Test Report.

5.1.2.7 National Severe Storms Laboratory, NSSL.

This organization provides meteorological assistance and support during the OT&E Integration and OT&E Operational test effort by verifying TDWR base data and weather products. They will then provide ACW-200 with a test report for inclusion into the OT&E Integration and OT&E Operational Test Report.

5.1.3 Test Conduct Team.

5.1.3.1 Test Director, ACW-200.

The Test Director is appointed by the APMT. Specifically, the Test Director:

1. Ensures the OT&E Integration and OT&E Operational test effort follows the specific test plan and procedures:

2. Ensures all required equipment and personnel are available prior to the start of the test;

3. Ensures all relevant data for analysis is collected;

4. Maintains a daily test log;

5. Conducts pretest and post-test briefings;

6. Provides the status of all testing activities to the APMT.

5.1.3.2 Test Manaqer.

A Test Manager is not needed for the TDWR OT&E Integration and OT&E Operational testing.

5.1.3.3 Test Operators, ACW-200, AOS-230, ACN-100, AT, AF, NSSL.

Test Operators are responsible for manning the test positions during a particular test. They follow the test procedures and record all test results. In addition, they will assist the Test Director in maintaining the daily test log. The Test Operators report to the Test Director.

5.1.3.4 Test Monitors, ACW-200, ANR-900, AOS-230, ATR-120.

Test Monitors are responsible for ensuring that the test scenarios and procedures are being followed by the Test Operators. Test Monitors assist the Test Operators by reporting observations, assisting in the recording of measurements, and keeping track of day-to-day activities by maintaining test logs.

5.1.3.5 ATQ-1 Representative.

ATQ personnel perform the IOT&E oversight mission for this test in accordance with paragraph 5.1.2.4 of this document.

5.2 TRAINING.

The following paragraphs will describe the training needed to develop and execute the OT&E Integration and Operational test procedures.

5.2.1 Test Developer Traininq.

No formal TDWR training is required for test procedure development and execution. However, a thorough understanding of TDWR system operation including the use of the System MDT, RPG/RMS MDT, BDD, BDR, GSDs, and RDTs is required.

5.2.2 Test Participant Traininq.

Test participants should also be familiar with overall TDWR system operations including the MDTs, BDR, and all displays.

5.3 TEST CONDUCT.

5.3.1 Quality Control and Confiquration Manaqement.

ANR-900 will officially provide software. Version Numbers/Checksums will be provided before the start of testing.

5.3.2 Test Readiness Criteria.

ACW-200D will conduct Build 5B OT&E Integration and OT&E Operational tests after contractor on-site Design Qualification Tests (DQT) are completed and a configuration audit is performed.

5.4 TEST REPORTS.

The following subsections define the necessary reports that will be generated during OT&E Integration and OT&E Operational testing.

5.4.1 Individual Test Results Reporting.

Individual test results will be recorded by Test Operators in the spaces provided in each test procedure. At the conclusion of each test, a summary of the test results will be included in the test procedure.

5.4 - 2 Service Reports (SR) . The Test Director will ensure all test discrepancies and problems observed during testing are documented in SRs. The SRs will be forwarded to the Program Office for resolution. The SR format will be the same as in previous TDWR OT&E testing.

5.4.3 Periodic Test Status Reports/Briefinqs.

This paragraph identifies the type of briefings that will be conducted throughout OT&E Integration and OT&E Operational testing.

5.4.3.1 Pretest Briefinqs.

This briefing, chaired by the Test Director, will be scheduled immediately prior to the start of each test and attended by all personnel participating in the test. The pretest briefing will include the status of prerequisites, software, system equipment, test equipment, and a test summary.

The pretest briefing consists of a brief explanation of the type of test that will be conducted, what the test will attempt to accomplish, and the hardware/software configuration that will be utilized for the test. The pretest briefing will also accomplish the following:

a. Identify any needed changes, and red-line the procedures accordingly;

b. Review the hardware and software configurations of the test environment;

c. Ensure that all.items in the material check list (contained in the test procedures) have been received;

d. Provide Service Report forms to attendees;

e. Generate a record of the pretest briefing.

5.4.3.2 Post-test Briefinq.

This briefing will be conducted after test completion. It is chaired by the Test Director and attended by all test personnel. The purpose of the meeting is to review the results of the test activity. An assessment of the quality of the test and the impact of the problems (i.e., SRs) will be discussed during the review of the Test Director's post-test briefing package.

The post-test briefing package, prepared by the test director prior to the post-test brief, should consist of the following:

a. The "as-run" hardware and software configuration, how it differed from that stated in the procedures, and its significance to the test results;

b. Any deviations, planned and unplanned, in the test procedure steps and their significance to the test results. Procedure steps with problems noted and/or SRs initiated against them should be rescheduled for retest;

c. Any discrepancies, anomalies, and exceptions that were recorded during the test and their significance to the test results;

d. A summary of the outcome of the test. This summary can be derived by reviewing the test logs, test data, and SRs that were generated.

5.4.3.3 Status Telecons.

These status telecons will serve to keep the TDWR Test Support Group abreast of the status of OT&E Integration and OT&E Operational testing. These weekly telecons will be chaired by ACW-200 and will serve as a technical interchange of issues and concerns.

5.4.4 Ouick Look ReDort.

A Quick Look report will be written within 15 working days after test completion. This report will include a description of the test, a summary of test activities, significant test results that are known at the time, and test result conclusions. It will provide an immediate indication of the outcome of the test and highlight test discrepancies noted during test execution and their significance.

The Quick Look Test Report will contain the following:

a. Quick Look Test Report title page;

b. Executive Summary;

c. Introduction;

d. OT&E Description;

e. Results;

5.4.5 Final Report.

The TDWR Test Director will be responsible for preparing a Final Test report within 60 days after all OT&E testing is complete. The Final Test Report will document the results of detailed test analysis, and assess the compliance of each test to defined criteria. The status of problems identified previously in the Quick Look Test Reports will be updated, and a revised assessment will be made of their impact on the tested system, and the suggested corrective actions required. Any new problems discovered by detailed evaluation will be identified and their impact in the system described.

The Final Test Report will contain the following:

a. Final Test Report title page;

b. Executive Summary;

c. Table of Contents;

d. Introduction;

e. Documents referenced;

f. System Description;

g. Test Description;

h. Results and Discussion;

i . Conclusions ;

j. Recommendations;

k. Acronyms and Abbreviations.

5.5 SCHEDULES AND PERSONNEL REQUIREMENTS.

This section includes the overall schedule of TDWR Build 5B OT&E events and personnel requirements for OT&E Integration and OT&E Operational testing.

5.5.1 Test Schedule.

This section presents the schedules for TDWR OT&E Integration and OT&E Operational activities. TDWR OT&E activities are traceable and supportive of the TDWR TEMP.

This schedule indicates the TDWR OT&E Test Activity as shown in appendix B. The schedule is developed, released, and controlled by the Test Director, ACW-200. The function of this schedule is to provide guidance for all TDWR activities. They identify the major tasks to be accomplished (e-g., Test Plan and Test Procedures complete) and identify task start and stop dates. This schedule enables the Test Director to provide detailed test status to the test groups.

5.5.2 Personnel Resource Reauirements.

The personnel requirements for OT&E Integration and OT&E Operational test conduct are included in table 5.5.2-1.

TABLE 5.5.2-1 TDWR OT&E INTEGRATION and OT&E OPERATIONAL TEST SUPPORT PERSONNEL

ORGANIZATION ACW-200D ACW-200D AF Field Personnel AOS-230 ATR-120 ACN-100 ATQ-1 NSSL ANR-goo

NO. OF PEOPLE POSITION 1 Test Director

Test Monitor/Operator Test Operator Test Monitor/Operator Test Monitor/Operator Test operator Test Witness Test Monitor Test Witness

Note: Not all of these organizations will be present during every test. The test procedures will identify appropriate personnel.

6. ACRONYMS AND ABBREVIATIONS.

A ACN

ACW ADR AF ANR ANT APMT AOS AT ATC ATR ATQ

Analysis Engineering, Test, and Evaluation Service, FAA Technical Center Weather and Primary Radar Division, FAA Technical Center Archive Data Recorder Airways Facilities Program Director for Weather Radar Antenna Associate Program Manager For Test Systems Maintenance Service, FAA Aeronautical Center Air Traffic Air Traffic Control Air Traffic Plans and Requirements Service Office of Independent Operational Test and Evaluation Oversight

BDD Base Data Display BDR Base Data Recorder bps Bits per second

CFW Center Field Wind CMTP Contractor's Master Test Plan CMU Concrete Masonry Unit COTS Commercial-Off-the-shelf CSCI Computer Software Configuration Item

D DFU DPL DPO DQT DSP DT&E DVX

Demonstration Display Functional Unit Display Computer Software Data Processing Operating System Design Qualification Test Digital Signal Processor Development Test and Evaluation Terminal Doppler Weather Radar site in Denver, CO

FAA Federal Aviation Administration FAAAC Federal Aviation Administration Aeronautical Center FAR False Alarm Ratio

GSD Geographical Situation Display

HWCI Hardware Configuration Item

I Inspection ICD Interface Control Document IMCS Interim Monitor and Control Software IRD Interface Requirements Document

LLWAS Low Level Wind Shear Alert System

MB A MDA MDT M&OS MPS MSIA MTBF MTBCF MT S

NAS NSSL

0s OT&E

PM POD PSF

RDA RDT REX RMMS RMS RPG

SCN scu SDT SF0 S PB S PT SR

T TCCC TDWR T&E TE TEMP TRACON TTL TVRTM

UNIX-UNX

VRTM VTX

WSA

Microburst Alerts Microburst Detection Algorithm Maintenance Data Terminal Maintenance and Operations Support Maintenance Processor Subsystem Microburst Shear Integration Algorithm Mean Time Between Failure Mean Time Between Critical Failure Moving Target Simulator

National Airspace System National Severe Storms Laboratory

Operating System Operational Test and Evaluation

Program Manager Probability of Detection Program Support Facility

Radar Data Acquisition Ribbon Display Terminal Receiver/Exciter Remote Maintenance Monitoring System Remote Monitoring Subsystem Radar Product Generator

Specification Change Notice Servo Control Unit Software Development Tools Sector Field Office Site Program Bulletin Special Test Equipment Service Report

Test Tower Control Computer Complex Terminal Doppler Weather Radar Test and Evaluation Transmission Equipment Test and Evaluation Master Plan Terminal Radar Approach Control Facility Test Tools Library Test Verification Requirements Traceability Matrix

Display System Operating System

Verification Requirements Traceability Matrix VRTX-32 Operating System

Wind Shear Alert

Terminal Doppler Weather Radar

NAS-SS-1000 Volume I Test Verification Requirements Traceability Matrix

Reqt .

NAS-SS-1000

Description/Title

Verification Level/Method

Remarks

ID#

OTKE

OT6E

3.2.1.1.1.1.1

Air traffic control functional

x I

Build 5A and 5B

characteristics

- Disseminate weather data

3.2.1.1.4.1.B

Weather functional characteristics .

x x

Verified during 1992 m

6~

Collect/sense weather information

3.2.1.1.4.1.0

Weather functional characteristics -

Display

X

T

Build 5A and 58

weather information

3.2.1.1.4.1.6


x

T

Build 5A and 5B

Classify weather information

1005

3.2.1.1.4.1.H

Weather functional characteristics

- Alert

x T

Build 5A and 58

specialists of hazardous weather

1006

3.2.1.1.4.1.1


X

T

Build 5A and 5B

Disseminate weather information

1007

3.2.1.1.4.1.K


x T

Build 5.4 and 58

Generate weather products

1008

3.2.1.1.4.1.N

Weather functional characteristics

- Archive

x T

Build 58

weather information

Data and voice archiving

I x

T

Build 5B

1010

3.2.1.2.4.A.l

Weather performance characteristics -

Detect

x x

Verified during 1992 TFTKE

surface weather conditions aloft

1011

3.2.1.2.4.A.2.B

Weather performance characteristics -

x x

Verified during 1992 TFT6E

Terminal

Verification Methods: T=Test.

D=Demonstration. A=Analysis. I=Inspection, x=Not Applicable

C 0 N C

W

N

CCCCC 00000 ~rrrr Owm4h

WWWWW

NNNNN

r CCrCC C C r C

N NNNNN N N N N VI

m ~PPPP P L P * V)

* '"T?? h, C ? !' " 0

0 m PUN N C P C 0

n r. naaaa ,- a a a a m a ::EGG E E E E $ g 5 5 5 g aaa a a g a !? a g g' b7 "7

mm; : : "7 L" m m

C w

r w E rn

w w N N ::

C 0 c "7

W

N

z 2 m

z 2 m

C 0 c P

W

N

r 0 r W

W

N

0 '+ c N

W

N

?3 H m 019 P"


NAS-SS-1000 Volume I11 Test Verification Requirements Traceability Matrix

Reqt .

NAS-SS-1000

Description/Title


Remarks

ID#

OTSE

I OTSE

3001

3.2.1.2.5.1.1

Functional characteristics

- Receive

T

x

weather products from LLWAS

3002

3.2.1.2.5.1.2.A

Identify weather phenomena

- Microburst

x I

3003

3.2.1.2.5.1.2.B


- Gust front

x I

3004

3.2.1.2.5.1.2.C


- Precipitation

x

I

3005

3.2.1.2.5.1.2.D


- Storm motion

x x

3006

3.2.1.2.5.1.3.A

Measure weather phenomena

- Reflectivity

x x

3007

3.2.1.2.5.1.3.B


- Mean radial

x I

X

velocity

3008

3.2.1.2.5.1.3.C


- Spect-

width

x x

3009

3.2.1.2.5.1.4.A

Weather data processing

- Type of weather

x

I

3010

3.2.1.2.5.1.4.0


- Location of

x I

weather

3011

1 3.2.1.2.5.1.4.C


- Velocity of

I weather

Ix

I1

Build 5A and 5B

I

Build 5A and 58

Storm motion unavailable

Build 5A and 58

Build 5A and 58

1 3012

1 3.2.1.2.5.1.4.D

1 Weather data processing

- Severity of

1 x

I I

I Build 5A and 5B

3013

3.2.1.2.5.1.4.E


- Direction of

x x


storm motion

3014

3.2.1.2.5.1.5.A


- Microburst map

x I

Build 5A and 5B

3015

3.2.1.2.5.1.5.B


- Microburst

x T

Build 5A and 5B

message/alarm

3016

3.2.1.2.5.1.5.C


- Gust front map

x I

Build 5A and 58

3017

3.2.1.2.5.1.5.0


- Gust front

x T

Build 5A and 5B

messaqe/alarm

3018

3.2.1.2.5.1.5.E

Generate weather products . Precipitation

x I

Build 5A and 58

3019

3.2.1.2.5.1.5.F


- Storm motion

x x


map

lerification Methods: T=Test. D=Demonstration, A=Analysis, I=Inspection, x=Not ApplicaDle

Reqt . r;


NAS-SS-1000 Volume I11 Test Verification Requirements Traceability Matrix

NA

S-S

S-1

00

0

DescriptionlTitle

3.2.1.2.5.2.1

Performance characteristics

- Detection


NAS-SS-1000 volume 111 Test Verification Requirements Traceability Matrix

P

VI

Ln Ln 0 0

"7 "7 m 0 0

"7 Ln 0 0 0 0 w

"7

0 0 0 0 0 0 0 0 H m m 4 m rn * W N +. 0 19

* "

W W W W W W W W

N N N N N N N N

C C C C C C C C

C C C C C C C C m

C C C C C C C C m C C C C C C C C C

0 C C C C C C C C 0

0

1; W

: N C

w r C +.

m a w

am YVO nre mv 5 .I m $ :: 2 t-$n-n,r.

E oow 5 .mow F-o orom EV&2E

mw rmm w.w.am P.W rr Byg2m g$262gw 8?12" E P.m. "":;- ""0

E P 6 *or WOmz . nwm mm mano arnoo~ a 5 vronoqa IJ vmwmw*. 0-7 PYU

36;; SF rtmm NVOV Pm qb?

mm~ ~~rng?~~

wommr .03v tT v "5 ovna '1.3 Pv $z~u~ '"*'"

,&q&v ? !-;mw 3 P E Kzma am-" Sww:'5L?n -.m$62 0 m w.5 5 g . ""0 , n 0 vv. U)

" C P r- 0 rr Y "" IJ

" v. 0 Y -. z " v m

""

rn Y +. : a

Y ; " rj rj .3 e rj 4 e

" P 8 2 m

X X X X X X X 20 c 5: P g " w r a

0 CI D w D D 0 0 m n, m m 0

m m

m '1 m r(

v v ., v '1 m M i! '1

E E E a a a D m

a m a

6 6 0" 0" S 6 S 6

C C C 0 0 0

C C 0 0

C 0

C +. 0 0 0 0 0 0

0 0 0 F

0 R ::

"7 0 C "7

W

N

C

C

r C

N

C m

*" ~iag, P.O 803 "" rrrmr.r mr,m P. m r- 3DI om

mr.0) 3 - $ '" rr: "we,

8 2 rw om,,. cm wr- rr"m3z ;?"m; mmww .- .. "'LamX rmvl c

0 rrw ev:, wmm C 'I v ar

Z8,..Z .3~ o 3 Y w-nm

m r p:.mt

$5

H

X

0 m !2 'I m a

S

g C 0 0

rn 0 C P

W

N

C

C

C

C

N

C a

$Kg3 ;;zm

zv;g E$sm wmw mvnT

4- a YP) """" $'ISL? r-mmo zg;; .m.;

"1-8 m F .. r-m w

z r.~ P.OM

Po" 6 4

w "X r 0 0%

4

X

0 m !2 w m a

S

K ? C 0 0

"7 0 C W

W

N

C

C

C

C

N

C o

6P3 m

zgg Egm mw

4 mp

3 : -.om 2;: + , w g

28~: mc ..at

~5 0

a ms "X

zs

4

X

0

m m w 'I m a

;

g C 0 0

"7 0 C N

W

N

C

C

C

C

N

F

EP7S m

:gig *. w SZ~O

"2S& o m w

v m

wmrr 3;: mv

no 2"- mow 4

;; g rn w Z$$ 8%-

zm

e

X

0

E M *I m a

0 Tt

z ? C 0 0

"7 0 C C

W

N

C

C

C

C

N

r LSF5.?4&2$5.GS 3v0rrvmaumrtmm

v.c rKz.z 2 rv ~:'I2m"3mrncm?i w mr-rnmmuvm

rr~ 4 r.3 OQrwQu~nrr~m

m r-v s r.m o , " m.,,, gS& 25yn6aQFZ8L WC* 04 m "r.0 o grg3mmvz on mwQD

o ~(rmrw~rrrmu g r.uimrmvw

avo mrem 'IQ ul m m oB1 cmrnmcarr wmm mvua rrm

8Fa -3mz;zsg om# eavgZwmrom

o

cmmrrr vmrrc wa; gm gg $gg;

Eg";~9%%j.ma m r.3 ;,m3w. L-QEgS -4 r.mr -

OP i5 E: " '$0

m

4

X

0

m m 'I 'I m a

S

z ? C 0 0

"7 0 C 0

W

N

C

C

C

C

C

P w

81: 3 :i2 rrm yl

UI

:& 'I:

ft wo m

mu 'I"

8s m>

3 & rn

ZE aQ 0)m

m o 'I

H

X

0

K v m a

0 "

z ? C 0 0

0 "7

0 m

W

N

C

C

C

C

C

P w

L$1!?$? ::?go is:- r.g rr rrnom mnmo, aOm~L"Y1

v a"r.r.p g%rn?:L

go$;gg q C+.W.V mo r-o 3 m or~s~o 9&"ae9 8:;:sw om,-tw.t- mag ;C

;g,gas 9 m zag L r.3 o r. m v rn vsu o $$wgEZ. mwrsmo 2-t-r-03 ",DO3 m SQ a "5." !

4

x

0 m m m H m a

;

g C 0 0

0 H m 0 63 V rr

5 0)

0) 0)

C 0 0 0

o : 0 'I

G (r

5 --. 2 " v m

Y

$2 :[.1 r.

" 6' : $2 rrn 2

e

2 Z

m rr

P

2 E 2 m

2 a

z R ::


P

m

Reqt .

ID#

5016

5017

5018

5019

5020

NA

S-S

S-1

00

0 Volume V Test Verification Requirements Traceability Matrix

NAS-SS-1000

3.2.1.1.1.1.2.1f

3.2.1.1.1.1.2.1g

3.2.1.1.1.1.2.111

3.2.1.1.1.1.2.1i

3.2.1.1.1.1.2.13

Verification Methods: T=Test, D=Demonstration, A=Analysis, I=Inspection, x=Not Applicable

Description/Title

The RMS shall monitor and check each and

every key perEormance parameter value for an

alarm or an alert condition at least once

during each general status cycle. A general

status cycle consists of collecting and

evaluating all data necessary to determine

the health of the system and reporting the

results (i.e., alarms, alerts, or system

okay1

to the RMS/MPS interface or the

RMS/MDT interface or both as required by the

communications mode in effect.

The time

period in which the general status cycle

must be completed shall be programmable from

five (51 seconds to sixty (60) seconds in

increments of five (51 seconds or less;

The RMS shall monitor and check each and

every key performance parameter value,

detect any changes in value, and report the

changed values to the RMS/MPS interface or

the RMS/MDT interface or both as required by

the communications mode in effect. The time

period in which the general status cycle

must be completed shall be programmable from

ten 110) seconds to two (2) minutes in

increments of

ten (101 seconds or less;

The RMS shall generate a general status

message and a key performance parameter

message at times which depend on the

individual cycle time defined above;

Th

eR

MS

sha

llg

en

er

ate

ar

etu

rn

-to

-no

rm

al

message when a parameter causing an alarm or

alert condition returns to its ideal

operating range;

The RMS shall determine if a monitored data

point, status, or condition has changed

between the sampling o

f parameter values and

generate a state change message if the state

has changed;

Remarks

Deferred to ACN-100

Deferred to ACN-100

Deferred to ACN-100

Deferred to ACN-100

Deferred to ACN-100

Verification

OT&E

Integration

T

T

T

T

T

Level/Method

OThE

Operational

x

x

x

x x


NAS-SS-1000 Volume V Test Verification Requirements Traceability Matrix

Reqt .

NAS-SS-1000

Description/Title


Remarks

ID#

OTb

rE

OTSE

Integration

merational

5021

3.2.1.1.1.1.2.1k

An

RM

Ss

ha

llin

itia

tea

dia

gn

os

tic

tes

tofa

T

x Deferred to ACN-100

subsystem, which includes fault isolation,

in response to the appropriate comand from

an MPS or an MOT;

5022

3.2.1.1.1.1.2.11

Th

eR

MS

sh

all

init

iate

afa

ult

re

co

ve

ry

T


routine if an alarm or alert is generated.

5023

3.2.1.1.1.1.2.2e

The RMS shall provide for the disabling of

T


automatic loq off of an MOT by an authorized

Operator;

5024

3.2.1.1.1.1.2.2f

The RMS shall generate an access denied

T


message to be sent to the MPS and to the

originating device when an invalid user

identification code or passvord is collected

or when an unauthorized function is

attempted;

5025

3.2.1.1.1.1.2.2g

When an MOT is connected to or disconnected

T

x

Deferred to ACN-100

from an RMS, the RMS shall generate a state

change message for transmission to the MPS;

5026

3.2.1.1.1.1.2.2h The RMS shall allow comunications with an

T

X

Deferred to ACN-100

MDT via an external link only if processed

through an MPS, including MOT'S connected to

a separate RMS.

5027

3.2.1.1.1.1.2.3a

won receipt of a valid command from either

T

X

Deferred to ACN-100

the MPS or MDT, the RMS shall execute the

control command;

5028

3.2.1.1.1.1.2.3b

Upon receipt of a valid consnand from either

T


an MDT or an MPS, the RMS shall change the

current operating mode or configuration of a

subsystem to the operating mode or

configuration requested;

x' w

Verification Methods: T=Teet. D=Demonstration, A=Analysis. I=Inspection, x=Not Applicable


NAS-sS-1000 volume v Test Verification Requirements Traceability Matrix

Reqt .

NAS-SS-1000

Description/Title


Remarks

ID#

OT6E

OT6E

Integration

Operational

5029

3.2.1.1.1.1.2.3~ Upon receipt of a valid comand from either

T


an MDT or an MPS, the RMS shall adjust the

subsystem parameter as requested;

5030

3.2.1.1.1.1.2.3d Upon receipt of a valid command from either

T


an MDT or an MPS, the RMS shall reset a

subsytem or part of a subsystem:

5031

3.2.1.1.1.1.2.3e

Uponreceiptofavalidcommandfromeither

T


an MDT or an MPS, the RMS shall disable an

alarm or alert indication;

5032

3.2.1.1.1.1.2.3f

Uponreceiptofavalidcommandfromeither

T


an MDT or an UPS, the RMS shall change the

requested threshold values of the parameters

being monitored;

5033

3.2.1.1.1.1.2.3g

Upon receipt of a valid command from an

T


onsite MDT, the RMS of single thread

equipments shall switch from remote

communication with the MPS to a local

communication mode with the MDT, providing

exclusive control of the subsystem from the

MDT;

5034

3.2.1.1.1.1.2.3h

Upon receipt of a valid command from an

T


onsite MDT, the RMS of multithread

(redundant) equipments shall provide

communication and exclusive control without

interruption of off-line units to the MDT

monitoring of

on-line equipments;

5035

3.2.1.1.1.1.2.3i

Upon disconnect of

an onsite MDT, the RMS

T


shall automatically return to the remote

communication mode with the MPS;

x' v 0

Verification Methods: T=Test. D=Demonstration, A=Analysis, I=Inspection, x=Not Applicable

Terminal Doppler weather Radar


Reqt .

NAS-SS-1000

ID#

5036

3.2.1.1.1.1.2.4f

The RMS shall provide a date in the form of

I I

I I

T

Deferred to Act-100

month/day/year and universal time code (UTC)

in the form of hours/minutes/seconds on each

Dercription/Title


Remarks

5037

5038

5039

Verific

3.2.1.1.1.1.2.4b

3.2.1.1.1.1.2.4~

3.2.1.1.1.1.2.4d

3.2.1.1.1.1.2.4e

The RMS shall compare filtered key

performance parameter values with the two

sets of threshold values as part of each

General Status Cycle to determine if an

alarm or alert condition has occurred. One

set o

f threshold values is for alarm

condition determination while the other set

of thresholds is for alert condition

3.2.1.1.1.1.2.4g

determination.

The RMS shall generate a report containing

performance parameter values in response to

a data request;

The RMS *hall generate a status report

containing alann and alert condition in

response to a subsystem status request;

The RMS shall generate a maintenance data

message containing information requested by

either an MDT or an MPS;

3.2.1.1.1.1.2.4h

OTLE

Integration

T

The RMS shall accept commands and requests

from the HDT;

The RMS shall generate the appropriate

3.2.1.1.1.1.2.4i

3.2.1.1.1.1.2.4j

3.2.1.1.1.1.2.4k

T

T T

GT

LE

Operational

x

T

I

:ion Methods: T=Test, D=Demonstration, A=AnalYsin. I=Inspection, x=Not Applicable

The RMS shall make available all command

responses to the MPS or the MDT or both

depending upon the nature of the request;

The RMS shall prepare all messages for

transmission in the appropriate protocol;

The RMS shall convert sensor input

information into values directly related to

engineering units such that no scaling other

than decimal placement shall be required of

the receiving MPS or MDT;

Deferred to ACN-100

x x x

T

response to all commands;

Deferred to Act-100

Deferred to Act-100

Deferred to ACN-100

x

T

T T

Deferred to Act-100

I

x Deferred to Act-100

X x x

Deferred to Am-100

Deferred to Act-100

Deferred to Am-100



Reqt .

NAS-SS-1000

Description/Title


Remarks

ID#

OTSE

OTSE

Integration

Operational

5046

3.2.1.1.1.1.2.4.1 The RMS shall contain two modes

- a remote

T

x

Deferred to ACN-100

mode for comunication solely with the MPS, a

local mode for communication solely with the

MDT, and a dual mode which provides all

messages to both the MPS and the MDT while

being controlled solely via the M

DT

interface.

5047

3.2.1.1.1.1.3.la

The RMS shall store all detected alarms and

T


alerts until such alarm or alert condition no

lonqer exist;

5048

3.2.1.1.1.1.3.1b

The RMS shall be able to store key

T

x

Deferred to ACN-100

performance parameter values, diagnostic

results, and operating mode data in temporary

storage in preparation for transferring said

information to the MPS;

5049

3.2.1.1.1.1.3.1~ The RMS shall store terminal messages routed

T


from an MDT to an MPS and routed from an UPS

to the MDT until the transfer has been

succe~~fully

received by the MPS or the MDT;

5050

3.2.1.1.1.1.3.1d

The RMS shall store two sets of threshold

T


values (each set to include: an upper limit,

a lower limit, or both) with one set for

alarm thresholds and one set for alert

thresholds in nonvolatile storage;

5051

3.2.1.1.1.1.3.1e

The RMS shall store general programs needed

T


for filtering data, formatting messages,

encoding messages, converting data, and

addressing messages in nonvolatile storage;

5052

3.2.1.1.1.1.3.1f

The RMS shall store cycle time intervals for

T

x Deferred to Am-100

each of

the cycles required by

3.2.1.1.1.1.2.1f;

5053

3.2.1.1.1.1.3.1g

The RMS shall maintain records of the value

T


of each monitored parameter, periodically

updating each record.

Verification Methods: T=Test, D=Demonstration, A=Analysis, I=Inspection, x

=~ot ~~~licabl~



r Reqt .

NAS-SS-1000

Description/Title


Remarks

ID#

OTCE

OTCE

Intwration

Operational

5054

3.2.1.1.1.1.3.3a

Th

eR

MS

sha

llst

or

ein

for

ma

tio

nn

ee

de

dto

T

x Deferred to A

m-100

decode control and adjustment commands for

that RMS;

5055

3.2.1.1.1.1.3.3b

Th

eR

MS

sh

all

sto

re

the

init

iali

za

tio

nd

ata

T


needed to initialize the subsystem including

all site dependent parameters in non

volatile memory;

5056

3.2.1.1.1.1.3.3~ The RMS shall store all disable commands

T


received until the alarm is re-enabled;

5057

3.2.1.1.1.1.3.4a

The RMS shall store only filtered key

T

x

Deferred to A

m-100

performance parameter values obtained

through monitoring;

5058

3.2.1.1.1.1.3.4b

The RMS shall store alarm and alert

T


threshold values, initialization tables,

data required for interpreting addressing,

and control and adjustment message function

codes in non volatile storage;

5059

3.2.1.1.1.1.3.4~ The RMS shall update stored performance

T


parameter values and status data at least

once during the general status cycle time

interval, only keeping the most current

equipment performance data;

5060

3.2.1.1.1.1.3.4d

The RMS shall store, in nonvolatile memory,

T


the data necessary for interpreting a

message function code (the code within a

message used by the RMS to determine the

type of message) ;

5061

3.2.1.1.1.1.3.4e

The RMS shall retrieve maintenance data

T


stored in the RMS and deliver it to the

requesting unit upon receipt of a valid

command.

5062

3.2.1.1.1.1.4.1a

The RMS shall transfer collected subsystem

T

x Deferred to A

m-100

performance data and status messages to the

MDT and MPS upon request;

Verification Methods: T=Test, D=Demonstration, A=Analysis, I-Inspection, x=Not Applicable



Reqt .

NAS-SS-1000

Description/Title


Remarks

ID#

OTSE

OT6E

Integration

Operational

5063

3.2.1.1.1.1.4.1b

The RMS shall transfer performance parameter

T

x

Deferred to ACN-100

data as a data report to the MPS at a

specified interval defined as the key

performance parameter cycle time interval;

5064

3.2.1.1.1.1.4.1c

At a specified interval defined as the

T

x

Deferred to ACN-100

general status cycle time interval, the RMS

shall transfer general status information

consisting of a subsystem identifier, a date

and time-stamp, and an indication that the

subsystem is either 11 in an alarm condition

(red status1 , 2) in an alert condition

(yellow status), or 31 operating properly

(green status1 ;

5065

3.2.1.1.1.1.4.1d

The RMS shall transfer a state change

T

x

Deferred to A

m-100

message when such a change is determined and

requires MPS notification.

If appropriate,

this message includes information indicating

a specialist has loqged on or off the RMS

via an MDT;

5066

3.2.1.1.1.1.4.le

The RMS shall transfer the diaqnostic

T


performance parameter values to either the

MDT or the MPS when requested. This request

does not imply MPS control;

5067

3.2.1.1.1.1.4.lf

If an alarm or an alert condition is

T

x

Deferred to ACN-100

detected, the RMS shall transfer the

appropriate alarm or alert message

containing measured parameter values to the

MPS once.

5068

3.2.1.1.1.1.4.2

All security alarms, either facility or data

T

x

Deferred to ACN-100

access, shall be transmitted to the MPS.

5069

3.2.1.1.1.1.4.3a The RMS shall transfer a messave indicating

T


a state change whether the change is due to

an automatic process or a command;

5070

3.2.1.1.1.1.4.3h

Upon receipt of an invalid command, the RMS

T

x Deferred to A

m-100

shall transfer a message indicatinq that the

received command is invalid to the source of

the input;

Verification Methods: T=Test, D=Demonstration, A=Analysis, I=Inspection, x=Not Applicable



Reqt .

NAS-SS-1000

Description/Title


Remarks

ID#

OT6E

OThE

Integration

Operational

5071

3.2.1.1.1.1.4.3~ The RMS shall report the disabling and

T


enabling of an alarm or an alert as a state

change.

5072

3.2.1.1.1.1.4.4a When an MDT is attached to the RMS port, the

T

x

Deferred to ACN-100

RMS shall provide the MDT operator access to

the RMMS network provided that the operator

satisfies the appropriate security

procedures;

5073

3.2.1.1.1.1.4.4b

The RMS shall transmit data in response to a

T

x Deferred to A

m-100

valid request from the MPS and the MDT;

5074

3.2.1.1.1.3a

The NAS subsystem containing the RNS shall

T

x

Deferred to A

m-100

contain a dedicated port for attachment of

an MDT;

5075

3.2.1.1.1.3b

No RMS function shall interfere with other

T


functions of the RMS or the subsystem of

which it is a part.

P

Verification Methods: T-Test. D=Demonstration, A=Analysis, I=Inspection, x=Not Applicable

CL