N68335-17-R-0068.docx

N68335-17-R-0068

Section A - Solicitation/Contract Form

GENERAL INFORMATION

Proposals under NAWCADLKE’s Request for Proposal (RFP) number N68335-17-R-0068 shall be submitted prior to XX July 2017 1:00pm EST Naval Air Warfare Center Aircraft Division Hwy 547 Bldg. 120 Room 180 Attn: Evanuel Hairston

JBMDL, NJ 08733

The Offeror shall provide its DD 2345 to Evanuel Hairston at evanuel.hairston@navy.mil to receive Attachments, 1, 3, and 4, Control Indicator Control Monitor (CICM) Hardware Processing Platform Requirements Specification Figure 1 and Figure 2. The Offeror shall provide its current mainlining address to receive Attachments 1,3, and 4.

Section B - Supplies or Services and Prices

Control Indicator/Control Monitor

FFP

Prototype 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: 1300579748

NET AMT

FFP

Prototypes for Government Environmental Testing 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

FFP

Prototypes for Contractor Environmental Testing 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

Contracts Data Requirements List

FFP

Not Separately Priced

NET AMT

Section C - Descriptions and Specifications

STATEMENT OF WORK

STATEMENT OF WORK

INTEGRATED CONTROL INDICATOR/CONTROL MONITOR (CI/CM)

SOLUTION

1.0 BACKGROUND: NAWCAD 4.11.2 provides support and expertise for the AN/UPX-29(V) Interrogator System of which the AN/UPX-24(V) Interrogator Set is a component. The AN/UPX-24(V) set includes the Control Indicator (CI) C-10064 and the Control Monitor (CM) C-10065 which provide remote access and control to the AN/UPX-24(V). The design of the current CI and CM components is not flexible and subsequently cannot be configured to support new Mode 5 and Mode S Identification Friend or Foe (IFF) capabilities.

1.1. SCOPE: NAWCAD 4.11.2 requires the integration of the two separate CI and CM components into a single box that is software configurable to operate as either the CI or CM. NAWCAD 4.11.2 requires the delivery of quantity one (1) integrated CI/CM prototypes and the Technical Data Package (TDP) of the integrated CI/CM with the option for the Contractor or the Government to perform Environmental Testing on an additional quantity two (2) integrated CI/CM prototypes. The determination of who does the Environmental Testing will be made approximately 30 days after contract award. The integrated CI/CM must be able to convert from the CI configuration (vertical) to the CM configuration (horizontal) without the addition or removal of parts.

2.0 APPLICABLE DOCUMENTS

2.1. Military Specifications and Standards

2.2. Handbooks and Guides

2.3. Performance Specification

CI/CM Hardware Processing Platform Specification

2.4. Non-Government documents

3.0 DESCRIPTION OF EFFORT. The work scope includes the delivery of hardware, software, technical data documentation, shipping expenses, and a warranty period after delivery and final acceptance.

3.1. Hardware Requirements

3.1.1. The contractor shall build quantity three (3) integrated CI/CM solution prototype units. The performance of the prototypes shall be functionally equivalent to performance of deliverable production units per the specifications provided and shall maintain an equivalent form factor to deliverable production units. The prototypes must include all changes incorporated for both environmental qualification testing and Factory Acceptance Testing (FAT).

3.1.1.1 A Functional Configuration Audit of the prototypes shall be conducted to validate that the development of the configuration items has been completed satisfactorily and that the configuration items have achieved the performance and functional characteristics specified in the functional or allocated configuration identification.

3.1.1.2 A Physical Configuration Audit of the prototypes shall be conducted to verify that the configuration items “as-built” configuration conforms to the technical documentation that defines the configuration items.

3.1.2. The contractor shall develop the integrated CI/CM solution in accordance with the CI/CM Hardware Processing Platform Specification.

3.1.3. Prototype Delivery

3.1.3.1 Contractor shall deliver quantity one (1) prototype no later than 6 months after contract award

3.1.3.2 Contractor shall deliver quantity two (2) prototypes used for Environmental Testing no later than 12 months after contract award should the Contractor perform Option: Environmental Testing.

3.1.3.3 Contractor shall deliver quantity (2) prototypes no later than 6 months after contract award should the Government perform Option: Environmental Testing.

3.2. Software Requirements

3.2.1. The contractor shall license and provide installable/usable media to the government consisting of the required number of license(s) and media to support Government development, installation, and operation of Government Furnished Information, (GFI) to be supported by the contracted hardware units, (e.g. if a software component is licensed as Per-Unit fees, the contractor shall supply a sufficient quantity of licenses for the contracted hardware, whereas a software component under a one-time perpetual license shall only require one license for all contracted hardware). For development software, the Government requires sufficient licenses for (2) development workstations.

3.2.2. The contractor shall provide a Summary Delivery Report, detailing a list of all hardware and software and documentation items delivered under the contract. (CDRL A001)

3.3. Technical Data Package Requirements

3.3.1. Configuration Identification: Baseline/As-Built Configuration Data List. The contractor shall maintain and deliver a Configuration Identification Baseline Report. The Configuration Identification Baseline shall consist of an Engineering Family Tree prepared in the form of a top-down breakdown of all hardware, software and firmware items with their associated technical documentation. The Configuration Identification Baseline Report shall be prepared using EIA-649 or the contractor’s configuration management process as guidance. (CDRL A002)

3.3.2. The contractor shall deliver a Technical Data Package (TDP) to support the integration CI/CM solution that includes, but is not limited to:

3.3.2.1 Installation Control Drawings, (ICD) shall consist of outline and installation drawings detailing all physical characteristics of the major equipment components including interface and installation control drawings. The report shall identify the source of physical dimension, power and cooling requirement data (i.e., calculated or measured) and the variance of physical characteristics from requirements as specified in the performance specifications. The report shall also include cable block diagrams. It shall also include cable running sheets (including connector, mating connector, recommended backshell information). The installation documentation provided in this report shall meet the data requirements specified in MIL-D-23140D. However, contractor format is acceptable. This documentation may be submitted in the form of an Installation Control Document or equivalent. Drawing symbology, dimensioning, and tolerancing provided in this documentation shall be in accordance with ASME Y14.5M-2009 or a matrix cross referencing the deliverable drawing symbology, dimensions and tolerances to this specification can be provided. (CDRL A003)

3.3.2.2. The following is a list of requirements for all Installation Control Documents and Contractor Furnished Information necessary for development of products for Ship Design and Installation. The ICD shall follow the format below and contain the following information:

General Documentation

Physical Size

Foundation

Topside

Power

Heat Dissipation

Electrical Interfaces

Environmental

Other

3.3.3. The contractor shall deliver a Computer-Resources Integrated Support Document, (CRISD) that includes, but is not limited to (CDRL A004):

3.3.3.1 List of required software necessary for the Government to develop software and provide life-cycle maintenance of GFI software.

3.3.3.2 Source of each of the technical data or computer software included under SOW 3.2.

3.3.3.3 Whether an item is commercial or non-commercial as per DFARS Subparts 227.7100 et seq and 227.7200 et seq, and for all commercial items attach a copy of the license the Government will be offered.

3.3.3.4 Data rights to be extended to the Government.

3.3.3.5 Software licensing description for all components identified, both Commercial and Non-Commercial.

3.3.3.6 What ownership rights the contractor has to each component.

3.4. Test Documentation.

3.4.1. Environmental Test Documentation

3.4.1.1 The contractor shall prepare an environmental test plan (CDRL A005) and an environmental test procedure. (CDRL A006)

3.4.1.2 The contractor shall provide any environmental test data (analytical data or actual test data) they have for the proposed item as well as listing tests offered to be conducted as part of the proposal to be conducted by the contractor to meet the environmental requirements of the CI/CM Hardware Processing Platform Specification.

3.4.1.3 Qualification shall be by one of three methods; the first is analysis, the second is by similarity and the third is by test. The table below indicates the method of qualification that is acceptable for each requirement.

X

Below Decks Ambient Temperature – MIL-STD-810G

X

Vibration – MIL-STD-167-1A

X

Shock – MIL-S-901D

X

RF EME MIL-STD-464 Revision A Paragraph 5.3 Tables 1A and 1B

X

EMI of MIL-STD-461E (CE102, CS101, CS114, CS116, RE101, RE102, RS101, RS103)

X

X

Below Decks Humidity – MIL-STD-810G

Lightning Strike - MIL-STD-464

X

X

3.4.1.4 The contractor shall identify any environmental tests required to be performed by the government as well as how changes required to meet deficiencies identified during government conducted test of the environmental requirements will be identified.

3.4.1.5 The contractor shall notify the Government of the planned test event. (CDRL A007)

3.4.1.6 The contractor shall complete all identified, funded, and completed tests, analysis, or similarity qualification tests, utilizing quantity two (2) CI/CM prototypes.

3.4.1.7 The contractor shall deliver an Environmental Qualification Report, detailing the summary of all environmental requirements and test results of the CI/CM Hardware Update to the original specifications. (CDRL A008)

3.4.2. The contractor shall prepare a Factory Acceptance Test (FAT) Procedure. (CDRL A006)

3.4.2.1 The contractor shall, after completion of manufacturing and successful performance of the FAT, deliver a FAT Report for each unit (CDRL A008)

3.5. Program Management

3.5.1. The contractor shall submit a monthly Technical Status Report. (CDRL A009)

3.5.2. Problem Identification Report. The contractor shall notify NAWCAD when learning of any major event which (CDRL A010):

3.5.2.1 Could affect program planning or production schedules.

3.5.2.2 Degrades the safety of the item/system such that personnel injury or property damage may be involved.

3.5.2.3 Identifies a potential hazard requiring corrective action.

3.5.2.4 Requires assistance to resolve problems/potential problems due to communications bottlenecks or shortages of material which have the potential of contributing to program delays and adversely affect progress of the contractor's program.

3.5.3. The contractor shall participate in status meeting telecons weekly and ad hoc. The contractor shall submit meeting minutes within 5 business days of telecon completion. (CDRL A011)

3.6. Quality Assurance

3.6.1. The contractor shall maintain a certified Quality System for the duration of the contract. The Quality System shall be applied to all areas of the project.

3.6.2. Measurement and Calibration Systems. The contractor shall use a measurement and calibration system for the duration of the contract, and it shall conform with the requirements of ISO 10012-1 Quality Assurance Requirements for Measuring Equipment – Part 1: Metrological confirmation system for measuring equipment, ANSI/NCSL Z540.3-2006 or equivalent: Calibration – Calibration Laboratories and Measuring and Test Equipment, or equivalent Government Quality Assurance publications revision in effect on date of contract award.

3.6.3. Electro Static Discharge Sensitive Parts. The contractor shall use a system that conforms to the requirements of MIL-STD-1686C or equivalent to ensure that static susceptible units, assemblies and components are adequately protected from Electrostatic Discharge (ESD) damage during the manufacturing, test, inspection, packaging and shipping cycles. Packages shall be marked with an ESD cautionary note and/or symbol as required.

3.7. Configuration Management.

3.7.1. Configuration Management is to be performed using EIA-649-1 and or ANSI/EIA-649, National Consensus Standard for Configuration Management, or existing contractor configuration management processes.

3.7.2. Hardware/Software/Firmware Configuration Management. The contractor shall maintain and implement a configuration management system. The configuration management system shall have as a minimum:

3.7.2.1 Configuration Identification – Identification and documentation of the functional and physical characteristics of configuration items.

3.7.2.2 Configuration Change Control – Control of changes to those configuration items and their related documentation.

3.8. Review and Audits

3.8.1. Formal Technical Reviews. The contractor shall plan and conduct the following formal reviews using the NAVAIR Systems Engineering Technical Review (SETR) process as guidance.

· System Requirements Review

· Preliminary Design Review

· Critical Design Review

· Test Readiness Review

3.8.2. The contractor, with government authorization, may combine reviews where the design maturity permits. Virtual Meeting Reviews, (e.g. WEBEX™), with government authorization, may be utilized. An agenda for a review must be provided at least ten (10) business days prior to the review (CDRL A012). Minutes and actions (CDRL A011) from a review shall be provided five (5) business days after the review. Final copies of presentations and/or other technical documentation for government acceptance from the review shall be provided (10)-days after the review (CDRL A013).

3.8.3. Configuration audit reports shall be prepared, as required, by the contractor and submitted to NAWCAD for approval. (CDRL A014) NOTE: For guidance on both the Functional and Physical Configuration Audits use EIA-649.

3.9. Deviations and Waivers. The contractor shall use the standard DD Form 1694 in compliance with EIA-649 when submitting deviations and waivers or contractor Configuration Management Process defined Deviation or Waiver procedures and forms. (CDRL A015)

3.10. Life Cycle Documentation

3.10.1. Contractor shall provide all Life-Cycle Support documentation including Provisioning Technical Documentation and Reliability, Maintainability, and Availability Reports.

3.10.2. Provisioning Technical Documentation (PTD). The contractor shall provide PTD for all supplied equipment. All PTD deliveries shall be in electronic format.

3.10.2.1 Provisioning Parts List (PPL). The PPL portrays the top down breakdown of the physical composition of each Free Standing Unit (FSU) or configuration item. This list contains all items subject to wear or failure and other items required for maintenance throughout the expected life cycle of the end item. All PPL deliveries shall be in electronic format and in a media compatible with the Interactive Computer Aided Provisioning System (ICAPS), as specified in the NAVSEA Provisioning, Allowance, Fitting Out Support (PAFOS) Manual, Chapter 4, Appendix K (MS EXCEL is acceptable) available at https://navsea.dod.afpims.mil/Home/Warfare-Centers/NUWC-Keyport/NSLC/PAFOS/. ICAPS was developed by the government for the purpose of developing and transmitting provisioning related data. If PPLs have previously been delivered and accepted, the FSU reference number has not changed and less than 10% of the existing document has changed, the contractor can submit a Certificate of Identicality in lieu of a PPL. (CDRL A016)

3.10.2.2 Engineering Drawings. The contractor shall provide engineering drawings that show a complete parts breakdown of the end item and/or piece part items that have replaceable or repairable components to the Line Replaceable Unit (LRU) level. The drawings should also include the quantity, supplier part number, original manufacturer CAGE code and the original manufacturer's part number. Supplied drawings shall be in Standard English. The legibility and contrast of these drawings shall be such that every line, number, letter, and character is clearly readable and capable of being used to reproduce legible prints. Drawings and associated lists shall be submitted in AutoCAD™ 2000 or equivalent contractor format. Proprietary Drawings shall be marked per FAR 52.227-14. Engineering drawings are an essential element relative to the Provisioning and PTD deliverable requirements. (CDRL A017)

3.10.2.3 Technical Maintenance Documentation. The contractor shall provide Commercial Technical Manuals, Equipment and General purpose and Supplemental Data in sufficient depth to support operation and maintenance of equipment by the intended operator/user without the services of a manufacturer’s representative. The contractor shall identify the complete set of technical manuals, handbooks, fault isolation/repair procedures (at the organizational level), system/console operator guides, preventive/planned maintenance procedures and supporting reference documentation to be provided in support of the contract. (CDRL A018)

3.10.3. Reliability, Maintainability, and Availability (RM&A). The contractor shall submit a R&MA prediction report for all equipment (including hardware, firmware and software). For equipment that is already designed, any accepted industry Reliability and Maintainability (R&M) Report is acceptable. MIL-HDBK-217F, Telcordia, PRISM, or experience data will be accepted for existing hardware equipment predictions. If another method is used, a detailed explanation providing the prediction methodology shall be provided (CDRL A019).

3.10.3.1 Reliability: The Reliability section of the R&M Report shall include, but not be limited to, reliability modeling parameters, calculated Mean Time Between Failure (MTBF), calculated Mean Time Between Mission Critical Failures (MTBMCF).

3.10.3.2 Maintainability: The Maintainability section of the R&M Report shall include, but not be limited to, the calculated Mean Time To Repair (MTTR) tables, with maintainability predictions at the organizational level, including Fault Detection/Fault Isolation (FD/FI), access, interchange, egress, adjustment, retest/check out times, and any time required to download firmware. Scheduled maintenance, such as cleaning filters and making adjustments, as well as the number of persons required to perform a specific task, shall be identified. MIL-HDBK-472 may be used as a guide.

3.10.3.3 Availability: The Availability section shall detail proposed sparing option and Mean-Logistics-Delay time for each sparing option.

3.10.3.4 Obsolescence Reporting. The contractor shall provide their methodology used to proactively monitor, assess impacts, and resolve obsolescence issues.

3.10.4. The contractor shall provide timely notice of obsolescence status and any risks/impacts to the system within 10 days of awareness the LRU level for hardware and loss of support for any software component for the duration of the contract. Any obsolescence status change impacting the delivery schedule or requiring re-submission of a CDRL or software delivery under 3.2 shall be reported as a Problem Report.(A010)

Section D - Packaging and Marking

CLAUSES INCORPORATED BY FULL TEXT

Best commercial practices

M/F: To be determined per individual Delivery Order

CAUTION

CONTAINS ASBESTOS FIBERS

AVOID CREATING DUST

BREATHING ASBESTOS DUST MAY CAUSE SERIOUS BODILY HARM

(e) All items containing asbestos in a form that can be inhaled shall be packaged in sealed, impermeable bags or other impermeable containers, as required by 29 CFR.

NOTE TO SUPPLIERS: If the supplies to be furnished on this document require the asbestos caution label described above, the contractor shall notify the contract administrator indicated in the schedule prior to shipment.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLAUSES INCORPORATED BY REFERENCE

Code: N00421

NAWCAD

17598 Webster Field Road Bldg 8115 St. Inigoes, MD 20684-0010 M/F: Mike Fisher, 4.11.2.1

(b) Acceptance of all Contract Line Items/Sub Line Items (CLINs/SLINs) shall be made by signature of the accepting authority on a DD 250 submitted through the WAWF system. Acceptance will only occur when the accepting authority is sure that inspections performed demonstrate compliance with contract requirements.

Section F - Deliveries or Performance

DELIVERY INFORMATION

MIKE FISHER

17598 WEBSTER FIELD ROAD, BLDG 8115

ST. INIGOES MD 20684-0010

(301) 995-6662

N00421

N00421

N00421

Section G - Contract Administration Data

Combo

michael.fisher4@navy.mil

(Contracting Officer: Insert applicable email addresses or "Not applicable.")

TBD

(2) The following additional contract administration functions are assigned (see FAR 42.302(b)):

(c) Inquiries regarding payment should be referred to: MyInvoice at https://myinvoice.csd.disa.mil//index.html.

Section H - Special Contract Requirements

Section I - Contract Clauses