N6660414R2200_RFP.pdf

PDF 865 KB Posted

Attached to
Radio Frequency Distribution and Control Systems and Parts
Solicitation number
N66604-14-R-2200
Issued by

About this file

Solicitation for RFDACS Systems and System Parts

View the file

Other files

File Type Posted
N6660414R22000002.pdf PDF
N6660414R22000001.pdf PDF
Exhibit_B_RFDACS_Parts_List.pdf PDF
Attachment_1_RFDACS_Systems.pdf PDF
Attachment_2_Section_F_Delivery_Information.pdf PDF
Exhibit_A_CDRLs.pdf PDF
Attachment_3_Government_Furnished_Property.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 25 Aug 2014

X

A

X B

X C X D

EX

X

G

F 58 - 74

75 - 90

X H 91 lisa.mckeon@navy .mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

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

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

Prescribed by GSA

FAR (48 CFR) 53.214(c)

1 99

(If other than Item 7)

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

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

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

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N66604 8. ADDRESS OFFER TO

See Item 7

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

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

Handcarried not authorized conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

LISA M. MCKEON 401-832-7087

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

1 - 2

3 - 9

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

10 - 24

25 - 27

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

28 - 31

32 - 33 X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 34 - 38 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 39 - 41 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

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

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

13. DISCOUNT FOR PROMPT PAYMENT

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

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

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

FACILITY

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

SOLICITATION, OFFER AND AWARD

X

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

PART I - THE SCHEDULE

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

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

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

AWARD (To be completed by Government)

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

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

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

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

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

PART IV - REPRESENTATIO NS AND INSTRUCTIO NS

PART III - LIST O F DO CUMENTS, EXHIBITS AND O THER ATTACHMENTS

42 - 56

PART II - CO NTRACT CLAUSES

NAVAL UNDERSEA WARFARE CTR. DIV., NPT.

LISA M MCKEON, CODE 5912

COMMERCIAL ACQUISITION DEPARTMENT

1176 HOWELL STREET, BLDG. 1258

NEWPORT RI 02841

401-832-7087

401-832-4820FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.

1300345159

5. DATE ISSUED

10 Jul 2014

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N66604-14-R-2200

Section SF 30 - BLOCK 14 CONTINUATION PAGE

NOTES TO OFFERORS

1. Offerors shall complete Section B Pricing Tables included as Attachment 1, RFDACS Systems and Exhibit

B, RFDACS Parts List. Interested parties must contact the Contract Negotiator at lisa.mckeon@navy.mil to obtain Excel Spreadsheets for the RFDACS Parts List. Compact Disks

(CDs) with completed tables must be included with proposal submissions.

2. Section F, Delivery Information is included as Attachment 2.

3. Offerors shall complete Exhibit B, RFDACS Parts List delivery information. Interested parties must contact the Contract Negotiator at lisa.mckeon@navy.mil to obtain Excel Spreadsheets for the

RFDACS Parts List. Compact Disks (CDs) with completed tables must be included with proposal submissions.

4. All offers must be made valid through 31 Dec 2014.

5. All technical questions in response to the solicitation must be submitted in writing to Lisa McKeon at lisa.mckeon@navy.mil by 18 Aug 2014. Any questions asked after this date may not be answered by the

Government.

6. Contract ceiling will be calculated as follows (***Different than evaluation criteria detailed in Section

M***):

Total Contract Ceiling = Production Ceiling (CLINs 0001 – 0005) + Spare Parts Ceiling (CLIN 0006)

RFDACS Production CLIN ceiling*: 20 units multiplied by Year 5, Quantity 1 unit price. This number will be divided by 5 and split evenly across CLINs 0001, 0002, 0003, 0004, and 0005.

*Production ceiling may be shifted between CLINs 0001, 0002, 0003, 0004 and 0005 as Government requirements arise, but the sum of CLINs 0001 – 0005 will not be exceeded.

RFDACS Spare Parts ceiling (CLIN 0006): $16,250,000.00

7. In order to receive the drawings/specifications/Technical Data Package/GFI, the company must be registered in the Joint Certification Program (JCP). All requests for drawings/specifications/TDP/GFI must be sent to Lisa McKeon via email to: lisa.mckeon@navy.mil. The request must include:

a. Company name,

b. Company’s complete address,

c. Cage code,

d. Point of contact,

e. Telephone number,

f. Required JCP registration number, and

g. Shipping account information.

mailto:lisa.mckeon@navy.mil mailto:lisa.mckeon@navy.mil mailto:lisa.mckeon@navy.mil

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 1 Lot RFDACS SYSTEM (Year 1)

FFP

RADIO FREQUENCY DISTRIBUTION AND CONTROL SYSTEM (RFDACS)

OK-664(V)X/BRC IN ACCORDANCE WITH PERFORMANCE

SPECIFICATION (Section C) AND THE TECHNICAL DRAWING PACKAGE.

Offerors must provide pricing in Attachment 1, RFDACS Systems.

ANTICIPATED ORDERING PERIOD: DATE OF AWARD TO 31 DEC 2015

IN ACCORDANCE WITH DFARS 252.211-7003, UNIQUE ITEM

IDENTIFIER (UID) APPLIES TO THIS LINE ITEM. THE UID

INFORMATION MUST BE SUBMITTED IN WAWF AND A UID TAG MUST

BE AFFIXED TO THIS ITEM PRIOR TO SHIPPING.

FOB: Destination

PURCHASE REQUEST NUMBER: 1300345159

MAX

NET AMT

UNIT UNIT PRICE MAX AMOUNT

0002 1 Lot RFDACS SYSTEM (Year 2)

FFP

RADIO FREQUENCY DISTRIBUTION AND CONTROL SYSTEM (RFDACS)

ANTICIPATED ORDERING PERIOD: 1 JAN 2016 TO 31 DEC 2016

INFORMATION MUST BE SUBMITTED IN WAWF AND A UID TAG MUST

BE AFFIXED TO THIS ITEM PRIOR TO SHIPPING.

UNIT UNIT PRICE MAX AMOUNT

0003 1 Lot RFDACS SYSTEM (Year 3)

FFP

RADIO FREQUENCY DISTRIBUTION AND CONTROL SYSTEM (RFDACS)

ANTICIPATED ORDERING PERIOD: 1 JAN 2017 TO 31 DEC 2017

INFORMATION MUST BE SUBMITTED IN WAWF AND A UID TAG MUST

UNIT UNIT PRICE MAX AMOUNT

0004 1 Lot RFDACS SYSTEM (Year 4)

FFP

RADIO FREQUENCY DISTRIBUTION AND CONTROL SYSTEM (RFDACS)

ANTICIPATED ORDERING PERIOD: 1 JAN 2018 TO 31 DEC 2018

INFORMATION MUST BE SUBMITTED IN WAWF AND A UID TAG MUST

UNIT UNIT PRICE MAX AMOUNT

0005 1 Lot RFDACS SYSTEM (Year 5)

FFP

RADIO FREQUENCY DISTRIBUTION AND CONTROL SYSTEM (RFDACS)

ANTICIPATED ORDERING PERIOD: 1 JAN 2019 TO 31 DEC 2019

INFORMATION MUST BE SUBMITTED IN WAWF AND A UID TAG MUST

UNIT UNIT PRICE MAX AMOUNT

0006 1 Lot RFDACS System Parts

FFP

RADIO FREQUENCY AND DISTRIBUTION SYSTEM (RFDACS) SYSTEM

PARTS IN ACCORDANCE WITH PERFORMANCE SPECIFICATION (See

Section C) AND THE SPARE PARTS DRAWINGS NOT IN THE V(17) TDP.

Offerors must provide pricing in Exhibit B, RFDACS Parts List.

Anticipated Ordering Period:

Year 1 - Date of Award - 31 December 2015

Year 2 - 1 January 2016 - 31 December 2016

Year 3 - 1 January 2017 - 31 December 2017

Year 4 - 1 January 2018 - 31 December 2018

Year 5 - 1 January 2019 - 31 December 2019

IDENTIFIER (UID) APPLIES TO ANY ITEM IN THIS LINE ITEM WITH A

VALUE OF $5,000.00 OR MORE. THE UID INFORMATION MUST BE

SUBMITTED IN WAWF AND A UID TAG MUST BE INCLUDED WITH

ANY ITEM WHOSE VALUE IS $5,000.00 OR MORE PRIOR TO SHIPPING.

FOB: Destination

PURCHASE REQUEST NUMBER: 1300345159

VENDOR PART NR: 100000929680-0010

ITEM NO SUPPLIES/SERVICES ESTIMATED

UNIT UNIT PRICE ESTIMATED AMOUNT

DATA

FFP

CONTRACT DATA REQUIREMENTS LIST (CDRL) - See Exhibit A.

***NOT SEPARATELY PRICED***

ESTIMATED

CONTRACT MINIMUM

CONTRACT MINIMUM/MAXIMUM QUANTITY AND CONTRACT VALUE

The minimum quantity and contract value for all orders issued against this contract shall not be less than the minimum quantity and contract value stated in the following table. The maximum quantity and contract value for all orders issued against this contract shall not exceed the maximum quantity and contract value stated in the following table.

MINIMUM

MINIMUM

AMOUNT

MAXIMUM

QUANTITY

MAXIMUM

AMOUNT

$500,000 TBD at time of contract award

CLAUSES INCORPORATED BY FULL TEXT

HQ B-2-0022 CONTRACT SUMMARY FOR PAYMENT OFFICE (FIXED

PRICE) (FEB 1997)

This entire contract is fixed price.

Section C - Descriptions and Specifications

PERFORMANCE SPECIFICATIONS

The contract shall be performed in accordance with the Performance Specification, as follows:

PERFORMANCE SPECIFICATION

For The

Antenna Control Group OK-664(V)X\BRC

RADIO FREQUENCY DISTRIBUTION AND CONTROL SYSTEM (RFDACS)

SYSTEM PRODUCTION and PARTS MANUFACTURE

27 May 2014

1.0 BACKGROUND

This contract is for the procurement of Radio Frequency Distribution and Control Systems (RFDACS) and manufacture of RFDACS parts. The RFDACS provides a means of routing signals and information between the various antenna systems and other submarine communication subsystems. It replaces point-to-point wiring of radio frequency (RF) and control signals, and provides modular architecture for both hardware and software for simplified expansion or modification of the system. There are several variants of the RFDACS. The (V)17 variant will be installed onboard Los Angeles and Virginia class submarines. A list of parts which may be procured during the term of the contract will be provided with the solicitation. These parts may be required to support On Board Repair Parts

(OBRPs) requirements, system modernization requirements, and/or Naval Supply Command (NAVSUP) stocking requirements.

2.0 SCOPE

This Performance Specification sets forth contractor tasks required for the production of the OK-664(V)17\BRC

Radio Frequency Distribution and Control Systems (RFDACS) and RFDACS parts.

3.0 GOVERNMENT FURNISHED INFORMATION (GFI)

The following documents form a part of this performance specification to the extent specified herein. The contractor shall use best commercial practices in the manufacture of the RFDACS systems and parts. Reference shall be made to the technical drawing package for a full understanding of the production effort. All commercial standards and in house procedures which are used by the contractor in the performance of this contract shall be identified and made available to the Naval Undersea Warfare Center Division, Newport upon request.

(1) RFDACS_dwg_pkg (V)17 Technical Drawing Package

(2) RFDACS_parts_dwg_pkg RFDACS Parts Technical Drawing Package

(3) 3493-08-007-2_L2.0.0.0 Certification Test Procedure

(4) NAVMAT P-9492 Navy Manufacturing Screening Program

(5) Parts List List of parts that may be procured

3.1 GOVERNMENT FURNISHED EQUIPMENT (GFE), GOVERNMENT FURNISHED MATERIAL

(GFM), AND SOFTWARE

Multi-function mast antenna simulators and other test support equipment will be furnished by the Government as

GFE for use during system testing. The RFDACS software will be provided as GFM for delivery with each manufactured system. Certain parts which are used in the RFDACS and are obsolete and difficult to procure will be provided as GFM as required. These parts are identified in the GFP list included with the solicitation.

4.0 REQUIREMENTS FOR SYSTEM PRODUCTION AND PARTS MANUFACTURE

Paragraphs 4.1 and 4.2 set forth the tasks required to be performed by the contractor throughout the term of the contract for the production of RFDACS systems and parts. Paragraphs 4.3 through 4.14 set forth the tasks required to be performed by the contractor in support of the production efforts of paragraphs 4.1 and 4.2.

4.1 SYSTEM PRODUCTION

The contractor shall manufacture, test, and deliver OK-664(V)17\BRC Radio Frequency Distribution and Control

Systems in accordance with this Performance Specification and the RFDACS technical drawing package. The contractor shall develop and implement a program of system level screening in accordance with the guidance of GFI

(4)-NAVMAT P-9492, Navy Manufacturing and Screening Program. The program shall feature a procedure to be applied by the contractor to each system. A Government representative may be present during the first screening and following screenings at the Government’s discretion. These tests shall be performed at the unit (chassis) level.

Environmental screening shall be performed in accordance with Section 4.0 of GFI (4)-NAVMAT-P-9492. The contractor shall perform unit level and system level hardware certification (acceptance) testing on each unit and system in accordance with test procedures developed from GFI under paragraph 4.5. Prior to acceptance of each system, an incoming inspection will be performed by the Government's Technical Design Agent at a Government designated facility.

4.2 PARTS MANUFACTURE

The contractor shall procure/manufacture and deliver parts in accordance with this Performance Specification, the

RFDACS technical drawing packages, and the parts list provided as GFI. Parts shall be procured or manufactured, screened, and shipped to the Naval Undersea Warfare Center Division, Newport, for testing to ensure that the parts perform as required. The Government has primary responsibility for final acceptance testing of parts delivered under this paragraph. However, the contractor shall conduct production screening of vendor parts, cable assemblies, circuit cards, modules, units, and other assemblies, to the maximum extent possible to identify functional defects at the lowest possible assembly level and correct any deficiencies detected prior to delivery to the Government. The contractor shall develop and implement a program of unit level screening in accordance with the guidance of GFI

(4)-NAVMAT P-9492, Navy Manufacturing and Screening Program for any complete units ordered under this paragraph. The program shall feature a procedure to be applied by the contractor to each unit. These tests shall be performed at the unit (chassis) level. Environmental screening shall be performed in accordance with Section 4.0 of

GFI (4)-NAVMAT-P-9492.Within 90 days of receiving parts, the Government will return to the contractor any parts that do not perform as required. The contractor shall repair or replace the non-performing parts within 30 days of return receipt at no additional cost to the Government.

The contractor shall establish a Return Material Authorization (RMA) system for tracking of all repair actions. The contractor shall submit a failure analysis and corrective action report for each repair required in accordance with

CDRL A004.

4.3 PROGRESS REPORTS

The contractor shall document progress in a contractor's progress, status and management report in accordance with

CDRL A001. This report shall include status of the program, information concerning potential problem areas, RMA status of returned parts, production schedule and status, and contract funding status. The contractor shall establish, maintain, and use a cost/schedule system for planning and controlling costs and schedules, and for measuring performance.

4.4 PROGRAM MANAGEMENT REVIEWS, PRODUCTION READINESS REVIEW, AGENDAS,

AND MINUTES

The contractor shall participate in Program Management Reviews (PMRs), a Production Readiness Review, provide agendas, and prepare minutes in accordance with the following sub-paragraphs.

4.4.1 PROGRAM MANAGEMENT REVIEWS

The Naval Undersea Warfare Center Division, Newport, will conduct Program Management Reviews at the Naval

Undersea Warfare Center Division, Newport, in Newport, RI and at the contractor’s facility. Program Management

Review meetings shall be conducted thirty (30) days after contract award and quarterly thereafter. These reviews shall be conducted for the purpose of reviewing program progress, problem areas, planned activities, configuration management status, technical issues, and schedule. The contractor shall provide program status presentations as part of each PMR. During PMRs, the contractor shall make available in-process documents and hardware for review if requested by the Naval Undersea Warfare Center Division, Newport. The PMRs shall be scheduled by the contractor. Dates for the reviews shall be approved by the Naval Undersea Warfare Center Division, Newport. The first PMR will be conducted at the contractor’s facility. Other PMRs may be conducted at the contractor’s facility or at the Naval Undersea Warfare Center Division, Newport, in Newport, RI. No more than two reviews per year will be conducted at the Naval Undersea Warfare Center Division, Newport.

The contractor shall host informal In-Process Review meetings with the RFDACS principal investigator, lead engineer, and/or Contracting Officer’s Representative (COR) lasting approximately 1 hour in length. In-Process

Reviews shall be held every two weeks or as requested by the Government for the duration of the contract. These meetings will be held via teleconference.

4.4.2 PRODUCTION READINESS REVIEW

The Naval Undersea Warfare Center Division, Newport, will conduct a Production Readiness Review at the contractor’s facility prior to the start of production. This requirement may be waived by the Government if it can be determined that the contractor is ready to proceed with production by other means.

4.4.3 AGENDAS

The contractor shall provide agendas for all Program Management Reviews and the Production Readiness Review required by this contract in accordance with CDRL A002. All agendas shall identify a period of open discussion as an agenda item. The agendas will be approved by the Government prior to each PMR.

4.4.4 MINUTES

The contractor shall prepare minutes of all Program Management Reviews and the Production Readiness Review in accordance with CDRL A003. The minutes shall include all action items and the current status of each action item.

Action items resulting from the reviews will be considered completed only upon approval by the Government.

4.5 TEST PLANS, PROCEDURES, AND REPORTS

The contractor shall conduct all screenings and tests required by this Performance Specification in accordance with test plans and procedures prepared by the contractor and approved by the Naval Undersea Warfare Center Division, Newport. Test completion will be based on the ability to ensure that testing demonstrates the OK-664(V)17\BRC compliance with all contract requirements. Draft certification test procedures shall be provided as GFI and enhanced by the contractor. The contractor shall be required to perform environmental screening and hardware certification

(acceptance) testing. The GFI test procedures provided will contain all testing required for RFDACS and includes unit level and non-commercial off the shelf (COTS) VXI CCAs. Note that VXI CCA testing is generally performed when installed in the unit chassis. Approved test procedures shall fully describe all procedures, test setups, and test equipment, and shall include data sheets to provide for the complete documentation of test results. All changes shall be subject to approval by the Naval Undersea Warfare Center Division, Newport. Test plans shall be submitted in accordance with CDRL A006. Test procedures shall be submitted in accordance with CDRL A007.

Prior to performance of each examination or test required by the contract, the contractor shall provide written notice of such examination or test to the Naval Undersea Warfare Center Division, Newport. The contractor shall ensure actual receipt by the Contracting Officer’s Representative (COR) at least thirty (30) days before performance of each examination or test. The contractor shall prepare test reports for each examination and test. Testing of the manufactured systems may be witnessed by a Government representative at the manufacturing facility at the

Government’s discretion. Following the testing of each of the systems to be delivered, a test data package shall be forwarded to the Contracting Officer’s Representative. Test reports shall be submitted in accordance with CDRL

A008.

4.6 MATERIAL REVIEW BOARD (MRB)

The contractor shall establish a Material Review Board (MRB). The composition of the Material Review Board shall be at the discretion of the contractor subject to the approval of the Government. The contractor shall establish MRB procedures and provide adequate engineering capabilities and personnel who are fully knowledgeable of the product's technical requirements to participate in making MRB decisions. MRB authority is limited to Type II nonconformances and is not authorized to accept Type I nonconforming material. The contractor shall notify the

Government concerning MRB disposition of all Type II nonconformances via a Notice of Revision (NOR) submitted in accordance with CDRL A00C. Written approval of the Notice of Revision in the form of an e-mail from the

Contracting Officer’s Representative will be acceptable to implement the change. A Request for Waiver (RFW) shall be used for acceptance of all Type I nonconformances. The contractor shall submit Requests for Waivers in accordance with CDRL A00D. This process shall only apply to changes that do not impact price or schedule. These changes are typically administrative in nature such as vendor part number changes, substitution of alternate parts that do not result in a price change, and clarification of information contained in the drawing packages. If a proposed change impacts price or schedule, a contract modification will be required to implement that change. The following definitions apply:

a. Type I Nonconformance. The materials or supplies that depart from contract specifications and affect one or more of the following major areas: performance, durability, interchangeability, effective use or operations, (when a factor) weight or appearance, health or safety.

b. Type II Nonconformance. The materials or supplies which depart from contract specifications which are considered minor or have no bearing on the effective use or operation of the item or related components for the intended application and do not affect any of the criteria specified in Type I above.

4.6.1 NONCONFORMANCE MATERIAL

All nonconformance material shall be recorded on a suitable review record and shall be attached to the material and remain with the material until all MRB actions are complete as practical. The record shall at a minimum have the following information:

a. Part number, serial number, and specification number (if applicable)

b. Type of nonconformance

c. Quantity of nonconformance items

d. Description of the nonconformance

e. Corrective action to prevent recurrence

f. Recommended disposition (i.e., use as is, repair, rework, scrap)

g. Signature of Contractor and Government representative

Final decision regarding acceptance of nonconformance supplies or services are solely the prerogative of the

Government.

4.6.2 DEFECT DATA

The contractor shall maintain defect data throughout the duration of the contract. The contractor shall record and maintain defect data at each inspection or test station throughout the contract’s period of performance. The contractor shall identify and monitor critical quality control inspection/test points via process control techniques such as Statistical Process Control (SPC) to ensure that manufacturing processes are within specified control limits. The contractor shall initiate corrective actions as appropriate to identify and correct the root cause of deficiencies identified through SPC and similar techniques. Data shall be recorded and maintained to indicate the effectiveness of any corrective actions implemented. The contractor shall present defect data summaries and corrective action summaries as part of the program management reviews conducted by the Government.

Defects shall include all defects, discrepancies, nonconformances, anomalies, failures, etc., that occur or are first detected during manufacturing. The contractor shall track the recording of defect history and defect distribution at the serialized sub-assembly level, prior to any routine rework such as solder touch-up. Recording of defect reduction shall be at the contract configured item level. All such reports shall be tracked by the Material Review Board

(MRB) and shall be available for inspection and audit by the Government at the contractor’s facility.

4.6.3 FAILURE ANALYSIS

The MRB shall have the authority to require the contractor to perform a failure analysis to reveal failure mechanisms and provide the basis for corrective action. The Contractor shall submit failure analysis and corrective action reports in accordance with CDRL A004.

4.7 CONFIGURATION MANAGEMENT PROGRAM

The contractor shall establish and implement a Configuration Management (CM) program to the lowest repairable/replaceable part level for hardware configuration items (HWCI) for the OK-664(V)17\BRC. The contractor’s CM program shall ensure that a concise and well-defined process is established and implemented to ensure that all systems are equivalent, that all changes are necessary, that changes are not incorporated which cause the systems to not meet approved specifications, and that the configuration of each system is known at all times. The contractor’s CM program shall include the establishment of a Configuration Control Board (CCB). The CCB membership shall consist of engineering and manufacturing experts to approve or disapprove each recommended change. Recommended changes shall be documented using Engineering Change Proposal (ECP), Request for

Deviation (RFD), Notice of Revision (NOR), or Request for Waiver (RFW) forms in accordance with CDRLs

A00A, A00B, A00C, or A00D respectively. No change shall be implemented without CCB and Naval Undersea

Warfare Center Division, Newport approval. This process shall only apply to changes that do not impact price or schedule. These changes are typically administrative in nature such as vendor part number changes, substitution of alternate parts that do not result in a price change, and clarification of information contained in the drawing packages. If a proposed change impacts price or schedule, a contract modification will be required to implement that change.

4.7.1 BASELINE DESCRIPTION

The contractor shall update the baseline description each time the OK-664(V)17\BRC or associated documentation is changed. Updated baseline descriptions shall be submitted in accordance with CDRL A009.

4.7.2 CONFIGURATION RECORD

The contractor shall prepare and maintain configuration baseline description records to provide for configuration identification, change control, status accounting, compatibility, traceability, and integrity of HWCIs. These records shall be refined and updated throughout the duration of this contract and shall be made available to representatives of the Naval Undersea Warfare Center Division, Newport, upon request. These baseline description records shall include, as a minimum, the following information:

a. List of all the Government and contractor-developed specifications, including dates, titles, and revision levels;

b. Specification tree depicting all the specifications (including commercial specifications);

c. List of components to include all prime end items, non-complex items, and special test equipment in a top-down breakdown indentured level list to the piece-part level;

d. List of all associated drawings (e.g., schematic and wiring diagrams, installation, assembly, specification control, source control, detail, parts lists, etc.) identified by issue dates, titles and revision levels;

e. List and description of the Lowest Replaceable Units (LRUs);

f. List of interface control documents;

g. Configuration technical reviews;

h. List of all ECRs, RFDs, NORs, and RFWs and their status;

i. List of all the Acceptance Test Plans, Descriptions, Procedures, and Reports;

j. List of the current approved configuration documents and identification number associated with each LRU;

k. List of status and final disposition of identified discrepancies resulting from configuration audits; and

l. List of the effective and installation status of configuration changes to all LRUs at all locations.

4.8 RELIABILITY PROGRAM

The contractor shall perform reliability program planning activities and shall implement and maintain a Reliability

Program. The contractor shall use best commercial practices in implementing the reliability program. The contractor shall collect operating time and failure data, including data from warranty service to the component level. The contractor shall analyze the failure data, addressing: historical operating time and data, determination of the cause of each failure down to the component that caused the failure, identification of components that have had two or more failures, determination of the root cause from electrical stress, quality, environmental or operational problems, and recommended corrective actions. Failure analysis and corrective action reports shall be submitted in accordance with

CDRL A004.

4.9 QUALITY ASSURANCE AND MATERIAL TRACEABILITY

The contractor shall maintain and apply a Quality Management System (QMS) during the performance of work performed under this contract. The Contractor's Quality Management System (QMS) shall be documented and shall be available for review by the Contracting Officer or his representative prior to initiation of production and throughout the life of the contract. The Prime Contractor shall, upon notification, make his facilities available for audit by the contracting Officer or his authorized representative. The Contractor shall deliver a Contract Quality

Plan in accordance with CDRL A00G describing how the contractors QMS will be applied to the performance of this contract. The Quality Plan may cite the relevant sections of the contractor’s QMS by reference and need not reiterate existing QMS documents.

The Government reserves the right to perform any necessary inspection, verification, or evaluations to ascertain conformance to requirements and the adequacy of the implementing procedures. The contractor shall require of sub tier suppliers, a quality system which adequately controls the quality of supplies and services provided.

The contractor shall mark all raw materials with a unique traceability number (except as specified below).

a. Stored raw materials requiring traceability shall be segregated to preclude intermingling with material not requiring traceability.

b. When traceability markings will be removed by the manufacturing or fabrication process, the marking shall be recorded prior to removal and be immediately restored upon completion of the process. If this cannot be done or is impractical, an appropriate material control procedure (such as a bag and tag, tagging, and/or tote box control) shall be employed. The material control procedure shall provide a method of positive control to preclude commingling of heats or loss of traceability. The traceability marking shall be reapplied upon completion of the final manufacturing process.

4.10 SOFTWARE

All systems shall be delivered with software installed. Current RFDACS software will be provided as GFM for delivery with each system. Operating system software licenses (Microsoft Windows 7 Professional 32 bit) shall be procured by the contractor. Prior to acceptance testing for each system, the contractor shall ship the CPU assembly to the Naval Undersea Warfare Center Division, Newport, for installation of the required software. The Naval Undersea

Warfare Center will return the CPU assemblies with the software installed to the contractor to support testing and delivery of the systems.

4.11 HAZARDOUS MATERIAL

Use of any hazardous material, either internally or in association with the supply and/or support of the OK-

664(V)17\BRC, must be approved by the Naval Undersea Warfare Center Division, Newport. Prior to approval, the contractor shall provide a Material Safety Data Sheet (MSDS) (OSHA Form 174), or Safety Data Sheet (SDS) as applicable, and written justification that shows the necessity for the type, container size, quantity of hazardous material (or material that results in hazardous waste), together with a listing of less hazardous potential substitutes that were considered and the reasons why these substitutes cannot be used. These requests shall be in accordance with CDRL A005.

4.12 NOTIFICATION OF PARTS OBSOLESCENCE

The contractor shall notify the Government within thirty (30) days of the date of notification from a parts supplier that a part will become obsolete. This notification shall be in accordance with CDRL A00E.

4.13 SPECIAL SUPPORT EQUIPMENT

The contractor shall provide all standard and nonstandard support and test equipment required for all levels of assembly and testing of the OK-664(V)17\BRC with the exception of Multi-Function Mast antenna simulators that will be provided to the contractor as Government Furnished Equipment (GFE) for use during testing.

4.14 TECHNICAL DRAWING PACKAGE

The contractor shall incorporate the RFDACS technical drawing package into their production drawing system. The contractor shall notify the Government of any drawing errors or discrepancies within 30 days of discovery via a trouble report in accordance with CDRL A00F and request a Notice of Revision or clarification. The contractor shall validate the technical drawing package throughout procurement, assembly, and test of the first production assembled unit(s) and system. The Government reserves the right to place an on-site representative at the contractor's manufacturing facility through the period of validation and until the first production unit has been accepted by the

Government. It shall be the contractor's responsibility to demonstrate to the Navy on-site representative that each part is manufactured and configured in accordance with the drawing package.

5.0 SECURITY

All tasking under this contract is UNCLASSIFIED.

C26 INFORMATION ASSURANCE – UNCLASSIFIED DOD INFORMATION ON NON-DOD

INFORMATION SYSTEMS (JUL 2012)

(a) The Contractor shall ensure that unclassified DoD information it receives or produces in support of DoD activities is protected according to the information safeguards described in DoD Instruction 8582.01 – Security of

Unclassified DoD Information on Non-DoD Information Systems, which is available at the following web address:

http://www.dtic.mil/whs/directives/corres/pdf/858201p.pdf

(b) Upon request by the Government, the Contractor shall provide documentation demonstrating the safeguards the contractor has implemented to ensure the security of unclassified DoD Information.

(c) Contractor personnel that have not been briefed on DoD Instruction 8582.01 – Security of Unclassified DoD

Information on Non-DoD Information Systems shall be denied access contractor systems that contain unclassified

DoD information.

(d) Subcontracts. If the Contractor issues any subcontracts in which the subcontractor will have access to unclassified DoD information, the Contractor shall include this clause.

C57 EXCEPTION FROM ELECTRONIC AND INFORMATION TECHNOLOGY ACCESSIBILITY

REQUIREMENTS (JUN 2001)

(a) The Government has determined that this procurement is an exception to the Electronic and Information

Technology (EIT) Accessibility Standards (36 C.F.R. § 1194).

(b) Notwithstanding that an exception exists, the Contractor may furnish items or services provided under this contract that comply with the EIT Accessibility Standards (36 C.F.R. § 1194).

HQ C-1-0001 ITEM(S) - 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) A, attached hereto.

HQ C-2-0002 ACCESS TO PROPRIETARY DATA OR COMPUTER SOFTWARE

(NAVSEA) (JUN 1994)

(a) Performance under this contract may require that the Contractor have access to technical data, computer software, or other sensitive data of another party who asserts that such data or software is proprietary. If access to such data or software is required or http://www.dtic.mil/whs/directives/corres/pdf/858201p.pdf to be provided, the Contractor shall enter into a written agreement with such party prior to gaining access to such data or software. The agreement shall address, at a minimum,

(1) access to, and use of, the proprietary data or software exclusively for the purposes of performance of the work required by this contract, and (2) safeguards to protect such data or software from unauthorized use or disclosure for so long as the data or software remains proprietary. In addition, the agreement shall not impose any limitation upon the

Government or its employees with respect to such data or software. A copy of the executed agreement shall be provided to the Contracting Officer. The Government may unilaterally modify the contract to list those third parties with which the Contractor has agreement(s).

(b) The Contractor agrees to: (1) indoctrinate its personnel who will have access to the data or software as to the restrictions under which access is granted; (2) not disclose the data or software to another party or other Contractor personnel except as authorized by the Contracting Officer; (3) not engage in any other action, venture, or employment wherein this information will be used, other than under this contract, in any manner inconsistent with the spirit and intent of this requirement; (4) not disclose the data or software to any other party, including, but not limited to, joint venturer, affiliate, successor, or assign of the Contractor; and (5) reproduce the restrictive stamp, marking, or legend on each use of the data or software whether in whole or in part.

(c) The restrictions on use and disclosure of the data and software described above also apply to such information received from the Government through any means to which the

Contractor has access in the performance of this contract that contains proprietary or other restrictive markings.

(d) The Contractor agrees that it will promptly notify the Contracting Officer of any attempt by an individual, company, or Government representative not directly involved in the effort to be performed under this contract to gain access to such proprietary information. Such notification shall include the name and organization of the individual, company, or Government representative seeking access to such information.

(e) The Contractor shall include this requirement in subcontracts of any tier which involve access to information covered by paragraph (a), substituting "subcontractor" for

"Contractor" where appropriate.

(f) Compliance with this requirement is a material requirement of this contract.

HQ C-2-0008 ASSIGNMENT AND USE OF NATIONAL STOCK NUMBERS

(NAVSEA) (MAY 1993)

To the extent that National Stock Numbers (NSNs) or preliminary NSNs are assigned by the Government for the identification of parts, pieces, items, subassemblies or assemblies to be furnished under this contract, the Contractor shall use such NSNs or preliminary

NSNs in the preparation of provisioning lists, package labels, packing lists, shipping containers and shipping documents as required by applicable specifications, standards or

Data item Descriptions of the contract or as required by orders for spare and repair parts.

The cognizant Government Contract Administration Office shall be responsible for providing the Contractor such NSNs or preliminary NSNs which may be assigned and which are not already in possession of the Contractor.

HQ C-2-0009 ASSIGNMENT OF SERIAL NUMBER(S) (NAVSEA) (SEP 1990)

The Contractor shall request serial number assignment, in writing, from the Cognizant

Technical Program Office, with a copy to the cognizant Contract Administration Office.

The request for serial number assignment shall contain the following minimum information:

(a) Contract number;

(b) Assigned line item number and description;

(c) Assigned type designation;

(d) Assigned model number;

(e) Top drawing number and ID (List of Drawings) number;

(f) Exact quantity for which serial numbers are being requested, including preproduction samples required by the contract; and

(g) National Stock Number

HQ C-2-0011 COMPUTER SOFTWARE AND/OR COMPUTER DATABASE(S)

DELIVERED TO AND/OR RECEIVED FROM THE GOVERNMENT

(NAVSEA) (APR 2004)

(a) The Contractor agrees to test for viruses all computer software and/or computer databases, as defined in the clause entitled "RIGHTS IN NONCOMMERCIAL

COMPUTER SOFTWARE AND NONCOMMERCIAL COMPUTER SOFTWARE

DOCUMENTATION" (DFARS 252.227-7014), before delivery of that computer software or computer database in whatever media and on whatever system the software is delivered.

The Contractor warrants that any such computer software and/or computer database will be free of viruses when delivered.

(b) The Contractor agrees to test any computer software and/or computer database(s) received from the Government for viruses prior to use under this contract.

(c) Unless otherwise agreed in writing, any license agreement governing the use of any computer software to be delivered as a result of this contract must be paid-up and perpetual, or so nearly perpetual as to allow the use of the computer software or computer data base with the equipment for which it is obtained, or any replacement equipment, for so long as such equipment is used. Otherwise the computer software or computer database does not meet the minimum functional requirements of this contract. In the event that there is any routine to disable the computer software or computer database after the software is developed for or delivered to the Government, that routine shall not disable the computer software or computer database until at least twenty-five calendar years after the delivery date of the affected computer software or computer database to the Government.

(d) No copy protection devices or systems shall be used in any computer software or computer database delivered under this contract to restrict or limit the Government from making copies. This does not prohibit license agreements from specifying the maximum amount of copies that can be made.

(e) Delivery by the Contractor to the Government of certain technical data and other data is now frequently required in digital form rather than as hard copy. Such delivery may cause confusion between data rights and computer software rights. It is agreed that, to the extent that any such data is computer software by virtue of its delivery in digital form, the

Government will be licensed to use that digital-form data with exactly the same rights and limitations as if the data had been delivered as hard copy.

(f) Any limited rights legends or other allowed legends placed by a Contractor on technical data or other data delivered in digital form shall be digitally included on the same media as the digital-form data and must be associated with the corresponding digital-form technical data to which the legends apply to the extent possible. Such legends shall also be placed in human-readable form on a visible surface of the media carrying the digital-form data as delivered, to the extent possible.

HQ C-2-0012 CONFIGURATION MANAGEMENT (NAVSEA) (APR 2004)

(a) Baseline Definition - For configuration control purposes, all contractual documentation in effect at the time of contract award shall constitute the Contract Baseline which shall be considered incorporated in the baseline documentation.

(b) General Requirement - (1) The Contractor shall maintain a Configuration Control Program to assure that all detail level work being performed under this contract is in compliance with appropriate baseline documentation. The

Contractor shall prepare a Configuration Management Plan in accordance with the requirements of the contract for approval by the Government.

(2) Whenever a situation arises wherein the Contractor cannot comply with a baseline document, or whenever intent of such documentation is significantly changed by detail level documentation, the Contractor shall submit change documents to modify baseline documents to resolve the conflict or to allow non-compliance.

Whenever the cost of implementing a proposed change is less than the threshold requiring certified cost or pricing data, the Contractor shall provide documentation explaining the nature of related costs as shown on the change document. Whenever the contract cost changes by an amount greater than the threshold requiring certified cost or pricing data, the Contractor shall complete such cost and pricing data as the Contracting Officer shall require detailing all related costs, and attach it to the change document. Requirements for cost and pricing data shall be determined by the gross amount of the change unless otherwise directed by the contracting officer. Change documentation shall be submitted to the Contracting Officer in accordance with the Contract Data Requirements List

(CDRL), and as described in paragraphs (c) through (f) below.

(c) Engineering Change Proposals (ECPs) - ECPs shall be prepared in accordance with the approved configuration management plan and the requirements of the contract. DI-CMAN-80639C approved 30 Sep 2000 and MIL-HDBK-

61A of 7 Feb 2001 apply. An ECP should be submitted whenever the detail level physical configuration, material quality, operational or functional performance of equipment or installed systems will not be in compliance with baseline design-related documents (Specifications, Contract Drawings, etc.), and a change to the baseline document is considered an appropriate means of resolving a design-related issue. Documentation shall be developed in sufficient detail to enable Government review and evaluation of the merits of the proposed change, including cost and scheduling impact, ship class impact, and consequences if disapproved. All existing drawings and technical manuals impacted by the change shall be listed along with a brief narrative explanation of needed changes to incorporate the ECP if approved. Weight and moment data incidental to the change shall be provided. The

Contractor shall also prepare applicable baseline document insert sheets, with specific word changes or proposed re-write, to facilitate baseline documentation changes.

(d) Non-Engineering Change Proposals (NECPs) – An NECP should be submitted whenever necessary to document administrative, procedural, scheduling, or documentation changes that do not directly impact the physical configuration of the equipment. The NECP shall explain the nature of the problem, identify the applicable baseline document (i.e., Contract Data Requirement List (CDRL), Contract Clause, etc.) and provide a detailed explanation justifying the proposed course of action desired to resolve the problem. Insert sheets for applicable documents shall also be attached to facilitate change action in the event the Non-Engineering Change Proposal (NECP) is approved.

(e) Deviations and Waivers - In the event that a baseline design-related document requirement cannot be met, and a change to the baseline document is considered inappropriate, the Contractor shall submit a Request for Deviation

(RFD) or Request for Waiver (RFW), as applicable. DI-CMAN-80640C approved 30 Sep 2000 and MIL-HDBK-

61A of 7 Feb 2001 apply. The explanation of "need for deviation" should provide detailed justification and consequences of approval, to include technical details explaining the degree of non-compliance or effect on ship equipment or system operation constraints. In a similar manner, a waiver shall document an "as built" configuration that departs from baseline documentation and should include any proposed corrections or modifications to better meet the intent of the baseline document.

(f) Equitable Adjustments for Change Documentation Preparations - For its effort expended in preparing ECPs, NECPs, Deviations and Waivers, the Contractor shall receive equitable adjustment under the following circumstances:

(1) In the event the Contractor, on its own initiative, and without written request from the Contracting

Officer, develops a change document that is later disapproved by the Government, the Contractor shall bear the cost of this effort.

(2) To avoid such loss, and at its option, the Contractor may submit a "preliminary" document that outlines intent, but without detailed supporting documentation and request the Contracting Officer's approval for expenditure of effort to complete the detailed supporting documentation. In the event the Contracting Officer denies this request, the Contractor will bear the cost of development of the "preliminary" document, and shall make no further effort to complete detailed supporting documentation.

(3) In the event the Contracting Officer approves the Contractor's request to develop supporting documentation, the Contractor shall be equitably compensated for its effort for both the "preliminary" and "final" documentation, regardless of whether or not the change document is later approved.

(4) In the event the Contracting Officer requests in writing that the Contractor develop change documentation, the effort expended by the Contractor in developing such documentation shall be subject to equitable adjustment, regardless of whether or not the change document is later approved.

(5) In the event the Contractor, on its own initiative, and without written request from the Government, develops a change…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .