W909MY22R0009 Amendment 0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offers 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 amendments: (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 ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: 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 data, 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.)

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)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

W909MY

ARMY CONTRACTING CMD-APG

10205 BURBECK RD

FORT BELVOIR, VA 22060-5811

JESSICA L. HAWKINS

EMAIL: JESSICA.L.HAWKINS27.CIV@ARMY.MIL

W909MY-22-R-0009

2022JUN10

X

X

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 17

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: JESSICA L. HAWKINS

Buyer Office Symbol/Telephone Number: CCAP-CCV/(703)704-0829

Type of Contract 1: Firm Fixed Price

Kind of Contract: Research and Development Contracts

*** End of Narrative A0000 ***

2 17

W909MY-22-R-0009

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION J - LIST OF ATTACHMENTS

List of Number List of Number

Addenda Title Date of Pages Transmitted By Addenda Title Date of Pages Transmitted By________________ ____________________________________________________________ _______________ ____________ _______________________________ ____________________________________________________________ _______________ ____________ _______________

Exhibit A CONTRACT DATA REQUIREMENTS LIST 11-JUL-2022 010 EMAIL

Attachment 0005 3K STEP EMD PD UPDATED 11-JUL-2022 149 EMAIL

Attachment 0007 DRAFT TACTICAL MICROGRID STANDARD 06-MAY-2022 438 EMAIL

Attachment 0008 GOVERNMENT ANSWERS TO OFFEROR QUESTIONS 12-JUL-2022 001 EMAIL

3 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 General Instructions

L.1.1 Manner of Submission. Each Offeror shall submit one (1) proposal, via email, to the Contracting Officer, Darbye T. Rivera, via email at darbye.t.rivera.civ@army.mil and Contract Specialist, Jessica L. Hawkins, via email at jessica.l.hawkins27.civ@army.mil prior to the due date for proposals. The size per email shall not exceed 9MB. When submitting proposals, the subject line shall include the term "Proposal. If submitting multiple emails, the subject line shall also include "Email 1 of 2," "Email 2 of 2," as appropriate to the number of emails submitted. Offerors shall not submit compressed, self-executing (.exe), or .zip files. If the Offeror does not receive confirmation of receipt, it is the responsibility of the Offeror to contact the Contracting Officer and Contract Specialist to confirm the proposal has been received by the Government. Offeror's shall not submit password protected documents. Any proposal where the

Government is unable to access the files due to corruption, virus, or any other malfunction may not be considered for award, giving appropriate consideration to the fact-specific circumstances.

L.1.2 Early Submission Encouraged. Transmission of emails from non-Government to Government email systems is not instantaneous or infallible. Offerors should not wait until the last minute to submit proposals. To avoid submission of late proposals, the Government highly recommends Offerors transmit their proposal files 24 hours prior to the required proposal due date and time. FAR 52.215-1 will govern situations involving late proposals.

L.1.3 Questions. Offerors shall pose any questions regarding the solicitation in writing via e-mail to the Contracting Officer

(darbye.t.rivera.civ@army.mil) and Contract Specialist (jessica.l.hawkins27.civ@army.mil), at least 10 days before the solicitation closing date (questions received after that may or may not be answered). The Government will answer questions electronically so that all

Offerors will see both the question and the answer. The Government will attempt to sanitize questions as necessary to protect the identity of the Offeror(s) submitting the question(s), but it is ultimately an Offerors responsibility to ensure that their questions do not contain proprietary or trade-secret type information. Offerors shall not contact any Government personnel other than the Contracting

Officer and Specialist regarding the Solicitation. Contacting any other Government personnel other than the Contracting Officer and

Contract Specialist identified may result in an organizational conflict of interest (OCI) and may result in an Offeror being excluded from competition and award.

L.1.4 Organizational Conflicts of Interest. The Offeror shall disclose (in its Administrative Proposal volume) any potential OCI situations with itself, subcontractors, partners or any other Offeror as it applies to this solicitation. Disclosure shall be made to the Contracting Officer and Contract Specialist as soon as the potential OCI is identified, including if identified prior to proposal submission, or the Offeror shall submit an affirmation statement in its proposal that they are not aware of any OCIs. The disclosure shall include the facts and an analysis of the actual or perceived conflict and shall recommend an approach to neutralize, mitigate, or avoid the potential conflict. The Contracting Officer will determine if resolution is necessary and will promptly respond to resolve any potential conflicts, which may include notifying an Offeror of their exclusion from the competition. The Government may communicate with any Offeror during the pendency of the source selection regarding OCIs and protecting the integrity of the procurement process and those communications shall not constitute discussions.

L.1.5 Cost of Proposal Preparation. Costs associated with the preparation and submission of a proposal in response to this solicitation are the solely the responsibility of the Offeror.

L.1.6. Proposal Validity. Each Offerors entire proposal shall remain valid for a minimum of 180 days from the due date for proposals.

If an Offeror states in their proposal that the proposal is valid for any period less than 180 days, the proposal will not be evaluated or considered for award.

L.1.7 Prohibition on Classified Information. Proposal files shall not contain classified data.

L.1.8. Incorporation of Proposals. The Government reserves the right to incorporate any portion(s) of the winning proposal(s) into the resultant contract(s).

L.1.9 Clarity and Compliance. Offerors should not make assumptions in preparing their proposals. All concerns shall be addressed by submitting questions by the date specified in this solicitation. Offerors are also cautioned that parroting of the Technical requirements 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.

L.1.10. Required Proposal Formatting.

L.1.10.1. Each Offeror shall submit its proposal in five separate volumes as specified in Table 1, below. Offerors shall generally use the file naming convention in the table to the extent possible. Offerors shall replace XXXX with their company name and MMDDYY with the date the proposal is submitted. For example, Acme Corp_Technical Proposal_02152022.docx.

Table 1 Page Counts and File Names

Volume Title File Name Maximum Pages

4 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

I Technical XXXX_Tech Vol_ MMDDYYYY.docx (or pdf) 40*

II Price XXXX_Price Narrative_MMDDYYYY.docx

XXXX_Price Model_MMDDYYYY.xls No limit

III Past Performance XXXX_PastPerf_ MMDDYYYY.docx (or pdf) No limit

IV Small Business XXXX_Small Bus_ MMDDYYYY.docx (or pdf) No limit

V Admin Volume XXXX_Admin Volume_MMDDYYYY.docx (or pdf) No limit

(Solicitation, Offer and Award Documents and Reps & Certs, etc)

L.1.10.2. Regarding page counts, every page within a volume shall be numbered, starting at the first page, such that the page numbers correspond to the actual number of the page in the PDF or Word file. The page limits are inclusive of all pages, including, for example, title page, table of contents, list of illustrations, acronym list or cross reference index, glossary and any summary section. If the

Offeror includes its own annexes or attachments, those annexes or attachments must be clearly identified and will count toward page limits. *The appendix required by Section L.2.2.6 (Supporting Data) does not count against the 40-page limit for the Technical proposal volume. Any pages that exceed the page limit for the Technical volume will not be evaluated.

L.1.10.3. The submission shall be clearly indexed and logically assembled. All pages (not including the Excel Price Model) shall use the following parameters:

Margins Top, Bottom, Left, Right 1

Gutter 0

From Edge Header, Footer 0.5

Page Size, Width 8.5

Page Size, Height 11

Normal text shall be 12-point Arial or New Times Roman Font (tables and graphic may be reduced to 10-point).

Page numbers, headers/footers, and proprietary markings may be within the page margins.

L.1.10.4. All Offeror-provided information the Offeror desires the Government to consider for each factor shall be confined to the appropriate proposal volume.

L.1.10.5 Price information shall not be included in the Technical Volume. Proposals that fail to separate Price information from the

Technical Volume may be either not considered for award, or redacted prior to being provided to the technical evaluators in a manner that may end up being detrimental to technical evaluators understanding of the Offerors proposal.

L.1.11 Availability of Funds. The award of this contract is subject to the availability of adequate funds. The Government reserves the right to cancel this program/requirement at any time, based on changes in funding, mission requirements, or any other pertinent reasons.

L.2. Volume I: Factor 1 Technical Factor

L.2.1. The Technical Factor proposal volume shall contain information explaining and supporting the Offerors ability to meet the requirements of the SOW and Purchase Description. This volume may contain any introductory material the Offeror desires, but then shall be organized by Subfactor.

L.2.2. Subfactor 1: System Design

L.2.2.1 Design Description. The Offeror shall thoroughly describe the STEP 3kW system to be developed and the technical approach proposed to meet the requirements of the Statement of Work and Purchase Description. The Offerors system description shall include a discussion of the systems size, weight, power output, reliability, and interface controls (including communications). The system description shall also include a discussion of the engine, generator, and power converter (if used) to be used in the design. If these components have not yet been selected, the Offeror shall detail how and when in the design process that selection will be made. The

Offerors narrative shall delineate aspects of the system that have already been developed/achieved versus those that the Offeror proposes to develop during the EMD contract.

L.2.2.2 Requirements Compliance. The Offerors technical proposal shall include a requirements compliance chart that addresses each of the following listed Threshold and Objective criteria from the Purchase Description:

PD Para # Description_____________________________

3.2.1 Set Rating

3.3 Reliability

5 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

3.11.5 Fuel Consumption

3.13 Storage

3.18.3 Weight

3.30 Governing System (and sub-paragraphs)

3.31.12 Voltage Performance (and sub-paragraphs)

3.8 Starting, operating, and stopping (and sub-paragraphs)

3.31.8-3.31.11 Voltage characteristics

3.23 Non-linear load

This chart shall explain whether or not the Offerors STEP 3kW system currently meets each Threshold requirement and Objective goal for each of the above listed PD paragraphs. The Offeror may, and is encouraged to, also include any other Objective criteria from the

Purchase Description that the system meets. Ability to meet additional Objective requirements will generally be evaluated more favorably, as discussed in Section M. For requirements/goals that are met, the Offeror shall explain what evidence supports meeting the requirement; for requirements that are not yet met, the Offeror should explain how it plans on meeting the requirement during the contracts base period for development. Evidence of requirements/objectives compliance may include (but is not limited) to system-level test data (the most credible evidence), followed by component-level test data (the next most credible evidence), technical papers/analysis, modeling and simulation data, and finally supplier documentation. Test data and test reports may be provided as an appendix to the Technical Proposal Volume which does not count against page limits.

L.2.2.3 Maturity Level. The Offer shall assess and describe the current level of maturity (at the time of proposal submission) of the

Offerors proposed solution. The Offeror shall assess a specific Technology Readiness Level (TRL) of its proposed system, with supporting rational. Where photos and other evidence are available to support the Offerors assessment, they should be provided. (For example, an

Offeror that asserts its proposed system is currently at TRL 6 should be able to provide evidence of a representative model or prototype system tested in a high-fidelity laboratory environment or in simulated operational environment.) A list of the applicable TRL levels is included as an attachment to the solicitation.

L.2.2.4 Long-term Sustainability and Affordability. The Offeror shall discuss how its proposed system is reliable, producible and maintainable. The Offeror shall discuss its design and developmental approach to minimizing the amount of complexity of user maintenance and minimizing the unit cost during production. Notwithstanding the general prohibition on discussing proposed costs in the Technical proposal volume, Offerors may discuss production costs and issues related to production costs in this section of the Technical Proposal.

L.2.2.5 Known Challenges. The Offeror shall discuss existing performance limitations of its proposed system and its development approach for overcoming these shortcomings. As there is no known design that currently meets all Government requirements, the Government anticipates that all Offerors will have a discussion of performance limitations; the Government is primarily interested in how the

Offeror plans on overcoming known limitations of their system.

L.2.2.6 Supporting Data. The Offeror shall provide a summary of available independent and Offeror test reports to provide supporting evidence of the proposed technologys feasibility and maturity. The test reports discussed shall be included, in full, as an appendix to the Technical Proposal Volume; this appendix does not count against page limits.

L.2.3. Subfactor 2: Management Approach

L.2.3.1. Organization. The Offeror shall describe its organizational structure, roles, and responsibilities for supporting the STEP 3kW

EMD phase contract.

L.2.3.2 Experience. The Offeror shall describe its experience and expertise with managing complex electro/mechanical development efforts. The Offeror shall especially include any experience designing military generator sets for the Department of Defense. The

Offeror shall also describe any experience creating and delivering to a DoD program office in the analysis and information products required by CDRLS C001, C002, C004, C005, and C006.

L.2.3.3. Quality Control. The Offeror shall describe its proposed Quality Control plan, processes, and any relevant certifications it holds (for example, ISO certifications).

L.2.3.4 IMS. The Offeror shall provide an Integrated Master Schedule (IMS) which includes the Offerors proposed plan to meet the SOW and

Purchase Description requirements. The IMS shall include all contract tasks, reviews, and deliverables, as well as procurement of long lead items. The IMS shall also clearly state and depict how long (in months) the Offeror proposes for each of the following four phases:

Phase 1/CLIN 0001: Preliminary Design Review (PDR); Phase 2/CLIN 1001: Critical Design Review (CDR); Phase 3/CLIN 2001: Prototype Build and Delivery; and Phase 4/CLIN 3001: Test Support. Phase 4 shall be 12 months for all Offerors, and Phases 1, 2, and 3, when combined, shall not exceed 21 months. Offerors are permitted and encouraged to propose a shorter/faster timeline for Phases 1, 2, and 3 (i.e., a total duration of the three phases that is less than 21 months). Shorter/faster execution of Phases 1, 2 and 3 will generally be evaluated more favorably, as discussed in Section M.

L.2.3.5 Risk. The Offeror shall provide a risk discussion that identifies potential program risks and plans to develop risk mitigation strategies. This discussion should include supply-chain risks such as materiel and component shortages.

6 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.2.3.6 Testing. This Offeror shall describe any testing it would perform above and beyond contractually required testing to ensure successful system performance. The Offeror shall identify the testing equipment it believes it would need to possess to perform the development effort; explain how the Offeror would utilize that equipment; and for the identified testing equipment, shall explain whether it already owns, leases, or otherwise has access to that equipment, and if not, what the Offerors plan is to obtain that test equipment for the performance of the contract.

L.2.3.7 Future Manufacturing Capacity. The Offeror shall discuss, at a top level, its manufacturing capability and plan to produce production quantities at a sustained rate of up to 150 units per month, if the Offeror is ultimately selected for a future production contract.

L.2.3.8 Data Rights. The Offeror shall discuss the extent to which the rights in technical data (TD), computer software (CS) and computer software documentation (CSD) offered to the Government ensure unimpeded and cost-effective production, operation, maintenance, and upgrade of the STEP 3kW system throughout its life-cycle, and will allow for open and competitive procurement of spare and repair parts. (The Government generally views more favorable approaches to Data Rights that will allow for future competitive procurement). The

Government does not desire to be locked into a sole source vendor for spare, repair, and consumable parts. At a minimum, Offerors shall include a list of consumable items and provide the level of data rights license the Government will receive for technical data associated with that item (e.g. Unlimited, Government Purpose, or Limited rights license). Offerors are encouraged to do the same for common spare/repair parts.

L.2.3.9 Data Assertion List. The Offeror shall attach to the Technical Proposal Volume a list identifying all commercial and noncommercial TD, CS, and CSD that it asserts should be delivered with other than Unlimited Rights licenses. Guidance concerning the formatting of this list are set forth in the DFARS 252.227-7017 Identification and Assertion of Use, Release, or Disclosure

Restrictions. In addition to the instructions at DFARS 252.227-7017, this list shall: (1) contain every CDRL and the level of data rights the Government will receive in that CDRL, and (2) expressly state Unlimited Rights for any CDRL being provided with that level of rights (even though DFARS 252.227-7017 does not normally require an express statement for deliverables with Unlimited Rights licenses).

L.3. Volume II: Factor 2 Price

L.3.1. As a threshold matter, the Government has an affordability goal of $7.5M per contract. Price proposals that exceed $7.5M may be determined to be unaffordable and eliminated from consideration for award, notwithstanding any technical advantages contained in the

Offerors proposal volume for the Technical Factor.

L.3.2. Certified cost and pricing data are not required at the time of proposal submission. However, the Government reserves the right to request certified cost and pricing data, or other than certified cost and pricing data, or any other data supporting proposed prices prior to award.

L.3.3. The Price proposal volume has two components, a Price narrative (Word Document) and Price Model (Excel Chart). Offerors shall submit a Price narrative with sufficient explanation and documentation necessary to adequately support and explain the costs proposed.

This should include a detailed discussion of how prices, estimated labor hours, labor rates, overhead, etc., were determined and list of major equipment and materiel requirements. There is no page limitation for the Price volume. The Price volume should contain all information the Offeror believes necessary for the Government to determine its proposed price to be fair and reasonable. The narrative should include a breakdown of cost elements and profit, detailing how the contract funding will generally be spent. Direct and indirect rates should be justified based on past commercial or Government rates, or by providing examples of equivalent rates for equivalent talent. If rates are based on DCMA or DCAA negotiated rates, the rate agreements shall be provided. For materials, hardware, and software costs, list all major materials, supplies, equipment, and software, and provide vendor quotes where applicable. For travel costs, list the number of trips, number of days per trip, departure and arrival destinations, number of people, etc., and break the travel out by categories such as lodging (hotel), airfare, per diem (daily allowance for meals), and any other miscellaneous costs.

Importantly, the Offerors price narrative should specifically include costs associated with Phase 4 developmental testing (such as travel, spares, consumables, etc.) necessary to provide the Government confidence that the Offeror has planned accordingly to meet SOW requirements during Phase 4.

L.3.4. The Offerors Price Model shall use the format provided with the solicitation, which lists the Offerors Total Proposed Price, as well as the Offerors price, broken out by CLIN/Phase for the following four phases: Phase 1: Preliminary Design Review (PDR); Phase 2:

Critical Design Review (CDR); Phase 3: Prototype Build and Delivery; and Phase 4: Test Support. As discussed for the Section L Technical

Factor instructions, Phases 1, 2, and 3, when combined sequentially, must have a total duration of twenty-one (21) months or less; Phase

4 shall be twelve (12) months.

L.3.5. For proposal purposes, all contract performance other than testing shall be at the Offerors facilities; prototype delivery and testing support shall be at the Aberdeen Test Center. For the purpose of developing a Price proposal, Offerors should assume an award date of 1 December 2022; the dates of the Phase 4 testing are dependent on how long the Offeror proposed for Phases 1, 2, and 3.

L.4. Volume III: Factor 3 Past Performance

7 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.4.1 Overview. This volume shall contain past performance information regarding similar contracts (past performance references.)

Offerors shall submit no more than three Government and/or commercial contracts past performance references, which may be from the prime

Offeror or any major subcontractor. Each past performance reference must be both Recent and Relevant to be considered. The Past

Performance Volume consists of two parts; the below described information submitted by the Offeror itself, and Past Performance

Questionnaires which the Offeror facilitates, but are provided directly to the Government by outside entities. Offerors are reminded that while the Government may elect to consider past performance information obtained from other sources, the burden of providing thorough and complete past performance information rests with the Offeror.

L.4.2. Recency. A recent effort is defined as one that has been awarded and/or had performance occurring during the past five years from the original issue date of this RFP. (This date will not adjust or shift-right as a result of any subsequent RFP amendments).

L.4.3. Relevancy. Each past performance reference can have one of four levels of relevance: Not Relevant, Somewhat Relevant, Relevant, and Very Relevant. A Somewhat Relevant effort is defined as a previous contract effort valued at more than $900k and involving development of electro/mechanical hardware. A Relevant effort is defined as a previous contract effort valued at more than $1 million and involving the development of generator design. A Very Relevant characterization is reserved for previous development effort valued at more than $1 million, involving the development of a military-specific generator set. All other contracts not meeting any of these definitions are considered "Not Relevant."

L.4.4. Format.

L.4.4.1. This volume shall provide data concerning the prime Offeror first, followed by data for any proposed major subcontractor. Each past performance reference shall clarify whether it is for the prime Offeror or a proposed major subcontractor. Major subcontractors are those who will are anticipated to be performing more than 15% of the Total Proposed STEP 3kW EMD contract price.

L.4.4.2. The Offeror shall provide the following information for each past performance reference:

a. Contractor/Subcontractor place of performance, Contractor and Government Entity (CAGE) Code and Data Universal Numbering System

(DUNS) Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone and fax numbers).

b. Government contracting activity, Contracting Officer name, telephone number, and email address.

c. Government Contracting Officer Representative (COR) and/or technical representative, telephone number, and email address.

d. Government contract administration activity, Administrative Contracting Officer (ACO) name, telephone number, and email address.

e. If Offeror performed as a subcontractor, prime contractor company name, point of contact name, telephone number, and email address.

f. Contract type, and in the case of indefinite-delivery contracts, primary type and secondary type (for example, indefinite-delivery indefinite-quantity, cost-plus-fixed-fee).

g. Awarded price/cost.(If the reference is for past performance previously performed as a subcontractor, also explain the value of the work actually performed as a subcontractor, as opposed to the overall contract value of the prime contract).

h. Final or projected final price/cost.

i. Awarded period of performance.

j. Final (actual) or projected final (if ongoing) start and end dates of the period of performance.

k. Percentage of effort, based on the total cost of the work performed, performed as a prime contractor or subcontractor at the time of proposal submission.

l. Description of the specific tasks or activities performed by the Offeror itself under the contract.

m. Most importantly, a narrative describing past performance reference, the objectives achieved, and how the past performance reference relates to the requirements of this STEP 3kW EMD solicitation.

n. If the original cost, schedule, or technical requirements of the contract were not met, the offeror shall provide a brief explanation of the reason(s) the original requirements were not met and any corrective actions taken by the contractor.

o. The Offeror shall provide copies of any Show Cause Notices, Cure Notices, or Letters of Concern received for each past performance reference, or shall affirmatively state that no such notices/letters were received for the past performance reference.

8 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.4.4.3. Corporate entities, intra-divisional companies, joint ventures, and partnerships. If any past performance example was performed by a corporate entity, intra-divisional company, or partner other than the corporate entity or intra-divisional company that will perform the work described in this solicitation, identify them, describe the relationship, and indicate which entity or company will perform this effort.

L.4.4.4.Predecessor companies. If the proposed past performance was performed by a predecessor company, provide the information for the recent and relevant contract of the predecessor company and document the history of the evolution from the predecessor company. Any corporate experience of a company that in the future might, but has not yet, become part of the Offeror's company, including but not limited to any pending novation agreements, mergers and acquisitions, will likely not be considered. Any corporate experience of a predecessor company or division divested away from the Offeror also likely will not be considered.

L.4.4.5.New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to the other requirements in this section, the Offeror shall discuss in detail the role performed by such persons in the prior contracts cited.

Information should be included in the files described in the sections above. Letters of Commitment shall be included in the proposal for these employees in order to be considered.

L.4.5 Past Performance Questionnaires. The Offeror shall complete Part I of the Past Performance Questionnaire and email the questionnaire to the Government contracting activity or technical representative responsible for the past performance reference contract. The POCs shall be requested to electronically complete Part II of the questionnaire and email the entire questionnaire to the

Contracting Officer and Contract Specialist for this solicitation, no later than the proposal due date. The Offeror shall include in its

Past Performance Volume the POCs who were sent a questionnaire and the date the questionnaire(s) were sent. The Government may or may not reach out to these POCs regarding questionnaires that are not received by the proposal due date.

L.4.6 Utilization of Small Business. All Offerors shall submit information substantiating the Offerors past performance in complying with FAR 52.219-8, Utilization of Small Business. Offerors shall also provide a statement indicating whether any negative information has been reported in the past three years concerning the Offerors past compliance with FAR 52.219-8. If any such negative information has been reported, the Offeror may submit explanations or comments responding to such negative information. Offerors with no prior contracts containing FAR 52.219-8 shall expressly state this.

L.5 Volume IV: Factor 4 Small Business

L.5.1. For the Small Business proposal volume, each Offeror (large and small) shall submit a Small Business Participation Plan. Large business must also submit a Small Business Subcontracting Plan.

L.5.2. The small business participation goal for each awarded contract is contained in Section M.5.2 and shall be calculated as a percentage of total proposed price.

L.5.3. All Offerors, whether small or large businesses, shall submit a Small Business Participation Plan which outlines the level of participation of small businesses (as a small business prime and/or small business subcontractors) in the performance of the contract, and which shall include the following:

(1)Type of Business of Prime Contractor:

Check all applicable boxes:

{ } Large

{ } Historically Black Colleges and Universities/Minority Serving Institution (HBCU/MIs)

{ } Socio-economic Concerns (check below)

{ } Small Disadvantaged Business Concerns (SDB)

{ } Women-Owned Small Business (WOSB)

{ } Historically Underutilized Business Zone (HUBZone) concerns (SBA certified)

{ } Veteran Owned Small Business (VOSB)

{ } Service Disabled Veteran Owned Small Business (SDVOSB)

(2) Submit the total combined percentage of work to be performed by both large and small businesses (include the percentage of work to be performed both by Prime and Subcontractors):

Total Contract Value (TCV): (Including Options, etc.) $__________

Dollar Value of your participation as a Prime Contractor: $_________

Total Percentage Planned for Large Business(es) __________%

Total Percentage Planned for Small Business(es) __________%

* Note When combined, Large and Small Business totals must equal 100%.

(3) Indicate the total percentage of participation to be performed by each type of subcategory small business. An Offeror who qualifies as a small business should include its prime Contractor dollars in calculating its proposed percentage goals in all of the small business categories that it qualifies for. The percentage of work performed by small businesses that qualify in multiple small business categories may be counted in each category.

9 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Example: Victory Prog Mgt (WOSB and SDVOSB) performing 2%; and Williams Group (SDB, HUB Zone, and WOSB) performing 3%. Results equate to: SDB 3%, HUB Zone 3%, WOSB 5%, SDVOSB 2%, VOSB 2%). SDVOSBs are also VOSBs automatically; however VOSBs are not automatically

SDVOSBs.

Percentage of TCV

Small Disadvantaged Business ____________%

HUB Zone Small Business ____________%

Woman Owned Small Business ____________%

Veteran Owned Small Business ____________%

Service Disabled Veteran Owned SB ____________%

Offerors who propose small business participation percentages that cannot meet the Governments Small Business goals for this procurement shall explain in detail why such goals cannot be met.

NOTE: The sum of all the percentages need not equal 100% as individual subcontractors may be counted towards more than one category.

All percentages shall use Total Evaluated Price as a baseline.

(4) Provide a listing of all proposed Sub-Contractors, their Commercial and Government Entity (CAGE) code, and respective type of business concern in the format below. Any Subcontractor identified as an 8(a) or HUBZone MUST have an active SBA certification of its status at the time of proposal:

Company

CAGE

Large Business

Small Business

Small Disadvantaged Business

Woman Owned Small Business

HUBZone Small Business*

Veteran Owned Small Business

Service Disabled Veteran Owned Small Business

*MUST BE SBA CERTIFIED

(5) Describe the extent of commitment to use small businesses as defined by FAR Part 19, as subcontractors. Offerors that have enforceable agreements must provide fully executed copies (i.e. the entire agreement and not just the first and last pages). An enforceable commitment is defined as A written and signed agreement (by both parties) that details that all parties have agreed to a business relationship for this procurement." This document must be clear that both parties have defined and agreed to the extent of the relationship to include the type or types of work the subcontractors/partners shall perform and what areas of the PWS they will cover.

The agreement shall be specific in nature.

Offerors shall also list all small business subcontractors with which they have teaming agreements for this solicitation and shall list the types of commitments if any are in place for this specific acquisition (small business prime, written contract, verbal, enforceable, non-enforceable, joint venturing, mentor-prote'ge', etc.).

COMPANY

TYPE BUSINESS(Small Business, Small Disadvantaged Business, Woman Owned Small Business, HUBZone Small Business, Veteran Owned Small

Business, Service Disabled Veteran Owned Small Business)

TYPE OF RELATIONSHIP (i.e., unilateral agreement, bilateral agreement, long term relationship, mentor prot\'e9g\'e9)

(6) A list of supply/service each small business will provide for this procurement. Be as specific as possible (i.e. references to the Performance Work Statement) to demonstrate the variety and complexity of work:

COMPANY

TYPE OF BUSINESS (Small Business, Small Disadvantaged Business, Woman Owned Small Business, HUBZone Small Business, Veteran Owned Small

Business, Service Disabled Veteran Owned Small Business)

10 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

TYPE OF SUPPLY OR SERVICE

REFERENCE (Paragraph/section in PWS if applicable)

(7) The realism of the proposal. Provide narrative information on how goals for this effort were developed and the proposed plan execution to ensure goals will be met or exceeded (i.e. goals developed based on Technical Methodology/Approach).

(8) Detailed explanations/documentation supporting the proposed participation percentages, or lack thereof. Also, list the details of what conferences or trade shows will be attended and their relevance to this requirement.

(9) Small Business (SB) participation to include all small businesses' socio economic categories, shall be expressed in dollars and percentages of TOTAL CONTRACT VALUE.

Fill in the chart below to include dollars and percentages by NAICS code (expand if necessary):

COMPANY

TYPE OF BUSINESS(lists all SB and SB socio economic categories as applicable)

NAICS

% OF TOTAL CONTRACT

VALUE

$$ OF TOTAL CONTRACT VALUE

(10) In order to comply with the requirements for the Small Business Participation Plan, please be sure to include the following:

(a) Base the percentages on total proposed cost;

(b) Provide specific percentages and allocation in dollars for all small businesses and socio-economic categories in this acquisition;

(c) Include detail and documentation supporting the small business goals you have proposed. If applicable, be sure you explain why target goals cannot be met or exceeded as stated in Section M Basis for Award;

(d) Include details regarding your historical performance with small businesses; and

(e) Include specifics and details of how you will execute the plan in order to meet requirements.

Offerors shall complete and submit a list of proposed subcontractors, titled List of Proposed Subcontractors (Large and Small

Businesses). This list will be established as the approved subcontracting list at award.

L.5.4. Large Businesses Only. Each Large Business Offeror shall also provide a separate Small Business Subcontracting Plan meeting the requirement of FAR 52.219-9, Small Business Subcontracting Plan (DEVIATION 2016-O0009) and DFARS 252.219-7003. This plan shall be submitted separately from the Small Business Participation Plan required above, which applies to both large and small businesses. The

Small Business Subcontracting Plan is a requirement for award to a large business and will be incorporated into any resultant contract.

Subcontracting plans shall reflect and be consistent with the commitments offered in the Small Business Participation Plan. The Small

Business Subcontracting plan will be evaluated IAW with AFARS Appendix DD.

L.6 Volume V: Administrative Volume

L.6.1 The Administrative Volume shall include a cover letter on company letterhead. The following information, at a minimum, shall be included in the cover letter:

a. The point of contact for the proposal, including the individuals name, company position/title, phone number, and email address.

b. An affirmative statement that the identified point of contact has the authority to enter into an agreement on behalf of the Offerors company.

c. An affirmative statement that the Offeror is not aware of any OCI with itself, subcontractors, partners or any other Offeror as it applies to this solicitation for contract award, or an affirmative statement that any OCI that the Offeror is aware of for any Offeror

11 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

as it applies to this solicitation has been disclosed to the Contracting Officer and the date it was disclosed, including if disclosed with proposal submission.

d. An affirmative statement that the entire proposal will remain valid for a minimum of 180 days from the due date for proposal submission.

e. The Offerors CAGE code, DUNS number, and cognizant DCAA and DCMA offices.

L.6.2. Section K Attachments. Offerors shall provide with its Administrative proposal volume any submissions required in accordance with

Section K of this solicitation.

L.6.3 Signed Offer. Offerors shall attach to its Administrative proposal volume signed copies of all SF 33 and SF 30 forms. Digital signatures or handwritten signatures on a scanned copy are acceptable.

L.6.5 Additional Information. The Administrative proposal volume shall contain sufficient information about the Offerors accounting systems and property management systems to support that the Offeror can meet the criteria in FAR 52.245-1, Government Furnished

Property. The Government may request additional information, from any Offeror individually, about accounting systems and/or property management systems at any time prior to award, including during the source selection; such requests shall not constitute discussions, as these systems are not part of the trade-off decision or basis of award.

*** END OF NARRATIVE L0001 ***

12 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION M - EVALUATION FACTORS FOR AWARD

B. BASIS FOR AWARD (Section M)

M.1.0 Basis for Award. This is a best-value tradeoff source selection conducted in accordance with Federal Acquisition Regulation (FAR)

15.101-1. The Government intends to award up to three (3) EMD contracts, utilizing four evaluation factors: Technical, Past Performance, Small Business, and Price. The best-value tradeoff shall be between only the Technical, Past Performance, and Price factors. The

Technical factor is significantly more important than the Past Performance factor, which is significantly more important than the Price factor. All evaluation Factors other than Price, when combined, are significantly more important than Price. In the event that all

Offerors submit total Prices close to, but within the $7.5M affordability goal, the award decision will depend primarily on the

Technical factor. The Technical factor is comprised of two subfactors: System Design and Management Approach, each of which are of equal importance.

M.1.1 Consideration for Award. Prior to conducting evaluations, the Government may screen proposals for compliance with the Section L instructions and affordability. An Offerors material failure to comply with the Solicitations instructions or unaffordability goal may result in a proposal not being considered for award. After conducting evaluations, in order for an Offeror to receive consideration for award: (1), the Offeror must receive an adjectival rating of no less than Acceptable for the Technical and Small Business factors; (2) the Offerors Price proposal must be fair and reasonable, balanced, and affordable; and (3) the Past Performance factor must receive at least a minimum rating of Satisfactory Confidence. In the case of an Offeror without a record of relevant past performance or for whom information on past performance is not available, a rating of neutral/unknown risk will be assigned (a neutral rating based on lack of past performance history will not, by itself, result in an offer being ineligible for award). However, a Substantial Confidence or

Satisfactory Confidence past performance rating is worth more (e.g. is more advantageous to the Government) during the tradeoff process than a Neutral Confidence past performance rating.

M.1.2 Discussions. The Government does not anticipate conducting discussions. However, the Government reserves the right and discretion to engage in discussions, should the Government determine that it is in its best interest to do so.

M.1.3 Application of Partial Small Business Set Aside

The Government is initially setting aside two of the three contract awards for small businesses (the restricted or SB awards). The remaining award is unrestricted, in that it is not initially set aside for small businesses.

In applying this set aside, the Government will first evaluate all proposals, from both large and small business, at the same time.

However, the Government will conduct its trade-off and award decision for the restricted (small business) awards first. After the

Government determines the awardees for the restricted awards (e.g., the small business proposals determined to represent the Best

Value), any remaining small business proposals (those not selected for a restricted award) will be grouped together with any large business proposals. That remaining group of proposals, which may be from businesses of any size, will be traded-off for award of any unrestricted award(s). If there are not two small business proposals eligible for award, then one or both of the restricted (small business) awards will be opened to large businesses. The Government is under no obligation to conduct discussions for the purpose of allowing a small business to correct deficiencies in its proposal prior to opening up the restricted award to businesses of all sizes.

For example:

If the Government receives three (3) technically acceptable proposals from small businesses and two (2) technically acceptable proposals from large businesses, the Government would (after evaluating proposals): (Step 1) conduct a trade-off and award two restricted awards to the two best small business proposals; (Step 2) conduct a trade-off for the unrestricted award, considering the two

(2) large business proposals and the third-best small business proposal (that was not selected for a restricted award).

If the Government receives one (1) technically acceptable proposal from a small business, one (1) technically unacceptable proposal from a small business, and two (2) technically acceptable proposals from large businesses, the Government would (Step 1) select the technically small business proposal for one restricted award, and then (Step 2) open the second restricted award to large businesses. In this scenario, the Government also has the discretion to conduct discussions with the initially unacceptable small business, which might result in two (2) acceptable small business proposals, and therefore result in only one unrestricted award available for the large businesses.

C. EVALUATION APPROACH

M.2.0 Factor 1: Technical:

The Technical Factor is divided into the following two Subfactors, which are of equal importance:

Subfactor 1: System Design

Subfactor 2: Management Approach

Each Subfactor will be evaluated and assessed findings which shall be characterized as Strengths, Weaknesses, Significant Weaknesses, and Deficiencies, utilizing the following finding definitions:

Deficiency. A material failure of a proposal to meet a Government requirement or a combination of significant weaknesses in a proposal

13 17

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

that increases the risk of unsuccessful contract performance to an unacceptable level.

Strength. An aspect of an Offerors proposal that has merit or exceeds specified performance or capability requirements in a way that will be advantageous to the Government during contract performance.

Weakness. A flaw in the proposal that increases the risk of unsuccessful contract performance.

Significant Weakness. A flaw in the proposal that appreciably increases the risk of unsuccessful contract performance.

(The Government may also prepare uncharacterized findings that are neither favorable nor unfavorable and do not fit any of the above finding definitions).

After evaluating and developing findings for each Subfactor, the Government will assign one overall Adjectival Rating for the Technical

Factor, utilizing the ratings definitions from the below table (Subfactors will not receive their own Adjectival rating):

Technical Factor Combined Technical/Risk Adjectival Ratings

Adjectival Definition and Color…