PBC RPP (29May25).docx

DOCX document 120 KB Posted

Attached to
Platoon Bulk Charger
Solicitation number
W91CRB-25-R-0022
Issued by

About this file

This Request for Prototype Proposal (RPP) is for the development of a Platoon Battery Charger (PBC) issued by Army Contracting Command - Aberdeen Proving Ground. The solicitation seeks innovative solutions to create a bulk battery charger capable of charging multiple battery types used by the Army and DoD, including BB-2590, Conformal Wearable Battery, and radio batteries. The prototype development will consist of up to two competitively awarded Other Transaction Authority (OTA) Agreements, with a firm fixed price and a performance period not exceeding 12 months.

Key requirements include developing a charger that operates in extreme environments, powered by AC and DC sources, and capable of charging various battery types. The contractor must deliver ten fully functional prototype samples that can pass Prototype Qualification Testing, with specific tests covering battery charge times, input voltage, temperature resilience, drop resistance, immersion, and rain exposure. At the end of the prototyping phase, the government intends to select one offeror for a low-rate initial production award, with proposals due by 12:00 PM Eastern Time on 17 July 2025. The evaluation will focus on five factors: System Operational Concept and Capability, Charger Design and Portability, Schedule, Price, and a Bid Sample, with Factors 1 and 2 being of equal importance.

View the file

Other files

File Type Posted
Attachment 6 Question and Answers_Consolidated v5.xlsx XLSX spreadsheet
Attachment 6 Question and Answers_Consolidated v4 2July25.xlsx XLSX spreadsheet
Attachment 5 Price Template_CLIN_Structure2July25.xlsx XLSX spreadsheet
A007 - PBC SAR (27Jun25).pdf PDF
PBC SOW (27Jun25).docx DOCX document
PBC RPP (2July25).docx DOCX document
Attachment 4 Assertions and Other Applicable Clauses.docx DOCX document
A003 PBC TDP.pdf PDF
A002 IMS.pdf PDF
Attachment 2 PBC SOW (29May25).docx DOCX document
Attachment 1 OTA Terms and Conditions.docx DOCX document
A009 PBC QMS PP.pdf PDF
A008 PBC Charger Logging Application.pdf PDF
A007 PBC SAR.pdf PDF
A006 PBC PQT Report.pdf PDF
Attachment 6 Question and Answer Template.xlsx XLSX spreadsheet
Attachment 5 Price Template_CLIN_Structure.xlsx XLSX spreadsheet
Attachment 3 Perf Spec Rev 1 2025-04-02 for (PBC).pdf PDF
A004 PBC FRACAS Reports.pdf PDF
A001 PBC AgendasBriefs Meeting Minutes Reports.pdf PDF
A005 PBC PQT Plan.pdf PDF
Show all 21

On GovTribe

Work with this file

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

Text version

Request for Prototype Proposal (RPP) for Platoon Battery Charger (PBC)

Prototyping Phase

Issued by:

Army Contracting Command – Aberdeen Proving Ground (ACC-APG)

APG, MD 21005

29 May 2025

In support of:

Product Manager Soldier Maneuver Sensors (PdM SMS) Ft. Belvoir, VA 22060

TABLE OF CONTENTS

1INTRODUCTION1
1.1Background1
1.2Prototyping Effort Overview1
1.3Prototype Exit Criteria and Success Determination2
2PROPOSAL SUBMISSION REQUIREMENTS / INSTRUCTIONS2
2.1General Instructions2
2.1.2Solicitation Attachments3
2.2Proposal Deliverable List3
2.3General Appearance3
2.4Compliance with Instructions4
2.5Proposal Preparation Cost4
2.6Security Requirements4
2.7Data Rights4
2.8Non-Traditional Defense Contractor Participation Certification6
3PROPOSAL ELEMENTS6
3.1Factor 1 - System Operational Concept and Capability6
3.2Factor 2 - Charger Design and Charger Portability7
3.3Factor 3 - Schedule7
3.4Factor 4 - Price7
3.5Factor 5 - Bid Sample8
3.5.1Bid Sample Submission8
3.5.2Bid Sample Demonstration8
4EVALUATION APPROACH and BASIS FOR AWARD9
4.1Basis for Award9
4.2Evaluation Approach and Methodology9
4.3EVALUATED FACTORS10
4.3.1Factor 1 - System Operational Concept and Capability10
4.3.2Factor 2 - Charger Design and Charger Portability10
4.3.3Factor 3 - Schedule13
4.3.4Factor 4 - Price13
4.3.5Factor 5 - Bid Sample13

PBC Request for Prototype Proposal

1 INTRODUCTION

The purpose of this Request for Prototype Proposal (RPP) is to provide offerors the opportunity to present innovative solutions that meet all the Platoon Battery Charger (PBC) performance requirements in the most robust and effective manner given the current technology and available materials.

The Offeror shall use the Statement of Work (SOW) and Performance Specification (PS) to detail their proposed approach as to how the program requirements will be met. This approach provides Offerors the flexibility to develop cost-effective solutions and the opportunity to propose innovative alternatives that meet the stated objectives.

Background Product Manager (PdM) Soldier Maneuver Sensors (SMS) intends to conduct a prototyping effort to develop the PBC. The PBC is being developed as a platoon-level bulk battery charger that will charge a variety of Army and DoD batteries, including but not limited to: BB-2590, the Conformal Wearable Battery (CWB, BB-2525), and the AN/PRC-148 and AN/PRC-163 radio batteries. The PBC will operate in a variety of tactical environments – such as extreme cold and hot temperatures, driving rain, high humidity, and extreme solar loading. The PBC will be powered by both alternating current (AC) and direct current (DC) power. The power sources will include commercial grid power, tactical generators, and vehicles.

Prototyping Effort Overview The PBC prototype development will consist of up to two competitively awarded Other Transaction Authority (OTA) Agreements to develop prototypes and test the design in accordance with (IAW) the SOW and PS requirements. The Prototype OTA(s) will be awarded via firm fixed price (FFP) with a period of performance (PoP) not to exceed 12 months.

At the end of the prototyping effort, the contractor will be required to deliver ten (10) fully functional sample prototypes that will be able to successfully pass the Prototype Qualification Test (PQT). While only select tests will be performed in the PQT, it is expected that the charger will be able to meet all the requirements defined in the PS. The PQT is a subset of First Article Test (FAT), the full production qualification test 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:

1. Battery Types and Charge Times (PS §4.5.1.1)

2. Input Voltage, AC (PS §4.5.5.1)

3. Temperature (PS §4.7.1)

4. Transit Drop (PS §4.7.7.2)

5. Immersion (PS §4.7.10)

6. Rain (PS §4.7.12)

The necessary sample quantities are defined by group as follows:

Group
# of samples
Test(s)
1
3
· Transit Drop (PS §4.7.7.2)
2
2
· Temperature (PS §4.7.1)

· Immersion (PS §4.7.10)

· Rain (PS §4.7.12)

3
1
· Battery Types and Charge Times (PS §4.5.1.1)

· Input Voltage, AC (PS §4.5.5.1)

All samples in a group are required to undergo and pass all tests for that group. The total number of samples required for PQT is six (6). From the prototype lot of ten (10) samples, the Contractor shall deliver four (4) samples to the Government for Government Integration Test (GIT) and a User Assessment (UA). The remaining six (6) samples shall be delivered to the Government following completion of PQT.

At the end of the prototyping phase, the Government intends to select one Offeror for a low-rate initial production (LRIP) award via a follow-on Production OTA. However, the Government reserves the right to down select to one Offeror at any time during the prototyping phase if:

· Both Offerors successfully conclude their contractual requirements before the end of the PoP or

· One Offeror has been successful, and the other Offeror has been determined by the government to lack the ability to complete the required efforts within the allotted timeline.

Prototype Exit Criteria and Success Determination

1. A final report, accepted by the Government, showing that all PQT requirements have been met

2. Delivery of 10 fully functional prototypes.

2 PROPOSAL SUBMISSION REQUIREMENTS / INSTRUCTIONS

General Instructions Each Offeror shall submit a single, complete proposal that contains the Offeror’s best terms. Failure to adhere to these instructions may result in rejection of the offer without evaluation or consideration for the award. Offerors are cautioned that “parroting” of the technical requirements or the SOW with a statement of intent to perform does not reflect an understanding of the requirement or capability to perform. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal.

1. The proposal shall be submitted via email to both the Agreements Officer (AO), Gerald Simmons, gerald.a.simmons2.civ@army.mil and the Agreements Specialist (AS), Kiristen Anderson, Kristin.l.anderson24.civ@army.mil no later than (NLT) 12:00 PM Eastern Time on 17 July 2025.

2. If necessary, Offerors may submit multiple emails, or request to use DoD SAFE. The maximum email size with attachments is 30MB. If a complete proposal is not submitted by this closing time, the Offeror’s proposal will not be considered for award. If the Offeror does not receive confirmation of receipt, it is the responsibility of the Offeror to contact the Agreement Officer (AO), and the Agreement Specialist (AS), identified above to confirm their proposal has been received.

3. Offerors shall not submit classified information with the proposal. If the Offeror deems it necessary to include classified information in the proposal, the Offeror will be required to submit a special request to the AO to justify and coordinate this information transmittal.

4. Offerors shall not submit any assumptions, terms, conditions, caveats, or exceptions with proposals. All questions shall be submitted using the Q&A Template (Attachment 6) via email to both the AO and the AS NLT 10:00 AM Eastern Time on 26 June 2025. No assumptions, terms, conditions, caveats or exceptions submitted with proposals will be accepted or incorporated into the award. The Government’s responses will be posted on SAM.gov for all to review.

5. All communications shall be conducted in writing only and directly to the AO and AS.

6. Any Offeror with active exclusion records in System for Award Management (SAM) will not be evaluated and will not be considered for the award.

7. Price information shall not appear in any of the non-price factors.

8. The entire proposal shall remain valid for a minimum of 180 days from receipt by the Government. Proposals offering a shorter period of time validity may not be considered for the award.

9. Offeror shall complete and return Attachment 4 - Assertions and Other Applicable Clauses. This document will be incorporated into any OTA resulting from this solicitation.

2.1.2 Solicitation Attachments

The following documents and attached hereto:

Attachment 1 – OTA Terms and Conditions Attachment 2 – PBC Statement of Work Attachment 3 – PBC Performance Specification Attachment 4 – Assertions and Other Applicable Clauses Attachment 5 – Price Template_CLIN_Structure Attachment 6 – Question and Answer Template

ADRLs A001 – A009 (Nine PDF documents)

Proposal Deliverable List The submission shall be divided into the following sections with the identified page limits (annexes, if requested, not included):

1. Factor 1 - System Operational Concept and Capability (45 pages limit)

2. Factor 2 - Charger Design and Charger Portability (No page limit)

3. Factor 3 - Schedule (including the actual Microsoft (MS) Project file (No page limit)

4. Factor 4 - Price (Attachment 5 and assertion letter) (No page limit)

5. Factor 5 - Bid Sample (Hardware and PowerPoint Brief) (No page limit)

6. A Completed Attachment 4 - Assertions and Other Applicable Clauses

General Appearance Offerors shall adhere to the specific formatting parameters listed below (for all submitted documents which shall be developed via Microsoft Office products). The intent is to facilitate a streamlined Government evaluation by having a uniform, easy to read, easy to display, and uncluttered proposal. Factors 1, 2, and 3 shall have a cover page, table of contents, and an optional acronym list which will not be included in the page count.

Font:Aptos, Arial, or Calibri (All Text)
Minimum Size (Narrative)11pt
Minimum Size (Spreadsheet)10pt
Minimum Size (Figures & Tables)8pt
Font ColorBlack (Body Text & Headings)
Line Spacing (minimum)Single (1.0)
Page Size (Narrative)8.5” x 11”

Page Size (Figures/Tables/Graphic) 8.5” x 11” or (11” x 17” this counts as 2 pages)

Margin (Word)1” Left, fight, top, bottom
Page Number LocationBottom Center e.g. 1 of 20
Page BackgroundBackgrounds/Themes not allowed
Table Heading ShadingYes
Table Cell/Row ShadingYes
Table Line colorAutomatic
Table Line Size1 (minimum)

(File Naming Convention) The Offeror shall name each file as follows:

PBC_Factor1SOCC_CompanyName.

PBC_Factor2CDCP_ CompanyName.

PBC_Factor3Schedule_ CompanyName.

PBC_Factor4Price_ CompanyName.

Compliance with Instructions The Government will consider how well the Offeror complied with these instructions when evaluating the Offeror's capability to perform the prospective contract. The Government will consider an Offeror's noncompliance with these instructions or any attempt to take advantage of loopholes in these instructions to be indicative of the type of conduct that it may expect from the Offeror during contract performance. The Government will evaluate the Offeror's capability accordingly. Offerors are advised to ask the AO for clarification or explanation of any part of these instructions that they do not understand.

The Government reserves the right to make an award without conducting discussions. Accordingly, initial proposals should contain the Offeror’s best terms.

Proposal Preparation Cost The cost of preparing proposals in response to this RPP is not considered a direct charge to any resulting award or any other contract.

Security Requirements The PBC prototyping development effort is permissible in an UNCLASSIFIED facility. The effort will require handling of Controlled Unclassified Information (CUI), and the offeror should be trained and certified accordingly.

Data Rights In accordance with DFARS 252.227-7013/7015, the Government will seek from the Offeror, unlimited rights to form, fit, and function (F3) data; data necessary for operation, maintenance, installation, or training (other than detailed manufacturing data). The Government will also seek from the Offeror, right-to-repair provisions.

This sufficiency of data rights will be re-evaluated at the conclusion of/during the currently planned OT agreement prototype phase/acquisition of PBC in preparations for a follow-on effort.

The Government will negotiate the Intellectual Property (IP) clauses to determine the appropriate level of IP rights required to support any follow-on development or acquisition. The Government envisions obtaining Government Purpose Rights, at a minimum, for all hardware and spare part drawings and specifications delivered to the Government under this Agreement. The Offeror shall complete the table below to identify all hardware and software requiring restrictions (State none if applicable) and include it as the proposal submission:

Data Rights Assertion

Technical Data or Computer Software to be Furnished with Restrictions*
Basis for Assertion**
Asserted Rights Category***
Entity Asserting****

The Offeror asserts for itself, or the entities identified in the table above, that the Government’s rights to use, release, or disclose the following technical data or computer software should be restricted.

*For technical data (other than computer software documentation) pertaining to items, components, or processes developed at private expense, identify both the deliverable technical data and each such item, component, or process. For computer software or computer software documentation, specifically identify the software or documentation.

**Generally, development at private expense, either exclusively or partially, is the only basis for asserting restrictions. For technical data, other than computer software documentation, development refers to development of the item, component, or process to which the data pertain. The Government's rights in computer software documentation generally may not be restricted. For computer software, development refers to the software. Indicate whether development was accomplished exclusively or partially at private expense. If development was not accomplished at private expense, or for computer software documentation, enter the specific basis for asserting restrictions. Note that funding provided by the Government during the development of an item is the basis for Government Purpose Rights.

***Enter asserted rights category (e.g., Government purpose license rights from a prior contract, rights in Small Business Investment Research (SBIR) data generated under another contract, limited, restricted, or Government Purpose Rights under this or a prior contract, or specially negotiated licenses).

****Corporation, individual, or other person, as appropriate.

Non-Traditional Defense Contractor Participation Certification Offeror shall return a signed certification/affirmation of size status for itself and all of its team members/partners for the project on a separate document with the proposal.

Conditions
Yes
No

1. At least one (1) non-traditional defense contractor (NTDC) is participating to a significant extent in this Prototype project.

2. All significant participants in the transaction other than Federal Government are small businesses or NTDCs.

3. At least 1/3 of the total cost of the prototype project is to be paid out of funds provided by parties to the transaction other than the Federal Government.

If you answered “Yes” to Condition 1, then the Offeror’s submission shall provide a description of how the significant participant meets the requirements for a NTDC, how they will be participating to a significant extent, and the percentage and dollar amount of the significant participation and certify:

“[Significant Participant Offeror Name] is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the Department of Defense for the procurement or transaction, any contract or subcontract for the Department of Defense that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section.”

If you answered “Yes” to Condition 2, then Offeror’s submission shall provide a description of how all significant participants are small businesses or how the significant participants meet the requirements for an NTDC and certify:

“[Significant Participant Offeror Name] is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the Department of Defense for the procurement or transaction, any contract or subcontract for the Department of Defense that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section.”

If you answered “Yes” to Condition 3, then Offeror’s submission shall state the amount that is being proposed and the cost sharing cash contribution. If the offer contains multiple team members, this information shall be provided for each individual team member providing cost share.

3 PROPOSAL ELEMENTS

Factor 1 - System Operational Concept and Capability The Offeror shall submit a Technical Proposal that describes in detail their proposed PBC system and how the proposed approach meets the requirements of the PBC PS and the delivery of hardware prototypes which will successfully meet the testing requirements within the 15-month PoP. The Offeror’s Technical Proposal shall address each of the 7 items in a point-by-point fashion as follows:

1. A narrative describing an overview of the System Operational Concept and Capability, so that the overall approach can be well understood.

2. How the Offeror will complete all required testing, to include Government testing, to demonstrate system performance requirements within the OTA PoP.

3. How the Offeror could potentially mitigate schedule and cost risks, and identify the highest risks related to technology and integration and your plans to mitigate those risks.

4. Provide the number of each required battery that will be charged and estimated charge time from 0 – 90% State-of-Charge (SOC) when the charger is fully loaded with one type of battery.

5. Total System Weight: Provide a total system size estimate (PS §3.4.1 Dimensions) and weight estimate (PS §3.4.2 Weight).

6. Operation: Describe the design that allows the charger to meet the temperature operation range (PS §3.7.1.1 Temperature Operation), charging in humid (PS §3.7.2 Humidity), rain (PS §3.7.12 Rain), and icing (PS §3.7.14 Icing).

7. Electrical Conditions: Describe the design to meet PS §3.6 Electrical conditions including PS §3.6.1 EMI.

Factor 2 - Charger Design and Charger Portability The Offeror shall provide the following metrics for the proposed design:

Sub-Factor A: Charger Design

Element
Parameter
Proposed Value
Units
A1
Efficiency
A2
# of batteries charged (CWB)

count

A3
# of batteries charged (2590)

count

A4
Charge time (15 CWBs to 90%)

hours

A5
USB Type-C PD ports

count and type

Sub-Factor B: Charger Portability

Element
Parameter
Proposed Value
Units
B1
Charger weight per CWB (See 4.3.2)

lbs.

B2
Dimensions (volume per CWB See 4.3.2)

in. (LxWxH)

Factor 3 - Schedule The Offeror shall provide a narrative to demonstrate their integrated plan to complete all required tasks and deliverables within the period of performance. The Offeror shall provide an integrated master schedule (IMS) that addresses a Work Breakdown Structure (WBS) to outline the Offeror’s system engineering approach. Areas of importance to the Government are the schedule of major design reviews, dates of system availability, demonstrations, tests, and deliverables.

Factor 4 - Price The objective Price Factor is to assess the proposed price as fair, reasonable and realistic. During negotiations, additional information may be requested from the Offeror in order to accomplish this.

This requirement is Firm Fixed Price. The Offeror shall complete Attachment 5 – Pricing Template / CLIN Structure, in its entirety.

Offerors shall provide a short letter asserting their ability to comply with the following:

Awardee shall maintain adequate records to account for:

1. Federal Funds Received

2. Member Funding (if Cost Sharing Procedures are Implemented)

Awardee shall have an accounting system that:

1. Complies with Generally Accepted Accounting Principles (GAAP)

2. Complies with the Requirements of this Agreement

3. Controls & Documents All Cash Receipts and Disbursements Properly

Factor 5 - Bid Sample The bid sample is intended to provide evidence that the Offeror has the capability and experience in the development, integration, and production of systems similar to the PBC. It is understood that the bid sample may not fully meet the PBC PS, but at a minimum, must demonstrate the Offeror’s capabilities to design and build a charger that meets the requirements of the PS.

3.1.1 Bid Sample Submission

The Offeror shall submit one functional bid sample charger at the time of proposal submission. Offerors shall ship their bid sample hardware to the address below. Shipments should be in hard cases to prevent damage, contain a full inventory sheet (with pictures if needed, not required), and be locked/sealed to ensure nothing is tampered with.

Shipping Address:

U.S. Army C5ISR Center, Power Division POC or ATTN: Tony DeAnni 6631 Cyber St., BLDG 5100 Aberdeen Proving Ground, MD 21005

· The bid sample presentation shall be submitted in MS PowerPoint and Adobe Acrobat *.pdf in the Offeror’s format.

· Included with the bid sample will be any applicable user’s guide and/or technical data sheet describing the characteristics and operation of the bid sample hardware.

3.1.2 Bid Sample Demonstration

After proposal submission, the Government will schedule an opportunity for each Offeror to present their prototype. The presentation will be held at the C5ISR – Power Division at Aberdeen Proving Ground, MD. During the demonstration event, the Offeror shall provide an overview briefing of the bid sample’s capabilities and features. After the presentation, the Offeror shall instruct Government personnel on the operation of the bid sample.

Upon conclusion of the bid sample demonstration, the bid sample hardware will remain with the Government until the end of source selection to enable the Government to further evaluate them, at which time they will be returned to the Offeror if requested.

By providing the bid sample hardware, the Offeror releases the Government from liability for any damage that may occur to the bid sample in the normal course of testing described herein.

4 EVALUATION APPROACH and BASIS FOR AWARD

Basis for Award The five factors to be evaluated are as follows:

Factor 1 - System Operational Concept and Capability Factor 2 - Charger Design and Charger Portability Factor 3 - Schedule Factor 4 - Price Factor 5 - Bid Sample

The Government may award more than one contract on a best value trade-off basis considering Factors 1, 2 and 4.

Basis of Award: Factor 1 and Factor 2 are of equal importance. Factor 4 is nearly as important as Factor 1 or Factor 2 individually, but of less importance when Factors 1 and 2 are combined. Factors 3 and 5 will be evaluated as Acceptable or Unacceptable.

To receive consideration for award, proposals must achieve Acceptable or better evaluations in all non-price factors (Factors 1, 2, 3 and 5), and the Price Factor 4 must be judged to be fair and reasonable. An evaluation rating of Unacceptable for any non-price factor will cause the entire proposal to be evaluated as Unacceptable.

The Government intends to offer an agreement based on the initial proposal submissions without conducting further negotiations. Therefore, each offer should contain the Offeror's best terms from a price and technical standpoint. The Government reserves the right to conduct negotiations at any time during the evaluation process. The standard the Government will uphold in conducting negotiations is to treat all Offerors fairly; this standard does not imply that the Government will conduct negotiations with all Offerors, nor does it imply that all negotiations will be of the same nature or depth.

Evaluation Approach and Methodology

Proposals will be evaluated by a team of Government (evaluators/voting members) and support contractor (advisory role only) personnel. The team will evaluate the proposals to determine whether the technical requirements specified in the RPP have been adequately and completely considered, defined, and satisfied by the Offeror. The evaluators will consider the following criteria when evaluating.

· Understanding of the Problems - The extent to which the proposal demonstrates a clear understanding of all technical features involved in solving the problems and meeting the requirements. Extent to which uncertainties are identified and resolutions proposed.

· Feasibility of Approach - The extent to which the proposed system approach is workable and the end results achievable. The extent to which successful performance is contingent upon proven devices and techniques which do not require excessive development. The proposal will be evaluated to determine whether the Offeror's methods and approach in meeting the requirements in a timely manner provide the Government with a high degree of confidence of successful completion. The extent to which the Offeror is expected to be able to successfully complete the proposed tasks and technical requirements within the required schedule.

· Completeness - The team will evaluate the extent to which the proposal is complete and addresses all aspects of the SOW and technical performance requirements. The team will also evaluate the extent to which Offeror's performance claims are substantiated and the extent to which the Offeror's plan articulates the proposed effort.

· Compliance with Instructions - The team will evaluate the extent to which the Offeror's proposal complies with the instructions contained herein.

EVALUATED FACTORS

4.1.1 Factor 1 - System Operational Concept and Capability

The System Operational Concept and Capability evaluation will be based on the degree to which the Offeror has demonstrated their proposed approach meets the requirements of the PBC PS and the delivery of hardware prototypes which will successfully meet the testing requirements within the 12-month PoP, and sufficiently addressed all seven (7) items from Section 3.1.

Factor 1 - System Operational Concept and Capability will receive adjectival ratings as described below:

· Outstanding - The proposed approach exceeds or satisfies the Government requirements. The approach offers strengths which significantly outweigh weaknesses. The approach is highly feasible, and the Offeror demonstrates a comprehensive understanding of the problems. The proposal provides extensive detail and predictions are thoroughly substantiated.

· Good - The proposed approach satisfies the Government requirements. The approach offers strengths which slightly outweigh weaknesses. The approach is feasible, and the Offeror demonstrates an ample understanding of the problems. The proposal provides ample detail and predictions are well substantiated.

· Acceptable - The proposed approach satisfies the minimum Government requirements. The approach offers strengths and weaknesses which are of equal weight. The approach is feasible, and the Offeror demonstrates a general understanding of the problems. The proposal provides adequate detail and predictions are sufficiently substantiated.

· Unacceptable - The proposed approach is deficient in satisfying the minimum Government requirements. The approach offers strengths which are outweighed by significant weaknesses or a deficiency. The feasibility of the approach is questionable, and the Offeror demonstrates a lack of understanding of the problems. The proposal provides inadequate detail and predictions are not substantiated. None of these conditions can be corrected without a major rewrite or revision of the proposal.

4.1.2 Factor 2 - Charger Design and Charger Portability

Sub-Factor A - Charger Design will receive adjectival ratings based on the Offerors information and the table below.

Element A1: Efficiency [1]

Outstanding
> 90%
Good
85% - 90%
Acceptable
80% - 84%
Unacceptable
< 80%

Element A2: # of Batteries Charged (CWB) [2]

Outstanding
>20
Good
16-20
Acceptable
15
Unacceptable
< 15

Element A3: # of Batteries Charged (2590) [2]

Outstanding
>12
Good
9-12
Acceptable
8
Unacceptable
< 8

Element A4: Charge Time (CWB) [3]

Outstanding
≤ 2 hours
Good
≤ 2.75 hours
Acceptable
≤ 3.5 hours
Unacceptable
> 3.5 hours

Element A5: USB Type-C PD Ports [4]

Outstanding
≥4 ports (240W) or ≥4 ports with PPS capability (240W)
Good
>4 ports (100W) or ≥4 ports with PPS capability (100W)
Acceptable
4 ports, 100W each
Unacceptable
<4 ports or <100W capability
[1]
Efficiency is taken as the combined total output power at the charger bays over the measured AC input power. The use of a custom software monitoring tool is necessary to collect this measurement (see PS §3.10.8). The efficiency should be given for charging the maximum number of CWBs at full rate (between 20% and 60% state-of-charge).
[2]
The maximum number of batteries (CWB or BB-2590) that can be simultaneously loaded on the charger adapters for charging.
[3]
Charge time is the time required to charge 15 CWB 3.6 from 0% to 90% Relative State of Change (RSoC) when the charger is powered from a 120V 60Hz AC power source.
[4]
Type-C PD ports are rated according to their quantity and characteristics. This is on the charger itself, not adapters.

The Government will evaluate the responses and associated supporting rationale as appropriate and according to their ability to meet or exceed the PS requirements for dimensions (PS §3.4.1) and weight (PS §3.4.2). For evaluation purposes, the dimensions (volume) and weight will be normalized by the total number of CWBs the charger can accommodate charging at one time.

For example, a charger with dimensions 30”x18”x12” that charges 15 CWBs and weighs 30 lbs would have a normalized volume of 432 in3 per CWB and 2.0 lbs per CWB. The evaluation will also consider the rationale/methodology for the design (electrical/mechanical components) to achieve the proposed charger dimensions, weight, and battery quantity.

Sub-Factor B - Charger Portability will receive adjectival ratings based on the Offerors information and the table below:

Element B1: Charger Weight [1]

Outstanding
<1.30 lbs. per CWB
Good
1.30 - 1.69 lbs. per CWB
Acceptable
1.70 - 2.33 lbs. per CWB
Unacceptable
>2.33 lbs. per CWB

Element B2: Charger Volume [2]

Outstanding
<80 in3 per CWB
Good
80 - 139 in3 per CWB
Acceptable
140 - 432 in3 per CWB
Unacceptable
>432 in3 per CWB
[1]
Weight is measured with the charger in transport configuration (PS §3.4.7) including any adapters necessary to charge the maximum number of CWBs, and the AC input cable (PS §3.10.3.1).
[2]
Volume is determined by the proposed dimensions, to be measured with the charger in transport configuration (see PS §3.4.7) including any adapters necessary to charge the maximum number of CWBs, and the AC input cable (PS §3.10.3.1).

The Government will evaluate the responses and supporting rationale according to their ability to meet the requirements in PS §3.4.1 and §3.4.2.

If an Offeror is awarded an agreement and the Offeror’s proposed performance capabilities exceed the thresholds in the charger specification for which the Government assesses, the Government reserves the right to incorporate those specific performance capabilities into the agreement.

4.1.3 Factor 3 - Schedule

The schedule will be evaluated on an Acceptable or Unacceptable basis. The Offeror’s proposed schedule will be determined to be Acceptable if at a minimum, GIT & PQT is ready to start within nine months. All others will be deemed Unacceptable.

4.1.4 Factor 4 - Price

Price will be evaluated to determine if the prices proposed are fair, reasonable and realistic. Attachment 5 – Pricing Template shall be completed.

Awardee shall maintain adequate records to account for:

1. Federal Funds Received

2. Member Funding (if Cost Sharing Procedures are Implemented)

Awardee shall have an accounting system that:

1. Complies with Generally Accepted Accounting Principles (GAAP)

2. Complies with the Requirements of this Agreement

3. Controls & Documents All Cash Receipts and Disbursements Properly

4.1.5 Factor 5 - Bid Sample

Bid samples will be evaluated by the US Army C5ISR Power Division Test & Evaluation group. This evaluation will take place in the evaluation laboratories located at 6631 Cyber St, Bldg. 5100, Aberdeen Proving Ground, MD. The following four minimum requirements must all be met to achieve a rating of Acceptable. Any Offeror that does not meet all four will be deemed Unacceptable:

1. Ability to fully charge at least one of the following Army batteries:

· Conformal Wearable Battery (CWB) 3.5/3.6

· Conformal Wearable Battery (CWB) 3.6.2

2. BB-2590

3. At least 1,000W total input power

4. Charge time for a full set of batteries (powered from a 120VAC 20A circuit)

The evaluation is intended to establish the offeror’s ability to build a charger meeting the PS requirements.

The bid sample hardware will initially be evaluated during the Offeror’s bid sample demonstration followed by a limited evaluation will be performed by the Government. Because the bid sample does not comply with the PS on a line-by-line basis, there is no intent to conduct extensive, quantitative performance tests on the bid sample. Rather, the evaluation will be more in keeping with a demonstration of those functions that are included in the bid sample hardware. Where the bid sample does include capability that is closely aligned with the performance/features required in the PS, Government evaluation of that capability will help inform the maturity assessment of those items in the Technical Factor and relevant sub factor. In those areas, the Government may perform more in depth/quantitative testing.

Acronyms

Acronym
Term
AC
Alternating Current
ADRL
Agreement Deliverable Requirements List
ATTN
Attention
C5ISR
Command, Control, Communications, Computers, Cyber, Intelligence, Surveillance, and Reconnaissance
CDR
Critical Design Review
CWB
Conformal Wearable Battery
DC
Direct Current
DFARS
Defense Acquisition Regulation System
FFP
Firm Fixed Price
IMS
Integrated Master Schedule
IAW
In Accordance With
LRIP
Low-Rate Initial Production
MS
Microsoft
NLT
No Later Than
NRE
Non-Recurring Engineering
NTDC
Non-Traditional Defense Contractor
OTA
Other Transaction Authority
PdM
Product Manager
PEO
Program Executive Office
PM
Program Manager
POC
Point of Contact
PPS
Programmable Power Supply
PS
Performance Specification
PQT
Prototype Qualification Test
RPP
Request for Prototype Proposal
RSoC
Relative State-of-Charge
SoW
Statement of Work
SRR
System Requirements Review
TRR
Test Readiness Review
UA
User Assessment
WBS
Work Breakdown Structure

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