W91CRB20R0009 Amendment 0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

See SF30 Continuation Page Amendment 2 Summary

1. CONTRACT ID CODE PAGE OF PAGES

J 1 62

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 13-Aug-2020

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X W91CRB20R0009

X 9B. DATED (SEE ITEM 11)

15-Jul-2020

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

13-Aug-2020

CODE

ACC - APG - W91CRB

BLDG 4310

6515 INTEGRITY COURT

ABERDEEN PROVING GROUND MD 21005-3013

W91CRB 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W91CRB20R0009

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT 2 SUMMARY

The following Sections have been updated:

Section C

Section I

Section J Updated Attachment J-4 CDRLs A003 and A004

New Attachment J-9 Questions and Answers Round 2 has been added

Section L

Section M

SECTION B - SUPPLIES OR SERVICES AND PRICES

Global Changes

CLIN 0001 -- CLIN 0011

The PSC code has changed from 6130 to 6140.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

Project Manager Close Combat Squad, Ground Soldier Systems

Conformal Wearable Battery (CWB)

STATEMENT OF WORK

SECTION C.1 - GENERAL

C.1.1 Scope.

This Statement of Work (SOW) includes tasks for manufacturing, qualification testing and delivery of the Conformal Wearable Battery (CWB) and associated documentation.

The CWBs produced under this SOW shall comply with a multiphase approach:

The Contractor shall produce and deliver the number of CWBs specified in the contract for the completion of First Article Testing (FAT), that are fully compliant with the documents cited herein, including the MIL- PRF-32383 (Attachment J-2) as modified by the MIL-PRF-32383/4X (Attachment J-1: Performance Specification).

Upon successful completion of FAT, as determined by the Government, the Contractor will be notified that they can enter a full rate production phase, delivering the quantities that are compliant with the terms and conditions of the contract. During production, the Contractor shall conduct product configuration management and quality surveillance testing to ensure conformance to the Performance Specification, and support to Government quality surveillance functions.

During the execution of this effort, the Government may elect to implement product improvements to the CWB as per 3.3 of this SOW.

C.1.2 Deliverables

The Contractor shall provide CWBs that meet the requirements of this document and the Attachment J-1: MIL-PRF- 32383-4X Performance Specification.

C.1.3 Background

The CWB is a centralized energy source that can power the Nett Warrior (NW) suite of electronic devices, the Integrated Visual Augmentation System (IVAS), and the Next Generation Squad Weapon (NGSW), while also providing recharging capability to the batteries in these devices. The CWB has the ability to: (1) increase the mission time without having to stop for battery resupply; and (2) eliminate the need to swap out the batteries in each device. The “Conformal” in the title refers to the requirement for the battery to be semi-flexible in order to conform to body and soldier-worn equipment location constraints.

C.1.4 Order of Precedence

In the event of a conflict between the text of this SOW and the references cited herein, the text of this SOW shall take precedence. Any discrepancies between documents included in this contract shall be brought to the attention of the Contracting Officer. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

C.1.5 Distribution Statement

The following distribution statements shall appear on the cover of all data produced or reproduced under this contract (unless the document is classified or the Government provides subsequent direction during contract administration):

Technical Manual(s) and Training Material will be marked with “Distribution Statement A. – Approved for public release; distribution is unlimited.”

All other data/documents: DISTRIBUTION STATEMENT D. Distribution authorized to Department of

Defense and US DoD contractor only to protect information and technical data that provides insight into vulnerabilities of U.S. critical infrastructure, including DoD warfighting infrastructure, vital to National Security that are otherwise not publicly available. [date of contract award]. Other requests for this document shall be referred to Project Manager – Close Combat Squad (CCS) 5966 12th Street, Bldg. 1024, Fort Belvoir, VA 22060

C.1.6 Applicable Documents

DEPARTMENT OF DEFENSE SPECIFICATIONS

MIL-PRF-32383 – Batteries, rechargeable, Sealed, Dated 16 June 2011 MIL-PRF-32383/4X – Battery, Rechargeable, Sealed, Lithium Ion, BB-2525 and BB-3525,12 August 2020

DEPARTMENT OF DEFENSE STANDARDS

MIL-STD-130N Change 1 Department of Defense Standard Practice: Identification Marking of U.S. Military Property MIL-STD-461G Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment MIL-STD-810G w/ Change Note 1 Environmental Engineering Considerations and

Laboratory Tests MIL-STD-882E System Safety DoDI 8500.2 Information Assurance (IA) Implementation

(Copies of these documents are available online at http://quicksearch.dla.mil/ or from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094.)

DEPARTMENT OF DEFENSE REGULATONS

Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7003 Defense Federal Acquisition Regulation Supplement (DFARS) 252.246-7001 Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7013(b)(1)

U.S. ARMY REGULATONS

AR 700-142 Type Classification, Materiel Release, Fielding, and Transfer

Non-Government publications.

ANSI/ASQC (Q9001) Quality Systems – Model for Quality Assurance in Design, Development, Production, Installation and Servicing ANSI / ASQ Z1.4 - 2008: Sampling Procedures and Tables for Inspection by Attributes

SECTION C.2 - PROGRAM MANAGEMENT

C.2.1 Technical Representative

The Government uses an Integrated Product Team (IPT) to perform CWB program management. The Government will assign a technical representative from the IPT to coordinate technical activities and maintain schedule insight with the Contractor’s efforts. A Contracting Officer Representative (COR) will also be assigned to the contract. The COR will give official guidance on technical matters, but does NOT have authority to alter any terms or conditions of the contract. Only a Contracting Officer (KO) may alter the terms and conditions of the contract.

C.2.2 Integrated Master Schedule

The Contractor shall develop and maintain an Integrated Master Schedule (IMS). All activities and tasks associated with this SOW shall be defined and logically linked, showing predecessor/successor relationships and critical path.

The defined activities shall be sufficient to account for the entire program under contract, and shall display all required data items, deliverables, integration, testing, hardware fabrication, firmware development, program events, decision points which impact contractual terms and conditions, and events requiring Government participation.

Contractor milestones shall be measurable events and individual scheduled activities shall be further decomposed if it exceeds fourteen (14) calendar days in duration. Changes to the schedule do not require Government concurrence unless the change modifies the terms or conditions of the contract or dates/durations of Government required events (e.g., reviews, testing), or how events which impact terms and conditions of the contract are linked in the schedule.

In these cases, the Contractor shall within five (5) calendar days notify the Government KO, COR, and the IPT technical representative of the required change. Accompanying the notification, the Contractor shall provide a proposed solution for Government approval prior to the Contractor implementing the change. The IMS shall be provided in accordance with (IAW) CDRL A002. If the Government KO concurs with the schedule change, a modification will be done to incorporate the revised schedule into the contract.

C.2.3 Data/Correspondence

The electronic format of all correspondence and documents shall be compatible with Microsoft Windows operating systems, and Microsoft Office 2013 suite of programs (Word, Excel, PowerPoint, and Project 2013).

C.2.4 Environmental Protection

C.2.4.1 Environmental Compliance

The Contractor shall ensure that all aspects of contract execution, to include activities associated with design, build, test, shipping, storage, and disposal are in compliance with Federal, State, and Local environmental regulations and requirements. The Contractor shall notify the KO within three calendar days if the Government gives any direction that could result in violations in Environmental Compliance.

C.2.4.2 Pollution Prevention and Hazardous Materials Management

The Contractor shall eliminate, or minimize, the use of toxic, hazardous materials and Ozone Depleting Substances in the production and testing of the CWB. To the maximum extent possible the Contractor shall avoid manufacturing processes that will have a detrimental impact upon the environment and shall select environmentally preferable, recycled, or recovered materials.

The Contractor shall comply with the Pollution Prevention Act of 1990. The Contractor shall plan, develop, implement, monitor, and maintain effective hazardous materials management process for the physical components of the CWB in accordance with applicable local, state and federal legal requirements.

C.2.5 Information Security Requirements

The Government considers, verbal information and documents handled or generated in conjunction with this acquisition to be Sensitive but Unclassified (SBU) and such information shall be protected against release to unauthorized organizations or individuals.

Release of any Government documents to outside entities, not directly associated with the efforts required for successful completion of this contract, is strictly prohibited. During all phases of contract execution, release of ANY information associated with this acquisition to ANY Government or private individual, firm, or business is prohibited. Product(s) or product information related to the production or performance of the CWB shall not be marketed, displayed, demonstrated or discussed at any trade show, symposium, or through any other medium.

Release of any information, to include information presented at public events, requires the express written approval of Government KO or Government COR or Product Manager Ground Soldier System (PdM GSS) or PdM GSS designated representative. Request for release approval shall identify the specific information to be released, the medium to be used and the purpose for the release.

The Contractor shall maintain Government-approved facilities for storage and control of classified information when required. CWB program classification information is contained in the NW Security Classification Guide (SCG).

Following contract award, the awardee will be required to complete a DD254 Form, and will receive a copy of the NW SCG. The Government, at its discretion, may determine information development by the Contractor related to this effort as classified.

C.2.6 Item Unique Identification (IUID) Requirements

C.2.6.1 Item Unique Identification

The Contractor shall implement specific Item Unique Identification (IUID) marking, as defined in MIL-STD-130 and Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7003. The IUID marking shall be incorporated into existing data plates when possible. Bar Coding and the two-dimensional (2D) IUID data matrix shall be machine-readable with common optical scanning devices and shall be accompanied by the corresponding human readable markings when practical. All 2D data matrix shall be permanently affixed and have the ability to withstand and perform within the same environmental conditions as the CWB.

The Contractor shall use Table IV (UII Construct 2) and Figure 1 of MIL-STD 130 as a guide when developing the CWB data plate.

C.2.6.2 IUID Data Plate Information

The IUID marking shall include the following:

Nomenclature Part number – not needed if NSN assigned Serial number Contract Number User Agency National Stock Number (NSN) Manufacturer’s Commercial and Government Entity (CAGE) code Date of Manufacture (MM/YYYY) Two-dimensional Unique Identification (UID) data matrix not smaller than ½ inch square

Battery markings shall also not be removed or made unreadable as per para. 3.6.15 of MIL-PRF 32383/4X.

C.2.7 Data Rights

Unless otherwise stipulated in the contract, the Government shall have “Unlimited Rights” as defined in DFARS 252.227-7013(b)(1).

Technical Data, wherein the contractor or original manufacturer has proprietary data rights, will be marked in such a manner as to identify the rights limited or unlimited. These markings shall be in accordance with Defense Federal Acquisition Regulation Supplement 227-71, Rights in Technical Data. The contractor shall grant the Government “Unlimited” data rights for all electrical / mechanical interface, operational, and maintenance type documents, software code and technical data produced under this SOW in accordance with DFARS 252.227-7013.

C.2.8 Warranty

The warranty requirements on this contract are divided into two (2) parts: CWB Performance Warranty and the Warranty of Contract Data.

C2.8.1 Performance Warranty

The contractor warrants this product to be free from defects in workmanship and materials, under normal operations and conditions, to include storage at temperatures specified in the MIL-PRF 32383/4X, for a period of twenty-four

(24) months. The warranty shall also cover defects in the software / firmware code that may result in the software / firmware not performing IAW the Attachment J-1: Performance Specification. The warranty will commence upon delivery to the Government. The warranty shall be included in the unit price. During the warranty period, the contractor shall replace defective CWBs (i.e. CWBs that fail to comply with the Attachment J-1: Performance Specification) within thirty (30) days of receipt, at no cost to the Government. The warranty will exclude CWB failures caused by natural disaster, or misuse. The contractor shall pay for all shipping costs for warranty items. All delivered CWBs shall also be covered by a comprehensive software / firmware warranty. Within thirty (30) days from the time the defect is reported by the Contractor or the Government the contractor shall produce a fix, and provide a corrective action plan that is approved by the KO to remedy any defects in the CWB software / firmware.

The aforementioned software / firmware fix shall be accomplished by the Contractor without any manner of physical alteration or mechanical disassembly of the CWB, and without cost to the Government, or the failed CWB must be replaced with a new CWB that is free of defects of any kind.

C.2.8.2 Warranty Tracking

The Contractor shall establish and maintain a warranty tracking system that identifies and documents all CWBs warranted under this contract. Each item warranted shall be indexed and identified by serial number, model or part number, and date of warranty expiration. All pertinent data required for the Government to pursue warranty provisions, remedy, and relief for each item shall be maintained by the Contractor for the duration of five (5) years past the end of each CWB’s warranty period and shall be provided to the Government upon request. All warranty claims and transactions shall be documented and made available for Government review during scheduled meetings and/or reviews.

C.2.8.3 Warranty of Data

The Contractor shall warranty all data delivered under this contract in accordance with DFARS 252.246-7001 for warranty of data requirements and invocation stipulation.

C.2.9 Program Protection

The Contractor shall support the Government critical functionality assessment of the CWB, to include an assessment of the source of components, subassemblies and supply chain for any impacts or risk to the program.

SECTION C.3 - ENGINEERING AND TECHNICAL ACTIVITIES

The Contractor shall perform the tasks identified, and deliver the technical documentation specified, in the following subtasks:

C.3.1 Engineering

The Contractor shall perform engineering activities consistent with internal processes and contract requirements.

Minimum engineering activities comprise; (a) configuration management, (b) risk management, (c) value engineering, (d) identification of potential obsolesce of part/components, and (e) identification of potential areas for product and manufacturing improvements, along with routine monitoring of CWB performance.

C.3.2 Technology Management Plan

The Contractor on an annual basis shall present a summary of their analysis of emerging/advanced technologies that offer the opportunity for improvements to the CWB, and are candidates for product improvement based Engineering Change Proposals (ECPs). Areas of interest to the Government include, but are not limited to technologies, components, and materials that increase capacity, reduce weight, decrease charging time, reduce price, and offer improvements in safety. The status of this analysis shall be topic at each quarterly In Process Review (see Table 1:

Meetings and Reviews). Information shall be in compliance with CDRL A003.

C.3.3 Product Improvement

Any time after contract award, the Contractor may submit a proposal(s) for changes to materials, components, subassemblies, and/or manufacturing processes that have the potential for CWB enhancement. These proposals can address such improvements as increased manufacturability, improved quality, higher performance, and/or reducing the unit price.

The written proposal shall contain sufficient information for the Government to determine the technical merit of the approach for improving the CWB. Proposals shall include, at a minimum, a technical discussion of the proposed approach, the methodology for obtaining the results of the proposed approach, the benefits to the CWB, a Rough Order of Magnitude (ROM) of the projected price for FAT, and the potential impact on the CWB unit price.

The contractor shall be in compliance with C.3.5 Configuration Management or as directed by the Government for any and all changes.

C.3.4 Configuration Baseline

The CWB has a two (2) part configuration baseline, Government and Contractor. The Attachment J-1: Performance Specification is considered the Government’s CWB functional baseline. The Contractor’s Product Baseline (drawings and assembly instructions) shall be traceable to the Government’s functional baseline. The product baseline shall be configuration managed using the contractor’s internal processes. A Technical Data Package (CDRL A008) shall be maintained and available for Government review and Government use that describes the following:

Configuration and interface dimensional data applicable to the envelope, mounting and interconnection of the related items;

Complete external interface definitions (mechanical, electrical, electronic, etc.), which affect the physical or functional characteristics of co-functioning items;

Assembly and testing instructions Component and assembly part numbers, drawings and locations within the battery.

Component and material sources of supply Firmware versions Detail connectors, pinouts, mechanical, and electrical parameters needed to interface the CWB with external components or systems to the CWB Detail software Application Programming Interfaces (APIs) information necessary to query, command, or communicate with the CWB Equipment and procedures necessary to upgrade the software/firmware of the CWB Detail diagnostic, troubleshooting, maintenance, and repair procedures for the CWB.

Any other characteristics that cannot be changed without affecting CWB interfaces.

The Contractor shall record and save the following information for each item produced under this SOW:

Bill of materials (to include component manufacturer and related date code) Software / Firmware Version All related Internal Contractor conducted test results All Government required test results Battery production lot traceability records

All of the data in this section shall be available to the Government for no less than five (5) years after the Government acceptance of delivery of the battery.

C.3.5 Configuration Management

The Contractor shall maintain a configuration status accounting system that provides an auditable trail of all configuration changes.

Changes to the Contractor’s product baseline are accomplished through an ECP, or a Value Engineering Change Proposal (VECP). Either of these documents can be initiated by either the Government or the Contactor. The contractor shall maintain a record of the actual effective date of each approved change resulting from an Engineering Change Proposal (ECP) or Value Engineering Change Proposal (VECP). These records shall identify:

(a) Approval date of the change,

(b) The specific units (identified by serial number, contract/lot number, etc.) of the as-delivered Configuration Item affected by an approved change,

(c) Nature of the change,

(d) Date implemented into production,

(e) And all required concurrence and approval signatures.

When the contractor proposes changes to the Attachment J-1: Performance Specification, the contractor shall submit an ECP (Appendix B) to the Government for a Request for Deviation (RFD), a Request for Waiver (RFW), or a permanent Configuration Change Request. ECPs submitted to the Government shall be sufficiently detailed (with drawings as applicable) to allow the Government to evaluate the technical, logistical, price, schedule and programmatic impacts. An ECP may include multiple suggested changes if they are related to a single overall topic or objective. Government approval through the KO is required prior to implementing any change of this type. Any changes to the Product Baseline shall not impact operational use, maintenance activities, interchangeability and interoperability without Government approval through the KO.

C.3.5.1 Configuration Control Signature Authority

The Contractor shall identify to the KO, the COR and the Government IPT technical representative, the name(s) of the official(s) of its organization who are authorized to sign change proposals submitted for Government review.

This information shall be provided as part of the initial (Post Award Conference) meeting material. Name changes shall be provided as necessary.

C.3.5.2 ECP Class Definitions

ECPs shall be considered as Class I or Class II as defined below.

C.3.5.2.1 Class I Engineering Change

A Class I Engineering Change impacts the form, fit, function or safety of the CWB and requires written Government approval before implementation, and may require a repeat of some or all of the FAT at the discretion of the Government. This includes firmware, parts/components, subassemblies and any assembly materials of the CWB.

C.3.5.2.2 Class II Engineering Change

A Class II Engineering Change does not impact the form, fit, function or safety of the item, its ability to support the usage of the end items, or related logistics and sustainment functions. A Class II engineering change does not impact the CWB’s performance of the requirements detailed in the Attachment J: 1 - Performance Specification. A Class II engineering change does not impact the CWB support concept, is transparent to the Government/Military operators and maintainers, and does not impact information contained in Government owned technical or logistics documentation used to support the CWB. Notice of a Class II engineering changes shall be provided to the COR and IPT technical representative prior to implementation, but does not require Government approval.

Class II engineering changes shall be tracked by the Contractor and shall be discussed at scheduled Government reviews.

If combinations of multiple Class II changes in effect constitute a Class I change, then the contractor shall correct at no cost to the Government, any product delivered or in the Work-in-Process as well as any associated documentation and any other penalty the KO imposes based on the resolution of this inappropriate classification of the engineering change.

The implementation of a Class II engineering change shall not impact contract price or delivery schedule. If implementation of a Class II engineering change impacts price or schedule the Government may seek equitable adjustment to the contract.

C.3.5.3 Requests for Deviation/Waiver

C.3.5.3.1 Request for Deviation (RFD)

A RFD describes a proposed temporary departure prior to manufacture from configuration documentation for a specific number of units or specific period of time. A RFD enables the Government to determine the impact on performance, operational readiness, logistical support and other affected areas. A RFD shall not be revised.

Changes to an RFD shall be treated as a new RFD, assigned a new RFD number and submitted for Government approval.

C.3.5.3.2 Request for Waiver (RFW)

A RFW is used to obtain authorization to deliver non-conforming material that does not meet all criteria, but is suitable for use "as-is" or after repair. A RFW enables the Government to evaluate and authorize acceptance of items not conforming to all contract requirements. An RFW shall not be revised. Changes to an RFW shall be treated as a new RFW, assigned a new RFW number and submitted for Government approval.

C.3.6 Safety Engineering

The Contractor shall ensure that contract safety requirements are met. To ensure that safety tasks meet Government standards, the Contractor shall provide qualified personnel to accomplish the required safety tasks, establish the authority for implementing safety tasks through all levels of management, allocate appropriate resources, and establish lines of communication between system safety and other functional elements of the program (see MIL- STD-882E for additional guidance). A summary of any open System Safety and Health hazards, and mitigations being worked shall be provided during program reviews. The Contractor shall provide safety related technical information and clarification through the assigned Government technical representative to support the Government safety release process upon request.

C.3.7 Risk Management

Risk management and reporting shall be an integral part of all technical reviews, periodic program management reviews, and meetings. The Contractor shall document and manage all risks, risk mitigation efforts, and risk status, to include:

Brief description, including both the title and type, of the risk;

Brief description of the risk root causal factor(s);

Assessment of the risk's likelihood and the estimated severity of its effect on the delivery of qualified CWBs if mitigation fails;

Planned mitigations, along with critical dates (risk reduction milestones), that address the root cause(s) and effect(s);

Technical Performance measures, value engineering activities and other tracking metrics.

SECTION C.4 - MEETINGS AND REVIEWS

C.4.1 General

The Contractor shall include the reviews, meetings and conferences listed in Table I: Meetings and Reviews, in the IMS. For ease of discussion the terms reviews, meetings and conferences are used interchangeably throughout this SOW. The Contractor shall conduct each review in cooperation with the appropriate Government designated representative.

Unless specified otherwise in this SOW or directed by the Government, the Contractor shall host each review at their facility, and shall provide necessary personnel, equipment, technical data, technical products (presentation materials, mockups, drawings, models, software / firmware, etc.), and the provisions for remote teleconferencing required to conduct each review. The Contractor shall also provide all review presentations electronically at least three (3) working days (unless specifically stated elsewhere in the contract) prior to each review. At the conclusion of each review, the Contractor shall prepare meeting minutes (IAW with CDRL A001), including copies of all documents and presentations made during the meetings, list of actions and assigned action officers, and closure suspense dates, within five (5) calendar days.

Table 1: Meetings and Reviews

Name of Review/Meeting * Frequency SOW Paragraph

Post Award Conference Once C.4.2

Quarterly In Process Review

90 calendar days after Post Award Conference then Quarterly

C.4.3

FAT Test Readiness Review Once** C.4.4

System Verification Review Once** C.4.5

Physical Configuration Audit Once** C.4.6

Weekly Telecon Weekly C.4.7

Logistics Guidance Conference/Government Provisioning

Conference Once

C.7.1/C.7.2

* The Government/Contractor team shall attempt to combine reviews/meetings if possible.

** Once for each CWB configuration proposed by the Contractor.

C.4.2 Post Award Conference

The Contractor shall conduct a Post-Award Conference no later than (NLT) fourteen (14) calendar days after contract award or as otherwise specified by the Government. The Contractor shall present, as a minimum, an overview of its entire contractual effort within the IMS, to include: CWB design review and completion schedule, FAT schedule, capital equipment schedule (as required), organization structure (including subcontractors), entrance/exit criteria for significant events, program risks, subcontractor/supplier award schedules, and manufacturing planning, and production schedule. The Contractor shall submit the presentation material and meeting minutes IAW CDRL A001.

C.4.3 Quarterly Reviews

The Contractor shall conduct the first Quarterly Review NLT ninety (90) calendar days after the Post Award Conference, and on a quarterly basis thereafter. The Contractor and subcontractor representatives (as required by the Contractor) shall participate and support quarterly program reviews. The program reviews may be conducted as Teleconferences or face-to-face, as determined by the Government. The program reviews shall provide a working level forum to identify, discuss, and resolve issues that could affect the CWB performance, manufacturing, testing, logistical support, deliveries, and program schedule. The Contractor shall submit the presentation material and meeting minutes IAW CDRL A001.

The Quarterly Review shall, at a minimum, include status on the following topics:

Program schedule;

Component and material supply;

Manufacturing capability;

Test and qualification;

Failure analysis (when appropriate);

Risks and Issues.

C.4.4 Contractor FAT Test Readiness Review (TRR)

A successful FAT Test Readiness Review (TRR) (CDRL A009) is required prior to conducting the Contractor FAT.

The Contractor FAT TRR assesses test objectives, test methods and procedures, scope of tests, and safety. It confirms that required test resources have been properly identified and coordinated to support planned tests. The Contractor FAT TRR verifies the traceability of planned tests to contract requirements. It verifies completeness of test plan / procedures. The Contractor shall conduct a FAT TRR at least fourteen (14) calendar days prior to the beginning of FAT, unless otherwise agreed to by the Government. The Contractor shall meet the following entrance criteria prior to commencing the FAT TRR:

Documentation that demonstrates the ability of the proposed design to meet the requirements of the following as detailed in the Section J-1: Performance Specification.

o Nail penetration, cell (para. 3.7.1.2) o Nail penetration, battery (para. 3.7.2.8.1) o Crush, cell (para. 3.7.1.3) o Projectile (para. 3.7.2.6) o Weapons Characterization (para. 3.7.2.8.3) o Transportation Requirements (para 3.9)

Contractor FAT plan/procedure approved by the Government;

Completion of the build of 200 CWBs on the Contractor production line;

Required resources are identified, scheduled and available (i.e. people, test articles, facilities, data systems, support equipment, logistics, etc.);

Contractor FAT risk assessment completed.

The decision to proceed into the Contractor FAT shall be documented in meeting minutes for Government approval.

The Contractor shall submit the presentation material and meeting minutes IAW CDRL A001.

C.4.5 System Verification Review (SVR)

The System Verification Review (SVR) is a Government conducted event, with Contractor participation, supported by data from the Contractor FAT and Government Testing. The SVR verifies that the CWB product meets the Attachment J-1: Performance Specification. The Government will leverage the Contractor FAT, Government Testing, Information Assurance (IA) certifications, CWB Material Type Classification documentation (reference AR700-142), and results of the Physical Configuration Audit, as the primary data sources for SVR. The Government will assess all test and verification data to determine a successful SVR prior to the Contractor commencing full production. The results of the SVR shall be recorded by the Contractor IAW CDRL A001.

C.4.6 Physical Configuration Audit (PCA)

The Physical Configuration Audit (PCA) establishes that the, “as built” configuration items physically match the full production product baseline manufacturing documentation. The Contractor shall conduct a Government witnessed PCA , updating documentation as required, and provide a certification that the product baseline manufacturing documentation matches the, “as built” items as part of CDRL A010. The Contractor shall include the PCA in the schedule and provide the Government two week (14) calendar day notification prior to the PCA. The end item and associated support equipment shall be available during the review as applicable. The Contractor is required to successfully pass the PCA following a successful FAT and prior to the first Government production quantity lot acceptance. The results of the PCA shall be recorded IAW CDRL A001.

C.4.7 Weekly Telecon

The Contractor shall provide weekly status updates via scheduled telecons to the Government on contract execution, program risks and schedule status. The Contractor shall submit the presentation material and meeting minutes IAW

CDRL A001.

SECTION C.5 - MANUFACTURING MANAGEMENT

Diminishing Manufacturing Sources and Material Shortages (DMSMS)

The Contractor shall identify and forecast Diminishing Manufacturing Sources and Material Shortages (DMSMS) obsolescence timelines throughout the full contract period IAW CDRL A005 and using DI-MGMT-82274 (Appendix C). The Contractor shall provide impact assessments and mitigation plans when manufacturing sources and / or material shortages are anticipated to impact deliveries according to the terms and prices detailed in the contract, and if a Class I or Class II ECP will be required. The DMSMS forecasts and mitigation plans (if required) shall be presented at the quarterly reviews.

C.5.2 Quality Assurance

Quality shall be viewed as an attribute, which is controlled by the Contractor’s engineering/design and business processes. The Contractor shall establish and maintain a quality system that, at a minimum, adheres to the requirements of ISO 9001 or the ANSI/ASQC equivalent, ASQC (Q9001), “Quality Systems – Model for Quality Assurance in Design, Development, Production, Installation and Servicing” or an equivalent Contractor-specific quality system consistent with defined internal processes. The Government reserves the right to disapprove the quality system or portions thereof when it fails to meet its contractual requirements. Acceptance of the Contractor quality system (CDRL A004) shall not in any way relieve the Contractor of responsibility for compliance with all contract requirements. The quality system plan, procedures and all documentation and data that comprise the quality system shall be made available to the Government. The Government may require the Contractor to perform audits, inspections, verifications, and tests to ascertain conformance to the requirements and the adequacy of the implementation procedures.

C.5.3 Government Furnished Material (GFM) For all GFM received under this contract, the contractor shall be responsible for conducting all necessary examinations, inspections, maintenance, and tests. The contractor shall be responsible for reporting all inspection results, maintenance actions, losses, and damage to the Government.

C.5.4 Government Furnished Equipment (GFE).

For all GFE received under this contract, the contractor shall be responsible for securing this equipment and assuring it is maintained in functioning condition. The contractor shall be responsible for reporting all inspection results, maintenance actions, losses, and damage to the Government.

SECTION C.6 – PRODUCT TEST AND ANALYSIS

C.6.1 Contractor First Article Testing FAT/ Plan/Procedures The Contractor shall provide a FAT Test Plan/Procedures that when executed verifies compliance with the Attachment J-1: Performance Specification Table IV “First Article Tests”), and in accordance with CDRL A006.

The Government approval of the Contractor FAT test plan/procedures shall occur prior to commencement of the test readiness review.

The FAT Test Plan/Procedures, in addition to CDRL A006 content requirements, shall contain the following additional information:

The delineation and allocation of tests to be performed on each of the First Article units and the order of such tests;

Test procedures for each test and the data sheets to be employed to document the results of testing;

Identification of required test facilities, equipment and any personnel with unique capabilities (cross referenced to the appropriate test);

A table which cross references the paragraph number of the specification requirement (including a brief description of the requirement) and the associated paragraph number of the First Article Test Plan.

C.6.2 Contractor FAT

a. All 200 CWBs in support of the Contract FAT shall be assembled at the same location, on the same production line, at which future production CWBs shall be assembled, using the same parts, materials, and manufacturing processes to be employed for subsequent production.

b. All training required for operation of Government Furnished Equipment shall be performed prior to initiation of FAT.

c. Written notices concerning the time and location of FAT shall be furnished to the KO, the COR and the Government’s technical representative no less than twenty-one (21) calendar days prior to the commencement of FAT. The Government at its discretion may have a Government representative to witness all or specific tests.

d. The Contractor FAT testing shall be conducted in accordance with the associated Government approved Contractor FAT test plan/procedures.

e. The Contractor shall verify and document that the FAT CWBs meet the Performance Specification requirements criteria (i.e. IAW MIL-PRF-32383/4X, Table IV “First Article Tests”) to provide the Government confidence that the CWBs are acceptable for Government Integration Testing.

f. The minimum lot size for the first production lot is 200 units, of which each battery shall have passed Group A inspection in Attachment J-1 Performance Specification and up to 93 units, selected by the Government from the 200 built CWBs, shall undergo the contractor FAT testing.

g. Upon successful completion of the contractor FAT, the contractor shall provide the associated contractor FAT test report in accordance with CDRL A007.

C.6.3 Failure During Contractor FAT

In the event of a CWB failure to meet the requirements of the Attachment J-1: Performance Specification during Contractor FAT, all items in the lot shall be withheld from Government acceptance, and a failure report (including proposed corrective action) shall be prepared by the contractor and submitted in accordance with the Failure Analysis Process (SOW paragraph C.6.13) for Government approval.

FAT failures shall be reported to the KO, COR and Government technical representative within twenty-four (24) hours of occurrence. All testing that is currently in process at the time of the incident within the same group as the failed test can continue until completed. The impact of the failure on tests that are in process shall be noted utilizing the Failure Reporting, Analysis and Corrective Action System (FRACAS) (SOW paragraph C.6.13) for Government approval. No new tests or corrective actions shall be commenced without prior approval by the Government. The impact of a failure on the entire FAT will be evaluated by the Government and any of the tests, including test that passed, may need to be repeated at the discretion of the Government based on the Failure Analysis Report. Any additional testing required as result of a FAT failure will be at the contactor’s expense. All FAT failures, corrective actions and retest shall be summarized in the FAT report.

Once the corrective action has been implemented and verified to the Government’s satisfaction, the CWBs can be presented to the Government for conditional acceptance pending successful completion of both the balance of the FAT and the Government Integration Testing of the system configurations identified in the Performance Specification.

C.6.4 Contractor FAT Report

Contractor FAT Report. A Contractor FAT Report shall be prepared and submitted IAW FAR 52.209-3 and CDRL A007, within 14 calendar days of the completion of Contractor FAT. The FAT Report shall be complete, accurate, readable, and shall provide sufficient data to determine that the hardware item meets all the requirements delineated in the contract. The contractor FAT report shall address all testing performed, failures encountered and corrective actions implemented.

C.6.5 FAT Approval

Contract FAT samples shall meet all contractual requirements or all variances shall be documented by Government approved waivers. First Article approval shall be contingent upon the submission of a complete and acceptable FAT report to include verification of corrective action for reported FAT failures to include adequacy of identified changes to the design/manufacturing process.

C.6.6 Disposition of FAT Units

Any CWBs that determined to be defective during FAT, other than those that are damaged by destructive tests, shall be replaced under Warranty, at no cost to the Government. Any units damaged during FAT that are not eligible for Warranty, shall be disposed by the Contractor.

C.6.7 Government Integration Testing (GIT).

The Government will conduct independent testing on defined integrated NW, IVAS, and/or NGSW systems configured with the CWB. The GIT is conducted to ensure that the contract requirements are satisfied for the integrated system configurations identified in the Attachment J-1: Performance Specification, in an operational environment. GIT may begin concurrently, or occur subsequent to the Contractor FAT. The GIT test locations are anticipated to be Aberdeen Test Center, MD., Electronics Proving Ground, AZ., Yuma Proving Ground, AZ., and / or Eatontown, NJ.

C.6.8 Contractor support during the GIT.

The Contractor shall provide two (2) participants in the GIT for a period not to exceed two (2) weeks. The Government will pull the required number of CWBs out of the Contractor FAT production build lot. The Contractor participants shall monitor all battery performance, record all battery anomalies or failures, and provide a detailed final report (IAW CDRL A001) within 14 calendar days of the completion of GIT, including proposed corrective actions for the battery for anomalies and/or failures observed during the GIT.

C.6.9 Failure During Contractor GIT

In the event of a CWB failure to meet the requirements during Government Integration Testing of the system configurations identified in the Attachment J-1: Performance Specification, all items in the lot shall be withheld from Government acceptance, and a failure report (including proposed corrective action) shall be prepared by the contractor and submitted in accordance with the Failure Analysis Process (SOW paragraph C.6.13) for Government approval.

GIT failures shall be reported to the KO, COR and Government technical representative within twenty-four (24) hours of occurrence. All testing that is currently in process at the time of the incident within the same group as the failed test can continue until completed. The impact of the failure on tests that are in process shall be noted utilizing the Failure Reporting, Analysis and Corrective Action System (FRACAS) (SOW paragraph C.6.13) for Government approval. No new tests or corrective actions shall be commenced without prior approval by the Government. The impact of a failure on the entire GIT will be evaluated by the Government and any of the tests, including test that passed, may need to be repeated at the discretion of the Government based on the Failure Analysis Report. Any additional testing required as result of a GIT failure will be at the contactor’s expense. All GIT failures, corrective actions and retest shall be summarized in the GIT report.

Once the corrective action has been implemented and verified to the Government’s satisfaction, the CWBs can be presented to the Government for conditional acceptance pending successful completion of both the balance of the GIT of the system configurations identified in the Attachment J-1 Performance Specification and the Contractor

FAT.

C.6.10 CWB Updates Based on FAT & Government Integration Testing

The Contractor shall incorporate all necessary changes to the CWB to correct failures to meet Attachment J-1:

Performance Specification requirements identified during Contractor FAT and/or during Government Integration Testing at no additional cost to the Government.

Retesting of specific First Article tests, or a complete First Article Test, may be required at no additional cost to the Government, to demonstrate compliance with the Performance Specifications. Such corrective action and subsequent retesting if required will be based on the Government’s acceptance of the completed FRACAS analysis for determining the cause of the failure(s).

C.6.11 Conformance Acceptance Testing (CAT)

The CAT is a subset of the more extensive Contractor FAT testing and as such the Government approved Contractor FAT plan/procedures can be reused for the applicable CAT testing. If a particular CAT test is not part of the existing Contractor FAT test plan/procedure then the Contractor shall update the Contractor FAT test plan/procedure and resubmit for Government approval prior to conducting any of the CAT testing.

The CAT consists of Groups A, B, and C as defined in MIL-PRF 32383 and MIL-PRF 32383/4X and this SOW.

During full production, which occurs after successful completion of Contractor FAT, the Contractor shall conduct on each production lot: Groups A (100% of all items), Group B, and Group C tests, as specified in this SOW and in Attachment J-1 performance specification. All CAT samples shall be randomly chosen by the Government. The use of lot sampling shall not eliminate the Contractor’s responsibility that all products delivered to the Government shall meet all performance requirements on the contract. Upon successful completion of each CAT lot testing the Contractor shall provide a CAT Lot Test Report (CDRL A014). The CAT Lot Test Report shall address all testing performed, failures encountered and corrective actions implemented.

Sampling for…