N00024-21-R-6410-0004.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

See Summary of Changes.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 19

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 29-Jul-2021

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X N0002421R6410

X 9B. DATED (SEE ITEM 11)

24-Jun-2021

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

29-Jul-2021

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2060

N00024 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002421R6410

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

# Date Document Page

Section/Paragraph Question

Proposed Action/Change

Answer

31 7/13/2021 N/A N/A N/A

One of the key questions, which is still unresolved, is a export license to send the performance spec to foreign nationals (UK). It is our opinion and those of independent consultants and Commerce, that a license is required. We respectfully request a 30 day extension to commence after our license is approved. This is only fair and without this extension we are at a severe disadvantage, especially if others sent this information on without a license.

N/A See Amendment 0004.

32 7/13/2021 N/A N/A N/A

Are additional attachments (test reports, detailed analysis, etc.), that are deemed technically relevant, permitted to be attached to our response as additional proof of meeting certain requirements or should an offeror acknowledge in our base response that additional information is available to the Government upon request to further substantiate our initial validation of adherence to a specific requirement?

N/A

Offerors should ensure their proposal is complete and does not rely on an external support not contained within the proposal. All proposals must conform to the requirements of the RFP.

33 7/13/2021 RFP 29 Section B, Note D

Please clarify what is an estimated budget for the delivery of the contract as Note D states: “Orders may be placed under these PIO CLINs up to the maximum combined value of $20,000,000, and as identified in the CLIN descriptions.”

Does this mean that the excepted budget for this solicitation shall not exceed $20,000,000?

N/A

The contract budget will not be released.

As indicated in the RFP, Note D applies to

CLIN 0901.

34 7/13/2021 RFP 137 1.2, Paragraph 4

We respectfully request an extension for two weeks after receipt of the export license for the question and answer period. Again, we will need time to digest and ask questions and receive answers in a timely manner.

Right now, we could receive answers after the Q&A period which may generate other questions.

N/A See Question 31.

35 7/13/2021 RFP 143

Section L 4.1.5.2

Subcontractor Management

The solicitation states “a.

Provide a supplier and sub-vendor listing, including a brief description of raw material source, listing of subcontractors, and a description of how the Offeror controls and monitors subcontractors.”

Regarding the supplier and sub-vendor listing – are major subcontractors required to also provide a supplier and sub-vendor listing or is a listing only required from the primary offeror?

N/A

Offers should provide the information required by section L

4.1.5.2 for all major subcontractors.

36 7/13/2021 Attachment

J-1 N/A Section 3.2.1.6

In reference to performance spec statement 3.2.1.6., Alphanumeric Display Operation: “Must have capability for on-board decompression computer to be added via software update”

What DOD/National security requirements must be met for the on-board decompression computer and software?

N/A

IAW SOW

Section 3.2.1.6, any future software upgrades would need to go through an updated IV&V process. The future upgrades will also have to undergo EMI/EMF and magnetic testing to address some aspects of the alphanumeric display.

37 7/13/2021 Attachment

J-1 N/A Section 3.4.8

In reference to performance spec statement 3.4.8.

Material Selection “Breathing loop components shall be reviewed to ensure that off gassing of components does not include formaldehyde or other harmful gases.”

Is there a list of prohibited materials? Are materials that are baked off during the manufacturing process to remove harmful gasses acceptable? Will this be tested, if so is there list of harmful gasses that will be tested?

N/A See Amendment 0004.

38 7/13/2021 Attachment

J-1 N/A Section 4.4.8

In reference to performance spec statement 4.4.8.

Material Selection “Materials, and support material provided by the manufacturer, will be reviewed to ensure that off gassing is not harmful in any intended use environments. “

How will ‘Materials, and support material” be reviewed or tested?

N/A See Amendment 0004.

39 7/14/2021

RFP

Attachment J-1

Section 2.1 Ref B

Based on reference to MIL- STD-810H dated 31-Jan-19 in the RFP and Attachment J-1 we believe that "Change 1" in the Attachment J-1 reference is a holdover from the previous version MIL- STD-810G Change 1. If our understanding is correct, please update the reference accordingly.

N/A See Amendment 0004..

40 7/14/2021 RFP 41 3.2.2.5

Requirement states the TDP shall be maintained IAW

ASME Y14.100, ASME

Y14.34M, ASME Y14.35M

and ASME Y14.24. The MMUBA design documentation was established using recognised European standards including BS 8888 and ISO 8015. Is it acceptable to include documentation

N/A

The TDP shall be submitted in accordance with the RFP.

within the TDP which conforms to equivalent recognised international standards?

41 7/14/2021 RFP 43 3.2.3.6

Do we need to make accomodation for the full-face mask assembly in our packaging?

N/A See Amendment

42 7/16/2021 RFP 44 3.2.3.12.1

The A001 CDRL is for presentation materials for Meetings, Reviews, and Conferences. The above SOW section states Digital 3D models and original, raw files for the computer-based training will be delivered with the TDP to support Government updates. Please provide a CDRL that states which DID to follow for format, file types, and information required we need to have for this CDRL.

Also, please state what the delivery date is for this data.

N/A See Amendment 0004.

43 7/16/2021 RFP 175 4.1.1

The participants of the Government evaluation under the MMUBA T&E program provided seven sample MMUBAs that were tested. Can the Government confirm that they have access to the test data from this evaluation program and that the evaluation participants can make reference to the testing in their proposal to demonstrate technical compliance with the Specification.

N/A See Question 32.

44 7/16/2021

EX. A

CDRLS

N/A General

Please provide the CDRLs that appear to be missing fromWhen compared to the SOW in RFP section C, CDRLS A031 (Repair Parts Report) and A034 (Transition of Depot Maintenance Report) appear to be missing. Please provide these CDRLs.

N/A

The government has verified that A031 and A034 are included as part of the base solicitation.

45 7/16/2021 Amendment

3 General

Question response numbers skip from 15 to 18 -- will responses to questions 16 and 17 be published?

N/A See Amendment 0002.

46 7/16/2021 Amendment

5 Question # 23

Should there be a period after "narrative" in the answer to question #23?

N/A

Question 23 answer is confirmed to be correct.

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 10-Aug-2021 02:00 PM to 25-Aug-2021 02:00 PM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

1 Scope/System Description

1.1 Scope/System Description

The MMUBA is an Underwater Breathing Apparatus (UBA) that supports a variety of military diving operations in situations such as deep or shallow water diving, heavy and stationary workloads, and swimming appreciable distances. The MMUBA program provides amplified capabilities compared to the current MK 16 Mod 1 UBA and provides Explosive Ordnance Disposal (EOD) and Mobile Diving and Salvage Unit (MDSU) divers with access to new technology, while meeting the requirements outlined elsewhere in this SOW. Key to these increased capabilities are an Emergency Gas Supply (EGS), increased safety features, increased reliability, increased usability, and data download to assist in forensics. The baseline system software and hardware architecture will be able to accommodate future upgrades such as a Heads-Up Display (HUD) and CO2 monitoring.

The primary mission area for the MMUBA will be EOD missions for Mine Counter-Measures (MCM) (including the Very Shallow Water (VSW) MCM mission). The MMUBA will also support MDSU missions, including underwater emergency/battle damage repair, combat harbor clearance/search, underwater ship’s husbandry, rescue and assistance, and demolition in a variety of expeditionary environments.

2 Applicable Documents In the event of conflict between the documents referenced herein and the contents of this SOW, the order of precedence shall be IAW FAR 52.215-8.

Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available on the internet at the Department of Defense ASSIST database at https://assist.dla.mil/. Joint Chiefs of Staff, DoD Directives (DoDD), DoD Instructions (DoDI) and Publications documents can be found on the Acquisition, Technology, and Logistics (AT&L) Acquisition Knowledge Sharing System (AKSS) at or at the DoD Issuances website at: http://www.dtic.mil/whs/directives/. Non-Government documents should be obtained from commercial sources.

The following documents of issue in effect as of the execution date of the contract are applicable to this Statement of Work and attached appendices to the extent specified herein or as modified under the contract. These documents are for guidance only.

2.1 Military Standards Specifications, and Handbooks

MIL-STD-810H 31-Jan-19 Environmental Engineering Considerations and Laboratory Tests

MIL-STD-1330D

Change 1

28-Jun-07 Standard Practice for Precision Cleaning and Testing of Shipboard Oxygen, Helium, Helium-Oxygen, Nitrogen, and Hydrogen Systems

MIL-DTL-19595D 11-Feb-03 Magnetic Effect Limits for Non-Magnetic Equipment Used in the Proximity of Magnetic Influence Ordnance

MIL-STD-1472H 15-Sep-2020 Design Criteria Standard: Human Engineering

MIL-STD-2073-1E

Change 4

22-Apr-19 Standard Practice for Military Packaging

MIL-STD-129R Change

27-Sep-19 Military Marking for Shipment and Storage

EIA-649C 07-Feb-19 Configuration Management Standard

NEDU TM 15-01 01-Jun-15 U.S. Navy Unmanned Test Methods and Performance Limits for Underwater Breathing Apparatus

SS521-AA-MAN-010

Rev 3 Change A

05-Mar-18 U.S. Navy Diving and Manned Hyperbaric Systems Safety Certification Manual

IEEE Standard 1012-

9-Sept-17 System, Software, and Hardware Verification and Validation

MIL-STD-882E 11-May-12 Department of Defense Standard Practice System Safety

MIL-STD-31000B Oct-18 Technical Data Packages

ASME Y14.100 2017 Engineering Drawing Packages

ASME Y14.34M 2013 Associated Lists

ASME Y14.35M 2014 Revisions of Engineering Drawings and Associated Documents

2.2 Department of Defense Regulations, Directives and Instructions

DoDI 8510.01 28-Jul-17 Risk Management Framework (RMF) for DoD Information Technology, Change 2

DoDI 8500.01 14-Mar-14 Cybersecurity

2.3 Other References

NIST SP 800-171A Jun-18 Assessing Security Requirements for Controlled Unclassified Information

S1317-00-000-A-P-C Rev I

Sep-10 Underwater Configuration Management (CM) Plan

FIPS 140-2 25-May-01 Security Requirements for Cryptographic Modules

3 Requirements

3.1 General Requirements (ALL CLINS WITH THE EXCEPTION OF 0901, 1100, 1101, 2100, 2101, 2102, 3100, 3101, 3102, 4100, 4101, 4102, 5100, 5101, 5102, 6100, 6101, 6102, 7100, 7101, and 7102)

3.1.1 Program Management

The Contractor shall establish and maintain a Program Management (PM) process that ensures all work associated with this SOW is clearly and concisely demonstrated and meets all technical objectives within the Contractor’s established cost, schedule, and performance baselines. Program management shall include metrics and tracking processes, and risk and opportunity management to allow clear visibility into the program and to ensure the program remains within cost and schedule. The Contractor shall designate a single Program Manager who will ensure all work conducted within this contract is planned and executed in a manner that will achieve all management, technical, logistics, budgetary, and schedule objectives.

3.1.2 Meetings and Reviews

The Contractor shall prepare presentation material (CDRL A001) to support all management and technical reviews.

When hosting a review, the Contractor will make all facility arrangements. The Contractor shall capture meeting minutes (CDRL A002) and action items during all meetings and technical reviews.

A Contract Kick-Off Meeting shall be held within thirty (30) calendar days after contract award at the Contractor’s facility. This meeting shall be a face-to-face or video conference meeting between key personnel and shall include a team introduction, general program discussion, contract execution strategy and risks, and a depot level maintenance strategy. The Contractor shall provide presentation materials to the Government ten (10) business days in advance of the kick-off meeting.

In conjunction with the kick-off meeting, the Contractor shall host a meeting with the Government to review Government Furnished Equipment/Government Furnished Information (GFE/GFI). The Contractor shall provide questions about the GFE/GFI ten (10) business days prior to the kick-off meeting.

The duration of the kick-off meeting and the GFE/GFI exchange is anticipated to be no longer than two (2) business days.

CDRL: Presentation Materials – A001 CDRL: Meeting Minutes – A002

3.1.3 Schedule Management

The Contractor shall develop and maintain an Integrated Master Schedule (IMS) (CDRL A009) by logically networking detailed program activities including but not limited to: testing schedule, production schedule, sustainment schedule, planned events and milestones, accomplishments, and activities from contract award to the completion of the contract. The IMS shall also include the efforts of all activities, including the Contractor and subcontractor, and present a current, integrated view of the contract or agreement that is consistent with resource plans, and other approved documentation. Furthermore, the IMS shall reflect those risks identified and documented in the Contractor’s risk management plan (CDRL A010). The Contractor shall notify the Government in writing within five (5) working days of identifying any anticipated or projected work stoppages or delays that will impact delivery schedules.

CDRL: Integrated Master Schedule (IMS) – A009 CDRL: Contractor’s Risk Management Plan – A010

3.1.4 Quality Assurance and Subcontract Management and Control The Contractor shall develop and maintain a Government-approved quality assurance (QA) program IAW SS521- AA-MAN-010 that provides reasonable confidence, through inspections and documentations, that all work has been accomplished in accordance with approved drawings, sketches, applicable Military Standards and Specifications, and other directives. The Contractor shall submit a corresponding QA Program Plan (CDRL A003) to PMS 408, for approval. The Contractor shall also support the establishment of the QA program in support of the Government efforts.

The Contractor shall identify and monitor subcontractor technical, quality, schedule, and milestone achievement on a continuing basis, according to the Contractor’s established subcontract management processes. The Contractor shall also ensure that any subcontractors are in compliance with the Contractor’s approved Quality Assurance Program Plan (CDRL A003).

CDRL: Quality Assurance Program Plan – A003

3.1.5 SSP Requirements

The Contractor shall establish and maintain a System Security Plan (SSP) and Plans of Action (CDRL A012).

3.1.5.1 System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews

a) Within thirty (30) days of contract award, the Contractor shall make its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) available for review by the Government at the contractor’s facility. The SSP(s) shall implement the security requirements in Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract. The Contractor shall fully cooperate in the Government’s review of the SSPs at the Contractor’s facility.

b) If the Government determines that the SSP(s) does not adequately implement the requirements of DFARS clause 252.204-7012 then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government. The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a plan of action and milestones (POAM) for the correction of the identified deficiencies. The Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

c) Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s) at the Contractor’s facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies in the SSP(s).

d) The Government may, in its sole discretion, conduct subsequent reviews at the Contractor’s site to verify the information in the SSP(s). The Government will conduct such reviews at least every three (3) years (measured from the date of contract award) and may conduct such reviews at any time upon thirty (30) days’ notice to the Contractor.

CDRL: System Security Plan & Plans of Action – A012

3.1.5.2 Compliance to NIST 800-171

a) The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1) (NIST SP 800-171), or establish a SSP(s) and POA&Ms that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b)(2), for all covered contractor information systems affecting this contract.

b) Notwithstanding the allowance for such variation, the contractor shall identify in any SSP and POA&M their plans to implement the following, at a minimum:

(1) Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as CNC equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted;

(2) Implement Control 3.1.5 (least privilege) and associated Controls, and identify practices that the contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;

(3) Implement Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

(4) Audit user privileges on at least an annual basis;

(5) Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e.

FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM); and,

ii. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program);

(6) Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation which shall be evaluated by the Navy for risk acceptance.

(7) Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

CDRL: Cybersecurity Documentation to Support Risk Management Framework (RMF) – A014

3.1.5.3 Cyber Incident Response:

a) The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period), deliver all data used in performance of the contract that the Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

b) Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3) Instructions for Submitting Media available at http://www.acq.osd.mil/dpap/dars/pgi/docs/Instructions_for_Submitting_Me.... In delivery of the incident data, the Contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

c) If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification.

The contracting officer will approve or disapprove the request after coordination with DC3.

CDRL: Cyber Incident Report – A013

3.1.5.4 Naval Criminal Investigative Service (NCIS) Outreach

The Contractor shall engage with NCIS industry outreach efforts and consider recommendations for hardening of covered contractor information systems affecting DON programs and technologies.

3.1.5.5 NCIS/Industry Monitoring

a) In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

b) If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor's information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the Contractor.

c) In all cases, the collection or provision of data and any activities associated with this statement of work shall be in accordance with federal, state, and non-US law.

3.2 Certification and Production (ALL CLINS WITH THE EXCEPTION OF 0901, 1100, 1101, 2100, 2101, 2102, 3100, 3101, 3102, 4100, 4101, 4102, 5100, 5101, 5102, 6100, 6101, 6102, 7100, 7101, and 7102)

3.2.1 General Requirements

The MMUBA systems shall meet the technical specifications specified in the System Performance Specifications, Attachment J-1. The Contractor shall provide an As-Built Configuration List (ABCL) (CDRL A016) that documents each MMUBA delivered to identify original manufacturers and include serial numbers and part numbers. The Contractor shall provide a warranty for delivered systems IAW FAR 52.246-17.

CDRL: As-Built Configuration List (ABCL) – A016

3.2.1.1 MMUBA Production Reporting

The Contractor shall include Item Unique Identification (IUID) markings on MMUBA Systems via Wide Area Work Flow (WAWF) in accordance with DFARS 252.211-7003. The Contractor shall maintain marking and verification records for all IUID qualifying items manufactured on this contract. These records shall be available for inspection by the Government at all times.

CDRL: IUID Marking Activity and Verification Report (A017)

3.2.1.2 Status Reporting

The Contractor shall provide status reviews on a monthly basis during the certification portion of the contract.

Following completion of the certification effort, status reviews shall be held quarterly. Status reviews may be held virtually. The Contractor shall provide a summary of the Monthly Status Report, a Risk and Opportunity Assessment, and the IMS. The Contractor shall provide briefing materials to the Government three (3) business days prior to the scheduled meeting. The briefing materials shall address (at a minimum):

Status of significant program events Status of significant/major certification, production, logistics efforts, and/or issue resolution Configuration Baseline Status (to include implementation status of approved changes) Risk and opportunity assessment Schedules and critical path analysis for individual tasks, delivery orders, and equipment production/deliveries Action item status from prior reviews, plan of action for resolution, and estimated completion dates

CDRL: Presentation Materials – A001 CDRL: Meeting Minutes – A002

3.2.1.3 Production Inspection and Acceptance

First Article Qualification Testing (FAQT) and Factory Acceptance Testing (FAT) will be completed by the Contractor at the Contractor’s facility.

For CLIN 1000, the Contractor shall submit a FAQT Plan for Government approval (CDRL A018). The FAQT will be conducted by the Contractor on all initial production units IAW with SS521-AA-MAN-010. The Government, at its discretion, may elect to observe the FAQT. The Contractor shall document and deliver the FAQT results subsequent to successful FAQT completion (CDRL A019).

For CLINs 3000, 4000, 5000, 6000, and 7000, if exercised, FAT shall be completed IAW with SS521-AA-MAN-

010. The Contractor shall deliver units to the Government within 60 days of FAT completion. The Contractor shall document and deliver FAT results subsequent to completion (CDRL A020).

Government Acceptance Testing (GAT) of all delivered units will be completed by Government personnel at destination upon delivery (see Section C, 3.2.2.2 and 3.2.3.7).

3.2.1.4 Failure Mode, Effects, and Criticality Analysis (FMECA) The Contractor shall provide an analysis of failures IAW SS521-AA-MAN-010, and document the resulting potential impact on mission success, performance, personnel safety, and maintainability. This analysis is intended to promote design corrective actions by identifying potential failure risks in order that appropriate corrective actions may be taken early to eliminate or control high risk items to improve operational readiness and reduce life cycle costs.

CDRL: FMECA Report – A021

3.2.1.5 Independent Validation & Verification (IV&V) Report

Prior to initial certification, the Contractor shall deliver an independent IV&V in accordance with IEEE Standard 1012-2016 (CDRL A026). The Contractor shall ensure that the IV&V organization is financially and managerially independent of the development team.

CDRL: Independent Validation & Verification (IV&V) Report – A026

3.2.1.6 Software Development Plan (SDP)

The Contractor shall prepare and deliver a Software Development Plan (SDP) for software developed or maintained under this effort. The SDP shall meet the requirements of Clause C-227-H007, Software Development Requirements (NAVSEA) (OCT 2018). The software shall meet the cybersecurity and other security requirements specified in this SOW. Once approved by the Government, the Contractor shall follow the SDP for all computer software developed or maintained under this effort.

CDRL: Software Development Plan (SDP) – A033

3.2.2 Certification (CLIN 1000)

3.2.2.1 Physical Configuration Audit (PCA)

Prior to initial certification, the System Certification Authority (SCA) will conduct an on-site visit to the manufacturer’s facility, which shall include a facility tour. A Physical Configuration Audit (PCA) survey will also be conducted by the Government on the first article production build of the MMUBA units. PCA surveys of MMUBA units shall be completed at the site of delivery as determined by the Program Office. A PCA Plan will be developed and provided to the manufacturer prior to the survey. The Contractor shall provide Subject Matter Expert (SME) support and all necessary special tools required to support the Government PCA. The PCA Plan will be used to: validate the production process, examine the “as-built” configuration against the final design drawings, and perform a review of the Objective Quality Evidence (OQE). OQE shall be generated by the manufacturer to document: certificates of conformances for all material/components/parts used in the fabrication of the MMUBA, results of non-destructive and functional testing, and verification of system oxygen cleaning.

The Contractor shall respond via letter to PCA findings, recommend corrective actions, and resolve all deficiencies identified during these audits within 30 calendar days of the PCA, and deliver a final report on the PCA process and results. The Contractor shall document the results of the PCA in a Configuration Audit Summary Report (CDRL A015).

CDRL: Physical Configuration Audit Summary Report – A015

3.2.2.2 Government Acceptance Testing (GAT)

Government Acceptance Testing (GAT) for CLIN 1000 will verify that each MMUBA system conforms to the attached performance specifications. The tests will include unmanned tests, environmental tests, and manned in-water tests. Testing will be accomplished in accordance with MIL-STD-810H and NEDU TM 15-01. The Government will conduct testing to validate operational suitability. This certification testing of the system will be in accordance with SS521-AA-MAN-010. As part of the certification process, the Government will perform site visits to the Contractor’s facilities and conduct Government Quality Assurance Audits to ensure that a robust quality system is in place. Additionally, the Contractor must be able to provide auditors access to Quality Assurance Procedures/Data, Design, and Drawing Control Data, Material Control Data, Fabrication and Manufacturing Control Data, and Cleaning Control Data to ensure that processes and procedures are monitored and corrected as required.

CDRL: FAQT Plan and Procedures – A018 CDRL: FAQT Report – A019 CDRL: Factory Acceptance Testing (FAT) Report – A020

3.2.2.3 System Verification Review (SVR)/Production Readiness Review (PRR) A SVR/PRR shall be held no later than ninety (90) ninety calendar days prior to exercise of CLIN 3000 at Contractor’s location. This meeting shall be a face-to-face meeting between key personnel, and include presentations and material developed by both the Government and Contractor. The Contractor shall provide presentation materials to the Government ten (10) business days in advance of the meeting.

The presentations developed by the Contractor and subcontractors shall include information on production planning and quality controls in place for producing the systems, and the overall manufacturing readiness. These briefs will focus on providing confidence to the Government that the Contractor has quality systems and planning in place and there are no high risks associated with moving forward. During this time the System Certification Authority (SCA) will conduct a quality management system audit of the manufacturer’s management and processes used in the production of the systems. The on-site audit shall include a tour of the facility, to include all areas used in the production of the systems. The Contractor shall prepare presentation material (CDRL A001) to support all management and technical reviews.

The duration of the meeting shall be no longer than two (2) business days.

CDRL: Presentation Materials – A001

3.2.2.4 Manufacturing Readiness Assessment (MRA)

A Government-led Manufacturing Readiness Assessment (MRA) will be held prior to PRR and will assess the Contractor’s Manufacturing Readiness Level (MRL), as defined in the MRL Deskbook, Version 2018. The Contractor is responsible for assessing the MRL of their own production facility and their highest risk suppliers, including, but not limited to, the suppliers who provide the longest lead time components or have the lowest rate of passing incoming inspection after receipt of material by the Contractor. The Contractor shall conduct MRAs at mutually-agreed critical suppliers with Government participation. The Contractor shall identify high manufacturing risk technologies or components and present appropriate risk analysis and associated maturation plans within the Integrated Master Schedule. The Contractor shall monitor and provide status at all program reviews for in-house and supplier MRLs and shall re-assess MRLs in areas for which design, process, major source of supply, or facility location changes have occurred that could impact the MRL. The Contractor shall set up and participate with the Government in regularly scheduled Integrated Product Team meetings dedicated to production readiness. The Contractor shall achieve MRL 7 in preparation for the PRR, and shall demonstrate plans and progress to reaching

MRL 8.

CDRL: Presentation Materials – A001

3.2.2.5 Technical Data Package (TDP) (Level II)

The Contractor shall provide the Government with a Level II TDP (CDRL A022), desired with Government purpose rights, or better, that reflects final system design and configuration, in conjunction with system certification efforts.

The TDP shall consist of the product engineering data related to the design and manufacture of the MMUBA system with the minimal disclosure of proprietary design data and software data that will be required to support MMUBA certification by NAVSEA 00C as referenced in the NAVSEA SS521-AA-MAN-010. Software data shall include sufficient software communication information language to support NAVSEA 00C certification. The product drawings and/or CAD models shall contain all descriptive documentation needed to ensure the Government can develop all required training and provide lifecycle support down to the Lowest Replaceable Unit (LRU) level.

The TDP shall be maintained IAW MIL-STD-31000B, ASME Y14.100, ASME Y14.34M, and ASME Y14.35M.

The Level II TDP shall include, at a minimum: hardware, firmware, and software component description documents, manufacturing processes, and final assemblies, work, welding and cleaning procedures, process instructions, native/master files for drawings, parts lists, data lists, wiring lists, schematics, interconnect diagrams, Gerber files, special tooling drawings, specifications, special packaging instructions (including storage and/or shipping containers with accomodation for a M48 Mod 1 FFM), source control drawings, specification control drawings, digital photographic images of assembly procedures, cable dressing techniques, software, and interface control information for hardware and software/firmware. Product drawings and associated lists shall be developed and maintained by the Contractor and structured IAW ASME Y14.24. Material and process specifications, special inspection equipment drawings and special tooling drawings and their associated lists shall be included in the TDP for complete product definition without disclosure of proprietary design data.

The Contractor should also provide one detailed and complete 3D model of the unit/system assembly, desired with Government purpose rights. If different system configurations exist (e.g., optional tools), the Contractor shall provide one detailed and complete 3D model for each configuration (at the assembly level). Model(s) shall be in a 3D CAD supported format (compatible with Autodesk 3DS Max (e.g., .ipt, iam)). Model(s) shall include all parts (e.g., housing, electronics, brackets, tubing, other hardware). Model(s) with materials applied are preferred.

The TDP shall be delivered to the Government NLT 60 days prior to delivery of initial production MMUBA units.

The Contractor shall provide an updated TDP and 3D models to reflect any modifications made to the commercial UBA as a result of engineering changes contractually implemented under the ECP process.

CDRL: Technical Data Package (TDP) – A022

3.2.2.6 Level of Repair Analysis (LORA)

The Contractor shall complete a LORA for the system that addresses:

Analysis conducted for all top-level configured items (CI), the part failure percentage information, and information on the environmental conditions where the failure occurred, if available

Resulting recommendations to present the most effective and efficient location where top-level configured items (CI) can be repaired

Provide sufficient detail (personnel, facilities, test equipment, etc.) for the Government to make an initial judgement of the repair and maintenance facilities to maintain the UBAs procured under this contract.

The Contractor shall research tasks and skills required for the system in its intended environment and develop and deliver the final LORA Report (CDRL A032), to identify the rates and specialties required for system operation and maintenance.

CDRL: Technical Report – Study/Services (LORA Report) – A032

3.2.3 Production (CLINs 1001, 1002, 1003, 1004, 1005, 2001, 2002, 2003, 2004, 3000, 3001, 3002, 3003, 3004, 3005, 4000, 4001, 4002, 4003, 5000, 5001, 5002, 6000, 6001, 6002, 7000, 7001, and 7002)

3.2.3.1 Configuration Management

The Contractor shall plan, establish and implement a Configuration Management (CM) Program in accordance with EIA-649C. The Contractor’s change management process shall be capable of processing required configuration changes in a time frame that enables identification, evaluation, and implementation of proposed changes without impact to production schedules.

The Contractor shall provide a CM Plan (CDRL A004) identifying and documenting the Contractor’s CM Program.

Configuration Management shall be maintained by the Contractor in accordance with S1317-00-000-A-P-C Rev I.

The principal use is to provide the Government a basis for review, evaluation, and monitoring of the CM program and its proposed components.

CDRL: Configuration Management Plan (CM Plan) – A004

3.2.3.2 Change Management Process for Design Changes

In the event that the design of the system has to be permanently changed, a Preliminary Engineering Change Proposal (PECP) must be submitted and approved prior to submission of an Engineering Change Proposal (ECP).

ECPs will be defined by the Government as either Class I or Class II ECPs. All PECPs and ECPs shall be submitted in accordance with the approved S1317-00-000-A-P-C Rev I.

CDRL: Engineering Change Proposal (ECP) – A005

3.2.3.3 Notice of Revision (NOR)

The Contractor shall provide a NOR, which as required, is an ancillary document to the ECP. This form is used to document the drawing changes associated with the ECPs.

CDRL: Notice of Revision (NOR) – A006

3.2.3.4 Request for Variance (RFV)

The Contractor shall submit a RFV only as required. These requests are called non-permanent design changes because they are only approved for a specific set of serial numbered Configuration Items and Systems. RFVs are used to document specific Configuration Items and Systems that do not meet the documented drawing or specification requirements. RFVs require approval by the Contracting Officer and will require contract consideration from the Contractor. The Contractor shall submit proposed consideration with each RFV.

CDRL: Request for Variance – A007

3.2.3.5 Obsolescence Management

The Contractor shall be responsible for minimizing obsolescence by selecting products that will avoid or resolve hardware, software and firmware obsolescence issues. The Contractor shall be required to develop a continuous Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management process (CDRL A008) which shall provide quarterly status reports, as well as notification of emergent obsolescence issues relevant to the approved MMUBA baseline. The Contractor shall provide engineering technology assessments to predict and forecast obsolescence. The assessment shall be provided quarterly, and will consist of:

Courses of actions to address the issue Provide a timeframe to correct the issue Forecast when to take action to eliminate negative impact

The Contractor shall recommend and conduct out-of-production investigations, trade studies, capability demonstrations for potential upgrades, rework, design changes, and technology insertion programs as needed for product operational improvements. The Contractor shall also perform a tailored analysis of alternatives to identify and monitor the best value solutions for critical DMSMS issues. The Contractor shall participate in DMSMS reviews as a member of the DMSMS Management Team (DMT) and liaison with Government engineering on findings of DMSMS monitoring for reporting.

CDRL: DMSMS Management Plan (DMSMS Health Assessment) – A008

3.2.3.6 Government Furnished Equipment (GFE)/Government Furnished Information (GFI) The Government will provide Full-Face Mask (FFMs) Assemblies as GFE to the Contractor. These FFMs may be used for benchmark testing and to support Government-led certification to ensure the MMUBA meets operational requirements.

The Contractor shall manage and comply with Government procedures for any GFE received in accordance with

FAR 52.245-1.

The Contractor’s procedures shall address the following, at a minimum:

a) Examination upon receipt, consistent with practicality, to detect damage in transit

b) Inspection for completeness, proper type and quantity

c) Methods for assurance of adequate storage conditions, proper handling, and protection from deterioration during storage

d) Testing, as required, to determine satisfactory operation

e) Identification and protection from improper use or disposition

These procedures shall be subject to review by the Government. The Contractor shall submit a GFE/GFI deficiency report (CDRL A011) for all deficiencies with regards to GFE/GFI.

CDRL: GFE Deficiency Report – A011

3.2.3.7 Government Acceptance Testing (GAT)

Government Acceptance Testing (GAT) for CLINs 3000, 4000, 5000, 6000, and 7000, if exercised, will consist of product inspections and functional checkouts. Failure will be defined as anything that prevents successful completion of the GAT (including, but not limited to: missing hardware, defective hardware, and test results not consistent with performance specifications). The Contractor shall provide support for GAT as needed.

CDRL: FAQT Plan and Procedures – A018 CDRL: FAQT Report – A019 CDRL: Factory Acceptance Testing (FAT) Report – A020

3.2.3.8 Spares (CLIN 1001, and, if exercised, CLINs 2002, 3001, 4001, 5001, 6001, and 7001) The Contractor shall provide recommendations on, and deliver, all Spares, Depot Spares and Installation and Check- Out (INCO) equipment and parts for the purposes of maintaining and supporting the procured systems throughout the base and option years. The Contractor shall provide recommendations for the initial and replenishment spares as necessary to support deployed operation, training, and maintenance of the systems. The Contractor shall provide the appropriate data and support needed to develop an initial spares list down to the Lowest Replaceable Unit (LRU) based on the approved maintenance concept that includes part number, nomenclature, cost, manufacturer, and quantity for each item.

Any changes to the configuration of the UBA that impact sparing must first be approved by the Government prior to delivery.

CDRL: Priced Bill of Materials (BOM) – A023

3.2.3.9 Consumables (CLIN 1002, and, if exercised, CLINs 2003, 3002, 4002, 5002, 6002, and 7002) The Contractor shall provide recommendations on, and deliver, all consumables for the purposes of maintaining and supporting the procured systems throughout the base and option years. A consumable is defined as an administrative or housekeeping item, not identified as a spare part, such as an O-ring, batteries or sensor that is used up or wear out regularly. For example, items in a 24M or 72M maintenance kit may be considered consumables. The Contractor shall provide recommendations for the initial and replenishment consumables as necessary to support deployed operation, training, and maintenance of the systems. Any changes to the configuration of the UBA that impact consumables must first be approved by the Government prior to delivery.

3.2.3.10 Peculiar Support Equipment (CLIN 1003, and, if exercised, CLINs 2004, 3003, and 4003) The Contractor shall support development, integration, operation, and maintenance of the program hardware by identifying and/or recommending hardware components such as common support equipment and peculiar support equipment. Peculiar Support Equipment changes that result from UBA configuration changes must be documented and approved through the processes in Paragraph 3.1.4 in this SOW.

CDRL: Priced Bill of Materials (BOM) – A023

3.2.3.11 Operations and Maintenance (O&M) Manuals (CLIN 1005, and, if exercised CLIN 3005) The Contractor shall provide a digital version of an O&M Manual (CDRL A024), desired with Government purpose rights, or better, to serve as the basis for training and corresponding supplemental data, including Quick Reference and Troubleshooting Guides.

CDRL: COTS Manuals and Associated Supplemental Data (O&M Manual) – A024

3.2.3.12 Training (CLIN 1004, and, if exercised 2001 and 3004) The Contractor shall provide classroom and in-water training sessions to Government personnel. Training courses shall be provided for up to 15 personnel per course. Training courses shall be performed at the NSWC PCD for EOD dive personnel. Training shall cover the setup, operation, and basic operator level maintenance of the MMUBA system, and shall be conducted with Government Production representative systems.

The Contractor shall:

a. Develop and deliver training curriculum and materials to train and certify personnel to operate and maintain the systems

b. Ensure safety, effectiveness and affordability of operational technology

c. Develop and maintain system maintenance and repair documentation and procedures

3.2.3.13 Depot Manuals (CLIN 1005)

The Contractor shall provide digital Depot Manuals (CDRL A025), desired with Government purpose rights, or better, to serve as the basis for repair, check out and QA Procedures and corresponding supplemental data, including a Quick Reference Guide (QRG).

CDRL: COTS Manuals and Associated Supplemental Data (Depot Manuals) – A025

3.3 Engineering Services (ES)

The Contractor shall provide ES when tasked via a Government issued Technical Instructions (TI) IAW C-242- H003 (NAVSEA) (OCT 2019) as approved by the Contracting Officer.

Any travel and incidental material requirements shall be billed as cost only under the respective ODC CLINs as stated in Section B of the contract. The Contractor shall provide a status of the following in the Contractor’s Progress, Status and Management Report:

Total cost expended by authorized TI Total hours…