Attachment1-PerformanceWorkStatement(PWS)NSCCANSATE22Dec2020.pdf

NSCCA/NSATE Attachment 1 12/22/2020

NUCLEAR SAFETY CROSS-CHECK ANALYSIS (NSCCA)/ NUCLEAR SAFETY ANALYSIS AND

TECHNICAL EVALUATION (NSATE)

ii

DEPARTMENT OF THE AIR FORCE

AIR FORCE NUCLEAR WEAPONS SYSTEM DIRECTORATE

(AFNWCSD)

PERFORMANCE WORK STATEMENT (PWS)

NSCCA/NSATE Attachment 1

NUCLEAR SAFETY CROSS-CHECK ANALYSIS (NSCCA)/ NUCLEAR

SAFETY ANALYSIS AND TECHNICAL EVALUATION (NSATE)

12/22/2020

PREPARED BY:

NSCCA/NSATE Program Manager

TECHNICAL EVALUATION (NSATE)

iii

TABLE OF CONTENTS

1 PURPOSE AND BACKGROUND

1.1 Purpose

1.2 Background

2 CONTRACT PERFORMANCE OBJECTIVES

2.1 Applicable Documents

3 REQUIREMENTS SUMMARY

3.1 Nuclear Safety Cross Check Analysis/Nuclear Safety Analysis and Technical

Evaluation

3.1.1 Nuclear Certification Plan for Software Evaluations

3.1.2 Analysis, Test, Recommendation, and Demonstration for Nuclear Safety Cross-

Check Analysis

3.1.3 Analysis, Test, Recommendation, and Demonstration for Nuclear Safety Analysis and Technical Evaluation (NSATE)

3.1.4 Nuclear Safety Analysis and Technical Evaluation

3.2 Nuclear Surety

3.3 Engineering Services

3.3.1 Systems Engineering

3.3.2 Data Rights

3.3.3 Data Management

3.4 Tools Sustainment

3.4.1 CMMI

3.4.2 Facilities

3.4.3 GFP/GFE

3.4.4 Software Development Plan (SDP)

3.4.5 Hardware/Software/Firmware

3.4.6 Simulations/Test Stations

3.4.7 Commercial Off the Shelf (COTS) Items

3.4.8 COTS Licenses

3.5 Program Support

3.5.1 Program Management

3.5.2 Transition Plan

3.5.3 Phase-Out Transition

3.5.4 Business and Financial Management

3.5.5 Commercial Small Business Involvement

3.5.6 Travel

3.5.7 Contractor Manpower Reporting

4 AUDITS OF CONTRACTOR PERFORMANCE

4.1 Service Summary

Table 1. – Services Summary Matrix

5 PROPERTY MANAGEMENT

TECHNICAL EVALUATION (NSATE)

iv

5.1 Government-Furnished Property/Government-Furnished Equipment (GFP/GFE)

6 GENERAL INFORMATION

6.1 Security Requirements

6.2 Quality Assurance

6.3 Contracting Officer Representative (COR)

6.4 Records

6.5 Environmental Controls

6.6 Government Observations

6.7 Safety Requirements

6.8 Continuation of Essential DoD Contractor Services During Crisis

7 APPENDICES

NUCLEAR SAFETY CROSS-CHECK ANALYSIS (NSCCA)/ NUCLEAR SAFETY ANALYSIS AND TECHNICAL

EVALUATION (NSATE)

1 PURPOSE AND BACKGROUND

This Performance Work Statement (PWS) defines engineering services the contractor shall perform that will directly and indirectly support nuclear surety certification of system software and hardware for

Nuclear Safety Cross-Check Analysis/Nuclear Safety Analysis and Technical Evaluation

(NSCCA/NSATE). NSCCA/NSATE is defined in AFMAN 91-119, and it is expected that all references in this PWS refer to the AFMAN 91-119 definition as a process that is primarily an analysis of code and other evaluation techniques to prove safety and surety of the weapon system. Test, simulations, and other evaluation techniques are used as input for a thorough software verification process. In this context a test failure does not imply an NSCCA failure. It is simply an input to the analysis to verify that the code is operating as expected. An NSCCA product output is a recommendation, based on independent analysis, to the program and the USAF Safety Center regarding the safety and surety of the elements of the program under review.

The work efforts for this contract will be identified in specific task orders and encompass the requirements levied by:

The following organizations. MMIII SPO, AFSEC and/or AF NWSSG.

The following policies. AFI 91 series – including: AFI 91-101, AFMAN 91-118 and AFMAN 91-

119.

AFNWC Nuclear Certification Requirements Plans (CRPs).

Services deemed beneficial to software nuclear surety evaluations, including special studies, tools development, and sustainment activities.

Each task order may address more specific task requirements, project scheduling, and other related performance criteria, as applicable.

Note: For the purpose of this PWS, software includes hardware, embedded software, commercial-off-the-shelf (COTS) software, firmware, associated software operating environment, and data parameters. Department of Defense (DoD) Instruction 5230.24, Distribution Statements on

Technical Documents, Enclosure 4, Table 5, identifies six (6) authorized distribution statements for

Scientific and Technical Information (STINFO). The Contractor shall mark all technical data, regardless of media or form, with the appropriate STINFO markings (i.e., distribution statement, export control warning [if applicable], and destruction notice) as specified on the DD Form 1423-1, Contract Data Requirements List (CDRL). For written or printed material, the STINFO markings shall appear in full text on the front cover/title page and the abbreviated markings shall appear on subsequent pages as specified in the CDRL. Distribution statements shall include all applicable

“reasons” based on the contents of the document. The “date of determination” within each distribution statement shall reflect the date the CDRL was signed. The Controlling DoD Office

(CDO) will review all technical data (e.g., technical reports, test reports, final summaries, and briefings) prior to finalization to ensure the correct STINFO markings (i.e., distribution statement, export control warning [if applicable], and destruction notice) are applied to all documents. A distribution statement designation is distinct from, and in addition to, a security classification marking applied in accordance with (IAW) DoD Manual 5200.01, Volume 2, DoD Information

Security Program: Marking of Classified Information.

EVALUATION (NSATE)

1.1 Purpose

The purpose of the AFNWCSD NSCCA/NSATE Program is to maintain the nuclear safety and security of United States Air Force (USAF) ICBM Weapon Systems. This PWS identifies the contract requirements necessary to perform independent analyses of new or modified software requiring nuclear certification. These requirements help ensure there is no sabotage or system degradation to the nuclear surety of the ICBM weapon systems due to nuclear critical software updates and determine if the critical signal propagation are technically valid and safe. This PWS also outlines services the contractor shall perform to maintain and improve tools used in support of

NSCCA/NSATE processes.

This PWS describes the scope of services the NSCCA/NSATE contractor shall perform; it is not intended to suppress innovative ideas or approaches for performing required services that adhere to defined guidance specified in this contract. Unless otherwise specified, “Government” refers specifically to the Air Force Nuclear Weapon System Directorate (AFNWC) and “contractor” refers to the NSCCA/NSATE contractor. All references to other contractors will be specifically stated and clarified in associated task orders. Tools task order will cover new and existing NSCCA task orders.

1.2 Background

The Minuteman III (MMIII) is a mature weapon system that is in the Operations and Support Phase of its life cycle. As a critical leg in the strategic nuclear triad, the ICBM Weapon System requires continued sustainment of the critical software to ensure operational capabilities are maintained and new war-fighter requirements are implemented and independently certified for operational nuclear surety. Ground Based Strategic Deterrent (GBSD) is a new weapon system that may require transitional support from the NSCCA/NSATE contractor. The ICBM weapon system software requires updates and independent nuclear certification to provide a supportable and functional weapon system through 2039. The NSCCA/NSATE contractor independently assesses that nuclear certified and critical software will not adversely affect critical signal initiation and propagation through the missile system, will only perform as intended by the design, that there have been no acts of sabotage or unintended functionality, and the software complies with applicable requirements of AFMAN 91-118 and AFMAN 91-119, and will not cause a violation of the four

DoD nuclear surety standards detailed in DoD 3150.02.

EVALUATION (NSATE)

2 CONTRACT PERFORMANCE OBJECTIVES

The AFNWC/NM is expected to issue a Requirements contract and will issue task orders for direct services, studies, secure facilities or other services that support nuclear surety evaluations.

Contractor responsibilities shall include fulfilling the requirements of the basic contract and specific task assignment as designated by individual task orders. When performing individual task orders, the contractor shall use an integrated approach that considers effects of all task orders, systems, and system interactions of all software to efficiently meet all requirements of each individual task order.

The Government will identify a contract-wide Contract Data Requirements List (CDRL) that will capture all possible CDRLs associated with this contract. This list will be Attachment 2 of the

Basic contract. Each task order will specify which of the CDRLs the contractor shall perform for each task order.

2.1 Applicable Documents

Compliance and reference documents related to specifications, standards, handbooks, regulations, instructions and tables applicable to the work the contractor shall perform under this contract are listed in Appendix B: Applicable Compliance/Reference Documents.

The contractor shall comply with the current versions of applicable regulatory and compliance documents throughout the period of performance of this contract. Previously identified CDRLs will remain contractually required.

EVALUATION (NSATE)

3 REQUIREMENTS SUMMARY

The contractor shall perform tasks in accordance with separately issued task orders providing engineering, technical, and support services, as specified therein.

3.1 Nuclear Safety Cross-Check Analysis/Nuclear Safety Analysis and Technical Evaluation

Verification of critical signal initiation or propagation are accomplished through NSCCA/NSATE code review, simulation testing, and deep analysis (for example, at a previous Certification

Demonstration there were discussion there were discussions concerning areas that had two sectors of difference when the CD was run in the bit-for-bit. The Government needs to know the reasons why) [CDRL A059-1, Technical Report - Study/Services (Deep Analysis)]. Although these evaluations use many similar techniques, they typically have different requirements, and, consequently, the analysis and reporting are written according to the corresponding requirements.

Since NSCCA affects software that is nuclear critical, the contractor needs to consider that a significant majority of the effort under this PWS will be slanted toward NSCCA analysis and

NSATE efforts will be a lesser portion of the contract. NSCCA efforts typically involve programs that support nuclear critical software. The analysis under NSCCA/NSATE ensures compliance with corresponding requirements levied on the software being studied. In accordance with an approved Organizational Conflict of Interest (OCI) Plan (Government document) and

Independence Assurance Plan (contractor document), NSCCA/NSATE will be performed by an organization that is technically, managerially, and financially independent of the developer. The

AF Safety Center, currently AFSEC/SEW, will make the final determination regarding independence requirements.

Nuclear safety design certified software is evaluated according to the Government Nuclear Safety

Software Verification Plan (NSSVP). AFMAN 91-119, Safety Design Criteria for Nuclear

Weapon Systems Software, provides requirements and criteria for NSCCA evaluation.

Requirements for software evaluation can change according to the current Air Force directives.

All current Air Force nuclear certification requirements for MMIII/GBSD, whether referenced in this document or not, must be integrated and followed by the NSCCA contractor as soon as declared in force unless exempted by waiver. The publication date of the AFMAN 91-119 at the time of signature date of the NSSVP, for each task order, determines the version of AFMAN 91-

119 which shall be used. The task orders shall comply with the NSSVP, to include all applicable

AFI and AFMAN guidance. [CDRL A008-5, Work Management Plan (Nuclear Safety

Software Verification Plan)]

NSCCA and NSATE evaluations will parallel the development lifecycle with incremental deliveries of requirements, design, and code changes from the program and developers as defined at task order level.

3.1.1 Nuclear Certification Plan for Software Evaluations

The contractor shall provide and implement a NSSVP at the task order level that includes criteria for new or modified ICBM hardware and software components, systems, subsystems, support equipment, facilities, special test, and maintenance programs. [CDRL

A008-5, Work Management Plan (Nuclear Safety Software Verification Plan)]

EVALUATION (NSATE)

3.1.1.1 The NSSVP for each task order shall contain the following information:

Nuclear Safety Objectives (NSO) number

Text of NSO

Corresponding reference from the AFMAN/AFI from which the

NSO is derived

What could cause a violation to that NSO

Any clarifying comments pertaining to the NSO

A mapping of the NSO to the different system computer software configuration items (CSCI) within the weapon system that is being developed/modified within the task order

Rationale for NSOs not allocated to specific CSCIs

Nuclear Safety Requirements (NSR) that are derived from the NSOs and their allocation to each CSCI

Current AF and industry-standards for security and cybersecurity implementation

3.1.1.2 The contractor shall develop and review NSOs and NSRs. NSOs and NSRs for verification at the task order level shall meet all requirements IAW AFMAN 91-

119, Safety Design Criteria for Nuclear Weapon Systems Software; AFMAN 91-

118, Safety Design and Evaluation Criteria for Nuclear Weapon Systems; their current parent or subordinate Nuclear Surety regulations referenced in AFMAN

91-119 and AFMAN 91-118; or successor documents to these documents. At the direction of the Government: [CDRLs A008-5, Work Management Plan

(Nuclear Safety Software Verification Plan); A059-2, Technical Report -

Study/Services (NSOs & NSRs)

The contractor shall document and provide details of the NSOs imposed on the design of the software by the safety standards in AFMAN 91-

119.

The contractor shall ensure the NSSVP includes traceability analysis to demonstrate that all NSOs are represented in the NSRs and that all

NSRs are derived from one or more NSOs.

The contractor shall provide traceability from the developer’s design and code to the NSRs.

EVALUATION (NSATE)

3.1.2 Analysis, Test, Recommendation, and Demonstration for Nuclear Safety Cross-

Check Analysis

The contractor shall provide independent NSCCA of ICBM nuclear critical software at the task order level by conducting both manual and automated tests, analyzing test results, performing demonstrations for each software item, and identifying discrepancies. [CDRLs

A059-3, Technical Report – Study/Services- Nuclear Safety Software Verification

Report (NSSVR); A035, Deficiency Report].

The contractor shall provide AFSEC/SEW a Nuclear Safety Software Verification Report as detailed in AFMAN 91-119 and required by CDRL. [CDRL A059-3, Technical

Report - Study/Services (Nuclear Safety Software Verification Report)]

The contractor shall provide NSATE NSSVR as required by AFMAN 91-119.

The NSSVR shall describe the testing accomplished, deficiency reports (DR) generated, and a recommendation for certification.

The NSSVR shall include a full test report that documents the tests in detail, the test procedures used, and the results for each step within the test procedures.

The NSSVR shall document the step-by-step procedures for the certification demonstration with the results for each step in the procedures, including the signatures of all attendees.

3.1.2.1 The contractor shall provide a cross-reference matrix in the NSSVR, or Test Plan and Test Procedures, to trace NSOs and NSRs to test and analysis procedures.

[CDRLs A059-2, Technical Report - Study/Services (NSOs & NSRs); A059-

3, Technical Report - Study/Services (Nuclear Safety Software Verification

Report); A060, Test Plan]

3.1.2.2 The contractor shall evaluate the developer Software Requirements Specification

(SRS), Interface Requirements Specifications (IRS), Interface Design Description

(IDD) if applicable, and Interface Control Documents/Drawings (ICD) to determine their compliance to the NSOs and NSRs. [CDRLs A059-3, Technical

Report - Study/Services (Nuclear Safety Software Verification Report);

A060, Test Plan; A061 Test Procedure]

3.1.2.3 The contractor shall provide comments or issues from initial evaluations of these documents to the Government prior to the next Government-facilitated working group throughout the development lifecycle. [CDRL A059-4, Technical Report

– Evaluation Issues]

3.1.2.4 The contractor shall support discussions and resolution of comments within

Government-facilitated working group meetings and other specific meetings as requested by the Government.

3.1.2.5 The contractor shall provide to the Government detailed Test Procedures, including: test inputs, interfaces between operational/simulated system elements

EVALUATION (NSATE)

and external expected environment, test results, expected results, analysis, and criteria for evaluating results. [CDRL A059-3, Technical Report -

Study/Services (Nuclear Safety Software Verification Report)]

3.1.2.6 Upon completion of testing, the contractor shall provide a nuclear certification recommendation with justification in the NSSVR.

3.1.2.7 The contractor shall provide Deficiency Reports (DR) that identify components that contain improper design, code, or instructions for nuclear critical software that could violate nuclear safety criteria defined in AFI 91-101, Air Force

Nuclear Weapons Surety Program and any parent or subordinate ICBM Nuclear

Surety regulations. [A035, Deficiency Report]

3.1.2.8 The contractor shall participate as required in Software Screening Boards (SSBs) and accept SSB adjudication of DR conflicts between developer and contractor.

[A035, Deficiency Report]

Note: The Government has established a SSB process detailed in OI 91-14, Discrepancy Screening Boards

3.1.2.9 The contractor shall respond to Government DR comments and document responses in the NSSVR.

3.1.2.10 The contractor shall provide recommendation for closure of DR upon correction by the development contractor.

3.1.2.11 The contractor shall include DRs and their status in the NSSVR.

3.1.2.12 The contractor shall document the test results in the NSSVR. [CDRL A059-3, Technical Report - Study/Services (Nuclear Safety Software Verification

Report)]

3.1.2.13 Under Government Two-Person Concept (TPC) IAW AFI 91-101, Air Force

Nuclear Weapons Surety Program, the contractor shall demonstrate the version of the ICBM nuclear critical software that the Government accepted at PCA contains the exact bit-for-bit code that underwent NSCCA analysis, meets the media format requirements as outlined in relevant Air Force documents, and is delivered according to the required protocols of the receiving organization and the associated program management team.

3.1.2.14 The certification demonstration shall be documented in the NSSVR.

3.1.2.15 The contractor shall ensure the PCA-accepted version of the software is delivered to the Government TPC team that is present for the demonstration.

3.1.3 Analysis, Test, Recommendation, and Demonstration for Nuclear Safety Analysis and

Technical Evaluation (NSATE)

The contractor shall provide an NSATE analysis of ICBM software at the task order level by conducting both manual and automated tests, analyzing test results, performing

EVALUATION (NSATE)

demonstrations for each software item, and identifying discrepancies. [CDRLs A059-3, Technical Report – Study/Services – Nuclear Safety Software Verification Report;

A035, Deficiency Report; A059-5, Technical Report - Study/Services - Nuclear Safety

Analysis and Technical Evaluation (NSATE) Analysis]

The contractor shall provide NSATE NSSVR as required by AFMAN 91-119.

The NSSVR shall describe the testing accomplished, deficiency reports (DR) generated, and a recommendation for certification.

The NSSVR shall include a full test report that documents the tests in detail, the test procedures used, and the results for each step within the test procedures.

The NSSVR shall document the step-by-step procedures for the certification demonstration with the results for each step in the procedures, including the signatures of all attendees.

3.1.3.1 The contractor shall evaluate the developer SRS, IRS, IDD if applicable, and ICD to determine their compliance to the NSOs and NSRs.

3.1.3.2 The contractor shall provide comments or issues from initial evaluations of these documents to the Government prior to the next Government-facilitated working group throughout the development lifecycle. [CDRL A059-4, Technical

Report- Study/Services – Evaluation Issues]

3.1.3.3 The contractor shall support discussions and resolution of comments within

Government-facilitated working group meetings.

3.1.3.4 The contractor shall develop NSRs to serve as the NSATE criteria in the NSSVP for analysis and testing to ensure there is no degradation in nuclear surety or the weapon system due to the software changes. [CDRL A059-2, Technical Report

- Study/Services (NSOs & NSRs); A059-3, Technical Report –

Study/Services- Nuclear Safety Software Verification Report (NSSVR)]

3.1.3.5 The contractor shall provide a sequence flow in the NSSVP cross-reference matrix to track processing threads in the design and code for traceability to the

NSRs. [CDRL A059-3, Technical Report – Study/Services- Nuclear Safety

Software Verification Report (NSSVR)]

3.1.3.6 The contractor shall provide a NSSVP, including: the software test environment, test objectives, tests to be executed, and verification methods. [CDRL A059-3, Technical Report – Study/Services- Nuclear Safety Software Verification

Report (NSSVR)]

3.1.3.7 The contractor shall provide a detailed NSSVP including: test inputs, interfaces between operational/simulated system elements and external environment, expected results, and criteria for evaluating results. [CDRL A059-3, Technical

Report – Study/Services- Nuclear Safety Software Verification Report

(NSSVR)]

EVALUATION (NSATE)

3.1.3.8 The contractor shall conduct analysis of each software item IAW the NSATE

NSSVP.

3.1.3.9 The contractor shall provide DRs that identify components that contain improper design, code, or instructions for nuclear critical software that could violate NSRs as developed IAW Section 3.1.3.4. [CDRL A035, Deficiency Report]

3.1.3.10 The contractor shall participate in the DR resolution process and all issues shall be adjudicated in accordance with current Government procedures and instructions.

3.1.3.11 The contractor shall provide a test report and make recommendation for certification in the NSSVR.

3.1.3.12 The contractor shall include DRs and their status in the NSSVR.

3.1.3.13 The contractor shall document the test results in the NSSVR.

3.1.3.14 The contractor shall perform a certification demonstration (bit-for-bit compare), as identified at task order level, to ensure the NSATE software is an exact match for the software delivered at FCA/PCA.

3.1.3.15 The certification demonstration shall be documented in the NSSVR.

3.1.3.16 The contractor shall ensure the PCA-accepted version of the software in the proper format is delivered to the Government TPC team, if needed, which is present for the demonstration.

3.1.4 Nuclear Safety Analysis and Technical Evaluation

While performing NSCCA or NSATE task orders, the contractor shall identify and document software critical signal initiation and propagation as defined in AFMAN 91-119.

[CDRL A059-7, Technical Report - Study/Services (Software Inefficiencies)]

3.2 Nuclear Surety

The Air Force uses the DoD 3150.02, DoD Nuclear Weapons Surety Program definition for

Nuclear Weapons Surety: Policies, procedures, controls, and actions that encompass safety, security, and control measures which ensure there will be no nuclear weapon accidents, incidents, or degradation of weapon effectiveness during its lifecycle. The contractor shall comply with requirements listed in Appendix B: Applicable Compliance/Reference Documents, as well as all other Nuclear Surety related requirements.

The contractor shall support the Government in maintaining its ICBM Nuclear Certification

Program IAW requirements detailed in DoD Directive (DoDD) 3150.02, DoD Nuclear Weapon

Surety Program, DoD 3150.2-M, DoD Nuclear Weapon System Safety Program Manual, and AFI

63-125, Nuclear Certification Program.

The contractor shall perform the following NSCCA/NSATE tasks on the developers IAW with

AFMAN 91-119, that shows the developer has:

EVALUATION (NSATE)

Developed code to the same standard as the original development

Followed an established process for both management and engineering activities

Used a defined, reproducible, and rigorous safety-critical development process

Used a non-repudiable configuration management system

Protected the configuration management system IAW the Program Protection Plan

3.3 Engineering Services

The contractor shall perform tasks in accordance with separately issued task orders providing engineering, technical, and support services, as specified therein. Task Orders issued will be for one or more of the following services.

3.3.1 Systems Engineering

The contractor shall perform systems engineering activities necessary to accomplish task orders. [CDRL A055, Systems Engineering Management Plan (SEMP)]

3.3.1.1 The contractor shall provide a SEMP that includes or references the following lower-level and subcontractor technical plans, e.g., configuration management, data management, requirements management, and risk management.

3.3.1.2 The contractor shall provide a plan for Risk Management that includes:

identification, assessment, scoring, ranking, and risk handling methods consistent with the NSCCA/NSATE Risk Management Plan. [CDRL A010, Contractor’s

Risk Management Plan]

3.3.1.3 The contractor shall provide a Configuration Management Plan that includes:

configuration identification, control, status accounting, backups, and audits for configuration management baselines, databases, CDRLs, and data prepared for the program. [CDRL A011, Supplier’s Configuration Management Plan]

3.3.1.4 The contractor shall ensure the Configuration Management system is isolated and independent from ICBM Program software developers.

3.3.1.5 The contractor shall maintain and provide to the Government, annually, non-rewriteable media (DVD-R, CD-R, etc.) backups of all NSCCA/NSATE software, source code, configuration files and environment, instructions, and tools necessary for NSCCA/NSATE contract activities and reproduction of

NSCCA related software and tools.

3.3.1.6 The contractor shall perform special studies as identified in task orders. [CDRL

A059-8, Technical Report - Study/Services (Special Studies)]

3.3.1.6.1 The contractor shall support Government technical and cost trade studies to assess the impact of sustainment efforts to nuclear critical software.

EVALUATION (NSATE)

3.3.1.6.2 The contractor shall support TIMs with the developing contractor, associated contractors, and the Government in order to present study results.

3.3.1.6.3 The contractor may recommend/support special studies in support of

NSCCA/NSATE efforts.

3.3.1.6.4 The contractor shall provide a systems engineering overview that includes program impacts on all other domains/programs.

3.3.1.6.5 At Government request, the contractor shall provide technical data, analysis methodology and theory, NSCCA results, tool and methodology documentation and theory for Government understanding and use. Additionally, the contractor shall provide enhanced understanding for Government-furnished equipment and tools. The intent is to benefit the Government’s understanding of technical data, methodology, theory, and tools usage. [CDRL A059-9, Technical

Report - Study/Services (Technical Data Analysis and

Methodology)]

3.3.1.6.6 The contractor shall assist the Government in engineering studies for research on the missile system(s) and allow transparency in contractor analysis and thought process regarding missile and software operations.

3.3.1.7 The contractor shall maintain historical system analysis statistics. Note: The

Government may request contractor to perform a comprehensive NSCCA analysis for system software code and system-wide critical signals. [CDRL

A059-10, Technical Report - Study/Services (NSCCA Analysis)]

3.3.2 Data Rights

All data developed, delivered and/or otherwise provided shall be marked in accordance with DFARS 252.227-7013, 252.227-7014 and 252.227-7015. Ordering of data items on the Data Accession List (DAL) per CDRL A111, Data Accession List (DAL), shall take place using the deferred ordering clause, DFARS 252.227-7027. All data indexed on the

DAL, including drafts of deliverables if applicable, shall be considered delivered for purposes of the DFARS data rights clauses (and subject to the same rights asserted for final deliveries).

However, non-final versions of future deliverables shall not be acceptable for purposes of

Inspection and Acceptance requirements or the DFARS data rights clauses.

3.3.2.1 Identification and Assertion of Data Rights Restrictions

The Contractor shall not deliver or otherwise provide to the Government any technical data or computer software with restrictive markings (or otherwise subject to restrictions on access, use, modification, reproduction, release, performance, display, or disclosure) unless the technical data or computer software are identified in accordance with 3.3.2 requirements.

EVALUATION (NSATE)

3.3.2.2 Task Order Identification, Assertion, and Notification of Data Rights

The Contractor (including subcontractors or suppliers, or potential subcontractors or suppliers, at any tier) shall identify, for each task order issued hereunder, all technical data and computer software that it proposes will be delivered or otherwise provided (including all Option CLINs as if the Option was exercised) with less than Unlimited Rights. The contractor shall ensure the technical data and computer software are identified by specific reference to the requirement in each task order to deliver or provide that technical data or computer software, e.g.

by referencing the associated CLINs, CDRLs, or paragraphs in the PWS.

Identification shall be completed as follows:

3.3.2.2.1 The contractor shall identify such data by providing an update to clause

DFARS 252.227- 7017 during task order proposal and/or negotiations.

The updated clause may be included in section K of each task order.

Restrictions on noncommercial technical data and noncommercial computer software shall be identified pursuant to DFARS 252.227-7013 and 252.227-7014.

3.3.2.2.2 The contractor shall also identify and assert any restrictions for all commercial technical data, i.e., technical data pertaining to a commercial item by providing an update to clause DFARS 252.227-

7017. This includes commercial technologies that are used as platforms, frameworks, base concepts etc. upon which the contractor creates derivative or complementary works.

In accordance with DFARS 227.7102, the contractor shall not be required, except for items described in DFARS 227.7102-1(a), to furnish technical information related to commercial items or processes that is not customarily provided to the public or relinquish to or otherwise provide the Government rights to use, modify, reproduce, release, perform, display, or disclose technical data pertaining to commercial items or processes except for a transfer of rights mutually agreed upon.

The Contractor shall provide copies of all proposed specially negotiated license(s), commercial license(s), and any other asserted restrictions other than Government purpose rights; limited rights; restricted rights;

Small Business Innovative Research (SBIR) data rights for which the protection period has not expired; or Government’s minimum rights as specified in the clause at DFARS 252.227-7015. Licenses for commercial technical data will be included as an attachment to task orders as mutually agreed upon and applicable.

3.3.2.2.3 The contractor shall identify and assert any restrictions for all commercial computer software, including Open Source Software by providing an update to clause DFARS 252.227- 7017. This includes commercial software that is used as a platform, framework, firmware, database or other embedded tools upon which the contractor creates

EVALUATION (NSATE)

derivative or complimentary works. The Contractor shall provide copies of all commercial license(s) with task order proposals. Applicable and mutually agreed upon commercial licenses for software, including any seat limitations, will be included as an attachment to task orders.

3.3.2.2.4 Upon request by the Contracting Officer, the Contractor shall provide sufficient information to enable the Contracting Officer to evaluate any listed assertion of less than unlimited Government rights.

3.3.2.3 Updates to Task Order Identification and Assertions

Except as provided in this paragraph, the Contractor (including subcontractors or suppliers at any tier) shall not supplement or revise task order listings, licenses or assertions required by paragraph 3.3.2.2 unless mutually agreed upon, in writing by the Contracting Officer.

3.3.3 Data Management

Individual task orders will include a separate and specific list of required CDRLs the contractor shall perform. The CDRLs associated with this PWS are the basis of the individual task orders.

3.3.3.1 The contractor shall use secure electronic delivery for CDRL data to the maximum extent practicable using the Government’s Electronic Data Interchange

(EDI) system. The CDRL instructions provided with each task order will outline the Government EDI process.

3.3.3.2 The contractor shall establish and maintain a secure integrated data environment

(IDE) for hosting all technical data and computer software produced in the performance of this contract, unless an IDE is already provided by the

Government. Note: program management information such as cost, risk and schedule data can also be hosted in the IDE. The purpose of the IDE is to create a seamless, collaborative data environment for the contractor and Government team which contains all pertinent data about the project throughout its development and delivery. Functionality shall include data search, back-up, version control and simple interfaces to manage data items. This data management program, including IDE structure, format, processes, and procedures, shall be documented as part of the SEMP [CDRL A055, Systems

Engineering Management Plan (SEMP)].

3.3.3.3 The contractor shall provide the Government (and/or Government support contractors with properly completed Non-Disclosure Agreements) data stored on the integrated digital (or development) environment (IDE) and the ability to download artifacts throughout the term of the contract. The Government reserves the right to witness all Contractor efforts to accomplish requirements and maintains the right to comment on processes. The Contractor shall provide 30 business days’ advance notice of any events, tests, or activity that the

Government identifies as a specific item of interest. Access to the IDE shall

EVALUATION (NSATE)

include the ability to request and receive all data listed in the DAL (CDRL A111, DAL). All items posted to the IDE, including drafts of deliverables that are not final versions, shall be considered delivered for purposes of the DFARS data rights clauses (and subject to the same rights asserted for final deliveries).

However, these non-final versions shall not constitute acceptance for purposes of

Inspection and Acceptance requirements or the DFARS data rights clauses.

3.3.3.4 The contractor shall provide storage and retrieval capability of Government provided historical hard copy data, as identified by task order.

3.4 Tools Sustainment

The contractor shall maintain and modify Government Furnished Property (GFP) (see Section 5:

Property Management) that is provided in support of ICBM NSCCA/NSATE task orders. The objectives of NSCCA/NSATE tools include accelerating analyses, reducing Government Test Lab needs by the NSCCA/NSATE contractor, and the ability to confirm anomalies that are difficult to or cannot be replicated in the Government labs. In the event the both current and old contract have active work involved, the tools contract is expected to provide support for both basic contracts.

3.4.1 CMMI

At a minimum, when developing or sustaining tools, the contractor shall document and follow disciplined, well-defined processes equivalent to the Capability Maturity Model

Integration for Development (CMMI-DEV) Maturity Level 3.

3.4.2 Facilities

The contractor shall maintain a secure facility sufficient to handle all NSCCA contractual requirements. This facility will be used to control, qualify, maintain, and document software analysis and test environments, including maintenance and support of

NSCCA/NSATE tools and laboratories IAW with current/updated Security Requirements referenced in the DD254 requirements.

3.4.3 GFP/GFE

The contractor shall assist with the management of Government Furnished Property (GFP) and Government Furnished Equipment (GFE). Contractor shall ensure accurate and complete property management of NSCCA GFP/GFE, and shall provide reports upon

Government request. [CDRL A108, Government Property Inventory Report]. The

Contractor is expected to assess and help the Government determine the GFP (equipment, material, and information) required to perform all NSCCA functions. Refer to the GFP list titled “Attachment 5: GFP/GFE List” for the NSCCA/NSATE contract’s initial GFP/GFE list. Note: Each time a piece of equipment is added or deleted, the Government will not issue a contract modification to provide an updated GFP list.

EVALUATION (NSATE)

3.4.4 Software Development Plan (SDP)

The contractor shall provide a SDP that documents the requirement and the methodology, plan, process, and procedures the contractor shall follow when developing new tools, modifying tools, and maintaining tools needed to support NSCCA/NSATE analysis and testing. [CDRLs A041, Software Development Plan (SDP)]

3.4.5 Hardware/Software/Firmware

The contractor shall notify and obtain written approval from the Government Tools

Sustainment PM prior to the purchase, use, and/or incorporation of any proprietary and/or commercial software, application, or firmware. Any determination to use proprietary tools, hardware, software, and/or firmware shall be approved by the Government and documented by the Contractor.

3.4.6 Simulations/Test Stations

The contractor shall not coordinate the use of common or simulation tools with any ICBM software development and/or software maintenance organizations, with the exception of unique ICBM system simulations and test stations such as the Strategic Missile Integration

Complex (SMIC) and other already nuclear certified test resources. Other exceptions include unique computer hardware, computing environment compilers, operating systems, assemblers, linkage editors, and similar platform unique software, only if the Contractor is unable to independently obtain a separate copy.

3.4.7 Commercial Off the Shelf (COTS) Items

The contractor shall employ COTS tools, when available, to conduct NSCCA/NSATE analysis and testing. Due to the potential cost savings, the Government will review the inclusion of COTS tools on a case by case basis. The use, inclusion, or integration of

COTS software requires written approval from the Government Tools Sustainment PM.

3.4.8 COTS Licenses

The contractor shall ensure there is no functionality in the tools software (including COTS) that would inhibit tool operations unless explicitly specified and approved by the

Government Tools Sustainment PM. This applies to the periodic need to enter a license code, the presence of a physical key or similar device to enforce licensing conditions.

3.5 Program Support

3.5.1 Program Management

3.5.1.1 The contractor shall maintain technical, managerial, and financial independence from ICBM Program software developers IAW AFI 91-101 and AFMAN 91-

119. The Air Force Safety Center, Weapons Safety Division (AFSEC/SEW), will make the final determination regarding organizational independency requirements. The contractor shall include the Government PM in all

EVALUATION (NSATE)

communications between contractor and developer as required to maintain awareness of necessary developer interactions.

3.5.1.2 The contractor shall complete and submit an Independence Assurance Plan (IAP) addressing technical, managerial, and financial independence from ICBM

Program software developers. [CDRL A008-2, Work Management Plan

(Independence Assurance Plan)]

Note: In order to maintain technical independence, the ICBM Program software developer contractors shall not have access to the NSCCA contractor’s processes, Test Plans, Test Procedures, and NSSVR.

3.5.1.3 If the contractor must conduct on-site (developer or Government facilities) testing, as no other alternative exists, then the testing must be done with

AFNWCSD representatives (or approved alternate Government representative) present to ensure independence is maintained.

3.5.1.4 The contractor shall provide a Management Plan that is approved by the

Government and includes the contractor organization, practices, processes, techniques, and management to be used during the execution of the contract.

[CDRL A008-1, Work Management Plan]

3.5.1.5 The contractor shall establish and maintain an organizational team structure possessing the knowledge, skills, and experience capable of performing all

NSCCA/NSATE requirements IAW this PWS and all relevant AFIs and

AFMANs. This team structure shall be subject to periodic review by the

Government.

3.5.1.6 The contractor shall maintain technical personnel staffing per Labor Category

Descriptions. The contractor shall provide replacement personnel within 30 business days of occurrence of vacancy (Attachment 4, Labor Category

Descriptions).

3.5.1.7 The contractor shall notify the Government Program Manager (PM) of any

Senior Technical/Program personnel changes during the lifetime of this contract.

In the event that personnel do not meet the education or experience requirement defined in the Labor Category Descriptions, a waiver is required. Waivers may be granted and approved by the Government PM on a case-by-case basis. Waivers will be granted for no longer than one year at a time, and waivers will need to be reviewed annually. Notifications and waiver requests shall be in writing and must occur within 10 business days of personnel changes.

3.5.1.8 The contractor shall provide monthly program status reports and shall present reports to the Government at Program Management Reviews (PMR). These reports shall be presented at the PMRs at the task order level. [CDRL A026, Status Report]

EVALUATION (NSATE)

3.5.1.8.1 PMRs shall include, but not be limited to, milestone progress and status of risks in order to minimize technical, cost, and schedule impacts to the contract.

3.5.1.8.2 The contractor shall request Government Program Management team approval of meeting methods (e.g., in- person meetings, videoconferencing, etc.) at least 15 business days prior to meeting.

3.5.1.8.3 The contractor shall request Government Program Management team approval of meeting agenda items at least 15 business days prior to conference. [CDRLs A002, Conference Agenda (Meeting Agenda);

A003, Briefing Material]

3.5.1.8.4 The contractor shall generate meeting minutes from the PMRs and deliver the meeting minutes to the Government Program Management team within 10 business days after the PMR completion. [CDRL A004, Report, Record of Meeting Minutes]

3.5.1.9 The contractor shall provide an Integrated Program Management Report

(IPMDAR). [CDRL A001, Integrated Program Management Data and

Analysis Report (IPMDAR)]

3.5.1.10 At the request of the Government, the contractor shall support PMRs, Technical

Interchange Meetings (TIM), working group meetings, Software Specification

Reviews (SSR), Software Design Reviews (SDR), Preliminary Design Reviews

(PDR), Critical Design Reviews (CDR), Test Readiness Reviews (TRR), Functional Configuration Audits (FCA), Physical Configuration Audits (PCA) and other meetings with ICBM development contractors, other MMIII-managed contractors, associated contractors, and the other Government ICBM organizations. These meetings will be identified at the task order level.

3.5.1.11 The contractor shall be aware of the ICBM Program software developer schedules and provide NSCCA/NSATE schedule updates to the Government as required. [CDRL A001, Integrated Program Management Data and Analysis

Report (IPMDAR)]

3.5.1.12 Quality of work and level of support shall meet task requirements. Work shall require little or no rework and services shall meet or exceed expectations.

Deliverables shall be complete and accurate to meet customer objectives.

3.5.1.13 Deliverables shall be completed IAW with the Task Order CDRLs.

3.5.1.14 Contractor shall provide program funding and status information at the task order level in a clear, organized manner. [CDRL A018 Contract Funds Status

Report (CFSR)]

3.5.1.15 Contractor shall provide recovery plans which clearly describe the necessary steps and estimated timelines associated with 100% of important issues/delays

EVALUATION (NSATE)

and of significant issues/delays. [CDRL A008-3, Work Management Plan

(Recovery Plan)]

3.5.1.16 The contractor shall provide a Performance and Cost Report. [CDRL A020, Performance and Cost Report]

3.5.2 Transition Plan

3.5.2.1 The contractor shall provide a Transition Plan detailing all necessary transition actions NLT than 30 business days after Government request, including schedule of actions, from the current NSCCA/NSATE contract to ensure there is uninterrupted NSCCA/NSATE support. The contractor shall document and submit the Transition Plan. [CDRL A008-4, Work Management Plan

(Transition Plan)]. The contractor’s Transition Plan shall address, but is not limited to, the following:

3.5.2.2 A comprehensive list of tasks to be accomplished, entrance and exit criteria for each task, and all GFP, which may include, but is not limited to: hardware, software, tools, data, documentation, and processes, and the responsible person(s) for those tasks.

3.5.2.3 Identify, score, and rank risks for transitioning tasks and tools. In addition, provide mitigation strategies for those risks. [CDRL A008-4, Work

Management Plan (Transition Plan)]

3.5.2.4 Detailed staffing plans to support transition plan.

3.5.2.5 Detailed activities and tasks to acquire knowledge and expertise to perform all task identified in the transition plan.

3.5.2.6 Assembly and Government-witnessed checkout of GFP at the contractor’s facility.

3.5.2.7 Detailed schedule for transition of tasks and GFP to complete transfer of responsibility.

3.5.2.8 The contractor shall begin executing the Transition Plan within 5 business days of the Contracting Officer (CO) notifying the contractor of Transition Plan approval. The contractor shall complete transition within 60 business days after contract award.

3.5.2.9 The contractor shall report status and transition progress to Government Program

Management team until transition is complete. [CDRL A026, Status Report].

The contractor shall meet with the Government to discuss the transition of task orders and Government-Furnished Property (GFP) after contract award until transition is successful with no issues.

EVALUATION (NSATE)

3.5.3 Phase-Out Transition

The contractor shall prepare and submit a Phase-Out Transition Plan that details a clear and orderly transition of workload and responsibility from the contractor to future contractor(s), subcontractor(s), or Government organization. [CDRL A026 Status Report]

3.5.4 Business and Financial Management

The contractor shall monitor its obligations and expenditures, and report results to the

Government, update obligation and expenditure plans, and provide reports to the

Government that may include financial suspenses and funding cut drills. [CDRL A018

Contract Funds Status Report (CFSR); A019 Contract Summary Report]

3.5.5 Commercial Small Business Involvement - RESERVED

3.5.6 Travel

The contractor shall travel to support the objectives of this PWS as identified at task order level. The allowable baseline for airfare cost is the “lowest priced airfare available to the contractor as outlined in FAR 31.205-46 and IAW the Federal Travel Regulations. All travel requires Government approval and authorization. The contractor is responsible for making all necessary travel arrangements.

3.5.7 Contractor Manpower Reporting

The contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site as specified by the current CDRL.

The contractor shall completely fill in and provide the Government access to all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported at any time during the FY, all data shall be reported no later than 31 October of each calendar year.

Contractors may direct questions to the Contractor Manpower Reporting Application

(CMRA) help desk. [CDRL A022, Funds and Labor Hour Expenditure Report]

EVALUATION (NSATE)

4 AUDITS OF CONTRACTOR PERFORMANCE

4.1 Service Summary

Performance standards the Government will use for monitoring contractor performance will be based at the task order level. If the contractor does not have processes in place or meet the performance standards listed in each task order, then the contractor shall establish a corrective action plan to correct the deficiency. [CDRL A012, Contractor’s Corrective Action Plan]

Table 1. – Services Summary Matrix

Performance Objective PWS Para Performance Threshold

Quality: Quality of work and level of support shall meet task requirements.

Work shall require little or no rework and…