DRAFT SOW for PBC.docx

Platoon Battery Charger (PBC)

DRAFT

Statement of Work (SOW)

1. SCOPE

This Statement of Work (SOW) includes tasks for manufacturing, qualification testing, and delivery of the Platoon Battery Charger (PBC) and associated required documentation. For purposes of this document, the term PBC shall be used to define the basic charger and all the required components (cables, adapters, connectors, etc.). The PBCs produced under this SOW shall comply with a multiphase approach:

· The Contractor shall produce and deliver the quantity of PBC prototypes specified in the contract that demonstrate the proposed design’s capabilities to meet or exceed the requirements of the PBC Performance Specification.

· Upon the completion of the prototype production phase, the delivered prototypes will undergo limited, specific PBC Performance Specification tests as detailed in 5.2, which will be identified in the solicitation that includes this SOW. These tests are referred to as the Prototype Qualification Tests (PQT).

· Upon successful completion of the PQT, as determined by the Government, and submittal and acceptance of the associated test report, the Contractor will be notified that they will be eligible for competing for the separately planned, competed contract to be awarded for production of PBC.

Deliverables The Contractor shall provide chargers that meet the requirements of this document as defined in the PBC Performance Specification and related contractual documentation.

Background The PBC is man-portable bulk battery charger that can charge a variety of batteries that the Soldier carries in austere environments. The PBC will facilitate a unit’s ability to operate self-sustained from battery resupply for operations up to and exceeding seventy-two (72) hours in duration. The design of the PBC meets the charging requirements of the dismounted Platoon Charger as laid out in the Capabilities Development Document-Updated (CDD-U) for Small Unit Power (SUP), signed 24 March 2022.

2. APPLICABLE DOCUMENTS

Table 1 below lists the documents which form a part of this SOW to the extent specified herein. Unless otherwise specified, the latest revision of each document shall apply.

Table 1 – Applicable Documents Guide/Regulation/ Specification/Standard

Discrepancies The contractor is responsible for notifying the Procuring Contracting Officer (PCO) immediately in the event that any information contained within this SOW contains any inconsistencies and or vacuities.

Copies of Specifications The contractor shall review the entire contract to identify all directly cited and subsequent referenced documents. Copies of the specifications required by contractors in connection with specific procurement functions should be obtained from the procuring activity, as directed by the PCO.

3. PROGRAM MANAGEMENT

This section is outlined in four sub-sections: Integrated Product Team (IPT), Integrated Master Schedule, Environmental Compliance, and Information Security Requirements.

Integrated Product Team (IPT) The Government uses an Integrated Product Team (IPT) to perform PBC 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. An Agreement Officer Representative (AOR) will also be assigned to the contract. The AOR will give official guidance on technical matters ONLY and 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.

Integrated Master Schedule (IMS) The Contractor shall develop and maintain an 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 they exceed 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 the 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) ADRL A002. If the Government KO concurs with the schedule change, a modification will be made to incorporate the revised schedule into the contract.

Environmental Compliance The Contractor shall ensure that all aspects of contract execution, including activities associated with design, build, test, shipping, storage, and disposal are in compliance with DoD, federal, state, and local environmental regulations and requirements. The Contractor shall notify the KO within three (3) calendar days if the Government gives any direction that could result in violations in environmental compliance.

The Contractor shall eliminate or minimize the use of toxic, hazardous materials and ozone-depleting substances in the production and testing of the PBC. 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 PBC IAW applicable local, state and federal legal requirements.

Information Security Requirements The Government considers verbal information and documents handled or generated in conjunction with this acquisition to be Controlled Unclassified Information (CUI) 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 PBC 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 Soldier Warrior 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.

PBC program classification information is contained in the Nett Warrior (NW) Security Classification Guide (SCG), following contract award, the awardee will receive a copy of the NW SCG.

4. ENGINEERING AND TECHNICAL ACTIVITIES

The Contractor shall perform engineering activities consistent with internal processes and contract requirements and deliver the technical documentation specified. Minimum engineering activities include but are not limited to:

· Configuration management

· Risk management

· Identification of potential obsolescence of part/components

· Identification of potential areas for future product and manufacturing improvements

· Routine monitoring of PBC performance

Configuration Baseline The PBC Performance Specification is considered the Government’s program functional baseline. The Contractor’s product baseline (drawings and assembly instructions) shall be traceable to the Government’s functional baseline. The Contractor’s product baseline shall be configuration managed using the Contractor’s internal processes. A Technical Data Package IAW ADRL A003 shall be delivered to the Government and shall include the following:

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

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

· Firmware as a component of the PBC

· Connectors parameters, pinouts parameters, mechanical parameters, and electrical parameters needed to interface the PBC with external components or systems to the PBC

· Detail software Application Programming Interfaces (APIs) information necessary to query, command, or communicate with the PBC

· Equipment list and procedures necessary to upgrade the software/firmware of the PBC

· Graphical User Interface (GUI) IAW Performance Specification

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

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

· Description - title and type

· Description - root causal factor(s)

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

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

· Technical performance measures, value engineering activities, and other tracking metrics

5. MEETINGS AND REVIEWS

The Contractor shall conduct each review and meeting in cooperation with the appropriate Government-designated representatives. The Contractor’s IMS shall include each of the reviews, meetings, and conferences listed in Table 2. For ease of discussion, the terms “reviews”, “meetings”, and “conferences” are used interchangeably throughout this SOW.

Unless specified otherwise in this SOW or directed by the Government, the Contractor shall host each review at their facility or virtually as determined by the Government, and shall provide necessary personnel, equipment, technical data, technical products (presentation materials, mockups, drawings, models, software/firmware, etc.) and the provisions for remote teleconferencing. The Contractor shall also provide all review presentations electronically at least three (3) business days (unless specifically stated elsewhere in the contract) prior to each review. At the conclusion of each review, within five (5) calendar days, the Contractor shall provide to the Government:

· Meeting minutes IAW ADRL A001

· Copies of all documents and presentations provided during the meetings

· Lists of actions and assigned action officers and closure suspense dates

Table 2 – Meetings and Reviews

*Bi-weekly is defined as once every other week. Written meeting minutes and advanced copies of discussion materials are required. Discussion materials shall be provided no less than 24 hours prior to the meeting. The contractor shall provide a written summary of program status on non-telecon weeks.

Post-Award Conference (PAC) The Contractor shall host a Post-Award Conference (PAC) 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:

· PBC Design Review and Completion Schedule

· PQT Schedule

· Organization Structure (Including Subcontractors)

· Entrance/Exit Criteria for Significant Events

· Program Risks

· Subcontractor/Supplier Award Schedules

· Manufacturing Planning

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

Prototype Qualification Test (PQT) Test Readiness Review (TRR) A successful PQT TRR and approved PQT Test Plan is required prior to the initiation of the PQT. The PQT 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 PQT TRR verifies the traceability of planned tests to contract requirements. It verifies completeness of test plan / procedures. The Contractor shall conduct a PQT TRR no more than fourteen (14) calendar days prior to the beginning of PQT, unless otherwise agreed to by the Government. The Contractor shall meet the following entrance criteria prior to commencing PQT TRR:

· Government-approved PQT Plan (See 6.1) that demonstrates the step-by-step test procedures of the six (6) test requirements detailed in the Performance Specification. These tests are:

· Battery Types and Charge Times (Perf Spec 4.5.1.1) (2 chargers ea.)

· Input Voltage (Perf Spec 4.5.5.1) (1 charger ea.)

· Operating Temperature (Perf Spec 4.7.1) (2 chargers ea.)

· Transit/Drop Test (Perf Spec 4.7.7.2) (3 chargers ea.)

· Immersion (Perf Spec 4.7.10) (2 chargers ea.)

· Operation in Rain (Perf Spec 4.7.12 (2 chargers ea.)

· Completed build of the number of prototype samples required by the contract

· Identified, scheduled and available required resources (i.e., people, test articles, internal and external facilities, data systems, support equipment, logistics, etc.)

· Completed PQT risk assessment

The Contractor shall submit the presentation material IAW ADRL A005 – PQT Test Plan. The decision to proceed into the PQT shall be documented in meeting minutes for Government approval.

IPT Bi-Weekly Meeting (Telecon) The Contractor shall provide bi-weekly status updates via scheduled telecoms to the Government on contract execution, program risks, and schedule status. Meeting minutes shall be provided to the Government IAW ADRL A001.

6. PROTOTYPE TEST AND ANALYSIS

The Contractor shall conduct a TRR based on the PQT Test Plan to assess test objectives, schedule, test methods and procedures, scope of tests, safety, and to verify the required test resources have been properly identified and coordinated to support planned tests. The Contractor shall host the PQT TRR no more than fourteen (14) days before the start of PQT. At TRR, the Government shall verify the traceability of tests to program requirements, determine the completeness of the test procedures and compliance with test plans and descriptions.

PQT – Test Plan The Contractor’s PQT Test Plan, when executed, verifies compliance with the testing to be conducted as required in 5.2 detailed in the Performance Specification. The document shall be prepared IAW ADRL A005. The Government approval of the PQT Test Plan shall occur prior to commencement of the Test Readiness Review. ADRL A005 shall contain the following information/documentation:

· The delineation and allocation of tests to be performed on each of the prototype 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 PQT Test Plan

· A cover sheet that contains:

· The signature and date of the preparer

· The signature and date of the company approver

· The signature and date of the Government Technical approver

· A configuration control page that is blank. This page will be used for any changes that are made after the document is approved by the Government.

· Data sheets for each test, which should contain entry blocks for the following at a minimum:

a. Manufacturer

b. Contract Number

c. Specification number and revision date

d. Date test was performed

e. Test being conducted with the appropriate pass/fail criteria

f. Did the test pass or fail?

g. For each charger tested:

i. Serial number

ii. Measured test result for each parameter tested (if applicable)

iii. Any unusual conditions observed during the test

iv. Signature (initials) of the person performing the test, person who reviewed the results / Government witness (if required)

PQT – Test Procedures

· To the maximum extent possible, all chargers built in support of the PQT shall be assembled at the same location, on the same production line, at which future production PBCs shall be assembled, using the same parts, materials, and manufacturing processes to be employed for possible full rate production.

· Written notices concerning the time and location of PQT 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 PQT. The Government at its discretion may have a Government representative witness all or specific tests.

· The Contractor PQT testing shall be conducted IAW the associated Government approved Contractor PQT Test Plan IAW ADRL A005.

· Upon successful completion of the contractor PQT, the contractor shall provide the associated contractor PQT Test Report IAW ADRL A006.

Failure Reporting, Analysis, and Corrective Action System (FRACAS) The Contractor shall utilize a closed-loop FRACAS IAW ANSI/GEIA-STD-0009A, as its mechanism for monitoring and communicating throughout the organization descriptions of test and field failures, analyses of failure modes and root cause failure mechanisms, the status of design- and/or process-corrective actions, risk mitigation decisions, the effectiveness of corrective actions, and lessons learned. The Contractor shall address failure modes in a timely manner, consistent with their impact on safety, reliability, performance, and total life cycle cost.

In the event of a charger failure to meet the requirements of the Performance Specification during PQT, 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 IAW the FRACAS for Government approval.

PQT 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. No new tests or corrective actions shall be commenced without prior approval by the Government. The impact of a failure on the entire PQT 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 FRACAS Report in ADRL A004. Any additional testing required as result of a PQT failure will be at the contactor’s expense. All PQT failures, corrective actions and retest shall be summarized in ADRL A006 – Test Report.

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

Failure During PQT In the event of a PBC failure to meet the requirements of the Performance Specification during PQT, 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 IAW the FRACAS for Government approval.

PQT 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. No new tests or corrective actions shall be commenced without prior approval by the Government. The impact of a failure on the entire PQT 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 FRACAS report. Any additional testing required as a result of a PQT failure will be at the contactor’s expense. All PQT failures, corrective actions and retest shall be summarized in the PQT Test Report.

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

PQT – Test Report A PQT Test Report shall be prepared and submitted IAW ADRL A006, within 14 calendar days of the completion of PQT. The PQT Test 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 PQT Test Report shall address all testing performed, failures encountered, and corrective actions implemented.

PQT Approval Contractor PQT samples shall meet all contractual requirements, or all variances shall be documented by Government approved waivers. PQT approval shall be contingent upon the submission of a complete and acceptable PQT Test Report to include verification of corrective action for reported PQT failures to include adequacy of identified changes to the design/manufacturing process.

7. PQT Exit Criteria Successful conclusion of OTA is an approved PQT Test Report and delivery of ten (10) fully functional sample prototypes. The PQT is a subset of the full production qualification test (“First Article Test” or FAT) defined in the PS. The Government reserves the right to witness any or all of the PQT. The set of tests required is as follows:

a. Battery Types and Charge Times (PS Section 4.5.1.1)

b. Input Voltage, AC (PS Section 4.5.5.1)

c. Temperature (PS Section 4.7.1)

d. Transit Drop (PS Section 4.7.7.2)

e. Immersion (PS Section 4.7.10)

f. Rain (PS Section 4.7.12)

8. Disposition of PQT Units Any chargers determined to be defective during PQT, including those from the prototype lot from which the PQT samples were selected but not utilized, other than those that are damaged by destructive tests, shall be replaced and delivered to the Government. Disposition of PQT samples subjected to testing and considered operational shall be determined by the Government.

Government Integration Testing (GIT) The Government will conduct independent testing on defined integrated NW, IVAS, and/or NGSW systems configured with the PBC. The GIT is conducted to ensure that in an operational environment, the contract requirements are satisfied for the integrated system configurations identified in the Performance Specification.

GIT will not commence prior to the initiation of PQT and will be scheduled at a time when the Government has a reasonable expectation that PQT will be completed without any safety or major performance-related failure.

GIT test location is anticipated to be held at Aberdeen Proving Ground, MD.

Contractor Support During GIT The Contractor shall provide two (2) participants for the GIT for a period not to exceed two (2) weeks. The Government will pull the required number of chargers out of the Contractor PQT prototype build lot. The Contractor participants shall monitor all battery performance, record all battery anomalies or failures, and provide a detailed final report IAW ADRL A007, including proposed corrective actions for observed anomalies and/or failures within 14 calendar days of GIT completion.

Failure During GIT In the event of a charger failure to meet the requirements during GIT, all items in the lot shall be withheld from Government acceptance and a FRACAS report including proposed corrective actions, shall be prepared by the Contractor and submitted IAW ADRL A004 for Government approval.

Safety Assessment Report (SAR) The Contractor shall prepare a SAR and provide Safety Data Sheets (SDS) for the PBC IAW ADRL A007. The SAR shall contain SDS for all chemicals and materials determined by the Government to present a toxicity hazard that are incorporated in the design that has successfully completed PQT.

The SAR shall document the comprehensive evaluation of the safety risk being assumed prior to a Government test or operation of the chargers. The SAR shall identify all safety features of the chargers, results of safety testing, and specific controls or precautions to be followed in the use, maintenance, storage, transportation, demilitarization and disposal of the charger. The SAR shall provide verification of compliance with safety requirements identified in the contract.

APPENDIX A – AGREEMENT DELIVERY REQUIREMENTS LIST (ADRL)

Table of Contents Sanity Check (To Be Removed):