SOW.pdf

DISTRIBUTION STATEMENT A. Approved for public release: Distribution is unlimited.

3-Nov-20

Statement of Work (SOW) for

Expeditionary Fluid Analysis System (EFAS)

Prepared by

SUPPORT EQUIPMENT AND VEHICLES PROGRAM OFFICE

235 BYRON ST STE 19A

ROBINS AFB GA 31098-1813

THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

1. SCOPE

2. APPLICABLE DOCUMENTS

2.1 Government documents

2.1.1 Specifications, standards, and handbooks

2.1.2 Other Government documents, drawings, and publications

2.2 Non-Government publications

2.3 Order of precedence

3. REQUIREMENTS

3.1 Program management

3.1.1 Program manager

3.1.2 Plant access

3.1.3 Monthly status report

3.1.4 Integrated master schedule (IMS)

3.2 Conferences and program reviews

3.2.1 Post-award conference (PAC)

3.2.2 Technical reviews

3.2.2.1 Design review

3.2.2.2 Test readiness review (TRR)

3.2.2.3 Technical review documentation

3.2.3 Program Management Review support

3.2.4 Conference room

3.2.5 Meeting agendas

3.2.6 Meeting minutes

3.3 Systems engineering

3.3.1 Environment, Safety, and Occupational Health (ESOH)

3.3.1.1 System safety

3.3.1.2 Hazardous materials

3.3.2 Counterfeit Prevention Plan (CPP)

3.3.2.1 Applicability

3.3.2.2 Definitions

3.3.2.3 Parts availability and use of parts brokers

3.3.2.4 Procurement policies

3.3.2.4.1 Risk assessment

3.3.2.5 Detection and avoidance responsibilities

3.3.2.6 Testing and verification

3.3.2.7 Configuration identification and traceability

3.3.2.8 Counterfeit notification and reporting

3.3.2.9 Counterfeit prevention training

3.3.3 Cybersecurity

3.3.3.1 Cybersecurity analysis

3.3.3.2 Risk management framework (RMF)

3.3.3.3 Cyber-secure development environment

3.4 Logistics

3.4.1 Technical Order (TO) requirements

3.4.1.1 TO verification

3.4.2 Provisioning

3.4.2.1 Provisioning Guidance Conference

3.4.3 Software data deliverables

3.4.3.1 Executable code

3.4.3.2 Automated Computer Program Identification Number (ACPIN) Data and Control Record

3.4.3.3 Software documentation

3.4.4 Calibration and Measurements Requirements Summary (CMRS). …………………

3.4.5 Calibration Certification and Report

3.4.6 Reserved ................................................................................ Error! Bookmark not defined.

3.5 Testing and evaluation

3.5.1 Design analysis

3.5.2 First article inspection

3.5.2.1 Contractor first article inspection

3.5.2.2 First article test procedure

3.5.2.3 First article testing

3.5.2.4 First article test report

3.5.3 Software and Application Certification Assessment (SACA)

3.5.4 Restoration

3.5.5 Disposition

3.6 Configuration management

3.6.1 Configuration requirements

3.6.1.1 Baselines

3.6.1.1.1 Functional baseline

3.6.1.1.2 Allocated baseline

3.6.1.1.3 Product baseline

3.6.2 Engineering Change Proposals (ECPs)

3.6.3 Request for Variance (RFV)

3.7 Training/familiarization

3.7.1 Operation and maintenance familiarization/orientation material

3.7.2 Government rights

3.8 Government Furnished Property (GFP)

1. SCOPE

This document defines the tasks associated with the procurement of the Expeditionary Fluid Analysis System (EFAS) as described by purchase description PD20TNKRLPEB01.

2. APPLICABLE DOCUMENTS

The following documents are applicable to the SOW to the extent specified herein.

2.1 Government documents.

2.1.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks of the exact revision listed below form a part of this SOW to the extent specified herein.

FEDERAL STANDARDS

FED-STD-313F Material Safety Data, Transportation Data, and Disposal Data for Hazardous Materials Furnished to Government Activities

DEPARTMENT OF DEFENSE STANDARDS

MIL-STD-882E System Safety MIL-STD-1568D Materials and Processes for Corrosion Prevention and

Control in Aerospace Weapons Systems

NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY (NIST)

NIST 800-37

NIST SP 800-53

Guide for Applying the Risk Management Framework to Federal Information Systems

Security and Privacy Controls for Federal Information Systems and Organizations

PERFORMANCE SPECIFICATION

MIL-PRF-32216A Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data

2.1.2 Other Government documents, drawings, and publications.

AIR FORCE INSTRUCTION (AFI)

AFI 32-7086 Hazardous Materials Management, dated 4 February

AFI 17-101 Risk Management Framework (RMF) for Air Force Information Technology (IT)

(Copies of this document are available online at http://www.e-publishing.af.mil/.)

DEPARTMENT OF DEFENCE INSTRUCTIONS (DODI)

DoDI 8500.01 Cybersecurity DoDI 8510.01

Risk Management Framework (RMF) for DoD Information Technology (IT)

(Copies of this document are available online at http://www.e-publishing.af.mil/.)

COMMITTEE ON NATIONAL SECURITY SYSTEMS INSTRUCTION (CNSSI)

CNSSI No. 1253 Security Categorization and Control Selection for National Security Systems

DATA ITEM DESCRIPTIONS (DIDs)

DI-MGMT-81928 NOT 1

DI-MGMT-81861B/T

DI-MISC-80508B

DI-ADMN-81249B

DI-ADMN-81250B

DI-SAFT-81626

DI-SAFT-80101C

Contractor's Progress, Status and Management Report Integrated Program Management Data and Analysis Report (IPMDAR) Technical Report – Study/Services Conference Agenda Conference Minutes System Safety Program Plan (SSPP) System Safety Hazard Analysis Report

DI-MISC-81832 Counterfeit Protection Plan

DI-MGMT-82135

DI-TMSS-80527C

RMF A&A Products Commercial Off-The-Shelf (COTS) Manuals and Associated Supplemental Data

DI-SESS-81758A NOT 1

DI-SESS-81874

DI-AVCS-80700A

DI-MISC-81454D

DI-IPSC-81441A NOT 1

DI-IPSC-81442A NOT 1

DI-IPSC-81448B NOT 1

DI-QCIC-80278C

DI-QCIC-80798C

Logistics Product Data Engineering Data for Provisioning (EDFP) Computer Software Product End Item Automated Computer Program Identification Number

(ACPIN))

Software Product Specification Software Version Description Firmware Support Manual Calibration and Measurements Requirements Summary

(CMRS)

Calibration Certificate/Report http://www.e-publishing.af.mil/ http://www.e-publishing.af.mil/

DI-SESS-80639E

DI-SESS-80642E

DI-SESS-80640E

DI-ILSS-80872 NOT 1

DI-NDTI-80603A

DI-NDTI-80809B

Engineering Change Proposal (ECP) Notice of Revision (NOR) Request for Variance (RFV) Training Materials Test Procedure Test/Inspection Report

(Copies of these documents are available online at http://quicksearch.dla.mil.)

DEPARTMENT OF DEFENSE GUIDES

(no identifier) Risk Management Guide for DoD Acquisition, Sixth Edition, Version 1.0

DEPARTMENT OF DEFENSE MANUALS

TM-86-01R Air Force Technical Manual Contract Requirements

T.O. 00-5-16 Computer Program Identification Number (CPIN)

Management

DEPARTMENT OF DEFENSE HANDBOOKS

MIL-HDBK-29612-3/A Development of Interactive Multimedia Instruction (IMI) (Parts 1-5)

PURCHASE DESCRIPTIONS

PD20TNKRLPEB01 Expeditionary Fluid Analysis System

2.2 Non-Government publications. The following documents of the exact revision listed below form a part of this document to the extent specified herein.

N/A

SOCIETY OF AUTOMOTIVE ENGINEERS (SAE)

AS5553 Aerospace Standard, Counterfeit Electronics Parts;

Avoidance, Detection, Mitigation, and Disposition

GEIA-HB-0007B Logistics Product Data Handbook

(Application for copies should be addressed to SAE, Inc., 400 Commonwealth Drive, Warrendale PA 15096, http://www.sae.org/.)

http://www.sae.org/

2.3 Order of precedence. In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. REQUIREMENTS

3.1 Program management.

3.1.1 Program manager. The contractor shall identify to the Government and maintain a single point of contact (Program Manager) for all matters under this contract. The contractor shall also ensure that all program management personnel assigned to the program shall be available, as required, to meet program objectives.

3.1.2 Plant access. The contractor shall arrange for full access to applicable contractor facilities and offices by Government representatives conducting any business, making observations, or performing inspections required by public law or by this contract.

3.1.3 Monthly status report. The contractor shall track program progress and document such via monthly status reports. The contractor shall submit a monthly status report that shall cover the engineering and technical development of the system and subsystems as well as a projection of planned work for the remaining effort. Reports shall document tasks, issues, actions, and deliverables. Problem areas shall be identified with proposed solutions and outcomes. The current program integrated master schedule (IMS) (see 3.1.4) and risk management analysis, mitigation plan, and tracking (see 3.3.3) shall be provided as attachments to the monthly status report. (A001, DI-MGMT-81928, Contractor's Progress, Status and Management Report)

3.1.4 Integrated master schedule (IMS). A baseline IMS shall be developed at the start of the program in accordance with DI‑MGMT‑81861. The contractor shall implement and maintain the IMS using the original baseline schedule as an unchanging reference. The IMS shall include contractor’s cybersecurity risk management framework activities and events (see 3.3.3.2). The IMS shall be provided in both Microsoft Project and PDF formats as an attachment to the monthly status report (see 3.1.3). (A002, DI‑MGMT‑81861, Integrated Program Management Data and Analysis Report)

3.2 Conferences and program reviews.

3.2.1 Post-award conference (PAC). The Government will convene a PAC conference with the contractor virtually on-line and by telephone within 30 days after contract award. The Procuring Contracting Officer (PCO) will coordinate the actual date, time, and location of the conference with the contractor.

3.2.2 Technical reviews.

3.2.2.1 Design review. If requested by the Government, the contractor shall conduct a design review within 90 days of contract award. The design review shall be held at Tinker AFB, Oklahoma City, Oklahoma, or via teleconference. The PM will coordinate the actual date, time, and location of the reviews with the contractor. The design review shall include a formal technical review of the EFAS design; program risks shall be reviewed on a technical and schedule basis.

The review shall include, but is not limited to: calculations; any necessary design studies or analyses required in 3.5.1 herein; proprietary or restricted design processes, components, and information; electrical and mechanical design; lists of materials, parts, and processes; software design, integration, and verification to include integration with DoD networks; production and manufacturing capability; and quality considerations. Any mockups or assemblies shall be made available for Government review as well.

3.2.2.2 Test readiness review (TRR). If requested by the Government, the contractor shall host and conduct a test readiness review (TRR) 14 days prior to the start of the first article test. The TRR shall assess test objectives, test methods and procedures, scope of tests, and determine if required test resources have been properly identified and coordinated to support planned tests. The TRR shall be held at Tinker AFB, Oklahoma City, Oklahoma, or via teleconference. The PM will coordinate the actual date, time, and location of the reviews with the contractor.

3.2.2.3 Technical review documentation. The contractor shall prepare all necessary detailed status reports for the technical review meetings, conference agendas, and conference minutes. The contractor shall prepare formal documentation of the TRR. (A003, DI-MISC-80508, Technical Report/Study Services)

3.2.3 Program Management Review support. The contractor shall participate in and support all reviews, audits, and meetings as requested by the PCO, PM or the contractor. Program Management Reviews shall be conducted quarterly or as required via teleconferences.

3.2.4 Conference room. The contractor shall provide a conference room suitable for meetings of up to 15 Government representatives, plus contractor personnel, in support of scheduled meetings at the contractor’s facility.

3.2.5 Meeting agendas. The contractor shall publish an agenda for all meetings and conferences specified in 3.2.2 and 3.2.3. The contractor shall request from the Government any items or issues to be discussed or presented at the meetings, and shall include such items in the agenda. Agendas shall be submitted not less than five working days prior to any meeting. (A004, DI-ADMN-81249, Conference Agenda)

3.2.6 Meeting minutes. The contractor shall provide a written record of the discussions, decisions, and action items identified at each meeting. Minutes shall include presentation material. (A005, DI-ADMN-81250, Conference Minutes)

3.3 Systems engineering.

3.3.1 Environment, Safety, and Occupational Health (ESOH).

3.3.1.1 System safety. The contractor shall establish, conduct, document, and maintain a system safety program in accordance with MIL-STD-882. The contractor shall document their approach for analyzing, eliminating, or minimizing ESOH hazards during all phases of the program. The contractor shall initiate changes in the system design based on safety analysis results such that the associated risk is reduced to a level acceptable to the Government. A system safety program plan and a system safety hazard analysis report shall be provided with the first article test report. (A006, DI-SAFT-81626, System Safety Program Plan (SSPP); A007, DI-SAFT-80101, System Safety Hazard Analysis Report (SSHAR)).

3.3.1.2 Hazardous materials. The contractor shall manage hazardous materials, including those embedded in the system or used during operation or maintenance, as an element of the Systems Engineering process. The system shall not generate or use Class I or Class II Ozone Depleting Substances (ODS) during operation, maintenance, or disposal. The use of hexavalent chromium is also prohibited. The contractor shall list any hazardous materials, as defined in AFI 32-7086, to be delivered under this contract, including locations, quantities, and special handling and disposal procedures. This information shall be documented in the design analysis (see 3.5.1) and reviewed at the technical reviews; it shall be in accordance with FED-STD-313.

3.3.2 Counterfeit Prevention Plan (CPP). Contractors that supply electronic parts or systems that contain electronic parts shall establish policies and procedures to avoid, detect, mitigate and disposition counterfeit electronic parts to prevent such parts from entering the USAF/DoD supply chain. These policies and procedures shall be documented in a CPP for submission and approval in accordance with Data Item Description (DID) DI-MISC-81832 and accomplished for all specified contract items. DI-MISC-81832 is applicable to Parts, Material, and Processes Selection (PMPS) associated with delivery of systems and assemblies to the USAF and DoD. The requirements established by DI-MISC-81832 also apply to electronics components procured in sustainment of such systems and assemblies. The requirements of the DoD-adopted SAE AS5553, Aerospace Standard, Counterfeit Electronics Parts; Avoidance, Detection, Mitigation, and Disposition shall also apply. The initial CPP shall be provided with the first article test report.

(A008, DI-MISC-81832, Counterfeit Protection Plan)

3.3.2.1 Applicability. The contractor shall identify all Business locations and programs to which the CPP applies. The CPP shall address materials, hardware, electronic parts, and procured assemblies.

3.3.2.2 Definitions. The contractor shall utilize definitions in accordance with AS5553 to ensure consistency. Any contractor-derived definitions must be included in an appropriate CPP appendix or annex. (Ref. 3, 3.1, 3.2, 3.3, and Appendix H of AS5553)

3.3.2.3 Parts availability and use of parts brokers. The contractor shall not procure materials, systems, assemblies, subassemblies, or parts from parts brokers when available from Original Manufacturers (OM) or their Authorized Distributors. In cases where materials, systems, assemblies, subassemblies, or parts are no longer available from the OM or their Authorized Distributors, procurement from brokers may be authorized as defined by the contractor’s policy and their CPP. (Ref. 4.1.1, 4.1.2.e., and Appendix A of AS5553)

3.3.2.4 Procurement policies. The contractor shall provide and implement policy directing development and implementation of business practices, procedures, and processes to prevent procurement of Counterfeit materials and parts. The contractor shall identify the appropriate office(s), business units, functional organizations, and programs, who shall have responsibility for development, maintenance, and implementation of the CPP. The CPP shall identify the specific roles and responsibility for each. (Ref. 4.1.2, 4.1.3, and Appendices B, C, and D of AS5553)

3.3.2.4.1 Risk assessment. The contractor shall address the risk of using unknown sources and/or unauthorized suppliers in the CPP. Application or technical risk assessments shall establish the effect that counterfeit parts may have on in accordance with performance. Vendor or source of supply risk assessments shall establish the potential for obtaining counterfeit parts. Using any risk analysis tool acceptable to the Government, the contractor shall conduct a risk assessment based upon item characteristics and how likely it is that a counterfeit part will be received. The contractor shall identify and describe in the CPP how parts are selected for assessment and what risk is acceptable based upon the parts design, construction, material, and functional requirements. As a minimum, analysis shall be completed for flagging high risk items, such as items that are obsolete, discontinued, rare, etc. The contractor shall require completion of a trade study, documented within the CPP that shall facilitate determining whether 100% testing of parts procured from after-market sources is more cost effective than qualification or requalification of a manufacturer. (Ref. 4.1.2,

4.1.3 and appendices B, C, and D of AS5553)

3.3.2.5 Detection and avoidance responsibilities. The contractor shall establish processes for the review and approval of contractor and applicable subcontractor systems for the detection and avoidance of counterfeit electronic parts and suspect counterfeit electronic parts, which processes shall be comparable to the processes established for contractor business systems under section 893 of the Ike Skelton National Defense Authorization Act for Fiscal Year 2011 (Public Law 111–383;

124 Stat. 4311; 10 U.S.C. 2302 note). The contractor shall flow down such requirements and processes to their subcontractors in accordance with ODASD Memo titled “Overarching DoD Counterfeit Prevention Guidance”, dated 16 March 2012. (Ref. AS5553, 4.1.4, 4.1.5, appendix E)

3.3.2.6 Testing and verification. The contractor shall establish and accomplish testing and verification processes for items not received from an original equipment manufacturer, original component manufacturer, or authorized distributor that are identified as having high risk for counterfeit potential. These processes apply to prime contracts, and to subcontracts or suppliers below the prime contracts. The contractor shall provide a list of acceptable test facilities if the subcontractor or supplier does not have the capability to in accordance with form required testing.

Submittal of Certificates of Compliance indicating the parts are not counterfeit shall be acceptable for verification of testing. (Ref. 4.1.4 and Appendix E of AS5553)

3.3.2.7 Configuration identification and traceability. The contractor shall identify and control the configurations of all systems, assemblies, subassemblies, and parts, and enable mechanisms to provide traceability of parts. The contractor shall report to the Government when control of the configurations of all systems, assemblies, subassemblies, and parts, and mechanisms to provide traceability of parts are not possible. The contractor shall identify the specific systems, assemblies, subassemblies, and parts beyond the contractors’ control. The contractor shall be responsible for detecting and avoiding the use or inclusion of counterfeit materials and parts, to include procured assemblies and subassemblies, in such products and shall be responsible for the rework or corrective action that may be required to resolve the use or inclusion of counterfeit materials and parts. The cost of counterfeit electronic parts and suspect counterfeit electronic parts and the cost of rework or corrective action that may be required to remedy the use or inclusion of such parts are not allowable costs under Department contracts, unless:

a. the contractor has established a counterfeit avoidance/detection system approved by the DoD,

b. the counterfeit parts were procured from a DoD-accredited trusted supplier or provided as Government property.

c. the contractor has provided timely notification to the Government. (Ref. 4.1.6 and

Appendix F of AS5553)

3.3.2.8 Counterfeit notification and reporting. The contractor shall report in writing to the Procuring Activity within 30 days of determining any end item, component, part, or material contained in supplies purchased by the Department of Defense, or purchased by a contractor or subcontractor for delivery to, or on behalf of, the Department, contains counterfeit electronic parts or suspect counterfeit electronic parts for the purpose of investigation and notification of the Air Force Office of Special Investigations (AFOSI). The PCO will coordinate reporting to the appropriate Program Management/Item Management, System Engineering Management, the AFMC Discrepant Materiel Reporting Program (DMRP) Office in 406 SCMS/GULAB, and the AFOSI. Additionally, the contractor shall within the same 30 day period ensure all suspected or confirmed counterfeit items are entered into the Government-Industry Data Exchange Program (GIDEP) system, which will serve as the DoD central reporting repository. (Ref. 4.1.7 and Appendix G of AS5553)

3.3.2.9 Counterfeit prevention training. The contractor shall provide appropriate training and shall require all in accordance with personnel working procurement within their company, to include at a minimum their supply chain management specialists, receiving inspectors, and engineers, to complete said training. The contractor shall determine the appropriate training required. Training may be developed in-house or may be other Industry accepted training. The CPP shall describe and list the training provided by the contractor to their in accordance with personnel.

3.3.3 Cybersecurity. The contractor shall implement cybersecurity for the EFAS in accordance with DoDI 8500.01, DoDI 8510.01, and AFI 17-101. The contractor shall provide cybersecurity support to include, but not limited to, engineering and technical analysis and assessment of system cybersecurity, development and delivery of Risk Management Framework (RMF) artifacts, and design, integration, testing, and documentation of implemented cybersecurity controls.

3.3.3.1 Cybersecurity analysis. The contractor shall perform engineering analysis and risk and technical assessment of system cybersecurity. The engineering analysis shall include, but is not limited to, system hardware and software architecture, input/output (I/O) data flow, supply chain integrity, and operational conditions as it relates to system cybersecurity. The contractor shall perform a comprehensive risk assessment based on the system cyber vulnerabilities and threats.

The contractor shall conduct analysis for any commercial of-the-shelf (COTS) and/or non-developmental items to ensure that they are appropriately configured, software/hardware/firmware is controlled, and any unique risks they pose are mitigated. This information shall be documented in the design analysis (see 3.5.1) and reviewed at the technical reviews. (A003, DI-MISC-80508, Technical Report/Study Services)

3.3.3.2 Risk management framework (RMF). The contractor shall develop and deliver the required artifacts for Platform Information Technology (PIT) Assessment and Authorization (A&A) package to meet the intent and requirements of DoDI 8510.01 and AFI 17-101 for RMF implementation on the EFAS within 90 days after award. The contractor shall utilize Committee on National Security Systems Instruction (CNSSI) 1253, National Institute of Standards and Technology (NIST) Special Publication (SP) 800-37, NIST SP 800-53, and applicable overlays in addressing the security controls associated with the various artifacts. The contractor shall include cybersecurity risk management framework activities and events on the Integrated Master Schedule (IMS). (A009, DI-MGMT-82135, RMF A&A Products)

3.3.3.3 Cyber-secure development environment. The contractor shall maintain a cyber-secure development environment that reduces and manages risk by implementing, at a minimum, the following select controls as defined in NIST SP 800-53: SA-10, SA-15, and AT-2.

3.4 Logistics.

3.4.1 Technical Order (TO) requirements. The contractor shall develop and deliver technical manuals in accordance with TM-86-01. (TM-86-01, Air Force Technical Manual Contract Requirements). Note: excluding the first article EFAS unit(s), no EFAS delivery acceptance will occur without completed and Government accepted technical manuals.

3.4.1.1 TO verification. Technical order verification shall be in accordance with MIL-PRF- 32216, Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data. The contractor shall deliver manuals in accordance with (A010, DI-TMSS- 80527, Commercial Off-The-Shelf (COTS) Manuals and Associated Supplemental Data). A manual must be accepted by the Government prior to ordering of production units.

3.4.2 Provisioning. The contractor shall identify and recommend logical spare/repair parts sufficient to meet system/equipment operation and supportability in accordance with the Air Force Initial Provisioning Performance Specification (IPPS). GEIA-HB-0007 (Logistics Product Data Handbook) should be used as a guide. The format shall be consistent with existing government Provisioning data system (D220). The following Data Item Descriptions (DIDs) may apply:

a. A011, DI-SESS-81758, Logistics Product Data. Specific Logistics Product Data to be submitted:

(1) Short Form Provisioning Parts List (SFPPL)

(2) Design Change Notices (DCNs)

(3) Statement of Prior Submission (SPS)

b. A012, DI-SESS-81874, Engineering Data For Provisioning (EDFP).

3.4.2.1 Provisioning Guidance Conference. A Provisioning Guidance Conference (PGC) shall be scheduled by the Prime Provisioning Activity (PPA) and should be held within 45 days after receipt of contract. The PGC is normally held for two days to ensure both the contractor and the Government understand the provisioning requirements on contract. The PGC will be held via telephone and virtually using Microsoft teams. If a PGC is not desired, the contractor shall submit a written request for waiver of the PGC to the PPA. In the event a waiver is approved, a mutual understanding of the Provisioning requirements shall be communicated in some forum in which the AFMC Form 718 (Provisioning Performance Schedule (PPS)) shall be documented/completed, signed by both the Government and contractor, and a contract modification issued, if required.

(A004, DI-ADMN-81249, Conference Agenda; A005, DI-ADMN-81250, Conference Minutes)

3.4.3 Software data deliverables.

3.4.3.1 Executable code. The contractor shall own the executable code and shall manage and make in-house revisions/updates as necessary to support the EFAS through the term of the contract. The contractor shall notify the Government of any and all revisions/updates. The Government shall protect the contractor proprietary information embodied in the code and will not disclose this information to a third party without the contractor’s explicit approval. The Government shall have the right to reproduce and distribute the software to users as necessary. The contractor shall deliver the final application software Computer Software Configuration Item (CSCI) on CD/DVD-ROM, which shall be compatible with the CD/DVD-ROM reader used on the EFAS. The first delivery shall be within 90 days of contract award with subsequent deliveries as required. (A013, DI- AVCS-80700, Computer Software Product End Item)

For any and all commercial software used on the EFAS that requires a license, the license “key” shall not be hardware based (i.e., universal serial bus (USB)-based dongle key). The ability to utilize any and all commercial software shall not require any additional hardware to verify possession of appropriate and corresponding license(s), nor require any recurring license fees for continued use of and reinstallation of the existing software configuration. All licenses shall be “royalty-free,” worldwide, irrevocable and non-exclusive.

3.4.3.2 Automated Computer Program Identification Number (ACPIN) Data and Control Record.

The contractor shall request a Computer Program Identification Number (CPIN) for the EFAS application software configuration entity to be delivered to the Government to support the EFAS.

To request a CPIN from the Government all custom and/or commercial software packages shall be labeled independently and described thoroughly on AF Forms 1243 in accordance with TO 00- 5-16 guidelines. The first delivery shall be within 90 days of contract award with subsequent deliveries as required. (A014, DI-MISC-81454, Automated Computer Program Identification Number (ACPIN)).

3.4.3.3 Software documentation. The contractor shall document all aspects of the EFAS application software CSCSI to include executable software description, source files, and software support information, including “as built” design information and compilation, build, and modification procedures via a Software Product Specification (SPS) and Software Version Description (SVD). The contractor shall document via a Firmware Support Manual (FSM), where applicable, required aspects of any and all custom (non-COTS) firmware that is used as a part of EFAS. This applies to read only memories (ROMs), Programmable ROMs (PROMs), Erasable PROMs (EPROMs), and any other firmware devices (i.e. EEPROMs, FPGAs, etc.). (A015, DI- IPSC-81441, Software Product Specification; A016, DI-IPSC-81442, Software Version Description; A017, DI-IPSC-81448, Firmware Support Manual)

3.4.4 Calibration and Measurements Requirements Summary (CMRS). The contractor shall develop and deliver a Calibration and Measurements Requirements Summary. Standards shall be traceable to National Institute of Standards and Technology (NIST) or other DoD approved measurement sources. (A018, DI-QCIC-80278, Calibration and Measurements Requirements Summary (CMRS))

3.4.5 Calibration Certification and Report. The contractor shall provide a report and certification for all materials used to calibrate, or standardize, operations of the EFAS. This report and certification shall also include certification for any filters used to perform tests with the EFAS.

The report shall be delivered within 120 days of contract award. (A019, DI-QCIC-80798, Calibration Certificate/Report)

3.5 Testing and evaluation. Testing and verification of the EFAS shall be performed in accordance with 4.1 of PD20TNKRLPEB01.

3.5.1 Design analysis. A design analysis of the system and each subsystem shall be performed to verify compliance with this SOW and each applicable requirement of the PD. The analysis shall include, but is not limited to, the following:

• System safety (see 4.5.2 of the PD)

• Service life (see 4.5.3 of the PD)

• Surface transportability (see 4.5.7.1.1 of the PD)

• Air transportability (see 4.5.7.2 of the PD)

• Diagnostic software (see 3.7.5 of the PD)

• Software and interface (see 4.2.2 of the PD)

A Material Safety Data Sheet (MSDS) shall be provided for each hazardous material identified for use in the program (see 3.3.1.2). (Note that the system safety hazard analysis is addressed in 3.3.1.1) An initial design analysis shall be provided 14 days prior to the design review; updated versions of the analysis shall be provided 14 days prior to the TRR, and with the first article test report. (A003, DI-MISC-80508, Technical Report/Study Services)

3.5.2 First article inspection. First article inspection shall be accomplished in accordance with 4.2 of PD20TNKRLPEB01. The contractor is granted a waiver for the tests, analyses, and demonstrations listed in Table 1 below. In lieu of conducting these tests, analyses, and demonstrations the contractor shall submit certification(s) demonstrating EFAS compliance with the following requirements of PD20TNKRLPEB01: 3.3.5, 3.3.9, 3.4.1, 3.4.2, 3.4.4, 3.4.5, 3.4.6, 3.4.7, 3.4.8, 3.4.9, 3.4.10, 3.6.1, 3.6.2, 3.7, 3.7.1, 3.8.2, 3.8.3, and 3.8.4. The certification(s) shall be included with the first article test report (see 3.5.2.4).

PD20TNKRLPEB01 Paragraph Test, Analysis or Demonstration

4.5.3 Service-life analysis

4.5.4 Electromagnetic interference test

4.5.5 Environmental testing

4.5.7 Transportability verification

4.5.8 Maintainability analysis and demonstration

4.5.10 Software demonstration

Table 1: Tests, Analyses, and Demonstrations Waived from PD20TNKRLPEB01

3.5.2.1 Contractor first article inspection. The contractor shall be responsible for scheduling, coordinating, and ensuring successful execution of all first article inspection, whether conducted at the contractor’s facility or at an external laboratory. No Government inspection shall take place until such time as all contractor first article inspection has been successfully completed and approved by the Government.

3.5.2.2 First article test procedure. The contractor shall develop a detailed first article test procedure and submit it for the Government review and approval. The test procedure shall address all requirements identified in 4.2.1 of PD20TNKRLPEB01 and this SOW. The test procedure shall include at a minimum: data record sheets, charts, graphs, top level test instructions, simple block style diagrams of test instrumentation connections, and identification of test instruments by manufacturer and model number. (A024, DI-NDTI-80603, Test Procedure)

3.5.2.3 First article testing. After Government approval of the contractor’s test procedure, the contractor shall schedule the testing to be conducted. Twenty calendar days prior to the contractor’s first article inspection testing, the contractor shall notify the Government of the date, time, and location of the testing. The Government reserves the right to witness any of the first article testing conducted. Testing shall not be conducted without occurrence and Government approval of the TRR as specified in 3.2.2.2.

3.5.2.4 First article test report. The contractor shall submit a preliminary first article test report within 30 calendar days of completion of the testing. No further testing will occur until the preliminary test results are submitted and approved by the Government. Completed analysis, certification, inspection, and demonstration results shall be presented with the test data requirement. The contractor shall submit a final first article inspection test report upon completion of the software and interface inspection in accordance with 4.2.1 of PD20TNKRLPEB01. The final copy shall include all data submitted in the preliminary version plus identify any issues and corrections that occurred during software and interface inspection. (A025, DI-NDTI-80809, Test/Inspection Report)

3.5.3 Software and Application Certification Assessment (SACA). Following successful completion first article phase one, contractor examination, the EFAS application software shall be subjected to the SACA process. Software products planned for use on the AF Network (AFNET) shall be certified via the Software and Application Certification Assessment (SACA) process. HQ CCC/SACA conducts security testing, evaluates supportability and compatibility then forwards the documents to the Air Force Enterprise Security Control Assessor for certification in accordance with AFI 17-101. Once certified, the software is placed on the AF Evaluated Products List (AF EPL) for use on AFNET. Details of the SACA process can be found at https://cs2.eis.af.mil/sites/10007/sc/SitePages/Home.aspx. The procuring activity will function as the PM/Sponsor for the process, and the contractor shall provide technical support to include analysis, assessment, technical documentation delivery, input/completion of Government forms and paperwork, and any software modification needed to satisfy the certification requirements.

Figure 1 below is a summary of the SACA process.

Figure 1: Software and Application Certification Assessment (SACA) process

3.5.4 Restoration. After completion of the contractor’s first article inspection and SACA acceptance, the first article EFAS unit(s) shall be shipped, within 30 days, to the contractor’s facility for restoration. The contractor shall be responsible for any repairs that may be necessary to restore the first article EFAS units to a serviceable, “like new” condition while retaining configuration integrity. The contractor shall be responsible for all costs associated with shipping of the first article EFAS to the contractor's facility for restoration.

3.5.5 Disposition. One first article EFAS shall be retained at the contractor’s facility, to serve as a manufacturing standard, until the last shipment. The remaining first article EFAS units shall be shipped to the location(s) specified in the contract.

3.5.6 Common Access Card (CAC). The contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for https://cs2.eis.af.mil/sites/10007/sc/SitePages/Home.aspx

DoD facility entry control and /or for physical access to facilities and buildings to perform tasks on the contract/order, the contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO> The Government will provide the contractor instruction on how to complete a Contractor Verification System (CVS) application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Document System (RAPDIS) issuing facility [usually the Military Personnel Flight (MPF)]. The Contractor shall immediately report a lost or stolen CAC as directed by Local Government policy. The contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The contractor shall return an expired CAC within five business days after the expiration date. The contractor shall return any and all CACS within five business days after completion/termination of the contract as directed by local Government policy.

3.6 Configuration management.

3.6.1 Configuration requirements.

3.6.1.1 Baselines.

3.6.1.1.1 Functional baseline. The functional baseline is the PD20TNKRLPEB01.

3.6.1.1.2 Allocated baseline. All of the documents used to produce and define the accepted design review EFAS configuration shall constitute the allocated baseline.

3.6.1.1.3 Product baseline. All of the documents used to produce and define the accepted first article EFAS shall constitute the product baseline.

3.6.2 Engineering Change Proposals (ECPs). Notwithstanding any other provision in the contract, no contractor or subcontractor's change in design, fabrication, assembly, part, material, process, or source of supply shall be made to the allocated or product baseline unless such change is submitted in writing by ECP and approved by the procuring activity. Any request for change shall be accompanied by complete documentation supporting the need for the change. A system safety impact statement shall be provided as part of the submittal; it shall quantify and qualify the system safety risk identified and how it impacts the system safety risk already identified for the system.

A Notice of Revision (NOR) shall be submitted with each ECP. Should the Government approve an ECP, the contractor shall be responsible for submitting updated TOs and the system safety hazard analysis report (see 3.3.1.1) to reflect the changes made in the ECP. (A020, DI-SESS-80639, Engineering Change Proposal (ECP); (A021, DI-SESS-80642), Notice of Revision (NOR).

3.6.3 Request for Variance (RFV). The contractor shall prepare an RFV whenever a departure from the contractually-specified product base line is proposed for a specific number of units or for a specific time. (A022, DI-SESS-80640, Request for Variance (RFV))

3.7 Training/familiarization.

3.7.1 Operation and maintenance familiarization/orientation material. The contractor shall develop an interactive multimedia system (program media) on CD-ROM or DVD-ROM to be used during the operation and maintenance orientation and for use in the field for familiarization of operational and maintenance personnel at the organizational level. MIL-HDBK-29612/3A shall be used as a general guide, although contractor format is acceptable. This program media shall be in sufficient detail to provide the technician adequate skills to operate and provide general maintenance for the up-keep of the EFAS in the field. The program media shall also be in sufficient detail to allow the Air Education and Training Command (AETC) to formulate a training course for future use. The program media shall be compatible with existing United States Air Force (USAF) personal computers (Microsoft Windows based operating systems) and consist of all materials (e.g., software, firmware) necessary to execute the material. Approximately 15 copies of the draft version program media shall be available for use at the operation and maintenance orientation for Government personnel within 90 days of Government acceptance of the test report. The operation and maintenance familiarization/orientation shall be conducted either on-site at Tinker AFB, or via videoconferencing using Microsoft Teams. Feedback from the Government personnel attending the operation and maintenance orientation shall be gathered and used to develop the final version of the program media to be used for organizational level familiarization. The program media shall be subject to final Government approval before final delivery. Final delivery of two copies of the program media shall be made to procuring activity. One copy of the program media shall be sent with each EFAS as back up data. Note: excluding the first article EFAS unit(s), no EFAS delivery acceptance will occur without completed and Government accepted orientation material. (A023, DI-ILSS-80872, Training Materials)

3.7.2 Government rights. The contractor shall extend to the Government unlimited usage rights for the duplication and distribution of the operation and maintenance familiarization/orientation material (program media) identified in 3.7.1 herein. The contractor may identify to the Government any specific proprietary materials or items needing to be limited due to proprietary rights.

3.8 Government Furnished Property (GFP). The Government will provide a copy of the Standard Desktop Configuration (SDC) operating system software as GFP to be used by the contractor during development, integration, and testing. The most current version of the SDC at time of contract award shall be provided. In the event that the SDC is changed/modified/updated during the performance of this contract, the Government will provide that version as GFP. The contractor must use the most current version of SDC available at time of T&E and SACA activities.

3.9 Definitions. The following are acronyms that appear on the Contract Data Requirements Lists (CDRL) along with their meaning.

As Required (AS REQ): Delivery of a data deliverable follows the occurrence of the requiring event.

Days After Contract Start (DAC): The number of days after contract start that the data is due.

Days After Test Completion (DATC): The number of days after test completion that the data is due.

Days Before to Test (DPTT): The number of days before a test event that the data is due.