19RJM30_sol.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 22 Jan 2018

X

A X B X C X D

EX

X

G F 57 - 73

74 - 82 X H 83 - 88 stewart.lindsey@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)

DO-A2 1 88

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

N00164 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 1 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

NSWC CRANE, BLDG 121

conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

STEWART W. LINDSEY 812-854-4571

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 6

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

7 - 23 24 - 25

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

26 - 27 28 - 29

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 30 - 35 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 36 - 37 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 - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

38 - 55

PART II - CONTRACT CLAUSES

NAVAL SURFACE WARFARE CENTER CRANE DIV

S. LINDSEY (812-854-4571)

BLDG 121

300 HWY 361

CRANE IN 47522-5001

812-854-4571

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

20 Dec 2018

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N0016419RJM30

Section B - Supplies or Services and Prices

IDC CONSTRAINTS

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

QUANTITY

MINIMUM

AMOUNT

MAXIMUM

QUANTITY

MAXIMUM

AMOUNT

170.00 EA* $7,800,000.00

(estimated)

*Note: The minimum quantity for this contract will be met with the order of the following:

(CLIN 0001- Design, Development and Design Verification Tests, Avionics: 1EA, CLIN 0002- Design, Development and Design Verification Tests-Flight Control: 1 EA, CLIN 0003- Pre-Production Units-Avionics Modules: 84 EA and CLIN 0004- Pre-Production Units-Flight Control: 84 EA)

ITEM NO SUPPLIES/SERVICES QTY U/I UNIT PRICE AMOUNT

0001 Design, Development

1 Each and Design Verification Tests for Avionics Modules IAW Statement of Work (SOW) 3.5 and Performance Specification JXM-PS-0650. For Non-Recurring Engineering (NRE) costs.

Vendor can expect payment for this CLIN upon the Government's receipt and acceptance of final engineering drawings IAW section 5.2.2 of the SOW.

IDIQ Min: 1 EA.

PSC: 6135

FOB: Destination

FFP

0002 Design, Development

1 Each and Design Verification Tests for Flight Control Modules IAW SOW 3.6 and Performance Specification JXM- PS-0650. For NRE costs.

Vendor can expect payment for this CLIN upon the Government's receipt and acceptance of final engineering drawings IAW section 5.2.2 of the SOW.

IDIQ Min: 1 EA.

0003 Pre-Production Units-

84 Each

Avionics Modules IAW SOW 3.7 and Performance Specification JXM-PS-0650.

IDIQ Min: 84 Each

0004 Pre-Production Units-

84 Each

Flight Control Modules. IAW SOW 3.8 and Performance Specification JXM-PS-0650.

IDIQ Min: 84 Each

ITEM NO SUPPLIES/SERVICES MAX QTY U/I UNIT PRICE MAX AMOUNT

0005 Production Units Avionics

Modules

UNDEFINED Each

IAW SOW 3.9 and Performance Specification JXM-PS-0650.

(IDIQ Min: 0)

See pricing matrix below:

PRICING MATRIX- CLIN 0005

CLIN 0005

Quantity

Contract Year

Contract Year

Contract Year

Contract Year

Contract Year

22 Each* 23-44 Each 45-66 Each 67-88 Each

89-110 Each 111-132 Each

*Note: The Government will typically order these units in multiples of 22 Each

ITEM NO SUPPLIES/SERVICES MAX QTY U/I UNIT PRICE MAX AMOUNT

0006 Production Units Flight

UNDEFINED Each

Control Modules. IAW SOW 3.10 and Performance Specification JXM-PS-0650.

(IDIQ Min: 0)

See pricing matrix below:

PRICING MATRIX- CLIN 0006

CLIN 0006

Quantity

Contract Year

Contract Year

Contract Year

Contract Year

Contract Year

22 Each* 23-44 Each 45-66 Each 67-88 Each

89-110 Each 111-132 Each

*Note: The Government will typically order these units in multiples of 22 Each

ITEM NO SUPPLIES/SERVICES QTY U/I EST COST FIXED FEE TOTAL EST CPFF AMT

0007 Engineering Services

1 Lot

To Be Negotiated (TBN) only if needed. CLIN type may be FFP or CPFF if required. In Accordance With (IAW) Statement of Work 3.11 (SOW).

The Government does not anticipate the total cost of this CLIN to exceed $1,000,000 during the course of the resultant contract.

Do not propose against this CLIN.

PSC: R425

CPFF

ITEM

NO SUPPLIES/SERVICES QTY U/I UNIT PRICE AMOUNT

0008 Data

Technical Data Requirements for CLIN(s) 0001 thru 0007 in accordance with (IAW) the Statement of Work (SOW) Paragraph 6, CDRL(s) A001 thru A019 provided in Section J, and applicable DID(s). The price/costs for all technical data generated by the contractor directly or indirectly in its performance of this procurement effort is included in the price/costs paid by the Government under CLIN(s) 0001 thru 0007. Not Separately Priced.

See Exhibit A

Lot

CLAUSES INCORPORATED BY FULL TEXT

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

(a) As part of the negotiated fixed price or total estimated amount of this contract, 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.

Section C - Descriptions and Specifications

STATEMENT OF WORK

Statement of Work Flight Control/Avionics Power System

1.0 GENERAL

This Statement of Work (SOW) defines tasking for offeror’s performing work for the development/fabrication of the flight control/avionics system.

1.1. Scope

The tasks defined in this document are for the design and fabrication of power systems. The effort will consist of design and development of a reserve, power system that will undergo verification testing at Naval Surface Warfare Center, Crane Division (NSWC Crane).

1.2 Background

The intent of this effort is to design and fabricate a power source for a tactical configuration.

1.3 Objective

The main objective of this effort is to develop a robust power solution for the flight control and avionics sections of a missile system. The design is expected to consist of a quantity of individual thermal battery modules. A Technical Data Package will be developed for the battery(s) design to document key design parameters.

2.0 APPLICABLE DOCUMENTS.

The documents listed below in their latest revision are pertinent to the requirements of this contractual effort.

2.1 Government Documents

2.1.1 DoD Documents

DoD 5200.1-M Standard for Security and Operations at Acquisition Facilities

DoD 5220.22-M National Industrial Security Program – Operating Manual, dated Feb

2006 and Supplemental dated Dec 1994

S9310-AQ-SAF-010 Technical Manual for Batteries Navy Lithium Safety

2.1.2 Military Standards

MIL-STD-882 Standard Practice for System Safety MIL-STD-1629 Procedures for Performing a Failure Mode Effects and Criticality

Analysis

2.1.3 NSWC Crane Documents

JXM-PS-0650 Product Requirement Specification, Reserve Battery for Flight Control and Avionics

2.2 Non-Government Documents

2.2.1 Various Publications

SAE AS9100 Quality Systems, Model for Quality Assurance in Design, Development, Production, Installation and Servicing IPC J-STD-001 Requirements for Soldered Electrical and Electronic Assemblies IPC A-610 Acceptability of Electronic Components

3.0 PROGRAM MANAGEMENT REQUIREMENTS

3.1 General Management

The offeror shall provide all personnel, facilities, materials and services to accomplish the tasks identified in this SOW. The security principles of DoD 5100.21-M and 5220.22-M shall be applied to the program.

3.2 Program Management

The offeror may assign a Program Manager to this effort. The Offeror’s Program Manager should provide overall leadership of the effort, be the main point of contact with the Procuring Activity, develop and report project schedules/milestones, report failures or anomalous occurrences, and oversee the execution and resources assigned to support this effort.

3.2.1 Program Schedule

The offeror shall develop an Integrated Master Schedule (IMS) reflecting the major activities required to execute requirements per the contract. The offeror shall use input from the Procuring Activity to ensure milestones/deliverables match programmatic goals. See Contract Data Requirements List (CDRL) A001 for requirements on the IMS.

3.2.2 Management Communication and Status Reports

The offeror shall provide written communications of programmatic, management, and financial status to the Procuring Activity. At a minimum, monthly status reports shall be submitted per CDRL A002. The offeror shall also support ad-hoc meetings and special meetings to support the Procuring Activity.

3.3. Risk Management

The offeror shall utilize a risk management process to manage program risks. MIL-STD-882 provides a risk identification tool that is familiar to the Procuring Activity. Risk management shall be applied to offeror in-house activities, sub-contracted activities, and any activities critical to the execution of the contracted effort. The offeror shall report technical and programmatic risks and associated mitigations a minimum of monthly in CDRL A002.

3.4 Monthly Conference Calls

The offeror shall support monthly planned conference calls scheduled by the Procuring Activity.

The offeror shall discuss technical progress, issues, risks, and any other factors pertinent to successful execution of this effort. Agendas will be developed and provided by the procuring activity prior to the Conference Call. The offeror shall support resolution of assigned actions.

3.5 Design/Development/DVT’s of Avionics Modules

This activity encompasses all of the non-recurring activities that go into product design to achieve the requirements identified in JXM-PS-0650 and other applicable contractual documents for the Avionics module. This also includes the DVT’s defined in paragraph 4.4.3 of this SOW.

Activities as defined in paragraphs 4.2, 4.3, and 4.4 of this SOW (with the exception of 4.4.40 which may be considered a pre-production phase) constitute those typically done during design/development. It would be expected that deliverables such as those defined in paragraph

5.2.2 of this SOW would be drafted but not necessarily finalized during this phase. Any internal DVT’s conducted prior to this formalized submittal are to be considered in this phase. Additional guidance on DVT samples is provided in paragraph 4.1 of JXM-PS-0650.

3.6 Design/Development/DVT’s of Flight Control Modules

This activity encompasses all of the details identified in paragraph 3.5 of this SOW for the Flight Control Module.

3.7 Pre-production Units Avionics Modules

Pre-production units are those submitted to the Procuring Activity to conduct verification testing as defined in JXM-PS-0650 paragraph 4.2.2 for the Avionics application. Activities should follow sequentially from the completion of paragraphs 3.5 and 4.4.4 of this SOW. A total of 84 modules (some of which will be sent to system integrators) is the maximum expected quantity for this CLIN.

3.8 Pre-production Units Flight Control Modules

Pre-production units are those submitted to the Procuring Activity to conduct verification testing as defined in JXM-PS-0650 paragraph 4.2.2 for the Flight Control (also referred to as the Actuator) application. Activities should follow sequentially from the completion of paragraphs

3.6 and 4.4.4 of this SOW. A total of 84 modules (some of which will be sent to system integrators) is the maximum expected quantity for this CLIN.

3.9 Production Units Avionics Modules

Once Avionics thermal modules have met all of the requirements of the pre-production tests of paragraph 4.2.2 of JXM-PS-0650 to the satisfaction of the Procuring Activity the baseline design is considered to be frozen. This is the configuration of Avionics module production units (unless Engineering Change Requests of paragraph 5.2.1 of this SOW are submitted and approved by the Government). All aspects of this SOW where applicable are to be considered at this point of the life cycle. A total of 484 production units maximum over the contract period of performance is projected.

3.10 Production Units Flight Control Modules

Once Flight Control thermal modules have met all of the requirements of the pre-production tests of paragraph 4.2.2 of JXM-PS-0650 to the satisfaction of the Procuring Activity the baseline design is considered to be frozen. This is the configuration of Avionics module production units (unless Engineering Change Requests of paragraph 5.2.1 of this SOW are submitted and approved by the Government). All aspects of this SOW where applicable are to be considered at this point of the life cycle. A total of 484 production units maximum over the contract period of performance is projected.

3.11 Engineering Support

Engineering support shall be individually negotiated prior to establishment of a task order.

Engineering support functions are those that are currently unknown and may come up as a result of missile system design changes or items not originally anticipated in the development of contract requirements. It can also consist of technical support from the offeror whose knowledge of the product design can aid in engineering activities including but not limited to root cause analyses. The intent is for the Procuring Activity to have the ability to support mission readiness with this contract vehicle in the event of unknowns.

4.0 TECHNICAL REQUIREMENTS

The following sections identify specific aspects of technical requirements for activities required under this contractual effort.

4.1 Systems Engineering

The offeror shall establish a systems engineering process and use it to perform system analysis, flow down, allocation and documentation to meet the requirements identified in JXM-PS-0650.

The offeror shall flow down the requirements defined in the specification into the power system design. The offeror shall conduct and document trade studies to define the selected design. A System Requirements Review (SRR) shall be conducted within 2 months after contract award.

4.2 Hardware Design and Engineering Requirements

4.2.1 Design

The offeror shall design, integrate and test the reserve battery per the requirements defined in

JXM-PS-0650.

The offeror shall ensure functional, performance, and interface requirements are identified, achieved, and controlled.

The initial phase will consist of the offeror’s development of thermal battery modules to meet the electrical requirements of the governing documentation. Design Verification Tests should be at the battery module level, without concern over mechanical interfaces. The output terminals shall be sufficient to carry the specified loads. The offeror is expected to provide ‘slick’ cans which the procuring activity will determine methodology to secure in the end application.

Verification and validation results shall be documented and shared with the procuring activity during reviews or conference calls.

The offeror shall demonstrate analytically the ability of the power source to meet applicable electrical requirements. Demonstration is in accordance with contractor format but can be as simple as calculations copied from an engineering notebook presented during a monthly status or discussed during a monthly conference call.

The design shall have sufficient margin to cover expected statistical variations.

The offeror shall develop an Acceptance Test Plan for the reserve battery (see CDRL A013 later in this document).

The offeror shall develop a compliance matrix to ensure all specification requirements are met.

The compliance matrix shall identify applicable specification/SOW requirements and a description of how the requirement is being met and controlled.

The offeror shall support the Procuring Activity in the development of the power system. The offeror shall take design and procurement authority following completion of actions resulting from the Critical Design Review (CDR).

4.2.2 Hardware Analysis

The offeror shall conduct analysis on hardware as necessary to ensure projected performance parameters are within rated design parameters.

4.3 Reliability Engineering Requirements

4.3.1 Reliability Analysis

The offeror shall meet the reliability requirements identified in JXM-PS-0650. Analysis and testing shall be conducted to demonstrate conformance to the requirements. Failure rates for parts or items shall be established from the best available sources of data and be included in the analysis. The analysis shall be provided to the Procuring Activity in accordance with CDRL A003.

4.3.2 Parts De-rating and Margin Analysis

Parts/components used in the power source design shall be appropriately de-rated to allow for ample margin and provide positive results for any associated analyses.

4.3.4 Failure Mode, Effects and Criticality Analysis.

The offeror shall perform a Failure Mode, Effects and Criticality Analysis (FMECA) on the power system being delivered using the guidelines of MIL-STD-1629A. The FMECA shall be contained in a detailed report containing a system description, assumptions, data sources, analysis methodology, analysis results, a Criticality Matrix and FMECA worksheets. The report shall be in accordance with CDRL A004.

4.3.4 Failure Reporting and Corrective Action System (FRACAS).

The offeror shall establish and maintain a FRACAS system. The associated data shall begin at the start of hardware acceptance testing and continue all the way through the entire process until power systems are built and tested including any returns after delivery for corrective action.

FRACAS items shall be documented and reported in accordance with CDRL A005. FRACAS items shall encompass failures, non-conformances, out of family behavior, and trends which are going in a direction that could lead to non-conformance.

4.3.5 Parts, Material, and Process Management.

The offeror shall develop a plan to identify component/part acceptance criteria. The offeror shall conduct analysis, test, or inspect individual components as received to ensure the end item will function as expected and that parts meet quality expectations (including verification that they are not counterfeit). Whether the part will be 100% examined or sampled in accordance with established criteria shall be identified in the plan. The plan shall be in accordance with CDRL A006. The offeror shall establish a Configuration Management Board of personnel with subject matter expertise in associated materials and experience in building power sources to resolve material issues, obsolescence, material substitutions, vendor changes, etc.

4.3.6 Bill of Materials.

The offeror shall develop an indentured Bill of Materials (BOM) identifying the components/assemblies that make up the power system. The BOM shall contain manufacturer part numbers, drawing numbers, cage code or company name of accepted parts vendors, description, any internal governing documents, and quantities at a minimum. The BOM shall be in accordance with CDRL A007.

4.4 Technical Reviews and Meetings.

The offeror shall work with the Procuring Activity during the course of the contract to ensure visibility and mutual agreement on aspects of the power system design.

A Review Team shall be established to review and approve progress during critical stages such as the Critical Design Review (CDR), Test Readiness Reviews (TRR’s) and Production Readiness Reviews (PRR’s). The Review Team shall consist of technical/contractual representatives from the Procuring Activity. The team shall provide approval or conditional approval to proceed to subsequent milestones. Conditional approval shall be associated with the completion of actions assigned.

Action items will be captured by the offeror during technical reviews and meetings. Action item progress shall be reported by the offeror on a monthly basis. The Review Team shall approve resolution of action items. Closure of action items shall be considered entrance criteria for subsequent milestones.

4.4.1 Technical Interchange Meetings (TIM’s)

TIM’s will be held a maximum of quarterly to provide the Procuring Activity with program status, future plans, and risks. TIM’s will alternate between the offeror’s facility and the Procuring Activity. Meeting minutes shall be generated by the offeror summarizing the TIM and recording any action items. Meeting minutes shall be in accordance with CDRL A008. TIM’s shall address at a minimum:

Design progress Compliance with product specification/SOW Issues/Concerns/Risks Documentation Cost and schedule performance

4.4.2 Preliminary Design Review (PDR)

The offeror shall conduct a PDR within 4 months of contract award at the offeror’s facility. A PDR presentation shall be developed and submitted by the offeror a minimum of two working days prior to the PDR in accordance with CDRL A009. The PDR shall address:

A preliminary power system design A requirements matrix based on JXM-PS-0650 and this SOW showing how requirements will be achieved (including objective quality evidence that may be gathered)

Documentation status Risks/Issues

The PDR should demonstrate that the offeror understands all applicable requirements and has a path forward to meet requirements. The PDR should identify technical and programmatic risk areas and mitigations. Final risk should be acceptable in order to proceed with the detailed design.

The offeror shall capture meeting minutes and action items from the PDR. Successful resolution of action items shall be assessed by the Review Board. Reasonable entrance and exit criteria for the PDR are provided below.

ENTRANCE CRITERIA: Preliminary design has been completed, requirements are tabulated and a path forward to achieving requirements has been identified, major risks have been identified and mitigated to the extent possible, and required documentation has been identified.

EXIT CRITERIA: Procuring Activity concurrence with requirements analysis and plan forward, and completion of agreed upon action items.

4.4.3 Design Verification Tests (DVT’s)

DVT’s shall be conducted on a minimum of 5 samples at the operating temperature extremes defined by JXM-PS-0650. The intent of the DVT’s is to verify the battery design prior to going into CDR. If the offeror feels that risk of unsuccessful performance is greater for a specific test condition called out in JXM-PS-0650, subjecting a DVT sample to that condition as a risk mitigation would be appropriate. The offeror shall generate a DVT test plan in accordance with CDRL A010 to be approved by the Procuring Activity. A test report detailing the results (and including raw test data in ASCII format) shall be provided by the offeror in accordance with CDRL A011. The offeror shall notify the Procuring Activity one week prior to testing so that the Procuring Activity can witness testing.

4.4.4 Critical Design Review (CDR)

The offeror shall conduct a CDR within 6 months of the PDR unless it is mutually agreed by the Procuring Activity that it should be delayed. A CDR presentation shall be developed and submitted by the offeror a minimum of five working days prior to the CDR in accordance with CDRL A012. The intent of the CDR is to demonstrate that the power system design is mature, demonstrate that Objective Quality Evidence (OQE) has been generated that shows the ability of sub-scale or full scale items to meet requirements, components/sub-assemblies have acceptable risk associated, producability/process factors are acceptable, and documentation has been sufficiently vetted and finalized. The offeror shall also provide data/analysis to show that the battery can meet the safety tests called out in S9310-AQ-SAF-0010.

The offeror shall capture meeting minutes and action items from the CDR. Successful resolution of action items shall be assessed by the Review Board. Reasonable entrance and exit criteria for the CDR are provided below.

ENTRANCE CRITERIA: Design has been completed, all open action items from previous reviews are closed, requirements matrix analysis complete, baseline drawings for the power system are completed, demonstrations (Design Verification Tests) have occurred verifying that design is adequate, material specifications are complete, and process documentation is complete.

EXIT CRITERIA: Procuring Activity concurrence with requirements compliance, successful resolution of agreed upon action items during CDR, concurrence with documentation adequacy, development of a detailed schedule for the remaining contractual effort, and concurrence with DVT results.

CDR represents the point at which the design baseline is frozen and changes thereafter require a formal change process.

4.4.5 Test Readiness Review (TRR)

A TRR shall be held prior to any significant tests conducted at the offeror’s facility. The TRR can be at the offeror’s facility (if Procuring Activity attends) or by telephone conference. The intent of the TRR is to go over the test regime, identify test equipment planned for use, and ensure the proposed test will meet program goals.

4.4.6 Production Readiness Review (PRR)

Prior to production of qualification or deliverable samples, the offeror shall conduct a PRR. The PRR shall demonstrate the offeror’s readiness to begin production. The PRR shall address the indentured drawings that make up the power system to ensure the drawings are current and any changes made since the design was frozen are formally documented. The PRR shall also address the individual components that will be used for the power system, and any non-conformances or discrepancies against the components or sub-assemblies. Another significant aspect that shall be reported during the PRR is the process documentation. Process documentation should be approved, validated, and accurate.

4.5 Acceptance Testing.

The offeror shall conduct acceptance testing on the final fabricated power system in areas where the tests are non-destructive and aid in providing an objective quality measure that power systems meet the requirements of JXM-PS-0650 or allow for an in-family assessment of key quality control indicators. The offeror shall generate an Acceptance Test Procedure identifying these 100% tests in accordance with CDRL A013 for Procuring Activity approval. The procedure shall cover any 100% tests called out in JXM-PS-0650 and any that the offeror feels provides value to the end product.

4.6 Compliance OQE

For a given fabrication lot (qualification or production deliverable) the offeror shall provide a final report with the lot that provides Objective Quality Evidence (OQE) of conformance to key requirements. Certificates of conformance, Acceptance Test Results, assays, etc. (including items identified later in this SOW) shall be included in the report. CDRL A014 identifies the requirements for compliance OQE. For items which the offeror does not include in CDRL A014 because of proprietary concerns, data relating to the build and providing OQE for conformance shall be maintained for a minimum of 10 years after delivery. This data shall be made available to the Procuring Activity for review at the offerors facility upon request.

4.7 Hardware for Verification

The offeror shall fabricate the contractually required quantity of power systems and deliver to the Procuring Activity for verification testing under environments as defined by JXM-PS-0650.

5.0 Program Support Requirements

5.1 Supply Chain Management

The offeror shall have a documented supply chain management program. The offeror shall take preventive measures to ensure counterfeit parts do not enter the supply chain. The offeror shall only accept contractual direction from the Procuring Activity contract specialist or contracting officer.

5.2 Configuration Management

5.2.1 Engineering Change Requests

The offeror shall manage the configuration of items procured in accordance with the applicable delivery order/base contract. Once the design baseline is frozen, the offeror shall submit an Engineering Change Request (ECR) in accordance with CDRL A018. The ECR shall be reviewed and approved by the Procuring Activity prior to implementation.

5.2.2 Engineering Drawings

The offeror shall generate and submit a Technical Data Package (TDP) in accordance with CDRL A015. As part of CDRL A015, once the mechanical interface is determined, the contractor shall provide source control drawings from the offeror which define how the assembly is configured and how the assembly or individual modules will meet interface requirements. The TDP shall consist of a main source control drawing for the power supply along with all of the component/sub-assembly drawings that make up the battery. The drawings shall be level II. The intent of the drawings is for engineering personnel to support the power system over its intended life, not for competitive procurement.

5.2.3 Physical Configuration Audit (PCA)

The offeror shall support a PCA at the offeror’s facility. The PCA shall go through build documentation and power system hardware to ensure documentation is correct and the process is occurring per approved documentation. The PCA is anticipated to be three days in duration.

The audit will take place after CDR but prior to any non-developmental production units.

5.3 Failure Analysis Support

In the event of product failure, the offeror shall support the Procuring Activity in determination of the root cause. The offeror shall provide access to process and component data. The offeror shall participate on the team to assess root cause.

5.4 Quality Program

The offeror shall have a Quality Program in accordance with SAE AS9100 or equivalent. The offeror shall allow the Procuring Activity to review the documentation regarding the Quality Program upon request.

5.5. Foreign Object Debris (FOD)

The offeror shall establish a FOD control program for fabrication of the power systems in this contract. The offeror shall report FOD related incidents in the compliance reports identified in

CDRL A014.

5.6 Repair/Rework/Scrap

The offeror shall document all repair, rework, and scrap on a given lot or delivery order of power systems provided. Any repair or rework shall be completed with approved documented processes and procedures. The summary of repair, rework, and scrap shall be contained in the compliance reports of CDRL A014.

5.7 Lot Homogeneity

Components within power systems of a given lot shall be homogenous to the maximum extent possible. Pedigree of individual power system components shall be tracked and documented for components that have a high likelihood of affecting performance. A matrix for pedigree tracking for a given lot shall be delivered in accordance with CDRL A016 for critical components.

5.8 Contract Status Reporting Via eCRAFT

This applies to Engineering Services Contract Line Items. The Contractor agrees to upload the Contractor's Funds and Man-hour Expenditure Reports in the Electronic Cost Reporting and Financial Tracking (eCRAFT) System and submit the Contract Status Report on the day and for the same timeframe the contractor submits an invoice into the Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) system. Compliance with this requirement is a material requirement of this contract. Failure to comply with this requirement may result in contract termination.

The Contract Status Report indicates the progress of work and the status of the program and of all assigned tasks. It informs the Government of existing or potential problem areas.

The Contractor's Funds and Man-hour Expenditure Report reports contractor expenditures for labor, materials, travel, subcontractor usage, and other contract charges.

(1) Access:

eCRAFT: Reports are uploaded through the eCRAFT System Periodic Report Utility (EPRU). The EPRU spreadsheet and user manual can be obtained at:

http://www.navsea.navy.mil/Home/Warfare-Centers/NUWCNewport/ Partnerships/Commercial-Contracts/Information-eCraft-/ under eCRAFT information.

The eCRAFT e-mail address for report submission is: Ecraft.nuwc.npt.fct@navy.mil. If you have problems uploading reports, please see the Frequently Asked Questions at the site address above.

(2) Submission and Acceptance/Rejection:

The contractor shall submit their reports on the same day and for the same timeframe the contractor submits an invoice in iRAPT. The amounts shall be the same. eCRAFT acceptance/rejection will be indicated by e-mail notification from eCRAFT. A report shall be submitted in accordance with CDRL A017, e-CRAFT.

5.9 System Security

The contractor shall provide a System Security Plan to identify planned control of Controlled Unclassified Information (CUI). The contractor shall ensure multi-factor authentication, FIPS 140-2 validated encryption, “need to know” principles, and security principles in accordance with NIST 800-171 (Rev 1) are implemented. See CDRL A019.

6.0 CDRLs Summary Chart

ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (NAVSEA)

a. The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the [insert named component] via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities; (4) D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

b. The contractor is required to completely fill in all required data fields using the following web address https://www.ecmra.mil.

c. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://dod.ecmra.support.desk@mail.mil.

Applicable CLINs: 0007

ELECTRONIC COST REPORTING AND FINANCIAL TRACKING (eCRAFT) SYSTEM REPORTING

(NAVSEA)

(a) The Contractor agrees to upload the Contractor's Funds and Man-hour Expenditure Reports in the Electronic Cost Reporting and Financial Tracking (eCRAFT) System and submit the Contract Status Report on the day and for the same timeframe the contractor submits an invoice into the Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) system. Compliance with this requirement is a material requirement of this contract. Failure to comply with this requirement may result in contract termination.

(b) The Contract Status Report indicates the progress of work and the status of the program and of all assigned tasks.

It informs the Government of existing or potential problem areas.

(c) The Contractor's Funds and Man-hour Expenditure Report reports contractor expenditures for labor, materials, travel, subcontractor usage, and other contract charges.

(1) Access:

eCRAFT: Reports are uploaded through the eCRAFT System Periodic Report Utility (EPRU). The EPRU spreadsheet and user manual can be obtained at: http://www.navsea.navy.mil/Home/Warfare-Centers/NUWC- Newport/Partnerships/Commercial-Contracts/Information-eCraft-/ under eCRAFT information. The eCRAFT e-mail address for report submission is: Ecraft.nuwc.npt.fct@navy.mil. If you have problems uploading reports, please see the Frequently Asked Questions at the site address above.

(2) Submission and Acceptance/Rejection:

The contractor shall submit their reports on the same day and for the same timeframe the contractor submits an invoice in iRAPT. The amounts shall be the same. eCRAFT acceptance/rejection will be indicated by e-mail notification from eCRAFT.

HQ C-1-0001 ITEM(S) 0008 - 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-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-0012 CONFIGURATION MANAGEMENT (NAVSEA) (APR 2015)

(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-SESS-80639D approved 7 April 2015 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 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 Variance.

DI-SESS-80640D approved 7 April 2015 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 document that is later approved by the Contracting Officer, the cost of developing such documentation shall be incorporated in the contract modification that implements the change.

(6) Failure to agree to such equitable adjustment in contract price shall constitute a dispute, and shall be adjudicated in accordance with the requirements of the clause entitled "DISPUTES" (FAR 52.233-1).

(g) Any cost reduction proposal submitted pursuant to the clause entitled "VALUE ENGINEERING" (FAR 52.248-1) shall be submitted as a Code V Engineering Change Proposal (VECP). DI-SESS-80639D approved 7 April 2015 and MIL-HDBK-61A of 7 Feb 2001 apply. Information required by the "VALUE ENGINEERING" clause shall also be submitted as part of the change request.

HQ C-2-0014 CONTRACTOR'S PROPOSAL (NAVSEA) (MAR 2001)

(a) Performance of this contract by the Contractor shall be conducted and performed in accordance with detailed obligations to which the Contractor committed itself in Proposal dated in response to NSWC Crane Solicitation No. N00164-19-R-

JM30.

(b) The technical volume(s) of the Contractor's proposal is incorporated by reference and hereby made subject to the provisions of the "ORDER OF PRECEDENCE" (FAR 52.215-8) clause of this contract. Under the "ORDER OF

PRECEDENCE" clause, the technical volume of the Contractor's proposal referenced herein is hereby designated as item

(f) of the clause, following "the specification" in the order of precedence.

HQ C-2-0023 EXCLUSION OF MERCURY (NAVSEA) (MAY 1998)

Mercury or mercury containing compounds shall not be intentionally added or come in direct contact with hardware or supplies furnished under this contract.

HQ C-2-0032 INFORMATION AND DATA FURNISHED BY THE GOVERNMENT - ALTERNATE II

(NAVSEA) (SEP 2009)

(a) NAVSEA Form 4340/2 or Schedule C, as applicable, Government Furnished Information, attached hereto, incorporates by listing or specific reference, all the data or information which the Government has provided or will provide to the Contractor except for

(1) The specifications set forth in Section C, and

(2) Government specifications, including drawings and other Government technical documentation which are referenced directly or indirectly in the specifications set forth in Section C and which are applicable to this contract as specifications, and which are generally available and provided to Contractors or prospective Contractors upon proper request, such as Federal or Military Specifications, and Standard Drawings, etc.

(b) Except for the specifications referred to in subparagraphs (a)(1) and (2) above, the Government will not be obligated to provide to the Contractor any specification, drawing, technical documentation or other publication which is not listed or specifically referenced in NAVSEA Form 4340/2 or Schedule C, as applicable, notwithstanding anything to the contrary in the specifications, the publications listed or specifically referenced in NAVSEA Form 4340/2 or Schedule C, as applicable, the clause entitled "GOVERNMENT PROPERTY" (FAR 52.245-1) or "GOVERNMENT PROPERTY INSTALLATION OPERATION SERVICES " (FAR 52.245-2), as applicable, or any other term or condition of this contract.

(c)(1) The Contracting Officer may at any time by written order:

(i) delete, supersede, or revise, in whole or in part, data listed or specifically referenced in

NAVSEA Form 4340/2 or Schedule C, as applicable; or

(ii) add items of data or information to NAVSEA Form 4340/2 or Schedule C, as applicable; or

(iii) establish or revise due dates for items of data or information in NAVSEA Form 4340/2 or Schedule C, as applicable.

(2) If any action taken by the Contracting Officer pursuant to subparagraph (c)(1) immediately above causes an increase or decrease in the costs of, or the time required for, performance of any part of the work under this contract, the…