Attachment 1 - Draft SIR - Section C - ASDE-3 SMR Replacement SOW (Release).docx

Surface Movement Radar Model 4 (SMR4)

Section C: Statement of Work For Draft SIR

September 12, 2022

SIR 693KA7-23-R-00002

PART I – SECTION C

STATEMENT OF WORK

Table of Contents

Revisions Summary Page

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 up to 34 Surface Movement Radar Model-4 (SMR4) systems and any options exercised by the Government. These radars will be installed at 27 airports and 3 Federal Aviation Administration (FAA) support facilities.

The FAA intends to acquire a Commercial Off The Shelf (COTS) Surface Movement Radar (SMR) subsystem with necessary form, fit, and function enhancements to integrate with the existing surface surveillance systems. The changes are anticipated to be limited to developing the interface between the SMR and the surface surveillance system and support remote maintenance and monitoring. Additional development work is expected to be required to mount the SMR on existing towers.

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 Federal Aviation Administration 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 Controllers (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. Sustaining non-cooperative surveillance plays a significant role in maintaining the level of safety and efficiency that 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.

The new SMR4 will replace all ASDE-3 SMRs. This acquisition will procure all new hardware and support elements required for the replacement of the ASDE-3 SMR.

1.2. Purpose

The purpose of this Statement of Work (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-X-XXXX, provided in Section J (Attachment J-5) of this contract. This SOW also includes provisions for Program Management (PM), System Engineering (SE), System Design, System Development, Test and Evaluation (T&E), Implementation, Integrated Logistics Support (ILS), and Engineering Services. The Contract Data Requirements List (CDRL) contained in Section J-3 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:

1. Establish and maintain a Program Management Organization (PMO)

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

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

4. Implement the SMR4 on existing air traffic control and remote lattice towers and execute disposition of legacy ASDE-3 equipment at all operational sites

5. Develop documentation and training for FAA SMR4 maintainers, Second Level Engineering, and Depot personnel

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

7. Provide Engineering Services and Site Support The Government intends to acquire the data and designs necessary to support and maintain SMR4 until its final disposition.

Applicable Documents The following specifications, handbooks, orders, standards, and drawings form a part of this SOW and are applicable to the extent specified herein. Additional applicable documents can be found in the Systems Specifications Document, and Interface Requirements Document. The latest version of these documents as of the contract date must apply. In the event of conflict between this SOW and any of the applicable documents cited below, the provisions of this SOW take precedence.

1. 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. FAA Orders can be found on the FAA public website at: https://www.faa.gov/regulations_policies/orders_notices/.

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

3. 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. Some documents are also available at the website, https://quicksearch.dla.mil/.

4. 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.

5. 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/.

6. 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, Email: info@ansi.org Web sites: http://www.ansi.org or http://www.iso.org

7. 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

8. Copies of the Internet Engineering Task Force (IETF) Standard (RFC) documents may be obtained through the web site: http://www.rfc-editor.org/rfc-index2.html

9. Copies of EUROCONTROL documents may be obtained through the web site: http://www.eurocontrol.int/services/specifications-documents Military Handbooks

FAA/DOT Specifications, Standards, Orders, and Handbooks

Other Publications and Specifications

Requirements Program Management Program Management Organization The Contractor must establish and maintain a PMO to manage the contract and subcontracts. The contractor must develop and implement a program management function 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 Equipment (GFE) and Government Furnished Information (GFI), risk management and security.

The Contractor must assign a Program Manager to manage all elements of the contract. The Program Manager will be the point of contact between the FAA and the Contractor in the execution of this program. The Program Manager must have resources, authority, and overall responsibility to ensure efficient and timely program execution and must be the Contractor's focal point for all required program tasks. The Contractor's Program Manager must be prepared to present and discuss the status of contract activities at any time.

Program Management Plan The Contractor must develop an integrated Program Management Plan (PMP) IAW CDRL PM01 to detail the methodologies to ensure that the program management requirements set forth in this SOW are met. The Contractor must implement the methods, processes, and procedures described in the PMP to execute all the requirements of this contract efficiently and effectively.

An integral factor in the success of the program is the Contractor's plans for interaction with the Government. The Contractor must ensure that all interaction is managed and conducted to provide maximum benefit toward successful completion of the program.

CDRL PM01 Program Management Plan (PMP) Program Control The Contractor must continuously monitor the technical performance of this contract, and of all subcontracts.

The Contractor must maintain performance measurement systems and related procedures throughout this contract.

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 select, and upon receiving Government approval, utilize an application to measure and track the status of the following metrics:

1. Project Requirements (Stability Measure)

2. Software Development Progress

3. Requirements Validation Progress

4. Program Trouble Reports (PTR)

5. Risk Management The Contractor must provide the Government with an assessment of program progress or problems at the Program Management Reviews (PMR) and in the Program Management Status Report (PMSR). The PMSR contains the progress of work, status of the program and assigned tasks.

The Contractor must develop and deliver the PMSR IAW CDRL PM03.

CDRL PM03 Program Management Status Report (PMSR)

Risk Management The Contractor must identify Risks, Issues, and Opportunities (RIO) IAW 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, IAW the guidance provided in Attachments J-XX through J-YY.

Specific risk management functions must include the following:

1. Identification of known and potential RIOs

2. Assessment of risks, including a relative ranking IAW the program impact and likelihood scales described in Attachment J-XX

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

4. 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

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

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

7. 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 PM03), and the status and mitigation plans must be presented and discussed at the PMRs.

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.

Planning and Reporting Contract Work Breakdown Structure (CWBS) The Contractor must prepare and deliver the Contractor Work Breakdown Structure (CWBS) IAW CDRL PM02.

CDRL PM02 Contractor Work Breakdown Structure (CWBS) Earned Value Management System (EVMS) The Contractor must have a documented and validated Earned Value Management System (EVMS) and provide status as part of the PMSR (CDRL PM03). The Contractor EVMS must comply with EIA Standard “Earned Value Management System”, EIA-748.

The Contractor must utilize the EVMS to manage and document:

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

2. Timely baseline establishment and control

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

4. Objective measurement of accomplishment against the plan at levels where the work is being performed and IAW the approved CWBS

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

6. Analysis of significant variances

7. The implementation of management actions to mitigate risk and manage cost and schedule performance The Contractor's EVMS must:

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

2. Incorporate changes to the contract budget base on approval of the Government

3. Establish constraints to preclude subjective adjustment of data to ensure performance measurement remains realistic. Unless the FAA 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

4. 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 The Contractor must prepare and submit Contract Funds Status Reports (CFSR) IAW CDRL PM08, and PMSR (CDRL PM03), utilizing the EVMS. EVMS must be reported at monthly PMRs. The EVMS information must include integrated subcontractor information in a manner to prevent any lag in reporting.

The Contractor must provide a monthly Financial Status Report, IAW CDRL PM09, clearly stating the financial status by CLIN and reporting all Contractor’s cost 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.

CDRL PM08 Contract Funds Status Report (CFSR) CDRL PM09 Financial Status Report Integrated Master Schedule (IMS) The Contractor must develop an Integrated Master Schedule (IMS) IAW CDRL PM04. The Contractor must ensure that the IMS portrays an integrated schedule plan to meet the milestones and delivery requirements of this contract. The Contractor must identify the specific milestones constituting the critical path and must report on these at each PMR.

The Contractor must present the current version of the IMS at each PMR. The IMS schedule information must include integrated subcontractor information in a manner to prevent any lag in reporting.

CDRL PM04 Integrated Master Schedule Integrated Baseline Review (IBR) The Contractor must 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 Government intent is to follow the FAA Program Level Integrated Review Guide, Attachment J-XX. The Contractor must provide all required documentation 30 days prior to the IBR. The IBR must ensure that appropriate reporting levels have been identified and variance thresholds agreed to by the Government and Contractor. The IBR must be held within 90 days after contract award. The IBR must include performance measurements for subcontractors. The Contractor must also demonstrate that its 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. The Contractor may use “estimated Subcontractor actuals” in keeping with standard EVMS practices. However, the Contractor must explain, at the IBR, methods for record keeping that ensure accuracy.

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

Conferences, Reviews, and Meetings The Contractor must conduct conferences, reviews, and meetings IAW the SOW. The Contractor must provide a Meeting Agenda IAW CDRL PM06 and supporting documentation for each conference, review, and meeting prior to the event.

At each management 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 such meetings required for management of the contract. The Contractor must include current efforts to maintain requirements traceability and architectural integrity.

The Contractor must submit Meeting Minutes IAW CDRL PM07 after each conference, review, and meeting.

The Contractor must respond to all assigned action items with either a proposed closure or a plan for closure in the Meeting Minutes (CDRL PM07). The Contractor must track the status of all action items.

The Contractor must not consider conferences, reviews, and meetings complete until approval of the final minutes by the Government.

CDRL PM06 Meeting Agenda CDRL PM07 Meeting Minutes 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. The conference will be held to thoroughly review the contract and SOW to ensure all parties have a clear understanding of all contractual requirements. 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:

1. Discuss proposed resources and efforts to meet contractual requirements

2. Discuss key contractual requirements

3. Discuss Contract type, options, deliverables and delivery schedule

4. Describe Inspection and acceptance provisions

5. Discuss Invoicing and billing procedures

6. Discuss pre-approval of Contractor’s travel by the COR

7. Discuss any questions raised by the Government

8. Introduce Key Personnel to Government counterparts and discuss roles of the Key Personnel and their Government counterparts

9. Discuss and provide a tour, if possible, of Contractors’ Facilities (production, testing, etc.)

10. Discuss any enhanced capabilities identified in the Contractor's proposal. The Government will identify which, if any, enhanced capabilities, and requirements from the Contractor's System/Subsystem Specification (SSS) that must be included at System Requirements Review (SRR)

11. Discuss any product upgrades and enhancements

12. Discuss information exchange and a file naming convention for all documents stored in the Data Management/Document library

Program Management Reviews (PMR) The Contractor must conduct and administratively support PMRs on a monthly basis 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 PM03). The Government reserves the right to reduce the frequency of the PMRs throughout the contract period of performance. The FAA 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 PM07) 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:

1. Review of overall program status and focus areas

2. Review of IMS and reasons for any variances

3. Review of EVMS and reasons for any variances

4. Review program RIOs

5. Review the Contractor Funds Status Report

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

7. A description and status of:

a. Program Trouble Reports (PTR)

b. Engineering Change Proposals (ECP)

c. Request for Variance

d. Action Items

e. Open Items/Summary Technical Interchange Meetings (TIM) The Contractor must conduct and administratively support TIMs on a monthly basis 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 performance. The FAA 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.

Quality Assurance The Contractor must establish and maintain a documented quality management program IAW 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 SAE AS9100D Quality Management Systems requirements for Aviation, Space, and Defense Organizations; and DO-278A Software Standard for Non-Airborne Systems Assurance Level 4 for the development of computer software.

The Contractor must prepare a Quality System Plan (QSP) IAW CDRL QA01. The Contractor is responsible for incorporating as part of its subcontracts all applicable Quality Assurance (QA) provisions of this contract to its subcontractors and vendors. In addition, the Contractor’s QSP must specifically address how the Contractor will ensure subcontractor, vendor, and supplier compliance to the applicable requirements of this contract. For example, the Contractor ensures that subcontractor and vendor-supplied spare parts are subjected to incoming inspection to verify the Part/Number (P/N), National Stock Number (NSN), Serial Number of the part(s) being delivered, and any other applicable documentation that demonstrates physical, functional, and performance parameters.

CDRL QA01 Quality System Plan Configuration Management (CM) Program The Contractor must use a configuration management system for the control of all elements of the SMR4, including hardware, software and firmware, documentation, test equipment, space, physical media, and physical parts. The Contractor must maintain configuration control of the hardware to the LRU Level and software to the current version level.

The Contractor must establish, implement, and maintain a configuration management (CM) program using Electronic Industries Association (EIA) Configuration Management Requirements For Defense Contracts, EIA-649-1 as guidance. Additionally, the CM program must fulfill the requirements of RTCA DO-278A Software Standard for Non-Airborne Systems Assurance Level 4. 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.

Configuration Management Plan (CMP) 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 CMP must be developed IAW CDRL CM01.

The CMP must describe the Contractor’s CM Program including responsibilities, methodology and procedures for baseline identification, configuration control and audit, and status accounting of software and hardware, documentation, support equipment, firmware, and databases.

The processes defined in the CMP must be used by the Contractor for control of all configuration items (e.g., hardware, firmware, software, physical media and parts, documentation, space, and adaptation parameters) and to maintain the integrity and traceability of its configuration. A software release management and approval process must be part of the CMP along with how flaw remediation is performed in relation to the Configuration Management Process.

CDRL CM01 Configuration Management Plan (CMP) Configuration Identification The Contractor must recommend Configuration Items (CI) using the guidelines provided in EIA-649-1. A CI is an aggregation of hardware and associated software/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.

The Contractor must use and maintain the Contractor CM system to provide a definitive basis for control and status accounting to validate the status of approved CI throughout the SMR4 system life cycle. The documentation and repositories for the developmental and production configurations must remain the Contractor's responsibility for the period of performance of this contract.

The Contractor must develop and maintain a Program Document Library that retains all documentation for identification, control, and status accounting of all CIs throughout the program life cycle. The Contractor must assign a discrete part number or item identification number to each CI.

The Contractor must assign a discrete part/item identification number at the LRU level until such time as the product baseline is established. At that point, parts must be re-identified only upon Government approval whenever a non-interchangeable condition is created. 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.

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.

Configuration Baselines The Contractor must use and maintain configuration baselines and the required documentation to support these baselines using EIA-649-1 as guidance.

Functional Baseline: Consists of the hardware and software system design. The Functional Baseline must be approved and established upon CDR approval.

Product Baseline: Consists of the hardware and software CIs. The Product Baseline must be established prior to start of formal Development Test (DT).

The Contractor must provide and maintain a Product Baseline Index Report IAW CM07 that documents the product baseline.

CDRL CM07 Product Baseline Index 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 product baseline.

The Contractor must document any proposed changes to the Functional and Product Baselines in a Program Trouble Report (PTR) (CDRL SE11), 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 COTS and at the component level for all other CIs.

The Contractor must prepare and deliver Engineering Change Proposals (ECP) (CDRL CM03) and Requests for Variance (RFV) (CDRL CM04), as required and directed by the CCB.

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 updated to reflect the appropriate baseline. Affected documentation includes design and interface documents, training material, technical documentation, and other Integrated Logistics Support (ILS) documentation.

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

Engineering Change Proposal (ECP) The Contractor must implement an effective engineering change control program. The Contractor must generate ECPs IAW CDRL CM03 as directed by the CCB and submit them to the Government for approval. A PTR (CDRL SE11) with a corrective action directing the Contractor to generate an ECP must be approved by the CCB in order for the Contractor to initiate an ECP. Government approval of each ECP must occur prior to its implementation and incorporation in the baselined requirements, documents, or design.

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. Each change description must include the exact proposed changes by citing the words/information to be changed in “From/To” format, to easily distinguish proposed changes from approved documentation contents.

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 Product Baseline. Once the ECP has been successfully tested, the ECP is closed by the CCB.

CDRL CM03 Engineering Change Proposal (ECP) Request for Variance (RFV) The Contractor must submit a Request for Variance (RFV) IAW CDRL CM04 to request permission and receive approval from the Government to deviate from, not conform with, or deliver a production departure from the Government requirements or an approved baseline. The departure from the approved baseline must be specified as applicable to 1) a specific unit, 2) a specific number of units, or 3) a specific period of time without requiring revision of the approved baseline. Government approval of an RFV requesting permission to depart from a requirement(s) indicates Government acceptance of the item “as is”.

A PTR (CDRL SE11) with a corrective action directing the Contractor to generate an RFV must be approved by the CCB in order for the Contractor to initiate an RFV.

CDRL CM04 Request for Variance Configuration Audits The Contractor must prepare for and support configuration audits using EIA-649-1 as guidance. The Contractor must prepare and submit a Configuration Audit Plan for FCA/PCA IAW CDRL CM02, 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 Plan. The Contractor must prepare and submit a Configuration Audit Summary Report IAW CDRL CM05 documenting the findings of the FCA/PCA.

CM02 Configuration Audit Plan CM05 Configuration Audit Summary Report 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 Product Baseline meets all requirements contained in the Test Verification Requirements Traceability Matrix (TVRTM).

FCA entrance criteria must include:

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

2. 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 PE07) Successful completion of the FCA must include validation by the Government that all requirements have been successfully verified.

At a minimum, the following documents must be audited:

1. TVRTM (CDRL TE02)

2. System Subsystem Specification (SSS) (CDRL SE04)

3. Test Procedures (CDRL TE04)

4. Test Reports (CDRL TE05)

5. PTRs (CDRL SE11)

6. ECPs (CDRL CM03)

7. RFVs (CDRL CM04)

8. Analysis Reports (CDRL TE03)

9. Test with Data Reports (CDRL TE06)

10. Requirements Design Review Meeting Minutes (CDRL PE07) Physical Configuration Audit (PCA) The Contractor must support a Physical Configuration Audit (PCA) upon completion of DT on a first article SMR4 system at the Contractor facility. Subcontractor, vendor, and supplier PCAs must be performed for all CIs.

At a minimum, the following documents must be approved by the Government prior to start of the PCA:

1. Software Design Description (SDD) (CDRL SW01)

2. Software Version Description (SVD) (CDRL SW02)

3. Software Programs (CDRL SW06)

4. System Adaptation Description Documents (CDRL SE08)

5. Technical Instruction Books (TIB) (CDRL TD04)

6. Program Trouble Reports (PTR) (CDRL SE11)

7. Engineering Change Proposals (ECP) (CDRL CM03)

8. Request for Variance (RFV) (CDRL CM04)

9. Engineering Production Drawings (TD02)

10. Logistics Management Information (LM02) Successful completion of the PCA must include, but not be limited to:

1. Successful conclusion of the FCA

2. Verification by the Government that the documented product conforms with specified requirements

3. Verification by the Government that the documentation conforms to the physical SMR4 Configuration Status Accounting (CSA) Information The Contractor must maintain a Configuration Status Accounting (CSA) Information System to ensure accurate identification of each CI. The Contractor must ensure that the CSA information is available for review by the Government, as requested.

The Contractor must generate Configuration Status Accounting Reports (CSAR) IAW CDRL CM06 to ensure the configuration of development and implemented systems and that delivered documentation accurately describes the system/hardware configuration. The Contractor must record and report the following information:

1. Current approved configuration documentation associated with each configuration item

2. Status of proposed engineering changes and requests for variance from initiation to approval and status of implementation

3. Results of configuration audits including disposition of actions

4. Traceability of changes

5. Status of the implementation of changes at all locations

6. Identifiers of electronic documentation and software that have been delivered The Contractor must use the CSARs to provide traceability of any change through the change control process. The Contractor must present status at PMRs as updates occur.

CDRL CM06 Configuration Status Accounting Report (CSAR) Data Management/Document Library The Contractor must establish a data management program to maintain all contractually required and supporting documentation and correspondence related to schedule, development, design, test, implementation, management of equipment, and production documentation. The Contractor must document the data management process in the CMP (CDRL CM01).

Details of the data management process must include a process for collecting, monitoring, reporting, status accounting, long-term preservation, interoperability with Government systems and exchange, and a cross-matrix of changes, additions, or deletions of data item deliverable contents. All data items must be configuration-managed by the Contractor.

The Contractor must control the generation, receipt, approval, storage, and delivery of subcontractor data. The Contractor must also ensure that the subcontractor data meets requirements of the contract and is integrated into contract deliverables.

The Contractor must establish and maintain an electronic document library with all documents developed by the Contractor and subcontractors as well as any Government Furnished Information (GFI). The list of documents included in the library must be available upon Government request. At a minimum, the Contractor's Document Library must contain:

1. Copies of all correspondence between the Contractor and the Government

2. Copies of all briefings

3. All configuration management documentation

4. Action items

5. PTR Database

6. Site Hardware and Software Inventory Lists

7. All CDRL deliverables

8. All test artifacts, including test logs, test input files, test output files, and as-run Test Procedures.

The Contractor must place documents in the Contractor's library concurrent with the document delivery to the Government.