ASSC Section C.pdf

DTFAWA-12-C-00018A

P00005

AIRPORT SURFACE SURVEILLANCE CAPABILITY

(ASSC)

SECTION C: STATEMENT OF WORK

MAY 07, 2012

DTFAWA-12-C-00018A, P00005

PART I – SECTION C

STATEMENT OF WORK, May 7, 2012

C-2

REVISIONS SUMMARY PAGE

Date/ Rev Affected Sections Change 12/29/2011 All Contract Award Release 05/07/2012 All Replaced “FAA-E-XXXX” with “FAA-E-3021”

05/07/2012 2.2 FAA/DOT

Specifications, Standards, and Orders

Replaced “ASSC System Specification, Version 1.0” with “National Airspace System (NAS) Subsystem Level Specification for Airport Surface Surveillance Capability (ASSC)”

Deleted reference to FAA Order 1600.8F, Communications Security

(COMSEC)

Added references to FAA Order 6050.19F, Radio Spectrum Planning and FAA Order 6050.32B, Spectrum Management Regulations and Procedures Manual

05/07/2012 3.0 System Requirements

Replaced “ASSC Specification” with “National Airspace System (NAS) Subsystem Level Specification for Airport Surface Surveillance Capability (ASSC)”

05/07/2012 3.1.7.1 Data Items First paragraph, deleted “One hard copy of each deliverable shall be delivered to the ATO Data Manager.”

05/07/2012 3.2.3 Software Fifth and sixth paragraphs, replaced “The Contractor shall provide unlimited rights to the Government for all software and firmware integrated with the ASSC system under this contract. The Government shall have ownership and modification rights to all source code of all software and firmware used to satisfy the requirements of this SOW and ASSC system specifications, including all software and hardware support tools.

For standard commercial software employed to satisfy requirements, the Contractor shall submit corresponding commercial documentation, licensing agreements, and usage limitations to the Government for approval. The Contractor shall ensure that the Government has unrestricted access to additional copies of commercial software documentation.” with “The Government shall have rights to all software and firmware integrated with the ASSC system under this contract in accordance with Part II, Section I, Contract Clause 3.5-13, Rights in Data-General.”

05/07/2012 3.2.3.1.2 Software Design Description

Deleted last paragraph “For standard commercial product software employed to satisfy ASSC system requirements, corresponding commercial documentation, licensing agreements, and usage limitations shall be submitted to the Government for approval. The Contractor shall ensure that the Government has unrestricted access to additional copies of commercial software documentation.”

05/07/2012 3.2.3.1.4 Software Development Tools

First paragraph, replaced “The Contractor shall provide two (2) licensed copies of all commercial, non-commercial, developed/modified software development and support tools, and instructions necessary to power, set-up, configure, and optimize the ASSC. For Commercial Off-the-Shelf (COTS) and Non- Developmental Item (NDI) tools, executable code shall be provided.” with “The Contractor shall provide two (2) copies of all commercial, non-commercial, developed/modified software development and support tools, and instructions necessary to power, set-up, configure, and optimize the ASSC.

C-3

05/07/2012 3.2.3.1.4 Software

Development Tools

Added “All software used during the linking process shall be included in executable form. Software development tools used such as compilers, linkers, and libraries shall be included. Instructions for building the ASSC, Second Level Engineering Tools, and Simulation Computer software using the source code, software development tools, and executables mentioned above shall be included.

Flow charts and fully documented source code listings and object code for all Contractor-developed software and firmware shall be provided on DVD+R or CD ROM.”

05/07/2012 3.2.3.1.5 Software Programs

First paragraph, added new sentence “Software development files shall be included.”

05/07/2012 3.2.3.1.5 Software Programs

Deleted “The Government shall have ownership and modification rights to all source code of all software and firmware used to satisfy the requirements of this SOW and ASSC system specifications.”

05/07/2012 3.2.4.3 Hardware Identification and Selection

First paragraph, replaced “the ASSC specification” with “FAA-E- 3021”.

05/07/2012 3.2.6 Security Deleted bullet reference to FAA Order 1600.8F, Communications Security (COMSEC) and changed fourth paragraph from “ ...through the Physical and Communications Security Breach/Incident Report...” to “...through the Physical Security Breach/Incident Report...”

05/07/2012 3.2.7.3 Preliminary Design Review

Fifth paragraph, changed 32nd bullet from “Power consumption goals for each unit of the system” to “Power consumption goals for each component of the system.”

05/07/2012 3.2.7.4 Critical Design Review

Fifth paragraph, changed 35th bullet from “Power consumption goals for each unit of the system” to “Power consumption goals for each component of the system.”

05/07/2012 3.2.9 Interface Documentation

First paragraph, deleted “the ASSC specification”

05/07/2012 3.2.10 Reliability Program

Third bullet, replaced “Documenting all failures (hardware and software) in Program Trouble Reports (PTRs) and presenting these to the Government’s Reliability Review Board for decision based upon the FAA-HDBK-006A.” with “Documenting all failures (hardware and software) in Program Trouble Reports (PTRs), based upon FAA-HDBK-006A, and presenting their status at TIMs and PMRs.

05/07/2012 3.2.12 Electromagnetic Interference and Susceptibility

First paragraph, replaced “the ASSC specifications” with “FAA-E- 3021”.

C-4

05/07/2012 3.2.13 Spectrum

Compliance (New Section)

Added “The Multilateration Subsystem Sensor(s) shall operate in accordance with the Manual of Regulations and Procedures for Radio Frequency Management (47 Code of Federal Regulations (CFR) Part 300) and FAA Order 6050.19F, Radio Spectrum Planning.

Appropriate Facility Transmit Authorizations (FTA) shall be obtained from the Spectrum Engineering and Assignment Office prior to transmitting in accordance with FAA Order 6050.19F and FAA Order 6050.32B, Spectrum Management Regulations and Procedures Manual.

ASSC equipment data shall be provided to the FAA in support of the FAA's electromagnetic compatibility study in accordance with Order 6050.19F.”

05/07/2012 3.7.5.2.6.1.4 Software Maintenance Manual (SMM)

Replaced “SMM” with “Software Maintenance Manual (SMM)” (spelled out first occurence of acronym).

05/07/2012 3.7.6.1 Implementation

Replaced “DID TP-001” with “DID TP01” (corrected reference).

05/07/2012 3.8.3.1.4 First Article System Test

Last paragraph, changed “…power consumption of each unit in the Test Report, CDRL TE03.” to “…power consumption of each component in the Test Report, CDRL TE03.”

05/07/2012 3.9.3 Site Survey Entire section revised to consolidate pre-site survey and site survey activities for First Article and Production systems, and to update the sequence of contract deliverables.

05/07/2012 3.9.13 Contractor Acceptance Inspection

Second paragraph, replaced “The Contractor in conjunction with the Government shall perform a CAI using the CAI checklist in the ADP to confirm that the ASSC system is working properly and ready for SAT.” with “The Contractor in conjunction with the Government shall perform a CAI using the CAI checklist in the ADP to confirm that the ASSC system is working properly following successful completion of SAT.”

05/07/2012 4.7.7.2.2.1.2 Software Tools and Source Code

First paragraph, replaced “The Contractor shall provide one licensed copy of all software development tools identified in the SMM that were not delivered for the First Article.” With “The Contractor shall provide one copy of all software development tools identified in the SMM that were not delivered for the First Article per paragraph 3.2.3.1.5.”

C-5

05/07/2012 4.7.7.2.2.1.2

Software Tools and Source Code

Second paragraph, replaced “The Contractor shall provide source code, as updated to include changes described in Section 4.2.1, for all non-proprietary, Contractor generated ASSC operational support, including developmental, tools, Second Level Engineering Tools, Simulation Computer, and test support software including source code listings. The Contractor shall also provide all software programs used to develop required test data, technical design data, or documentation data.” with “The Contractor shall provide source code, as updated to include changes described in Section 4.2.1, for all ASSC operational support, including developmental, tools, Second Level Engineering Tools, Simulation Computer, and test support software including source code listings. The Contractor shall also update, as necessary, all software programs used to develop required test data, technical design data, or documentation data.”

05/07/2012 4.7.7.2.2.1.2 Software Tools and Source Code

Third paragraph, replaced “The Contractor shall identify the specific software components that are proprietary. All proprietary software used during the linking process shall be included in executable form.

Software development tools used such as compilers, linkers, and libraries shall be included. Instructions for building the ASSC, Second Level Engineering Tools, and Simulation Computer software using the source code, software development tools, and proprietary executables mentioned above shall be included.” with “All software used during the linking process shall be included in executable form.

Software development tools used such as compilers, linkers, and libraries shall be included. Instructions for building the ASSC, Second Level Engineering Tools, and Simulation Computer software using the source code, software development tools, and executables mentioned above shall be included.”

05/07/2012 4.9.1 Site Survey Section renamed “4.9.1 Site Survey (Optional Systems)” and revised to address optional MLAT and non-MLAT site survey activities and contract deliverables.

05/07/2012 4.9.4.5 Contractor Acceptance Inspection

Second paragraph, replaced “The Contractor in conjunction with the Government shall perform a CAI using the CAI checklist in the ADP to confirm that the ASSC system is working properly and ready for SAT.” with “The Contractor in conjunction with the Government shall perform a CAI using the CAI checklist in the ADP to confirm that the ASSC system is working properly following successful completion of SAT.”

05/07/2012 5.0 Glossary Deleted “COMSEC Communications Security”

C-6

TABLE OF CONTENTS

1.0 OVERVIEW

2.0 APPLICABLE DOCUMENTS

2.1 MILITARY STANDARDS AND SPECIFICATIONS

2.2 FAA/DOT SPECIFICATIONS, STANDARDS, AND ORDERS

2.3 OTHER PUBLICATIONS AND SPECIFICATIONS

3.0 SYSTEM REQUIREMENTS

3.1 PROGRAM MANAGEMENT

3.1.1 Program Management Organization

3.1.2 Program Management Plan

3.1.3 Contractor Work Breakdown Structure (CWBS)

3.1.4 Risk Management

3.1.5 Performance Analysis and Reporting

3.1.6 Integrated Master Schedule

3.1.7 Data Management

3.1.8 Meetings, Program Reviews and Conferences

3.2 SYSTEMS ENGINEERING

3.2.1 Systems Engineering Management Plan

3.2.2 Metrics

3.2.3 Software

3.2.4 Hardware Manufacture, Assembly and Test

3.2.5 System Engineering Requirements

3.2.6 Security

3.2.7 Technical Reviews

3.2.8 System Problem Report (SPR)

3.2.9 Interface Documentation

3.2.10 Reliability Program

3.2.11 Maintainability Program

3.2.12 Electromagnetic Interference and Susceptibility

3.2.13 Spectrum Compliance

3.3 QUALITY ASSURANCE

3.4 ENVIRONMENT, OCCUPATIONAL SAFETY AND HEALTH (EOSH)

3.4.1 System Safety Program

3.5 CONFIGURATION MANAGEMENT PROGRAM

3.5.1 Configuration Management

3.5.2 Configuration Identification

3.5.3 Configuration Baselines

3.5.4 Configuration Control

3.5.4.1 Engineering Change Proposal

3.5.4.2 Request for Deviation

3.5.4.3 Request for Waiver

3.5.4.4 Parts Substitution

3.5.5 Configuration Audits

3.6 HUMAN FACTORS

3.6.1 System Guidelines

3.7 INTEGRATED LOGISTICS SUPPORT

3.7.1 ILS Program Management

3.7.2 Maintenance

3.7.3 Supply Support

3.7.4 Support and Test Equipment List

3.7.5 Technical Data

3.7.6 Training and Training Support

C-7

3.7.7 Contractor Support and Services

3.8 TEST AND EVALUATION

3.8.1 Test Program Description

3.8.2 Test and Evaluation Management

3.8.3 ASSC Test Program

3.8.4 Test Equipment

3.8.5 Operational Test & Evaluation (OT&E)

3.9 DELIVERY, INSTALLATION AND CHECKOUT

3.9.1 Site Adaptation Description

3.9.2 Site Optimization

3.9.3 Site Survey

3.9.4 Site Preparation

3.9.5 Delivery of ASSC Units

3.9.5.1 Delivery of ASSC Displays

3.9.6 System Installation

3.9.7 Damage to Site

3.9.8 Contractor Use of Premises

3.9.9 Security Requirements

3.9.10 Installation Spare/Repair Parts

3.9.11 Miscellaneous Services

3.9.12 Acceptance Data Package (ADP) / Site Adaptation Description Document (SADD)

3.9.13 Contractor Acceptance Inspection

3.10 ENGINEERING SERVICES

3.10.1 Engineering Task Assignments

4.0 PRODUCTION SYSTEM REQUIREMENTS

4.1 PROGRAM MANAGEMENT

4.1.1 Program Management Organization

4.1.2 Program Management Plan

4.1.3 Risk Management

4.1.4 IMS

4.1.5 Data Management

4.1.6 Meetings, Program Reviews and Conferences

4.1.7 Program Management Reviews

4.1.8 Performance Analysis and Reporting

4.2 SYSTEMS ENGINEERING

4.2.1 System Modifications

4.2.2 Software Modifications

4.2.3 Parameter Adaptation

4.2.4 System Problem Report

4.2.5 Technical Interchange Meetings

4.2.6 Failure Reporting, Analysis, and Corrective Action

4.2.7 System Refresh and Upgrade

4.3 QUALITY ASSURANCE

4.4 INFORMATION SYSTEMS SECURITY (ISS) AND SAFETY

4.5 CONFIGURATION MANAGEMENT PROGRAM

4.5.1 Configuration Management

4.5.2 Configuration Identification

4.5.3 Configuration Baselines

4.5.4 Configuration Control

4.5.5 Engineering Change Proposal

4.6 MANUFACTURE, ASSEMBLY, AND TEST

4.7 INTEGRATED LOGISTICS SUPPORT (ILS)

4.7.1 ILS Management

4.7.2 Maintenance

C-8

4.7.3 Supply Support

4.7.4 Support and Test Equipment List

4.7.5 Technical Data

4.7.6 Training and Training Support

4.7.7 Contractor Support and Services

4.8 TEST AND EVALUATION

4.8.1 MTP

4.8.2 Production First Unit Regression Test

4.8.3 FAT

4.8.4 SAT

4.9 DELIVERY, INSTALLATION AND CHECKOUT

4.9.1 Site Survey (Optional Systems)

4.9.2 Site Preparation

4.9.3 Delivery of ASSC Units

4.9.3.1 Delivery of ASSC Displays

4.9.4 System Installation

5.0 GLOSSARY

C-9

1.0 Overview

The Statement of Work (SOW) includes provisions for program management, systems engineering, system test and evaluation, implementation, training, delivery, installation, integrated logistics support, and operational support for nine (9) Airport Surface Surveillance Capability (ASSC) Systems, and any options exercised by the Government.

For the purposes of this SOW, references to “days” mean calendar days, unless otherwise specified.

2.0 Applicable Documents

The following specifications, handbooks, orders, standards, and drawings form a part of this SOW and are applicable to the extent specified herein. The latest version of these documents as of the contract date shall apply. In the event of conflict between this SOW and any of the applicable documents cited below, the provisions of this SOW shall apply.

a. Copies of FAA specifications and interface documents may be obtained from the Federal Aviation Administration, Headquarters Public Inquiry Center APA-230, 800 Independence Avenue SW, Washington, DC 20591, 202-267-3484. Requests should fully identify material desired and cite the solicitation or contract number.

b. Requests for copies of documents not covered in the preceding paragraph should be addressed to the Contracting Officer (CO). Requests should fully identify material desired and cite the solicitation or contract number.

c. Military Standards and Specifications can be ordered from the Department of Defense Single

Stock Point (DODSSP), Building 4/Section D, 700 Robbins Avenue, Philadelphia, PA 19111- 5098. Information is available at their website, http://dodssp.daps.dla.mil.

d. Copies of ANSI/ASQC-Q9001-2008 and ISO 9000-3:2004 can be obtained from the following source: American Society for Quality Control P.O. Box 3005, Milwaukee, WI 53201-3005 or 600 North Plankinton Avenue, Milwaukee, WI 53203 Phones: (414) 272-8575 or (800-984)- 4323. The Fax is: (414) 272-1734.

e. Copies of the Acquisition Management System Test and Evaluation Process Guidelines are available in the FAA Acquisition System Toolset (FAST). The on-line internet address of FAST is: http://FAST.faa.gov.

2.1 Military Standards and Specifications

MIL-HDBK-61A Configuration Management Guidance MIL-HDBK-470A Designing and Developing Maintainable Products and Systems, Volumes I and II MIL-HDBK-781A Reliability Test Methods, Plans, and Environments for Engineering Development, Qualification, and Production MIL-HDBK-217F Reliability Prediction of Electronic Equipment MIL-PRF-49506 Logistics Management Information MIL-PRF-28000B Digital Representation for Communication of Product Definition Data: IGES Application

Subsets and IGES Application Protocols MIL-DTL-31000C Technical Data Packages

MIL-STD-129P Military Marking

MIL-STD-1189 Bar Code Symbology

C-10

2.2 FAA/DOT Specifications, Standards, and Orders

FAA-HDBK-006A Reliability, Maintainability, and Availability (RMA) Handbook FAA-E-3021 National Airspace System (NAS) Subsystem Level Specification for Airport

Surface Surveillance Capability (ASSC) FAA-E-2942 Airport Surface Detection Equipment - Model X (ASDE-X) Specification, Version 2.0, Preliminary, August 27, 2009 FAA-E-2943b ASDE-X Visual Specification for Airport Surface Applications (VSASA) DOT/FAA/HFDS 2003 Human Factors Design Standard DOT-VNTSC-FAA-95-3 Human Factors in the Design and Evaluation of Air Traffic Control Systems FAA Order 3900.19B Occupational Safety and Health FAA Order 3900.57 FAA Pre-Construction and Maintenance Project Safety and Health Checklist FAA Order 1050.1E Policies and Procedures for Considering Environmental Impacts FAA Order 1600.72A Contractor and Industrial Security Program FAA Order 1600.75 Protecting Sensitive Unclassified Information FAA Order 6950.2C Electrical Power Policy Implementation at National Airspace System Facilities FAA Order 1050.10C Prevention, Control and Abatement of FAA Environmental Pollution FAA Order 1050.20A Airway Facilities Asbestos Control Program FAA Order 1050.14A Polychlorinated Biphenyls (PCBs) in the National Airspace System (NAS) FAA Order 1050.17 Airway Facilities Environmental and Safety Compliance Program FAA Order 1050.18 Chlorofluorocarbons and Halon Use at FAA Facilities FAA Order 1053.1A Energy and Water Management Program for FAA Buildings and Facilities FAA Order 4600.27A Personal Property Management FAA Order 1800.66 Configuration Management Policy

FAA-D-2494B

Technical Instruction Book Manuscript: Electronic, Electrical, & Mechanical Equipment Requirements for Preparation of Manuscript & Production of Books

FAA-G-2100H Electronic Equipment, General Requirements FAA-STD-028C Contract Training Program FAA-STD-021A Configuration Management FAA-STD-025F Preparation of Interface Control Documentation FAA-STD-026A NAS Software Development, June 1, 2001 FAA-STD-019E Lightning and Surge Protection, Grounding, Bonding and Shielding Requirements for Facilities and Equipment FAAD-STD-1293c Servicing Standards and Test Requirements for Ground Electronic Equipment FAA Order 1370.82A Information Systems Security Program FAA Order 6000.30C Policy for Maintenance of the National Airspace System FAA Order 6050.19F Radio Spectrum Planning FAA Order 6050.32B Spectrum Management Regulations and Procedures Manual SMS Manual FAA Safety Management System (SMS) Manual SRMGSA FAA Safety Risk Management Guidance for System Acquisitions HF-STD-001 Human Factors Design Standard N/A FAA Human Factors Job Aid

2.3 Other Publications and Specifications

ANSI/ASQC-Q9001-2008 American National Standard, Quality System-Model for Quality Assurance in Design, Development, Production, Installation, and Servicing ISO 9000-3:2004 International Standard, Quality Management and Quality Assurance

Standards - Part 3: Guidelines for the Application of ISO 9001 to the Development, Supply and Maintenance of Software

SP 800-53 (REV.3) NIST Special Publication, Recommended Security Controls For Federal Information Systems And Organizations - Information Security

ANSI/EIA-748 Earned Value Management System IEEE Standard 830-1998 IEEE Recommended Practice for Software Requirements Specifications

C-11

IEEE Standard 1016-1998 IEEE Recommended Practice for Software Design Descriptions IEEE Standard 1063-1987 IEEE Standard for Software User Documentation IEEE/EIA 12207-1996 IEEE/EIA Standard Industry Implementation of International Standard

ISO/IEC12207:1995 and (ISO/IEC 12207) Standard for Information Technology—Software life cycle processes

FED-STD-795 Uniform Federal Accessibility Standards OMB Circular A-130 Management of Federal Information Resources 29 CFR Labor 40 CFR Protection of the Environment 49 CFR Transportation National Environmental Policy Act (NEPA) of 1969

National Fire Protection Association Code 70. Current edition: 2008

National Fire Protection Association Code 780 Current edition: 2011

Standard for Installation of Lightning Protection

National Fire Protection Association (NFPA) 70E, Electrical Safety in the Workplace

Federal Air Regulation, 14CFR, Part 77

Airport Design Standards Advisory Circular, AC-150-5300-13

Executive Order 12699 Seismic Safety of Federal and Federally Assisted or Regulated New Building Construction

Executive Order 12941 Seismic Safety of Existing Federally Owned or Leased Buildings Executive Order 13423 Strengthening Federal Environmental, Energy, and Transportation

Management Executive Order 13514 Federal Leadership in Environmental, Energy, and Economic Performance OSHA Act of 1970 Clean Air Act Clean Water Act Resource Conservation and Recovery Act (RCRA)

RTCA/DO-260B Minimum Operational Performance Standards for 1090 MHz Automatic Dependent Surveillance – Broadcast (ADS-B)

RTCA/DO-282B Minimum Operational Performance Standards for Universal Access Transceiver (UAT) Automatic Dependent Surveillance – Broadcast

RTCA/DO-278 DO-278/ED-109 Software Standard for Non-Airborne Systems

3.0 System Requirements

The Contractor shall produce a First Article ASSC system at San Francisco International Airport, such that all requirements in the SOW, National Airspace System (NAS) Subsystem Level Specification for Airport Surface Surveillance Capability (ASSC) (FAA-E-3021), and FAA-E-2943b are satisfied.

The Contractor shall produce, integrate, test, deliver, install, checkout, and adapt, and optimize the First Article system. The system shall include all hardware, software, firmware, interfaces, commercial and non-commercial licenses, special support and test equipment, delivery installation, integration, and

C-12 checkout. During First Article, the Contractor shall be responsible for all site level maintenance until the Government accepts the system.

The Contractor shall also produce/procure one full production system with the minimal number of Multilateration Subsystem Sensors (MSS) necessary to support Government factory tests, second level engineering, and Contractor Depot Logistics Support (CDLS). The production system shall satisfy the same requirements as the First Article system.

3.1 Program Management

3.1.1 Program Management Organization

The Contractor shall establish and maintain a formal organization to manage this contract and subcontracts. The Contractor shall develop and implement a management program to efficiently and effectively execute the requirements of this contract to include the following: program control, quality assurance, configuration management, integrated logistics support, subcontract management, management of Government furnished resources, risk management, and security.

The Contractor shall assign a designated Program Manager (PM) to manage this effort. The PM shall be the point of contact between the FAA and the Contractor in the execution of this program and shall be prepared at all times, given reasonable notice, to present and discuss with the FAA the status of contract activities.

3.1.2 Program Management Plan

The Contractor shall develop and implement an integrated Program Management Plan (PMP). The PMP shall integrate all functional areas identified: system engineering, engineering data and specifications, software engineering, configuration management, quality assurance, integrated logistics support, training, and implementation, and shall articulate the specific objectives to be accomplished. The PMP shall specify the work tasks, at an overview level, required to meet the ASSC objectives. The PMP shall include the Contractor’s risk management, configuration management, and systems engineering management plans and processes. The PMP shall also discuss the staffing and other resources required to meet contract requirements.

CDRL PM01 Program Management Plan

3.1.3 Contractor Work Breakdown Structure (CWBS)

The Contractor shall prepare the Contractor Work Breakdown Structure (CWBS) based on the Acquisition Management System (AMS) Work Breakdown Structure (WBS), Sections 3 and 4, as described in FAST at: http://FAST.faa.gov.

The Contractor shall maintain and update the CWBS to a minimum level 3 unless otherwise specified.

The CWBS shall be developed by the Contractor to reflect the manner in which the work will be accomplished on the contract and to map to the FAST WBS Sections 3 and 4.

There shall also be available a correlation matrix that shows the mapping between the CWBS and the functional Organization Breakdown Structure (OBS). This correlation matrix shall enable reporting of cost, schedule, and technical performance and task responsibilities by either WBS or OBS elements if necessary.

CDRL PM02 Contractor Work Breakdown Structure

C-13

3.1.4 Risk Management

The Contractor shall identify cost, schedule, and technical risks and describe how they will effectively manage these risks throughout the performance of this contract. The Contractor shall quantify risks with respect to the impact on all aspects of the management of this contract, including, but not limited to, development, integration, manufacture, test, installation, performance, schedule, and cost. The Contractor shall identify risks and assign a priority for developing a recommended course of action to mitigate against these risks. The Contractor shall develop and maintain a risk management plan in accordance with (IAW) CDRL PM01 that identifies, analyzes, and classifies program risks. Program risks shall be classified as low, medium, or high priority. The Contractor shall identify risk management techniques and shall define risk mitigation plans for medium and high priority risks. Identification of risk, with the associated required mitigation plans shall be an attachment to the PMP. The Contractor shall provide updates to the risk analysis status and risk mitigation plans in the Program Management Reviews (PMR).

3.1.5 Performance Analysis and Reporting

The Contractor’s management methods and procedures shall ensure that they provide visibility into timely progress; reporting on contracted efforts for internal management; and information for Government oversight purposes. The management system shall also ensure reliable funds requirement forecasts. For all CLINs, the Contractor and any major subcontractors shall implement a cost and schedule performance measurement and reporting system and related management procedures. The system shall be the basis for all data reported on the modified “no criteria” Cost Performance Report (CPR) (CDRL PM03). The Contractor shall maintain the system and related procedures throughout the contract.

The Contractor shall establish the cost/schedule performance measurement baseline for all CLINs within 60 days after contract award. The Contractor shall use standard earned value practices IAW the EIA Standard “Earned Value Management System”, ANSI/EIA-748. The Contractor shall present cost/schedule performance by CWBS element at each subsequent PMR. Quarterly, the Contractor shall report cost and schedule activities at the OBS level (Section 3.1.3) at the PMRs in addition to the WBS reporting.

The CPR formats 1, 3, and 5 shall be used, or tailored, for reporting on all CLINs. The Funds and Man- Hour Expenditure Report (CDRL PM11) shall be used for reporting on time and material CLINs only.

CDRL PM03 Cost Performance Report CDRL PM11 Funds and Man-Hour Expenditure Report

3.1.6 Integrated Master Schedule

The Contractor shall develop an Integrated Master Schedule (IMS) based on the sequence of events required to accomplish the efforts required by this contract and the CWBS developed for this effort. The Contractor shall ensure that the IMS portrays an integrated schedule plan to meet the milestones and delivery requirements of this contract. The Contractor shall identify the specific milestones constituting the critical path and shall report on these at each PMR. The Contractor shall present the current version of the IMS at each PMR.

CDRL PM04 Integrated Master Schedule

3.1.7 Data Management

The Contractor shall establish a data management program to maintain contractually required documentation and correspondence; design, test, and production documentation; and other supporting documentation. This shall be done in one logical and inclusive system using ISO 9001/9000-3:2004, and

C-14

MIL-HDBK-61A as guidance. This effort shall include documentation involved with, but not limited to, the development, implementation, testing, schedule, and management of the equipment. This specifically shall include a process for monitoring, reporting, status accounting, and cross-matrixing of changes to, additions of, or deletions of data item deliverable contents. All data items shall be configuration-managed by the contractor.

The Contractor shall identify a single focal point for integrating and maintaining the total Contractor data management effort. When requested by the Government, the Contractor shall make available, for Government review, the internal documents used to design and manage the program.

3.1.7.1 Data Items

Data items referenced by their Contract Data Requirements List (CDRL) titles are to be performed IAW the CDRL of the same name. All data deliverables shall be prepared and delivered IAW the corresponding CDRL items specified under the SOW requirement. A cover letter for each deliverable shall be delivered to ATO. Electronic copies shall be distributed IAW block 14 of each CDRL sheet in place of hard copy. If a deliverable is not printable as a letter, legal, or ledger-size document, soft and hard copies should be delivered to every organization in block 14 on the 1423-1 sheet for that deliverable.

The Government will review all CDRL items to verify Contractor compliance with the system requirements specified herein, as well as with FAA-E-3021 and FAA-E-2943b. The Contractor shall track all document revisions and shall submit revised documents with revision marks. Revision marks shall be removed in the final delivery of documents unless otherwise stated. All documents shall be configuration managed.

The Contractor shall perform IAW all plans developed in response to this SOW and as approved by the Government. All references to the "Government" in this SOW shall mean by authority of the CO or designee. All CDRL items identified in this SOW shall be delivered to the Government in digital media compatible with the Microsoft Office suite of products, version 2003, VISIO, and Project, or PDF format, as well as hard copy unless superseded by specific CDRL instructions. The Contractor shall submit a Contract Data Status and Schedule report IAW CDRL PM05.

Government response to all CDRLs will be 30 days from the Government’s receipt of the CDRL, unless otherwise noted in the CDRL form. Designated Government personnel will be made available to work at the Contractor’s facility as needed during documentation development to provide early guidance in documentation content and to conduct in-process reviews as requested by the Contractor.

CDRL PM05 Contract Data Status and Schedule Report

3.1.8 Meetings, Program Reviews and Conferences

The Contractor shall conduct meetings and reviews IAW this SOW. At each management review, technical review, or audit, the Contractor shall provide backup data regarding assumptions made and methodologies used in arriving at specific recommendations or conclusions. The Contractor shall prepare and submit a meeting agenda, meeting minutes, and presentation materials for all meetings. The Contractor shall provide minutes, accompanied by a summary of action items and all presentation materials used, to the Government for approval. Management and technical reviews and audits shall not be considered complete until approval by the Government is granted in writing. The Contractor shall propose an overall strategy for conducting each set of reviews.

C-15

Meeting support provided by the Contractor shall include, but is not limited to, facilities, materials, office equipment, clerical personnel, technical data, and subcontractor participation (when requested by the Government).

CDRL PM06 Agenda CDRL PM07 Meeting Minutes

3.1.8.1 Post Award Conference

The Contractor shall plan for, host, support, and participate in a Post Award Conference to be held at the Contractor's site within one month after contract award. The FAA will determine the specific date within two (2) weeks after contract award. At this conference, the Contractor shall address the plans and schedules for the ASSC work efforts.

3.1.8.2 Program Management Reviews

The Contractor shall conduct and administratively support PMRs on a monthly basis during the period of performance of this contract. The PMRs shall be conducted at the Contractor's facility, or a Government designated location, and each PMR shall be no more than one day in duration. The PMR should be conducted approximately 5 working days after the monthly electronic submission of the CPR and IMS.

PMRs shall include a review of the CPR format 1 and IMS, and reasons for variances.

The Contractor shall present at each PMR for Government information, not approval, a log of all open and recently closed Contractor-internal System Problem Reports (SPR) including a brief description of each SPR.

The Contractor shall identify and deliver for Government approval, a set of Technical Performance Measurements (TPM) in a TPM Plan IAW CDRL PM08. The TPMs shall measure achievement and progress to date. Other requirements are:

TPMs (or parameters) shall be key indicators of program success.

TPM interrelationships shall be depicted by means of tiered dependency trees.

A time-phased value profile (with a tolerance band) shall be constructed for each TPM.

Each TPM shall be related to cost, performance, schedule, and risk.

The Contractor shall incorporate Government comments into their TPM Plan and shall present the Government approved TPMs at the third, and subsequent PMRs.

CDRL PM08 Technical Performance Measurements Plan

3.1.8.3 Integrated Baseline Review

The Contractor shall present the contents and underlying assumptions of its time-phased performance measurement baseline to the Government during an Integrated Baseline Review (IBR) at the Contractor’s facilities. The IBR shall ensure that appropriate reporting levels have been identified and variance thresholds agreed to by the Government and Contractor. The IBR shall be combined with a PMR, not later than the third PMR after contract award. The IBR shall include performance measurements for subcontractors. The Contractor shall also demonstrate that its CPR management procedures comply with the intent of the earned value management systems criteria of Paragraph A.1.c – Earned Value Management System (EVMS), ANSI/EIA-748, or FAST Toolbox Guidance T1.13 – Metrics and Performance Management during an on-site visit by the Government should non-compliance be detected during IBR or regular CPR surveillance. The Contractor may use “estimated Subcontractor actuals” in keeping with standard EVMS practices, however the Contractor shall explain, at the IBR, methods for

C-16 record keeping that ensure accuracy. The Contractor shall provide ongoing access during contract performance to pertinent records and data, which underlie and support the cost and schedule data reported.

3.2 Systems Engineering

The Contractor shall execute a systems engineering program for the definition, development, manufacture, verification, integration, and testing of the system. System engineering efforts shall consider all aspects of performance, quality, life cycle cost, maintainability, reliability, schedule, data processing reserves, and future growth requirements. The Contractor shall maintain effective control over the system engineering and design development process, including subcontract items and services, to ensure that cost, performance, and schedule are met, to provide early detection of problems, and to reduce risk. The Contractor shall specify a senior systems engineer with the authority to serve as point of contact (POC) for system engineering tasks.

3.2.1 Systems Engineering Management Plan

The Contractor shall develop a Systems Engineering Management Plan, as part of the Program Management Plan CDRL PM01 that describes the Contractor’s practices and procedures for functional analysis, the process for generating derived requirements, requirements allocation, traceability of requirements, and synthesis.

3.2.2 Metrics

The Contractor shall select, and upon receiving Government approval, utilize an application to measure and track the status of the following metrics. Software metrics shall be for Contractor-developed and modified software:

1) Project Cost and Schedule (Baseline)

2) Project Requirements (Stability Measure)

3) Software Development Progress

4) Requirements Validation Progress

5) System Problem Reports (SPR)

6) Earned Value Management (EVM)

7) Risk Management

The Contractor shall discuss the status of these metrics at each PMR.

CDRL PM09 Program Metrics Report

3.2.3 Software

The Contractor shall design, code, unit test, and integrate with the hardware the ASSC system software that is required for the approved design architecture, and shall use IEEE/EIA 12207 paragraphs 5.3, 6.2 and 6.3 in establishing a software development process, as well as DO-278.

Where requirements cannot be met by using commercially offered software packages, the Contractor shall develop the required computer software. The Contractor shall conduct unit tests on the developed code to ensure correctness prior to its integration with the hardware. The Contractor shall treat non-COTS firmware (software that resides on programmable memory or programmable arrays) as software.

The Contractor shall ensure that the software is IAW the manufacturer recommendations of the operating system and COTS applications and applicable industry standards to assure compatibility with future releases of the operating system and related COTS software applications.

C-17

The Contractor shall implement updates and revisions as they occur until the associated Test Readiness Review. The Contractor shall provide for the implementation of updates and revisions, as well as software-specific design descriptions and requirements, in the Software Design Description (SDD) IAW with CDRL SW03 (see section 3.2.3.1.2). The Contractor shall justify all modifications to commercial software to the Government. The Contractor shall include the method of documentation, alternatives reviewed, cost, schedule, and risk analysis in the justification. The Contractor shall obtain Government technical concurrence and approval in writing for any deviations.

The Government shall have rights to all software and firmware integrated with the ASSC system under this contract in accordance with Part II, Section I, Contract Clause 3.5-13, Rights in Data-General.

For all commercial computer software Contractor will provide only the standard commercial license as specified in the license customarily offered to the public. Should the standard commercial license not meet the Governments needs and should the Government require additional rights for said software, then Contractor and the Government will require a Specifically Negotiated License Rights Agreement

(SNLR).

The Contractor shall acquire/develop, document, test, and manage all system software provided or developed under this contract. The Contractor shall use IEEE/EIA 12207 paragraphs 5.3, 6.2 and 6.3 in establishing a software development process. The Contractor shall develop a Software Development Plan (SDP) IAW CDRL SW01 describing the process for managing and controlling the software development program.

CDRL SW01 Software Development Plan

3.2.3.1 Software Documentation

The Contractor shall provide the software documentation for requirements allocation, design, test, quality assurance, delivery, installation, operation, maintenance, and support of each computer program configuration item (CPCI) of Contractor-developed software. The Contractor shall submit all software documentation to the Government for review and approval.

The following sections describe the required software documentation to be provided by the Contractor.

3.2.3.1.1 Software Requirements Specification

The Contractor shall develop a Software Requirements Specification (SRS) IAW IEEE-Standard-830- 1998, Section 5 for each computer program configuration item (CPCI) and shall submit the same to the Government for review and approval.

CDRL SW02 Software Requirements Specification

3.2.3.1.2 Software Design Description

The Contractor shall develop a Software Design Description (SDD) document for each CPCI documented by an SRS and shall submit the same to the Government for review and approval. The SDD shall satisfy the requirements of IEEE Standard 1016-1998, Sections 5, 6 and Annex A.

The following guidelines shall apply:

Firmware (software that resides on programmable memory) shall be treated as software.

C-18

Commercially available operating systems used in the ASSC shall be Portable Operating System Interface (POSIX) compliant and be the most recent release or update.

ASSC software shall be IAW the operating system, COTS application manufacturer recommendations, and applicable industry standards.

Updates and revisions shall be implemented by the Contractor as they occur until the test readiness review. If the Contractor chooses to modify commercial software, he shall supply the justification for the change to the Government. The justification shall state alternatives reviewed, cost, schedule, risk analysis, and the method of documentation. All changes shall require Government approval.

CDRL SW03 Software Design Description

3.2.3.1.3 Software Version Description Document

The Contractor shall develop a Software Version Description (SVD) Document that will identify the exact physical configuration (version) of each CPCI contained within the ASSC. The SVD shall accompany the shipment of each Computer Software Configuration Item (CSCI) to the Government. The Contractor shall use and maintain a system that ensures that each CSCI change is accounted for, following approval by the Government. The SVD shall be updated as required to describe all changes to any CSCI version delivered subsequent to the initial CSCI delivery.

CDRL SW04 Software Version Description Document

3.2.3.1.4 Software Development Tools

The Contractor shall provide two (2) copies of all commercial, non-commercial, developed/modified software development and support tools, and instructions necessary to power, set-up, configure, and optimize the ASSC.

All software used during the linking process shall be included in executable form. Software development tools used such as compilers, linkers, and libraries shall be included. Instructions for building the ASSC, Second Level Engineering Tools, and Simulation Computer software using the source code, software development tools, and executables mentioned above shall be included.

Flow charts and fully documented source code listings and object code for all Contractor-developed software and firmware shall be provided on DVD+R or CD ROM.

CDRL SW05 Software Development Tools

3.2.3.1.5 Software Programs

The Contractor shall provide source code for all ASSC operational, support, training, and test software including source code listings and build instructions. The Contractor shall also provide all software programs used to develop required test data, technical design data, or documentation data. Software development files shall be included. In addition, the Contractor shall provide all software programs necessary to load, analyze, modify, reassemble, and reproduce the system's executable software and/or firmware.

CDRL SW06 Source Code

3.2.3.2 System Firmware

Computer programs and/or micro-programs that are loaded in a class of memory, e.g., Field- Programmable Gate Array (FPGA) or Programmable Logic Devices (PLD) that cannot be dynamically modified by the system or a computer during processing shall be considered firmware. For new

C-19 development work, since firmware consists of a composite of programs and memory, documentation of such memory shall be included. Related computer programs or micro-program(s) shall be provided with appropriate documentation for their understanding, implementation and modification. Contractor-developed firmware in this effort shall not reside in masked-programmed ROM's. Instructions on procedures required to replace and/or modify firmware elements shall be provided.

3.2.3.3 Software Engineering Practices

The Contractor shall use software engineering practices that result in the design, integration, test, and delivery of software to the Government that is correct, error-resistant, non-redundant, and maintainable.

The Contractor shall stress hierarchical structure, independence of components, modularity, and clarity of interconnections in the software design.

3.2.3.4 Programming Languages

The Contractor shall write all newly developed software in a higher order programming language technically acceptable to and approved by the Government. The Contractor shall obtain prior Government approval to use assembly language for new development. The Government will approve the use of assembly language only when the Contractor shows, to the satisfaction of the Government, that the use of assembly language is required to meet performance requirements.

3.2.3.5 Development of Support Software

The Contractor shall provide any support software such as simulation software, training software, test software and development/maintenance tools with documentation. This includes software used to test operational system software via system level simulations and developmental software used to create operational software and tools for maintaining operational software. Support software that is required for development, installation, test, support, maintenance or optimization of the ASSC system shall be subject to validation.

3.2.4 Hardware Manufacture, Assembly and Test

The Contractor shall procure/develop/manufacture, document, integrate, test, and manage all system hardware provided or developed under this contract. The Contractor shall employ best commercial practices as guidance for all hardware design. A system grounding design IAW FAA-STD-019E shall be used for all ASSC units.

The structural strength and rigidity of the cabinets, frame and consoles shall be such that normal handling in loading, shipping, unloading and setting into position for installation will not result in any damage to the equipment.

3.2.4.1 Hazardous Materials

The Contractor shall ensure that program equipment is delivered free of asbestos, polychlorinated biphenyls (PCBs), lead (except for lead-acid batteries, and lead-based solder on circuit boards if no acceptable substitute is available), mercury-containing equipment, any Class I ozone-depleting substances (ODSs), and some Class II ODSs (i.e., HCFC-22, HCFC-141b, and HCFC-142b), IAW relevant federal regulations and FAA Orders, including but not limited to: FAA Order 1050.10C, Prevention, Control, and Abatement of FAA Environmental Pollution, FAA Order 1050.20A, Airway Facilities Asbestos Control Program, FAA Order 1050.14A, Polychlorinated Biphenyls (PCBs) in the National Airspace System (NAS), and 40 CFR Part 82, Protection of Stratospheric Ozone.

The Contractor shall identify, handle, store, and ship any hazardous materials, or ASSC equipment containing hazardous materials, IAW relevant federal, FAA, state, and local requirements, including but not limited to: 40 CFR 260-280; 49 CFR 170-180; 29 CFR 1910.1200; FAA Order 3900.19B; FAA Order

C-20

3900.57, and FAA Order 4600.27A. All hazardous materials brought onto the job site shall have Occupational Safety and Health Administration (OSHA) and Department of Transportation-required hazard labels, and all containers shall be clearly marked as to their contents at all times. Material Safety Data Sheets (MSDS) for hazardous components or materials in the ASSC system shall be furnished with the delivery of the First Article ASSC system, IAW 29 CFR 1910.1200 and FAA Order 3900.19B. The Contractor shall provide the facility manager with information regarding precautionary measures (e.g., engineering controls they will implement to avoid excessive exposure to personnel), and post copies of MSDSs adjacent to the work project.

The Contractor shall identify and minimize the use of hazardous materials that could cause toxic exposures during use, maintenance, or fire. ASSC systems shall minimize the use of hazardous materials requiring special installation/disposal procedures. Recyclable materials are preferred.

The Contractor shall develop and deliver a Disposition Plan (CDRL PM10) for identifying, handling, storing, and disposing of all hazardous materials in ASSC equipment, IAW the Resource Conservation and Recovery Act (RCRA) and FAA Order 4600.27A, Personal Property Management.

The Contractor shall prepare any hazardous or non-hazardous waste manifest(s) required to dispose of wastes generated by ASSC that are regulated by federal, state or local government, as well as any required Land-Ban Restriction Notifications. The COTR shall sign all manifests.

Facilities requiring…