RFP_Conformed.docx

N00024-17-R-5369

Section B - Supplies or Services and Prices

CLIN Number 0001

MK 5 Velocimeter

FFP

First Article Units (FAU) See Note A

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

PURCHASE REQUEST NUMBER: N0002415NR43624

NET AMT

CLIN Number 0002

DATA

FFP

Data for Items 0001, 0101, and 0102 (See DD Form 1423, Exhibit A). Not separately priced – Price included in the price of Items 0001, 0101, and 0102.

NET AMT

CLIN Number 0101

MK 5 Velocimeter

FFP

See Notes B and C NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

NET AMT

CLIN Number 0102

Software

FFP

See Notes C and D

NET AMT

CLAUSES INCORPORATED BY FULL TEXT

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-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-0022 CONTRACT SUMMARY FOR PAYMENT OFFICE (FIXED PRICE) (FEB 1997)

This entire contract is fixed price.

Note A: The Government plans to award up to two firm-fixed price contracts for CLIN 0001. CLIN 0002 is NSP and is included in the cost of CLIN 0001.

Note B: Phase II refers to CLIN 0101 which will be a down-select option to only one vendor from the vendor(s) who are selected for Phase I.

Note C: Option Item 0101 and 0102, to which the option clause in Section I is applicable, are to be supplied only if and to the extent said options are exercised. The Government is not obligated to order any or all of these items. Exercise of one option will not obligate the Government to the exercise of other options.

Note D: The Government may wish to exercise the option to procure unlimited rights to the software code under CLIN 0102. The Government would have the option to award CLIN 0102 following Phase II.

Section C - Descriptions and Specifications

STATEMENT OF WORK

MK 5 MOD 0

Velocimeter Replacement

GENERAL STATEMENT OF WORK

This Statement of Work defines the effort required for the design, construction, testing, configuration, and program management for the acquisition for MK 5 MOD 0 Velocimeter Replacement Systems. A two-phased procurement approach will be utilized. Phase I includes CLIN 0001 and CLIN 0002. Phase II includes OPTION CLIN 0101, as well as OPTION CLIN 0102. Since the Government intends to award up to two contracts under Phase I of this solicitation and will down-select to exercise a single awardee’s Phase II CLIN, Attachment 5 contains all of the down-select criteria the Government will consider in determining which awardee’s Phase II CLIN to exercise, if the Government decides to exercise any Phase II CLINs.

SCOPE

1.1 Description

The Department of the Navy’s Naval Sea Systems Command (NAVSEA) Headquarters (HQ) is intending to procure an instrument capable of measuring velocity of 5-inch projectiles, as fired from a Mark (MK) 45 MOD 2 (54-Caliber) or MOD 4 (62-Caliber) Gun Mount (GM) aboard United States Navy (USN) ships and controlled by the MK 160 Gun Computer System (GCS). The proposal shall be from companies interested in design, development, and production of a new system. The instrument shall be a replacement of the existing Velocimeter MK 5 MOD 0, hereafter referred to as the MK 5 Velocimeter System.

This Statement of Work (SOW) describes the requirements for the design, manufacture, assembly, test, delivery, and acceptance of a velocimeter meeting the requirements of this SOW. The government requires delivery of First Article Units (FAU) for acceptance testing to prove that the FAUs meet all requirements of the SOW and Weapon Specification. After government testing has been completed, the Contractor will adjudicate any deficiencies found during Government test. The Contractor shall correct any deficiencies under the scope of CLIN 0001. The Government will not accept the FAUs under CLIN 0001 until they have met all testing requirements. Based on the results of testing, the government may exercise Option Item 0101 (Phase II) to procure additional production units, as described in Attachment 5.

1.2 Background

The Government will consider all solutions that can meet the requirements as defined in this SOW. The current system, the MK 5 Mod 0 Velocimeter, is a Radio Frequency (RF) Doppler radar, installed on all USN and U.S. Foreign Military Sales (FMS) Gun Computer System (GCS) MK 160 variants deployed aboard Arleigh Burke Class Destroyers (DDG 51) and Ticonderoga Class Cruisers (CG 47) ship classes. The current MK 5 MOD 0 Velocimeter design is a single unit that consists of an antenna, RF transmitter, receiver, and electronics required to measure and process muzzle velocity of the fired 5-inch projectile. It is mounted externally on the non-recoiling section of the gun barrel, to measure and provide muzzle Initial Velocities (IVs) of the fired projectiles to the GCS via a bi-directional RS-232 serial link.

The current Velocimeter has two basic operating modes, passive trigger and active trigger.

a. Passive Trigger Mode: The Velocimeter automatically senses the gun shock, turns on its RF signal, and measures the projectile muzzle velocity. Once the measurement is completed, it shuts off the signal until the next shot.

b. Active Trigger Mode: Active trigger mode has two submodes, manual and automatic.

1. Manual Active Trigger Submode: The Velocimeter’s RF signal is commanded on by the GCS, via a RS-232 interface. The Velocimeter shuts off its RF signal once the measurement is completed.

2. Automatic Active Trigger Submode: The Velocimeter’s RF signal remains on continuously until turned off by the GCS.

After a power-on or system self-test, the Velocimeter monitors the ambient noise on each of its five operating RF channels and automatically selects the frequency which has the least noise. This capability allows multiple Velocimeters to operate in close proximity without interference. The Velocimeter is capable of measuring velocity between 20-2,000 meters per second (m/s) at a firing rate of up to 100 rounds per minute. The current Velocimeter weighs approximately 18 lbs, it is mounted externally on the non-recoiling section of the gun barrel, and its dimensions are 12.75"(H) x 9.25" (W) x 4.5" (D). For bolt pattern on mounting bracket, see ICD 6298126.

2.0 applicable documents

The following documents in effect at the time of the Request for Proposals (RFP) form a part of this SOW to the extent specified herein.

2.1 Military Specifications, Standards and Handbooks

MIL-D-23140D

Drawings, Installation Control, for Electronic Equipment

MIL-P-24534A

Planned Maintenance System: Development of Maintenance Requirement Cards, Maintenance Index Pages, and Associated Documentation

MIL-DTL-24784/22

Technical Content Development Requirements For Combat System Technical Operations Manuals (CSTOMs); Hull, Mechanical, And Electrical (HM&E) System And Equipment Manuals; Electronic [Including Service Test Electronic, Experimental Electronic And Interior Communication (IC)] System And Equipment Manuals; And Weapon Systems And Weapon Equipment Manuals

MIL-DTL-24784/23

Illustrated Parts Breakdown (IPB) Requirements

2.2 Engineering Documentation

WS-35463

System Specification for the Gun Weapon System MK 34 with Gun Computer System MK 160 for the United States Navy Aegis Modernization Advanced Capability Build 12 Cruisers and Destroyers

WS-32820A

Interface Design Specification (IDS) for Velocimeter Mk 5 Mod 0 and GCS Mk 160 Mods 4 and Follow

2.3 Commercial and Industry Specifications

ANSI/ISO/ASQC Q9001-2000

American National Standard Institute, Quality Management Systems Requirements Standard

ANSI/ISO/ASQC Q9000-1-1994

American National Standard Institute, Quality Assurance for the Chemical and Process Industries

ASME Y14.24

Types and Applications of Engineering Drawings

2.4 Availability of Specifications and Standards

Copies of Military specifications, standards, handbooks, and guidance data listed are available from the ASSIST website at https://assist.dla.mil/.

Copies of Government documents other than specifications, standards, and handbooks may be obtained through PEO IWS 3.0.

Copies of non-Government publications should be requested from the organization(s) that prepare, maintain, and distribute the documents.

2.5 Order of Precedence

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence to all except System Specification for the Gun Weapon System MK 34 with Gun Computer System MK 160 for the United States Navy Aegis Modernization Advanced Capability Build 12 Cruisers and Destroyers, WS 35463. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3 REQUIREMENTS

CLIN 0001 will be for the vendor(s) to provide 3 First Article Units (FAUs) NLT 6 months of Phase I contract award that can meet all requirements of the SOW and Weapon Specification proven through Government acceptance testing at NSWC Dahlgren. CLIN 0101 will be an option to build 50 production units identical to their delivered FAUs to only one of the vendors selected to build FAUs in CLIN 0001.

3.1 System Requirements (ITEMs 0001 and OPTION ITEM 0101)

The Contractor shall develop, produce, test, and deliver a replacement for the existing MK 5 MOD 0 Velocimeter that meets the requirements as specified in WS-32820A and this SOW. The government requires the Contractor to keep the same bolt pattern as provided in ICD6298126 and to meet the current physical description within the tolerances described in Section 3.2.

Prior to Contract award, the Contractor shall allow the Government to conduct a site survey to demonstrate that the Contractor has the facility and personnel to accomplish the requirements in this SOW.

3.1.1 First Article Units

Prior to the establishment of the product baseline, the Contractor shall deliver Velocimeter FAUs that meet the requirements as specified in WS-32820A and this SOW. First Article Acceptance Testing will be performed at NSWC Dahlgren to prove that the FAUs meet all requirements. If the FAUs do not pass all testing, report will be sent back to the vendor with the opportunity to update the deficiencies. FAUs will not be accepted if they do not pass all testing at NSWC Dahlgren. The FAUs shall be used to complete all Design Verification Testing required by this SOW.

3.1.2 Technical Reviews

The Contractor shall participate in Technical Reviews with the Government. The Contractor shall include in its IPMR a formal Technical Review schedule including milestones and the key events for the MK 5 Velocimeter System. The Technical Reviews will include the following:

a. Identify and confirm the configuration item baseline for the MK 5 Velocimeter System.

b. Identify all planned modifications to the Non-Development Item (NDI) Configuration Item (CI) baseline and all planned modification to each CI.

c. Identify the Computer Software Configuration Items (CSCI) to be used in the MK 5 Velocimeter System.

d. Review the CM program for hardware and software.

e. Review plans for the system qualification testing.

f. Verify all qualification requirements of the System Requirement.

Entrance and exit criteria for Design Reviews shall be developed in accordance with Program Executive Officer (PEO) Integrated Warfare Systems (IWS) Technical Review Manual (TRM) Version 2.0 dtd 18 December 2009. Design review criterion are tailorable upon request by the Contractor and require approval by the Government, however, the requirements set forth in WS 32820A, this SOW, and the contract remain in effect without exception. The proposed design review schedule shall include a Design Review one month after contract award and a Test Readiness Review (TRR) one month prior to the delivery of the FAUs and a Physical Configuration Audit (PCA) after the delivery of the FAUs. The Government will be responsible for final acceptance testing against requirements.

(CDRL A023)

3.1.3 Product Baseline

The product baseline is a production ready, shipboard ready MK 5 Velocimeter, which will be fully tested and integrated into the MK 34 GWS by NSWC Dahlgren. This will be verified during the First Article Testing that it meets all requirements described in the SOW.

3.1.4 Production Units (CLIN 0101)

All Velocimeter production units procured shall be built to the product baseline, once it has been established after successful completion of Design Verification Testing and Physical Configuration Audit (PCA) of the FAUs, as specified in Section 3.9.1 of this SOW.

(CDRL A001)

3.2 Design/Performance Requirements

As a replacement of the MK 5 MOD 0 Velocimeter, the MK 5 Velocimeter System shall be capable of measuring the muzzle velocities during day and night under environmental conditions defined in section 3.2.3 of this SOW. The system, upon power-up and initialization, shall be capable to as a minimum:

a. Built to the same size and utilizes the same bolt pattern according to ICD 6298126. Capable of operating in two basic modes: passive trigger and active trigger as described in section 1.2

b. Capable of monitoring five operating RF channels and automatically selects the frequency which has the least noise

c. Perform self-test upon initialization, or when commanded, and report the statuses

d. Accept and retain the system applicable setup parameters, even after being powered down, until subsequent request

e. Accept expected velocity range input and discard Initial Velocity (IV) out of range

f. Measure velocity between 20-2,000 m/s and at a firing rate of up to 100 rounds per minute

g. Automatically detect when the gun is fired and measure the projectile IV with an accuracy of ±0.305 m/s

h. Report IV or No Data for each shot

i. Store IVs and shot numbers in the non-volatile memory for up to 1,000 shots for later use

j. Report stored IVs with associated shot numbers, when commanded

k. Delete individual IV or all IVs from memory, when commanded

l. Disable/Enable radiated emissions, if applicable, when commanded

m. Report fault(s), when occurred

n. Report software version and perform software update, when commanded

o. Perform diagnostic tests, when commanded

p. Reset system setup parameters to default values, when commanded

q. Return acknowledgement for each received command/message

r. Reliability: Mean Time Between Failure (MTBF) > 4,500 hrs

s. Maintainability: Mean Time To Repair (MTTR) < 8 hrs

t. Operational Availability: Ao ≥ 0.8

3.2.1 Interface Requirements

The MK 5 Velocimeter System shall be configurable to support communication with the MK160 GCS via the following interface:

RS-232 Serial Interface – existing GCS systems interface operates asynchronously at 9600 baud with eight data bits, one stop bit, and no parity bits comprising each byte transferred. Three signal lines are used: (1) Transmitted Data, (2) Received Data, and (3) Signal Ground. The communication protocol and all exchanged messages through this interface are defined in the IDS for Velocimeter MK 5 MOD 0 and GCS MK 160 MOD 4 and follow, WS-32820A, REV A.

An all-weather, waterproof, totally sealed connector designed to meet the environmental requirements in section 3.2.3 shall be used for the interface. The connector shall have the signal pin-out as specified in the following table, and mate with a female connector having a MK 45 GM part number of DG123A6R15-97S1.

3.2.2 Operating Radio Frequencies

The operating frequencies shall be compliant with international and national spectrum allocations and regulations and shall be spectrum supportable worldwide. The MK 5 Velocimeter System shall also:

a. Have an approved Frequency Allocation Document (DD Form 1494) with a JF-12 number and shall be delivered to the government. www.dtic.mil/whs/directives/forms/eforms/dd1494.pdf

(CDRL A027)

b. Comply with MIL-STD-461F and MIL-STD-464C.

Note: Having a Federal Communications Commission (FCC) ID is not a replacement or substitute for (a). When more than one system is in operation with a single GCS, as in a two gun Cruiser, the MK 5 Velocimeter Systems shall not interfere with each other.

3.2.3 Environmental Requirements

The MK 5 Velocimeter System shall survive without damage when subjected to the following conditions while in a non-operating condition:

a. Complete immersion in seawater in accordance with MIL-STD-108E Notice 2, and returning to service after removal from the water.

b. Exposure to winds having a relative velocity of up to 100 knots.

c. Exposure to storage temperature from -50°F to 150°F.

The MK 5 Velocimeter System shall be capable of operating without defect when subjected to the following environmental conditions:

· MIL-S-901D, Grade A shock, otherwise.

· MIL-STD-167/1A, Type I vibration, 0 to 25 Hz, otherwise.

· Exposure to wind driven dust 1-10 microns, 70 ppm.

a. 50 V/m for frequency from 14 KHz to 2 MHz.

b. 200 V/m for frequency from 2 MHz to 25 GHz.

3.2.4 Safety Requirements

The MK 5 Velocimeter System shall satisfy the following safety requirements.

a. Fail-Safe Feature – A loss of interface or power shall not create any dangerous condition to personnel or cause damage to the Velocimeter or MK 45 Gun Mount equipment.

b. Radiation Hazard – The MK 5 Velocimeter System shall be designed to prevent exposure of shipboard personnel to RF radiation in excess of the exposure limits specified in American National Standards Institute Standard (ANSI STD) C95.1, Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 300 KHz to 100 GHz, 1991.

c. Hazards of Electromagnetic Radiation to Ordinance (HERO) – The MK 5 Velocimeter System shall not produce an electromagnetic environment that causes safety or reliability degradation of any ordnance and shall be IAW NAVSEA OP 3565/NAVAIR 16-1-529/NAVELEX 0967-LP-624-6010, Electromagnetic Radiation Hazards (Hazards to Personnel, Fuel, and other Flammable Material)

d. Toxic or Corrosive Materials and Compounds – Materials that would produce harmful toxic effects, emit corrosive substances, or induce corrosion within an assembly due to exposure to credible environmental extremes or operating conditions shall not be used without prior approval of the Government.

3.3 Software Requirements

The Contractor shall be responsible for the development, maintenance and/or delivery of computer software products for the MK 5 Velocimeter System. The computer software products include at least the source code, executable code and associated software documentation. Any and all technical data and computer software submitted by the contractor as required under paragraph 3.6, shall be provided to the government with government purpose rights in accordance to the applicable data rights clauses of this contract.

3.3.1 Software Development

The Contractor shall develop and maintain the software for the MK 5 Velocimeter System. The software shall comply with the Interface Design Specifications, WS-32820 REV A. The Contractor shall prepare and submit a Software Development Plan (SDP) defining the software efforts and tasks required for this contract.

(CDRL A002)

3.3.2 Software Development Testing

The Contractor shall fully test the MK 5 Velocimeter System software at the unit and at the system level prior to delivery of each MK 5 Velocimeter System, and for each software release during the life of the contract. All tests shall be documented in the SDP and maintained by the Contractor as part of the program records for use in reviews and reports.

(CDRL A002)

3.3.3 Contractor Software Configuration Management

The Contractor shall maintain a Configuration Management Plan (CMP) for the software of the MK 5 Velocimeter System. The management of data shall be documented and maintained by the Contractor as part of the program records. The Contractor may use their own processes or procedures however the CMP shall address the following Configuration Management process requirements: Configuration Management Phasing and Milestones, Configuration Identification, Interface Management, Configuration Control, Configuration Status Accounting, Functional and Physical Configuration Audits, Data Management, Configuration Management Library, Configuration Management Resources, Configuration Management Metrics.

(CDRL A021)

a. Configuration Management Phasing and Milestones shall describe the sequence of events and milestones for implementation of configuration management in phase with major project milestones and events, including at a minimum the establishment of Functional, Allocated and Product baselines

b. Configuration Identification shall be established for the identification of CIs and their versions to be controlled for the project. For each CI and its versions, the following shall be identified: the documentation that establishes the baseline, the version references, and other identification details to include but not limited to Naming Convention, how the code, documentation and date of identified baselines are physically controlled and tracked in the projects configuration management libraries.

c. Software Configuration Identification shall be established for the identification of software configuration components, scripts, configuration files, and any other elements required to build a software configuration from source code. For each software configuration item and its versions, the following shall be identified: the documentation that establishes the baseline; the version references of that software configuration item; and the version and date of each software component of that software configuration item.

d. Interface Management shall be defined to establish requirements for internal and external interfaces ensuring accountability and timely dissemination of changes.

e. Configuration Control shall be performed: identification and recording of change requests; analysis and evaluation of the changes; approval or disapproval of the request; and implementation, verification and release of the modified software item. An audit trail shall exist, whereby each modification, the reason for the modification, and authorization of the modification can be traced. Control and audit of all accesses to the controlled CIs that handle safety or security critical functions shall be performed.

1. Requesting a Change shall describe the procedures that have been established for requesting changes to baseline CIs for the project. Established reporting forms may be used to request a change. As a minimum, the information necessary for proposing a change shall contain the following:

i. Date of initiation

ii. Originator of request

iii. Scope

iv. Subject

v. Identification of requested item, service or response

vi. Detailed description of requested item, service or response, including suspense date

vii. Justifications

2. Evaluating the Change shall specify type of analysis conducted to determine the impact of the proposed change and the review procedures necessary to accomplish the analysis. Potential threats and vulnerabilities regarding the management of any mobile code technologies that have an impact on the operability or functionality of the system must be identified and described.

3. Approving or Disapproving the Change shall describe the functions of configuration management boards (i.e. Configuration Control Board (CCB) or Functional Review Board (FRB)) and the level of authority for approving a proposed change. A CCB may be an individual or a group. NOTE: The procedures established for approval or disapproval of changes not requiring a CCB or FRB (i.e. the Project Manager approves Class II, etc.) must also be documented in this area.

4. Implementing the Change shall describe how an approved change request is implemented into an existing base lined CI, to include information addressing how all applicable mobile code software will be implemented with the change. The minimum information necessary for completing a change shall contain the following:

i. The associated change requests

ii. Names and versions of the affected items

iii. The identifier of the new version

iv. Verification date and responsible party

v. Installation date and responsible party

5. Configuration Status Accounting shall describe the management records and status reports that show the status and history of controlled items including software baseline shall be prepared and delivered (A026). Status reports should include the number of changes for a project, latest software item versions, release identifiers, the number of releases, and comparisons of releases.

6. Release Management and Delivery: The release and delivery of software products and documentation shall be formally controlled. Master copies of source code and documentation shall be delivered to the government and maintained by the contractor for the duration of this contract. The source code and documentation that contain safety or security critical functions shall be handled, stored, packaged, and delivered in accordance with the government's requirements. There shall be no release of software to a third party without Government approval.

(CDRL A021)

f. Configuration Status Accounting shall describe the management records and status reports that show the status and history of controlled items including software baseline shall be prepared. Status reports should include the number of changes for a project, latest software item versions, release identifiers, the number of releases, and comparisons of releases.

g. Configuration Audits shall be performed to verify that the software product is built according to the requirements, standards and contractual agreement. The audit process will verify that all software products have been produced and correctly identified, and that all changes requests have been resolved. The completeness and correctness of the changes to the baselines also should be verified to ensure that the changes were implemented as intended.

1. The information listed below must be defined prior to conducting an audit:

i. Objective of audit or review

ii. CIs to be audited or reviewed

iii. Audit or review schedule of events

iv. Procedures for conducting the audit or review

v. Participants involved

vi. Necessary documentation required to be reviewed or to support the audit or review

vii. Method of identifying discrepancies and reporting corrective actions

viii. Approval criteria and specific actions required

h. Configuration Management Library shall describe the number and types of configuration management libraries, from physical to automated, that will control and maintain the various types of software products associated with software development.

i. Configuration Management Resources shall describe the configuration management tools, techniques, equipment, personnel and necessary skills, and training required for implementing a sound project configuration management discipline.

j. Configuration Management Metrics shall describe the type of metrics to be collected at the project level, frequency of collection, and reporting requirements.

3.3.4 Software Acceptance

The Government will accept the released software executables and source code and control the CM upon successful completion of software validation and verification. The Contractor shall provide a copy of the accepted software, source code, and a Software Installation Plan (SIP). The Contractor shall provide a test plan and report verifying all requirements documented in the SOW were tested and the results of the test. Test pass/fail criteria shall be included in the test plan prior to testing, and clearly traced to the SOW. The Contractor shall also provide instructions and identify equipment required for the Government to perform the software loading.

(CDRL A025)

3.3.5 Software Delivery (OPTION ITEM 0102 only)

The Contractor shall provide the Government unlimited data rights to all software code to develop, operate, and maintain the MK 5 Velocimeter system as well as all the computer software products associated with the MK 5 Velocimeter System. The computer software products include at least the source code, executable code and associated software documentation. Any and all technical data and computer software submitted by the contractor as required under paragraph 3.6, shall be provided to the government with unlimited rights

3.4 General Requirements

All requirements apply to CLIN 0001. If exercised, CLIN 0101 may require an update to the IMS to ensure on time delivery. All other requirements of Option CLIN 0101 will be identical to CLIN 0001.

3.4.1 Program Management

The Contractor shall develop and implement a program management process which shall govern the execution of this contract. Program management tasks and objectives shall encompass all work initiatives necessary to execute, administer, and integrate the collective efforts necessary to satisfy the Contractor’s obligations under the contract. The Contractor shall identify an overall Program Manager (PM) as the Contractor’s single point of contact for communication throughout this program.

3.4.2 Integrated Master Schedule

The Contractor shall develop and maintain an Integrated Program Management Report (IPMR) that addresses the execution and performance of this contract. The IPMR shall be developed and maintained using Microsoft Project (version 2000) compatible software. The information developed for the IPMR shall reflect the Contractor’s Work Breakdown Structure (CWBS) as well as any other actions integral to meeting the overall contract and delivery requirements.

(CDRL A003)

The IPMR shall be the principal document for program management. The Contractor, via the IPMR, shall identify critical events, milestones, schedules and test requirements to monitor program risk. The Contractor shall coordinate efforts with the Government to perform a continuing assessment of the schedule and technical performance of the contract against the IPMR. The critical events, milestones and schedules in the IPMR shall be updated two weeks prior to each program progress review or technical review associated with the performance of this contract.

(CDRL A003)

The Contractor shall design, develop, and provide the 3 FAU MK 5 Velocimeters within 6 months of award of CLIN 0001; and, if CLIN 0101 is exercised the Contractor shall provide the first production unit within 6 months and one unit per week for each subsequent delivery after the MK 5 Velocimeter product baseline is created.

3.4.3 System Safety

The Contractor shall comply with the requirements of MIL-STD-882E.

3.4.3.1 Environmental Hazard Analysis

The Contractor shall avoid the use of hazardous materials in the fabrication, production, operation, and support of the MK 5 Velocimeter System. The Contractor shall develop, implement and manage a Hazardous Material Management Plan (HMMP) in accordance with NAS 411. HMM data submitted will be in accordance with NAS 411. The Contractor's HMM process and status will be discussed at the Technical Reviews during the scheduled reviews listed in 3.4.3. The avoidance effort shall continue throughout the Contractor’s period of performance of this contract. Use of hazardous materials in the MK 5 Velocimeter System requires Government approval prior to implementation.

(CDRL A024)

3.5 Specific Provisioning Data

The contractor shall provide provisioning data via the Interactive Computer Aided Provisioning System (ICAPS) software. ICAPS software may be downloaded from the ICAPS web site at https://icaps.dc3n.navy.mil/. The provisioning data shall include:

a. Technical Replacement Factor/Best Replacement Factor

b. Lead Time, production and/or procurement

c. Shelf Life Code

d. Shelf Life Action Code, if applicable

e. Precious Metal Indicator Code, if applicable

f. Contractor and Government Entity (CAGE) Codes

g. Original Equipment Manufacturer and Contractor’s Control Part Numbers

h. Item Name (descriptive name)

i. Price of item (as negotiated)

j. Dimensions (Length, height, width, and weight)

k. Reference Number (Exhibit Number, Control Number or ODS number)

l. Provisioning Line Item Sequence Number (PLISN)

m. Indenture Code

n. Reference Number Category Code (RNCC)

o. Reference Number Variation Code (RNVC)

p. Recommended Source, Maintenance and Recoverability Code (SM&R Code)

q. Failure Factor/Minimum Replacement Unit (MRU)

r. Unit of Issue

s. Mission Essentiality Code (MEC)

t. Quantity per Unit

u. Quantity per Assembly

v. Depot Overhaul Point (DOP)

w. Remain in Place code (RIP)

x. Repair Survival Rate (RSR)

y. Bill of Materials

z. Maintenance Task Analysis to include MTBF (Mean Time Between Failure) for major sub-components

(CDRL A004)

3.5.1 Provisioning Technical Documentation

The Contractor shall provide Provisioning Technical Documentation (PTD) for Commercial Off-The-Shelf (COTS) items, NDI, modified equipment and any Special Purpose Tools and Test Equipment (if used) that constitute the MK 5 Velocimeter System. The PTD data shall include the following:

a. Provisioning Parts List

b. Short Form Provisioning Parts List (if applicable)

c. Long Lead Time Items List

d. Repairable Items List

e. Interim Support Items List

f. Tools and Test Equipment List (general and special)

g. Common and Bulk Items List

h. Design Change Notice

i. Post Conference List

j. System Configuration Provisioning List

(CDRL A004)

Supplementary Provisioning Technical Documentation (PTD) shall include commercial drawings and manuals, engineering drawings, vendor catalog data, or vendor specification data sheets. The Contractor shall assemble and provide this data to serve as the basis for the required provisioning tasks.

(CDRL A005)

3.6 Technical Data

The Contractor shall prepare, assemble, and maintain a data package documenting the design, physical and functional characteristic, and external (physical) interface of the MK 5 Velocimeter System. The data package shall include an operational block diagram, product data sheets, engineering drawings and documentation, Installation Control Drawings (ICDs), parts lists, sparing information, technical manual data, and Maintenance Requirements Cards (MRCs) as detailed in the following paragraphs. In addition to any other delivery requirements, the Contractor shall deliver the data package at the Design Review and at the Physical Configuration Audit. Any and all technical data submitted by the contractor as required under paragraph 3.6, shall be provided to the government with rights in accordance to the applicable data rights clauses of this contract.

3.6.1 Technical Data Package

The Contractor shall prepare, assemble, and maintain a Technical Data Package (TDP) for the MK 5 Velocimeter System in accordance with MIL-STD-3100A.

(CDRL A006)

3.6.2 Interface and Installation Control Drawings

The Contractor shall prepare product level documentation describing all physical and software interfaces, installation details, and assemblies of the MK 5 Velocimeter System to the host platform in accordance with ASME Y14.100-2013 and Section 5 of ASME Y14.24-2012, and paragraph 3.3.8 of MIL-D-23140D shall be used for guidance on the content of ICDs. The Government will provide individual drawing number assignments and identification for the ICD(s).

(CDRL A007)

3.6.3 Engineering Manual

The Contractor shall prepare documentation of the MK 5 Velocimeter System suitable for inclusion in the GCS MK 160 technical manual.

(CDRL A008)

3.6.4 Maintenance Requirements

Using MIL-P-24534A as a guideline, the Contractor shall develop maintenance requirements inputs for the MK 5 Velocimeter System and deliver them to the government at the TRR.

(CDRL A009)

3.7 Testing, Inspection, and Acceptance Criteria

3.7.1 Quality Conformance Inspection and Test Procedures

The Contractor shall verify conformance of the MK 5 Velocimeter System design with the requirements specified in the SOW. Prior to acceptance of the first FAU, the unit must pass performance and GWS integration testing at Naval Surface Warfare Center Dahlgren Division (NSWCDD) land based site and all environmental tests. The Contractor shall support this integration testing by transporting the unit to and from the test site, installing and removing it, and providing technical support to resolve any issues encountered during testing. The contractor shall notify the government in writing when the FAUs are ready for testing. Within 60 days of the notification, the FAUs will be tested at Dahlgren. The FAUs will not be accepted unless they meet all requirements/pass all tests at Dahlgren.

(CDRL A010)

3.7.2 Design Verification and Qualification Test Report

The Contractor shall deliver a report documenting each examination, test, demonstration, and analysis performed and the test result. When all verifications are successfully completed, the Contractor shall deliver a summary test report summarizing all examinations, tests, demonstrations, and analyses performed and their results. No FAUs will be accepted by the Government until the summary test report has been reviewed and approved by the Government.

(CDRL A011)

3.7.3 Acceptance of First Article Units

FAUs that successfully meet the verification testing requirements are to be offered to the Government for acceptance.

3.7.4 Environmental Stress Screening Procedures and Implementation Plan

The Contractor shall conduct Environmental Stress Screening (ESS) on all units as a complete assembly. The ESS shall be conducted on one unit at time with the unit under power at a temperature range of -50°F to 130°F and temperature rate of change 10°F per minute and random vibration at:

a. Spectral Density - 6G

b. Frequency Limits - 100-1000 Hz

c. Axis - 3

d. Duration - 18 minutes Each unit must successfully complete the requirements of ESS before factory acceptance test is performed. The Contractor shall develop the ESS procedures and implementation plans, and shall address occurrence of failures and the process for rescreening of units. Government approval of the procedures and plans is required prior to implementation. An ESS report for each test shall be developed to document ESS results and all problems encountered during ESS. The ESS report shall also address unit failures and develop proposed resolution(s) prior to rescreening of units.

(CDRL A012 and CDRL A013)

3.7.5 Acceptance Testing

The Contractor shall develop and deliver to the Government their Test and Inspection Acceptance Procedure for Government approval. Each FAU and production unit must pass acceptance testing in accordance with the Government-provided acceptance test plan that will be conducted at Dahlgren. The Contractor’s Test and Inspection Acceptance Procedure should adhere to the Government-provided acceptance test plan. A test report shall be submitted to the Government for each unit tested concurrent with the delivery of the unit to the Government. All acceptance testing will be witnessed by the Government. The Contractor shall provide notice to the Government, at minimum, ten (10) working days prior to all units are ready for testing. Scheduling of testing may need to be done up to 60 days prior to testing date.

(CDRL A014 and CDRL A015)

3.7.6 Environmental Qualification Test Procedures and Reports

The Contractor shall develop and deliver to the Government the system Environmental qualification test procedures for approval. Environmental qualification tests shall be the verification of the MK 5 Velocimeter Systems physical and functional characteristics, when subjected to environments specified in the System Requirements. The contractor shall provide an environmental qualification test report to summarize all environmental tests as required by WS-32820A and this SOW.

(CDRL A016 and CDRL A017)

3.8 Quality Assurance

The Contractor’s quality system model shall be compliant with the ANSI/ISO/ASQC Q9001-2000. The Contractor may utilize their existing quality system by demonstrating to the Government, compliance to ANSI/ISO/ASQC Q9000. Documentation for COTS/Non Developmental Item (NDI) quality assurance shall be delivered to the Government in order to track the total Bill of Materials of the system.

(CDRL A026)

3.9 Configuration Management

3.9.1 Physical Configuration Audit Report

The Contractor shall conduct, with Government participation, a Physical Configuration Audit (PCA) and provide a report of the MK 5 Velocimeter System design. The PCA shall be conducted within two weeks after the acceptance of the FAUs. The PCA shall consist of a successful execution of the accepted Test and Inspection Procedure and a review of all relevant documentation (e.g., test documents, test results, verifications, examinations, drawings, etc.) pertinent to physical and functional characteristics not demonstrated by the Test and Inspection Procedure. The results of the PCA shall be documented. The successful completion of the MK 5 Velocimeter System PCA will establish the product baseline for the MK 5 Velocimeter System to be placed under formal Government configuration management for production units. MIL-HDBK-61B may be used for PCA guidance.

(CDRL A018)

3.9.2 Manufacturing Configuration Non-Conformance Report

The Contractor shall document and report all configuration non-conformances no later than seven (7) days after discovery for production baselined units including accepted FAUs. All configuration non-conformances shall be documented against the Product Baseline using the Contractor’s established configuration management system. Government approval is required for all configuration non-conformances that take place under this contract. The non-conformances shall be documented and reported to the Government for review and acceptance prior to implementation of the non-conformance into the MK 5 Velocimeter System configuration.

(CDRL A019)

3.9.3 As Built Configuration List

The Contractor shall generate and deliver an As-Built Configuration List (ABCL) for each MK 5 Velocimeter System pre-production/production unit produced under this contract. The ABCL shall identify the specific serial number and list the configuration of the MK 5 Velocimeter System as delivered (to the third indenture level) to the Government. Serialized COTS items listed on the ABCL shall include serial numbers. The ABCL shall include a listing of Government approved configuration non-conformances incorporated, at sub-assembly level and up, into the unit. Delivery of the ABCL shall be concurrent with each unit delivered. The Contractor shall coordinate with the Government for proper sequencing of serial numbers.

(CDRL A020)

3.9.4 Lowest Replaceable Unit Level Bills of Material

The Contractor shall develop, maintain, and deliver Lowest Replaceable Unit (LRU) Level Bills of Material to enable the identification, forecasting and management of piece part obsolescence impacts and mitigation. The Contractor shall also develop, maintain, and deliver LRU Component Level Bills of Material for any Contractor developed or modified (i.e., non-COTS) LRUs.

(CDRL A022)

4. ITEM 0002 Data

Contract deliverables shall be delivered to the Government in ISO 32000 Portable Document Format without content protection, unless otherwise specified herein. All computer files shall be delivered on CD or DVD and may, at the Contractor’s option, also be delivered electronically. Exceptions may be approved by the Government. Contract Data Requirements (CDRLs) will be required in accordance with DD Form 1423. The CDRL list is listed below.

HQ C-1-0001 ITEM 0002 - DATA REQUIREMENTS (NAVSEA) (SEP 1992)

The data to be furnished hereunder shall be prepared in accordance with the Contract Data Requirements List, DD Form 1423, Exhibit(s) A001-A027, attached hereto.

HQ C-1-0007 PROVISIONING TECHNICAL DOCUMENTATION (NAVSEA) (FEB 1994)

The Provisioning Technical Documentation (PTD) shall be in accordance with the Provisioning Requirements Statement (PRS), including NAVSEA…