CATP2_PWS.docx

Solicitation FA8540-21-R-0003 Revision 1 Date: 11 Aug 202113 May 2021

Sniper Comprehensive Advanced Targeting Pod (CATP) 2 Performance-Based Work Statement (PWS)

Purchase Request: FD2060-21-33102FD2060-21-33102

Change Summary

Table Of Contents

Description of Services

1.1. Objective(s)

This Performance-Based Work Statement (PWS) defines the requirements for a follow-on Sniper Indefinite Delivery/Indefinite Quantity (ID/IQ) contract. Details of efforts shall be issued on individual Delivery Orders (DOs) against this contract. This PWS describes the services required to insert technology into the Sniper Advanced Targeting Pod (ATP) system and to sustain the system. Lockheed Martin (hereafter referred to as Contractor) shall provide efforts required for the management, engineering, production, fabrication, integration, Configuration Management (CM), test, test support, and logistics support of the Sniper system to ensure a system availability rate and reliability Mean time Between Maintenance Events (MTBME) specified herein. The Contractor shall adhere to Contractor Quality System; ensuring it is an integral and integrated part of the Contractor’s complete management system.

Benefit to the United States Air Force (USAF) This second Sniper Comprehensive Advanced Targeting Pod (Sniper CATP2) acquisition benefits the Air Force by combining the separate efforts of the Sniper ATP Sensor Enhanced (ATP-SE) program with the Sniper ATP Modernization Program (ATP-MP) to support a comprehensive program called the ATP Technology Insertion (ATP-TI). The combining of programs reflected by this Sniper CATP2 acquisition will benefit the USAF through management reduction and contract efficiency increases. This acquisition incorporates a Government and Lockheed Martin partnership that has proven very successful in maintaining a very high readiness rate of the system. The USAF does not have full capability to provide the necessary services outside of this arrangement. The Indefinite Delivery, Indefinite Quantity (ID/IQ) contract supported by this PWS delivers a services-based framework that meets the above listed USAF objectives.

Background The ATP is an electro-optical target acquisition and designation system that incorporates day/night video sensors, laser range-finding and targeting capability, a data recorder, radio communications, and supporting equipment. A few Extended Range (XR) versions remain but most have been upgraded to a Sensor Enhancement (SE) version, which added digital data recording and two way data link radio communications. The latest technology insertion (TI) for the Sniper is the ATP Digital Video Interface (ATP-D). The ATP-D outputs digital video to the cockpit rather than analog video.

Services Summary (SS)

Para.

Performance Threshold

Government Property and Services Government Furnished Property (GFP) Any Government Furnished Property/Material if/when identified shall be listed as an attachment to the contract/delivery order and will revert to Government ownership at the conclusion of the contract.

Contractor Responsibility The Contractor shall be responsible for Government property, either provided by the Government or generated by contract execution, in accordance with the Federal Acquisition Regulation (FAR) , all other applicable Government regulations and as specified in the contract/order.

Reporting of Government Property: The Contractor shall create and maintain records of all Government property accountable to the contract/order. The Contractor shall record receipt and return of Government Furnished Property (GFP) in the GFP Module of the Procurement Integrated Enterprise Environment (PIEE). The Contractor shall record receipt and return of Government property, which falls under the Item Unique Identification (IUID) categories identified in the FAR, in the IUID Registry.

Definition of Loss of Government Property:

“Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

Reporting Loss of Government Property

a. The Contractor shall use the Defense Contract Management Agency (DCMA) eToolsoftware application for reporting report loss of Government property. Reporting value shall be at unit acquisition cost. The eTools “LTDD of Government Property” toolset can be accessed from the DCMA home page External Web Access Management application at HYPERLINK "https://www.dcma.mil/aboutetools/" https://www.dcma.mil/aboutetools/ in the GFP Module of PIEE.

b. Unless otherwise provided for in this contract, the requirements of paragraph (1) above do not apply to normal and reasonable inventory adjustments, i.e., losses of low-risk consumable material such as common hardware, as agreed to by the Contractor and the Government Property Administrator. Such losses are typically a product of normal process variation. The Contractor shall ensure that its property management system provides adequate management control measures, e.g., statistical process controls, as a means of managing such variation.

c. The Contractor shall report losses of Government property outside normal process variation, e.g., losses due to theft, inadequate storage, lack of physical security, or acts of God.

d. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under this contract.

Return or Retention of Government Property All property provided by the Government remains the property of the Government and shall be returned to the Government upon as directed by the Procuring Contracting Officer (PCO), but no later than the completion of the contract/order unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. Retention of the property by the Contractor will require modification of both losing and gaining contracts in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO.

All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed by the PCO, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

All Contract Data Requirement Lists (CDRL) deliverables become the property of the Government and shall be delivered to the Government as indicated by CDRL instructions.

Phone Service The Government shall provide the Contractor use of one DSN phone line in Warner Robins AFB Bldg. 640 for official use only in performance of the requirements of this contract. The Contractor shall comply with all requirements for use of this phone line including maintaining a phone log.

Computer Service The Government shall provide the Contractor continuous access to the .mil domain for one computer and five (5) users in Bldg. 640; and WEBREQ or similar system for ten (10) Contractor personnel. The Contractor shall comply with all information assurance requirements associated with use of a Government access computer system.

Travel Travel by Contractor personnel shall be conducted in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

Government Provided Logistic Support for OCONUS Contractor Employees

a. Logistic support for Contractor employees will be furnished in support of this Contract

b. Commissary (including rationed items)

c. AAFES Facilities (Mil Exchange) (including rationed items)

d. Armed Forces Recreation Facilities

e. Army Continuing Education Services

f. Class VI (alcoholic beverages including rationed items)

g. Credit Union Facilities

h. Customs Exemption

i. Dependent schools, on a space-required, tuition paying basis

j. Legal Assistance -- wills and power of attorney

k. Local Government Transportation for Official Government Business (Nontactical vehicle)

l. Local Morale/Welfare Recreation Services

m. Medical/Dental Services on a reimbursable basis (Dental Care available only for emergency conditions on a reimbursable basis)

n. Military Banking Facilities

o. Military Postal Facilities

p. Mortuary Services

q. Officer or NCO/EM Clubs

r. Pet/Firearm registration and control

s. Privately owned Vehicle (POV) license for USAEUR

t. Purchase of Petroleum and Oil (POL) products

u. Transient Billets

v. Messing Facilities at remote sites only on a reimbursable basis

w. Housing referral assistance

x. Quartermaster laundry/dry cleaning

y. Contract personnel must not be an ordinary resident in the host country, be nationals of Non-NATO countries, or be a stateless person. Personnel must be engaged full time in support of a US forces mission.

z. Specific attention is invited to the fact that permanent family or bachelor Government quarters are not included as items of individual logistic support.

Status of Forces Stamp on Passport

a. Under the provisions of Article 73, Supplementary Agreement to NATO Status for Forces Agreement, Contractor personnel who are assigned to USAEUR are considered as "Members of the Civilian Component" of the US Forces, provided they are:

Technical Experts who will serve the US Forces exclusively Not stateless persons Nationals of a NATO state, excluding Germany Not ordinarily a resident of Germany

b. Contractor personnel and their dependents are identified as "Members of the Civilian Component," by a Certificate of Status stamp in their passport. This certificate entitles the passport holder to the rights and privileges listed in the Status of Forces Agreement for this category of personnel. The Government will assist Contractor personnel to ensure the above Certificate of Status stamp in the passport is obtained, or such other or additional documentation for members as this will enable them to accomplish their missions and obtain proper benefits and status under NATO SOFA agreement.

Common Access Card (CAC)

CAC Issuing The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under 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 and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application(s). Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].

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

Item Unique Identification (IUID) Marking Requirement Unique Item Identification is required for all items to be delivered to the Department of Defense (DoD) that meet the criteria established by the FAR.

Reporting in IUID Registry Transmission of Government Property Transmission of Government property, which falls under the IUID categories identified in the FAR, must be recorded in the IUID Registry. The Government is required to record the transfer of GFPIUID-identified property to the Contractor. The Contractor is required to record the receipt of GFPIUID-identified property from the Government. The Contractor is required to record the return of GFPIUID-identified property to the Government.

Life Cycle Event Reporting The Government or contractor/subcontractor personnel responsible for causing a “life cycle event” (i.e., abandoned, consumed, destroyed by accident, destroyed by combat, donated, exchanged – repair, exchanged – sold, exchanged – warranty, expended – experimental/target, expended – normal use, leased, loaned, lost, reintroduced, retired, scrapped, sold – foreign government, sold – historic, sold – nongovernment, sold – other federal, sold – state/local, and stolen) will update the item record in the IUID Registry.

Technical Requirements Period and Place of Performance:

Contract/Order Period of Performance Five years plus 2 one-year options; will be 18 Dec 22 – 17 Dec 29.

Place of Performance The work will be performed both at the contractor’s facility and on Robins Air Force Base.

Contract Data Requirements List(s) (CDRL)

Data Management As a goal, the Contractor shall mark each data delivery with the Delivery Order number, CDRL number, document title, document number, document revision, and document date. The Government uses these, in addition to Multi-user ECP Automated Review System (MEARS) delivery ID, to track its data. The Government uses the document date marked on delivered data for tracking purposes, and does not use the document’s release date. The Contractor shall electronically deliver all contractual data using the Government-controlled method of delivery, Multi-user ECP Automated Review System (MEARS), https://mears1.redstone.army.mil/mears/Default.aspx. The Contractor shall work with the government to ensure that an adequate number of Contractor personnel obtain and possess Public Key Infrastructure (PKI) certification from an accepted Government source. The Contractor shall be receptive to the training offered by the Government on the MEARS system. The Contractor shall prepare, maintain, and track the contract data status, schedule and ensure timely data deliveries. An alternate method of delivery when MEARS is down for maintenance will be the DISA application, known as DOD SAFE, https://safe.apps.mil/. It will be available to all DOD Common Access Card (CAC) holders or Contractor personnel who possess Public Key Infrastructure (PKI) certification from an accepted Government source.

Quality of CDRL Deliverable The Government may reject a deliverable for technical or minor errors found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, applicable Data Item Description, PWS, Task Description, or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within the specified number of business days on the suspense of Government rejection.

Data Accession List The Contractor shall maintain a current listing of all non-CDRL data generated in performance of the contract in a Data Accession List (DAL) electronic information system accessible by the Government. All technical documentation and other data generated in performance of this program shall be made available to the Government via the DAL. The Contractor shall provide a central point of contact for Data Management who shall ensure contract data compliance with the contract.

(CDRL A023, DI-MGMT-81453B/T, Data Accession List (DAL))

Deliverable File Formats The Contractor shall deliver data in one of the Microsoft Office family of products native format. When a deliverable contains hand written text or otherwise cannot be delivered in a Microsoft file format, the Contractor may use Adobe Acrobat file format. Some exceptions may apply, such as executable software code.

Requirements Applicable to all Delivery Orders Configuration Baseline The scope of services performed under this Contract is for the Sniper pods procured with the product and functional baseline configurations defined below:

a. Product Baseline

(1) Sniper CMDL Targeting Pod P/N 77420000-049

(2) Sniper -059 Targeting Pod P/N 77420000-059

(3) Sniper ATP-SE Targeting Pod P/N 77422000-009

(4) Sniper ATP-D Targeting Pod P/N 77422000-109

b. Functional Baseline. The Sniper pod performance requirements and applicable Aircraft Interfaces as defined in:

(1) System Specification Sniper XR (U), 77420004, Rev E

(2) System Specification Sniper ATP For 77420000-059, Rev B

(3) System/Subsystem Specification Sniper ATP-SE, 77422004, Rev F

· Applies to ATP-SE P/N 77422000-009, and ATP-D P/N 77422000-109 Compliance Documents The Contractor shall ensure that all work performed under this contract meets the requirements as specified in this contract, including, as applicable, the functional baseline requirements listed in the Configuration Baseline of this PWS, and CDRLs. The compliance and reference documents are shown in Appendix A. The documents of the exact issue shown at the time of initial contract award form a part of this PWS to the extent specified herein. Only documents referenced within the specified requirements are applicable, and only to the extent applied to the requirement. In the event of a conflict between documents referenced and the PWS, the PWS shall take precedence.

Configuration Management The Contractor shall accomplish Configuration Management (CM) tasks in accordance with existing CM processes. As required in applicable DOs, the Contractor shall submit a Configuration Management Plan (CMP A013). The Contractor’s CMP shall include the Contractor’s internal processes for configuration identification, specification change control, engineering data management, configuration status accounting, configuration change control, and deficiency reports. The Government shall have CM authority of the Sniper functional baselines. The Contractor shall update Sniper functional configuration baselines identified in Configuration Baseline through the use of ECPs. The Contractor shall have CM authority of the Sniper allocated baseline, product baseline, and Sniper-unique Support Equipment. The Contractor shall define, maintain, and update each Sniper product configuration baseline identified in Configuration Baseline through the use of its internal CM process. The fielding of OFPs shall be controlled by the Government, while firmware updates shall be controlled by the Contractor.

(A013, DI-SESS-80858D, Supplier's Configuration Management Plan) Contractual and Financial Management Proposals shall be worked jointly between the Government and Contractor until such time as a final proposal is submitted.

Service Contract Reporting: In accordance with 10 United States Code 2330a, the Contractor shall provide an annual count of Contractor/Subcontractor personnel performing work for each fiscal year if the DoD is the requiring activity and if the acquisition is in excess of $3,000,000.00. The Contractor shall report all Contractor labor hours, including Subcontractor labor hours, required for performance of the services provided under the contract in the System for Award Management (SAM). Reporting shall be conducted for each fiscal year in accordance with the Service Contract Reporting User’s Guide located on the SAM website https://www.sam.gov/SAM/transcript/SCR_QSG.pdf. The Contractor shall establish a record for the contract/order in SAM no later than 30 calendar days after contract/order award. Additional information and user manuals for government personnel and Contractors are available at https://www.sam.gov. A DoD Guidebook for Service Contract Reporting in SAM is available on the DoD Procurement Toolbox at https://dodprocurementtolbox.com/site-pages/service-contract-reporting-scr. The contractor may present proposals using contract change proposals.

The Contractor shall submit Contract Funds Status Reports (CFSR) (A012) for all Delivery Orders that include cost-plus type funding. The Contractor will submit Contract Change Proposals (CCPs) (A046) on an as-needed basis for both cost-plus and fixed price type Delivery Orders.

(A012, DI-MGMT-81468A, Contract Funds Status Report (CFSR)); (A046, DI-ADMN- 81401C, Contract Change Proposals (CCPs))

Program Management The Contractor shall manage and/or direct all efforts through use of its existing Management Control System to provide visibility into the status of schedule and performance objectives. The Contractor’s Program Management activities shall include program coordination, data management, program finance support for cost control, risk management, other key functions Delivery Schedule Contract delivery schedules shall be mutually negotiated between the Government and the Contractor for all deliveries under this contract. See also Integrated Master Schedule.

Integrated Master Schedule As required by applicable Delivery Order, the contractor shall deliver an Integrated Master Schedule (IMS) per Integrated Program Management Report (IPMR) Format 6. The IMS shall include projected delivery dates of all CDRLs, hardware, and software due under the Delivery Order. Once approved by the Government, these CDRL delivery dates become contractually binding and supersede dates specified by a Delivery Order’s Task Description.

(A002, DI-MGMT-81861B/T, Integrated Program Management Data and Analysis Report (IPMDAR)) Single Process Initiatives Lockheed Martin Missiles and Fire Control (LMMFC) and its subcontractors, including other Lockheed Martin entities, are hereby authorized to work to and/or otherwise implement Single Process Initiatives in lieu of military or Federal specifications and standards approved by the designated Divisional Administrative Contracting Officer (DACO). The Contractor shall provide the latest list of single process initiatives, upon Government request.

Integrated Production & Process Development & Risk Management As required in applicable DOs, the Contractor shall provide for integrated process/product development, production, and risk management. The Contractor shall have the necessary resources and expertise to provide the contracted products in compliance with the applicable performance specifications and to meet project budgets and schedules.

Status Reports As required in applicable DOs, the Contractor shall submit a Status Report which provides a detailed status of all events pertinent to the contract and production of the deliverables. This report shall be in Contractor format and contain, at a minimum, a summary of work performed, accomplishments, DD250s, concerns/issues and path forward since the prior reporting period.

(A040, DI-MGMT-80368A/T, Status Report) Quality Requirements The Contractor shall manage and execute the design and verification of all prime mission equipment and supporting equipment. These actions shall include, but not be limited to, all aspects of design, testing, and supply management—to include supplier and major subcontractor management, parts procurement, inventory control, parts tracking, kitting, expediting, assembly, test, conformance verification, and status reporting. The Contractor shall implement a Quality Program Plan based on the Contractor’s Best Value Manufacturing Plan, which shall maintain an effective and economical quality system in accordance with AS9100D. The system shall provide controls of process and product characteristics and include criteria and methodology that are used to validate conformance to performance specifications and to achieve continuous improvement. The quality system shall be an integral and integrated part of the Contractor’s complete management system. As required in applicable DOs the Contractor shall deliver, for Government information only, the quality system procedures, planning and all other documentation and data that comprise the quality system (for both hardware and software).

(A044, DI-QCIC-81722/T, Quality Program Plan (QPP)) Risk Management The Contractor shall establish and maintain a risk/opportunities management program (to include an annual Integrated Risk Assessment review with the Government) to be held in conjunction with a Government & Contractor meeting such as Sniper ATP program reviews.

Meeting Support The Contractor shall conduct, attend, support and participate in regular planned and scheduled meetings which are mutually agreed with the Government as necessary to facilitate continued performance improvement and risk. The planned meetings shall include semiannual Program Management Reviews (PMRs) at the Contractor’s facility. The Contractor’s semiannual PMRs shall address risk management, program management, contracting, finance, and logistics status, data, and issues. The frequency of the PMRs may be decreased at Government direction depending upon the program stability.

Associate Contractor Agreements (ACAs) The Contractor shall establish ACAs with aircraft prime Contractors as necessary and actively support the establishment and control of interface agreements as necessary to support required integration to the platforms identified.

Systems Engineering As required in applicable DOs, the Contractor shall submit a Systems Engineering Management Plan. The Contractor shall ensure that system design integrity is maintained at the system and LRU levels.

The Contractor shall provide up to 100 drawings and/or documents yearly limited to existing items in Contractor format for engineering research purposes only.

(A036, DI-SESS-81785A/T, Systems Engineering Management Plan (SEMP)); (A037, DI-SESS-81003F, Commercial Drawings/Models and Associated ListsCommercial Engineering Design Data and Associated Lists) Operational Safety, Suitability, and Effectiveness (OSS&E) Support This requirement applies to all Delivery Orders for Development Efforts and Agile Software Sustainment. The Contractor shall support the Government’s OSS&E process by providing data for the proper assessment of Sniper-related hardware and/or software development, software sustainment, testing, qualifications and/or certifications. The Contractor shall provide a Subject Matter Expert as required to perform related studies and/or analysis. The Contractor shall prepare and submit reports in support of OSS&E Support (A024).

(A024, DI-MISC-80711A, Scientific and Technical Reports) Enhancements And Developmental Efforts This section is intended for efforts associated with 3010 (new capability), 3600 (development) funding, and 3400 (Operations and Maintenance). As required in applicable DOs, the Contractor shall ensure Sniper hardware and software changes are designed and produced to allow interchangeability of LRUs within the Sniper configuration baseline to the greatest extent possible. The Contractor shall provide support for, but not limited to, the following for the Sniper ATP hardware, firmware and/or software change:

· the design,

· development,

· pod integration

· platform integration (to include field support),

· System Safety analysis,

· Cyber Security taskings,

· verification,

· software or design verification test

· acceptance testing

· qualification testing

· flight testing (to include Qualification Test and Evaluation (QT&E),

· Qualification Operational Test and Evaluation (QOT&E),

· Force Development Evaluation (FDE),

· fabrication,

· production,

· quality control,

· tooling,

· support equipment, fixtures, or special test equipment required to support the hardware or software change

This range of tasks will also include configuration and data management, program management, logistics support, and status reports, and may include spectrum management, subcontract/supplier material management, deficiency report investigation, deficiency resolution, certification support, and other related tasks. The contractor shall provide a soft copy of A015, DI-SESS-81254C, Request for Nomenclature (DD Form 61) in adobe format also. The Contractor shall implement functional changes using the ECP process.

(A001, DI-NDTI-80566A/T, Test Plan); (A003, TMCR 86-01R, Air Force Technical Manual Contract Requirements (TMCR) – Depot Level and Commodity Technical Manual); (A007, DI-ILSS-80872/T, Training Materials (Aircrew Academics)); (A010, DI-ADMN-81373, Presentation Material); (A011, DI-SESS-80639E, Engineering Change Proposal (ECP); (A014 TMCR 86-01R (TMCR)P/T, Air Force Technical Manual Contract Requirements (TMCR) – Aircraft/Platform Source Data); (A015, DI-SESS-81254C, Request for Nomenclature (DD Form 61)); (A017; DI-IPSC-81433A, Software Requirements Specification (SRS)); (A018, DI-IPSC-81431A, System/Subsystem Specification (SSS)); (A019, DI-IPSC-81441A/T, Software Product Specification (SPS)); (A020, DI-IPSC- 81442A, Software Version Description (SVD)); (A021, DI-AVCS-80700A, Computer Software Product End Items); (A023, DI-MGMT-81453B, Data Accession List (DAL), (A024, DI-MISC-80711A, Scientific and Technical Reports); (A025, DI-MISC-81174, Frequency Allocation Data); (A026, DI-MISC-81454D, Computer Program Identification Number (CPIN) Catalog Information);Automated Computer Program Identification Number (ACPIN) Data And Control Record); (A027, DI-NDTI-80603A, Test Procedure); (A028, DI-NDTI-80809B, Test/Inspection Report); (A032, DI-SAFT-80102C/T, Safety Assessment Report (SAR)); (A038, DI-ADMN-81250B, Conference Minutes); (A039, DI- ILSS-80872/T, Training Materials (Operator Training)) Prohibited Materials - Class I Ozone-Depleting Substances (ODS) As required in applicable DOs, The Contractor shall minimize hazardous materials and Class I ODS from the design and manufacturing of individual Sniper upgrades. Use of hazardous materials or Class I ODS shall only be permitted with consent of the Government. As required in applicable DOs, the Contractor shall deliver a Programmatic Environmental Safety and Health Evaluation (PESHE) Plan. (The Government is using the PESHE Plan to replace Environmental Health and Safety Plan(s) delivered under prior contracts.)

(A016, DI-ENVR-81840, Programmatic Environmental Safety and Health Evaluation (PESHE) Plan) Digital Acquisition The Contractor shall apply Digital Engineering / Digital Acquisition concepts to redesign efforts.

Agile Software Sustainment This paragraph is intended to cover software sustainment associated with 3400 funding. As required in applicable DOs, the Contractor shall utilize an Agile Software approach to OFP sustainment. Sustainment will address the Sniper functionality including the various aircraft interface updates. Using the ECP process, the Contractor shall update the System/Subsystem Specification when Agile Software Sustainment alters the functional baseline. The OFP activities will include engineering analyses, deficiency report investigation, deficiency resolution, software modifications, integration, System Verification Tests (SVT), System Integration Lab (SIL) tests, ground tests, flight tests, system safety, Cyber Security support, configuration and data management, program management, logistics support, and status reports to facilitate fielding authorizations. Software modification and integration includes the incorporation of software and firmware originally developed on a Delivery Order that was outside the Agile Software Sustainment process. Agile Software Sustainment shall result in a quality controlled, fully qualified, operationally released version of the OFP that has a Computer Program Identification Number (CPIN) assigned by the Government.

(A001, DI-NDTI-80566A/T, Test Plan); (A007, DI-ILSS-80872/T, Training Materials (Aircrew Academics)); (A010, DI-ADMN-81373, Presentation Material); (A011, DI-SESS-80639E, Engineering Change Proposal (ECP); (A014 TMCR 86-01R (TMCR)P/T, Air Force Technical Manual Contract Requirements (TMCR) – Aircraft/Platform Source Data (A017; DI-IPSC- 81433A, Software Requirements Specification (SRS)); (A018, DI-IPSC-81431A, System/Subsystem Specification (SSS)); (A019, DI-IPSC-81441A/T, Software Product Specification (SPS)); (A020, DI-IPSC- 81442A/T, Software Version Description (SVD)); (A021, DI-AVCS-80700A, Computer Software Product End Items); (A023, DI-MGMT-81453B, Data Accession List (DAL), (A024, DI-MISC-80711A, Scientific and Technical Reports); (A025, DI-MISC-81174, Frequency Allocation Data); (A026, DI- MISC-81454D, Computer Program Identification Number (CPIN) Catalog InformationAutomated Computer Program Identification Number (ACPIN) Data And Control Record); (A027, DI-NDTI-80603A, Test Procedure); (A028, DI-NDTI- 80809B, Test/Inspection Report); (A032, DI-SAFT-80102C/T, Safety Assessment Report (SAR)); (A038, DI-ADMN-81250B, Conference Minutes); (A039, DI- ILSS-80872/T, Training Materials (Operator Training))

Engineering Change Proposals (ECPs) The Contractor shall use its own CMP and ECP forms, as applicable, for allocated or product baseline changes that are developed exclusively at private expense.

The following paragraph applies only when Government funding or mix funding is used. For Sniper or Sniper-related item changes, the Contractor shall prepare and submit an ECP using DD Form 1692. The ECP shall address data rights and include the impacts to Sniper prime mission equipment, support equipment, engineering, test, software, logistics, TMs, maintenance impacts to include O-level and D-level repairs, and safety; or, specifically state no impact to these areas. Software includes test software, software used to program programmable devices, and computer software configuration items.

The Contractor shall obtain DCMA concurrence on the classification of ECPs. The ECP is intended as a Government funding authorization tool and not intended to alter the change process specified by the CMP. Therefore, the Government will require ECPs when Government funding is used, and not only when an update to the System/Subsystem Specification is needed. The Contractor shall implement an ECP only when the change is incorporated into the contract by contract modification, or when directed by the Government PCO.

(A011, DI-SESS-80639E, Engineering Change Proposal (ECP)) Variances The Contractor shall not manufacture items for acceptance by the Government that incorporate a known departure from the approved specifications or Technical Data Package (TDP) content, unless a Request For Variance (RFV) has been submitted and incorporated into the contract by contract modification, or directed by the Government PCO. The Contractor shall utilize conforming materials and parts as specified by the TDP unless the Government has approved a RFV. The Contractor shall use DD Form 1694 to submit the RFV.

(A034, DI-SESS-80640E/T, Request For Variance (RFV)) Engineering Data The Engineering Data requirements herein apply only when a Government funded ECP has required delivery of product drawings. The Contractor shall develop and deliver Engineering Data that accurately depicts the item(s) associated with the ECP. The Engineering Data shall represent the approved, tested, and accepted configuration of the defined item(s). Engineering Data includes, as applicable, Computer Aided Design (CAD) data, Gerber data, and Bill of Materials (BOM). The Engineering Data shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). Engineering Data delivery shall include the entire document and associated data file (if applicable). For example, when a portion of a document is revised the entire document shall be delivered. Engineering Data shall be delivered to the Government with data rights to be specified by the ECP. The Engineering Data shall be prepared using Engineering Practices Manual EPM-DRAFTING as a guide. The Contractor shall levy on subcontractors and sub-vendors the same requirements for Engineering Data as are levied on them by this contract. This requirement shall apply at all tiers of subcontractor/vendor levels associated with the program.

(A033, DI-SESS-81000F/T, Product Drawings/Models and Associated Lists) Anti-Tamper As required in applicable Delivery Orders:

Anti-Tamper protects US Critical Information and Technology from being exploited. Critical Program Information (CPI) and Critical Program Technology are defined in DoDI 5200.39. The Contractor shall conduct a design analysis and prepare and submit a Technical Report-Study/Service (subtitled Anti-Tamper Plan) for Government approval (A029). The Contractor shall identify and protect the Anti-Tamper Plan in accordance with the Anti-Tamper Security Classification Guide. For each critical item/technology, the plan shall identify whether or not anti-tamper provisions will be required, specify the provision(s), and how they will be implemented.

Part 1:

The Contractor shall identify CPI/Critical Component (CC) in accordance with the DoD 6-step CPI/CC process provided as Government Furnished Information (GFI), and submit a list of recommended CPI/CC with rationale and an Anti-Tamper strategy/plan for review 90 days ARO for Government approval.

Part 2:

The Government will provide a final CPI/CC list to the Contractor as GFI. The Contractor shall develop and implement an Anti-Tamper Plan in accordance with DoDI 5200.39 using the DOD Anti-Tamper Template, provided as GFI. The Contractor shall submit an initial Anti-Tamper Plan 60 after the contract award.

Part 3:

The Contractor shall update the Anti-Tamper Plan (Final Anti-Tamper Plan), to include a Verification and Validation (V&V) Plan, 60 days prior to applicable CDR for Government approval.

(A029, DI-MISC-80508B, Technical Report-Study/Service) Software Version Descriptions Inventory of software contents shall include both source and executable file listings. File listings shall include the time stamp.