Attachment-1_CATP2_PWS_V6.pdf

Contract FA8540-23-D-0001 Revision 6

Date: 1 Sept 26

FA8540-23-D-0001 PWS Page 1 of 68

Sniper Comprehensive Advanced Targeting Pod

(CATP) 2

Performance-Based Work Statement (PWS)

FA8540-23-D-0001 PWS Page 2 of 68

Change Summary Rev Paragraph Change 0 All Initial Release 1 2 Services Summary changes to clarify that Availability Rate and

MTBME will be calculated quarterly. Deleted adherence to the Quality Management System as a Performance Objective

1 3.2, 3.4 Added new Government Property reporting requirements.

1 3.5 Added statements that make material and data generated under this effort to become Government property.

1 3.6.2.1 Happy-to-glad change of GFP to IUID-identified property.

1 4.2, 4.4, 4.4.2, 4.4.3, 4.5.5, 4.6.5.4, 4.6.5.11

Corrected errors found in the PWS-to-CDRL cross reference.

Corrected the title of CDRLs A026, A037, A042 and A047.

1 4.2.4 Added a paragraph for Deliverable File Formats. This requirement had previously appeared on the CDRLs.

1 4.4.2 Deleted the requirement for Request For Nomenclature to be delivered in Adobe format.

1 4.4.10 Expanded Type 1 Training course material to include theory of operation and instruction on how to operate the system, consistent with the language from an old Wright Patterson Sniper contract.

1 4.5.1, 5.2.7, 5.5.1

Happy-to-glad changes.

1 4.5.6 One happy-to-glad change, and deleted the redundant reference to CDRL A024.

1 4.6.1 Specified that the Fleet Availability Rate will be calculated quarterly.

1 4.6.5.15 Added a paragraph for Additional Depot Capability Standup.

This requirement is in the prior CATP.

1 4.6.10.4, 4.6.10.6

Clarification of calendar versus business days.

1 5.2 Added security regulations.

1 5.2.5 Added COMSEC requirements and regulations.

1 5.5.2 Deleted the existing paragraph titled Safety and Health

Plan/Program. This paragraph required the Contractor tho have a Safety and Health Plan. Subsequent paragraphs at Header Level 3 were renumbered.

1 5.5.2 For Mishap Notification/Investigation, modified who should be contacted to report a mishap.

1 5.7 Changed how Service Contract Reporting is to be accomplished.

FA8540-23-D-0001 PWS Page 3 of 68

1 5.8 Changed Invoicing/Payment and Receipt/Acceptance to specify the Wide Area Workflow module in Procurement Integrated Enterprise Environment (PIEE).

1 5.9 Added the FAR requirement for Combating Trafficking in Persons.

2 Various Format improvements and spelling out of acronyms.

2 1.3 Replaced Extended Range (XR) with ATP. Added acronyms.

2 3.5.2 Added EESOH-MIS 2 3.6.2.2 Deleted the paragraph titled Life Cycle Event Reporting.

2 4.1.2 Expanded the Place of Performance to worldwide locations.

2 4.2 Corrected PWS paragraph references.

2 4.2.2 Deleted the paragraph titled Quality of CDRL Deliverable.

2 4.3.1 Clarified the drawing numbers for the System Specifications.

2 4.3.3 Added the names of the functional baselines.

2 4.4.1 Made the paragraph applicable when required by a Delivery

Order.

2 4.4.2.2 Added the reason for Digital Engineering / Digital Acquisition.

2 4.4.10 Deleted Type 1 Training details that applied to Aircrew

Academics.

2 4.5.1 Limited the applicability of the AAR to "As required in applicable

Delivery Orders".

2 4.5.2 Significant change to the Cyber Security Strategy Implantation

Plan paragraph to include making the paragraph applicable when required by a Delivery Order.

2 4.5.3 Made the Security Evaluation Document applicable when required by a Delivery Order.

2. 4.5.4 Made the 1553 Bus Code Review applicable when required by a Delivery Order.

2 4.5.5 Clarified that Penetration Testing is Contractor-conducted.

2 4.5.7 Clarified that the Program Protection Implementation Plan is applicable when required by a Delivery Order. Made the PPIP applicable after it is approved.

2 4.6.2 Expanded MTBME exclusions FROM Site Activation Training TO any training.

2 4.6.10.2 Deleted the references to Site Activations.

2 4.6.10.3 Deleted the paragraph on CONUS/OCONUS Site Activation.

2 4.6.10.4 Deleted the paragraph on Site Survey 2 4.6.10.5 Deleted the paragraph on Site Activation Support Equipment 3 3.2 Excluded repair and return items from Contractor reporting of

Government property.

FA8540-23-D-0001 PWS Page 4 of 68

3 3.5 Deleted the new language that made all contract material, and

CDRLs, Government property.

3 4.2 Multiple Data Rights changes. Deleted Aircrew Academics

(Operator Training will take its place). Deleted CDRL A006, Failure Summary And Analysis Report.

3 4.2.1 Added a requirement for the Contractor to meet with the Government CM to agree o n CDRL due dates. This replaces the CDRL due dates going into the IMS.

3 4.2.2 Added a paragraph addressing DFARS Data Rights Assertions.

3 4.3.1 Deleted the ATP-XR and its System Specification from the scope.

3 4.3.5.2 Deleted the provision for CDRL due dates in the IMS to be contractually binding.

3 4.4.4 Deleted the requirement to delete an ECP for Government funded changes, except that it is still required for functional baseline changes.

3 4.4.6 Deleted ECP language from Engineering Data.

3 4.4.10 Deleted AFI 36-2670 and AFTECMAN 36-2601 as the standards for Type 1 Training.

3 4.5.6 Replaced Klocwork with Fortify as a code vulnerability analysis tool.

3 4.6.5.7 Deleted CDRL A006, Failure Summary And Analysis Report.

3 4.6.5.14.2 Deleted the reference to ECP paragraph 4.4.4. Added the CCP

CDRL A046.

3 4.6.7.5 Added LRU repair and replacement cost to the definition of

Beyond Economic Repair.

3 4.6.7.6.2 Deleted APO addresses and TAC funding for classified DDR international shipment.

3 4.6.10.2 Deleted site activations.

3 4.6.10.3 Reserved the paragraph on site activations and deleted all content.

3 4.6.10.4 Reserved the paragraph on Site Survey and deleted all content.

3 4.6.10.5 Reserved the paragraph on Site Activation Support Equipment and deleted all content.

3 4.7 Added a table specifying ATP-D kit content.

3 5.2.2 Changed the paragraph title to Program Protection

Implementation Plan (PPIP).

3 Appendix A Deleted the reference to the Sniper XR System Specification.

Updated the revision letter and dates of the other two System Specifications.

3 Appendix D Reserved the paragraph on Initial LRU Spares and deleted all content.

FA8540-23-D-0001 PWS Page 5 of 68

3 Appendix F Various deletions of unused acronyms.

3 Various Expanded the “As required in applicable DOs" to clarify that these paragraphs have to be activated by future Delivery Orders.

3 Various Format changes such as case changes, spacing and TOC updates are not marked with track changes.

4 4.5.8; 4.4.2 Adding CDRL x048 and x049 to the IDIQ. It will be used on individual delivery orders. Updated CDRL table and Table of Contents too.

4 3.2, 4.2 Adding CDRL x050 to the IDIQ. It will be used on individual delivery orders. Updated CDRL table as well.

4 4.5 Cybersecurity was changed to remove “and implementation changes”

4 4.2 Adjusted to show specific CDRL titles for each option year, per new internal policies

Various Change of RAMPOD references to APSR due to system change

5 4.2 Changed data rights for A014-G014 from unlimited to limited 6 Various USG review of LM redlines for extension years 6 and 7, change from 261k expected hours to 135k, change in metric language to include contractor website and new USG maintenance database

FA8540-23-D-0001 PWS Page 6 of 68

Table Of Contents

Paragraph Page

Description of Services

Objective(s) Benefit to the United States Air Force (USAF) Background

Services Summary (SS)

Government Property and Services

Government Furnished Property (GFP) Contractor Responsibility Definition of Loss of Government Property:

Reporting Loss of Government Property Return or Retention of Government Property

3.5.1. Phone Service

3.5.2. Computer Service

3.5.3. Travel

3.5.4. Common Access Card (CAC)

Item Unique Identification (IUID)

3.6.1. Marking Requirement

3.6.2. Reporting in IUID Registry

Technical Requirements

Period and Place of Performance:

4.1.1. Contract/Order Period of Performance

4.1.2. Place of Performance

Contract Data Requirements List(s) (CDRL)

4.2.1. Data Management

4.2.2. DFARS Data Rights Assertions

4.2.3. Data Accession List

4.2.4. Deliverable File Formats

Requirements Applicable to all Delivery Orders

4.3.1. Configuration Baseline

4.3.2. Compliance Documents

4.3.3. Configuration Management

4.3.4. Contractual and Financial Management

4.3.5. Program Management

Systems Engineering

FA8540-23-D-0001 PWS Page 7 of 68

4.4.1. Operational Safety, Suitability, and Effectiveness (OSS&E) Support

4.4.2. Enhancements And Developmental Efforts

4.4.3. Agile Software Sustainment

4.4.4. Engineering Change Proposals (ECPs)

4.4.5. Variances

4.4.6. Engineering Data

4.4.7. Anti-Tamper

4.4.8. Software Version Descriptions

4.4.9. System Safety

4.4.10. Type 1 Training

Cybersecurity

4.5.1. Architecture Analysis Report (AAR)

4.5.2. Cyber Security Strategy Implementation Plan

4.5.3. Security Evaluation Document

4.5.4. 1553 Bus Code Review

4.5.5. Information Assurance Support

4.5.6. Vulnerability Assessment

4.5.7. Program Protection Implementation Plan (PPIP)

4.5.8. Security Test Plan

Availability Support

4.6.1. Fleet Availability Rate

4.6.2. Mean Time Between Maintenance Events (MTBME)

4.6.3. Operating Hour Reconciliation

4.6.4. Availability Support — Fixed

4.6.5. Field Spare and Repair Parts

4.6.6. Technical Manuals

4.6.7. Availability Support—Variable

4.6.8. Counterfeit Electronic Parts

4.6.9. Government-Industry Data Exchange Program (GIDEP)

4.6.10. Logistics

4.6.11. Maintenance Workload 50/50 Report

4.6.12. Stand-Alone Support Equipment and LRU Spares

4.6.13. Over & Above

4.6.14. Pod Test and Evaluation

Production Hardware Upgrade Kits

4.7.1. Upgrades and Availability Support

4.7.2. Obsolescence – New Hardware & Upgrade Kits

4.7.3. Variances

Quick Program Support (Subtasks)

General Information

Continuation of Essential DoD Contractor Services Security Management:

FA8540-23-D-0001 PWS Page 8 of 68

5.2.1. Controlled Unclassified Information (CUI)

5.2.2. Program Protection Implementation Plan (PPIP)

5.2.3. Criticality Analysis

5.2.4. Security Classification Guide (SCG)

5.2.5. Communications Security (COMSEC)

5.2.6. Personnel Security

5.2.7. Security Incidents and Violations

Environmental Management System (EMS) Agency Affirmative Procurement Programs Safety Requirements

5.5.1. Contractor Compliance

5.5.2. Mishap Notification/Investigation

5.5.3. Voluntary Protection Program (VPP)

Inspection of Services Service Contract Reporting Invoicing/Payment and Receipt/Acceptance Trafficking in Persons

Appendices

Appendix A: References

Appendix B: Subtask Content

Appendix C: Previously identified Obsolete Repair Parts

Appendix D: Reserved

Appendix E: LRUs Repaired Under Public/Private Partnership Agreement

Appendix F: Acronyms

FA8540-23-D-0001 PWS Page 9 of 68

Description of Services

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 ATP versions remain but most have been upgraded to ATP Sensor Enhancement (ATP-SE) version, which added Digital Data Recording (DDR) and Two Way Data Link (TWDL) 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.

FA8540-23-D-0001 PWS Page 10 of 68

Services Summary (SS)

Performance Objectives PWS Para.

Performance Threshold

Maintain availability rate. 4.6.1 Minimum 90% as computed per provided instructions for calculation. This metric will be calculated quarterly.

Ensure Reliability – Mean Time Between Maintenance Events (MTBME).

4.6.2 Maintain a 428-hour MTBME score for

the Sniper pod Configuration Baseline as computed according to provided calculation formula. This metric will be calculated annually.

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) excluding repair and return items. 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 excluding repair and return items. In the event the automated transfer does not work, the Contractor shall provide the data to the Procuring Contracting Officer.

As part of the above paragraph, the Contractor shall also complete a semi-annual physical inventory of Government Property with a CDRL delivery (CDRL x050) due 30 days after each inventory is conducted. The current standard is for the Government and Contractor to conduct Government Property inventory checks semi-annually, typically

FA8540-23-D-0001 PWS Page 11 of 68 during the week of Program Management Reviews. Any deviations shall be agreed to in advance by both parties.

(CDRL x050, DI-MGMT-80441D, Government Property Inventory Report)

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 report loss of Government property 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 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

FA8540-23-D-0001 PWS Page 12 of 68 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.

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

3.5.2. 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, EESOH-MIS 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.

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

FA8540-23-D-0001 PWS Page 13 of 68

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.

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

FA8540-23-D-0001 PWS Page 14 of 68 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)

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

3.6.2. 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 IUID-identified property to the Contractor. The Contractor is required to record the receipt of IUID-identified property from the Government. The Contractor is required to record the return of IUID-identified property to the Government.

Reserved

Technical Requirements

Period and Place of Performance:

4.1.1. Contract/Order Period of Performance

Five years plus 2 one-year options; will be 18 Dec 22 – 17 Dec 29.

FA8540-23-D-0001 PWS Page 15 of 68

4.1.2. Place of Performance

The work will be performed both at the Contractor’s facility and on Robins Air Force Base, and will include worldwide locations as needed, or as specified on the DD254.

Contract Data Requirements List(s) (CDRL)

FA8540-23-D-0001 PWS Page 16 of 68

A015 B015 C015 D015 E015 F015 G015 DI-SESS-

81254C

Request for Nomenclature (DD Form 61)

4.4.2 Unlimited

A016 B016 C016 D016 E016 F016 G016 DI-ENVR-

81840

Programmatic Environmental Safety and Health Evaluation (PESHE) Plan

4.4.2.1 Unlimited

A017 B017 C017 D017 E017 F017 G017 DI-IPSC-

81433A

Software Requirements Specification (SRS)

4.4.2, 4.4.3 Restricted

A018 B018 C018 D018 E018 F018 G018 DI-IPSC-

81431A

System/Subsystem Specification (SSS) 4.4.2, 4.4.3 Govt Purpose

A019 B019 C019 D019 E019 F019 G019 DI-IPSC-

81441A/T

Software Product Specification (SPS)

4.4.2, 4.4.3,

4.6.5.11 Restricted

A020 B020 C020 D020 E020 F020 G020 DI-IPSC-

81442A/T

Software Version Description (SVD) 4.4.2, 4.4.3 Govt Purpose

A021 B021 C021 D021 E021 F021 G021 DI-AVCS-

80700A

Computer Software Product End Items 4.4.2, 4.4.3 N/A

A022 B022 C022 D022 E022 F022 G022 DI-MGMT-

81398C

Hazardous Materials Management Program (HMMP) Plan

4.6.7.2 Unlimited

A023 B023 C023 D023 E023 F023 G023 DI-MGMT-

81453B

Data Accession List

(DAL)

4.2.3, 4.4.2, 4.4.3, 4.6.5.8 Unlimited

A024 B024 C024 D024 E024 F024 G024 DI-MISC-

80711A

Scientific and Technical Reports

4.4.1, 4.4.2, 4.4.3, 4.5.1, 4.5.4, 4.5.6, 4.6.13, 4.6.14, 5.2.3

Limited for Safety of Flight letter, HAMAAR, Cybersecurity (1553 Bus Code Review, AAR), Delta CDR reports. Restricted for Static or Dynamic Code Vulnerability Analysis. Govt Purpose for the Software Roadmap.

TBD based on delivery order:

OSS&E Support, Over and Above Report, Pod T&E, and Criticality Analysis.

A025 B025 C025 D025 E025 F025 G025 DI-MISC-

81174

Frequency Allocation Data 4.4.2, 4.4.3 Unlimited

A026 B026 C026 D026 E026 F026 G026 DI-MISC-

81454D

Computer Program Identification Number (CPIN) Catalog Information

4.4.2, 4.4.3,

4.6.5.11 Unlimited

A027 B027 C027 D027 E027 F027 G027 DI-NDTI-

80603A Test Procedure 4.4.2, 4.4.3 Govt Purpose

FA8540-23-D-0001 PWS Page 17 of 68

A028 B028 C028 D028 E028 F028 G028 DI-NDTI-

80809B

Test/Inspection Report 4.4.2, 4.4.3 Restricted

A029 B029 C029 D029 E029 F029 G029 DI-MISC-

80508B

Technical Report- Study/Service (Anti- Tamper Plan)

4.4.7 Limited

A030 B030 C030 D030 E030 F030 G030 DI-MISC-

81832

Counterfeit Prevention Plan 4.6.8 Govt Purpose

A031 B031 C031 D031 E031 F031 G031 DI-MISC-

81762A

Security Evaluation Document (SED) 4.5.3 Limited

A032 B032 C032 D032 E032 F032 G032 DI-SAFT-

80102C/T

Safety Assessment Report (SAR) 4.4.2, 4.4.3 Unlimited

A033 B033 C033 D033 E033 F033 G033 DI-SESS-

81000F/T

Product Drawings/Models and Associated Lists

4.4.6 Data rights as specified by future Delivery Order(s)

A034 B034 C034 D034 E034 F034 G034 DI-SESS-

80640E/T

Request for Variance (RFV) 4.4.5, 4.7.3 Unlimited

A035 B035 C035 D035 E035 F035 G035 DI-PSSS-

81656B/T

Bill Of Materials (BOM) For Logistics and Supply Chain Risk Management

4.6.5.14.3,

4.7.2 Govt Purpose

A036 B036 C036 D036 E036 F036 G036 DI-SESS-

81785A/T

Systems Engineering Management Plan

(SEMP)

4.4 Unlimited

A037 B037 C037 D037 E037 F037 G037 DI-SESS-

81003F

Commercial Engineering Design Data and Associated Lists

4.4 Limited

A038 B038 C038 D038 E038 F038 G038 DI-ADMN-

81250B Conference Minutes 4.4.2, 4.4.3 Unlimited

A039 B039 C039 D039 E039 F039 G039 DI-ILSS-

80872/T

Training Materials (Operator Training) 4.4.2, 4.4.3 Unlimited

A040 B040 C040 D040 E040 F040 G040 DI-MGMT-

80368A/T Status Report 4.3.5.5 Unlimited

A041 B041 C041 D041 E041 F041 G041 DI-MGMT-

82144/T

Naval Aviation Program Protection Implementation Plan

4.5.7 Limited

A042 B042 C042 D042 E042 F042 G042 DI-MGMT-

82256/T

Supply Chain Risk Management (SCRM) Plan

4.6.5.4 Govt Purpose

A043 Not Used

A044 B044 C044 D044 E044 F044 G044 DI-QCIC-

81722/T

Quality Program Plan (QPP) 4.3.5.6 Unlimited

A045 B045 C045 D045 E045 F045 G045 DI-MGMT-

81749B

Distribution of Department of Defense (DoD) Depot Maintenance Workload (50/50) Report

4.6.11 Govt Purpose

FA8540-23-D-0001 PWS Page 18 of 68

4.2.1. 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, and shall meet quarterly with Government Configuration Management to discuss and agree on CDRL due dates. 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.

4.2.2. DFARS Data Rights Assertions

The Data Rights column in Table 4.2 above identifies data rights associated with CDRL deliverables based on data items comprising each CDRL; where data rights identified as less than unlimited rights are based on data items already in existence before the award of the contract and listed on the Data Assertions List, Attachment 6 of the contract. Any Data Rights for future requirements not covered by Table 4.2 shall be identified to the extent possible using the Data Assertions List, Attachment 6 of the contract. For the avoidance of doubt, the data rights identified in Table 4.2 are based on and consistent with previously asserted data rights and the Data Assertions List, Attachment 6 of the contract.

A046 B046 C046 D046 E046 F046 G046 DI-ADMN-

81401C

Contract Change Proposals

4.3.4,

4.6.5.14.2 Unlimited

A047 B047 C047 D047 E047 F047 G047 DI-MGMT-

81843

Information Assurance (IA) Test Report

4.5.5 Limited

N/A B048 C048 D048 E048 F048 G048 DI-NDTI-

81351 Security Test Plan 4.5.8 Govt Purpose

N/A B049 C049 D049 E049 F049 G049 DI-SESS-

81757A/T

Design Review Information Package (DRIP))

4.4.2 Govt Purpose

N/A B050 C050 D050 E050 F050 G050 DI-MGMT-

80441D

Government Property (GP) Inventory Report

3.2 Govt Purpose

https://mears1.redstone.army.mil/mears/Default.aspx

FA8540-23-D-0001 PWS Page 19 of 68

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

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

4.3.1. 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 -059 Targeting Pod P/N 77420000-059 or later configuration

(2) Sniper ATP-SE Targeting Pod P/N 77422000-009 or later configuration

(3) Sniper ATP-D Targeting Pod P/N 77422000-109 or later configuration

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

(1) System Specification Sniper ATP for 77420000-059 Hardware Configuration, Dwg. No. 77420009, Rev B

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

• Applies to ATP-SE P/N 77422000-009, and ATP-D P/N 77422000-

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

FA8540-23-D-0001 PWS Page 20 of 68

4.3.3. 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 (ATP, ATP-SE, and ATP-D). 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)

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

FA8540-23-D-0001 PWS Page 21 of 68

4.3.5. 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, and 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 hardware and software due under the Delivery Order.

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

FA8540-23-D-0001 PWS Page 22 of 68

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.

FA8540-23-D-0001 PWS Page 23 of 68

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 Engineering Design Data and Associated Lists)

4.4.1. Operational Safety, Suitability, and Effectiveness (OSS&E) Support As required in the applicable Delivery Order, 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)

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

FA8540-23-D-0001 PWS Page 24 of 68 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, o software or design verification test o acceptance testing o qualification testing o flight testing (to include Qualification Test and Evaluation (QT&E), o Qualification Operational Test and Evaluation (QOT&E), o 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 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);

FA8540-23-D-0001 PWS Page 25 of 68

(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)); (x049, DI-SESS-81757A/T, Design Review Information Package

(DRIP))

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 to increase the speed of capability delivery to the warfighter.

4.4.3. 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);

FA8540-23-D-0001 PWS Page 26 of 68

(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 Information); (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))

4.4.4. Engineering Change Proposals (ECPs)

The Contractor shall use its own CMP and ECP forms, as applicable, for allocated or product baseline changes. Functional baseline changes (System/Subsystem Specification) shall require ECP (DD Form 1692) submittal and Government approval.

(A011, DI-SESS-80639E, Engineering Change Proposal (ECP))

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

4.4.6. Engineering Data

As required in applicable Delivery Orders, the Contractor shall develop and deliver Engineering Data. 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).