OPF-L RFP_Attachment J.1_ SOW.pdf

ORGANIC PRECISION FIRES – LIGHT (OPF-L)

STATEMENT OF WORK (SOW)

8 September 2023

Marine Corps Systems Command Quantico, VA 22134

Attachment J.1: Statement of Work (SOW) i

1 NATURE AND SCOPE OF THE ACQUISITION

1.1 Background/Description

1.2 Scope

2 APPLICABLE DOCUMENTS

2.1 General

2.2 Government Documents

2.2.1 Specifications, Standards and Handbooks

2.2.2 Other Government Documents, Drawings, and Publications

2.2.3 Non-Governmental Documents

3 REQUIREMENT

3.1 Production

3.2 Program Management and Data Management

3.2.1 Schedule Planning

3.2.2 Subcontractor Management

3.2.3 Quality Management

3.2.4 Data Management

3.2.5 Program Manager

3.3 Meetings, Formal Reviews, Conferences and Audits

3.3.1 Contractor Responsibilities

3.3.2 Post Award Conference (PAC)

3.3.3 In Process Reviews

3.3.4 System Requirements Review (SRR)

3.3.5 Critical Design Review (CDR)

3.3.6 Test Readiness Review (TRR)

3.3.7 Production Readiness Review (PRR)

3.3.8 Physical Configuration Audit (PCA)

3.3.9 Provisioning Guidance Conference (PGC)

3.3.10 Provisioning Conference (PC)

3.4 Security Requirements

3.4.1 Document Markings Requirements

3.4.2 Common Access Card (CAC) Requirement

3.5 Configuration Management

3.5.1 Product Baseline

3.5.2 Product Description (PD)

3.5.3 Configuration Status Accounting (CSA)

3.5.4 Control/Accountability

3.5.5 Engineering Change Proposals

ii

3.5.6 Requests for Variance

3.5.7 Notices of Revision (NOR)

3.5.8 Notification of Changes to Commercial Equipment/Software

3.6 Environmental, Safety, and Occupational Health (ESOH)

3.6.1 System Safety

3.6.2 Hazard Management

3.6.3 Safety Assessment Report

3.6.4 Software System Safety Engineering and Analysis

3.6.5 Functional Hazard Analysis (FHA)

3.6.6 Material Safety Data Sheets

3.6.7 Support of Government Safety Certification

3.6.8 Explosive Safety

3.7 Cybersecurity

3.8 Radio Frequency Spectrum Compatibility

3.9 Testing

3.9.1 Government Verification Testing

3.9.2 Contractor Test Support for Government Testing

3.9.3 Contractor Training for Government Testing

3.9.4 Familiarization Training for Government Testing

3.9.5 Contractor Acceptance Testing

3.9.6 Contractor Support for Government Operational Testing (OT)

3.9.7 Special Purpose Support Equipment (SPSE)

3.10 Production

3.10.1 Change in Production Facility Location or Break in Production Line

3.10.2 Qualification/Verification of Suppliers

3.11 Supportability

3.11.1 Integrated Logistics Support (ILS)

3.11.2 Contractor Logistics Support (CLS)

3.11.3 Warranty

3.12 Government Property

3.12.1 Government Property Management (GPM)

3.12.2 Government Furnished Property (GFP)

3.13 Deliveries

3.13.1 Packaging, Handling, Storage and Transportation

3.13.2 Preservation and Packaging (P&P)

3.13.3 Development of Marking Requirements

3.13.4 Hazardous Materials

iii

3.13.5 Signed Receipts

3.13.6 Ammunition Data Cards (ADC)

3.14 Failure Reporting, Analysis and Corrective Actions System

3.15 Provisioning Technical Documentation

3.15.1 Provisioning Parts List (PPL)

3.15.2 Special Tools and Test Equipment List (TTEL)

3.15.3 Bill of Materials

3.15.4 Engineering Data For Provisioning

3.15.5 Copyright Release

3.15.6 Operator Technical Publications

3.16

3.17 Training

3.17.1 Training Developers and Instructors

3.17.2 Training Material

3.17.3 Job Aids

3.17.4 Training Conduct

3.17.5 Training Verification

3.17.6 Training Material Changes

3.17.7 Course Conduct Information Package (Trainee and Training Course Completion Data)

3.18 Demilitarization/Disposal Procedures

1 NATURE AND SCOPE OF THE ACQUISITION

1.1 Background/Description

The purpose of this contract is to procure a Non-Developmental Item Loitering Munition System that is man-packable by dismounted Marines in the infantry rifle squad. The system is referred to as Organic Precision Fires-Light (OPF-L). OPF-L shall provide the squad with an organic, loitering, precision strike capability to engage the enemy beyond the line of sight. OPF-L system shall consist of the loitering munition, associated ground control station to operate and control the loitering munition, training simulator, and ancillary equipment required to support the system.

1.2 Scope

This Statement of Work (SOW) defines the effort required by the contractor to produce, deliver, test and support the OPF-L system in accordance with the OPF-L Performance Specification.

The Contractor shall provide all material, services, and necessary support documentation needed to complete the tasks identified within this SOW. Additionally, the Contractor shall provide the requisite program management, systems engineering, quality assurance and logistics support to ensure that delivery schedules, performance requirements, and overall supportability of the OPF- L is accomplished as set forth in the contract.

2 APPLICABLE DOCUMENTS

Applicable to all contract line-item numbers.

2.1 General

The following documents form a part of this SOW to the extent specified herein. All second tier and below references cited in mandatory compliance documents shall be considered as guidance only. In the event of conflict between the applicable documents and this SOW, the SOW shall take precedence.

Nothing in this document supersedes applicable laws and regulations unless a specific exemption has been obtained. Unless otherwise stated, the following documents may be obtained from the Defense Logistics Agency (DLA) Document Services, Building 4/D, 700 Robbins Avenue, Philadelphia, PA 19111-5094 or visit https://quicksearch.dla.mil/qsSearch.aspx.

2.2 Government Documents

DEPARTMENT OF DEFENSE STANDARDS – Mandatory MIL-STD-130N Ch 1 16 Nov 2012 Identification Marking of U.S. Military Property

MIL-STD-882E 11 May 2012 Department Of Defense Standard Practice: System Safety

MIL-STD-2073-1E(4)

MIL-STD-709D

MIL-STD-129R

22 Apr 2019 Standard Practice for Military Packaging Ammunition Color Coding Military Marking for Shipment and Storage

MIL-STD-1168C

NAVSEAINST 8020.6E

Ammunition Lot Numbering and Ammunition Data Card Department of the Navy Weapon System Explosives Safety Review Board

MIL-PRF-29612B 31 Dec 2020 Training Data Products

DEPARTMENT OF DEFENSE MILITARY HANDBOOKS – Guidance

MIL-HDBK-29612B 31 Dec 2020 Instructional Systems Design/Systems Approach to

Training and Education (Part 2 of 5 Parts) MIL-HDBK-338B 1 Oct 1998 Electronic Reliability Design Handbook MIL-HDBK-470A 4 Aug 1997 Designing and Developing Maintainable Products and

Systems MIL-HDBK-502A 8 Mar 2013 Product Support Analysis MIL-HDBK-61B 7Apr 2020 Configuration Management Guidance MIL-HDBK-2155 11 Dec 1995 Failure Reporting, Analysis and Corrective Action Taken

The following other Government documents, drawings, and publications form a part of this document to the extent specified herein. Unless otherwise specified, the issuances of these documents are those cited below.

Reference No.* Date Title DoDI 8510.01 Ch. 3 29 Dec 2020 Risk Management Framework

(RMF) for DoD Information Technology (IT)

DoDI 8551.01 Ch. 1 27 July 2017 Ports, Protocols, and Services Management (PPSM)

NIST 800-37 Rev. 2 Dec 2018 Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy

NIST 800-53 Rev. 5 Sept 2020 Security and Privacy Controls for Information Systems and Organizations

GUIDANCE ONLY

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

3 REQUIREMENT

The contractor shall deliver inert rounds and All-Up Rounds (AUR) (AUR includes fully functioning warheads), Ground Control Station (GCS) (GCS include antenna, radio, controller, and other items that are required to fly and control the AUR), training simulators, and ancillary equipment that meets the specification criteria of the OPF-L performance specification. The Government will initially procure systems to conduct testing as outlined in Attachment J.2, Section 4. The contractor shall deliver final inspection records with the delivery of all systems associated with each Lot delivered under the production delivery CLINs.

3.1 Production.

Delivery Order 1: The Contractor shall deliver 22 LMs (live warhead), 0 Inert Rounds, 12 GCS, 4 Ancillary Equipment sets, and 10 additional LM batteries within 120 calendar days from receipt of Delivery Order 1. After this initial delivery, the remainder of Delivery Order 1 shall be delivered at a monthly rate of 15 LMs (Live and/or Inert). Attachment J.3, Table 2 and Attachment J.3, Figure 4 provide additional information required quantity and configurations by test event.

Follow-on delivery orders shall have progressively increasing delivery rates until a minimum monthly delivery rate of 75 LMs (Live and/or Inert), 27 GCS, and 27 Ancillary Equipment sets is achieved by FY26. Attachment J.3, Table 2 and Attachment J.3, Figure 4 provide additional information required quantity and configurations by test event.

3.2 Program Management and Data Management.

The Contractor shall establish a program management structure that ensures the provides visibility into the contractor’s organization and techniques used in managing the program to achieve overall quality of the OPF-L and compliance with delivery schedules. The Contractor shall ensure that it adequately addresses all task requirements pertinent to contract performance.

Upon Government request, the Contractor shall readily provide programmatic documentation to Government representatives. The Contractor shall submit Progress, Status and Management Reports (Monthly Status Report) (MSR) to the Government in accordance with (IAW) Contract Data Requirement List (CDRL) A001.

CDRL A001: Status Report – Monthly Status Report (MSR)

The Contractor shall maintain an accurate schedule of program events and recommended program schedules, including review and evaluation techniques, which provide for the earliest delivery schedule while at the same time satisfying all requirements. The program schedule shall include all significant events, and a Program Planning Milestone Chart shall depict major tasks and events from start to completion of the contract. At minimum, the Contractor shall track and report all shipments to the Government in the MSR. The Contractor shall notify the Government in writing of any anticipated or projected work stoppages or delays that will impact schedules.

The Contractor is responsible for performance of requirements delineated in this SOW and shall implement appropriate management actions relative to subcontractor performance. Requirements that are contractually specified shall apply to subcontractor performance. Contractor shall be accountable for subcontractor compliance and is responsible for ensuring all deliverable products comply with the contract requirements.

The Contractor's quality management system shall ensure product conformation to contractual requirements. The Contractor shall implement and document the ability to maintain the quality management system to be used on the contract. The Contractor shall make available all quality management documentation for the Government to review upon request.

The Contractor shall centrally manage all data to include, but not be limited to all necessary technical data (e.g., requirements, specifications, conceptual design drawings, developmental design drawings, test results, product drawings, engineering notebooks, parts lists, etc.), management plans and updates, updates of minutes of meetings and reviews, and historical versions of all aforementioned data. Tracking of Action Items resulting from meetings, program reviews, IPRs and IPT meetings shall be accomplished, recorded, and archived by the vendor. The Contractor, in developing information that shall be delivered to the Government, shall make the maximum use of existing data and technical information.

The contractor shall designate a Program Manager (PM) who shall possess sufficient corporate authority to manage, direct, execute and control all elements of the contract. The contractor shall notify the Government within five business days of any changes regarding authority, responsibility, or key personnel changes made by the contractor during the period of performance. Meetings, Formal Reviews, Conferences and Audits.

The Contractor shall plan, host, coordinate, support and conduct meetings, formal reviews, conferences, and audits. The reviews shall be conducted at Government and Contractor facilities. All such reviews shall be included in the IMS project schedule and may be held concurrently with the Government’s approval. The Contractor shall prepare and deliver agendas and conference presentation materials; and deliver meeting minutes following each review. The Government reserves the right to cancel any review. The Government will provide notice of cancelation no less than two business days before the scheduled start of any meeting, review, audit, and conference. The Contractor and the Government shall determine Action Item documentation, assignment of responsibility for completion and due dates prior to adjournment of all reviews. The Contractor shall include and deliver within reviews: meeting minutes, a summary of all action items, responsible parties and estimated completion dates.

The Contractor shall host a PAC at the Contractor’s location no later than 10 calendar days after contract award. The Contractor and Government will review the contract and all contract requirements, clarify any questions, and the contractor will demonstrate to the government they have a complete understanding of the technical requirements and management responsibilities during the PAC. The Contractor shall present management, key personnel, and program implementation processes during the PAC. The Contractor shall prepare and deliver presentation material for the PAC to include an overview of all agenda items.

CDRL A002: Meeting Agenda

CDRL A003: Briefing Material

CDRL A004: Meeting Minutes

In-Process reviews shall be held on a semi-annual basis or as needed basis, on a mutually agreed upon date at the contractor’s facility. The contractor shall recommend agenda items and the government will approve the agenda. The Contractor shall deliver presentation materials providing an overview of all agenda items. Contractor shall ensure that appropriate personnel are available for reviews to address and resolve agenda items.

CDRL A002: Meeting Agenda

The Contractor shall conduct an SRR immediately following the PAC at the Contractor’s production facility. SRR will ensure that system requirements have been completely and properly identified and that a mutual understanding between the government and contractor exists. It ensures that the OPF-L performance specification is traced to the contractor’s Product Description contained in their proposal and that all system and performance requirements are defined and testable. The Contractor shall support closure of the request for action generated during the SRR.

The Contractor shall participate in Government-led CDR at the Contractor’s facility no later than 60 calendar days after SRR. The CDR shall demonstrate that system hardware and software detailed designs are complete and have been validated to meet the requirements IAW the OPF-L P-SPEC and the contractor’s Product Description. The Contractor shall support closure of the request for action generated during the CDR.

The CDR information provided by the Contractor shall contain detailed design information on each configuration item providing a mechanical and electrical break down of the systems, to include key system interfaces. The Contractor shall include information on software, system response protocols, and user interface controls. The Contractor shall provide details on their warhead design, its performance and any safety testing already completed on the warhead. The Contractor shall describe any system interfaces that integrate with external systems. The contactor shall provide a trace from the Government PSpec to the major system Configuration

Item (CI) and their capabilities. The overall technical program risks shall also be reviewed.

CDRL B001: Critical Design Review Package -10 business days prior to CDR

CDRL B002: Interface Control Document (ICD)

The Contractor shall support the government led TRR with technical support and data per CDRL A005. The TRR shall consist of two meetings, not more than one business day each, to review upcoming Government led testing. The Government will track any request for action or request for information generated as part of the TRR, however, the Contractor may be required to provide information or supporting evidence to allow for the request to be closed. The Government requires TRRs for testing identified in Attachment J.3.

CDRL A005: Briefing Material (Test Readiness Review)

The Contractor shall host a PRR on a mutually agreed date to be determined at the PAC. The PRR shall address each hardware and software configuration items with related logistics support. The Contractor shall show and/or demonstrate that evaluations of materials, lead times, tooling, fabrication techniques, assembly methods, test equipment, skills, processes and inspection techniques have been accomplished for the system.

The Government shall tour the Contractor’s facility to confirm production capability. The Contractor shall show and/or demonstrate all the OPF-L hardware and software configuration item and related support equipment. The Contractor shall show and/or demonstrate that producibility objectives have been achieved, and shall identify all single source, sole source and diminishing source(s). This review will evaluate the progress, technical adequacy and risks of the system and will assess the technical risk associated with the selected assembly processes. This review shall verify that the production plan presented by the Contractor demonstrates their ability to produce the OPF-L system based on their documented assembly procedures, production and quality control processes, ability to meet schedule thresholds, and other established criteria. The Contractor shall demonstrate that the manufacturing methods, processes, and production flow to include critical inspection points, quality control system, measurements and test equipment, and training are adequately planned, followed, and controlled. The Contractor shall support closure of the request for action generated during the PRR.

CDRL B003: Configuration Audit Plan (Physical)

CDRL B004: Configuration Audit Summary Report (Physical)

The Contractor shall host a PCA on a mutually agreed date to be determined at the PAC. The PCA shall assess if the documentation (drawings, engineering, logistics, etc.) is correct and the “as built” configuration of the design matches the documentation. The Contractor shall develop and deliver a PCA plan utilizing MIL-HDBK-61A, Section 8 as a guide. The Government shall verify that the Contractor design configuration matches the final documentation deliverables as evidenced in its production configuration and determine that the system meets the documented functional requirements as well as the Contractor’s documentation such as drawings, commercial item descriptions, vendor item descriptions, and source control documents.

The Contractor shall host the PGC immediately following the PAC. The Contractor shall ensure all key logistics personnel are in attendance during the PGC. The Contractor shall be prepared to discuss all provisioning deliverables in detail and deliver associated documentation. The Contractor shall address joint development of a Provisioning Performance Schedule (PPS) using Form MC-ALB-4423/15 and scheduling of periodic submissions of Provisioning Technical Documentation (PTD) IAW the GEIA-HDBK-0007, GEIA-STD-0007 and the GEIA Attribute Selection Sheet and MIL-HDBK- 502A for Government review. The Government will provide list of provisioning deliverables prior to the PGC.

The Contractor shall host a PC at the Contractor's facility IAW the PPS, at which time the Contractor shall deliver copies of the Provisioning Parts List (PPL) and Engineering Data for Provisioning (EDFP). The Contractor shall be responsible for disassembly of the equipment during this conference to validate and verify all Provisioning Technical Documentation. The Contractor shall have all key logistics personnel in attendance during the PC. The Contractor and the Government will conduct a Hardware Breakdown (Top- Down Break Down) analysis of the item (s) to be provisioned during the PC. The Contractor shall acknowledge that the hardware breakdown shall be accomplished by sequencing all parts comprising the end item in a lateral and descending "family tree/generation breakdown." The Contractor shall further recognize that the breakdown shall consist of the end item, including all components, listing every assembly, subassembly, and parts that can be disassembled, reassembled/replaced. The Government and the Contractor will finalize the recommended spare components/parts list proposed by the Contractor as a result of the PC.

3.4 Security Requirements

The information provided to the contractor will be unclassified and/or Controlled Unclassified Information (CUI). The contractor is not required or expected to have a Facility Clearance and contractor personnel supporting this effort are not required to possess Personnel Clearance Levels. Any contractor personnel requiring access to U.S. Government CUI shall possess a completed background investigation (minimum of a T-1/NACI) for this Public Trust Position.

Due to Insider Threat concerns, the Company is requested to notify the MARCORSYSCOM Personnel Security (PERSEC) Office at 703-432-3952/3490/3374, within 24 hours of any adverse/derogatory information associated with the 13 Adjudicative Guidelines concerning any contractor performing on this contract.

In accordance with DoDI 5200.48, “Controlled Unclassified Information (CUI),” all contractors supporting MARCORSYSCOM who receive, store, or generate CUI are required to take the DoD Mandatory CUI Training, available on the Security Awareness Hub at:

https://securityawareness.usalearning.gov/cui/index.html. Per DoDI 5200.48 and pursuant to contractual requirements, DoD contractors require initial CUI training and annual CUI refresher training. Additional MARCORSYSCOM specific CUI training and guidance can be attained by contacting the MARCORSYSCOM Security Classification Management Office at 703-432-3141 / 3140 or MCSC_ACSG2_SCMO@usmc.mil.

While performing aboard NAVY/USMC sites, the contractor shall comply with the provisions of DoD Directive 5205.02E, “DoD Operations Security (OPSEC) Program,” SECNAVINST 3070.2A, “Operations Security,” MCSCO 3070.1B, “Operations Security Program,” Marine Corps Order 3070.2A, “The Marine Corps Operations Security (OPSEC) Program,” and the MARCORSYSCOMO P5510.2C, “Security Manual,” at all other sites the contractor shall comply with the local command and/or program OPSEC plan. Contractor personnel shall follow OPSEC concepts and principles in the conduct of this requirement to protect critical information, personnel, facilities, equipment, and operations from compromise. All Contractors (including Subcontractors) shall supplement their current security practices by requiring any personnel involved in executing this contract to complete Government-sponsored and administered OPSEC training.

At a minimum, for technical data/computer software delivered with government purpose or unlimited rights all deliverables will be marked “CUI” in the header and footer section of the document. Information determined to be CTI shall be marked in accordance with the DoDI 5200.48 guidance and shall include a distribution statement consistent with the DoDI 5230.24. If it has distribution statement B-F it is CUI and requires a CUI Designation indicator. CTI must be in all CUI Designation Indicators because Distribution Statements are for technical information.

The cover sheet and first page of deliverables containing CTI shall be marked with the CUI Designation Indicator and Distribution Statement. Must be legible. Font 6 acceptable.

Controlled by: USMC Controlled by: MCSC, PM FSS, PMM-142 CUI Category: CTI, EXPT Distribution Statement: D POC: Peggy Smith (703) 432-3590

On the first page or document cover the following Distribution Statement will be applied:

“DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only; Export Controlled, Critical technology, 14 July 2023. Other requests for this document must be referred to Commander, Marine Corps Systems Command (Attn: PM FSS, PMM-142), 2200 Lester Street, Quantico, VA 22134-5050.”

All deliverable documents containing Export Control information will also be marked with an Export Control Warning Label:

“WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Section 2751 of Title 22, United States Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 4801-4852 of Title 50, United States Code). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25 and DoD Instruction 2040.02.”

See Attachment J.15, CUI GUIDANCE FOR Contractors_May2023, for additional marking requirements and guidance.

The COR will identify and only approve those contractor employees performing on this contract that require a CAC in order to perform their job function. At this time, the only contractor employees expected to receive a CAC are those individuals responsible for performing tasks associated with Section 3.13.6.

In accordance with Headquarters, United States Marine Corps issued guidance relative to Homeland Security Presidential Directive – 12 (HSPD-12), all personnel must meet eligibility criteria to be issued a CAC. In order to meet the eligibility criteria, contractor employees requiring a CAC must obtain and maintain a favorably adjudicated Personnel Security Investigation (PSI). Prior to authorizing a CAC, the employee’s Defense Information System for Security (DISS) record must indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has been submitted and accepted (opened). The minimum acceptable investigation is a T-1 or a National Agency Check with Written Inquiries (NACI). If a contractor employee’s open investigation closes and is not favorably adjudicated, the CAC must be immediately retrieved and revoked. CACs are not issued for convenience.

Facility Security Officers (FSOs) are responsible for notifying the MCSC AC/S G-2 Personnel Security Office (PERSEC Office) at 703-432-3490/3952 if any contractor performing on this contract receives an unfavorable adjudication after being issued a CAC. Due to Insider Threat concerns, the Company is requested to notify the MCSC AC/S G-2 Personnel Security Office (PERSEC Office) at 703-432-3952/3490/3374, within 24 hours, of any adverse/derogatory information associated with the 13 Adjudicative Guidelines concerning any contractor performing on this contract, if they have been issued a CAC and/or a MCSC Building Badge.

Each CAC is issued with a “ctr@usmc.mil” e-mail account that the individual contractor is responsible to maintain as active by logging in on a regular basis (at least twice a month), sending an e-mail and clearing any unneeded e-mails. Contractors issued a CAC are prohibited from “auto- forwarding” e-mail from their .mil e-mail account to their .com e-mail account. If the “ctr@usmc.mil” e-mail account is not kept active, G-6 will deactivate the account and the CAC will also lose its functionality. Contractor employees shall solely use their government furnished “ctr@usmc.mil” e-mail accounts for work supporting the USMC, conducted in fulfillment of this contract, and shall not use a contractor supplied or personal e-mail account to conduct official U.S. government business. The use of a contractor or personal e-mail account for contractor business or personal use is allowed, but only when using cellular or a commercial internet service provider. If a contractor loses their eligibility for a CAC due to an adverse adjudicative decision, they have also lost their eligibility to perform on MCSC contracts.

3.5 Configuration Management

The Contractor shall have a documented and established CM process. Upon request, the Contractor shall provide requested CM documentation to the Government to validate compliance with standard processes and to confirm configuration of the system. The Contractor shall maintain a CM process for the control of all HW and SW configuration documentation, media and parts representing or comprising the OPF-L. The Contractor CM process shall be able to identify and document the OPF-L functional, performance and physical attributes. The Contractor CM process shall control changes to configuration items (CI) and associated documentation. The Contractor CM process shall record and report information needed to manage CI, including status of proposed changes and implementation of change. The Contractor CM process shall audit configuration items to verify conformance to specifications, drawings, and interface control documentation. The Contractor has the option to use MIL-HDBK-61A as guidance. The Contractor's CM process shall consist of configuration identification, configuration control, Configuration Status Accounting (CSA) and configuration audits. The Contractor shall notify the Government of any changes, which affect the Contractor's established CM process and make configuration data available for review upon request. All OPF-L systems and parts to include spares and repair parts delivered by the Contractor shall be configured to the current Government accepted configuration baseline.

The Contractor’s proposed system shall be the product baseline. Any change to this proposed baseline shall be documented by an Engineering Change Proposal (ECP). Technical compliance is based on evidence of the systems’ ability to meet the PSPEC performance standards. The Contractor shall document the requirements its system meets in the Product Description (PD). The Contractor PD shall include the software version description. If the Contractor’s system’s proposed configuration and level of performance exceeds PSPEC threshold requirements, then the Government will adopt and incorporate the improved configuration and performance as the PD baseline.

The Contractor shall provide a PD containing all the information necessary to define the performance and configuration of the OPF-L. The PD shall include a summary of verification procedures and relevant definitions applicable to each performance attribute. If the Contractor changes the configuration, it shall update the PD in accordance with configuration management and ECP processes IAW paragraph 3.5.5.

CDRL B005: Product Description

The Contractor shall establish and maintain a CSA database that represents the current configuration of the OPF-L system. The Contractor shall implement the CSA database as a tool to provide for the recording, maintaining, and reporting of configuration data to the Government to ensure effective management of the system.

The Contractor shall document all baselines and changes in the Contractor’s CSA database. The Contractor's CSA database shall permit acceptance of commercial product information; however, if requirements to report data outside of the Contractor's CSA database or format exist, the information may be delivered as a supplement to prevent disruption to their existing system. The Contractor's CSA database shall reconcile any differences between the supplier information and Contractor practices to provide the Government with clear accountability of product information.

Additionally, the CSA database shall provide a reliable source of configuration information to support OPF-L activities, including program management, systems engineering, logistics support and modification/maintenance actions. The Contractor shall utilize the CSA database to record completed field modifications or retrofit actions as a result of approved ECPs. The Contractor shall maintain the information that allows visibility of completed actions to the OPF-L serial numbers. The Government shall have access to the contractor’s CSA database throughout the period of performance.

The Contractor shall maintain control and accountability of the product baseline throughout the life of this contract. The Contractor shall notify the Government at the onset of their planning, which shall be at a minimum of 90 calendar days in advance, of all changes to established baselines that affect form, fit, function, cost or product delivery schedule throughout performance of this contract. The notification shall include a change impact analysis that assesses alternate solutions to determine what action is in the best interest of the Government. Additionally, notification information shall include enclosures and figures that identify and define the effect on Technical Publications which includes draft Technical Manual (TM) page changes, packaging data, testing supportability, interoperability/interchangeability, lifecycle costs, maintainability, reliability, environmental (to include identification of all ozone depleting substances) safety and health (ESH) and retrofit information. Sufficient supporting data to evaluate the proposed or requested change, such as engineering drawings, sketches, specifications, or manufacturing data sheets, shall also be submitted as supplemental information. All changes to the baseline shall be approved by the Government using the ECP accompanied, where appropriate, with a Notice of Revision (NOR) or the Request for Variance (RFV) Process.

The Contractor shall deliver Class I and Class II ECPs using DD Form 1692 completed with all required information. The Contractor shall deliver sufficient technical data to include engineering drawings, sketches, specifications, manufacturing data sheets, logistic impacts, and testing results at time of submission for the Government to evaluate the proposed or requested change. The Government may request any additional information from the vendor to support ECP evaluation and approval. The Government as the Configuration Control Authority (CCA) for all ECPs must approve all Class I ECPs and concur with the classification of all Class II ECPs prior to implementation into the OPF-L system. The Contractor shall maintain configuration control of the OPF-L product baseline throughout the contract period. The Contractor shall notify the Government of any changes impacting form, fit, function, interface, interchangeability, interoperability and parts management of the OPF-L. The Government will use the Activity Guide Tables in MIL-HDBK-61B as guidance for review of Contractor submitted change proposals and Notices of Revisions (NoRs).

CDRL B006: Engineering Change Proposal (ECP)

The Contractor shall deliver a RFV to request authorization to depart from current approved configuration documentation. Authorized variances are a temporary departure from the requirements and do not constitute a change in an approved baseline. Where it is determined that a change should be permanent, the Contractor shall process an ECP per paragraph 3.5.5. MIL-HDBK-61B, paragraph 6.2.1.1, provides guidance concerning the classification of RFVs, formerly known as Requests For Deviation.

CDRL B007: Request for Variance (RFV)

The Contractor shall generate and deliver Notices of Revision (NORs) concurrently with ECPs when technical documentation controlled by another Contractor or Government agency requires changes following approval of an ECP.

CDRL B008: Notice of Revision (NOR)

The Contractor shall deliver a notification to the Government when changes occur to commercial equipment or software that is being procured by the Contractor and affect form, fit or function. This early notification should precede any changes via ECP.

CDRL B020: Technical Report - Study/Service, (Change Notifications to Commercial Equipment/Software)

3.6 Environmental, Safety, and Occupational Health (ESOH)

The Contractor shall identify and evaluate environmental, safety and occupational health hazards; define risk levels; and establish a program that manages the probability and severity of all hazards associated with development, manufacture, use and disposal of the system IAW MIL-STD-882E. Residual risks will be evaluated by the Government IAW MIL-STD-882E and accepted as appropriate prior to exposing people, equipment or the environment to known system related ESOH risks. The Contractor shall identify all explosive safety risks as such in the system safety documentation. The Contractor shall participate as a member, and provide needed information, to the OPF-L ESOH Working Group (ESOHWG), IAW Task 105 of MIL-STD-882E, as directed by the Government. The information that the Contractor shall provide to the ESOHWG shall include at a minimum:

schedule of planned safety activities, summaries of completed safety activities to include description of relevant results and findings, status of open hazards and plans for resolution of open hazards. The Contractor shall effectively identify hazards early and take actions necessary to eliminate, control, or reduce their associated risks to the lowest level possible. The Contractor shall describe in detail the scope of the System Safety Program, required system safety tasks and associated responsibilities and milestones at ESOHWG meetings

The Contractor shall document the System Safety Program (SSP) in a System Safety Program Plan (SSPP) that describes in detail the scope of the SSP, required system safety tasks and associated responsibilities and milestones per MIL-STD-882E, Task 102, System Safety Program Plan. The SSPP shall include an appendix with a Software System Safety Program Plan (SwSSPP) addressing integration of software safety and Level of Rigor (LOR) specifically outlining what LoR activities were planned and completed for each Software Criticality Index (SwCI) level. The SwSSPP shall address all software used in the system to include Non- Developmental Item (NDI), Commercial Off-The-Shelf (COTS), reuse software, firmware and Field Programmable Gate Array (FPGAs). The Contractor shall assess compliance of the developed system hardware and associated software with the identified requirements and document in the SSPP.

CDRL B010: System Safety Program Plan (SSPP) to include SwSSPP

The Contractor shall support the Government-approved hazard tracking process. The Contractor shall document hazards in a hazard tracking system per the requirements of MIL-STD-882E, Task 101, Hazard Identification and Mitigation Effort Using The System Safety Methodology. The Contractor shall provide reports from the Contractor’s hazard tracking system at ESOHWG meetings as determined by the Government. Upon identification of any potential Serious or High risk hazards, the Contractor shall notify the Government immediately.

CDRL B011: Hazard Tracking Logs

The Contractor shall provide a Safety Assessment Report (SAR) per Task 301 in MIL-STD-882E that documents the Safety Assessment and clearly identifies risks. The Contractor shall perform and document an assessment to identify the status, at the time of the report, of safety hazards, associated risks, and mitigation measures. This documentation shall include hazards that were identified and eliminated, and specific procedural controls and precautions to be followed to mitigate the risks of hazards that could not be eliminated. The SAR shall include a signed statement that all identified hazards have been eliminated or their associated risks have been assessed, and that the risk assessment has been provided to the Government for Government risk acceptance. The SAR shall include a signed statement from the Contractor on whether the system is ready to test, field, and operate from a safety perspective. In addition, the Contractor shall make recommendations applicable to hazards at the interface of this system with other systems and any hazards associated with the AUR forward of firing line. The SAR shall also include a System Safety Risk Assessment demonstrating the process utilized to identify, analyze, and control hazards and risks. Of note the SAR shall include information in accordance with analyses as required by MIL-STD-882E, Task 204 Subsystem Hazard Analysis, Task 205 System Hazard Analysis, Task 206 Operating and Support Hazard Analysis, Task 207 Health Hazard Analysis. The Contractor shall include in the SAR, a Software Safety Analysis as defined in paragraphs 3.6.5. The Contractor shall include in the SAR all hazardous materials used in the system or the making of the system. This should include the name and description of the hazardous material, quantities used and where in the system the hazardous materials are used.

Additionally, the SAR shall include results from LOR Analysis of safety significant functions.

The SAR shall include Objective Quality Evidence (OQE) that demonstrates analysis of requirements, architecture, design and software code. In-depth safety specific testing applicable to the safety significant functions and their identified SwCI levels shall be included. The OQE shall include screen shots, analytics, white papers, simulation results, test results and other quantifiable evidence to demonstrate rigor. The LOR Task Table in Appendix A of the Joint Software Systems Safety Engineering Handbook (JSSSEH) shall be used to develop the process tasks necessary to meet MIL-STD-882E Table V LOR requirements. The Contractor shall provide Verification and Validation of safety critical functions. The Contractor shall update the SAR to support test, demonstration and evaluation events, and fielding, as determined by the Government.

CDRL B012: Safety Assessment Report (SAR)

The Contractor shall comply with the provisions of MIL-STD-882E, Section 4.4, and Appendix B for software system safety engineering and analysis requirements. For more detailed guidance, refer to the Joint Software Systems Safety Engineering Handbook and Allied Ordnance Publication 52 (AOP-52), Guidance on Software Safety Design and Assessment of Munition-Related Computing Systems. The use of these documents shall be for the purpose of identifying and assessing software safety risk associated with Contractor provided software. The Contractor shall provide all open software deficiencies such as Software Trouble Reports, and those deficiencies shall be assessed for safety risk level IAW Table B-1 of MIL-STD-882E.

The Contractor shall perform and document a FHA IAW MIL-STD-882E Task 208 using guidance provided in the NAVSEA SW020-AH-SAF-010 Weapon System Safety Guidelines Handbook Section 3 Chapter 11 to identify the Safety Significant Functions associated with the proposed design . As part of the FHA, the Contractor shall determine the software criticality index for each safety significant software function. The Contractor shall identify the required analyses and tests to meet the required level of rigor for each safety significant software function. The FHA should be based on the best available data, including mishap data (if obtainable) from similar systems and other lessons learned. This effort will include inputs, outputs, critical interfaces, and the consequence of functional failure.

CDRL B009: Technical Report - Study/Services (Functional Hazard Analysis (FHA))

The Contractor shall deliver to the Government the updated Safety Data Sheets as required by OSHA Hazard Communication Standard code of Federal Regulations 29 CFR 1910.1200 in accordance with FED-STD-313E.

The Contractor shall support reviews, certifications, boards, and/or audits performed by or for the Government IAW Task 104 of MIL-STD-882E. The Contractor shall support the Government with data as needed in required reviews for the OPF-L system, to include Department of the Navy Weapon System Explosives Safety Review Board (WSESRB) and sub-panels; Software System Safety Technical Review Panel (SSSTRP); Fuze and Initiation System Technical Review Panel (FISTRP). This also includes, but is not limited to, support of the Laser Safety and lithium battery certification. The Contractor’s laser safety certification involves delivery of OPF-L data and equipment consisting of test assets, safety test data, measurements, laser hazard results, corrective actions, and/or other system safety data IAW MCO 5104.1C (or latest version). All data shall be delivered IAW the CDRLs and coordinated with Government Safety personnel. The Contractor support shall include providing agreed upon data prior to the start of the Operational Assessment. The Contractor shall verify that proper system labeling is in place as required for the laser classification. The Contractor’s lithium battery certification support involves delivery of lithium battery data that documents the stability of design and validity of the battery selection, IAW NAVSEAINST 9310.1C and NAVSEA S9310-AQ-SAF-010 (3rd revision).

CDRL B013: Laser Safety Review Board (LSRB) Data

CDRL B014: Lithium Battery Safety Data (LBSD)

The Contractor shall ensure that ammunition and explosives are developed, so hazards can be properly classified, manufactured, tested, transported, handled, stored, used, maintained, demilitarized, labeled and disposed of safely within the Marine Corps munitions lifecycle environment. The Contractor shall provide all information pertaining to the systems energetics and the topics listed above. The Contractor shall provide all information required to demonstrate how the fuze meets the requirements of MIL-STD-1316F, and how the initiation system meets the requirements of MIL-STD-1901A. The Contractor shall support the Naval qualification processes to include the Naval WSESRB IAW NAVSEAINST 8020.6E, Insensitive Munitions IAW MIL-STD-2105D, Hazard Classification IAW NAVSEAINST 8020.8C, and Qualification and Final (Type) Qualification for Navy Explosives IAW

NAVSEAINST 8020.5D.

3.7 Cybersecurity.

The Contractor shall support cybersecurity Assessment and Authorization (A&A) by delivering all necessary technical documentation and participating in meetings, as necessary, to ensure compliance with all applicable security controls determined by the program office (Reference DoDI 8500.01, DoDI 8510.01, NIST 800-37 Revision 2, and NIST 800-53A Revision 45). The contractor shall assist the government in providing the Risk Management Framework (RMF) artifacts to include a vulnerability assessment. The Contractor shall deliver to the program office an OPF-L Cybersecurity System Architecture Design that includes all hardware, software applications, firmware, network configurations, and data flow. The Contractor shall deliver copies of all software license agreements and certify source code developed via digital signature.

The Contractor shall not utilize third party (i.e., freeware or Open Source Software) applications unless there are no alternative solutions. The Contractor shall identify all third-party software applications.

If COTS or Open Source software is proposed for delivery, the Contractor shall provide copies (and not merely links to websites) of each applicable License or End User License Agreement for review by the government. For each Open Source Software License, the Contractor must first review that license and highlight to the Government every instance where that license requires any “copyleft”/”viral” condition requiring the end software product to be dedicated to the open source community, or must provide a written certification that such review was conducted and that no “copyleft”/”viral” condition was found.

CDRL B015: Software License Requirements List – Software License Agreement(s)

CDRL B016: Cybersecurity System Architecture Design

3.8 Radio Frequency Spectrum Compatibility

The Contractor shall submit the data required to complete DD Form 1494 for obtaining an approved frequency for the OPF-L, if applicable.

CDRL B017: Spectrum Certification Spectral Characteristics Data

3.9 Testing.

The OPF-L program shall consist of Government led performance testing, Contractor acceptance testing and operational testing.

The Government will test the OPF-L system to ensure the OPF-L is able to meet the performance specification requirements. Multiple iterations of testing, as described in Attachment J.3 will be completed by the Government. Delivery Order 1 and Delivery Order 2 will support Government testing. The objective is to characterize system performance against the performance specification and determine safety along with suitability.

The contractor shall provide the support listed in Sections 3.9.2 – 3.9.7 for Government led performance testing.

The Contractor shall provide off site support during the conduct of Government Testing via phone or email. Throughout Government Testing, the Government Test Agencies will maintain an inventory of parts and Support and Test Equipment (S&TE) required to support testing. The Government will maintain a record of parts that have been used throughout testing, to include Operational Testing (OT), which will be verified against the Test Incident Reports (TIR). TIRs will be provided to the Contractor at regular intervals during testing.

The Contractor shall provide Operator/Operator Maintenance training to the Government test teams (which will include both Marines and Government Operators) to align with paragraph 3.17. The Contractor shall provide Operator and Ammo Handling training, to include all OPF-L systems and all modes of operation.

Estimated size of the operator training audience is no greater than 8 operators and 12 observers.

The Contractor will provide all equipment and materials required to conduct training. The Government will provide a classroom to support instruction as well as ranges to support any training flights required to support operator training. The courses shall include tasks associated with proficient and safe operation of the system during test and evaluation.