Draft_N00024-17-R-4200_Section_B_and_C_3_7_17.pdf

N00024-17-R-4200

Section B - Supplies or Services and Prices

The Contractor shall furnish the following supplies and services when ordered by the Contracting Officer in accordance with the terms and conditions set forth in this contract.

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

CLIN

Number

Machinery Control Systems (MCS) Non-Recurring Engineering/Qualification Including Qualification and First Article Tests and First Article Unit

FFP

1 Lot

FOB: Destination

NET AMT

Data for CLIN 0001

Lot NSP

(and if options are exercised CLIN's 0003 - 0011) Price to be included in CLIN's 0001 and 0003 - 0011. See DD Form 1423 Exhibit A attached hereto.

NET AMT NSP

Machinery Control System Shipset

1 Set

OPTION See Note A and Note B

MCS LBES Suite

3 Set

OPTION Machinery Control System Land Based Engineering Site Set See Note A and Note B.

MCS Training Set

OPTION Machinery Control System Land Based Engineering Site Set

MCS LBES Software Lab Set

OPTION Machinery Control System Land Based Engineering Site Main Engine Room Training Set

11 Set

12 Set

Engineering Services Labor T&M See Note C.

To be funded as required.

See Attachment C for Labor Rates.

Not to Exceed $ _________(to be filled in at award), and not to exceed 50,000 hours

TOT ESTIMATED PRICE

CEILING PRICE

Support for Engineering Services

COST

See Note C.

To be funded as required.

Estimated amount not to exceed $200,000

ESTIMATED COST

CEILING COST

Provisioning Technical Data

1 Lot NSP

Provisioning Technical Documentation for CLIN 0001 (and if Options are exercised CLINs 0003 - 0011).

See DD Form 1423 Exhibit B attached hereto.

Price to be included in the price of CLINs 0001 (and if Options are exercised CLINs 0003

- 0011).

NET AMT NSP

Provisioned Items Ordered

Installation and Checkout (INCO) Spares.

To be ordered and funded as required.

See Note C.

See Attachment D for Pricing.

Provisioned Items Ordered

On Board Repair Parts (OBRP) To be ordered and funded as required.

See Note C.

See Attachment D for Pricing.

NOTE A - The Government will specify which of the three base MCS configurations, or combination thereof, are required to be delivered within each option exercise. The different configurations (Configuration 1: Flight I/II BF, Configuration 2: Flight IIA BF, or Configuration 3: Flight III FF) are defined in Section C. The Government may designate a combination of the three different configurations to be delivered within the same order.

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. Option CLINs 0003-0011 contain alternate quantity pricing which may be exercised by the Government at the price included in “TABLE 1 – PRICING FOR ALTERNATE QUANTITIES FOR CLINS 0004- 0011” in Section B. The Government may exercise more than one Alternate Option or for less than the quantity stated under any CLIN in accordance with FAR 52.217-7, but in no event shall the total quantity order under any CLIN exceed the maximum quantity allowed by that CLIN, as detailed in the chart below.

CLIN Maximum Quantity 0004 3 0005 3 0006 3 0007 11 0008 12 0009 12 0010 12 0011 12

NOTE C – In addition to the Naval Sea Systems Command, The Navy Inventory Control Point (NAV-ICP) is also authorized as an ordering activity.

NOTE D – Engineering Services manhours (CLIN 0012) and Support for Engineering Services (CLIN 0013) shall be provided as tasked in accordance with the clause in Section H entitled “Technical Instructions”. Engineering Services shall be reimbursed at the fixed-price manhour rates set forth in the rate table included as Attachment C. Support for Engineering Services shall be reimbursed at actual costs with no provision for profit or fee.

TABLE 1 - PRICING FOR ALTERNATE QUANTITIES FOR CLINS 0004-0011

QUANTITY

(SHIPSETS)

UNIT PRICE

(to be completed by Offeror)

TOTAL PRICE

(to be completed by Offeror)

0004 1 0004 2 0004 3 0005 1 0005 2 0005 3

0006 1 0006 2 0006 3 0007 1 0007 2 0007 3 0007 4 0007 5 0007 6 0007 7 0007 8 0007 9 0007 10 0007 11 0008 1 0008 2 0008 3 0008 4 0008 5 0008 6 0008 7 0008 8 0008 9 0008 10 0008 11 0008 12 0009 1 0009 2 0009 3 0009 4 0009 5 0009 6 0009 7 0009 8 0009 9 0009 10 0009 11 0009 12 0010 1 0010 2

0010 3 0010 4 0010 5 0010 6 0010 7 0010 8 0010 9 0010 10 0010 11 0010 12 0011 1 0011 2 0011 3 0011 4 0011 5 0011 6 0011 7 0011 8 0011 9 0011 10 0011 11 0011 12

CLAUSES INCORPORATED BY FULL TEXT

HQ B-2-0022 CONTRACT SUMMARY FOR PAYMENT OFFICE (FIXED PRICE) (FEB 1997)

This entire contract is fixed price with the exception of CLIN 0012 Engineering Services which is Time and Materials and CLIN 0013 Support for Engineering Services which is reimbursed at costs with no provision for profit or fee.

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-0013 PAYMENT FOR ENGINEERING SERVICES AND SUPPORT – ALTERNATE I (NAVSEA) (JAN 2008)

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

(d) Separate invoices shall be submitted for selected replacement repair parts subsequent to the establishment of prices therefor in accordance with SECTION C of this contract.

HQ B-2-0016 PROVISIONING TECHNICAL DOCUMENTATION – WITHHOLDING OF PAYMENT

(NAVSEA) (SEP 1990)

(a) For the purpose of paragraph (c) of the "PROGRESS PAYMENTS" clause of this contract, if included, the requirement that the Contractor develop and deliver Provisioning Technical Documentation (PTD) is considered to be a "material requirement of this contract," and Contractor failure to make adequate progress in the development of PTD, or to deliver acceptable PTD on a timely basis, may result in reduction or suspension of Progress Payments as provided in said paragraph.

(b) The PTD is considered to be a part of the "Technical Data" specified to be delivered under this contract for the purposes of the "TECHNICAL DATA--WITHHOLDING OF PAYMENT" (DFARS 252.227-7030) clause. The terms and conditions of the clause entitled "LIMITATION ON WITHHOLDING OF PAYMENTS (FAR 52.232-9), if included in this contract, shall not apply to withholding of payment for failure to make timely delivery of the PTD or delivery of deficient PTD.

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) (APR 2015)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its actual travel costs in accordance with FAR 31.205-46. The costs to be reimbursed shall be those costs determined to be allowable, allocable and reasonable by the Procuring Contracting Officer, Administrative Contracting Officer or their duly authorized representative, as advised by 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 incidental 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 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.

Section C - Descriptions and Specifications

CONTRACT LINE ITEM DESCRIPTION

ITEMS 0001 (and 0003-0011 if options are exercised)

1.1 GENERAL The Contractor shall design, fabricate, assemble, qualify, and test a Universal Control Console (UCC) and Data Interface Unit (DIU) to meet the performance, design and test requirements specified in the DDG- M UCC/DIU Performance Specification provided in Attachment A. This includes, but is not limited to, machinery control system design and integration, mechanical and electrical power interface requirements, network system interfaces, and design integration. Unless indicated as provided by the Government, all assemblies, subassemblies, and components identified, or required for proper operation of the equipment, shall be furnished by the Contractor.

The Contractor shall provide qualified personnel, materials, facilities, equipment, controls and control interfaces, test instrumentation, data collection and analysis, applicable documents, hardware, software, and services that support the UCC/DIU.

Any approval by the Government as required under this contract or the DDG-M UCC/DIU Performance Specification (Attachment A) shall not relieve the Contractor of its obligation to fully comply with the requirements of this contract and the DDG-M UCC/DIU Performance Specification (Attachment A), nor shall it impose upon the Government any liability.

Definitions:

Configuration 1: Backfit (BF) Flight I/II DDGs (51-78) Configuration 2: Forward Fit (FF) Flight III DDGs (128 and follow), New Ship construction Configuration 3: Backfit (BF) Flight IIA DDGs (79-110)

1.1.1 The logistics support requirements for the UCC/DIU shall be provided in accordance with Attachment B. A complete logistics development is required. The training products, technical manuals, logistics management information, and engineering analysis shall completely cover the entire DIU and UCC configuration. It is incumbent on the Contractor to identify need dates for Government Furnished Information as early as possible. Refer to paragraph 1.20 of this section: GOVERNMENT RESPONSIBILITIES.

1.1.2 The Contractor shall provide all plans, technical data, drawings, pass/fail criteria, procedures, methods and results to the Government (including Government ISEA) for approval in accordance with Contract Data Requirements Lists, Exhibits A and B.

1.1.2.1 The Contractor shall provide a technical data package (TDP) for the UCC and DIU consisting of assembly drawings, performance data, wiring and signal lists, detail drawings, installation control drawings, UCC/DIU interface data, parts list(s), fabrication methods, test and inspection procedures. Attachment E of this contract provides the basic tailoring required of the TDP. The level of assembly of the TDP drawings is subject to approval by the Government at preliminary design review. In addition the Contractor shall provide, in the form of Interface Control Documents, technical data in advance of the TDP to support ship installation planning and installation drawing development.

The Contractor shall provide all drawings in accordance with paragraphs 3.3.1, 3.3.1.1, 3.3.1.2, 3.3.1.3, 3.3.1.4, and

3.4 of MIL-S-901D.

CDRLS: A002, A002A, A040

(Note: CDRLs cited herein are applicable to the SOW Section above the CDRLs specified).

1.1.2.2 The Contractor shall provide system and hardware requirements documents to the Government in a DOORS 9.0 compatible database. An export file of UCC/DIU system and hardware requirements documents from

DOORS into Microsoft EXCEL file format is required with each DOORS file delivery. This export file shall list all requirements in the technical specification. The export file shall have a verification method and list a CDRL that will document verification for every requirement providing a Requirements Verification Traceability Matrix

(RTVM).

CDRL: A051

1.1.2.3 Vendor Interface Requirements (VIR)

The Contractor shall provide estimated or available interface requirements information. The VIR submission shall include:

• Equipment Dimensions

• Weight

• Locations for cable entrances

• Locations for air exhaust and intake interfaces

• Equipment (and location in UCC and DIU) requiring removal or disassembly for repair or maintenance

• Estimated Maintenance envelope

• Estimated Shock envelope

• Mounting requirements

The Contractor shall provide a list of critical failures experienced or predicted with demonstrated or predicted mean time between failure (MTBF) and mean time to repair (MTTR) data and describe the basis for those predictions.

Predicted MTBF and MTTR shall be based on the duty cycle identified in the Technical Specification.

Definition: A critical failure shall be considered as any component or system failure that would cause an unscheduled loss of capability of the UCC and DIU system.

CDRL: A037 & A040

1.1.3 If disassembly and reassembly of the UCC is required for shipboard installation:

(a) the Contractor shall provide technician level instructions for disassembly and reassembly for Government approval. See CDRL: A053;

(b) the UCC shall be disassembled after Factory Acceptance Test and prior to shipping. The Contractor is responsible for all packaging and shipping of the console;

(c) the Contractor shall be responsible for in-field (Ship and Land Based Engineering Site) UCC reassembly and console Functional Acceptance Testing.

1.1.3.1 The length of DDG 51 Class Modernization availability is 26 weeks. There will be 2 weeks available for reassembly and console Functional Acceptance Testing.

1.1.4 All work performed under this contract shall comply with applicable Federal, State, and local laws and regulations. The Contractor shall have all valid permits and licenses necessary prior to performing the associated scope of work. The Contractor shall maintain valid permits and licenses throughout the period of performance of this contract.

The Contractor will not be responsible for the removal of EOOW, RSC, or DCC consoles or mounting of new UCCs or DIUs. The Contractor shall not be responsible for installation, removal, or relocation of ship’s equipment cabling.

The Contractor shall provide all UCC and DIU mating connectors, plugs, and backshells for all field cables.

1.1.5 CLIN 0001 will require full proof of prior successful qualification testing or will require that qualification testing be conducted as part of this contract. New qualification testing will require a First Article Test Set.

1.1.5.1 A First Article Test (FAT) set shall consist of the following data, components, and subsystems, at a minimum. Additional equipment, fittings, and accessories shall be provided as necessary to meet the requirements in the DDG-M UCC/DIU Performance Specification (Attachment A):

• Equipment name (Ship location)

• UCC1 (CCS)

• UCC3 (MER1)

• DIU2 (MER2)

• DIU4 (MER1)

• Required operating systems, runtime licenses, drivers, APIs, COTs applications, and Contractor developed applications.

• All installation media.

• The DIU cabinets can be any of the following three variants: Configuration 1, Configuration 2 or

Configuration 3.

1.1.6 CLIN 0003 and CLIN 0007 thru 0011 shipsets shall consist of the following data, components, and subsystems, at a minimum. Additional equipment, fittings, and accessories shall be provided as necessary to meet the requirements in the DDG-M UCC/DIU Performance Specification (Attachment A):

• Equipment name (Ship location)

• UCC1 (CCS)

• UCC2 (CCS)

• UCC3 (MER1)

• UCC4 (MER2)

• DIU1 (AMR1)

• DIU2 (MER2)

• DIU3 (GEN3)

• DIU4 (MER1)

• DIU5 (MER2)

• Required operating systems, runtime licenses, drivers, APIs, COTs applications, and Contractor developed applications.

• All installation media.

1.1.7 CLIN 0004 MCS Land Based Engineering Site (LBES) Set shall consist of the following data, components, and subsystems, at a minimum. Additional equipment, fittings, and accessories shall be provided as necessary to meet the requirements in the DDG-M UCC/DIU Performance Specification (Attachment A):

• Equipment name (Ship location)

• UCC1 (CCS)

• UCC2 (CCS)

• DIU1 (AMR1)

• DIU2 (MER2)

• DIU3 (GEN3)

• DIU4 (MER1)

• DIU5 (MER2)

• Required operating systems, runtime licenses, drivers, APIs, COTs applications, and Contractor developed applications.

• CLIN 0004 UCC console sets shall all be identical

CLIN 0004 DIU cabinets shall be produced in three variants: Configuration 1, Configuration 2 and Configuration 3.

1.1.8 CLIN 0005 MCS Training Set shall consist of the following data, components, and subsystems, at a minimum. Additional equipment, fittings, and accessories shall be provided as necessary to meet the requirements in the DDG-M UCC/DIU Performance Specification (Attachment A):

• Equipment name (Ship location)

• UCC1 (CCS)

• UCC3 (MER1)

• DIU4 (MER1)

• DIU5 (MER2)

• Required operating systems, runtime licenses, drivers, APIs, COTs applications, and Contractor developed applications.

• CLIN 0005 UCC console sets shall be identical.

CLIN 0005 DIU cabinets shall be produced in three variants: Configuration 1, Configuration 2 and Configuration 3.

1.1.9 CLIN 0006 LBES Software Lab Set shall consist of the following components and subsystems, at a minimum. Additional equipment, fittings, and accessories shall be provided as necessary to meet the requirements in the DDG-M UCC/DIU Performance Specification (Attachment A):

• Qty (1) UCC Primary WS processor (fully configured with OS/drivers/3rd party SW)

• Qty (1) UCC Secondary WS processor (fully configured with OS/drivers/3rd party SW)

• Qty (1) Data Repository Processor (fully configured with OS/drivers/3rd party SW)

• Qty (1) DIU processor (fully configured with OS)

• Qty (1 ea) DIU Input/Output (I/O) Signal Processing CCAs

• Qty (1) COTS desktop PC or laptop PC loaded with full development environment (IAW SIP/SPG)

1.2 APPLICABLE DOCUMENTS – THE DESIGN OF THE OVERALL SYSTEM IS REQUIRED TO BE

IN COMPLIANCE WITH THE FOLLOWING DOCUMENTS:

• ISO/IEC/IEEE 15289, Second Edition: Systems and Software engineering – Content of life-cycle information items (documentation)

• MIL-HDBK-61A (SE): Configuration Management Guidance

• SAE EIA-649B:National Consensus Standard for Configuration Management

• MIL-STD-882E

• NAVSEAINST 3900.8A SER 03/011 20MAY05

• ASTM F1166-07: Standard Practice for Human Engineering Design for Marine Systems, Equipment, and

Facilities

• ANSI/ASQC Q9001-2000

• MIL-STD-1686C

• MIL-HDBK 263B

• MIL-M-38510J: Microcircuits

• MIL-STD-883J: Microcircuits

• SAE JA1000-1, Appendix A, Method A10 and A32.

• MIL-STD-881C: Work breakdown

• NAVSEAINST 9491.1C

• NAVSEA Letter 55X/SH, Serial 87, dated 17 February 1984

• MIL-S-901D

• MIL-STD-167-1A

• MIL-STD-461 (Revision E or F)

• MIL-STD-810G

• MIL-HDBK 344A: Environmental Stress Screening of Electronic Equipment

• MIL-HDBK 2164A: Environmental Stress Screening Process Improvement Study

• FED-STD-595C

• MIL-STD-686C

• MIL-STD-130N

• MIL-DTL-15024F Type E

• MIL-M-43719 Type 1

• NAVSEA Technical Publication T9074-AS-GIB-010/271

• NAVSEA Clarification letter SER 05P3-047, dtd 9 Apr 03, "CLARIFICATION OF MIL-S-901 SHOCK

TEST REQUIREMENTS CONCERNING SHOCK QUALIFICATION OF CLASS I AND CLASS II

EQUIPMENT”.

• MIL-STD-3018 Parts Management

1.3 SOFTWARE ENGINEERING. The Contractor shall provide a software test tool(s) to test BIT, Self-test and Ground Detect functionality for DIU. The Contractor shall provide a software test tool(s) to test BIT and Self-test functionality for UCC. The Contractor shall develop software in C/C++ to meet the requirements in the DDG-M UCC/DIU Performance Specification (Attachment A). The Contractor shall provide software and source code for the following at a minimum: BIT, self-test, Ground Detect, calibration, CCA I/O data, status, and alarms.

CDRL: A014

1.3.1 The Contractor shall generate, provide, and implement a Software Development Plan (SDP). The SDP shall include the Software Configuration Management Plan (SCMP) and Software Quality Assurance Plan (SQAP).

CDRL: A025

1.3.2 The Contractor shall develop and provide the following software documentation for all software developed under this contract:

(a) detailed Interface Design Descriptions (IDD);

(b) Software Requirements Specifications (SRSs);

(c) Software Design Descriptions (SDD);

(d) Software Programmers Guide (SPG);

(e) Software Version Description (SVD);

(f) Software User’s Manual (SUM);

(g) Software Installation Plan (SIP);

(h) Software Test Plan (STP);

(i) Software Test Descriptions (STDs);

(j) Software Test Reports (STRs);

(k) Software Product Specifications (SPSs);

(l) System Deficiency Report (SDR); and (m)Software Transition Plan (STrP).

1.3.2.1 The software requirements shall be provided to the government as a DOORS 9.0 compatible database. An export file of UCC/DIU software requirements from DOORS into Microsoft EXCEL file format is required with each DOORS file delivery.

1.3.2.2 The Contractor shall provide the origin and Software Licensing Agreements for all Software Development Tools and Software used to satisfy the requirements of this contract. This includes the origin of all physical media and source link for all downloaded tools from the internet.

CDRLS: A012, A013, A014, A015, A016, A017, A018, A019, A020, A021, A022, A023, A024

1.3.3 The Contractor shall design and develop the software architecture in a manner which shall ensure maintainability throughout the development and lifecycle of the software. The Contractor shall follow best coding practices. The Contractor shall be appraised at a Capability Maturity Model Integration (CMMI) maturity level three (3) or higher by a certified SEI appraiser and must utilize its CMMI processes in performance of this contract.

The Contractor shall develop all software following the ISO/IEC/IEEE 15289, Second Edition: Systems and Software engineering – Content of life-cycle information items (documentation), section 10. The Contractor shall follow software development processes such as those developed for compliance with SEI SW CMMI Level III.

1.3.3.1 The Contractor shall address software safety in their Program Plan. Safety assurance shall be addressed in the SDP and safety requirements for software shall be addressed in the SRSs.

1.3.3.2 The Contractor shall conduct testing on all of the Computer Software Configuration Items (CSCIs) developed under this contract. The Contractor shall perform the software testing in accordance with the STP and report the test results via the STR. The Contractor shall validate the software is in compliance with the SRSs and IDDs developed under this contract. The Contractor shall address the software unit testing, software integration testing and software system testing in the STP and STD developed under this contract.

1.3.3.3 The Contractor shall design and develop all software using the following general requirements:

• No Binary or machine executable public domain software products with limited or no warranty such as those commonly known as freeware or shareware shall be used.

• Open Source Software (OSS) binary installation packages shall be obtained from official project download links provided by the project group maintaining the OSS package.

• OSS binary packages unavailable for download from a trusted OSS server shall be documented under appropriate supply chain and configuration management policies.

• OSS servers located in the continental United States in the “.gov” or “.mil” top level domain shall be considered trusted.

• OSS servers located in the continental United States not in the “.gov” or “.mil” top level domain shall be considered untrusted.

• OSS servers not located in the continental United States regardless of “.gov” or “.mil” top level domain shall be considered untrusted.

• Contractor shall provide Software License Agreements for all OSS.

• Software/Firmware shall ensure that file system objects are truncated before reusing the same name.

• Software/Firmware shall ensure that unused objects contents are zeroed before they are deallocated and relinquished to the operating system.

• Software/Firmware shall protect against buffer overflows, dynamic memory errors, dangling pointers, double frees, invalid frees, null pointer accesses, uninitialized variables, wild pointers, out of memory errors, stack overflows and allocation failures.

• Software/Firmware shall perform input validation of all data passed to a CSCI from any external interfaces such as but not limited to network packets, user provided input, and other CSCIs.

1.3.3.4 The Contractor shall provide the following items along with the SPS deliverable: applications, operating systems, licenses, Application Program Interfaces (APIs), all development tools, and documentation to the Government for all Contractor provided COTS software, firmware, and hardware/device drivers.

1.3.3.4.1 The Contractor shall deliver the entire system including Software, Software Licenses and Subscription services, Professional Software Configuration or Customization, Integration and Deployment services, and

Professional Software Consultation services for the system. Delivery of single aspect will not be sufficient or acceptable.

CDRL: A019, A023

1.3.3.4.2 Contractor shall provide with SPS deliverable including but not limited to the following: compiled binaries/executables, licenses, source code, APIs, BSP (Board Support Package), and development tools for all Contractor developed software scripts and software applications . The Contractor shall provide an SPG for all contractor developed software.

CDRLS: A019, A023

1.3.4 The Contractor shall provide installation procedures for complete installation, configuration, and set-up of all Contractor and COTS software delivered under the contract, including drivers as part of the SPS. The SPS shall include an installation and set-up procedure of all UCC/DIU BIOS, operating systems, and Contractor provided applications from initial hardware startup.

CDRL: A019

1.3.5 The Contractor shall ensure that each baseline and subsequent software builds and all software delivered under this contract are free from security vulnerabilities including viruses, malware, malicious code, Trojan horses and any other security vulnerability. The Contractor shall ensure that for each software baseline and subsequent software builds, the Contractor's software development environment incorporates updated Anti-Virus definitions that are current to within 30 days from the end of development. The Contractor shall also ensure that any embedded systems or solutions that only implement software via firmware are scanned with the most current Anti-Virus scanning tool(s) prior to delivery.

1.3.5.1 The Contractor shall continuously review and monitor its software products for security vulnerabilities and issue updates to its product to mitigate any security vulnerability. Security vulnerability is any inherent weakness in an information system, security procedures, internal controls, or implementation that could be exploited by a threat source, for example, viruses, malware, or Trojan Horses and other security threats such as those listed in NIST Special Publication 800-12: An Introduction to Computer Security: The NIST Handbook, Chapter 4. The Contractor shall warrant that any such computer software or computer database delivered under this contract is free of any viruses, malware, malicious code, Trojan horses, and any other security vulnerabilities at delivery and during the period of performance of this contract.

1.3.5.2 The contractor shall provide in depth expertise of the software and software coding and shall manage vulnerability testing and mitigation required by the RMF processes and achievement of RMF certifications for Security/IA.

1.3.5.3 System libraries shall be managed and maintained to protect privileged programs and to prevent or minimize the introduction of unauthorized code. A plan shall be developed by the vendor that illustrates this process. The plan shall be provided to the Government.

CDRL: A015

1.3.6 Data Rights and Patent Rights:

To be provided by the Contractor in accordance with its proposal and as incorporated into this contract as Attachment F.

1.4 HARDWARE DOCUMENTATION. The Contractor shall provide the following hardware documentation for all hardware designed under this contract: detailed power requirements, signal timing, thermal characteristics, software programming interface including but not limited to registers, memory locations, read/write locations, and feedback locations for signal write commands, and firmware reprogramming.

CDRL: A060

The Contractor shall provide Commercial off-the-shelf (COTS) manuals and associated supplemental data for all COTS Line Replaceable Units (LRUs).

CDRL: A007

1.5 OPERATING SYSTEM & IMAGING.

The UCC Primary, ICAC Processor, Secondary, and DR Processors shall be configured in accordance with DDGM SW configuration. Navy will provide preliminary DDGM SW configuration document 30 days after the Functional Design Review (FDR).

All system testing and component integration with Windows based Operating Systems shall be done with all Microsoft patches applied that are available at the time of Critical Design Review (CDR).

1.6 CONFIGURATION MANAGEMENT. The Contractor shall develop and deliver a Configuration Management Plan (CMP) in accordance with either MIL-HDBK-61A and/or EIA-649B. The Contractor shall control the configuration of the UCC/DIU based upon the requirements as defined by the DDG-M UCC/DIU Performance Specification (Attachment A) and Contractor hardware and software system requirements. The CMP shall address procedures for a Physical Configuration Audit (PCA) of the first production unit and Configuration Status Accounting (CSA) procedures. The CMP, PCA procedures, PCA data, CSA procedures, and CSA data shall be provided to the Government. The CSA procedures shall describe the Contractor’s method of ensuring that technical documentation, parts, and components in INCOS (Installation & Check-Out Spares) and Onboard Repair Parts Kits match the configuration of the production units and shall describe the Contractor’s configuration control process and the Government’s role in this process.

CDRLS: A046, A047, A048

1.6.1 An Engineering Change Proposal (ECP), also referred to as a Design Change Notice in Attachment B, shall be used by the Contractor to define a proposed change to a configuration item. The ECP form to be used will be provided 30 days after contract award. The ECP shall describe the scope of the change and contain sufficient data to allow evaluation of the effect on technical performance, logistics support, interface considerations, and costs of the proposed change. Class 1 changes are subject to Government approval. Class 1 ECPs are defined any change that would impact the form, fit or function of the system or system interfaces. The Contractor shall maintain the configuration definition established in the DDG-M UCC/DIU Performance Specification (Attachment A).

CDRL: A050

1.7 SYSTEM SAFETY/HUMAN ENGINEERING. The system safety criteria and considerations of MIL-STD- 882E and human engineering criteria and consideration of NAVSEAINST 3900.8A and ASTM F1166- 07 shall be considered and incorporated in the design of this equipment. The Contractor shall identify and evaluate personnel health and equipment hazards, define risk levels and establish mitigations through safety analysis and regulatory requirement evaluations.

CDRL: A036

1.8 QUALITY ASSURANCE PROGRAM. The Contractor shall provide and maintain a quality program that, as a minimum, adheres to the requirements of ANSI/ASQC Q9001-2000.

1.8.1 The Contractor shall provide and maintain a quality program in accordance with its Government approved Quality Assurance Plan for all supplies and services furnished. The quality program procedures, plans, data, and all other documentation that the quality program comprises shall be submitted to the Government for review and approval. The Contractor’s Quality Assurance Plan must include the quality programs of its major and critical subcontractors at the time it is submitted to the Government for approval. The Quality Assurance Plan shall be resubmitted any time major policy or process changes affect the scope of the contract. If the current Quality Assurance Plan has been approved, only changes to the plan need to be submitted along with the supporting documentation for review and approval by the Government prior to implementing the change. The Contractor shall require its subcontractors to provide a quality program achieving control of the quality of services and supplies provided consistent with the contract specifications and the intended use of the supplies/services. The Government reserves the right to disapprove the quality program or a portion thereof when it fails to meet the contractual requirements.

CDRL: A026

1.8.2 The Contractor’s and subcontractors’ quality programs shall be in accordance with the requirements of this contract and ANSI/ASQC Q9001-2000, American National Standard, Quality Systems-Model for Quality Assurance in Design, Development, Production, Installation and Servicing as supplemented below:

Design Control (add to section 4.4 of ANSI/ASQC Q9001-2000, hereinafter Q9001). The requirements of section 4.4, “Design Control,” of ANSI/ASQC Q9001 apply to design work conducted under this contract.

1.8.3 Control of customer-supplied product (add to section 4.7 of Q9001). The Contractor shall promptly report to the Government any Government-furnished property or material found damaged, malfunctioning, or otherwise unsuitable for use within 10 days of its first knowledge of the adverse condition of the material. In the event of damage or malfunction during or after installation, the Contractor shall determine, record, and report to the Government probable root cause and whether or not it is necessary to withhold property or material from use. As used in Section 4.7, the term “material” includes and applies to Government furnished equipment to be installed in or furnished with the end item. The term “property” is Government equipment which is used in the fabrication or assembly of the end item, and which is not delivered as part of the end item.

CDRL: A001

1.8.4 Contractor Inspection, test, and audit records (add to section 4.10.5 of Q9001) shall be delivered to the Government. Inspection and test records shall, as a minimum, indicate the nature of the observations, number of observations made, and the number and type of deficiencies found. Audit records shall include the scope of the audit, persons contacted, processes reviewed, checklists completed, nature and number of observations made, the number and type of findings, and corrective action taken. Data included in inspection, test, and audit records shall be complete, legible and accurate, and shall be usable by the Contractor and the Government for trend analysis and to assess corrective action effectiveness.

CDRL: A001

1.9 ELECTROSTATIC DISCHARGE (ESD) CONTROL PROGRAM. The Contractor shall establish this program in accordance with MIL-STD-1686C and MIL-HDBK 263B. This program shall be applicable to ESD sensitive parts listed in MIL-STD-1686C. The program shall be applicable from contract award date. The program shall include all procured electrical/electronic equipment, parts, and assemblies that were certified and qualified using the Electrostatic Discharge Sensitivity (ESDS) classifications 1, 2, and 3 designators and testing requirements specified under MIL-M-38510J and MIL-STD-883J. ESDS equipment, parts, and assemblies shall be identified and supplied to the Government Agency.

CDRL: A027

1.10 RELIABILITY AND MAINTAINABILITY (R&M). The Contractor shall implement a Reliability Program that shall be described in the Program Plan. The Reliability Program shall ensure traceability of reliability and maintainability requirements through design and provide customer interface on requirements, risk and design decisions. Milestones for reliability and maintainability efforts shall be included in the Integrated Master Schedule

(IMS).

1.10.1 The Contractor shall provide hardware Failure Modes, Effects, and Criticality Analysis (FMECA) to the Line Replaceable Unit (LRU) level. The analysis shall consider OS software and firmware failure modes. The Engineered Operating Cycle (EOC) shall be a 60-month operating cycle, duty cycle is always on. This equipment shall be considered Mission Essential. Contractor shall use SAE JA1000-1, Appendix A, Method A.10 for a Government sheltered environment, or a similar technique.

CDRL: A006

1.10.2 The Contractor shall provide a Reliability, Maintainability, and Availability Analysis and Assessment (RMAAA) with reliability and maintainability predictions of the complete UCC/DIU. The Contractor shall provide reliability predictions and maintainability predictions to the Line Replaceable Unit (LRU) level. Predictions shall reflect specified operating profiles and environmental conditions called out in the DDG-M UCC/DIU Performance Specification (Attachment A) and identify data sources used. Maintainability predictions shall include “tag-out” time, fault detection and isolation, LRU removal and replacement, and equipment check-out times. The Contractor shall use SAE JA1000-1, Appendix A, Method A.32 for a Government sheltered environment, or a similar technique.

CDRLS: A028 and A029

1.11 EQUIPMENT ANALYSIES.

1.11.1 THERMAL AND AIRFLOW ANALYSIS: The Contactor shall perform a Thermal and Airflow Analysis for all UCC/DIU equipment enclosures that have a volume larger than 1.1 cubic feet and contain critical components. The use of commercial modeling/simulation software is permissible. A thermal survey report is an acceptable substitute for analysis if the complete equipment enclosures are available for survey prior to CDR.

CDRL: A030

1.11.2 DYNAMIC ANALYSIS: The Contractor shall provide to the Government all equipment dynamic analysis including the shock isolation system design.

CDRL: A054

1.12 FAILURE REPORTING AND ANALYSIS PROGRAM. A Failure Reporting and Analysis Program (FRAP) shall be implemented by the Contractor. The Failure Reporting and Analysis Program shall include operating system (OS) software and failures. A summary list of all failures for which failure analysis reports have been prepared shall be provided to the Government.

CDRL: A031

1.13 PROGRAM PLAN. The Contractor shall develop, deliver, and maintain a Program Plan that includes an event based Work Breakdown Structure (WBS), reflecting how the effort shall be executed. The WBS shall be developed by the Contractor in a manner that reflects the Contractor’s customary way of organizing commercial projects and the need to have a direct relationship between project events and WBS. The WBS shall include a person-hour and labor category allocation for each separately identified task. The Program Plan shall include an Integrated Master Schedule (IMS) that reflects the event based WBS. The Contractor shall develop and maintain a WBS dictionary as specified in MIL-STD-881C. The schedule shall be maintained in Microsoft Project™ 2007 format and shall be made available to the Government electronically at regular intervals during the execution of the effort. The Government reserves the right to conduct an in-plant visit to the Contractor to review implementation of the Contractor’s schedule management system and to understand the methods the Contractor utilizes to determine progress. The intent of this in-plant visit(s) (business review(s)) is to ensure maximum visibility of the Contractor’s performance.

1.13.1 The Contractor shall develop, implement, manage to, update, and maintain the UCC/DIU Program Integrated Master Schedule (IMS) by logically networking detailed program activities. The IMS shall be maintained in Microsoft Project™ 2007 format. The IMS shall be consistent with schedule of the Government. All Contractor schedule information delivered or presented at program reviews shall originate from the IMS. The IMS shall be traceable to the Program Plan and shall contain all critical events, accomplishments, criteria, predecessors, and successors, and their dependencies. The IMS shall include a schedule for all WBS efforts using a Gantt chart. The Contractor shall conduct critical path analysis of the tasks and report problem areas and corrective actions required to eliminate/reduce schedule impact. The Contractor shall quantify the risk and provide optimistic, pessimistic, and most likely duration for each IMS activity and event. The Contractor shall ensure schedule integration with its subcontractors and shall verify/ensure the validity of the subcontractor’s schedule data, including demonstrating effective methods for incorporating schedule data from subcontractors into the Contractor’s IMS.

CDRLS: A032 and A033

1.14 MEETINGS AND PERIODIC REVIEWS. The Contractor shall plan, conduct, and document meetings and reviews held between the Government and the Contractor. The Contractor shall identify dates for the reviews in the Program Plan. The Contractor and the Government shall develop agendas for meetings jointly. Electronic copies of all presentation materials shall be made available to the Government for the purpose of documenting the meeting.

The Contractor shall prepare Meeting Minutes which document all material presented, key discussions, decisions made, and any action items resulting from the meeting.

CDRLS: A044 and A049

1.14.1 The Contractor shall participate in a post contract award conference at a site mutually agreed upon by the Contractor and the Government. The post award conference shall last no longer than one day and should occur within the first two weeks of the contract. Scheduling and coordination of technical reviews shall be at Contractor’s facility unless otherwise determined at post contract award conference.

1.14.2 The Contractor shall plan and conduct formal technical reviews on matters as coordinated with the Government. Formal reviews shall include a System Requirement Review (SRR), Software Specification Review (SSR), Preliminary Design Review (PDR), and Critical Design Review (CDR). The Contractor has the option to schedule Technical Manual In-Process Reviews and Provisioning Guidance Conference(s) (PGC) with the Government. The Contractor shall notify the Government of reviews with preliminary agenda topics, security considerations, locations, and times. The Contractor shall make available, in electronic format, the presentation material that is to be presented at the reviews and conferences cited in this provision. The material, including agenda, shall be made available at least two weeks in advance of the review or conference start.

CDRL: A049

1.14.3 The Contractor shall prepare a detailed design of the UCC/DIU and conduct SRR, SSR, PDR, and CDR for the purpose of describing the aspects of the designs chosen. These reviews shall include:

• Entrance and Exit Criteria

• IMS Update and Review

• Production Schedule

• Open Action Items

• Review of Requirements

• Trade-off analysis used to arrive at the design

• Details of methods used in the design process

• Progress of Technical Data Package to include detailed design drawings and interface control drawings

• Detailed design drawings and interface control drawings

• The status of the risk management efforts

• An assessment of the impact of cost drivers in the design

• The product selection supportability analysis including discussion of where components are in their lifecycle and highlighting obsolete components and assemblies

• An update of the projected production and life cycle costs

• Testing requirements

• A status of the design to date

During the reviews, the contractor shall enumerate, explain, and present traceability of requirements from the DDG- M UCC/DIU Performance Specification (Attachment A) to the design. The Contractor shall document verification that the design meets all requirements and reference other documents that verify the design meets specific requirements (e.g. reliability analysis).

CDRLS: A028 and A051

1.15 PROGRESS REPORTS. The Contractor shall submit a monthly Progress Report that reflects the technical and schedule status of the effort. The Progress Report shall contain the following information:

1.15.1 Planned efforts: The Contractor shall provide a copy of the updated IMS reflecting delivery in accordance with the contract delivery schedule.