v3_RFP_Generated_12-2-2014_withtrackchanges_1-16-2015.pdf

As of 1/16/2015 proposals are due by Noon on Thursday 2/19/2015.

N00024-15-R-5226

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

CLIN

Number

1 Lot

ISM Design (PDR)

CPIF

The Contractor shall complete all the tasks necessary to achieve a successful

Preliminary Design Review (PDR) for surface and submarine Inertial Sensor

Modules (ISM) in accordance with (IAW) para 3.2.14.1 of the Statement of

Work (SOW)

Share Ratio is 50/50 for underruns and overruns

See Note C

FOB: Origin

PURCHASE REQUEST NUMBER: N0002414NR46042

TARGET COST

TARGET FEE

TOTAL TGT COST + FEE

MINIMUM FEE

MAXIMUM FEE

SHARE RATIO ABOVE TARGET

SHARE RATIO BELOW TARGET

37 Unit

EDM Build (Surface)

CPIF

The Contractor shall build and deliver seven (7)three (3) surface ISM EDMs, to include both the hardware and the software as separate elements, IAW the SOW

3.2.6.1

Share ratio is 50/50 for underruns and overruns

See Note C

3 Unit

EDM Build (Submarine)

CPIF

The Contractor shall build and deliver three (3) submarine ISM EDMs, to include both the hardware and software as separate elements, IAW the SOW

3.2.6.1

See Note C

Data

Data Items for CLINs 0001, 0002, 0003 and if Option(s) exercised CLINs 0006, 0007, 0008, 0010, 1001, 1002, 1003, 1006, 1008, 2001, 2002, 2003, 2006, 2008, 3002, 3003, 3008, 4002, 4003, and 4008

FOB: Destination

Travel/ODCs

COST

The Contractor shall provide Travel and Other Direct Costs (ODCs) in support of

CLIN(s) 0001, 0002, 0003, and if Option(s) exercised CLINs 0006, 0007, and

0008 and 0010

ESTIMATED COST

OPTION ISM Design (CDR) (Surface)

CPIF

The Contractor shall complete all the tasks necessary to achieve a successful

Critical Design Review (CDR) IAW paragraph 3.2.14.2 of the SOW

Share Ratio is 50/50 for underruns and overruns

See Notes B and C

OPTION ISM Design (CDR) (Submarine)

CPIF

The Contractor shall complete all the tasks necessary to achieve a successful

CDR IAW paragraph 3.2.14.2 of the SOW

Share Ratio is 50/50 for underruns and overruns

See Notes B and C

2,500 Hours

OPTION Engineering Support Services (ESS) Yr 1

The Contractor shall provide ESS IAW the SOW paragraph 3.4 and as directed by Technical Instruction(s) (TIs)

See Notes B and C

CPFF

FIXED FEE

TOTAL EST COST + FEE

Data Rights

FFP

OPTION For those rights the Contractor is willing to sell, the Contractor shall provide an option price for acquiring Data Rights for Technical Data (TD), Computer Software (CS) and

Computer Software Documentation (CSD) in the event Government Purpose Rights are not provided by the Contractor at no cost to the Government and will require a separate contract action to acquire said rights. This includes all Contract Data Requirements Lists

(CDRL) and data required for installation, operation, maintenance, production, and training purposes.

See Note B

NET AMT

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE

CLIN Number

4 Unit

OPTION EDM Build (Surface)

CPIF

The Contractor shall build and deliver four (4) surface ISM EDMs, to include both the hardware and the software as separate elements, IAW the SOW 3.2.6.1

Share ratio is 50/50 for underruns and overruns

See Note C

MAXIMUM FEE

OPTION ISM Testing

CPIF

The Contractor shall provide Testing including Test Readiness Review (TRR)

IAW the SOW paragraphs 3.2.3.4, 3.2.7, and 3.2.14.3

4 Unit

OPTION PPUs (Surface)

CPIF

The Contractor shall build and deliver four surface PPUs IAW the SOW paragraph 3.2.6.2

Share Ratio is 50/50 for underruns and overruns

See Notes B and C

6 Unit

OPTION PPUs (Submarine)

CPIF

The Contractor shall produce six (6) submarine PPUs IAW SOW paragraph

3.2.6.2

Share Ratio is 50/50 for underruns and overruns

See Notes B and C

OPTION RESERVED

OPTION Travel/ODCs

COST

The Contractor shall provide Travel and ODCs in support of CLIN(s) 1001, 1002, 1003, 1006, and 1008

See Note B

OPTION Modeling & Simulation (M&S)

Modeling & Simulation IAW SOW paragraph 3.2.7.2 and 3.2.7.2.1

4,000 Hours

OPTION Engineering Support Services (ESS) Yr 2

The Contractor shall provide ESS IAW SOW paragraph 3.4 and as directed by

Technical Instructions (TIs)

See Notes B and C

FOB: Destination

OPTION Production Readiness Review (PRR)

CPIF

The Contractor shall complete all the tasks necessary to achieve a successful

PRR IAW SOW para 3.2.14.4

OPTION LRIP (Surface)

CPIF

Low-Rate-Initial-Production (LRIP)

The Contractor shall produce four (4) surface LRIP units

Share Ratio is 50/50 for underruns and overruns

See Notes B and C

FOB: DestinationOrigin

OPTION LRIP (Submarine)

CPIF

The Contractor shall produce four (4) submarine LRIP units

Share Ratio is 50/50 for underruns and overruns

See Notes B and C

FOB: DestinationOrigin

COST

The Contractor shall provide Travel and ODCs in support of CLIN(s) 2008

See Note B

OPTION Modeling & Simulation (M&S)

Modeling & Simulation IAW SOW paragraphs 3.2.7.2 and 3.2.7.2.1

See Notes B and C

FOB: Destination

Provisioned Items Order (PIO)

OPTION See Notes B and C

2,500 Hours

OPTION Engineering Support Services (ESS) Yr 3

The Contractor shall provide ESS IAW the SOW paragraph 3.4 and as directed by Technical Instructions (TIs)

See Notes B and C

FOB: Destination

Depot Spares

2 Set

OPTION The Contractor shall procure two (2) sets of Depot Spares for the surface ISM

See notes A and B

Depot Spares (Submarine)

OPTION The Contractor shall produce two (2) sets of Depot Spares for the submarine ISM

See Notes A and B

INCO Spares (Surface)

1 Set

OPTION The Contractor shall produce one set of Installation and Checkout (INCO) spares for the surface ISM

INCO Spares (Submarine)

OPTION The Contractor shall produce one set of INCO spares for the submarine ISM

See Notes A and B

OBRP Spares (Surface)

OPTION The Contractor shall produce one set of On Board Repair Parts (OBRP) spares for the surface ISM

OBRP Spares (Submarine)

OPTION The Contractor shall produce one set of OBRP spares for the submarine ISM

See Notes A and B

OPTION Reserved

OPTION Production (Surface)

FPI

The Contractor shall produce four (4) surface LRIP units

Share Ratio is 50/50 for underruns and overruns

See Notes B and C

TARGET PROFIT

TOTAL TARGET PRICE

CEILING PRICE

Number

OPTION

4 Unit

Production (Submarine)

FPI

The Contractor shall produce four (4) submarine LRIP production units

Share Ratio is 50/50 for underruns and overruns

See Notes B and C

TOTAL TARGET PRICE

CEILING PRICE

COST

The Contractor shall provide Travel and ODCs in support of CLIN 3008

See Note B

Number

OPTION

2,500 Hours

Engineering Support Services (ESS) Yr 4

The Contractor shall provide ESS IAW the SOW paragraph 3.4 and as directed by Technical Instructions (TIs)

See Notes B and C

FOB: Destination

Depot Spares (Surface)

OPTION The Contractor shall produce two sets of Depot spares for the surface ISM

See Notes A and B

OPTION The Contractor shall produce two sets of Depot spares for the submarine ISM

OPTION The Contractor shall produce one set of INCO spares for the surface ISM

See Notes A and B

See Notes A and B

OPTION The Contractor shall produce one set of OBRP spares for the surface ISM

See Notes A and B

OBRP (Submarine)

OPTION The Contractor shall produce one set of OBRP spares for the submarine ISM

See Notes A and B

OPTION Production (Surface)

FPI

The Contractor shall deliver four (4) surface production units

See Notes B and C

TOTAL TARGET PRICE

CEILING PRICE

OPTION Production (Submarine)

FPI

The Contractor shall deliver four (4) submarine production units

See Notes B and C

TOTAL TARGET PRICE

CEILING PRICE

COST

The Contractor shall provide Travel and ODCs in support of CLIN 4008

See Note B

COST

1,500 Hours

OPTION Engineering Support Services (ESS) Yr 5

The Contractor shall provide ESS IAW the SOW paragraph 3.4 and as directed by Technical Instructions (TIs)

See Notes B and C

FOB: Destination

Depot Spares (Surface)

OPTION The Contractor shall produce two sets of Depot spares for the surface ISM

See Notes A and B

OPTION The Contractor shall produce two sets of Depot spares for the submarine ISM

See Notes A and B

OPTION The Contractor shall produce one set of INCO spares for the surface ISM

See Notes A and B

See Notes A and B

OPTION The Contractor shall produce one set of OBRP spares for the surface ISM

OBRP Spares (Submarine)

OPTION The Contractor shall produce one set of OBRP Spares for the submarine ISM

See Notes A and B

HQ B-2-0001

NOTE A - The CLINs are unpriced at award. Following delivery of the TDP the spares list will be finalized and priced. Section B prices will be established prior to option exercise.

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- Applicable to Cost Plus Incentive Fee (CPIF) the minimum fee is 0% and the maximum fee is ten percent (10%). The Offeror shall fill in their Target Fee of 8% and Maximum Fee (0-10%) within this range. The share ratio for the CPIF portion of the fee structure is 50/50 (50% Government, 50% Contractor) for overruns and underruns.

Applicable to Cost Plus Fixed Fee (CPFF) Items the Offeror shall propose no more than eight percent (8%) for fixed fee. The available fixed fee amount shall be calculated as a percentage of the cost, less Facilities Capital Cost of

Money.

Applicable to Fixed Price Incentive Firm Target (FPIF) (if option is exercised) – The maximum profit is twelve and a half percent (12.5%) of the Target Cost. The Offeror shall fill in their target profit (0-12.5%) within this range. The share ratio is 50/50 above and below Target Cost. The Government share under Target Cost is fifty percent (50%).

The Government share above Target Cost to Ceiling is fifty percent (50%). The Ceiling is established at 120% of

Target Cost.

CLAUSES INCORPORATED BY FULL TEXT

HQ B-2-0004 EXPEDITING CONTRACT CLOSEOUT (NAVSEA) (DEC 1995)

(a) As part of the negotiated fixed price or total estimated amount of this contact, both the Government and the

Contractor have agreed to waive any entitlement that otherwise might accrue to either party in any residual dollar amount of $500 or less at the time of final contract closeout. The term “residual dollar amount” shall include all money that would otherwise be owed to either party at the end of the contract, except that, amounts connected in any way with taxation, allegations of fraud and/or antitrust violations shall be excluded. For purposes of determining residual dollar amounts, offsets of money owed by one party against money that would otherwise be paid by that party may be considered to the extent permitted by law.

(b) This agreement to waive entitlement to residual dollar amounts has been considered by both parties. It is agreed that the administrative costs for either party associated with collecting such small dollar amounts could exceed the amount to be recovered.

HQ B-2-0007 LIMITATION OF COST/LIMITATION OF FUNDS (NAVSEA) (SEP 1990)

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.

HQ B-2-0012 PAYMENT FOR ENGINEERING SERVICES AND SUPPORT (NAVSEA) (JAN 2008)

(APPLICABLE TO CLINS 0008, 1008, 2008, 3008, AND 4008)

(a) Invoices for engineering services and overtime shall contain the name(s) of engineer(s), date(s) and place(s) of performance, and a brief description of the services performed. This information may be included in the Comments tab of the applicable WAWF document. Each invoice shall be accompanied by a copy of the authorization for services and the original certification of performance. These documents may be attached to the invoice as described in the Invoice Instructions in Section G. A copy of each invoice shall be furnished to the applicable

NAVSEA/DRPM/PEO code identified in Section C under Engineering Services.

(b) Invoices for subsistence and transportation shall be supported by a statement of actual costs incurred by the

Contractor and claimed to be reimbursable and shall be in such form and reasonable detail as required by the cognizant

Defense Contract Audit Agency (DCAA). The Government shall make provisional payment after submission of each invoice and statement of costs. At any time prior to final payment, DCAA may audit the invoice(s) and statement(s) of costs, as appropriate.

(c) Each provisional payment for subsistence and transportation costs shall be subject to reduction to the extent any amount included in the related invoice and statement of costs is found not to be reimbursable under the support item(s) and shall also be subject to reduction for overpayment or to increase for underpayment on preceding invoices. Any disputes under this requirement shall be determined in accordance with the clause of this contract entitled "DISPUTES"

(FAR 52.233-1).

HQ B-2-0014 PAYMENTS OF FEE (S) (COMPLETION) (NAVSEA) (MAY 1993) (Applicable to CLINs 0001, 0002, 0003, 0006, 0007, 1001, 1002, 1003, 1006, 2001, 2002, 2003, 2006, 3002, 3003, 4002, and 4003)

(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, "fixed fee" in cost-plus-fixed-fee type contracts for completion and phase type contracts.

(b) The Government shall make payments to the Contractor, subject to and in accordance with 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 equal to * percent (*%) of the allowable cost of each invoice 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 (percentage of fee is based on fee dollars divided by estimated cost dollars, including facilities capital cost of money). Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract.

(c) In the event of discontinuance of the work under this contract, or any specified phase of the contract, in accordance with the clause of this contract entitled "LIMITATION OF FUNDS" (FAR 52.232-22) or

"LIMITATION OF COST" (FAR 52.232-20), as applicable, the fee shall be equitably adjusted by mutual agreement to reflect the diminution of work. If the adjusted fee is less than the sum of all fee payments made to the Contractor under this contract, the Contractor shall repay the excess amount to the Government. If the adjusted fee exceeds all payments made to the Contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract at the time of the discontinuance of work.

(d) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) in accordance with paragraph (c) above, or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.

(*To be filled in by the Government at award in accordance with the Offeror’s proposed Section B)

HQ B-2-0015 PAYMENT OF FEES(S) (LEVEL OF EFFORT – ALTERNATE I) (NAVSEA) (MAY 2010)

(Applicable CLINs 0008, 1008, 2008, 3008, and 4008)

(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 for level of effort type contracts.

(b) The Government shall make payments to the Contractor, subject to and in accordance with 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, and shall be paid at the hourly rate(s) specified above per man-hour performed and invoiced. 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.

HQ B-2-0017 REFUNDS (SPARES AND SUPPORT EQUIPMENT) (NAVSEA) (SEP 1990)

(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 only be made for the difference between the intrinsic value of the item at the time an agreement on price was reached and the contract price. Refunds will not be made to recoup the amount of cost decreases that occur over time due to productivity gains (beyond 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 will 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 with a unit price in excess of $100,000; or in excess of $25,000 if the Contractor submitted, and certified the currency, accuracy and completeness of, cost or pricing data applicable to the item.

HQ B-2-0020 TRAVEL COSTS - ALTERNATE I (NAVSEA) (DEC 2005) (APPLICABLE TO CLINS 0005, 1005, 2005, 3005, AND 4005)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its reasonable actual travel costs in accordance with FAR 31.205-46. The costs to be reimbursed shall be those costs accepted by the cognizant DCAA.

(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 incident to relocation are allowable to the extent provided in FAR 31.205-35;

however, Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incident 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.

HQ B-2-0023 CONTRACT SUMMARY FOR PAYMENT OFFICE (COST/FIXED PRICE) (FEB 1997)

This contract includes the following mixture of cost reimbursement and fixed price line items:

Item Type

0001 / 0002 / 0003 / 0006 /

0007 / 0010/1001 / 1002 / 1003 /

2001 / 2002 / 2003 / CPIF

0005 / 1005 / 2005 / 3005 /

4005 COST

0008 / 1006 / 1008 / 2006 / 2008

3008 / 4008 CPFF

0009 / 2007 / 2009-2014 / 3009-3014 /

4009-4014 FFP

3002 / 3003 4002 / 4003 FPIF

Section C - Descriptions and Specifications

SECTION C

Section C - Descriptions and Specifications

SECTION C

Section C: Descriptions and Specification

1.0 SCOPE

This Statement of Work (SOW) defines the effort required for the design, engineering, fabrication, test and production of an Inertial Sensor Module (ISM) for Surface and Submarine Platforms, which is a major component of a new inertial navigator, herein referred to as the Inertial Navigation System – Replacement (INS-R). Major milestones of this effort are successful completion of the Systems Engineering Technical Review (SETR) events as defined in Para. 3.2.14.

The scope shall include provision of Engineering Development Models (EDM), Pre-Production Units (PPU), Low

Rate Initial Production (LRIP), and two years of Full Rate Production. ISM EDMs, PPUs, LRIPs, and Production

Systems shall be designed, engineered, fabricated and tested to satisfy the requirements of this SOW. The final design shall be able to transition to production and shall be producible with minimal design changes. ISM integration with the Navigation Processing Module (NPM) and final system acceptance testing will be conducted by the Government Technical Design Agent (TDA). The requirements for associated program management, human engineering, and logistics support are also included in this SOW.

1.1 Background

The U.S. Navy, Program Executive Office Integrated Warfare Systems Command and Control Directorate (PEO

IWS 6.0), has initiated an effort to develop the INS-R to replace the aging AN/WSN-7/7A Ring Laser Gyro

Navigation (RLGN) system. The INS-R will provide improved real-time navigation performance and enhanced operational capability to meet current Navy navigation requirements as well as to allow future requirement/technological growth potential. An INS-R ship set will consist of dual redundant (two) Navigator Units

(NU) which will operate independently of each other. The redundant NUs are necessary to satisfy the INS-R

Operational Availability (Ao) requirement of 99%, as stated in the ISM Technical Requirements Document (TRD).

Per Figures 1.1 and 1.2 of the ISM TRD, provided as Government Furnished Information (GFI), each NU will contain an ISM and a NPM. The NPM is currently being developed by the U.S. Navy. Differences between the surface and submarine configurations are detailed in the ISM TRD.

2.0 APPLICABLE DOCUMENTS

The following specifications, standards, and handbooks form a part of this SOW to the extent cited herein. Unless otherwise specified, the latest version of Government documents listed in the Department of Defense Index of

Specifications and Standards (DoDISS) on the date of the solicitation associated with this SOW shall be applicable.

Non-Government standards listed are those in effect on the issue date of the solicitation associated with this SOW.

2.1 Military Specifications, Standards and Handbooks

MIL-STD-31000A Detail Specification, Technical Data Packages, 26 Feb 2013

MIL-HDBK-470A NOT 2

Design and Develop Maintainable Products and Systems, 31 May 2012

MIL-HDBK-781A

Reliability Test Methods, Plans, and Environments for Engineering

Development, Qualification, and Production, 01 Apr 1996

MIL-HDBK-1785 NOT 1

System Security Program Management requirements, 22 Apr 2014

MIL-STD-881C

Work Breakdown Structures for Defense Materiel Items, 03 Oct 2011

MIL-HDBK-29612-1A

NOT 2

Guidance for Acquisition of Training Data Products and Services (Part 1 of

5 Parts), 20 Jun 2011

MIL- PRF-29612B NOT 2

Performance Specification, Training Data Products, 20 Jun 2011

MIL-STD-129R DoD Standard for Military Marking for Shipment and Storage, 18 February

MIL-STD-130N Change 1 DoD Standard Practice for Identification Marking of U.S. Military

Property, 16 Nov 2012

MIL-STD-461F Requirements for the Control of Electromagnetic Interference Emissions &

Susceptibility, including notices, 10 Dec 2007

MIL-STD-882E DoD Standard Practice for System Safety, 11 May 2012

MIL-STD-167-1A Mechanical Vibrations of Shipboard Equipment

MIL-S-901D Shock Tests H. I. (High-Impact) Shipboard Machinery, Equipment, and

Systems, Requirements

EIA 649B National Consensus Standard for Configuration Management, 17 Jun 2011

GEIA-STD-0007 Logistics Product Data, 15 Oct 2008

MIL-STD-1472G Human Engineering, 10 Jan 2012

MIL-STD-2073-1E(1) DoD Standard Practice for Military Packaging, change notice, 07Jan 2011

MIL-STD-40051-2B DoD Standard Practice Preparation of Digital Technical Information for

Page-Based Technical Manuals (TIMs), 30 Nov 2012

MIL-HDBK-61A Configuration Management Guidance, 08 Sept 2014

MIL-STD-3034-NOT 1 Reliability-Centered Maintenance (RCM) Process, 22 Jun 2011

MIL-HDBK-502A

(Appendix C)

Product Support Analysis, 30 May 1997

MIL-STD-3022-1 Verification, Validation, and Accreditation (VV&A) Plan

2.1.2 Joint Chiefs of Staff, Department of Defense and DoD Services Documents

DoD 4120.24 M Defense Standardization Program (DSP) Policies and Procedures, 09 Mar

DoDI 5200.39, CH 1 Mandatory Procedures for Research & Technology Protection with the

DoD, 28 Dec 2010

DoD MCTL Military Critical Technologies List

DoD Guidance Modeling and Simulation Guidance for the Acquisition Workforce, Version 1.0.1, Oct 2008

DoDI 5000.02 Interim Operation of the Defense Acquisition System, 25 Nov 2013

DoD 5220.22M, CH 1 National Industrial Security Program Operating Manual, 28 Mar 2013

DoDI 8500.01 Cybersecurity, 14 Mar 2014

DoDI 8510.01 Risk Management Framework (RMF) for DOD Information Technology

(IT), 12 March 2014

DoDD 8570.01-M Information Assurance Workforce Improvement Program, 24 Jan 2012

DISA STIG Defense Information Systems Agency (DISA) Security Technical

Implementation Guides (STIG)

Directive-Type Memorandum

(DTM) 08-027

Security of Unclassified DoD Information on Non-DoD Information

Systems, 16 Sep 2010

SECNAVINST 4440.34 Implementation of Item Unique Identification within the Department of the Navy, 22 Dec 2009

OPNAVINST 1500.76C Naval Training Systems Requirements, Acquisition, and Management, 14 Aug 2013

OPNAVINST 5513.1F Department of the Navy Security Classification Guides, 07 Dec 2005

OPNAV N6/N7 Letter Requirement for Open Architecture (OA) Implementation, 23 Dec 2005

PEO IWS6 CMP Configuration Management Plan, 29 Apr 2013

PEO IWS6 RMP Risk Management Plan, Revision 3, Jan 2011

PEO IWS6 DMSMS Diminishing Manufacturing Sources and Material Shortages (DMSMS)

Management Plan, 08 Nov 2012

PEO IWS6 IUID Item Unique Identification (IUID) Implementation Plan, 05 Mar 2013

NAVSEA TRM Program Executive Office for Integrated Warfare Systems (PEO

IWS)/Naval Sea Systems Command Research & System Engineering

Warfare Systems (SEA 05) Technical Review Manual (TRM), Version 2

(Dated December 2009)

DMSMS Diminishing Manufacturing Sources and Material Shortages (DMSMS)

Program Management Plans and Metrics, dated 12 Apr 05

DMSMS The Program Manager’s Handbook – Common Practices to Mitigate the

Risk of Obsolescence (available online at http://www.dmea.osd.mil)

PEO IWS6 CAG PEO IWS6 Configuration Audit Guide

2.1.3 Non-Government and Commercial Standards, Specifications and other applicable publications

ASTM F1166 Standard Practice for Human Engineering Design for Marine Systems, Equipment, and Facilities, 15 Aug 1994

AR 700-15 Packaging Of Materiel, 12 Jan 2004

ASME Y14.24M Types and Applications of Engineering Drawings

CMMI-SE/SW/IPPD/SS Capability Maturity Model Integration (CMMISM) for Systems Engineering, Software Engineering, Integrated Product and Process Development, and

Supplier Sourcing, 10 Mar 2002

EIA-649B Engineering Change Proposals

GEIA STD-0007 Logistics Product Data

IEEE 1220-2005 IEEE Standard for Application and Management of the Systems Engineering

Process, 09 Sept 2005

IEEE/EIA 12207-2008 IEEE Systems and Software Engineering - Software Life Cycle Processes

IEEE STD 1016-2009 IEEE Standard for IT Systems Design Software Design Description, 19 Mar

ISO/IEC-15288 Systems Engineering- System Life Cycle Processes, 01 May 2003

ISO 9000 & 9001 Quality Management Systems, 17 Apr 2001

ISO 10007:2003 Quality Management - Guidelines for Configuration Management

NAS 411 National Aerospace Standard (NAS) 411, Hazardous Materials Management

Program

ANSI/EIA-748-B Earned Value Management Systems (EVMS), 01 Jun 2007

NSTISSAM

TEMPEST/1/92

Compromising Emanations Laboratory Test Requirements, Electromagnetics

SAE AS5553 Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, &

Disposition

OAAT Open Architecture assessment(s), using the Open Architecture Assessment

Tool (OAAT) version 3.0

Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available on the internet at the Department of Defense Single Stock Point (DoDSSP) at https://assist.dla.mil. DoD Directives, Instructions and Publications documents, as well as other services publications at DoD Issuances website at:

http://www.dtic.mil/whs/directives/. Non-Government documents should be obtained from the commercial sources.

Requests for copies of documents not available from sources listed above should be directed to the Procuring

Contracting Officer (PCO).

It is the intent of this solicitation and the resulting contract to fully implement the principles of the Department of

Defense (DoD) Acquisition Reform initiatives. Specifically, reference is made to the Secretary of Defense policy promulgated by memorandum on 29 June 1994 regarding the use of specifications and standards. When specifications are not practical, non-Government (industry developed) standards shall be used.

The Contractor shall use the revision effective as of the date of contract award for each of the documents listed in the following subparagraphs and to the extent specified in the requirements of this SOW. Nothing in this document however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

In the event of conflict between the documents referenced herein and the contents of this SOW, the order of precedence shall be:

1) Section 3 of this SOW;

2) INS-R Related Documentation listed in Section 2.2 of this SOW;

3) Specifications, Standards and Other Documents, listed in Section 2.1 of this SOW.

2.2 INS-R Related Documentation

TRD for the INS-R ISM for Surface Ships and Submarines, Version 4.5, dated 19 December 2013.

Interface Requirements Specification (IRS) for the INS-R NPM to ISM, Version 2.3, dated 19 December 2013.

Inertial Navigation System – Replacement Preliminary Installation Control Drawings (ICD), 31 January 2013.

Installation Control Drawings (ICDs): Inertial Navigation System Replacement (INS-R) USN Submarine Platforms

Final Release (Rev -) dated 27 June 2014

3.0 REQUIREMENTS

3.1 General

The Contractor shall perform this effort in accordance with this SOW and shall satisfy the requirements of the ISM

TRD and the NPM to ISM IRS. As a part of the overall effort, the Contractor shall host, participate in, and pass formal Systems Engineering Technical Reviews (SETRs) as defined in paragraphs 3.2.14 of this SOW, and in the

Program Executive Office for Integrated Warfare Systems (PEO IWS)/Naval Sea Systems Command Research &

System Engineering Warfare Systems (SEA 05) Technical Review Manual (TRM), Version 2 provided as GFI.

Entry into these reviews is predicated upon the Contractor satisfying the particular SETR Entrance Criteria. The required SETRs are:

Preliminary Design Review (PDR), chaired by the Government

Critical Design Review (CDR), chaired by the Government

Test Readiness Review (TRR), chaired by the Government

Production Readiness Review (PRR), chaired by the Government (not in the TRM)

The Contractor shall conduct a series of design disclosure meetings prior to the PDR and CDRs. These meetings shall address the engineering material and documentation sufficient to convey a detailed understanding to the

Government Technical Review Team (TRT), and to complete comment adjudication activities.

3.2 Detailed Tasks

3.2.1 Design and Engineering (CLINs 0001-0003, 0006-0007, 1001-1003, 1006, 2001-2003, 2006, 3002-3003, 4002-4003)

The Contractor shall provide an ISM hardware design or designs that meet both surface and submarine requirements. The ISM hardware design consists of an Inertial Measurement Unit (IMU), IMU support electronics, control panel, and appropriate interfaces that shall be housed in a single cabinet containing a shock isolation system.

The Contractor shall ensure the ISM design(s) will pass Environmental Qualification Testing (EQT), including

Grade A shock, vibration, temperature, humidity and Electromagnetic Interference (EMI). For surface application, the Contractor shall design the ISM cabinet such that it shall be deck mounted in accordance with the INS-R

Preliminary ICDs (provided as GFI) with the NPM cabinet mounted on top. The NPM estimated weight and dimension information is provided as GFI. For the submarine application, the Contractor shall design the ISM cabinet such that it shall be mounted in the overhead separately from the NPM, in accordance with ICD: RLGN

USN Submarine Platforms (provided as GFI),. Separate cabinet designs for surface and submarine platforms are acceptable; however, the IMUs shall be designed to be identical. The Contractor shall design and develop the software required for ISM IMU control, processing ISM IMU data, processing external sensor aiding inputs and any associated diagnostics as defined in the TRD. The software shall be designed to be hosted on the NPM processor(s) that reside in the NPM. The software shall provide the required ISM IMU control, processing of ISM IMU data, external sensor aiding inputs and any associated diagnostics between the ISM and NPM via the IRS.

The Contractor shall make maximum use of Commercial Off the Shelf (COTS) and Non-Developmental Items

(NDI), modified as necessary, to meet the requirements of this SOW.

Unclassified and Classified ISNR Technical Requirements and documentation are ITAR controlled, restricted by the

Arms Export Control Act (Title 22, U.S.C., SEC.2751 et seq.) or the Export Administration Act of 1979 as amended

(Title 50, U.S.C., APP.2401, ET. SEQ.). All ISNR Technical Requirements documentation are Distribution F. Items produced by foreign sources shall be able to meet the ISM requirements without requiring export of technical data and/or additional development by the foreign source Unauthorized export of technical data is prohibited. Violators will be prosecuted to the full extent of the law. The Contractor, and any subcontractors or supplier, shall also comply with all requirements set forth in the DD-254.The Contractor’s performance of this contract shall be in compliance with the Buy American Act and the Berry Amendment.

3.2.2 Design Analysis (CLINs 0001-0003, 0006-0007, 1001-1003, 1006, 2001-2003, 2006, 3002-3003, 4002-

4003)

The Contractor shall conduct a detailed design analysis of the proposed surface/submarine hardware and software design. Detailed physical and performance design characteristics (e.g. system mechanization, reset/calibration procedures and intervals, predicted ISM system performance, system error mitigation techniques, ISM to ISM alignment procedure, external sensor input requirements, Built-in-Test (BIT), environmental analysis (shock, vibe, etc.) shall be specifically identified. The Contractor shall present the results of the design analysis, including risk assessments, trade-offs made, and proposed logistic support/level of repair, at a Preliminary Design Review (PDR).

This shall be supported by the deliverables listed in this SOW section. The Contractor shall provide a Technical

Report – Studies/Services, ISM Drawing Tree identifying each of the ISM major assemblies/sub-assemblies and software modules.

The Contractor shall develop a Specification Requirement Verification Matrix, ISM Requirement Verification

Matrix that documents how each requirement contained in the ISM TRD will be verified (i.e. by Inspection, Analysis, Contractor Testing (provide specific reference to contractor test plan), Navy Functional and Physical

Configuration Audits (FCA/PCA) or Navy Testing).

CDRL A001 - TECHNICAL REPORT – STUDY/SERVICES, ISM DRAWING TREE

CDRL A002 - SPECIFICATION REQUIREMENT VERIFICATION MATRIX, ISM REQUIREMENTS

VERIFICATION MATRIX

3.2.3 Software/Firmware Engineering (CLINs 0001-0003, 0006-0007, 1001-1003, 1006, 2001-2003, 2006, 3002-3003, 4002-4003)

At a minimum, the Contractor and any subcontractors performing relevant work shall maintain and utilize

Capability Maturity Model Integration (CMMI) Level III accreditation throughout the life of the contract. The

Contractor shall perform all necessary software/firmware engineering efforts to design, develop, test, evaluate, and provide software/firmware products, services, and artifacts that implement the ISM capabilities stated in the ISM

TRD. The details of those efforts, including the required data deliverables and reviews, are described in the subsequent paragraphs of this SOW. The Government desires Government Purpose Rights (GPR) for software/firmware, middleware, and modeling artifacts developed under this contract. The Contractor shall minimize the amount of unique non-commercial software/firmware that must be developed/modified in the design of the ISM.

3.2.3.1 Software/Firmware Design

The Contractor shall implement open, modular software/firmware architecture, composed of Software Components

(SC), which minimize coupling and inter-dependencies. A Computer Software Configuration Item (CSCI) can contain one or more SCs that follow the functional partitioning as depicted in the ISM TRD. The Contractor shall identify all operational software/firmware in one or more CSCI(s).

The Contractor shall develop and deliver a Software Requirements Specification (SRS) which includes all middleware/interfaces and software/firmware, with associated details, to ensure requirements are met.

The Contractor shall develop and deliver a Software Design Description (SDD) which describes the architectural modularity and detailed design of the software/firmware component.

CDRL A003 - SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

CDRL A004 - SOFTWARE DESIGN DESCRIPTION (SDD)

3.2.3.2 Software/Firmware Development

The Contractor shall develop any ISM software/firmware not available in the open market. The Contractor shall develop and deliver a Software Development Plan (SDP), based upon guidance found in IEEE/EIA 12207 and In

Accordance With (IAW) CMMI requirements. In the software/firmware, the Contractor shall include functions for

Built-In Test Functions/Built-In Test Equipment (BIT/BITE), Calibration Algorithms, and Identification of Status and Control signals as defined in the ISM TRD. The Contractor shall use Open Architecture conventions in this development and shall document these conventions in the SDP. Any unique support items developed during the software/firmware development process shall be delivered to the Government with Unlimited Rights and the

Contractor shall make any non-unique support items available for review. In the SDP, the Contractor shall discuss software/firmware design integrity, quality and stability, address CM, defect tracking, peer reviews and other associated processes, as well as detail the software/firmware build environments. The Contractor shall use software/firmware management indicators and metrics to aid in managing the ISM software/firmware development process and communicating its status to the Government. The Contractor shall define goals for each of the software/firmware metrics and present these metrics for Government Approval at each Systems Engineering

Technical Review (SETR). The Contractor shall define a corrective action process for identifying software/firmware development impacts and resolution when goals are not met, and shall document this process in the SDP.

The Contractor shall define the software Operating Environment (OE) for the ISM. The Contractor shall manage the OE baseline throughout the ISM development. Upon completion of the Physical Configuration Audit (PCA), the

Contractor shall transition configuration control of the OE baseline to the Government. The Contractor shall process changes to the OE baseline in accordance with the Government approved Contractor’s Configuration Management

(CM) Plan. The Contractor shall obtain Government approval of any OE change before proceeding with software/firmware development.

The Contractor shall develop and deliver a Software Version Description (SVD). In the SVD, the Contractor shall detail all Operating Systems with their associated kernel version, configuration, operational libraries and firmware.

CDRL A005 - SOFTWARE DEVELOPMENT PLAN (SDP)

CDRL A006 - CONTRACTOR’S CONFIGURATION MANAGEMENT PLAN

CDRL A007 - SOFTWARE VERSION DESCRIPTION (SVD)

3.2.3.3 Commercial Off-the-Shelf (COTS) Software/Firmware

The Contractor shall provide all COTS software/firmware, including all software documentation, incorporated into the OE baseline(s) as well as software/firmware packages/tools utilized to generate OE baselines but not necessarily incorporated into the OE. The Contractor shall ensure interoperability of such software/firmware with the OE and shall document any interdependencies (such as minimal revision required) in the appropriate SVD(s). The

Contractor shall document all licensing requirements/restrictions for each COTS product in the SVD. The

Contractor shall include in this documentation all delivered software/firmware licenses required to provide the ISM software/firmware capabilities and to support full lifecycle implementation.

3.2.3.4 Software/Firmware Testing

The Contractor shall plan and conduct SC-level tests for all developed and modified COTS software/firmware SCs.

The Contractor shall develop and deliver a Software Test Plan (STP), a Software Test Description (STD), and

Software Test Reports (STR) that identify and document test cases describing their purpose, the functions being tested, the test environment, and the test cases. The Contractor shall conduct the SC test and record the results in accordance with the SDP and applicable SRS and SDD documents.

The Contractor shall plan and conduct ISM software/firmware integration testing. The Contractor’s iterative software/firmware testing shall include additional CSCI and external interfaces ensuring requirements compliance and sub-system stability. The Contractor shall repeat this process until all CSCIs and interfaces are integrated and tested. The Contractor shall conduct this testing in accordance with the Contractor’s STP.

CDRL A008 - SOFTWARE TEST PLAN (STP)

CDRL A009 - SOFTWARE TEST DESCRIPTION (STD)

CDRL A010 - SOFTWARE TEST REPORT (STR)

3.2.3.5 Software/Firmware Products

The Contractor shall develop Software Product Specifications (SPS) for each approved software/firmware product baseline. The Contractor shall identify all software/firmware licensing requirements and any software/firmware usage restrictions. The Contractor shall deliver all required software/firmware licenses with the final software/firmware product. The Contractor shall ensure software/firmware and software/firmware revisions are under CM control and documented in the SDP. The Contractor shall deliver the Computer Software Products including libraries and software/firmware packages, as well as all software/firmware tools/utilities. The Contractor shall successfully complete qualification testing of the computer software products prior to submission.

CDRL A011 - SOFTWARE PRODUCT SPECIFICATION (SPS)

CDRL A012 - COMPUTER SOFTWARE PRODUCT

3.2.3.6 Software/Firmware Delivery and Transition

The Contractor shall develop and deliver a Software/Firmware Support Manual (SFSM), which contains detailed technical information addressing the processes and resources required to build ISM software/firmware. In the

SFSM, the Contractor shall also include file format and data structures used in downloadable datasets and system logs, and describe processes and associated equipment to load and verify software/firmware on system hardware devices that are not defined in a CSCI.

The Contractor shall prepare, with the Government, the Software Transition Plan (STRP) that shall accompany the final Government accepted software/firmware release products and artifacts. This plan shall also be accompanied with a current SVD and SFSM.

CDRL A013 - FIRMWARE SUPPORT MANUAL (FSM), SOFTWARE FIRMWARE SUPPORT MANUAL

(SFSM)

CDRL A014 - SOFTWARE TRANSITION PLAN (STRP)

3.2.3.7 Commonality of Hardware, Software/Firmware and Interfaces (All CLINs)

The Government intends to procure (to the greatest extent possible) system(s) which have an Open System

Architecture and corresponding components. As part of this contract, the Contractor shall define, document, and follow an open systems approach for using modular design, standards-based interfaces, and widely-supported consensus-based standards. The Contractor’s ISM architectural methodology shall support the application of hardware and software/firmware Technology Insertion and Technology Refresh (TI/TR) strategy using an open systems approach responsive to changes driven by mission requirements and new technologies. The Contractor shall develop, maintain, and use an Open System Management Plan (OSMP), in conjunction with Open Architecture assessment(s), using the Open Architecture Assessment Tool (OAAT) Version 3.0 to support this approach and will be required to demonstrate compliance with that plan during all design reviews. In the OSMP, the Contractor shall identify all Commercial-Off-the-Shelf/Non-development Item (COTS/NDI) components, their functionality and proposed use in the system. The Contractor shall provide copies of license agreements related to the use of these components for Government approval prior to use. The proposed OSMP will be incorporated into the contract with any changes, alterations, and/or modifications requiring Government approval.

In satisfying the Government's requirements for the OSMP, the Contractor shall utilize, but not be limited to, the following system architecture approach characteristics:

Open Architecture - The Contractor shall develop and maintain an architecture that incorporates appropriate considerations for commonality, reconfigurability, portability, maintainability, TI/TR, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability as required by the 23 DEC 2005 Office of the Chief of Naval Operations (OPNAV N6/7) requirements letter.

(This letter is available at https://acc.dau.mil/oa.)

Interface Design and Management - The Contractor shall ensure that external information exchange requirements are implemented in a standard and open manner as part of this effort. These actions shall include planning that identifies the Contractor's specific approach to ensuring system and interface data is well-defined, available to all programs, and uses a standards-based tool for definition within the context of the Navy and Marine Corps upgrade programs. The Contractor shall develop system upgrades that ensure that 1) data will be posted to shared spaces for users to access except when limited by security, policy, or regulations; 2) data shall provide for interoperability with many-to-many exchanges of data, and verified trust and integrity of users and applications; and 3) data shall be transmitted through well and openly defined interfaces.

Modular, Open Design - The Contractor shall develop an architecture that is layered and modular and uses standards-based COTS/NDI hardware, operating systems, and middleware that all utilize either non-proprietary or non-vendor unique key Application Programming Interfaces (API). This applies to all subsystems and components. In the Open System Management Plan, the Contractor shall, at a minimum, describe how the proposed system architecture meets these goals, including the steps taken to use non-proprietary or non-vendor unique COTS or reusable NDI components wherever practicable. The

Government will conduct an Open Architecture assessment using the Open Architecture Assessment Tool

(OAAT) to evaluate the degree of system openness.

Module Coupling - The Contractor's design approach shall result in modules that have minimal dependencies on other modules (loose coupling), as evidenced by simple, well-defined interfaces and by the absence of implicit data sharing. The purpose is to ensure that any changes to one module will not necessitate extensive changes to other modules, and hence facilitate module replacement and system enhancement. The Contractor shall describe, in the OSMP, the approach used to determine the level of coupling and the design trade-off approach.

Module Cohesion - The Contractor's design shall result in modules that are characterized by the singular assignment of identifiable and discrete functionality (high…