DRAFT_Solicitation_N68335-19-R-0063.docx

N6833519R0063

Section A - Solicitation/Contract Form

SUMMARY INFORMATION

Points of Contact

Contracts POC:

Stephen Winkler

(732) 323-2971 stephen.winkler@navy.mil

Technical POC: TBD

In order to receive copies of the technical data package, interested offerors must be United States Government Contractors and/or DoD Contractors. Contractors must be registered in the System for Award Management (SAM), which can be accessed at www.sam.gov. Contractors must request the copies in writing from Mr. Stephen Winkler via e-mail: stephen.winkler@navy.mil.

The Government intends to award an Indefinite Delivery Indefinite Quantity (IDIQ) type contract with a total ordering period of three (3) years. It is the Government’s intention to award Delivery Order 0001 concurrently with the basic contract, which will satisfy the minimum requirement of the contract. The Government is not obligated to order any quantity beyond the guaranteed minimum order and may order up to the maximum quantity over the life of the contract.

Refer to NAVAIR clause 5252.216-9506 Minimum and Maximum Quantities (March 1999), listed in section F, for the minimum and maximum contract quantities.

Section B - Supplies or Services and Prices

EDM Non-Recurring Engineering

CPIF

The Contractor shall perform all non-recurring activities required to execute CLINs 0001 through 0004 of this contract. Non-recurring activities include all management, engineering, logistics, and other functions required to design, develop, integrate, and test Fourth-Generation Electro-Optic (EO4) subsystems that are compliant with the requirements of this SOW, See Section C, and the EO4 Subsystem Performance Specification (Attachment 1).

FOB: Destination

PSC CD: AC65

TARGET COST

TARGET FEE

TOTAL TGT COST + FEE

MINIMUM FEE

MAXIMUM FEE

SHARE RATIO ABOVE TARGET

SHARE RATIO BELOW TARGET

EO Subsystems

CPIF

The Contractor shall assemble and deliver Engineering Development Model (EDM) EO4 consoles, eCASS Interface Cables, host eCASS Augmentation Assets (if required), EO Carts (or equivalent UUT holding fixture), and Installation Kits (Mounting Rails, Shock Isolators, etc) in accordance with the statement of work, See Section C.

TARGET COST

TARGET FEE

TOTAL TGT COST + FEE

MINIMUM FEE

MAXIMUM FEE

SHARE RATIO ABOVE TARGET

SHARE RATIO BELOW TARGET

SMAT/CAL OTPS Upgrade Kits

CPFF

The Contractor shall deliver eCASS Self-Maintenance and Testing/Calibration Operation Test Program Set (SMAT/CAL OTPS) upgrade kits to achieve EO4 subsystem compatibility with the existing eCASS SMAT/CAL OTPS in accordance with this SOW, See Section C.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

Spares

The Contractor shall deliver spare replaceable assemblies for the EO4 subsystem in accordance with this SOW, See Section C.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

Earned Value Management

FFP

The Contractor shall perform earned value management functions as delineated within SOW paragraph 3.1.6 and its associated subparagraphs.

MAX

NET AMT

Engineering and Logistics Support Labor

The Contractor shall perform tasking as prescribed on separately placed delivery orders in accordance with this SOW paragraph 3.5, See Section C.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

Engineering and Logistics Supp Material

The Contractor shall provide material as prescribed on separately placed delivery orders in accordance with this SOW paragraph 3.5, See Section C.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

Engineering and Logistics Support Travel

COST

The Contractor shall perform travel as prescribed on separately placed delivery orders in accordance with this SOW paragraph 3.5, See Section C.

MAX COST

UNDEFINED

Data

FFP

The Contractor shall produce and deliver all data as prescribed herein in accordance with this SOW, See Section C and exhibits listed in Section J. Not Separately Priced

MAX

NET AMT

Section C - Descriptions and Specifications

STATEMENT OF WORK

Statement of Work (SOW) for the

Fourth Generation Electro-Optic (EO4) Subsystem

26 March 2019

DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense and U.S. DoD contractors only for Administrative or Operational purpose effective 26 Oct 2018. Other requests for this document shall be referred to Commanding Officer, PMA260, Suite 349. 47123 Buse Road, RADM William A. Moffett Building, Patuxent River, MD 20670-1547.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of document.

This document contains information that may be exempt from mandatory disclosure under the Freedom of Information Act.

Contents

Revisions

Scope (All CLINs) The Contractor shall design, develop, fabricate, assemble, integrate, test, and deliver Fourth-Generation Electro-Optic (EO4) subsystems that are compliant with the EO4 Subsystem Performance Specification (Attachment 1) requirements and that are compatible with the electronic Consolidated Automated Support System (eCASS) EO Configuration (P/N: 4027AS0979-01) and the Operational Test Program Sets (OTPSs) delineated herein. The Contractor shall, as required, conduct Earned Value Management (EVM) reporting and provide engineering and logistics support. EO4 subsystems shall include all items necessary to replace the functionality of the legacy EO3 subsystem (P/N: 2054AS800-2001).

Non Recurring Activities (CLIN 0001) The Contractor shall perform all non-recurring activities required to execute CLINs 0001 through 0006 of this contract. Non-recurring activities include all management, engineering, logistics, and other functions required to design, develop, integrate, and test Fourth-Generation Electro-Optic (EO4) subsystems that are compliant with the requirements of this SOW and the EO4 Subsystem Performance Specification (Attachment 1).

EO4 Consoles (CLIN 0002) The Contractor shall assemble and deliver Engineering Development Model (EDM) EO4 consoles, including external interface cables (power, communications, etc.) and any augmentation assets required to enable the eCASS system to host the EO4 console.

EO4 Carts (CLIN 0002) The Contractor shall assemble and deliver electro-optic (EO) carts, or a functionally equivalent item, that provides the means to hold Units-Under-Test (UUT) during the conduct of testing on an eCASS EO4 configuration system. The EO cart solution shall provide all functionality of the existing legacy EO carts (P/N: 63E919617G1).

EO4 Installation Kits (CLIN 0002) The Contractor shall deliver installation kits for the EO4 subsystems for use at shipboard and shore-based facilities that comply with the EO4 Subsystem Performance Specification (Attachment 1).

eCASS SMAT/CAL OTPS Upgrade Kits (CLIN 0003) The Contractor shall deliver eCASS Self-Maintenance and Testing/Calibration Operation Test Program Set (SMAT/CAL OTPS) upgrade kits if necessary to achieve EO4 subsystem compatibility with the existing eCASS SMAT/CAL OTPS.

EO4 Spares (CLIN 0004) The Contractor shall deliver spare replaceable assemblies for the EO4 subsystem.

Earned Value Management (CLIN 0005) The Contractor shall perform earned value management functions as delineated within SOW paragraph 3.1.6 and its associated subparagraphs.

Engineering and Logistics Support Labor (CLIN 0006) The Contractor shall perform tasking as prescribed on separately placed delivery orders.

Engineering and Logistics Support Material (CLIN 0007) The Contractor shall purchase material as prescribed on separately placed delivery orders.

Engineering and Logistics Support Travel (CLIN 0008) The Contractor shall perform travel as prescribed on separately placed delivery orders.

Data (CLIN 0009) The Contractor shall produce and deliver all data as prescribed herein.

Applicable Documents The documents listed below form a part of this SOW to the extent invoked herein. In the event of a conflict between the documents referenced herein and the contents of this SOW, the contents of this SOW shall take precedence, followed by SOW Attachments 1 through 6.

SOW Attachments

Government Documents Specifications

MIL-PRF-29612B

(Notice 3)

MIL-PRF-81705E

(Notice 1)

Military Standards

MIL-STD-129R

MIL-STD-130N

(Change 1)

Military Handbooks

MIL-HDBK-217F

(Notice 2)

Other

http://www.jointadlcolab.org/downloads/learner_assessment_bpguide_final.pdf

SECNAVINST 4140.2

http://www.jointadlcolab.org/downloads/learner_assessment_bpguide_final.pdf Non-Government Documents Commercial Standards

Security Documentation The following is a listing of Information Assurance references that apply to the EO4 Program:

DoD 8570.1-M (Change 4)

Workforce Improvement Program

DoDI 5220.22 (Change 1)

DoDI 5230.24 (Change 3)

DoDI 8510.01 (Change 2)

Requirements Program Management Program Management and Control (CLIN 0001) The Contractor shall:

a. Manage and control all program activities to ensure compliance with contract requirements and achievement of optimal technical, cost, and schedule performance.

b. Manage the program in accordance with an integrated master schedule (IMS), which contains all tasks required to successfully comply with all contract requirements.

c. Provide all necessary resources to accomplish the tasks of this SOW and the IMS.

d. Prepare and deliver a Contractor Progress, Status and Management Report (CPSMR) per CDRL A001.

(CDRL A001 - Contractor Progress, Status and Management Report) Subcontract Management (CLIN 0001) The Contractor shall:

a. Manage and be solely responsible for all sub-Contractor cost, schedule, technical performance, and quality workmanship.

b. Ensure that all contract requirements are flowed down to and effectively implemented by its sub-Contractors. Special attention shall be applied to the accomplishment of the sub-Contractor’s critical path tasks within the Contractor’s Integrated Master Schedule (IMS).

Contractor Work Breakdown Structure (CWBS) (CLIN 0001) The Contractor shall maintain the CWBS and the CWBS dictionary in accordance with MIL-STD-881. The CWBS shall be the foundation for control accounts and work packages during performance of the contract. The CWBS and associated CWBS dictionary shall be available for Government review via the Contractor’s Integrated Data Environment (IDE).

Contract Funds Status Report (CFSR) (CLIN 0001) The contractor shall prepare and deliver the CFSR per CDRL A002.

(CDRL A002, Contract Funds Status Report) Contractor Integrated Performance Management (IPM) (CLIN 0001) The Contractor shall prepare and deliver the IPM Report per CDRL A003, which shall include the Contractor’s IMS.

(CDRL A003, Integrated Program Management Report (IPMR)) Earned Value Management (CLIN 0005 ONLY) The Contractor shall:

a. Perform tasks within this section and associated subsections only if CLIN 0005 is awarded.

b. Establish, maintain, and use an integrated management system that is in compliance with the industry guidelines for Earned Value Management Systems (EVMS) EIA748-C as determined by the Defense Contract Management Agency (DCMA).

c. Prepare and deliver the Integrated Program Management Report (IPMR) per CDRL A004.

(CDRL A004, Integrated Program Management Report (Format 7)) Integrated Baseline Review (IBR) (CLIN 0005 ONLY) The Contractor shall establish and maintain a reliable performance measurement baseline. The Contractor shall host an IBR no later than 180 calendar days after contract award, during which the Government will assess the contractor’s baseline, including all subcontracted efforts, to ensure complete coverage of the statement of work, logical scheduling of work activities, adequate resourcing, and identification of inherent risks. Detailed planning, to the greater of, “six months beyond the IBR date” or “the next major milestone following the IBR” is required. IBR documentation shall be made available to the Government at least four weeks prior to the review. The Government will verify during the IBR that the contractor has established and maintains a reliable performance measurement baseline. The contractor will ensure that the baseline includes the entire contract scope of work consistent with contract schedule requirements, employment of adequate management, and assignment of adequate resources. The contractor will assure the Government that effective earned value methods are used to accurately status contract cost, schedule, and technical performance.

OTB/OTS/Restructure (CLIN 0005 ONLY) In the event Over Target Baseline (OTB), Over Target Schedule (OTS), or a Restructuring action is determined to be necessary, the contractor shall request and obtain written approval from the Government Procurement Contracting Officer prior to implementing an OTB/OTS/Restructuring action. The request shall include detailed implementation procedures and an implementation timeframe. The contractor shall refer to the IPMR Data Item Description (DID) for EVM reporting requirements prior to and after OTB/OTS execution.

Problem Identification Reports (PIR) (CLIN 0001) The Contractor shall prepare and deliver a PIR per CDRL A005 for each programmatic, technical or logistics issue, including obsolescence issues, that negatively impact the performance of this contract.

(CDRL A005 – Problem Identification Report (PIR)) Risk and Opportunity Management (CLIN 0001) The Contractor shall conduct risk and opportunity management using the PMA260 Risk Management Plan (RMP) as guidance. The Contractor shall continually assess program risks and opportunities and present findings during quarterly Contractor/Government risk review boards. All risk review board data will be maintained and available for Government review on the Contractor’s IDE.

System Safety Program (SSP) (CLIN 0001) The Contractor shall establish and maintain a SSP. The SSP shall address the EO4 subsystem components including all mechanical, electrical, optical and software interfaces. The Contractor shall perform a Subsystem Hazard Analysis (SHA) and an Operating and Support Hazard Analysis in accordance with MIL-STD-882E Task 204 and 206, respectively, and deliver via the IDE. The Contractor shall prepare a Safety Assessment Report (SAR) in accordance with MIL-STD-882E Task 301 and deliver via the IDE. The SAR shall be posted to IDE 45 days prior to CDR, 60 days prior to DT-B1 TRR, 60 Days prior to PCA and with revisions as required depending on changes to system design.

Hazard Risk (CLIN 0001) The Contractor shall track, monitor, and record via IDE the status of all hazards identified during the design effort. A Hazard Risk Index (HRI) and associated risk level shall be assigned to all hazards in accordance with MIL-STD-882E. All High, Serious, and Medium risk hazards, along with the risk mitigation plan and the residual risks, shall be presented at technical reviews. The Contractor shall mitigate all High risk level hazards, with the goal of eliminating or mitigating all hazards to a Medium risk level or lower for the service life of the subsystem.

Hazardous Materials Management Program (HMMP) (CLIN 0001) The contractor shall maintain a HMMP in accordance with National Aerospace Standard (NAS) 411 and Task 108 of MIL-STD-882E. The contractor shall perform all work under this contract in full compliance with all applicable Federal, State, and local environmental and occupational safety and health regulations.

HMMP Plan (CLIN 0001) The HMMP Plan shall document the Contractor’s method to identify, prohibit, restrict, eliminate, minimize and/or control hazardous materials. HMMP Plan shall be available for Government review via the IDE.

HMMP Report (CLIN 0001) The HMMP Report shall list EO4 subsystem hazardous materials identified in NAS 411 and the EO4 Subsystem Performance Specification (Attachment 1). The Contractor shall prepare an HMMP Report in accordance with NAS 411 and deliver via the IDE. The report shall be posted to IDE 30 days prior to PDR and additional revisions as changes occur.

If an identified hazardous material contains or consists of a NAVAIR Priority I or Priority II chemical as defined in the EO4 Subsystem Performance Specification (Attachment 1), an analysis shall be prepared documenting the technical and financial costs of alternative materials compared to the selected hazardous material in accordance with NAS 411, paragraph 4.3.3 and submitted per a Problem Identification Report, CDRL A005.

(CDRL A005 – Problem Identification Report) Quality Assurance (QA) (CLIN 0001) The Contractor shall establish, implement, document and maintain a Quality Management System (QMS) that ensures conformance to contractual requirements and meets the requirements of SAE AS 9100, AS 9102 and AS 9103 and ANSI/ASQC-Q9001. The procedures, planning, and all other documentation and data that comprise the quality system shall be made available to the Government via the IDE. Existing quality documents that meet the requirements of the contract may continue to be used. The Government may perform inspections, verifications, and evaluations to ascertain adequacy of the Contractors QMS. The Contractor shall require sub-Contractors to maintain a QMS that achieves control of the quality of the services and supplies provided.

Any non-conformance manufacturing practices shall be submitted to the Government as a PIR per CDRL A005.

(CDRL A005 – Problem Identification Report (PIR)) Parts Control Program (PCP) (CLIN 0001) The Contractor shall have a PCP to manage equipment, bit/piece, and ancillary equipment during design, development and production. The PCP shall:

a. Maximize designed-in product quality and design reuse

b. Maintain control of purchased items

c. Control proliferation of part types in products/programs

d. Ensure compliance with program technical documentation requirements

e. Include a counterfeit electronic part detection and avoidance system

f. Ensure compliance with established procedures for managing contract data Approved parts are those selected only from parts listed in the Government’s Haystack system or other commercial type provisioning screening products containing current Defense Logistics Information Service (DLIS) data or parts. The following order of precedence shall be used:

a. Haystack or other commercial type provisioning screening products containing current DLIS data. Commercial items (equipment and bit/piece) (MIL/QPL parts)

b. Alternate parts provided by Defense Supply Center Columbus (DSCC) through the web Parts Management Program Any other parts are considered unapproved. Unapproved parts shall be submitted per PIR CDRL A005 for approval by the Government. The PIR shall include the part's location, application, quantity used per subsystem and a detailed justification for use.

(CDRL A005 – Problem Identification Report (PIR)) Manufacturing and Production Planning (CLIN 0001) The Contractor shall:

a. Establish a manufacturing program and produce a manufacturing plan to which the Contractor shall provide Government access via the IDE.

b. Conduct planning to ensure that the potential follow-on production rate and delivery schedule can be met, considering the overall demand for facilities and personnel from competing programs.

c. Determine the types of manufacturing processes and methods required, and associated tooling and test equipment requirements. Where required processes or equipment do not exist, the Contractor shall determine whether they will be developed or outsourced and shall identify appropriate schedules for design/purchase and installation.

d. Review sub-Contractor and vendor manufacturing management plans and production facilities to assure visibility into manufacturing management by production surveillance and identification, including management and resolution of problems that may adversely impact the program.

e. Identify manufacturing risks and strategies for mitigation.

f. Plan the layout of the facility to ensure that machine loading, fabrication and assembly sequences, and part routings minimize part in-transit and queue time.

g. Conduct material planning to identify the types of materials and components needed for the construction of EO4 subsystem, considering producibility and the availability of parts and materials.

h. Conduct production planning to determine and schedule work orders and purchase orders, parts and material procurement, part/component fabrication, evaluation, assembly, test, and delivery based on lead time, planned delivery dates, inventory records, bills of material, available facilities and labor.

The manufacturing plan shall be completed and available on the Contractor’s IDE no later than ten working days prior to commencing the Production Readiness Review (PRR) event.

Support Agreements (CLIN 0001) The Contractor shall obtain support agreements from all EO4 subsystem hardware and software subcontractors and/or vendors that provide up to 20-year sustainment support for Government customers.

Government Furnished Property (GFP) (CLIN 0001) The Contractor shall:

a. Host a government site survey within 30 days after contract award to evaluate contractor facility requirements to support the operation of GFP.

b. Notify the Government Procuring Contracting Officer (PCO) of any GFP issues or deficiencies within 30 days of receipt.

GFP provided as part of this contract (SOW Attachment 2) shall be used only for the purposes of the EO4 program unless expressly authorized by the Government PCO. The Contractor shall not modify GFP from its original configuration unless authorized by the PCO and shall maintain/repair/return GFP in a fully functional, Ready For Issue (RFI) condition. In the event the Contractor cannot repair GFP, the Government shall be notified via PIR (CDRL A005).

(CDRL A005 – Problem Identification Report (PIR)) GFP Maintenance and Repair (CLIN 0001) The Contractor shall maintain/repair GFP with repair parts provided by the Navy.

Meetings and Reviews (CLIN 0001) The Contractor shall plan, coordinate, host, attend, support and conduct management, engineering and logistics meetings, reviews, conferences, and audits (hereinafter called "reviews"). Reviews shall be conducted at Contractor facilities and will be co-chaired by a Government and a Contractor representative. The Contractor shall make key personnel available to support the reviews. Principal sub-contractors shall attend reviews identified in the IMS. Reviews should be combined and conducted concurrently when possible. The Contractor shall deliver agendas and presentation materials via the IDE no later than ten working days prior to the review. Updates to all materials after the required posting date shall be provided at the reviews. The Contractor shall deliver minutes/reports/action items via the IDE no later than ten working days following each review. A summary of all action items, responsible parties, and estimated completion dates shall be included with the review minutes.

Post Award Conference (PAC) (CLIN 0001) The Contractor shall host a PAC at the Contractor facility within 30 calendar days of contract award.

The PAC shall entail, at a minimum, the following topics:

a. Introductions, roles, responsibilities, and organizational structure

b. Contractor Work Breakdown Structure (CWBS) and Control Account Managers (CAMs)

c. Contract Requirements

d. CLIN Structure

e. SOW Requirements

f. EO4 Subsystem Performance Specification Requirements (Attachment 1)

g. Contractor IMS, including critical path

h. GFP/GFI

i. GFP Maintenance

j. Risks/Opportunities

k. Action Items Quarterly Program Reviews (QPRs) (CLIN 0001) The Contractor shall host QPRs at the Contractor facility. The Contractor shall address all facets of contract performance including, but not limited to: program execution from a technical, cost, and schedule perspective; issues; risks and opportunities; corrective action plans; performance metrics; and estimates to complete remaining work.

Program Security (CLIN 0001) All Contractor personnel shall maintain a security clearance commensurate with the level of classification of the work performed as annotated in the Contract's DD-254, Contract Security Classification Specification Form.Contractor personnel shall require access to classified information in performance of this contract up to and including SECRET, with a safeguarding level of SECRET. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

The contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the contractor access shall be handled at the appropriate classification level. Unclassified information shall be handled in accordance with the appropriate designation (Controlled Unclassified Information; For Official Use Only; covered Defense Information). Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the Contracting Officer’s Representative (COR) of this contract for approval.

Controlled Unclassified Information including For Official Use Only and Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4 (enclosure 3 pages 11-18). Any product containing Covered Defense Information shall be assigned a distribution statement (B through F) using the criteria set forth in DoDI 5230.24 (Distribution Statements on Technical Documents) and have this statement displayed per Enclosure 3.

Classified reports, data and documentation, if any, shall be managed and prepared for shipment in accordance with the National Industry Security Program Operating Manual, DoD 5220.22-M.

INFORMATION SECURITY: If the work is performed at the Contractor's facility, the Contractor shall implement and maintain security procedures in accordance with DoD 5220.22-M (NISPOM), and SECNAV M-5510.36A, ensuring compliance up to and including SECRET mode of operation.

PUBLIC RELEASE: Any controlled unclassified information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through PMA260, 47123 Buse Road, RADM William A. Moffett Building, Patuxent River, MD 20670-1547C Operational Security (OPSEC) Program (CLIN 0001) The Contractor shall develop, implement, and maintain an OPSEC program. This program may include Information Assurance and Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security Decision Directive (NSDD) 298 and DoD 5220.22-M. The Contractor shall prepare and deliver an OPSEC Plan per CDRL A006.

(A006 – Operations Security (OPSEC) Plan) Cybersecurity (CLIN 0001) The Contractor shall comply with DoDI 8500.01 and DoDI 8510.01 and ensure subcontractor compliance. The Contractor shall identify, manage, and verify cybersecurity requirements. The contractor shall integrate cybersecurity into all functional areas including program protection and anti-tamper, if required. The Contractor shall ensure that relevant cybersecurity requirements are included in systems engineering and design documents, test plans, procedures, and reports. The Contractor’s cybersecurity workforce shall maintain compliance with DoD Directive (DoDD) 8140.01 and DoD 8570.01-M.

System Security Plan (SSP) (CLIN 0001) The Contractor shall prepare and maintain a SSP that implements the security requirements of DFARS 252.204-7012. The Contractor shall prepare and deliver an SSP per CDRL A007.

(CDRL A007 – System Security Plan (SSP)) Cybersecurity Test and Evaluation (CLIN 0001) The Contractor shall support the government in a cybersecurity test and evaluation activity including vulnerability scans and deficiency remedies.

Cybersecurity COTS/NDI (CLIN 0001) The Contractor shall conduct analysis for any commercial off-the-shelf (COTS) and/or non-developmental items (NDI) to ensure that they are appropriately configured, software/hardware/firmware is controlled, and any cybersecurity risks they pose are identified and mitigated.

Data (CLIN 0001) Unless otherwise specified in the CDRL, all time requirements contained in the SOW or the SOW attachments are in calendar days.

Duplication of Data (CLIN 0001) Data previously developed or available to the Contractor shall be used to the maximum extent possible in satisfying the requirements of this SOW. The Contractor shall report any redundant data requirements to the Government within this SOW and combine all documents, drawings and databases as appropriate.

Integrated Data Environment (IDE) (CLIN 0001) The Contractor shall establish and maintain a web-accessible IDE compatible with the Navy/Marine Corps Internet (NMCI). The IDE allows continuous, secure, real-time Government access for delivery and review of CDRLs and unclassified program documentation detailed in this SOW. The IDE shall be used to store, view, retrieve and manage digital data, including subcontractor data. The Contractor shall establish a digital environment that allows IPT members, as requested by the Government, full access to the IDE data. The Contractor shall maintain and make available on the IDE a list of authorized users. Upon contract completion, the Contractor shall prepare and deliver all data contained in the IDE per CDRL A008. (CDRL A008 - Integrated Data Environment (IDE) Information) Contract Data Requirements List (CDRL) (CLIN 0001) The Contractor shall submit all CDRL deliverables in electronic format via IDE unless otherwise specified within the individual CDRL. A CDRL delivery status spreadsheet shall be maintained on the IDE. All program documentation other than commercially available documentation shall be marked with an appropriate distribution statement in accordance with DoDI 5230.24 (Distribution Statement on Technical Documents). All Letter of Transmittals (LT) shall be delivered in a format compatible with Microsoft Office products.

Data Accession List (DAL) (CLIN 0001) The Contractor shall report all data/computer software/software applications that are used in the execution of this program and/or performance of this contract per CDRL A009.

(CDRL A009 - Data Accession List (DAL)) Maintenance Support During Development (CLIN 0001) The Contractor shall manage, maintain, repair, calibrate, test and return-to-service all EO4 subsystem hardware and software, including spares, in a fully operational condition until ownership is conveyed to the Government, which will occur upon approval of the final Technical Data Package (TDP) delivery to the Government. All EO4 subsystem hardware and software shall be in the latest configuration when ownership is conveyed to the Government.

Engineering Change Proposals (ECPs) (CLIN 0001) The Contractor shall prepare and deliver an engineering change proposal for any modification to a configuration end-item, including the eCASS EO configuration system and any Operational Test Program Set (OTPS), per CDRL A00A.

(CDRL A00A - Engineering Change Proposal (ECP))

Systems Engineering Systems Engineering Management (CLIN 0001) The Contractor shall manage systems engineering that is in alignment with the Government Systems Engineering Plan (SEP) (SOW Attachment 3).

Technical Reviews (CLIN 0001) Technical reviews, consisting of Systems Engineering Technical Reviews (SETR) and Technical Interchange Meetings (TIMs), shall be conducted in accordance with the SEP (SOW Attachment 3). TIMs may be conducted as meetings or teleconferences to review and discuss program status or issues.

Design Requirements Management (CLIN 0001) The Contractor shall utilize the Dynamic Object Oriented Requirements System (DOORS) requirements management tool to document and manage all system, subsystem and derived requirements. Requirements traceability shall link all testing requirements to source requirements and identify means of verification. The Contractor shall provide Government access to the DOORS database via the IDE and make available to the Government reports from the database. The Contractor shall prepare and deliver the DOORS database per CDRL B001.

(CDRL B001 – Dynamic Object Oriented Requirements System (DOORS) Database) Design for Interoperability (CLIN 0001) The Contractor shall ensure the EO4 subsystem is interoperable with the host eCASS system, the associated eCASS SMAT/CAL OTPSs, the F/A-18 ATFLIR OTPS, the H-60 MTS OTPS, and their associated weapon system units-under-test.

Open Systems Architecture (CLIN 0001) The Contractor shall demonstrate at design reviews that the standards selected for use are widely adopted international or national industry standards (including interface standards), or are widely adopted industry consensus-based standard where appropriate. Where non-widely adopted standards are used, the Contractor shall provide rationale, impact, and analysis for choosing that standard.

Proprietary and Non-Open Interface (CLIN 0001) The design shall be layered, modular, and maximize use of open, non-vendor-unique, non-proprietary Application Programming Interfaces (APIs).

The Contractor shall obtain government approval prior to the use of any proprietary and non-open interface standards to include data exchange standards, as well as physical interfaces, in their design.

Design for Human Systems Integration (HSI) (CLIN 0001) The Contractor shall provide status of human engineering integration requirements contained in the during EO4 design reviews and TIMs per the EO4 Subsystem Performance Specification (Attachment 1).

Design for Producibility (CLIN 0001) Designs shall include consideration for repeatable fabrication and satisfaction of physical and functional performance requirements. The Contractor shall utilize manufacturing personnel in the design process to ensure optimal ease and economy in fabrication, assembly, inspection, test and acceptance of production hardware. The Contractor shall consider materials, tooling, facilities, capital equipment, test equipment, methods, and processes in ensuring producibility of the EO4 subsystem. Resulting technical data, documentation, or reports from manufacturing related actions shall be presented at design reviews and retained in the IDE database with access provided to the Government.

Grounding, Bonding, and Shielding (CLIN 0001) The Contractor shall ensure that the EO4 subsystem is properly grounded, bonded and shielded to prevent ground loops and common ground returns for power and control circuits. The Contractor shall ensure that all metal parts, shields, control panels, switch handles and connectors are grounded to the system chassis and that provisions are made to ground EO4 subsystem to the ship or facility structure.

Laser Safety Review Board (LSRB) (CLIN 0001) The Contractor shall design an EO4 subsystem that complies with the requirements of OPNAVINST 5100.27B, Navy Laser Safety Control Program. The Contractor shall complete OPNAVINST 5100.27B Enclosure 2 Appendix B & C checklists and prepare a LSRB package in accordance with OPNAVINST 5100.27B Enclosure 4. The Contractor shall present their approach for laser safety during each design review and make available, via the IDE, the completed checklist and LSRB package at Test Readiness Review (TRR).

Facility Integration and Installation (CLIN 0001) The Contractor shall design an EO4 subsystem that provides simplicity in installation and removal. The Contractor shall provide EO4 subsystem installation procedures. The Contractor shall provide all hardware required for EO4 installation. The Contractor shall update the GFI eCASS Facility Requirements Document (FRD) per CDRL B002.

(CDRL B002 - Facility Requirements Document (FRD)) Software (CLIN 0001) The Contractor shall focus on the ease of maintainability throughout the development of the software. Elements that shall be considered include minimization of the number of unique programming languages within the system software, use of high level programming languages and the development/availability of detailed documentation.

The software source code shall be written to implement the required functions of the EO4 subsystem. The Contractor shall develop a single EO4 Software image. The EO4 software shall have a driver-level API that is designed to be called by the eCASS EO3 instrument wrapper as modified to work with the EO4 API.

The Contractor shall provide training material via the IDE for any Computer Aided Software Engineering (CASE) tools used for software documentation, development, testing, monitoring and support. Two sets of CASE tool licenses shall be delivered to the Government at the beginning of the software development process per Software Production Specification (SPS) CDRL B00E. The Contractor shall provide the Government team the ability to monitor the software development in real time by posting all software documentation, software development folders and software metrics using the IDE. Software shall be written using commercially available software so that the Government can cost effectively provide life cycle support.

CDRL B00E - Software Product Specification (SPS) Software Engineering Approach (Diskless Node) (CLIN 0001) The EO4 video processor/control computer shall be a diskless node that performs a network boot from the eCASS master's hard drive shall use iSCSI protocol. Use of non-volatile storage shall be restricted so that data is not written to non-volatile storage except under limited, controlled circumstances such as the updating of calibration factors or loading of firmware.

Software Development Plan (SDP) (CLIN 0001) The Contractor shall maintain a software design/development process that meets, at a minimum, the requirements of the Software Engineering Institute (SEI) Capability Maturity Model (CMMI) Level 3 or equivalent. The Contractor shall prepare and deliver an SDP that provides insight into, and a tool for monitoring, the processes to be followed for software development, the methods to be used, the approach to be followed for each activity, and project schedules, organization, and resources per SDP CDRL B003. The SDP level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted. Information provided must include, as minimum, specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification. The Contractor shall allocate the EO4 System performance requirements into the Computer Software Configuration Items (CSCIs) listed in the SSDP.

Software metrics related to schedule, quality, staffing, build stability, size, requirements volatility, testing and software maturity shall be prepared and delivered per SDP CDRL B004.

CDRL B003 - Software Development Plan (SDP) Software Requirements Specification (SRS) (CLIN 0001) The Contractor shall prepare and deliver an SRS per CDRL B004.

CDRL B004 - Software Requirements Specification…