N00024-21-R-6410.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 26 Jul 2021

X

A X B X C X D

EX

X

G F 101 - 130

131 - 169 X H 170 - 181 roy.williams@navy.mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

DO-A9 1 181

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N00024 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

Section L conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

ROY J WILLIAMS 202-781-3106

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 32

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

33 - 59 60 - 63

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

64 - 67 68 - 72

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 73 - 86 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 87 - 90 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

91 - 99

PART II - CONTRACT CLAUSES

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2060

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

24 Jun 2021

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N0002421R6410

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

CLIN

Number

Data

NOT SEPARATELY PRICED (NSP). This applies to ALL CLINs.

FOB: Destination

PSC CD: 4220

NET AMT

1 Lot

OPTION PIO

FFP

See Notes B and D.

7 Each

Certification Units

FFP

OPTION Spares

FFP

See Notes B and E.

OPTION Consumables

FFP

See Notes B and F.

OPTION Peculiar Support Equipment

FFP

See Notes B and G.

1 Set

OPTION Training

FFP

See Note B.

OPTION Operation & Maintenance, Depot Manuals

FFP

See Note B.

5,000 Hours

OPTION ES - Certification Support

CPFF

See Notes B and C.

FOB: Origin (Shipping Point)

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

OPTION ODC in Support of CLIN 1100

COST

See Note B.

2 Set

FFP

See Note B.

FFP

See Notes B and E.

FFP

See Notes B and F.

FFP

See Notes B and G.

5,000 Hours

OPTION ES - Certification Support

CPFF

See Notes B and C.

OPTION ODC in support of CLIN 2100

COST

See Note B.

120 Each

OPTION Full-Rate Production

FFP

See Notes A and B.

FFP

See Notes B and E.

FFP

See Notes B and F.

FFP

See Notes B and G.

1 Set

FFP

See Note B.

2 Each

OPTION Operation and Maintenance Manuals

FFP

See Note B.

5,326 Hours

OPTION ES - Engineering Services

CPFF

See Notes B and C.

5,326 Hours

OPTION ES - Sustainment Services

CPFF

See Notes B and C.

OPTION ODCs in Support of 3100 and 3101

COST

See Note B.

130 Each

FFP

See Notes A and B.

FFP

See Notes B and E.

FFP

See Notes B and F.

FFP

See Notes B and G.

8,218 Hours

CPFF

See Notes B and C.

8,218 Hours

CPFF

See Notes B and C.

OPTION ODCs in Support of 4100 and 4101

COST

See Note B.

65 Each

FFP

See Notes A and B.

FFP

See Notes B and E.

FFP

See Notes B and F.

9,665 Hours

CPFF

See Notes B and C.

9,665 Hours

CPFF

See Notes B and C.

OPTION ODCs in Support of 5100 and 5101

COST

See Note B.

80 Each

FFP

See Notes A and B.

FFP

See Notes B and E.

FFP

See Notes B and F.

11,444 Hours

CPFF

See Notes B and C.

11,444 Hours

CPFF

See Notes B and C.

OPTION ODCs in Support of 6100 and 6101

COST

See Note B.

73 Each

FFP

See Notes A and B.

FFP

See Notes B and E.

FFP

See Notes B and F.

13,069 Hours

CPFF

See Notes B and C.

13,069 Hours

CPFF

See Notes B and C.

OPTION ODCs in Support of 7100 and 7101

COST

See Note B.

NOTES

NOTE A - These CLINs consist of stepladder quantities.

The Government may unilaterally exercise a given CLIN more than once, prior to the latest option exercise date, identified in clause 52.217-7 (Section I, herein) for that CLIN and up to the total quantity listed. If an option CLIN is exercised more than once within sixty (60) days, the unit price for that CLIN shall be unilaterally modified to reflect the appropriate stepladder unit price for the entire quantity purchased for that CLIN. Exercising options will only result in quantity increase for given CLINs. The following hypothetical example illustrates how pricing will be adjusted if a given CLIN is unilaterally exercised more than once:

CLIN 9999

Step-ladder Quantity

Unit Price

1 - 75 $150 76 - 150 $120 151 - 225 $100

First exercise of option CLIN 9999: quantity of 150 at a unit price of $150 each for an extended price of $22,500 (=150*$150) funded on CLIN 9999.

Second exercise of option CLIN 9999: quantity of 200. The second exercised quantity of 200 plus the first exercised quantity of 150 equates to 350 in total for CLIN 9999.

The unit price for 350 units is $100, thereby making the extended total price $35,000 (=350*$100). Therefore, the unit price for CLIN 9999 would be unilaterally adjusted in accordance with Note A to reflect a quantity of 350 at a unit price of $100 with an extended price of $35,000.

For quantity increases not occurring within a 60-day period of when other quantities are exercised under the line item, the Government will use unit pricing from the stepladder pricing applicable to the quantity of hardware being added and the pricing of previous quantities under said line item shall not change.

STEPLADDER GUIDELINES

The stepladder quantities may range from the stated minimum quantities through the stated maximum quantities for each respective CLIN. The Maximum Number of Steps are provided for each CLIN and shall not be exceeded.

Offerors may propose fewer steps than the maximum number of steps provided. Offerors shall provide stepladder pricing in the “Stepladder Pricing Table” below. The Section B Firm-Fixed-Price (FFP) amount and the funding provided in each delivery order shall be unilaterally established based on the “Stepladder Pricing Table” for CLINs 3000, 4000, 5000, 6000, and 7000.

STEPLADDER PRICING TABLE (TO BE FILLED IN BY OFFEROR)

ITEM NO Step Number FROM QUANTITY TO QUANTITY UNIT PRICE

3000 1 1

6 120

4000 1 1

7 130

5000 1 1

3 65

6000 1 1

5 80

7000 1 1

4 73

NOTE B - Option item to which the option clause in SECTION I applies and which is to be supplied only if and to the extent said option is exercised.

NOTE C – Engineering and Sustainment Support Services For Cost-Plus-Fixed-Fee (CPFF) Engineering Support Services line items, The Contractor shall furnish Item (if Options are exercised) 1100, 2100, 3100, 3101, 4100, 4101, 5100, 5101, 6100, 6101, 7100, and 7101 in accordance with issued Technical Instructions (TI).

NOTE D – Provisioned Item Orders (PIO) (Applicable to CLIN 0901) 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. Periodically, Provisioned Items Orders (PIOs) may be placed against the PIO line item and the cost base thereof shall be negotiated by the parties to the contract prior to establishing Firm Fixed Price for each order. The profit percentage is hereby established to be ___% (to be filled in by Offeror), and shall be multiplied by the cost base (less FCCOM) at the establishment of each order. The Offeror shall not propose more than eight percent (8%) for profit.

NOTE E – Initial and Replenishment Spares Initial and Replenishment Spares Pricing Table are provided as Section J, Attachment 4. This attachment details the Firm Fixed Price pricing format corresponding to CLINs 1001, 2002, 3001, 4001, 5001, 6001, and 7001. Offerors shall submit a priced Section J, Attachment 4 with their proposal. The Government may unilaterally exercise this CLIN in whole or in part up to the maximum quantity specified.

NOTE F – Initial and Replenishment Consumables Initial and Replenishment Consumables Pricing Tables are provided as Section J, Attachment 5. This attachment details the Firm Fixed Price pricing format corresponding to CLINs 1002, 2003, 3002, 4002, 5002, 6002, and 7002.

Offerors shall submit a priced Section J, Attachment 5 with their proposal. The Government may unilaterally exercise this CLIN in whole or in part up to the maximum quantity specified.

NOTE G – Peculiar Support Equipment Peculiar Support Equipment Pricing Tables are provided as Section J, Attachment 6. This attachment details the Firm Fixed Price pricing format corresponding to CLINs 1003, 2003, 3003, and 4003. Offerors shall submit a priced Section J, Attachment 6 with their proposal. The Government may unilaterally exercise this CLIN in whole or in part up to the maximum quantity specified.

CLAUSES INCORPORATED BY FULL TEXT

B-215-H002 REFUNDS (SPARES AND SUPPORT EQUIPMENT) (NAVSEA) (OCT 2018)

(a) In the event that the price of a spare part or item of support equipment delivered under this contract significantly exceeds its intrinsic value, the Contractor agrees to refund the difference. Refunds will not be made to recoup the amount of cost decreases that occur over time due to productivity gains (excluding economic purchase quantity considerations) or changes in market conditions.

(b) For purposes of this requirement, the intrinsic value of an item is defined as follows:

(1) If the item is one which is sold or is substantially similar or functionally equivalent to one that is sold in substantial quantities to the general public, intrinsic value is the established catalog or market price, plus the value of any unique requirements, including delivery terms, inspection, packaging, or labeling.

(2) If there is no comparable item sold in substantial quantities to the general public, intrinsic value is defined as the price an individual would expect to pay for the item based upon an economic purchase quantity as defined in FAR 52.207-4, plus the value of any unique requirements, including delivery terms, inspection, packaging or labeling.

(c) At any time up to two years after delivery of a spare part or item of support equipment, the Contracting Officer may notify the Contractor that based on all information available at the time of the notice, the price of the part or item apparently exceeds its intrinsic value.

(d) If notified in accordance with paragraph (c) above, the Contractor agrees to enter into good faith negotiations with the Government to determine if, and in what amount, the Government is entitled to a refund.

(e) If agreement pursuant to paragraph (d) above cannot be reached, and the Navy's return of the new or unused item to the Contractor is practical, the Navy, subject to the Contractor's agreement, may elect to return the item to the Contractor.

Upon return of the item to its original point of Government acceptance, the Contractor shall refund in full the price paid.

If no agreement pursuant to paragraph (d) above is reached, and return of the item by the Navy is impractical, the Contracting Officer may, with the approval of the Head of the Contracting Activity, issue a Contracting Officer's final decision on the matter, subject to Contractor appeal as provided in the "Disputes" clause (FAR 52.233-1).

(f) The Contractor shall make refunds, as required under this requirement, in accordance with instructions from the Contracting Officer.

(g) The Contractor shall not be liable for a refund if the Contractor advised the Contracting Officer in a timely manner that the price it would propose for a spare part or item of support equipment exceeded its intrinsic value, and with such advice, specified the estimated proposed price, the estimated intrinsic value and known alternative sources or item, if any, that can meet the requirement.

(h) This requirement does not apply to any spare parts or items of support equipment whose price is determined through adequate price competition. This requirement also does not apply to any spare part or item of support equipment if the Contractor submitted, and certified the currency, accuracy and completeness of, cost or pricing data applicable to the item.

(End of text)

B-216-H006 FEE TABLE (NAVSEA) (MAR 2019)

FEE SCHEDULE FOR LOE ITEMS FEE SHCEDULE FOR LEVEL OF EFFORT ITEMS

ITEM

(1)

HOURS

(2)

ESTIMATED

COST

(EC)*

(3)

EC

HOURLY

RATE

=(2)/(1)*

(4)

FIXED

FEE

(FF)*

(5)

FF

HOURLY

RATE

=(4)/(1)*

HOURLY

EC+FF

=(3)+(5)*

EXTENDED

EC+FF

=(2)+(4)*

1100 5,000

2100 5,000

3100 5,326

3101 5,326

4100 8,218 4101 8,218 5100 9,665

5101 9,665

6100 11,444

6101 11,444

7100 13,069 7101 13,069

*The offeror shall divide the proposed fee for each CLIN by the quantity of labor hours indicated to complete the table. Fee is calculated based on cost less FCCOM; if FCCOM is proposed, necessary columns may be added.

In the event of any inconsistency between the above table and the CLIN pricing, the CLIN pricing shall take precedence.

B-231-H001 TRAVEL COSTS (NAVSEA) (OCT 2018)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its actual travel costs in accordance with FAR 31.205-46. The travel costs to be reimbursed shall be those costs for which the Contractor has maintained appropriate documentation and which have been determined to be allowable, allocable, and reasonable by the Procuring Contracting Officer, Administrative Contracting Officer, or their duly authorized representative.

(b) Reimbursable travel costs include only that travel performed from the Contractor's facility to the worksite, in and around the worksite, and from the worksite to the Contractor's facility.

(c) Relocation costs and travel costs incidental to relocation are allowable to the extent provided in FAR 31.205-35;

however, Procuring Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incidental to relocation.

(d) The Contractor shall not be reimbursed for the following daily local travel costs:

(i) travel at U.S. Military Installations where Government transportation is available,

(ii) travel performed for personal convenience/errands, including commuting to and from work, and

(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the Contractor's or employee's convenience.

B-232-H005 PAYMENTS OF FEE(S) (LEVEL OF EFFORT)--ALTERNATE I (NAVSEA) (OCT 2018)

(a) For purposes of this contract, "fee" means "target fee" in cost-plus-incentive-fee type contracts, "base fee" in cost-plus-award-fee type contracts, or "fixed fee" in cost-plus-fixed-fee type contracts.

(b) The Government shall make payments to the Contractor, subject to and per the clause in this contract entitled "Fixed Fee" (FAR 52.216-8) or "Incentive Fee", (FAR 52.216-10), as applicable. Such payments shall be submitted by and payable to the Contractor pursuant to the clause of this contract entitled "Allowable Cost and Payment" (FAR 52.216-7), subject to the withholding terms and conditions of the "Fixed Fee" or "Incentive Fee" clause, as applicable. Fee paid per hour shall be based on total fee dollars divided by total hours to be provided. Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract.

Applicable CLINs: 1100, 1101, 2100, 2101, 3100, 3101, 4100, 4101, 4102, 5100, 5101, 5102, 6100, 6101, 6102, 7100, 7101, 7102

B-232-H006 LIMITATION OF COST OR LIMITATION OF FUNDS CLARIFICATION (NAVSEA) (OCT 2018)

The clause entitled "Limitation of Cost" (FAR 52.232-20) or "Limitation of Funds" (FAR 52.232-22), as appropriate, shall apply separately and independently to each separately identified estimated cost.

Section C - Descriptions and Specifications

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