SMR4 Section C ASDE-3 SMR Replacement.pdf

Surface Movement Radar, Model 4 (SMR4)

Section C: Statement of Work

October 24December 13, 2024

V.10

SIR 693KA7-25-R-00001 Amendment 2

SURFACE MOVEMENT RADAR, MODEL 4 (SMR4)

SECTION C - STATEMENT OF WORK

C-2

1 Table of Contents

1 Overview

1.1. Introduction

1.2. Purpose

1.3. Scope

2 Applicable Documents

2.1 Military Handbooks

2.2 FAA/DOT Specifications, Standards, and Orders

2.3 Other Publications, Specifications, and Federal Regulations

3 Requirements

3.1 Program Management

3.1.1 Program Planning and Execution

3.1.2 Program Metrics and Reporting

3.1.3 Program Data Management

3.1.4 Program Data Items

3.1.5 Program Risk Management

3.1.5.1 Continuity of Services

3.1.6 Reviews, Conferences, and Meetings

3.1.6.1 Post Award Conference

3.1.6.2 Program Management Reviews (PMR)

3.1.6.3 Technical Interchange Meetings (TIM)

3.1.6.4 Integrated Baseline Review (IBR)

3.1.7 Foreign Visitor Requirements

3.2 Quality Assurance (QA)

3.3 Configuration Management (CM) Program

3.3.1 Configuration Identification

3.3.2 Configuration Baselines

3.3.3 Configuration Control

3.3.3.1 Configuration Control Board (CCB)

3.3.3.2 Engineering Change Proposal (ECP)

3.3.3.3 Request for Variance (RFV)

C-3

3.3.4 Configuration Audits

3.3.4.1 Functional Configuration Audit (FCA)

3.3.4.2 Physical Configuration Audit (PCA)

3.3.5 Configuration Status Accounting (CSA)

3.3.6 Data Management/Document Library

3.4 Environment, Occupational Safety and Health (EOSH)

3.4.1 Environmental Requirements

3.4.2 Seismic Requirements

3.4.3 Electrical Safety

3.4.4 Fire Life Safety

3.4.5 Occupational Noise

3.4.6 Fall Protection

3.5 System Design

3.5.1 Technical Reviews

3.5.1.1 System Requirements Review

3.5.1.1.1 SRR Entrance Criteria

3.5.1.1.2 SRR Presentation

3.5.1.1.3 SRR Acceptance Criteria

3.5.1.2 Preliminary Design Review

3.5.1.2.1 PDR Entrance Criteria

3.5.1.2.2 PDR Presentation

3.5.1.2.3 PDR Acceptance Criteria

3.5.1.3 Critical Design Review

3.5.1.3.1 CDR Entrance Criteria

3.5.1.3.2 CDR Presentation

3.5.1.3.3 CDR Acceptance Criteria

3.5.2 Design Engineering Meetings

3.5.2.1 Surface Surveillance System Interface Meeting

3.5.2.2 SMR4 Maintenance Terminal Review

3.5.3 Interface Documentation

3.5.3.1 Interface Design Description

3.5.3.2 Interface Control Document

3.5.4 Optimization

C-4

3.5.4.1 Optimization Documentation

3.5.4.2 SMR4 Radar Optimization

3.5.4.3 Surface Surveillance System Optimization

3.5.5 Reliability, Maintainability, and Availability (RMA)

3.5.5.1 Reliability, Maintainability and Availability (RMA) Modeling and Predictions

3.5.5.2 Reliability and Maintainability (R&M) Program

3.5.6 Access to System Development Environment

3.6 Systems Engineering

3.6.1 Requirements Management

3.6.2 System Safety Engineering

3.6.3 Information System Security

3.6.3.1 Information System Security Services

3.6.4 Program Trouble Reporting

3.6.4.1 Program Trouble Report (PTR)

3.6.4.2 Program Trouble Report (PTR) Database

3.6.5 Spectrum Compliance

3.6.6 Software Development

3.6.6.1 Software Engineering Practices

3.6.6.2 Software Maintenance

3.6.6.3 Software Documentation

3.6.6.3.1 Software Requirements Specification

3.6.6.3.2 Software Design Description

3.6.6.3.3 Software Version Description Document

3.7 Service Requirements and Support

3.7.1 Site Support

3.7.2 Second Level Engineering Transition

3.7.2.1 Program Support Facility (PSF) System Installation

3.7.2.2 Software Development and Support Tools

3.7.2.3 Software Programs

3.7.2.4 Site Software Licenses

3.7.2.5 Software Maintenance Transition

3.8 Integrated Logistics Support (ILS)

3.8.1 ILS Program Management

C-5

3.8.1.1 Integrated Logistics Management Team

3.8.2 Line Replaceable Unit (LRU) Designation

3.8.2.1 Line Replaceable Unit (LRU) Criteria

3.8.2.2 Lower Line Replaceable Unit (LLRU)

3.8.2.3 Non-Line Replaceable Unit (Non-LRU)

3.8.3 Reviews, Meetings, Conferences

3.8.3.1 Logistics Guidance Conference (LGC)

3.8.3.2 Training Guidance Conference (TGC)

3.8.3.3 Provisioning Conference (PC)

3.8.3.4 Logistics Management Information (LMI) Review

3.8.4 Integrated Support Plan

3.8.5 Supply Support

3.8.5.1 Logistics Management Information (LMI) Requirements

3.8.5.2 Site Spares

3.8.5.3 Site Consumables

3.8.5.4 Depot Spares

3.8.5.5 Support and Test Equipment (S&TE)

3.8.5.6 FAA Asset Management and Identification

3.8.5.6.1 FAA Asset Barcoding For Exchange and Repair Parts

3.8.5.7 Asset Identification Report

3.8.5.8 Piece Part List

3.8.6 Technical Data

3.8.6.1 Engineering Drawing Tree

3.8.6.2 Product Drawings

3.8.6.3 Master Pattern and Plan View of Parts Layout

3.8.6.4 Original Equipment Manufacturer (OEM) Manuals and Information

3.8.6.5 Manuscript Development Process

3.8.6.5.1 Manuscript Plan

3.8.6.5.2 Manuscript Prospectus

3.8.6.5.3 In-Process Reviews (IPR)

3.8.6.5.4 Manuscript Validation and Verification (V&V)

3.8.6.5.5 Manuscript Validation and Verification Completion Report

3.8.6.5.6 Technical Instruction Book (TIB)

C-6

3.8.6.6 Custom Test and Support Equipment Manuals

3.8.6.7 Custom Depot Test Equipment Manuals

3.8.6.8 Depot Repair and Test Procedures Manual

3.8.6.9 Software User Manual

3.8.6.10 Software Maintenance Manual

3.8.6.11 Software Diagnostics Manual

3.8.6.12 COTS Hardware Description Document

3.8.7 Training

3.8.7.1 General Requirements

3.8.7.1.1 Access to Contractor Facilities

3.8.7.1.2 Training Personnel Qualifications

3.8.7.1.3 Training Days

3.8.7.2 Test Team Familiarization Training

3.8.7.2.1 Training Development for Test Team Familiarization

3.8.7.2.2 Course Conduct for Test Team Familiarization

3.8.7.3 Second Level Engineering Training

3.8.7.3.1 Training Development for Second Level Engineering

3.8.7.3.2 Course Conduct for Second Level Engineering

3.8.7.4 Depot Level Training

3.8.7.4.1 Training Development for Depot Level Support

3.8.7.4.2 Course Conduct for Depot Level Support

3.8.7.5 Technical Operations Training

3.8.7.5.1 Commercial-Off-the-Shelf (COTS) Training Materials

3.8.7.5.2 Technical Operations Training Design

3.8.7.5.3 Technical Operations (TO) Training Development

3.8.7.5.4 Course Conduct for Field Maintenance

3.8.7.5.5 Training Delivery Notification

3.8.8 Interim Contractor Depot Level Support

3.8.8.1 Definitions

3.8.8.2 Interim Contractor Depot Level Support Services

3.8.8.3 ICDLS Priority

3.8.8.4 Exchange and Repair (E&R) Procedures

3.8.8.5 Depot Spares Lay-In

C-7

3.8.8.6 Interim Contractor Depot Level Service (ICDLS) Status Reporting

3.8.8.7 Point of Contact

3.8.8.8 Obsolete Parts Program

3.8.8.9 Depot Support Transition Plan

3.9 System Production

3.9.1 First Article Systems

3.9.1.1 In-Plant Development Test System

3.9.1.2 Program Support Facility (PSF)

3.9.1.3 Depot Support System

3.9.1.4 Academy System

3.9.1.5 Key Site Systems

3.9.2 Production Systems

3.9.3 First Article and Depot Support System Refurbishment

3.9.4 Additional Maintenance Terminals

3.10 Site Implementation

3.10.1 System Constraints and Siting Analysis

3.10.2 Site Survey

3.10.3 Construction Drawing Package (60%/90%/100%)

3.10.4 Site Preparation, Equipment Removal and Receipt, Installation, and Check Out

3.10.4.1 Site Preparation

3.10.4.2 Legacy Equipment Removal

3.10.4.3 Equipment Receipt

3.10.4.4 Installation, and Checkout

3.10.5 Optimization

3.10.6 Site Acceptance Test (SAT)

3.10.7 Contractor Acceptance Inspection (CAI)

3.10.8 Damage to Government Property

3.10.9 Contractor Use of Government Premises

3.11 Test and Evaluation

3.11.1 Test Program Description

3.11.2 T&E Program Management

3.11.3 Test Verification Requirements Traceability Matrix (TVRTM)

3.11.3.1 Instructions for TVRTM Development

C-8

3.11.4 Verification of Requirements Utilizing Demonstration, Test, or Inspection

3.11.5 Verification of Requirements Utilizing Analysis

3.11.6 Verification of Requirements Utilizing Test with Data

3.11.7 Verification of Requirements Utilizing Design Review

3.11.8 Formal Test Events

3.11.9 Test Tools and Equipment

3.11.10 Contractor’s T&E Program

3.11.10.1 Development Test (DT)

3.11.10.1.1 First Article Inspections

3.11.10.1.2 Verification of Environmental Requirements

3.11.10.1.3 Maintainability Test

3.11.10.1.4 Key Site Installation Test

3.11.10.1.5 Verification of Surface Surveillance System Interface Requirements

3.11.10.1.6 Verification of Resolution Requirements

3.11.10.1.7 Verification of Tracker Merge/Unmerge Requirements

3.11.10.1.8 Verification of Surface Surveillance Coverage Volume Requirements

3.11.10.1.9 Verification of Probability of Detection (PD) Requirements

3.11.10.1.10 Verification of Accuracy Requirement

3.11.10.1.11 Verification of False Track Requirements

3.11.10.1.12 Key Site System Stability Test

3.11.11 Production Acceptance Test (PAT)

3.11.12 Site Acceptance Test (SAT)

3.11.13 Regression Testing

3.11.14 Operational Test (OT) Support

3.12 Engineering Services

3.13 Transfer and Data Rights

3.14 Technology Refresh and Upgrade

C-9

Revisions Summary Page

Date/ Rev Rev Affected Sections

Change

10-24-2024 Initial Creation N/A N/A

12-13-2024 1 2.2, 3.4, 3.10.2, 3.10.4.2, 3.10.4.4, 3.8.3.2, 3.8.3.3, 3.8.5.5, 3.8.7.5, 3.9.2

2.2, 3.4, 3.8.3.2, 3.8.7.5 – update document references to current versions.

3.8.3.3 – fix a typographical error.

3.8.5.5 – delete “common and special/unique/ peculiar” from Tab 1 requirement.

3.9.2 – change production systems requirements.

3.10.2 – change “NTE” to “Budgetary Estimate.”

3.10.4.2 – change section heading.

3.10.4.4 – clarify contractor requirements.

C-10

1 Overview This 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 thirty-four (34) Surface Movement Radar, Model 4 (SMR4) systems and an option for nineteen (19) additional SMR4 systems.

The FAA intends to acquire a Commercial Off The Shelf (COTS) Surface Movement Radar (SMR) subsystem with necessary form, fit, and function enhancements to meet FAA requirements and integrate with the existing surface surveillance systems.

The FAA plans to test and evaluate the SMR to meet all safety and performance requirements for the National Airspace System (NAS) as set forth in this SOW.

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

1.1. Introduction

Currently, the FAA has two types of surface surveillance systems deployed at airports in the National Airspace System (NAS). These systems are Airport Surface Detection Equipment, Model X (ASDE-X) and Airport Surface Surveillance Capability (ASSC). ASDE-X and ASSC provide surface surveillance that enhances situational awareness for Air Traffic Control (ATC) to help prevent runway incursions. In this document, the term Surface Surveillance System will be used to indicate an ASDE-X or ASSC system.

The FAA Surface Surveillance Systems use cooperative and non-cooperative surveillance sensors to detect and track aircraft and vehicles within the Airport Movement Area (AMA). Cooperative surveillance sensors rely on aircraft transponder and vehicle transmitter transmissions to determine position and identity. Non-cooperative surveillance is provided by one or more SMRs and does not rely on any active transmission from a target.

The new SMR4 will replace all ASDE-3 SMRs. If the option is exercised, Surface Movement Radar – Improved (SMRi) systems will be replaced with SMR4s. Sustaining non-cooperative surveillance plays a significant role in maintaining the level of safety and efficiency airports currently experience with ASDE- X and ASSC installed. Without full surface surveillance services available at those airports, there will be gaps in movement area surveillance coverage, which may create potential hazards and increase runway incursions.

This acquisition will procure new hardware, software, data rights, development support, implementation support, training support, and all other support required for the replacement of the

ASDE-3 SMR.

1.2. Purpose

The purpose of this SOW is to define the scope of work, deliverables, timelines, and work locations to deliver the SMR4 systems meeting the requirements in the FAA SMR4 System Specification Document (SSD), FAA-E-37024, provided in Section J (Attachment J-3) of this contract. This SOW also includes, but is not limited to, provisions for Program Management (PM), System Engineering (SE), System Design, System Development, Test and Evaluation (T&E), Implementation, Integrated Logistics Support (ILS), and

C-11

Engineering Services. The SMR4 Contract Data Requirements List (CDRL) Matrix contained in Section J (Attachment J-2) of this contract defines the documents to be delivered to the Government resulting from the effort defined in this SOW.

1.3. Scope

The scope of this contract includes the following major components:

a. Establish and maintain a Contractor PM organization

b. Design, develop, and test all necessary interfaces between SMR4 and existing surface surveillance systems

c. Integrate, test, and evaluate the SMR4 system at operational sites

d. Implement the SMR4 on existing ATC and remote lattice towers

e. Develop documentation and training for FAA SMR4 maintainers, Second Level Engineering, and

Depot personnel

f. Develop and provide all Logistical Support elements and transition them to the Government

g. Provide Engineering Services and Site Support

The Government intends to acquire the data and designs necessary to support and maintain the SMR4 beyond completion of this contract.

2 Applicable Documents The following specifications, handbooks, orders, standards, and drawings form a part of this SOW and are applicable to the extent specified herein. In the event of conflict between this SOW and any of the documents referenced within this SOW, the provisions of this SOW take precedence.

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 the material desired and cite the solicitation or contract number. FAA Orders can be found on the FAA public website at: https://www.faa.gov/regulations_policies/orders_notices/.

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

c. Military Handbooks 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 Electronic Industries Alliance (EIA) standards may be obtained from the Electronic Industries Alliance, Technology Strategy and Standards Department, 2500 Wilson Boulevard, Arlington, VA 22201-3834, or by calling (703) 907-7500, or through their web site at http://www.ecianow.org/.

e. Copies of International Standards Organization (ISO)/International Electrotechnical Commission (IEC) documents may be obtained from American National Standards Institute, 11 West 42nd Street, 13th Floor, New York City, NY 10036. Telephone: (212) 642-4900, Telefax: (212) 398- 0023, or Email: info@ansi.org, or Web sites: http://www.ansi.org or http://www.iso.org http://dodssp.daps.dla.mil/ http://www.ecianow.org/ mailto:info@ansi.org http://www.iso.org/

C-12

f. Copies of Institute of Electrical and Electronics Engineers (IEEE)/American National Standards Institute (ANSI) documents may be obtained from IEEE Computer Service, 445 Hoes Lane, P.O.

Box 1331, Piscataway, NJ 08855-1331, or by calling (800) 701-4333 (in the U.S. and Canada), or

(732) 981-0060 (outside of the U.S. and Canada), or through their standards web site at:

http://www.ieee.org/web/standards/home/index.html

g. Copies of the Acquisition Management System (AMS) 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 Handbooks

Document Number Document Title MIL-HDBK-470A Designing and Developing Maintainable Products and Systems

MIL-HDBK-781A

Reliability Test Methods, Plans, and Environments for Engineering Development, Qualification, and Production

MIL-HDBK-217F Reliability Prediction of Electronic Equipment MIL-HDBK-61A Configuration Management Guidance

2.2 FAA/DOT Specifications, Standards, and Orders

Document Number Document Title FAA-E-37024 FAA SMR4 System Specification Document (SSD)

NAS-IR-nnnnnn

Interface Requirements Document for Surface Movement Radar, Model 4 (SMR4) To Airport Surface Detection Equipment, Model X (ASDE-X) and Airport Surface Surveillance Capability (ASSC)

FAA Order 3900.19C19D FAA Occupational Safety and Health (OSH) Policy FAA Order JO 1050.20B Management of Asbestos at Air Traffic Organization (ATO) Facilities FAA Order JO 1050.17B Environmental Compliance at Air Traffic Organization Facilities

FAA Order JO 3900.57A

Environmental and Occupational Safety and Health (EOSH) Requirements in the Planning and Execution of Construction and Maintenance Activities at National Airspace System (NAS) Facilities

FAA Order JO 3900.64A ATO Electrical Safety Program FAA Order JO 3900.67A ATO Hazardous Energy Control (Lockout/Tagout) Program FAA Standard HF-STD-001B Human Factors Design Standard FAA Order 1600.75 Protecting Sensitive Unclassified Information

FAA-D-2494B

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

FAA-G-2100J Electronic Equipment, General Requirements

FAA-STD-025F

US Department of Transportation, FAA Standard, Preparation of Interface Documentation, November 30, 2007

FAA Order 1370.121B FAA Information Security and Privacy Policy FAA Order 1370.121B, Supplement

FAA Information Security and Privacy: FAA Supplemental Security Controls http://fast.faa.gov/

C-13

FAA Order 1370.121B, Supplement FAA Information Security and Privacy: Governance FAA Order 1370.121B, Supplement

FAA Information Security and Privacy: FAA Implementation of NIST Controls

FAA Order 1370.121B, Supplement

FAA Information Security and Privacy: Protection of Sensitive Unclassified Information (SUI) on Federal and non-Federal Information Systems and Services by External Entities

FAA Order 1370.121B, Supplement

FAA Information Security and Privacy: User Responsibilities and Obligations

FAA Order 6050.19G Radio Spectrum Planning SMS Manual FAA Safety Management System (SMS) Manual SRMGSA FAA Safety Risk Management Guidance for System Acquisitions

FAA-HDBK-006D

FAA Handbook, System Reliability, Maintainability, and Availability

(RMA)

FAA Order 4600.27D Personal Property Management FAA Order JO 3000.57 ATO Technical Operations Training and Personnel Certification FAA Order JO 3000.22AC ATO Outcomes-Based Technical Training Management

FAA Order 6000.30FG National Airspace Systems Maintenance Policy for Maintenance of the National Airspace System

Not Applicable (N/A) FAA Asset Identification Process and Procedure Guide N/A AMS ILS Process Manual

2.3 Other Publications, Specifications, and Federal Regulations

OSHA 29 CFR 1910 OSH Standards (General Industry) OSHA 29 CFR 1926 Safety and Health Regulations for Construction EPA 40 CFR Resource Conservation and Recovery Act (RCRA)

SAE AS9100D

Society of Automotive Engineers (SAE), Quality Management Systems

- Requirements for Aviation, Space, and Defense Organizations

SP 800-53 (REV.5)

National Institute of Standards and Technology (NIST) Special Publication, Recommended Security Controls for Federal Information Systems And Organizations - Information Security

ANSI/EIA-748 Earned Value Management System IEEE Standard 1063-1987 IEEE Standard for Software User Documentation OMB Circular A-130 Management of Federal Information Resources NFPA 70 National Electrical Code NFPA 70E Standard for Electrical Safety in the Workplace N/A FAA Standard Work Breakdown Structure, Ver 5.3

C-14

3 Requirements

3.1 Program Management

The Contractor must establish and maintain a Contractor Program Management Organization (PMO) to execute the requirements of this contract efficiently and effectively. The Contractor must assign a Program Manager (PM) who has the resources, authority, accountability, and overall responsibility to ensure efficient and timely program execution. The PM will be the point of contact between the FAA and the Contractor in the execution of this program.

The Contractor must develop a Program Management Plan (PMP) in accordance with CDRL PM01 to define all functional elements of their program management, interactions and communications with the Government and other stakeholders, and the planning, execution, monitoring, control, and closeout of the program. The Contractor must implement the methods, processes, and procedures described in the

PMP.

CDRL PM01 Program Management Plan (PMP)

3.1.1 Program Planning and Execution

The Contractor must prepare and deliver the Contractor Work Breakdown Structure (CWBS) in accordance with CDRL PM02. The Contractor must maintain and update the CWBS to a minimum level 3 unless otherwise approved by the Government. The Contractor must map the CWBS to the FAA standard work breakdown structure as defined in the SMR4 Program Extract of Applicable Sections - FAA Standard Work Breakdown Structure (Attachment J-9). The Contractor must map the CWBS to its Organizational Breakdown Structure (OBS).

The Contractor must develop an Integrated Master Schedule (IMS) in accordance with CDRL PM03 that includes the entire scope of the program. The Contractor IMS must provide a time-based view of the detailed network of activities and tasks that are necessary for successful program execution. The Contractor IMS must contain milestones for all delivery items of this contract. The Contractor IMS must be capable of optimizing activities and reporting the critical path over the duration of the contract.

The Contractor must execute the program in accordance with the CWBS and IMS and use these tools for program performance analysis and reporting. The Contractor must present the IMS and recommended changes at all PMRs. The Contractor must receive Government approval prior to incorporating recommended changes into the IMS (CDRL PM03). The Government will notify the Contractor of Government initiated changes to the IMS.

The Contractor must submit an updated IMS (CDRL PM03) after any changes are incorporated into the schedule.

CDRL PM02 Contractor Work Breakdown Structure (CWBS)

CDRL PM03 Integrated Master Schedule

C-15

3.1.2 Program Metrics and Reporting

The Contractor must provide the Government with a Program Management Status Report (PMSR) in accordance with CDRL PM04.

The Contractor’s management methods and procedures must provide visibility into, and timely progress reporting on, all contracted efforts for internal management and Government oversight purposes. The Contractor must maintain performance measurement systems and related procedures throughout this contract. The Contractor must continuously monitor the technical performance of this contract, and of all subcontracts.

The Contractor must measure, track, and report the status of the following metrics at a minimum:

a. Project Requirements (Stability Measure)

b. Software Development Progress

c. Requirements Validation Progress

d. Program Trouble Reports (PTR) (CDRL SE04)

e. Risk Management

The Contractor must have a documented and validated Earned Value Management System (EVMS) and provide status as part of the Financial Status Report (CDRL PM06). The Contractor EVMS must comply with EIA Standard “Earned Value Management System”, EIA-748.

The Contractor must utilize the EVMS to manage and document:

a. All planned work scope for the program from inception to completion

b. Timely baseline establishment and control

c. Information broken down by product as well as by organization or function

d. Objective measurement of accomplishment against the plan at levels where the work is being performed and in accordance with the approved CWBS

e. Summarized reporting to higher management for use in decision-making

f. Analysis of significant variances

g. The implementation of management actions to mitigate risk and manage cost and schedule performance

The Contractor's EVMS must:

a. Apply all direct and indirect cost and provisions for use and control of management reserve and undistributed budget

b. Incorporate changes to the contract budget based on approval of the Government

c. Establish constraints to preclude subjective adjustment of data to ensure performance measurement remains realistic. Unless the CO provides prior written approval, in no case must the total allocated budget exceed the contract budget base. For cost reimbursement contract line items, the contract budget base must not be adjusted to reflect cost growth increases

d. Establish and document the capability to accurately identify and explain significant cost and schedule variances, both on a cumulative basis and projected at completion basis

C-16

The Contractor must prepare and submit Contract Funds Status Reports (CFSR) in accordance with CDRL PM05, and PMSR (CDRL PM04), utilizing the EVMS. The EVMS information must include all program data including subcontractor data.

The Contractor must provide a monthly Financial Status Report, in accordance with CDRL PM06, clearly stating the financial status by CLIN and reporting all Contractor’s costs associated with the contract. The cost data for the report must be from the prime Contractor’s internal financial accounting system. The prime Contractor must generate and deliver one consolidated report that includes the prime Contractor and all subcontractor's cost. Costs included in the initial submission must reflect the final negotiated position between the Government and the prime Contractor. The Financial Status Report must be delivered monthly.

The Contractor must provide a Funds and Man-Hour Expenditure Report, in accordance with CDRL PM11 for reporting all Contractor and Sub-Contractor labor, materials, travel, and other contract charges for all Time and Materials (T&M) CLINs.

The Contractor must provide a Cost Performance Report (CPR), in accordance with CDRL PM12, for all CLINs as part of the Contractor’s EVMS. The Contractor must implement a cost and schedule performance measurement and reporting system, and related management procedures that shall be the basis for all data reported on the CPR (CDRL PM12). The Contractor must establish a baseline for all CLINs within 60 days after contract award and must maintain the cost and schedule performance measurement and reporting system and related procedures throughout the contract period of performance.

The Contractor must present the CPR by CWBS element at every PMR. Quarterly, the Contractor must report cost and schedule activities at the OBS level at PMRs in addition to the CWBS reporting.

CDRL PM04 Program Management Status Report (PMSR)

CDRL PM05 Contract Funds Status Report (CFSR)

CDRL PM06 Financial Status Report

CDRL PM11 Funds and Man-Hour Expenditure Report

CDRL PM12 Cost Performance Report

3.1.3 Program Data Management

The Contractor must establish a data management program to maintain contractually required documentation and correspondence; design, test, and production documentation; and other supporting documentation. This must be done in one logical and inclusive system using ISO 9001/9000-3:2004, and MIL-HDBK-61A as guidance. This effort must include documentation involved with, but not limited to, the development, implementation, testing, schedule, and management of the equipment. This specifically must 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 must be configuration-managed by the contractor.

C-17

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

3.1.4 Program Data Items

All Program Data Items referenced throughout this SOW are listed in the CDRL Matrix (Attachment J-2) and are referred to as CDRLs. The Contractor must develop each Program Data Item in accordance with the CDRL and the corresponding Data Item Description (DID) with the same name. The Contractor must submit a cover letter with each CDRL delivered to the Government. The Contractor must submit all Program Data Items electronically and only provide hardcopies where specified in this SOW or the DID.

Government response to all CDRLs will be 30 days from the Government’s receipt of the CDRL, unless otherwise noted in the CDRL form.

The Contractor must submit a Contract Deliverables Status Report in accordance with CDRL PM07.

CDRL PM07 Contract Deliverables Status Report

3.1.5 Program Risk Management

The Contractor must define the process used to identify Risks, Issues, and Opportunities (RIO) as part of the PMP (CDRL PM01). The Contractor must describe its risk management program, plans, organization, processes, and techniques in the PMP. The Contractor’s risk management program must be compatible with the FAA Risk Management Program, in accordance with the guidance provided in the Surface Surveillance Program Risk, Issue, and Opportunity (RIO) Management Plan Standard Operating Procedure (SOP) (Attachment J-11).

Specific risk management functions must include the following:

a. Identification of known and potential RIOs

b. Assessment of risks, including a relative ranking in accordance with the program impact and likelihood scales described in Program RIO Identification Worksheet (Attachment J-12)

c. Establishment of critical thresholds or points for re-evaluation

d. Assessment and quantification of the impact of risks on successful completion of the work efforts by relating risks and costs to schedule and technical performance

e. Definition of methods or alternatives to mitigate or minimize these risks, including the identification of criteria upon which programmatic decisions can be based

f. Development, implementation, and report mitigation plans and progress for RIOs

g. Supporting information for conducting joint risk reviews with the Government

The Contractor must develop and maintain a list identifying, analyzing, and classifying program risks.

The Contractor must identify risks, assign a priority (Low, Medium, or High), and develop risk mitigation plans for these risks. The Government must be notified immediately upon Contractor identification of a Medium or High Priority risk. All risks must be identified in the PMSR (CDRL PM04), and the status and mitigation plans must be presented and discussed at the PMRs.

C-18

If it is determined that identified risks have significant potential for program impacts, the Contractor must present their mitigation plans and status at risk management meetings as requested by the Government.

3.1.5.1 Continuity of Services

The Contractor must provide a Continuity of Contract Performance Plan in accordance with CDRL PM13 to ensure supplies and services required under this contract are continued without interruption in the event of a national emergency or incidence of national significance.

CDRL PM13 Continuity of Contract Performance Plan

3.1.6 Reviews, Conferences, and Meetings

The Contractor must coordinate and receive Government approval for the times and locations for conduct of all reviews, conferences, and meetings. The Government may opt to hold events using teleconference technologies.

The Contractor must provide a Meeting Agenda in accordance with CDRL PM08, Presentation Materials in accordance with CDRL PM09, and any supporting documentation for each conference, review, and meeting prior to the event.

At each conference, review and meeting, the Contractor must provide empirical backup data regarding assumptions made and methodologies used in arriving at specific recommendations or conclusions.

These conferences, reviews and meetings include Post Award Conference, Program Management Reviews (PMR), Technical Interchange Meetings (TIM), System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Physical Configuration Audit and Functional Configuration Audit (PCA/FCA), and all other meetings required for management of the contract.

The Contractor must submit Meeting Minutes in accordance with CDRL PM10 after each conference, review, and meeting.

CDRL PM08 Meeting Agenda

CDRL PM09 Presentation Materials

CDRL PM10 Meeting Minutes

3.1.6.1 Post Award Conference

The Contractor must plan, host, support, and participate in a Post Award Conference to be held at the Contractor’s site within 30 days after contract award. At this conference, the Contractor must address the plans, schedules, and work efforts for this contract.

To successfully complete the Post Award Conference, the Contractor must:

a. Discuss proposed resources and efforts to meet contractual requirements

b. Discuss key contractual requirements

c. Discuss any questions raised by the Government or by the Contractor with respect to the performance and administration of the contract

C-19

d. Introduce Key Personnel to Government counterparts

e. Discuss any enhanced capabilities identified in the Contractor's proposal. The Government will identify which, if any, enhanced capabilities will be verified during the test program

f. Discuss any planned product upgrades and future obsolescence issues

g. Provide an overview of Site Surveys and the overall implementation process

h. Discuss information exchange and a file naming convention for all documents stored in the Data

Management/Document library

3.1.6.2 Program Management Reviews (PMR)

The Contractor must conduct and administratively support PMRs monthly during the period of performance of this contract. PMRs will be virtual unless otherwise specified by the Government. The PMRs must be targeted for no more than one day in duration.

PMRs should be conducted approximately seven days after the monthly electronic submission of the PMSR (CDRL PM04). The Government reserves the right to reduce the frequency of the PMRs throughout the contract period of performance. The Government CO, or their designated representative, will provide written notification of this change.

The Contractor must conduct PMRs to present program status. The Contractor must present cost and schedule status, provide performance measurement information, and present current and anticipated technical and implementation problems, as well as risks to the program. The Contractor must report the status of each action item at the PMR and in the Meeting Minutes (CDRL PM10) submitted for PMRs until the action item has been resolved as mutually agreed by the Government and Contractor.

PMRs, at minimum, must include the following:

a. Review of PMSR (CDRL PM04)

b. Review of overall program status and focus areas

c. Review of IMS (CDRL PM03) and reasons for any variances

d. Review of EVMS and reasons for any variances

e. Review program RIOs

f. Review the CFSR (CDRL PM05)

g. Report status, accomplishments, issues, and recommendations for each site

h. A description and status of:

1. PTRs (CDRL SE04)

2. Engineering Change Proposals (ECP) (CDRL CM02)

3. Request for Variance (RFV) (CDRL CM03)

4. Action Items

5. Open Items/Summary

3.1.6.3 Technical Interchange Meetings (TIM)

The Contractor must conduct and administratively support TIMs monthly during the period of performance of this contract. TIMs will be virtual unless otherwise specified by the Government. The Government reserves the right to reduce the frequency of the TIMs throughout the contract period of

C-20 performance. The Government CO, or their designated representative, will provide written notification of this change.

During the TIMs, the Contractor and the Government will discuss specific technical activities, including studies, test approaches/procedures, test results, design issues, technical decisions, implementation concerns, and other issues that require mutual resolution or further clarification.

3.1.6.4 Integrated Baseline Review (IBR)

The Contractor must conduct an Integrated Baseline Review (IBR) at Contractor facilities within 120 days after Contractor Award. The Contractor must consult with Government EVM POC(s) ahead of each IBR to inform the development of a mutually agreeable structure for EVM planning/work packages, and (where possible) to synchronize with any related existing Government EVM planning. The Contractor must provide all required documentation 30 days prior to the IBR.

The Contractor must present its time-phased performance measurement baseline to the Government and provide the underlying assumptions used in the development of the baseline. The Contractor must include the performance measurements baselines for subcontractors in the IBR. The Contractor must demonstrate that its management procedures comply with the earned value management systems criteria of Paragraph A.1.c – Earned Value Management System (EVMS), ANSI/EIA-748, or FAST Guidance T1.13 – Metrics and Performance Management. The Contractor must conduct all IBRs in accordance with FAA Program-Level Integrated Baseline Review Guide (Attachment J-15).

The Contractor must include prime and sub-contractor program management, and FAA Program Management and functional area subject matter experts to ensure all parties understand and concur with the technical, schedule-related, and cost-related baselines used to monitor program performance.

The Contractor must conduct additional IBRs upon request by the Government for significant changes to the contract, such as major contract revisions, a re-baseline, a major planning/work package rollout, rolling wave planning, or exercise of a contract option.

The Contractor must submit a Meeting Agenda (CDRL PM08) prior to each IBR. The Contractor must provide Meeting Minutes (CDRL PM10) following each IBR.

3.1.7 Foreign Visitor Requirements

The Contractor must submit a Visitor Request FAA Form 1600.78 (Attachment J-16) to the Government for all visits by foreign nationals to any FAA facility.

The Contractor must submit the form no later than 30 days prior to the planned visit. The Contractor must receive Government approval before conducting the visit.

3.2 Quality Assurance (QA)

The Contractor must establish and maintain a documented quality management program in accordance with Section E of this contract as a means of assuring compliance with all requirements of the contract.

The Contractor must provide and maintain a Quality Control (QC) program that fulfills the requirements of Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations, SAE

C-21

AS9100D. Additionally, the QC program must fulfill the Assurance Level 4 requirements of Software Standard for Non-Airborne Systems, RTCA DO-278A.

The Contractor must prepare a Quality System Plan (QSP) in accordance with CDRL QA01. The Contractor is responsible for incorporating, as part of its subcontracts, all applicable QA provisions of this contract to its subcontractors and vendors. In addition, the Contractor’s QSP (CDRL QA01) must specifically address how the Contractor will ensure subcontractor, vendor, and supplier compliance to the applicable requirements of this contract.

CDRL QA01 Quality System Plan

3.3 Configuration Management (CM) Program

The Contractor must use a Configuration Management (CM) system for the control of all elements of the SMR4, including hardware, software, firmware, documentation, test equipment, space, physical media, and physical parts. The Contractor must maintain configuration control of the hardware to the Line Replaceable Unit (LRU) level, and software and firmware to the current version level.

The Contractor must establish, implement, and maintain a CM program using Configuration Management for Defense Contracts, EIA-649-1, Revision A, as guidance. Additionally, the CM program must fulfill the Assurance Level 4 requirements of Software Standard for Non-Airborne Systems, RTCA DO-278A. The Contractor’s CM program must provide an organizational structure with configuration identification and control methods, configuration audits, and configuration status accounting procedures for the SMR4 system hardware and software and its environment and support systems.

The Contractor must identify a primary point of contact for all communication on CM related issues.

The Contractor must develop and submit a Configuration Management Plan (CMP) which fully documents the Contractor’s CM program including a description of how the Contractor will establish, implement, and maintain the CM program. The Contractor must deliver the CMP as an appendix to the

PMP (CDRL PM01).

The Contractor must use the processes, procedures and methodologies defined in the CMP for control of all configuration items (e.g., hardware, software, firmware, physical media and parts, support equipment, documentation, and adaptation parameters) and to maintain the integrity and traceability of its configuration.

3.3.1 Configuration Identification

The Contractor must recommend Configuration Items (CIs) using the guidelines provided in Configuration Management Requirements for Defense Contracts, EIA-649-1, Revision A. Configuration Item’s (CI) are designated for special (additional) CM activity distinct from that which is appropriately applied to every product.

A CI is an aggregation of any hardware, software, or firmware that satisfies an end-user function and is designated by the Government for separate CM. The configuration identification process combines the identified items into an overall product structure/hierarchy, establishing relationships with the CIs and all associated documents and support elements.

C-22

The Contractor must maintain configuration control and status accounting of approved CIs throughout the period of performance of this contract. The Contractor must assign a discreet part/item identification number to each software, firmware, and hardware CI.

Non-interchangeable LRU’s must not share the same part/item identification number. A part is considered non-interchangeable whenever its form, fit, or function must be changed to enable it to function in a different position in the SMR4 system.

Upon establishment of the System Baseline, the Contractor must not change the assigned discrete part/item identification number without Government approval.

The Contractor must assign a unique version identification number to each delivered software package containing SMR4 system release or build-type software executables. The software package must be inclusive of all software segments, thereby providing easy identification of software releases after the product baseline is established.

3.3.2 Configuration Baselines

The Contractor must establish and maintain configuration baselines and the required documentation to support these baselines using Configuration Management Requirements for Defense Contracts, EIA-649- 1, Revision A as guidance.

Commercial Product Baseline: Consists of the technical documentation and hardware, software, and firmware CIs that meet the requirements of the Contractor’s System/Subsystem Specification and is delivered as the initial First Article system.

System Baseline: Consists of the technical documentation and hardware, software, and firmware CIs after completion of design and development. The first System Baseline is based on the First Article system configuration delivered to the FAA for Development Test (DT), and the baseline is established prior to the start of the test. Subsequent System Baselines are established prior to the formal test for system updates to the Product Baseline.

Product Baseline: Consists of the technical documentation and hardware, software, and firmware CIs of the system configuration after completion of design, development, and testing such that the system functional, performance, interoperability, and interface requirements have been proven to be successfully achieved and physical parameters confirmed. The first Product Baseline is based on the First Article system configuration delivered to the FAA for fielding/deployment, and the baseline is established after completion of the formal test and FCA/PCA. Subsequent Product Baselines are established after completion of the formal test for system updates delivered to the FAA for fielding/deployment.

The Contractor must provide and maintain a Baseline Index Report in accordance with CM01 that documents the Commercial Product, System, and Product Baselines.

CDRL CM01 Baseline Index Report

C-23

3.3.3 Configuration Control

The Contractor must apply configuration control measures to each baseline CI, and its configuration documentation. The Contractor must maintain change control of the engineering design upon establishment of the System Baseline.

The Contractor must document any proposed changes to the established baselines in a Program Trouble Report (PTR) (CDRL SE04), which must be approved by the Configuration Control Board (CCB) prior to implementation of the proposed changes. The Contractor must maintain configuration control at the LRU level for hardware CIs and at the component level for all other CIs.

3.3.3.1 Configuration Control Board (CCB)

The Contractor must establish a CCB, co-chaired by the Contractor and the Government, to review and approve any changes to the configuration of the SMR4 and ensure that documentation associated with an approved change to the system is identified for updating to reflect the appropriate baseline. The Contractor must provide qualified personnel - capable of assessing potential system impacts of the discrepancies documented in PTRs and their proposed corrective action(s) - to participate in CCB meetings.

The CCB will review, prioritize, disposition, approve and close PTRs generated during the life of the contract. The CCB will also make recommendations regarding the necessity to initiate ECPs (CDRL CM02) and RFVs (CDRL CM03) in response to PTRs (CDRL SE04). The Contractor must convene with the CCB a minimum of once per month, following the establishment of the System Baseline. The Government may change the frequency of CCB meetings.

The Contractor must submit a Meeting Agenda (CDRL PM08) to the Government at least five days prior to each scheduled CCB. The agenda must include a listing of all PTRs to be discussed at the CCB. The Contractor must submit Meeting Minutes (CDRL PM10) after each CCB.

At the CCB, PTRs must be reviewed, approved by the Government, and jointly prioritized as follows:

a. Priority 1 is assigned to a problem that prevents the accomplishment of an operational, mission-critical, or mission-essential capability, jeopardizes safety or security.

b. Priority 2 is assigned to a problem that adversely affects the accomplishment of an operational, mission-critical, or mission-essential capability and no work-around solution is known.

c. Priority 3 is assigned to a problem that adversely affects the accomplishment of an operational, mission-critical, or mission-essential capability, but a work-around solution is known.

d. Priority 4 is assigned to a problem that results in a user/operator inconvenience or annoyance, but does not affect a required operational, mission-critical, or mission-essential capability.

e. Priority 5 is assigned to any other problem/defect not described above (e.g., system documentation errors).

The Contractor must notify the Government immediately of any Contractor initiated PTRs meeting Priority 1 and Priority 2 classification.

C-24

3.3.3.2 Engineering Change Proposal (ECP)

Upon CCB recommendation for an ECP (CDRL CM02) in response to a PTR (CDRL SE04), and at the direction of the Government, the Contractor must generate an ECP in accordance with CDRL CM02. The Contractor must obtain Government approval of each ECP prior to its implementation.

The Contractor must submit (attached to each ECP) a complete and accurate description of the changes proposed by the ECP and the changes for each document that would be modified if that ECP were approved.

As part of the ECP, the Contractor must provide estimated costs, schedules, benefits, and risks associated with the ECPs. Submittal of ECPs must begin at establishment of the System Baseline.

CDRL CM02 Engineering Change Proposal (ECP)

3.3.3.3 Request for Variance (RFV)

The Contractor must obtain Government approval of an RFV (CDRL CM03) to deviate from the Government requirements or an approved baseline. Upon CCB recommendation for an RFV in response to a PTR (CDRL SE04), the Contractor must generate an RFV in accordance with CDRL CM03.

CDRL CM03 Request for Variance

3.3.4 Configuration Audits

The Contractor must prepare for and support configuration audits using Configuration Management for Defense Contracts, EIA-649-1, Revision A, as guidance. The Contractor must prepare and submit a Configuration Audit Plan for FCA/PCA in accordance with CDRL CM04, which describes the Contractor’s approach to meeting the requirements. The Contractor must ensure that subcontractors, vendors, and suppliers participate in the configuration audits as proposed and approved via the Configuration Audit Plan. The Contractor must prepare and submit a Configuration Audit Summary Report in accordance with CDRL CM05 documenting the findings of the FCA/PCA.

CDRL CM04 Configuration Audit Plan

CDRL CM05 Configuration Audit Summary Report

3.3.4.1 Functional Configuration Audit (FCA)

The Contractor must support a Functional Configuration Audit (FCA) upon completion of DT at the Contractor facility using EIA 649-1 as guidance. During the FCA, the Contractor must demonstrate that the system documented by the System Baseline meets all requirements contained in the Test Verification Requirements Traceability Matrix (TVRTM).

FCA entrance criteria must include:

a. Successful completion of DT including closure of approved PTRs and incorporation of any approved ECPs and required retest

b. Approval of all DT Test Reports (CDRL TE04), Analysis Reports (CDRL TE03), Test with Data Reports (CDRL TE06), and Requirements Design Review Meeting Minutes (CDRL PM10)

C-25

Successful completion of the FCA must include validation by the Government that all requirements have been successfully verified.