ORDER

Project Implementation Plan for ARTS IIIA Mode C Intruder (MCI)

February 7, 1994

DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

Distribution: A=W(NA/AP/SU/HT/OS/SE/NS/TM/TZ/SM/FE/TP/TR/LM)-3tnitiatedBy: ANA-900

A-ZY-3; A-X(AF/AT)-3; A-FAF-7; A-FAT-8
217194

DIRECTIVE NO.

I

6190.15

I

CHANGE

T O

BASIC

SUPPLEMENT

OFWONAL

CHANGE

TO ,

BASIC

SUPPLEMENTS

OPTIONAL

FAA Form 1320-S (640) USE mEWus EDITION
217194 6190.15

This order transmits the project implementation plan for the Automated Radar Terminal

System (ARTS) IIIA Mode C Intruder (MCI) project. It provides management direction and

technical guidance fkom project inception through commissioning for orderly implementation

of the ARTS IIIA MCI project. The procedures and responsibilities of the Federal Aviation

Administration (FAA) were developed using current agency directives. This order establishes program management, project implementation policy, and responsibilities governing the

activities of organizations, and also identifies and describes specific events and activities to

be accomplished in order to implement the ARTS IIIA MCI project.

Program Manager

i(and ii)
217194 6190.15

TABLE OF CONTENTS

CHAPTER 1. GENEIUL

1. Purpose

2. Distribution

3. Authority to Change this Order

4. Applicability

5. Duration

6..19. Reserved

CHAPTER 2. PROJECT OVERVIEW

20. Synopsis

21. Purpose

22. History

23:29. Reserved

Figure 2-1 ARTS IIIA Software Development Process

CHAPTER 3. PROJECT DESCRIPTION

30. Functional Description

31. Physical Description

32. System Requirements

33. Interfaces

34. - 39. Reserved

CHAPTER 4. PROJECT SCHEDULE AND STATUS

40. Project Schedule and Status

41. Milestone Schedule Summary

42. Interdependency and Sequence

43: 49. Reserved

CHAPTER 5. PROJECT MANAGEMENT

50. Program/Project Management, General 13

51. Project Contacts 14

52. Project Coordination 14

53. Project Responsibility Matrix 31

54. Project Managerial Communications 31

55. Implementation Staffing 32

11

11

11

11
6190.15

56. Planning and Reports 32

57. Applicable Documents 33

58:59. Reserved 33

CHAPTER 6. PROJECT FUNDING

60.

61 . -

Project Funding Status, General

69. Reserved

CHAPTER 7. DEPLOYMENT

70. General Deployment Aspects

71 . Site Preparation

72 . Delivery

73 . Installation

74:79. Reserved

Table 53-1 Activity Responsibility Matrix

CHAPTER 8. VERIFICATION

80.

81 .

82 .

83 .

84.

85 .

86.

87.

88.

89.

General 39

Test Documentation 39

DT&E 40

OT&E Integration Testing 41

OT&E Operational Testing 42

PAT&E 43

OT&E Shakedown Testing 43

Operational Readiness Demonstration 44

Joint Acceptance & Inspection 44

Reserved 44

CHAPTER 9. INTEGRATED LOGISTICS SUPPORT

Maintenance Concept

Training

92:99. Reserved

90.

91 .

CHAPTER 10. ADDITIONAL PROJECT IMPLEMENTATION PLAN ASPECTS

100. Configuration Management

101 Commercial Software

102:109. Reserved

217194

35

35

37

37

37

37

37

45

45

45

47

47

47

iv
2/7/94

APPENDIX 1:

APPENDIX 2:

APPENDIX 3:

APPENDIX 4:

APPENDIX 5:

APPENDIX 6:

Software Development and Test Shcedule

MCI Hardware Delivery Schedule

MCI Program Milestones

Project Contacts

List of Applicable Documents

Acronyms List

6190.15

1

1

1

1

1

1
217194 6190.15

CHAPTERl. GENERAL

1. l?WU?OSE. This Project Implementation Plan (PIP) provides management direction and

technical guidance to all levels of the Federal Aviation Administration (FAA) in the implementation of the Automated Radar Terminal System (ARTS) IIIA Mode C Intruder (MCI)

project from inception through commissioning. The PIP provides overall guidance and

direction to involved organizations by establishing program management and project

implementation policy and defining organizational roles and responsibilities in support of

project implementation. In addition to providing overall guidance and direction for implementation, the plan also identifies and describes specific events and major project activities.

2. DISTRIBUTION. This order is distributed to the branch level of the Program Director

for Automation, Program Manager for Advanced Automation, Associate Administrator for

Contracting and Quality Assurance, Offices of Air Traffic System Management, Air Traffic

Program Management, Training and Higher Education, Requirements and Life Cycle

Managment, Operational Support Service, National Airspace System (NAS) System Engineering Service, NAS Transition and Implementation Service, Systems Maintenance Service,

Facility System Engineering Service, Air Traffic Rules and Procedures Service, and Air

Traffic Plans and Requirements Service; to the branch level at the FAA Technical Center; to

the branch level at the Mike Monroney Aeronautical Center; to the branch level of the

regional Airway Facilities and Air Traffic divisions; and to Air Traffic and Airway Facilities

field offices with ARTS IIIA automation systems.

3. AUTHORITY TO CHANGE THIS ORDER. This order is issued under the authority

of the Program Director for Automation, ANA-l; the Director, Air Traffic Plans and

Requirements Service, ATR-1; and the Director, Air Traffic Rules and Procedures Service,

ATP-1. The authority to issue changes to this order is reserved for the Program Manager

for Terminal Automation, ANA-SO.

4. APPLICABILITY. The information contained herein will be used by FAA offices,

services, regions, centers (Mike Monroney Aeronautical Center (AMC) and the FAA

Technical Center (ACT)), terminal sites, and contractor personnel for accomplishing their

support of the ARTS IIIA MCI project. The guidance and schedule information contained

herein will form the framework for these organizations in the more detailed planning

activities required at the regional and field levels. Deviations from this order must be

approved by the Program Manager for Terminal Automation, ANA-500.

5. DURATION. The duration of this program will continue through commissioning of the

last ARTS IIIA MCI site.

6.49. RESERVED.

Chap 1

Par 1 Page 1 (and 2)
217194

CHAPTER 2. PROJECT OVERVIEW

6190.15

20 SYNOPSIS. The ARTS IIIA MCI program will provide for functional and perforrnkce enhancements and establishment of a common-source software baseline for the ARTS

IIIA terminal facilities. The common-source baseline will facilitate software maintenance

until the terminal advanced automation system (TAAS) replaces the existing ARTS systems.

This common-source baseline product of the ARTS IIIA software development effort will be

deployment of the A3.06 version of the ARTS IIIA operational software. Development of

this version is a three-phase process. The initial phase utilized the A3.04 version deployed at

the time of project initiation. This contained the operational functions that were in use for

the ARTS IIIA facilities, additional functions to accommodate Tampa/Sarasota as another

ARTS IIIA dual site, and performance improvements needed for increased capacity as

derived from techniques successfully implemented at the New York (NY) Terminal Radar

Approach Control (TRACON). The second phase was to integrate the MCI conflict alert

(CA) from the NY TRACON ARTS IIIE, an enhanced performance monitor (EPM), retrack

processing (RETRACK) and continuous data recording (CDR) editor modifications, and

some processing efficiency improvements into the A3.04 standardized baseline. In a parallel

effort, the ARTS IIIA Field Support Branch Software Section, AOS-413, was developing the

next release of the ARTS IIIA operational software, A3.05, which was deployed in late

1992. The A3.05 software was provided to the contractor as Government-furnished property

(GFP). The third phase was to integrate the MCI standardized baseline with program

technical reports (PTR) into the A3.05 GFP as a new release of the operational baseline,

A3.06. Figure 2-1 shows this development process.

21. PURPOSE. The Federal Aviation Act of 1958, as amended, charges the FAA with

ensuring the safety of aircraft and the efficient use of airspace in the United States. One

aspect of this responsibility is the safe and efficient control of aircraft in the terminal areas.

Currently, some of the ARTS IIIA facilities are at or near the limits of software and

hardware capacity. As the system becomes saturated, a consistent level of safety is more

difficult to maintain and air traffic delays may occur. To accommodate the increased

tracking and display requirements and maintain the necessary level of safety, additional

equipment and upgraded software are required at each TRACON.

To handle the projected air traffic growth efficiently and remain within the existing

ARTS IIIA environment, the ARTS IIIA Interim Support Program (ISP)/MCI contract was

executed. The contract provides additional hardware and a software upgrade. To provide

added safety, the MCI software in use at the NY TRACON will be adapted and incorporated

into the ARTS IIIA operational baseline software in release A3.06. This will allow continued system growth within the existing ARTS IIIA architecture to operate with increased

Chap 2

Par 20 Page 3
6190.15 217194

numbers of sensors, attain a larger track capacity, and drive an increased number of local

and remote displays while meeting the future air traffic control (ATC) demands until

implementation of advanced automation system (AAS).

This PIP addresses the MCI operational baseline software portion of the contract. The

additional hardware was addressed in the ARTS IIIA ISP PIP, Order 6190.14 dated

February 1, 1993.

CONTRACTOR I GOVERNMENT

ACTIVITY I ACTIVITY

I I

TAMPA

FUNCTIONS

NY TRACON

EFFICIENCY

MCI

EPM

CPU EFF.

PTR's

-1 A3.04 1

1 I

STANDARDIZED

b BASELINE

MCI

STD/BL

v

A3.06

OP/BL

DEPLOY

Figure 2-1. ARTS IIIA Software Development Process

Page 4

Chap 2

Par 21
217194 6190.15

22. HISTORY.

a. Current Capability. The ARTS IIIA equipment provides the capability to process,

track, and display all primary and secondary radar data from single or dual sensors and

supports radar-to-beacon target correlation. Additionally, it provides minimum safe altitude

warning (MSAW) and CA.

The ARTS IIIA uses radar and beacon data, flight data from an Air Route Traffic Control

Center (ARTCC) host computer and manual data inputs to assist air traffic controllers in

performing real-time tracking of aircraft within the terminal area. Logical and computational

functions are performed by input/output processors. Processed data is supplied to multiplexed display buffer memories which control the presentation of alphanumeric data on the

controller displays.

The current ARTS IIIA systems have a maximum capacity of 700 tracks and 24 displays

dual-sensor configuration, or 350 tracks and 16 displays in a single-sensor configuration.

The ISP expands the capacity as follows:

ina

Sensors

1

2

3

Number of

Tracks

500

700

900

Displays

30

36

25

b. Planned Capability. CA provides visual and aural alerts to controllers in the

event that aircraft under their control are predicted to come into potentially hazardous

proximity to, are currently in close proximity to, or are noted to be in a maneuver which

could result in a potentially hazardous proximity to other controlled aircraft. The CA

function is extended in the MCI standardized software baseline to monitor and detect every

potential conflict between unassociated and controlled Mode C aircraft in the same sensor

subsytem. This MCI capability currently under development will be installed and operational

at all ARTS IIIA sites by September 1995.

c. Contract History. The ARTS IIIA ISP contract, DTFAOl-89-C-00058, was

awarded to Unisys Corporation, St. Paul MN, on September 29, 1989. This contract

provided for initiation of the MCI development for the ARTS IIIA system. The software

tasks included design of the standardized ARTS IIIA baseline. This was the initial task for

development and integration of the MCI capability. A letter contract was awarded to Unisys

on September 28, 1990. This contract, modification 007 to the basic ARTS IIIA contract,

was to complete the development, integration, and implementation of MCI. The letter

contract was definitized via modification 0013 to the basic contract on June 28, 1991.

Chap 2

Par 22 Page 5
6190.15 217194

This contract not only provided for MCI software development, but also provided for the

development and deployment of version A3.06 of the ARTS IIIA operational programs. It is

also the instrument for procurement of the hardware required to implement MCI.

23.-29. RESERVED.

Page 6

Chap 2

Par 22
217194

CHAPTER 3.

30. F’UNCTIONAL DESCRIPTION.

6190.15

PROJECT DESCRIPTION

The MCI function will provide the controller with

conflict situation warnings between controlled and uncontrolled Mode C-equipped aircraft.

This is in addition to the CA’s between controlled and unassociated Mode C-equipped

aircraft. Conflict situations between uncontrolled aircraft pairs are not detected nor declared

by the MCI or CA functions.

The CA function consists of two major software components that operate in series. These

two components are the primary filter and the secondary filter. The primary filter acts as the

front-end filter for the CA function. Its objective is to pass on to the secondary filters all

aircraft pairs that are currently in, or that could possibly be in, a conflict situation within

approximately 40 seconds, and to reject all other pairs. Its main purpose is to limit the

computer resources needed by the more central processing unit (CPU)-intensive secondary

filters, but not to eliminate aircraft pairs that are or could be in conflict. The CA primary

filter accomplishes its job by searching in the vicinity of each controlled aircraft within a

square geographical area for other controlled aircraft.

The three secondary filters contain the intelligent decision logic for detecting and declaring

alerts on specific aircraft pairs. The purpose of the secondary filters is to analyze aircraft

pairs data passed by the primary filter and determine which should result in an alert

displayed to the controller. For a specific pair, any one or more of the three secondary

filters can declare an alert on any given scan.

The change to CA to accommodate the integration of MCI occurs in the primary filter. The

modification to the primary filter is the enhancement of the box-check to examine all

controlled MCI-equipped aircraft for conflicts with uncontrolled MCI-equipped aircraft. The

functionality of the CA secondary filter alert declaration logic remains unchanged from the

current design. The only impact to the secondary filters is the increased number of aircraft

pairs that must be processed. Once an MCI pair is in conflict, it will continue to qualify for

secondary filter processing until the secondary filter declares that the conflict no longer

exists. The primary filter modification is to perform a box-check to examine all controlled

aircraft for conflicts with other controlled or uncontrolled aircraft. For all controlled aircraft

below a certain threshold speed (200 knots), the size of the primary box is increased by a

parameter distance on each side (3 nautical miles). Any new track on an uncontrolled

aircraft will qualify for a primary filter box-check.

With respect to the CA function, addition of the functionality is transparent to the controller.

It simply makes the primary filter more conservative by allowing more aircraft pairs to pass

Chap 3

Par 30 Page 7
6190.15 217194

onto the secondary fdters. Even though more aircraft pairs will pass on to the secondary

filters, these unmodified filters will prevent any extraneous, nuisance CA alerts fkom

occurring.

31 PHYSICAL DESCRIPTION. This PIP describes the evolution of the MCI software

capability within the ARTS IIIA operational program. There will be no physical change to

the existing ARTS IIIA’s. Additional input/output processors, type B (IOPB) will be

provided to each of the existing sites that will raise the quantity to six for single sensor sites

and eight at multiple sensor or high traffic volume single sensor sites.

This contract provides for the additional hardware equipment as well as the added safety

features of the MCI software that allows continued system growth within the ARTS IIIA

architecture, while meeting future ATC demands awaiting the implementation of the AAS.

32. SYSTEM REQUIREMENTS.

a. Required Operational Characteristics. The ARTS IIIA ISP/MCI must operate up

to the capacity limits defined in section 22.a. These characteristics, although somewhat

transparent to the air traffic controller, provide an enhanced capability over the ARTS IIIA

(non-ISP systems).

b. Required Technical Characteristics. Detailed technical characteristics are those

documented in the ARTS IIIA Computer Program Functional Specifications (CPFS) and

ARTS IIIA Software Requirements Specification, ATC 40012. Major characteristics of the

ARTS IIIA ISP are as follows:

(1) The capability to process up to 900 tracks, including flight plans.

(2) Processing capacity such that utilization will not exceed the specified amounts

for the following baselines:

(a) MCI Standardized baseline - 75% of the total processor capacity with at

least one spare processor available for system redundancy and support.

(b) Operational baseline - shall be measured but need not meet the requirements of the MCI standardized baseline.

(3) Memory utilization will not exceed the specified amounts for the following

baselines:

(a) MCI Standardized baseline - 75% of available memory.

Page 8

Chap 3

Par 30
217194 6190.15

(b) Operational baseline - shall be measured but need not meet the requirements of the MCI standardized baseline.

c. Unique Characteristics. While all ARTS IIIA ISP sites will receive MCI capability, selected sites will utilize full digital ARTS displays (FDAD) in lieu of data entry and

display system (DEDS). One site (Jacksonville) will operate in a unique triple-sensor

configuration. A number of sites, due to their high traffic volume, will require eight

IOPB’s, rather than six IOPB’s, to attain necessary expanded track capability.

33. -ACES.

a. Internal Interfaces. There are no changes to the internal interfaces within the

system as a result of the changes to the code.

b. External Interfaces. The external interfaces also remain the same. The IOPB’s

interface with the sensor receiver and processor (SRAP) or the surveillance communication

interface processor (SCIP) to receive surveillance data.

The interfacility communication adapter (ICA) provides the interfacility input/output (IO)

interface to the ARTCC.

The local bright radar indicator tower equipment @VIE) or digital BRITE (DBm)

alphanumeric subsystem (BANS) processor has an interface to the local BANS and the

remote BANS processor. It also has an interface to the remote display buffer memory

(RDBM)/BANS.

34. - 39. RESERVED.

Chap 30

Par 32 Page 9 (and 10)
217194 6190.15

CHAPTER 4. PROJECT SCHEDULE AND STATUS

40. PROJECT SCHEDULE AND STATUS. As noted earlier in this PIP, the primary

product of this project is delivery of the new release of the ARTS IIIA operational program,

A3.06, with the MCI feature incorporated. Implementation will be in accordance with the

standard procedures for deploying a new operational program release. The software

development/testing schedule shown in appendix 1 indicates that A3.06 release will occur in

January 1994. At that time, AOS-413 will initate a notice of national release. It will then be

the responsibility of the site to obtain a copy and adapt it to their individual site. Appendix 2

provides the delivery schedule for the hardware that must be in place prior to implementing

A3.06 with the MCI function. As a result of the extended period for hardware delivery,

those sites that will not receive the requisite hardware prior to the release of A3.06 will not

be able to implement MCI until after hardware installation. It will be the site responsibility

to call for, site adapt, load, test and activate A3.06 based upon availability of installed

hardware.

41. MILESTONE SCHEDULE SUMMAR Y. Appendix 3 provides the milestones

required to complete the software development and deploy the A3.06 operational program.

42. INTERDEPENDENCY AND SEQUENCE. Relationship to FAA’s Capital Investment

Plan (CIP):

a. CIP Project 32-20, Expand Automated Radar Terminal System (ARTS) IIIA

Capacity and Provide Mode C Intruder (MCI) Capability. In order to increase

ARTS IIIA processing capability, four IOPB’s are being added to the current system. MCI

software is being procured and implemented into the existing ARTS IIIA systems. Ancillary

ARTS IIIA hardware is also being procured to support MCI.

b. CIP Project 46-30, Interim Support Program (ISP). Provides interim support

actions using off-the-shelf devices and existing facilities project contracts. These actions

involve hardware replacement, the addition of operating positions at some existing facilities,

and software adaptations to expand the capacity of some ARTS systems. This is the second

major project that provides the basis for building to the ARTS IIIE components (see CIP

project 32-20 above).

c. CIP Project 56-58, National Airspace Integrated Logistics Support (NAILS).

Provides for two separate information systems to be established to aid program officials in

life-cycle logistics management by providing (1) pre-commissioning logistics event scheduling

and (2) actual field operations information.

43.- 49. RESERVED.

Chap 4

Par 40 Page 11 (and 12)
217194

CHAPTER 5. PROJECT MANAGEMENT

6190.15

50. PROGRAM/PROJECT MANAGEMENT, GENERAL.

a. ARTS IIIA ISP MCI Management. ARTS IIIA MCI integration will be accomplished by means of matrix management techniques, using established functional organizations. This approach requires a program manager (PM) to consolidate the efforts of a broad

range of supporting organizations, including FAA headquarters organizations, technical and

aeronautical centers, regional and field facilities, and possibly other government agencies and

contractors. The ARTS IIIA MCI project will be accomplished through the established FAA

Facilities and Equipment (F&E) program management organizations and lines of authority.

F&E PM’s will be accountable for their respective projects.

b. Memoranda of Agreement. The ARTS IIIA MCI PM will establish agreements

with each supporting organization and F&E program offices as required. These agreements

will be memoranda of agreement (MOA) outlining the tasks to be performed, products to be

delivered, schedules with milestones, and resource requirements. These agreements will

serve as commitments to satisfactory completion of agreed-upon tasks within the allocated

time.

c. ARTS IIIA MCI Project Manager Responsibility. The ARTS IIIA MCI project

manager is responsible for overall management of the ARTS IIIA MCI project according to

established MOA’s, periodic review of accomplishments, tracking of program resources, and

final review and approval of all tasks and products.

d. Executive Directors. Executive Directors for System Development, AXD-1 and

System Operations, AXO-1, are responsible for providing organization support to the

ARTS IIIA MCI project. They will ensure that all support services, deliverable products,

and resource requirements are provided within established schedules.

e. Project Management. Management of ARTS IIIA MCI project is the responsibility

of the Terminal Automation Program Office. The PM, ANA-500, is the ARTS IIIA MCI

project manager and the single focal point for all project management activities. The project

manager will ensure that the contractor has access to technical documentation, appropriate

data bases, and sources of information relative to GFP. In support of the projects, a

contracting officer (CO) acting as the Associate Program Manager for Contracts (APMC)

was designated by the Associate Administrator for Contracting and Quality Assurance (ASU)

to perform general contract management activities to assure that the terms of pertormance

under the contract are met. The CO has designated the Associate Program Manager for

Chap 5

Par 50 Page 13
6190.15 217194

Engineering (APME) as the technical officer (TO) within ARTS division (ANA-900) to

provide technical guidance and direction to the contractor within the scope of the contract.

The CO is the only person authorized to make changes affecting prices, deliverables, or

schedules. Management and technical support to the project manager and TO is provided by

the Advanced Automation Program (AAP) Systems Engineering and Technical Assistance

(SETA) program contractor.

51. PROJECT CONTACTS. Appendix 4 provides a listing of project management

personnel designated as contacts for their respective organizations.

52. PROJECT COORDINATION. Coordination between FAA organizational elements is

required in order for each organization to fulfill its assigned responsibilities. The following

paragraphs list organizational elements requiring coordination and their respective responsibilities in support of the project.

a. Headquarters. The following organizations within FAA headquarters, Washington,

DC, will fulfill the indicated project responsibilities:

(1) PM for Terminal Automation, ANA-500

(a) Provide overall management and direction of all FAA activities

necessary for successful development, acquisition, production, test and evaluation, transition

to user organization, and engineering support of the project.

(b) Define project needs, define tasks to be performed and expected

results, staffing estimates, contract cost estimates, budget estimates, schedules, management

procedures and controls, and required equipment and facilities.

(c) Establish matrix support agreements and hold functional organizations accountable for integrated logistics support, systems engineering technical support,

facilities planning, production quality and planning, test and integration, contracting, and

legal.

(d) Ensure timely preparation and submission of reports relative to

established cost, schedule, benefit and budget baselines to higher management and advise

them of project status and progress.

(e) Be the single focal point and point of contact (POC), serve as the

spokesperson, and provide coordination of all project management activities. The PM will

coordinate all public statements with the Office of Public Affairs.

Page 14

Chap 5

Par 50
217194 6190.15

(f) Initiate, conduct, and complete a thorough and objective project

deployment readiness review @RR) including fulfilling DRR team leader responsibilities.

(g) Develop project requirements (project verification requirements

traceability matrix WRTM]), prepare program directives for testing activities, prepare

requirements for development test and evaluation @T&E), coordinate shakedown testing,

and prepare documentation necessary for approving the budget to fund for the accomplishment of DT&E, integration, and shakedown testing.

(h) Co-chair the National Airspace Integrated Logistics Support

(NAILS) Management Team (NAILSMT).

(i) Formulate and manage the ARTS IIIA MCI budget. Provide

regular reports of the ARTS IIIA MCI status relative to established cost, schedule, and

budget baseline.

(j) Manage project interdependency with interfacing projects.

(k) Prepare and maintain the ARTS IIIA MCI master plan and other

documentation required to describe and manage the activities of the ARTS IIIA MCI project.

(1) Serve as the spokesperson for the ARTS IIIA MCI project and

control and approve the dissemination of program information according to FAA and

Department of Transportation (DOT) regulations. Represent the FAA in dealings with the

Office of the Secretary of Transportation (OST), other government agencies, contractors, and

the congress on matters regarding the ARTS IIIA MCI project.

(m) Develop and implement program controls and tracking systems to

support the management process.

(n) Provide liaison across organizational boundaries when necessary to

facilitate implementation of ARTS IIIA MCI.

(2) ARTS Engineering Division, ANA-900

(a) Provide technical guidance and direction to the contractor in the

design, development, testing, installation, integration, and production of hardware and

software and ensure that all technical contract requirements are met. Serve as the contract

TO.

(b) Serve as the Associate Program Manager for Engineering (APME).

Chap 5

Par 52 Page 15
6190.15 217194

(CCB).

(c) Serve as a member of the ANA Configuration Control Board

(d) Provide guidance to all offices, services, centers, and regions on

project implementation.

limitations.

(e) Ensure availability of fhnds and keep the contract within budget

(f) Serve as a member of the Test Policy Review Committee (TPRC)

as defined in Order 1810.4B, appendix I, page 19.

(g) Establish and chair project working groups as required.

(h) Prepare the Master Test Plan (MTP) jointly with the Engineering

Test and Evaluation Service (ACN).

(i) Conduct the Functional Configuration Audit (FCA) and Physical

Configuration Audit (PCA).

(3) Requirements and Life Cycle Management Service, Life Cycle Division,

ALM-500.

(a) Serve as the Associate Program Manager for Logistics (APML) to

support the PM in managing the total NAILS effort.

(b) Plan and coordinate the development of NAILS requirements.

(c) Coordinate development and update of the Integrated Logistics

support Plan (UP).

(d) Evaluate and integrate NAILS requirements in the planning and

procurement process.

(e) Monitor and track all NAILS functions.

(f) Review contractor NAILS data deliverables.

requirements.

(g) Review all procurement documents for inclusion of NAILS

.

Page 16

Chap 5

Par 52
217194

AOS-400.

CCB.

6190.15

(4) Operational Support Service, National Terminal Eqgineering Division,

(a) Develop software modifications tasked by the Air Traff% (AT)

(b) Integrate new software into the operational software.

(c) Test new software during development and prior to operational use.

(d) Provide technical input into the requirements definition process.

(e) Establish requirements for support software tools to be used in

their testing and maintenance of software.

(f) Support field elements in their software maintenance activities.

(g) Provide input to operational test and evaluation (OT&E) requirements.

(h) Support formal system tests.

(i) Develop system shakedown requirements.

(j) Develop shakedown test plan and procedures in accordance with

FAA-STD-024b, Preparation of Test and Evaluation Plans and Test Procedures.

(k) Conduct shakedown testing, perform data analysis, and prepare

reports.

(1) Support shakedown testing at the key field sites in accordance with

PM program directives.

(m) Support system on site tests (SOST).

(n) Support the FCA and PCA.

(0) Ensure software quality is maintained.

Chap 5

Par 52 Page 17
6190.15 217194

(5) Operational Support Service, National Systems Requirements Analysis

Division, AOS-100.

(a) Provides an interface within headquarters between air traffic, airway

facilities and program offices.

(b) Serves as a member of the CCB as required.

(c) Provide technical input into the requirements definition process.

(d) Ensures availability for second-level support functions.

(6) Air Traffic System Management Service, Airspace Management,

Current Systems Branch, ATM-520.

(a) Determine the operational acceptability of new terminal ATC

operational computer programs or systems prior to their delivery for operational testing and

use in the field facilities.

(b) Monitor computer program implementation schedules to ensure

terminal operational requirements are met.

(7) Air Traffic Rules and Procedures Service, Air Traffic Procedures

Division, ATP-100.

(a) Serve as the Associate Program Manager for Procedures (APMP).

(b) Update the operations and procedures orders as may be necessary.

(c) Coordinate with FAA components responsible for AT controller

operations to provide information on procedural matters.

(8) Air Traffic Plans and Requirements Service, System Plans and

Programs Division, ATR-100

(APMR).

(a) Serve as the Associate Program Manager for Requirements

(b) Develop plans, requirements, programs, and standards for system

improvement, modification, and expansion of the air traffic control system, and maintain the

air traffic system plan.

Page 18

Chap 5

Par 52
217194 6190.15

(c) Establish operational requirements for air traffic systems throughout the agency. This excludes the development of operating procedures and separation

standards.

(d) Validate and develop requirements in support of today’s and the

near term air traffic environment for:

operating system.

1. Integrating the results of development efforts into the

2 Expanding and improving the current system.

(e) Develop specific capital investment priorities based upon air traffic

system requirements for the F&E

scenarios.

budgetary processes for current and near-term planning

(f) Identify

the accomplishments of air traffic

and validate telecommunications requirements necessary

activities, and coordinate with Systems Maintenance

Service to develop plans for implementing the required service.

for

(g) Serve as the air traffic focal point for coordination of today’s and

the near-term programs and system requirements with other offices, services, agencies, and

organizations.

(h) Collaborate with the Automation Software Division, the Advanced

Systems and Facilities Division, and the Operational Support Service to ensure that the

validated requirements are being satisfied during development, testing, and evaluation of new

systems.

(i) Assess current programs and proposed planning requirements,

based on agency planning standards and guidelines; recommend priorities for system

improvement, modification, and expansion; and make adjustments as appropriate.

(j) Plan for a secure and effective air traffic system communications

capability and develop air traffic communications requirements.

(k) Serve as the air traffic focal point for coordinating FAA policy and

planning relating to privatization activities and aviation weather services provided by air

traffic facilities.

(1) Determine operational requirements for appropriate real-time data

interchange capability between en route, terminal, and flight service elements of ATC

automation systems.

Chap 5

Par 52 Page 19
6190.15 2l7J94

(9) Air Traffic Plans and Requirements Service, Automation Software

Policy and Planning Division, ATR-200

will be met.

0a

0)

0C

Develop software requirements.

Monitor development activities to ensure software requirements

Verify that requirements have been met before new functional

software is operationally utilized.

(d) Maintain configuration control of the software.

(e) Ensure the quality of air traffic functionalities.

(f) Provide the primary air traffic interface within headquarters on

automation software and automation performance issues.

(g) Establish and monitor policies and procedures used in testing,

implementation, and administration of all air traffic automation efforts.

(h) Ensure continuity and compatibility between air traffic automation

software systems and activities.

(APMSE).

ments.

0i

(10) NAS

0a

0)

0C

00

Serve as chairperson of the AT CCB.

System Engineering Service, Automation Division, ASElOO

Provide an Associate Program Manager for Systems Engineering

Serve as a member of the ANA CCB.

Serve as a member of the AT CCB.

Provide NAS system level requirements for test and evaluation

0e Verify compliance with the NAS system level and OT&E requirePage 20

Chap 5

Par 52
217194

(0

@I

Evaluation Policy.

0

0i

(11) NAS

6190.15

Coordinate test policy waivers.

Verify compliance with Order 1810.4B, FAA NAS Test and

Develop the VRTM.

Coordinate approval of the MTP.

Systems Engineering Service, Engineering Specialties and

Configuration Management Division, ASE600

ments.

0a

@I

0C

((0

0e

Provide NAS system level requirements for T&E.

Verify compliance with NAS system-level and OT&E requireCoordinate test policy waivers.

Verify compliance with Order 1810.4B.

Provide guidance and direction on the conduct of FCA and PCA.

(12) Associate Administrator for Contracts and Quality Assurance,

Contracts Division, Automation/Advanced Automation Branch, ASU-350.

(a) Serve as the CO.

(b) Serve as the Associate Program Manager for Contracts (APMC).

(c) Plan, negotiate, execute, and administer all prime and related

contracts in support of the PM.

(13) Associate Administrator for Contracts and Quality Assurance,

Industrial Division, Quality Assurance Branch, ASU-420.

(a) Provide an onsite Quality and Reliability Officer (QRO).

(b) Provide support to ANA-500 during’ factory verification tests.

Chap 5

Par 52 Page 21
6190.15 217194

(c) Provide quality assurance support for production acceptance test and

evaluation (PAT&E).

testing.

(d) Provide support to T&E parameters for incorporation in shakedown

(e) Serve as a member of the TPRC.

(f) Provide an Associate Program Manager for Quality (APMQ).

(14) Office of Training and Higher Education, Airway Facilities Training

Program Division, AHT-400

standards, systems,

laws, and Office of

are taken to correct

(15) Office of Training and Higher Education, Air Traffk Training

Program Division, AHT-500

(a) Develop and recommend technical training policies, programs,

and procedures to meet FAA program requirements, applicable federal

Personnel Management (OPM) and DOT regulations.

(b) Administer technical training programs and policies.

(c) Evaluate the technical training programs and ensure that measures

deficiencies.

(d) Provide training programs.

(e) Develop, operate, and maintain a management information system.

programs, standards,

ble federal laws, and

(a) Develop and recommend air traffic technical training policies,

systems, and procedures to meet FAA program requirements, applicaOPM and DOT regulations.

(b) Support the Training Requirements Program (ATZ-100) in the

development and administration of the training program.

(c) Provide consultant services to ATZ-100 as requested.

system.

(d) Develop, operate, and maintain a training management information

Page 22

Chap 5

Par 52
217194 6190.15

(16) Office of Air Traffic Program Management, Training Requirements

Program, ATZ-100

(a) Administer the national air traffic technical training program

through training proposals, review and approval of training plans, review of specifications

and contractor-developed proposals in response to request for proposal for training, and the

development of training courses and materials.

(b) Develop and administer technical training.policies, programs, standards, systems and procedures to meet FAA program requirements, applicable federal laws,

and OPM and DOT regulations.

(c) Evaluate the technical training programs and ensure that measures

are taken to correct deficiencies.

(d) Provide training programs.

(e) Develop, operate, and maintain a management information system.

(17) SETA Contractor. The SETA contractor is responsible for program

support in the following areas:

subsystems.

(a) Assist in the preparation of procurement packages for systems and

subsystems.

(b) Assist in reviewing contractor technical proposals for systems and

(c) Monitor system and subsystem design and the status of system and

subsystem technical activities.

(d) Provide technical assistance in the review and evaluation of system

and subsystem designs, production and test; and perform analyses of technical problems as

directed.

subsystems.

(e) Monitor activities associated with field installation of systems and

(f) Support the configuration management process.

(g) Provide technical assistance in the review and development of

training policies, programs, standards, systems and procedures.

Chap 5

Par 52 Page 23
6190.15 217194

b. Field Organizations. Responsibilities of the FAA Technical Center, regions, and

other field organizations follow:

(1) Federal Aviation Administration Technical Center, Engineering, Test,

and Evaluation Service, Automation Division, ACN-100. The FAA Technical Center will

provide the support necessary to test and evaluate the project for functional and operational

performance and for compliance with contract requirements. The FAA Technical Center will

perform these duties in accordance Order 1810.4B, which designates ACN as the test

director. Accordingly, ACN will designate a test director for the projects. ACN will also:

(a) Serve as the Assoicate Program Manager for Test (APMT).

(b) Develop OT&E and NAS integration requirements for each

subsystem (project) in coordination with air traffic, airways facilities, other user organizations, and acquisition PM’s.

(c) Prepare testing program directives and coordinate agreements with

ATRlANA/AAF/ASU/AOS/ATZ.

(d) Prepare test monitor guidelines; prepare test plans and test

procedures for OT&E in accordance with FAA-STD-024b; prepare NAS integration test

plans and procedures in accordance with FAA-STD-024b; and prepare/concur on DT&E test

plans and procedures.

(e) Direct the conduct of DT&E, NAS integration, production

acceptance test and evaluation (PAT&E), and OT&E; conduct DT&E, NAS integration and

OT&E data analysis, and prepare reports.

T&E.

(f) Support ASE in development of NAS system-level requirements for

(g) Support acceptance testing at the first field site in accordance with

PM program directives.

(h) Maintain the status of test progress and test problems.

(i) Present reviews to the PM, as required.

Page 24

(j) Serve as a member of the CCB, as required.

Chap 5

Par 52
217194 6190.15

(lc) Operate and maintain NAS subsystems delivered to the FAA

Technical Center after FAA acceptance of the equipment.

(1) Provide for facility readiness at the FAA Technical Center.

(m) Maintain project documentation in accordance with Order 1750.6.

(n) Establish initial training requirements for FAA Technical Center

personnel and coordinate with the Office of Air Traffic Program Management, Training

Requirements Program, ATZ-100.

(0) Establish financial and item management control and accountability

for all agency property received at the FAA Technical Center.

(p) Support the DRR process.

(2) Mike Monroney Aeronautical Center, FAA Academy, AMA-400.

(a) Develop, monitor, and conduct training programs as directed by

the Director of Training and Higher Education, AHT-1.

books.

(b) Participate, as requested by AHT-1, in the review of instruction

(c) Assure timely selection of necessary instructors and maintenance

personnel to meet Mike Monroney Aeronautical Center training and staffing requirements.

(3) Regions. Each cognizant region has appointed a regional associate

program manager (RAPM). The RAPM will ensure that facilities and engineering work, if

required, is completed prior to the delivery. The RAPM will monitor installation and

‘. coordinate requests for contractual or technical support with ANA-900 and AOS-400. The

RAPM will arrange for the appointment of a Technical Onsite Representative (TOR) at each

facility. The regions will fulfill the following responsibilities:

(a) Prepare and monitor site installation in accordance with the

schedules discussed in chapter 4 and provided in appendices 1 and 2. Coordinate with ANA,

ATR, and AOS on any changes to these schedules.

(b) Assign a regional integration group (RIG) to provide for coordination, direction, and guidance necessary for effective and timely implementation of the

project. The RIG will be chaired by the regional APM (RAPM) and will be comprised of

Chap 5

Par 52 Page 25
6190.15 217194

regionally selected AT and Airway Facility (AF) personnel knowledgeable in implementation

of automation programs. The RIG will be responsive to the guidance and direction of the

region for monitoring the efforts at each affwted site within the region. The RIG is to

monitor and provide assistance and guidance in all phases of the terminal automation

implementation for all regional sites.

(c) Designate a TOR to serve at each affwted terminal facility. The

TOR provides the regional coordination, direction, and guidance necessary for effective and

timely accomplishment of site preparation functions during the terminal automation implementation at the site to which he/she is assigned. This includes on-site decisionmaking and

day-to-day problem solving. The TOR is to be the principal on-site regional representative

who reports problems, progress, and other matters to ANA900 through appropriate regional

representatives. The TOR is to be guided by approved test documentation and the project

implementation plan. Established channels of communications between regions and PM are

to be used in carrying out the terminal automation program. The TOR is also to serve as a

member of the RIG and terminal integration group (TIG).

(d) Serve as a member of the TIG at each affected site. The TIG is to

be comprised of designated on-site regional AT and AF personnel experienced in the

implementation of electronic antior automation systems. The TIG will be responsive to the

guidance and direction of the TOR. Personnel assigned to the TIG are to be engaged in test

activities subsequent to initial operational capability (IOC).

(e) Provide regional logistics requirements to ANS-430, ANA-500,

and the FAA Logictics Center.

(f) Support the development of test plans and procedures

tion and shakedown testing. Y

(8)

testing.

09

0i

commissioning.

.

0)

0

Conduct software integration and shakedown testing.

for integraConduct and/or monitor site acceptance and field shakedown

Conduct the operational readiness demonstration (ORD) and

Support ACN during OT&E testing.

Conduct site shakedown and operations changeover testing in

accordance with the requirements of the test plans for these functions.

Page 26

Chap 5

Par 52
217194 6190.15

(1) Obtain through the Defense Commercial Communications Office

(DECCO), as appropriate, all telephone company (TELCO) services required for the timely

acquisition of communications required for ARTS IIIA ISPIMCI.

reached.

(m) Assure that appropriate FAA/military local on-site agreements are

(n) Prepare the operations changeover plan.

(0) Conduct the formal certification

designated terminal facilities.

A

exercise (commissioning) for

load tapes.

(p) Generate site-specific adaptation data for the creation of system

(cl) Establish financial and item management, control, and accountability for all agency property received in the region.

c. Project Support Organizations.

(1) In accordance with Order 1800.8F, National Airspace System Configuration Management, the CCB is authorized to approve or disapprove baselines and changes to

the baselines. There is a central NAS CCB to establish and control baselines and to

administer configuration control. From this CCB, authority is delegated to lower-level

CCB’s to effectively administer proposed changes at the most appropriate level. All

lower-level CCB’s will be accountable to the NAS CCB which has been established through

a charter defining its authority, responsibilities (including the specific documents over which

the CCB has control), and membership. Decisions and directives are documented in

configuration control decisions (CCD), which either approve, disapprove, defer, or refer the

change request to another CCB. When contractual action is required, the CCD serves as a

basis for preparation of a procurement request which is submitted to the CO. CCD’s may

also be distributed to other government agencies and serve as an official notification of CCB

action. Representation on the CCB includes the various agency/services/offices that have

responsibilities to acquire, support, and operate the system. Representatives of other

organizations may be invited to attend as required.

(2) Two lower level CCB’s have been established to oversee modifications to

the ARTS IIIA MCI system. The ANA CCB was established to act on NAS Change

Proposals (NCP) relating to the hardware and hardware specifications/standards. The ANA

CCB will refer NCP action to the NAS CCB if the circumstances dictate. The ATR CCB

Chap 5

Par 52 Page 27
6190.15 217194

was established to act on NCP’s relating to changes submitted to the operational software or

the software CPFS’s. They too have the authority to refer actions to the NAS CCB if

necessary.

(a) ANA CCB.

-*1

-O2

Management Branch.

a.

Division, ASE-600

ATR-200

AOS-100

Chairperson:

Director, Automation, ANA-l, or designated representative.

Executive Secretary:

ASE-620 or designated representative, Manager, Configuration

Other Permanent Members:

Manager, Maintenance Engineering Division, ASM-100

Manager, Advanced Automation System Division, AAP-200

Manager, Industrial Division, ASU-400

Manager, Automation System Engineering Division, ASE-100

Manager, Engineering Specialties & Configuration Management

Manager, System Plans and Programs Division, ATR-100

Manager, Automation Software Policy and Planning Division,

Manager, Facility Programs and Transition Division, ANS-200

Manager, National Systems Requirements Analysis Division,

Cognizant PM

Cognizant SETA manager

Page 28

Chap 5

Par 52
217194 6190.15

Cognizant SEIC manager.

3. Ad Hoc Members:

Ad hoc members represent FAA organizations other than those

already represented by the permanent ANA CCB membership, which will be impacted by

changes being decided by the ANA CCB. Their function is to ensure that proposed changes

are consistent with the technical and policy positions of their organizations. Ad hoc

members include:

Manager, National Engineering Field Support Division, AOS-200

Cognizant project TO.

Cognizant Program Engineering Service Division managers as

appropriate

Manager, Contracts Division, ASU-300

Manager, National Airspace System Division, AOV- 100

Manager, FAA Logistics Center, AML-1

Cognizant program CO.

5.. Technical Advisor, Consultants, and Program Control

are invited to attend ANA

management information.

Specialist:

Personnel from various government and contractor organizations

CCB meetings to provide specialized technical or program

(b) AT CCB.

1. Chairperson:

Manager, Air Traffic Automation Software Division, ATR-200.

2. Executive Secretary:

Branch Manager, Configuration Management, ASE-620.

Chap 5

Par 52 Page 29
6190.15 217194

AOS-400

3.

-*4

Other Permanent Members:

Manager, System Plans and Programs Division, ATR-100

Manager, Procedures Division, ATP-100

Manager, Civil Operations Division, ATM-100

Manager, National Terminal Systems Engineering Division,

Manager, Advanced Automation System Division, AAP-200

Director, Automation ANA-l, or designated representative

Manager, Maintenance Engineering Division, ASM-100

Manager, Advanced Systems and Facilities Division, ATR-300.

Ad Hoc Members:

Ad hoc members represent FAA organizations other than those

already represented by the permanent AT CCB membership, which will be impacted by

changes being decided by the AT CCB. Their function ensures that proposed changes are

consistent with the technical and policy positions of their organizations. Ad hoc members

include:

Cognizant SETA manager

Cognizant SEIC manager

Manager, National Airspace System Division, AOV-100

Division, ASE-600.

Manager, Engineering Specialties and Configuration Management

5. Technical Advisor, Consultants, and Program Control

Specialist:

Personnel from various government and contractor organizations

are invited to attend AT CCB meetings to provide specialized technical or program management information.

Page 30

Chap 5

Par 52
217194 6190.15

53. PROJECT RESPONSIBILITY MATRIX. Table 53-l identifies organizational offices

having primary and supporting responsibility for major project activities.

TABLE 53-l

ACTIVITY RESPONSIBILITY MATRIX

TASK/PLAN/ACTIVITY

Implementation Schedule

PRIMARY OFFICE

ANA-500

Training Programs ATZ,

Schedules and Assignments AHT-400/500

Configuration Management

(Operational Software)

ATR-200

Software Maintenance

(Operational Software)

AOS-400

NAS Integration Test Plan

and Procedures

ACN-100

Shakedown Test Plan and

and Scripts

Operations Changeover

Plan

Logistic Support Planning

ORD Test Plan/Procedures

AOS-400

Regions

ALM-500

Regions

ATR, ANA-900, ATM, AAT

AMA, AOS400,Regions

ANA-%X), ATP, AOS-400

Regions

ANA-500, ANA-900

Regions

ANA-900, ATR-200,

AOS-400, ASE-100,

ASE-600

ANA-900, ATP, ATM,

ATR, ACN, ASE, ASU

AOS-400, ATR, ATP,

ATM

ANA-900, ANA-500,

AML, Regions

Regions ATR, ANA-500,

ANA-900, ATP, ATM,

AOS-400, ASE

54. PROJECT MANAGERIAL COMMUNICATIONS. Project managerial communications are provided monthly to ANA-l, through a program director status review (PDSR).

This PDSR provides insight into cost, schedule, technical, and logistics issues that may exist.

Chap 5

Par 53

Page 31
6190.15 217194

Communication to the various branches of ANA, ATR, AOS, ATM, ATP, AMA, AML,

ATZ, FAA Technical Center, and the regions occurs formally through technical interchange

meetings (TIM) that are conducted during all stages of the program and weekly core team

meetings.

55. IMPLEMENTATION STAFFING. Staffing peculiar to implementation of this project

includes assignments of regional APM’s, RIG’s, TOR’s, and TIG’s. Responsibilities of

these persons and groups are defined in paragraph 52.b.

56. PLANNING AND REPORTS.

a. Reports.

(1) The configuration control and status accounting report provides the .

information needed to identify configuration identification and determine the status of change

proposals, deviations, and waivers including implementation status.

(2) The project progress report provides the PM, CO, and TO a monthly

assessment of contractual effort as of the date of the report, work scheduled for the next

period, and special problem areas including proposed solutions.

(3) The PDSR provides monthly information to FAA management on cost,

schedule, and technical status of the projects.

(4) The PAT&E test report documents the results of PAT&E and is the

responsibility of the FAA Technical Center test director.

(5) The hardware discrepancy report documents hardware discrepancies.

(6) The operational changeover report documents the changeover activities to

bring a site into the NAS.

(7) The program technical report documents software discrepancies.

(8) The shakedown test report documents the results of FAA Technical Center

shakedown testing.

(9) The NAS integration report documents the results of NAS integration

testing and is the responsibility of the FAA Technical Center test director.

(10) The OT&E test report documents the results of OT&E and is the

responsibility of the FAA Technical Center test director.

Page 32

Chap 5

Par 54
217194 6190.15

b. Plans.

(1) The shakedown test plan defines tests of the system in an operational

environment to assess the readiness of people, procedures, and the system to assume field

operational status.

(2) The operational changeover plan defines the procedures, schedules and

techniques, coordination and training required to transition a facility to a new system/subsystem without degrading NAS operations.

(3) The OT&E test plan defines testing to be accomplished for assessing the

operational suitability and operational effectiveness of the system.

(4) The training plan defines those training activities to be accomplished to

ensure personnel are qualified before participation in site or system certification.

(5) The NAS integration test plan defines testing to be accomplished for

verifying compliance with NAS integration requirements. Integration requirements assess the

operation of multiple interfaces and integration with other systems in as realistic an

operational environment as possible.

(6) The DT&E plan defines testing to be performed for design assistance,

technical risk assessment, and specification performance verification. DT&E plans are

developed by the contractor in accordance with the contract.

(7) The site shakedown test plans define the tests required to confirm the

integrated readiness of people, procedures, and the system to assume field operational status.

(8) The ARTS IIIA MCI baseline test plan defines the test to assess performance in an operational environment.

(9) The ILSP defines the elements of the NAILS program applicable to the

project. The ILSP also describes the maintenance concept to be applied.

(10) The MTP defines the T&E program for the project and provides a

framework for the systematic test and evaluation of the system to ensure that all functional

and performance requirements are satisfied.

(11) The CIP provides a comprehensive plan for modernizing and improving

ATC and airway facilities through the year 2000.

57. APPLICABLE DOCUMENTS. See appendix 5.

58.-59. RESERVED.

Chap 5

Par 56 Page 33 (and 34)
217194 6190.15

CHAPTER 6. PROJECT FUNDING

60. PROJECT FUNDING STATUS, GENERAL. The ARTS IIIA MCI project implemented by this project plan is fbnded according to the following profile:

FUNDING PROFILE ($000) - ARTS IIIA MCI PROJECT

FY91 FY92 FY93 FY94 TOTAL

MCI S/W $2,600 $6,052 $300 $6,838 $15,790

61.9 69. RESERVED.

Chap 6

Par60 Page 35 (and 36)
217194 6190.15

CHAFCER 7. DEPLOYMENT

70. GENERAL DEPLOYMENT ASPECTS. A DRR will be conducted in accordance

with Order 1800.63A and all critical checklist items resolved prior to deployment. See

appendix 3 for the DRR schedule. Site deployment planning, site preparation, instdllation of

required equipment, and scheduling shall be the responsibility of the FAA. Each site will

prepare site-specific implementation schedules consistent with their own requirements.

Required equipment installation and testing will be the responsibility of the contractor as

described in Order 6190.14, dated February 1, 1993.

71. SITE PREPARATION. No additional site preparation

Order 6190.14 is anticipated for implementation of A3.06.

beyond that described in

72. DELIVERY.

a. Software. The contractor is responsible for packing and shipping software

including computer program tapes (operational and other computer support tapes), manuals,

and other documentation to ACN-100 at the FAA Technical Center. Subsequent delivery of

the operational software is made by ACN-100 to AOS-400 who prepares the software for

distribution to individual sites. (NOTE: ACN-140 shall forward a copy of the manuals and

other operating and instruction documentation to ATP-100 for review to determine if any

document change proposals are necessary.)

b. Engineering Services. The contractor shall be available to provide hardware and

software engineering services throughout the life of the contract. This includes providing

changes to the MCI software (operational, diagnostic, off-line, and utility), firmware, and

documentation to correct discrepancies observed during installation and testing. The

ARTS III PM, ANA-500, is the single focal point for obtaining contractor engineering

services to correct discrepancies observed during installation and testing. All requests for

contractor engineering services shall be made through AOS-400 (operational software

maintenance software, hardware, and firmware), to the project TO, who will arrange for the

required contractor support.

73. INSTALLATION. Upon completion of key site testing, AOS-400 will announce a

national release of the new baseline operational software for ARTS IIIA sites that includes

the MCI functionality. Based on the status of the required equipment availability, each site

will be responsible for requesting the release from AOS-400. The individual sites will be

responsible to perform the necessary site adaptations, and load the new program for local

testing and cutover. AOS-400 and the contractor field engineering personnel will be

available for assistance upon request.

74.979. RESERVED.

Chap 7

Par 70 Page 37 (and 38)
217194 6190.15

CHAPTER 8. VERIFTCATION

80. GENERAL. When completed, the ARTS IIIA ISP/MCI project will provide safety and

efficiency enhancements for ATC terminal systems. Assurance of this enhancement is

provided by a program which verifies that project requirements compliance is successfully

accomplished. This verification program is applicable to all produced and deployed project

hardware and software and is applicable to other project operational requirements. Essential

to the verification program is the T&E process. This process is documented by detailing the

plans, procedures, and results of system testing. This documentation shall:

a. Define the scope of testing required to ensure that the system, subsystem,

computer system configuration items (CSCI), computer software components (CSC), and

computer software units (CSU) meet applicable requirements. The requirements are

contained in, or derived and allocated from, the System Requirement Specification (SRS) and

CPFS’s.

b. Discuss the test configurations and test environments and identify the test facility,

equipment, the simulation program requirements, and the methods employed to measure

performance. The discussion should include the data reduction and analysis requirements and

provide a schedule for conducting the tests.

c. Include a traceability matrix to document the software interface requirements that

are to be satisfied or partially satisfied by each test.

d. Identify the corresponding test procedures and reports to be provided.

81. TEST DOCUMENTATION. The test documents, prepared for FAA approval, will be

updated and submitted to support each of the different software development phases.

a. System Test Plan. The system test plan (SIP) will serve as the overall test

control document for the contractor’s ARTS IIIA MCI test program. The plan will describe

the contractor’s test approach to verify all requirements described in the requirements

analysis effort. Also included will be plans for conducting full qualification testing (FQT),

software stress testing, and plans for integrating CSCI’s with other configuration items. The

test plans will include a specification compliance matrix that clearly states the procedure to

be used for requirements verification. Detailed planning will be provided to address factory

acceptance test as the final phase of DT&E, formal FAA Technical Center OT&E, system

integration/and shakedown test, and site test. The test plans will be revised prior to critical

design review and test readiness review (TRR).

Chap 8

Par 80 Page 39
6190.15 217194

b. System Test Procedures. The system test procedures (STPR) developed prior to

critical design review contain the test cases necessary to petiorm FQT of a CSCI identified

in the SIP. The STPR’s developed prior to TRR will be revisions of earlier STPR’s.

c. Test Report(s). The system test reports (STR) provide records of the FQT

performed on the CSCI’s.

d. System OxAte Test Procedures. The system on-site test (SOST) procedure

documents prepared by the contractor define the minimum requirements for the system,

subsystem, and unit test procedures. This document will include such items as test objectives, manning responsibilities, test support hardware and software, detailed test operations,

instructions, and the requirement and procedures for the reduction and analysis of test data.

e. OT&E/Integration Test Plan. ACN-1OOE will be responsible for developing this

test document. The OT&E/integration test plan will specify the approach that will be used to

verify that the ARTS IIIA MCI standardized baseline functions in accordance with the

requirements stated in the SRS and that the ARTS IIIA operational baseline can successfully

replace the existing ARTS IIIA software. The OT&E/integration tests will include operational tests and interface tests, and will include scenarios and operational simulations that will

verify the operational suitability and operational effectiveness of the ARTS IIIA MCI

operational baseline software in the NAS environment. Various levels of testing will be

conducted at the FAA Technical Center and at the operational site(s).

f. OT&E Shakedown Test Plan. The Operational Support Service, National

Terminal Engineering Division (AOS-400) will be responsible for developing the plan and

procedures for verifying the systems’ operation in an NAS operational environment. OT&E

shakedown testing will confirm that all requirements are met.

82. DT&E

a. DT&E to Date. DT&E dry run testing and formal system testing of the MCI

standardized baseline has been completed at the FAA Technical Center.

b. Future DT&E. The contractor will conduct additional DT&E activities as

described in FAA-STD-026/DOD-STD-2167A in the course of the operational baseline

software development. The contractor will conduct an operational baseline TRR prior to

CSCI integration testing.

(1) DT&E Objectives. These tests will confirm that the CSCI’s interface

with each other and that the functionality of the CPFS’s meet the requirements as stated in

the SRS; that changes in functionality are those expected from the incorporation of case files

Page 40

Chap 8

Par 81
217194 6190.15

identified for the ARTS IIIA standardized or operational baseline; and that there has been no

significant degradation in system performance. ARTS IIIA operational baseline software will

be demonstrated at the CSCI level at the FAA Technical Center as the final phase of DT&E.

(2) DT&E Events/Scope of Testing/Basic Scenarios. The DT&E phase of

this upgrade, performed by the contractor, begins with informal module testing and continues

through component testing for both the standardized and operational baselines. These tests

may be performed on individual modules, components, or combinations of these entities.

Formal DT&E follows the TRR with CSCI testing and is scheduled to end at the completion

of contractor acceptance testing.

c. Critical DT&E

(1) Testing

(2) Testing

Items

memory requirements.

performance requirements of the IOPB.

83. OT&E INTEGRATION TESTING. OT&E integration testing, the responsibility of

ACN, will verify that the software meets the NAS integration requirements when the

operational environment includes a complete system configuration consisting of all ancillary

components and connectivity to external systems. Integration activities will be conducted at

the FAA Technical Center and the operational baseline integration activities will also be

conducted at a site to be selected and may be combined with OT&E.

a. OT&E Integration Testing to Date. No ARTS IIIA MCI OT&E integration

testing has been performed to date.

b. Future OT&E Integration Testing.

(1) OT&E Integration Testing Objectives

(2)

OT&E integration. 1

a. Test system performance end-to-end.

b. Test subsystem level of conformance to requirements.

c. Establish NAS baseline performance for the operational baseline.

d. Verify no NAS performance degradation.

OT&E Integration Testing Events/Scope of Testing/Basic Scenarios.

testing will be accomplished on at least two levels. At the FAA Technical

Chap 8

Par 82 Page 41
6190.15 217194

Center, the baseline system will be tested in either a simulated or actual ATC environment

by FAA Technical Center personnel. Upon satisfactory testing of the operational baseline at

the FAA Technical Center, the software will be installed at selected sites and tested by the

Terminal Field Support Branch, AOS-410. After system acceptance testing at the sites, the

system will be further tested by site personnel. Site testing includes integration into the NAS

to assure that an accurate, realistic test scenario is obtained.

c. Critical OT&E Integration Testing Items. No critical NAS integration issues

have been identified.

84. OT&E OPERATIONAL TESTING. The OT&E operational testing will verify the

software’s operational effectiveness and suitability requirements when the operational

environment includes a complete ARTS IIIA MCI system configuration connected to external

systems. OT&E operational testing may be combined with OT&E integration testing and

will be conducted at the FAA Technical Center and at the various sites upon installation of

the operational baseline.

a. OT&E Operational Testing to Date. No ARTS IIIA OT&E operational testing

has been performed to date.

b. Future OT&E Operational Testing. The ARTS IIIA operational baseline system

will be tested at the FAA Technical Center to verify suitability, supportability, and maintainability. The operational baseline system will be site adapted and tested at the FAA Technical

Center and at the specific sites where it is to be installed.

(1) OT&E Operational Testing Objectives. Testing will be conducted to

prove the operational effectiveness and suitability of software with user participation.

Testing will include:

a.

b .

c.

Reliability and availability.

Degraded operations and operational utilization scenarios.

NAS loading and stress testing of all inter-operable subsystems.

(2) OT&E Operational Testing Events/Scope of Testing/Basic Scenarios.

The OT&E operational testing event/scope of testing/basic scenarios will be developed during

the OT&E phase of the program.

c. Critical OT&E Operational Testing Items. None identified at this time.

Page 42

Chap 8

Par 83
217194 6190.15

85. PAT&E. The ARTS IIIA MCI system will use hardware which has been thoroughly

tested and accepted as a non-developmental item (ND& With the assumption that PAT&E is

performed on serially produced equipment only, no PAT&E testing will be performed.

a. NAS PAT&E to Date. The ARTS IIIA MCI hardware has been tested and

accepted as NDI. There is no requirement for software PAT&E.

b. Future NAS PAT&E. Not applicable.

(1) NAS PAT&E Objectives. Not applicable.

(2) NAS PAT&E Events/Scope of Testing/Basic Scenarios. Not applicable.

c. Critical NAS PAT&E Items. None identified at this time.

86. OT&E SHAKEDOWN TESTING. The responsibility for the creation of the OT&E

shakedown test plan is assigned to AOS. The OT&E for both the standardized and operational baselines will be conducted in accordance with policies and Order 1810.4B and

procedures described in Order 1320.48. OT&E shakedown testing is conducted to exercise

the system in an operational environment to determine the suitability and maintainability of

the ARTS IIIA MCI system. The operational and functional requirements of both baselines

of the ARTS IIIA software will be tested at the FAA Technical Center and for the operational baseline at a site to be upgraded. The testing will be directed by AOS-410.

a. OT&E Shakedown Testing. Initial ARTS IIIA MCI OT&E shakedown testing of

the software will be performed by AOS-410 at the FAA Technical Center. OT&E shakedown testing at the sites to be upgraded involves system users in an operational environment

and will be directed by regional AF and AT division personnel using the operational

baseline.

(1) OT&E Shakedown Testing Objectives

a. Identify any risks associated with development and deployment of

the ARTS IIIA operational baseline software.

b. Identify any additional modifications required to the standardized

baseline software before it undergoes operational baseline software development.

C. Identify any additional modifications required to the operational

baseline software prior to going operational.

Chap 8

Par 85 Page 43
6190.15 217194

d. Identify issues that are critical to the operation and have an adverse

impact on the system.

(2) OT&E Shakedown Testing Events/Scope of Testing/Basic Scenarios.

None identified at this time.

b. Critical OT&E Shakedown Testing Items. None identified at this time.

87. OPERATIONAL READINESS DEMONSTRATION (ORD). The ORD determines

and establishes the date on which a facility is to be placed into operational use. To accomplish ORD, the facility must satisfy installation, performance, operation, and maintenance

criteria. The ORD is the culmination of the site shakedown activity. It formally documents

that the facility, system, and equipment are ready to support real time ATC tasks and the

readiness of personnel, procedures, hardware, software, and support services to support these

tasks.

NOTE: Special emphasis will be placed on software functions. Adequate testing and

possible modification of site adaptation data and system parameters require close coordination

of site and test personnel.

88. JOINT ACCEPTANCE AND INSPECTION. The joint acceptance and inspection

(JAI) activities shall be conducted in accordance with Order 6030.45, Facility Reference Data

File. Accordingly, a JAI board shall be established to ensure that each ARTS IIIA facility

meets specified requirements for operation and maintenance and has demonstrated that the

facility is ready to be commissioned. The joint acceptance board, when convened, may

include the following representatives:

a. The ANA-900 APME or his representative.

b. AF sector manager (or designated person).

c. Regional AT division representative.

d. AT facility manager (or designated person) from the involved facility.

e. Aviation Standards National Field Office, Flight Inspection Field Offices, or

the regional Flight Standards Division representatives as appropriate.

f. Logistics division representatives.

g Other representatives of the regional office, national headquarters, and the

FAA Technical Center, when so selected.

89. RESERVED.

Page 44

Chap 8

Par 86
217194 6190.15

CHAPTER 9. INTEGRATED LOGISTICS SUPPORT

90. MAINTENANCE CONCEPT.

a. Software Maintenance. The Terminal Field Support Branch, AOS-410, will be

responsible for the operational software (including site adaptation software and associated

documentation) and non-operational support software, including maintenance of diagnostic

software and the associated documentation upon delivery to the first site.

b. Technical Reporting. Software technic&l reporting is accomplished via program

technical reports (PTR). PTR’s are completed by the ARTS IIIA MCI sites and forwarded

to AOS-410 for operational software/non-operational support software and diagnostic

software, in compliance with paragraph 12 of Order 1100.134A. Patches for reported PTR’s

will be provided to all sites via either magnetic tape or floppy disks.

91. TRAINING. All training will be developed in accordance with FAA Standard 028B.

The contractor will conduct software training and cadre training for controller courses and

provide each course graduate with a certificate of training. All classes will be held at the

contractor’s facility and will utilize contractor furnished training equipment.

92.-99. RESERVED. .

Chap 9

Par 90 Page 45 (and 46)
217194

CHAPTER 10. ADDITIONAL PROJECT

100. CONFIGURATION MANAGEMENT.

6190.15

IMPLEMENTATION PLAN ASPECTS

The configuration management procedures

for the ARTS IIIA MCI project will follow established FAA procedures identified in Order

1800.8F, National Airspace System Configuration Management; and NAS-MD-001, NAS

Subsystem Baseline Configuration and Documentation Listing. Configuration management is

required during the life cycle of the system. The following further defines the configuration

management process.

.a. Software Configuration Management (SCM). Software refers to the operational, non-operational support, and diagnostic computer programs delivered at the time the

product baseline is established; i.e., system acceptance at the FAA Technical Center. ANA500 will assume configuration management responsibility until the software product baseline

is established. The Automation Software Division (ATR-200) will assume configuration

management responsibilities for operational software upon delivery to the first site.

AOS-400 will have configuration management responsibilities for support software.

b. Reviews and Audits. Configuration reviews and audits are conducted to verify

that the level of performance achieved for each subsystem at that point in the life cycle is as

specified. Reviews are the mechanisms by which the different levels of specification

documentation are examined and approved before proceeding with the development.

Configuration audits must verify documentation against previous baselines and added

changes, as well as compare the configuration against the approved configuration identification document.

101. COMMERCIAL SOFIWARE. There is no commercial off-the-shelf software

utilized in the A3.06 operational software; therefore, no requirement for any commercial

license. In the course of implementing A3.06, the disposal of any existing commercially

licensed software that becomes excess shall be accomplished in accordance with the procedures in Order 4800.2B.

102.409. RESERVED.

Chap 10

Par loo Page 47
CONTRACT MONTHS

PHASE 1 -ARTS IllA

STANDARDIZE BASELINE

REVIEWS/EVENTS

RQMT ANALYSIS

S/w DESIGN

PHASE 2 - MCI

STANDARDIZE BASELINE

REVIEWS/EVENTS

REQUIREMENT ANALYSIS

DESIGN

CODE/INTEGRATE

COIWRACTORTEST

FORMAL SYSlEMS TEST

PHASE 3 - OPERATIONAL

BASEUNE

REVlEWS/EVENlS

REQUIREMENT ANALYSIS

DESIGN

INTEGRATE/CODE

CONTRAW’ORTEST

FORMAL SYSTEMTEST/

SOST

KEWTE #I

KEYSlTE#2

KEYSlTE#3

NATlONAL RELEASE

WI-E INSTALLATIONS

1989

123

1990 1991 1992

JFMAMJJAS ONDiJFMAMJJAS OND JFMAMJJAS OND

456789111111111122222222 223333333333

012345678901234567 890123456789

A A

SRR SDWPDF’I

A

cm

ASSR TRRA

A

SSR

PDR

1993

FMAMJJAS ONE

444444444455

012345678901

AUM

FCAfPCA

1994 9 95

JFMAMJJAS OND JFMA

555555556666 6666

23456 78901 2 3 1567
2/7/94 6190.15

Appendix 2

APPENDIX 2. MCI HARDWARE DELIVERY SCHEDULE

Installation of processors to support MCI implementation will begin in April 1993 with

installation completed at all ARTS IIIA sites by March 1995. Operational software (A3.06

with MCI functionality) will be ready for installation in January 1994. It is estimated that six

months will be required to adapt, build, and test the program after delivery of hardware or

software, whichever is later. Full implementation should be completed approximately 21 A

months after national release.

SITE

H/W INSTALL

COMPLETE

Dallas 3/l l/93

Chicago 4/8/93

Houston 4130193

Dulles 5118193

Atlanta 6110193

Boston 6124193

National 712193

FAA Academy 819193

Oakland 915193

Detroit 915193

Tampa 1016193

Seattle 1016193

Ontario (1) 1016193

Providence 1 I/4/93

Miami 1 l/4/93

St Louis 1 l/4/93

Pittsburgh 1216193

Indianapolis 1216193

Memphis 1216193

Columbus 1216193

San Antonio l/6/94

Phoenix 116194

New Orleans 116194

Buffalo 216194

Cincinnati 216194

Milwaukee 316194

Dayton 316194

Fort Rucker 316194

Portland 416194

Nashville 416194

Charlotte 416194

Louisville S/5/94

Tucson s/5/94

SITE

ADAPTATION ORD

Key Site 1213 1193

6 Months 717194

Key Site 1213 1193

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 717194

6 Months 8/6/94

6 months 816194

6 Months 916194

6 Months 916194

6 Months 916194

6 Months 1016194

6 Months 1016194

6 Months 1016194

6 Months 1 l/5/94

6 Months 1115194

Page 1
6190.15

Appendix 2

SITE

HIW INSTALL

COMPLETE

Birmingham 515194

Salt Lake City 5126194

Tulsa 5126194

Omaha 5126194

Albuquerque 6123194

Rochester 6123194

Oklahoma City 6123194

Burbank (1) 7124194

Des Moines 7124194

Raleigh Durham 7124194

Albany 8123194

El Paso 8123194

Syracuse 8123194

Shreveport 9123194

Hartford 9130194

Sacramento lOl23l94

Orlando 10/30/94

San Juan 1 II23194

Minneapolis 1 l/30/94

Cleveland 12124194

Santa Ana (1) 12124194

Baltimore 12130194

Las Vegas l/23/95

San Diego (1) l/30/95

Honolulu 2122195

Jacksonville 2122195

Kansas City 2122195

Norfolk 3124195

Philadelphia 3124195

Los Angeles (1) 3124195

Denver 3124195

SITE

ADAPTATION m

6 Months 1 l/5/94

6 Months 11126194

6 Months 1 l/26/94

6 Months 1 l/26/94

6 Months 12123194

6 Months 12123194

6 Months 12123194

6 Months l/24/95

6 Months l/24/95

6 Months l/24/95

6 Months 2123195

6 Months 2123194

6 Months 2123195

6 Months 3123195

6 Months 3130195

6 Months 4123195

6 Months 4130195

6 Months 5123195

6 Months 5130195

6 Months 6124195

6 Months 6124195

6 Months 6130195

6 Months 7123195

6 Months 7130195

6 Months 8122195

6 Months 8122195

6 Months 8122195

6 Months 9124195

6 Months 9124195

6 Months 9124195

6 Months 9124195

217194

TRACON’s moving to Southern California TRACON.

SCT relocation commissioning dates:

Los Angeles 2194

Santa Ana 4194

Burbank 10194

OntUiO 4195

San Diego 9195

With the exception of Los Angeles, the relocated TRACON’s should commission on A3.06. The dates in this table are predicated on presently contracted

hardware delivery/installation schedules.

Page 2
217194 6190.15

Appendix 3

APPENDIX 3. MCI PROGRAM MILESTONES

Activitv Description Scheduled

Contract Award

System Requirements Review (SRR) (1)

System Design Review (SDR) (1)

Preliminary Design Review (PDR) (1)

Contract Modification (MCIIOP Baseline)

Critical Design Review (CDR) (1)

Software Specification Review (SSR) (2)

SDR/PDR (2)

Initial DRR Team Meeting

CDR (2)

MCI Hardware First Article Test

SSRISDRIPDR (3)

Test Readiness Review (TRR) (2)

Formal System Test Complete (2)

Functional/Physical Configuration Audit

(FCAIPCA) (2)

TRR (3)

CDR (3)

Formal System Test Complete (3)

FAA System On Site Test (SOST). (3)

FCAIPCA (3)

Key Site 1 Test (Dual Sensor)

DRR Executive Committee (Software Only)

Key Site 2 Test (Dual Sensor)

Key Site 3 Test (Single Sensor)

National Release A3.06

Date

Completed

9129189

4118190

8115190

8115190

9l3Ol90

2127191

2127191

8121191

10/10/91

10/30/91

3110192

9110192

9/l l/92

1216192

312193

5125193

6122193

7128193

9117193

1 l/19/93

1213193

1217193

12117193

l/14/94

l/28/94

NOTES: (1) Phase 1 - ARTS IIIA Standardized Baseline

(2) Phase 2 - MCI Standardized Baseline

(3) Phase 3 - Operational Baseline (A3.06)

Page 1
217194

AEA Region Program Manager

Mr. Roger Hutchinson (AEA-421)

FAA Regional HQ - AEA

JFK International Airport

Fitzgerald Federal Building

Jamaica, NY 11430

ACE Region Program Manager

Mr. Douglas Edwards (ACE-425)

FAA Regional HQ - ACE

601 East 12th street

Kansas City, MO 64106

AAL Region Program Manager

Mr. Robert C. Knosalla (AAL-421C)

FAA Regional HQ - AAL

222 West 7th Avenue

Anchorage, AK 99513

ANE Region Program Manager

Mr. Bruce Ng (ANE-422)

FAA Regional HQ - ANE

12 New England Executive

Burlington, MA 0 1803

AWP Region Program Manager

6190.15

Appendix 4

718-553-0015

816-426-5676

907-271-53 12

Mr. John Shea (AWP-422.42)

FAA Regional HQ - AWP

1500 Aviation Blvd.

Hawthorne, CA 90009

617-238-7434

Park

3 10-297-1079

Page 1
6190.15

Appendix 4

217194

ANM Program Manager

Mr. Darby Curran (ANM-422T2)

FAA Regional HQ - ANM

Airway Facilities Div.

1601 Lind Ave., SW

Renton, WA 98055-4056

AGL Program Manager

Mr. Orlando Alers (AGL-42 1.9)

FAA Regional HQ - AGL

2300 East Devon Avenue

Des Plaines, IL 60018

ASW Program Manager

Mr. Gary Galbraith (ASW-429.3)

FAA Regional HQ - ASW

2601 Meacham Blvd

Fort Worth, TX 76193-0429

AS0 Program Manager

Mr. Paul Smith (ASO-420A.2)

FAA Regional HQ - AS0

1701 Columbia Ave

College Park, GA 30337

Program Manager for Terminal Automation, ARTS III

Mr. Mitchell J. Narins (ANA-500)

800 Independence Avenue, SW

Washington, DC 2059 1

Deputy Program Manager for Terminal Automation, ARTS III

Ms. Sandy Hershey (ANA-501)

800 Independence Avenue, SW

Washington, DC 2059 1

206-227-2434

3 12-694-7584

8 17-222-4293

404-305-6289

202-287-2790

202-287-7000

Page 2
217194 6190.15

Appendix 4

Business Manager for Terminal Automation, ARTS III

ARTS IIIA MCI Associate Program Manager for Engineering

Mr. 0. D. Crosse (ANA-920)

800 Independence Avenue, SW

Washington, DC 20591

ARTS IIIA ISP Associate Program Manager for Engineering

Ms. Sandy Hower (ANA-502)

800 Independence Ave. SW

Washington, DC 20591

Mr. Herbert Greenberg (ANA-950)

800 *Independence Avenue, SW

Washington, DC 20591

Associate Program Manager for Contracts/Contracting

Officer

Mr. Joseph M. Carey (ASU-350D)

800 Independence Avenue, SW

Washington, DC 2059 1

Associate Program Manager for General Counsel

Mr. Vincent Salgado (AGC-520)

800 Independence Avenue, SW

Washington, DC 2059 1

Associate Program Manager for Requirements

Ms. Heather Leonard (ATR-120.5)

800 Independence Avenue, SW

Washington, DC 20591

Associate Program Manager for Logistics

Mr. Bill Howard (AML-500)

800 Independence Avenue, SW

Washington, DC 2059 1

202-287-2793

202-287-2767

202-287-2766

202-267-3689

202-267-3 126

202-267-9175

202-267-8737

Page 3
6190.15

Appendix 4

Associate Program Manager for Testing

Mr. Ernest Heinz (ACN-1OOE)

Federal Aviation Administration

Technical Center

Atlantic City Int’l Airport, NJ 08405

Associate Program Manager for System Engineering . Mr. Michael McVeigh (ASE-12 1)

800 Independence Avenue, SW

Washington, DC 20591

Associate Program Manager for Procedures

Ms. Ann Brenden (ATP-120)

800 Independence Avenue, SW

Washington, DC 2059 1

Associate Program Manager for Airway Facilities/

Platform Manager, ATCTITRACON

Mr. Phil Shelstad (ANS-240)

800 Independence Avenue, ‘SW

Washington, DC 2059 1

Associate Program Manager for Quality

Mr. Frank Bachelor (ASU-425)

FAA-QRO

c/o UNISYS Corp., MIS 148

BOX6000

Clearwater, FL 34618

Automation Software

Mr. William Smith (ATR-211)

800 Independence Avenue, SW

Washington, DC 2059 1

217194

609-485-68 19

202-287-7115

202-267-9329

202-267-8582

8 13-854-7483

202-267-7088

Page 4
217194

Contracting Specialist

Ms. Sarah Engley (ASU35OD)

800 Independence Avenue, SW

Washington, DC 20591

FAA Technical Center Shakedown Testing

Mr. James Hanna (AOS-413)

Federal Aviation Administration

Technical Center

Atlantic City Int’l Airport, NJ 08405

Technical Coordinator Terminal Field Support

Mr. Pete Quartxaro (AOS 410.1)

Federal Aviation Administration

Technical Center

Atlantic City Int’l Airport, NJ 08405

Training Requirements - Air Traffic

Mr. Mike White (ATZ-110)

800 Independence Avenue, SW

Washington, DC 2059 1

Training Requirement - Technical

Mr. Larry Battle (ASM-250)

800 Independence Avenue, SW

Washington, DC 20591

Training-Maintenance, operations (Air Traffic)

Ms. Kathy Smith (AHT-500)

800 Independence Avenue, SW

Washington, DC 20591

Training-Technical

Ms. Jane May (AHT-400)

800 Independence Avenue, SW

Washington, DC 2059 1

6190.15

Appendix 4

202-267-7377

609-485-4338

202-366-1826

202-267-7892

202-366-7765

202-366-7024

Page 5
6190.15

Appendix 4

FAA Academy

Mr. Russ Davoren (AMA-551)

Mike Monroney Aeronautical Center

6500 South MacArthur

P.O. Box 25082

Oklahoma City, OK 73125

FAA Logistics Center

Mr. Jerald Wolf (AML-462)

Mike Monroney Aeronautical Center

6500 South MacArthur

P.O. Box 25082

Oklahoma City, OK 73125

Air Traffic Operations

Mr. Robert Berlucchi (ATM-120.1)

800 Independence Avenue, SW

Washington, DC 20591

405-954-4312

405-954-5239

202-267-7814

217194

Page 6
217194 6190.15

Appendix 5

APPENDIX 5, LIST OF APPLICABLE DOCUMEWS

DTFAOl-89-C-00058 ARTS IIIA Enhancement Contract

Order 1100.134A

Order 1320.48

Order 1750.6A

Order 1800.8F

Order 1800.63A

Order 1810.4B

Order 4800.2B

Order 6030.45

Order 6190.14

FAA-STD-024B

FAA-STD.026

FAA-STD-028B

DOD-STD-2167A

MIL-STD-1521B

ARTS IIIA

NAS-MD-001

ATC 40012

Maintenance of National Airspace System Automation

Subsystems

Engineering Field Support Sector Maintenance Program Procedures, National Airway Engineering Field Support Sector, and

National Automation Engineering Field Support Sector

NAS Documentation Facility

National Airspace System Configuration Management

National Airspace System Deployment Readiness Review Program

FAA NAS Test and Evaluation Policy

Utilization and Disposal of Excess and Surplus Personal Property.

Facility Reference Data File

ARTS IIIA Interim Support Program Project Implementation Plan

Preparation of Test and Evaluation Plans and Test Procedures

National Airspace System Software Development

Contract Training Programs

Defense System Software Development

Technical Reviews and Audits for Systems, Equipment, and

Computer Software

Computer Program Functional Specification NAS MD-631

through for ARTS IIIA, Operational Program A3.05 NAS MD649 contained in A3.05 Site Bulletin 1, April 15, 1992

NAS Subsystem Baseline Configuration and Documentation Lising

Software Requirements specification, Update 03 (Operational

Baseline), Revision A

Page 1
217194 6190.15

Appendix 6

APPENDIX 6, ACRONYM LIST

The acronyms in this list are used within this document.

Acronym

AAP

AAS

ACN

AF

ALM

APM

APMC

APME

APML

APMP

MMQ

APMR

APMSE

APMT

ARTCC

ARTS

AT

ATC

BANS

BRITE

CA

CCB

CCD

CDR

CIP

c o

CPFS

CPU

CSCI

csc

csu

DBRITE

DECCO

DOT

DRR

DT&E

Definition

Advanced Automation Program

Advanced Automation System

Engineering, Test, and Evaluation Service

Airway Facilities

Requirements and Life Cycle Management

Associate Program Manager

Associate Program Manager for Contracts

Associate Program Manager for Engineering

Associate Program Manager for Logistics

Associate Program Manager for Procedures

Associate Program Manager for Quality

Associate Program Manager for Requirements

Associate Program Manager for System Engineering

Associate Program Manager for Test

Air Route Traffic Control Center

Automated Radar Terminal System

Air Traffic

Air Traffic Control

BRITE Alphanumeric Subsystem

Bright Radar Indicator Tower Equipment

Conflict Alert

Configuration Control Board

Configuration Control Decision

Continuous Data Recording

Capital Investment Plan

Contracting Officer

Computer Program Functional Specification

Computer Processing Unit

Computer System Configuration Item

Computer Software Component

Computer Software Unit

Digitial Bright Radar Indicator Tower Equipment

Defense Commercial Communication Office

Department of Transportation

Deployment Readiness Review

Development Test and Evaluation

Page 1
6190.15

Appendix 6

EPM Enhanced Performance Monitor

2/7/94

F&E

FAA

FCA

FDAD

FQT

Facilities and Equipment

Federal Aviation Administration

Functional Configuration Audit

Full Digital ARTS Display

Full Qualification Testing

GFP Government Furnished Property

ICA

ILSP

IO

IOC

IOPB

ISP

Interfacility Communication Adapter

Integrated Logistics Support Plan

Input/Output

Initial Operational Capability

Input Output Processor, Type B

Interim Support Program

JAI Joint Acceptance and Inspection

MCI

MOA

MSAW

Mode C Intruder

Memorandum of Agreement

Minimum Safe Altitude Warning

Master Test Plan

NAILS National Airspace Integrated Logistics Support

NAILSMT NAILS Management Team

NAS National Airspace System

NCP National Airspace System Change Proposal

ND1 Non-Developmental Item

NY New York

ORD

OPM

OST

OT&E

Operational Readiness Demonstration

Office of Personnel Management

Office of the Secretary of Transportation

Operational Test and Evaluation

PAT&E

PCA

PDSR

PIP

PM

POC

Production Acceptance Test and Evaluation

Physical Configuration Audit

Program Director’s Status Review

Project Implementation Plan

Program Manager

Point of Contact

Program Technical Report

QRO Quality Reliability Officer

Page 2
217194 6190.15

Appendix 6

RAPM

RETRACK

RDBM

RIG

SCIP

SCM

SETA

SOST

SRS

STP

STPR

STR

T&E

TELCO

TIG

TO

TOR

TPRC

TIMCON

VRTM

Regional Associate Program Manager

Retrack Processing

Remote Display Buffer Memory

Regional Integration Group

Surveillance Communication Interface Processor

Software Configuration Management

Systems Engineering and Technical Assistance

System Onsite Test

Sensor Receiver and Processor

Software Requirement Specification

System Test Plan

System Test Procedures

System Test Report

Test and Evaluation

Telephone Company

Terminal Integration Group

Technical Interchange Meeting

Technical Office

Technical Onsite Representative

Test Policy Review Committee

Terminal Radar Approach Control

Test Readiness Review

Verification of Requirement Traceability Matrix

Page 3