GVSC TES - Sec L-M except Cost-Price.pdf

PDF 131 KB Posted

Attached to
GVSC Technical and Engineering Services (continuation of W56HZV_GVSC_TES) Federal contract opportunity
Solicitation number
W56HZV_GVSC_TES2
Issued by
Department of the Army Materiel Command TACOM Life Cycle Management Command

About this file

This document provides details regarding a federal contract opportunity to provide Technical and Engineering Services supporting the Combat Capabilities Development Command Ground Vehicle Systems Center. The opportunity involves the award of a single five-year cost-plus-fixed-fee indefinite delivery, indefinite quantity contract valued at an estimated total contract amount. Interested offerors are invited to submit white papers in response to the notice by February 25th providing feedback on draft RFP sections A through H. The draft RFP sections cover requirements that have been updated based on feedback from prior requests for information, an industry day event, and revised government requirements. Offerors are to submit responses electronically in PDF format to the specified email address including company identifying information. The document provides general instructions regarding proprietary information and states no reimbursement will be provided for response costs.

View the file

Other files for this federal contract opportunity

Other files attached to GVSC Technical and Engineering Services (continuation of W56HZV_GVSC_TES), newest first.
File Type Posted
TES QAs Revised 19MAY2022.pdf PDF
Attachment 0004 DD Form 254.pdf PDF
TES QAs Revised 11MAY2022.pdf PDF
Attachment 0012 Small Business Participation Certification Subcontractor.pdf PDF
Attachment 0010 Government Furnished Property.xlsx XLSX spreadsheet
Attachment 0009 Small Business Participation Instructions.pdf PDF
Attachment 0007 Government Furnished Pricing Model.xlsx XLSX spreadsheet
Attachment 0006 Sample Tasks.pdf PDF
Attachment 0002 Developmental Contractor Format TDP.pdf PDF
Draft W56HZV-22-R-0003.pdf PDF
Attachment 0003 Production Government Format TDP.pdf PDF
Attachment 0001 Personnel Minimum Qualifications.pdf PDF
Attachment 0011 Status Report Format.xlsx XLSX spreadsheet
Attachment 0008 Small Business Participation Workbook.xlsx XLSX spreadsheet
TES QAs Revised 29APR2022.pdf PDF
Attachment 0005 Technical Experience Matrix.xlsx XLSX spreadsheet
TES Strategy Posting.pdf PDF
Attachment 0008 Government Furnished Pricing Model.xlsx XLSX spreadsheet
Copy of Attachment 000X - GFPM 3 Mar 22 wo Total Compensation Tab.xlsx XLSX spreadsheet
Draft Sections L and M Cost-Price Language.pdf PDF
TES Industry Day One-on-one Q and A.pdf PDF
Attachment 0005 - SAMPLE TASKS.pdf PDF
SBP-Workbook.xlsx XLSX spreadsheet
Attachment_00XX_-_Technical_Experience_Matrix.xlsx XLSX spreadsheet
SBP-Certification-Subcontractor.pdf PDF
SBP-WorkbookInstructions.pdf PDF
Technical and Engineering Services Industry Day Participant List.pdf PDF
Links.docx DOCX document
W56HZV-22-R-0003 Draft RFP Sections A-H.docx DOCX document
TES Industry Day Slides_OPSEC_APPROVED_FINAL.pdf PDF
Industry Day Q and A.pdf PDF
Show all 31

On GovTribe

Work with this file on GovTribe

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

Text version

L.1 General Proposal Information

Offerors are cautioned to consult the Contracting Officer IN WRITING before submitting an offer that proposes any deviations or exceptions to any of the requirements, terms, and conditions of the solicitation because it may be cause for rejection of the proposal (See Section M.2)

L.1.1 The proposal, subject to the Submission, Modification, Revision, and Withdrawal paragraph of Instructions to Offeror(s) –Competitive Acquisitions (FAR Provision 52.215-1) contained in Section L of the solicitation, shall be submitted in the format and quantities set forth below.

All information necessary for the review and evaluation of a proposal is to be contained in the proposal volumes set forth below. Section M of the solicitation sets forth the evaluation criteria and delineates the Factors to be evaluated and their relative order of importance. The offeror's proposal, as required by this section, will be evaluated as set forth in Section M of this solicitation. The Government will not assume the offeror possesses any capability, understanding, or commitment not specified in its proposal. It is an offeror's responsibility to submit a well-written proposal, with adequately detailed information, which clearly demonstrates an understanding of and the ability to comply with the solicitation requirements to allow for a meaningful evaluation. The Government does not assume the duty to search for data to cure problems it finds in proposals.

L.1.2 Minimum Acceptance Period.

This provision supersedes any language pertaining to the acceptance period that may appear elsewhere in this solicitation (e.g. SF 33 Box 12).

ACCEPTANCE PERIOD means the number of calendar days available to the Government for awarding a contract from the date specified in this solicitation for receipt of offers.

L.1.2.1 The Government specified minimum acceptance period of 240 calendar days.

L.1.2.2 The offeror shall clearly state in its proposal Administrative volume the acceptance period. Offerors may specify a longer acceptance period than the Government's minimum acceptance period stated above.

L.1.2.3 An offer allowing less than the Government's minimum acceptance period, or fails to provide a proposal acceptance period, may be rejected.

L.2 Proposal Content, Format and Instructions

L.2.1 Proposal Content

L.2.1.1 All proposals shall be in English (American Standard) and shall be in US dollars.

Proposals not in English (American Standard) or in US Dollars may be rejected. The proposal shall include all information specified and shall address all requirements outlined in Section L. The offeror's proposal shall be organized and submitted in separate volumes as set forth below.

Volume Title Vol 1 Technical Experience Factor Vol 2 Sample Task Factor Vol 3 Cost/Price Factor Vol 4 Small Business Participation Vol 5 Administrative

L.2.1.2 A Proposal Executive Summary or transmittal letter is optional. A Proposal Executive Summary will neither be considered as part of the volumes required, nor will it be evaluated.

L.2.2 Proposal Format and Instructions

NOTE: Electronic proposals submitted via E-mail or Fax, and hardcopy proposals will NOT be accepted.

L.2.2.1 The proposal shall be submitted in electronic format on submitted CD-ROMs or DVDs, as outlined in these instructions. Each volume listed above shall be submitted on a separate set of CD-ROMs or DVDs. The offeror shall submit two identical sets of CD-ROMs or DVDs for each volume.

One set of media shall be labeled as the primary copy. In the case of defective file(s) on the primary disc, the second copy will be utilized only to retrieve and review the defective file(s) in question. If the primary disc is entirely defective, the second copy will be used entirely.

All other data on the primary disc will take precedence.

L.2.2.1.1 Each CD-ROM or DVD shall be labeled so it is easily identifiable for evaluation purposes (example: Vol 3, Cost/Price Factor, Set 1 of 2, CD 1 of X), and shall also include the offeror's name and the solicitation number. Each volume shall include a (i) title page, (ii) table of contents, and (iii) list of tables and figures. Each page of the proposal shall be numbered, and each paragraph of the proposal shall have a reference number. A list of all attachments and substantiating data shall be provided in the table of contents. The table of contents shall be organized as set forth below. The table of contents shall include the following information for each Factor, attachment, and for all substantiating data listed:

(a) Cross-reference to related Section L paragraph number

(b) Page number

(c) CD-ROM or DVD Volume and number

(d) File name

L.2.2.1.2 Electronic Files. The proposal electronic files names should not exceed 50 characters in length (not including the file extension). Ensure the file name does not contain any periods.

L.2.2.1.3 Acceptable File Formats. All electronic information provided in response to the solicitation must be provided in Microsoft (MS) Office 2016 compatible or Adobe Portable Document Format (PDF) format or except as noted in instructions for individual volumes. For files in PDF format, scanners should be set to 200 dots per inch. The proposal shall not contain citations for, or active links to live Internet sites or pages. All information shall be contained within the electronic proposal. Any linked or referenced information that is not contained in the proposal will not be accepted.

L.2.2.1.4 Unless otherwise specified, it is recommended that the proposal be formatted for 8.5 inch x 11 inch paper with a minimum font size of 10 pt. and with a minimum of 0.5 inch margins.

Schedules, drawings and other documents more appropriate to larger size should be formatted for no larger than 8.5 inch x 14 inch dimensions.

L.2.2.1.5 Provide spreadsheets that include all formulas, function, macros, computations, or equations used to compute the proposed amounts. For each workbook, all Rows, Columns, Cells, and Worksheets are to be visible. Do not include Zero height and zero width rows and columns in Worksheets. Do not format Worksheet cells with the font color equal to the fill color. If Workbooks or Worksheets are password protected, then the passwords must be provided. Do not submit Print image files or pictures or files containing only values. Failure to provide fully functional excel spreadsheets in the proposal may result in the proposal being rejected (See Section M.2.1 (a)).

L.2.2.1.6 The offeror shall make every effort to ensure that the proposal is virus-free.

Proposals (or portions thereof) submitted which indicate the presence of a virus, or which are otherwise rendered unreadable by damage in electronic transit, shall be treated as "unreadable" as described in FAR 15.207(c).

L.2.2.2 Submission Due Date

The offeror must ensure its proposal, in its entirety, reaches the required destination before the Offeror Due Date and Time established in this solicitation.

L.2.2.2.1 Lateness

The lateness rules for submitted proposals are outlined in FAR 52.215-1 "Instructions to Offerors-Competitive Acquisition” and are incorporated in to this solicitation.

L.2.2.3 Proposal Submission Address

Proposals shall be submitted to the address below. All proposals delivered in response to this solicitation, whether hand-carried or sent via U.S. mail, shall be addressed as follows:

US Army Contracting Command - Detroit Arsenal (DTA) Bldg 231, Mail Stop 303 Attn: GVSC Technical Engineering Services (TES) Proposal 6501 East 11 Mile Road Warren, MI 48397-5000

Solicitation Number: W56HZV-22-R-0003 Proposal Due Date & Time:

TO BE DELIVERED UNOPENED

(offeror's name)

L.2.2.4 Methods of Submission for Unclassified Proposal

Proposals shall either be hand-carried or sent via US mail. Hand-carried submissions* include proposals delivered by commercial carriers such as FedEx, UPS, or services other than the US Postal Service. Proposals must be delivered to the Detroit Arsenal (DTA) Mail Handling Facility (Building 255) between the hours of 8:00AM and 1:00PM local Warren, MI time. The package(s) will be dated and time stamped at the Mail Handling Facility and the Government will be responsible for forwarding the package(s) to the appropriate personnel. Offerors should ensure that any commercial carrier it uses has a tracking system that can provide documentation that will prove the date and time of delivery to the Government. If the proposal is hand-carried by other than a commercial carrier, the delivery person (even if an employee of the offeror) must be a US citizen, and must obtain a signed receipt, indicating date and time of delivery, from the Mail Handling Facility personnel. The delivery person must provide the receipt since the Mail Handling Facility personnel do not have them.

*Directions to DTA: From Van Dyke Avenue, travel west on East Eleven Mile road to railroad track.

Immediately after crossing railroad track turn right into DTA main gate and follow security officer directions to the Mail Handling Facility (Building 255). It may be necessary for the delivery person to obtain a visitors badge prior to being allowed to enter the installation. If so, the security officer will advise the delivery person of the procedures to follow.

L.2.2.4.1 Exterior envelopes must identify the solicitation number and date specified for receipt of proposals.

L.2.2.4.2 Offerors are cautioned that approval to enter the installation must be obtained prior to the closing date and time for receipt of proposals. Due to security procedures, delays are probable at the entry point and offerors must plan to accommodate them. It is the offerors responsibility to plan sufficient time to clear Detroit Arsenal security and ensure proposals reach the intended destination.

L.2.3 Single Proposal Submission

Offerors are limited to submitting one proposal with one approach to meeting the requirements of this solicitation. An offeror is defined as an entity competing independently that does not share a common parent with any other offeror or, does not have a parent/subsidiary relationship with any other offeror, or is not affiliated with any other offeror. For the purposes of Section L.2.3 (Single Proposal Submission), the Government will consider affiliation to exist if associated business concerns or individuals, directly or indirectly, either controls the other or can control the other (control can exist through common ownership, common management, or a contractual relationship such as a joint venture, where members have the power to control performance of the contract); or a third party controls or can control both.

L.2.4 Organizational Conflict of Interest

L.2.4.1 The provisions of FAR 9.5, Organizational Conflict of Interest (OCI), apply to any award under this Request For Proposal (RFP). Potential offerors should review their current and planned participation in any other Government contracts, subcontracts, consulting, or teaming arrangements where they may be in a position of actual or perceived bias or unfair competitive advantage.

L.2.4.2 Offerors should disclose any potential OCI situations to the Contracting Officer as soon as identified including prior to proposal submission. The disclosure should include the facts and an analysis of the actual or perceived conflict and a recommended approach(s) to neutralize or mitigate the potential conflict. The preferred approach to potential conflicts is to negate/obviate the conflict. Mitigation is considered only if it is not practical to negate/obviate the conflict. The Contracting Officer will promptly respond to resolve any potential conflicts.

L.3 All or None

Offers in response to this solicitation must be submitted for all the requirements identified in the solicitation. Offers submitted for less than all the requirements called for by this solicitation may be rejected or ineligible for award. Proposals that contain alternative terms and conditions may be considered as taking exception to the requirements of the solicitation.

See Section M.2.

L.4 Evaluation Factors

Offeror proposals shall address the following Factors:

a. Technical Experience Factor

b. Sample Task Factor

c. Cost/Price Factor

d. Small Business Participation Factor

L.4.1 Technical Experience Factor Volume

The Technical Experience Factor contains three Subfactors:

1) Subfactor 1: Ground Vehicle Robotics (GVR)

2) Subfactor 2: Software Engineering Center (SEC)

3) Subfactor 3: Vehicle Electronics and Architecture (VEA)

Section L.4.1 and its subparagraphs apply to all Subfactors, unless otherwise stated.

General Information: The below instructions are provided to advise offerors as to the information required by the Government to assess the contractor’s proposed experience. Since this information constitutes a basis of the Government's review, it is the offeror's responsibility to submit detailed and complete information as required so the Government may evaluate its Technical Experience volume, and imperative that the offeror present its experience in a clear and complete manner. Failure to provide the applicable information may result in an assessment that the referenced experience is not recent or lacks comparability, and be discounted in the evaluation.

The Government does not assume the duty to search for data to cure problems it finds in proposals. The burden of providing thorough and complete information remains with the offeror.

Definitions used in this Factor and Subfactor(s):

A “Contract” is defined as a written instrument that requires the performance of a distinct effort and demonstrates the distinct effort was actually performed. Written instruments containing supplies or services that can be ordered, such as Indefinite Delivery Contracts (FAR 16.5), Basic Ordering Agreements (BOA), Blanket Purchase Agreements (BPA), and Federal Supply Schedules (FSS) typically DO NOT demonstrate actual performance, and as such, would not meet the definition of a Contract. Written instruments considered to demonstrate actual performance may include a single task or delivery order, a single work directive/technical instruction, or a single definite quantity contract provided it demonstrates a distinct effort was actually performed. An offeror may submit, or the Government may require, written instruments that enhance the Government’s understanding of the distinct effort actually performed if it is not identified on the Contract itself. It is incumbent upon the offeror to demonstrate that a distinct effort was actually performed.

A “submission” is defined as the offeror’s proposed historical contractual instrument that is identified in cell B7 or C7 of a Subfactor tab in the Technical Experience Matrix (Attachment 000X).

L.4.1.1 For the Technical Experience Factor and Subfactors, the offeror shall substantiate recent and comparable experience by providing the requested information below. The offeror is limited to proposing up to two submissions for each Subfactor (L.4.1.3.1, L.4.1.3.2, and L.4.1.3.3), a maximum of six submissions for all Subfactors combined. It is incumbent upon the offeror to ensure that a submission meets the definition of a single Contract (see definition above). The proposed submission(s) must have been performed by the offeror as the prime contractor, unless otherwise allowed by L.4.1.4.1. In this context, the prime contractor is the party that executes an agreement with another party to perform work. Submissions may include foreign, federal, state, local and private industry Contracts. The Government will not consider the experience of individuals, key personnel, or subcontractors; only corporate experience will be considered.

L.4.1.2 The Government will only consider recent experience limited to (up to) two Recent Contract(s) for each Subfactor (L.4.1.3.1, L.4.1.3.2, and L.4.1.3.3) See L.4.1 for definition of a Contract. Recent experience is defined as tasks completed on a Contract determined to be recent. Recent Contract(s) are those performed within three years of the date of issuance of this Request for Proposal (RFP).

L.4.1.3 The Government will evaluate the extent to which the proposed recent experience for each Subfactor is comparable in scope and complexity to the following respective Subfactor statement of work activities involving a military ground vehicle system or system(s):

L.4.1.3.1 Subfactor 1 Ground Vehicle Robotics (GVR): Systems integration of autonomy, Human Robot Interaction, Platform Electronic Control, and Autonomy Safety technologies for multiple unmanned military ground vehicle systems for an operational test and demonstration; for integrated unmanned military ground vehicle systems of comparable complexity to that of a Robotics Combat vehicle (RCV) and Expedited Leader Follower efforts.

L.4.1.3.2 Subfactor 2 Software Engineering Center (SEC): Embedded systems software engineering for a military ground vehicle of a comparable complexity to that of a Stryker or Joint Light Tactical Vehicle (JLTV).

L.4.1.3.3 Subfactor 3 Vehicle Electronics and Architecture (VEA): Development of an electrical power system utilizing the voltage output referenced in MIL-STD-1275 and MIL-PRF-GCS600A for a military ground vehicle of a comparable complexity to that of a Bradley combat vehicle.

L.4.1.4 Technical Experience Proposal Information Requested

The Offeror shall clearly organize and label its Technical Experience proposal information separately by Subfactor, with the exception of the submitted Technical Experience Matrix (Attachment 000X).

L.4.1.4.1 The Government may consider the experience of an entity other than the prime offeror as follows:

L.4.1.4.1.1 Associated Corporate Entities. The Government may consider the experience of an associated entity if the offeror successfully demonstrates meaningful involvement by the associated entity in the proposed effort. Submit any required written narrative outlined in this L.4.1.4.1.1 section as separate, stand-alone document(s), which shall be limited to 2 pages per submission.

L.4.1.4.1.1.1 An associated entity may include a parent company, separate corporate division within the same parent company, subsidiary company, a legally affiliated company, etc. The offeror shall provide to the Government a narrative that explains the offeror’s relationship to the associated entity. The offeror shall support the narrative with legal documentation, including but not limited to corporate papers, establishing the legal nexus between the offeror and the associated entity.

L.4.1.4.1.1.2 The offeror shall provide to the Government a narrative that explains the meaningful involvement the associated entity will provide to the proposed effort. Evidence of meaningful involvement may include a description of the associated entity’s resources, such as its workforce, facilities, and/or other resources that will be provided or relied upon in the proposed effort and a cross-reference to how these resources are accounted for within other proposal volumes (i.e. the Cost/Price volume). A submission will not be considered unless the offeror successfully establishes meaningful involvement by the associated entity in the proposed effort.

L.4.1.4.1.2 Predecessor Companies. The Government may consider the experience of a predecessor company if the offeror demonstrates the experience of the predecessor company is reasonably predictive of the offeror’s performance under the proposed effort. Submit any required written narrative outlined in this L.4.1.4.1.2 section as separate, stand-alone document(s), which shall be limited to 2 pages per submission.

L.4.1.4.1.2.1 A predecessor company may include a company which was acquired by the offeror or merged with the offeror. It may also include other instances where the predecessor company was reorganized, restructured, or otherwise altered. A predecessor company does not include an entity which remains separate and distinct from the offeror. The offeror shall provide to the Government a narrative that explains the offeror’s relationship to the predecessor company. The offeror shall support the narrative with documentation evidencing the offeror’s status as the successor company.

L.4.1.4.1.2.2 The offeror shall provide to the Government a narrative that explains why the predecessor’s experience is predictive of the offeror’s performance under the proposed effort.

Evidence may include, but is not limited to, continuity of operations such as the continued employment of the predecessor’s employees and the transfer of assets including buildings, furnishings, and fixtures.

L.4.1.4.1.3 Individual Partners of a Joint Venture. If the offeror is a Joint Venture, the Government may consider the experience of each partner of the Joint Venture and any work performed by the Joint Venture itself previously. The offeror must successfully demonstrate meaningful involvement by the partner to the proposed effort. Submit any required written narrative outlined in this L.4.1.4.1.3 section as separate, stand-alone document(s), which shall be limited to 2 pages per submission.

L.4.1.4.1.3.1 The offeror shall provide to the Government a narrative that discloses the individual partners of the Joint Venture and shall provide documentation evidencing the Joint Venture.

L.4.1.4.1.3.2 The offeror shall provide to the Government a narrative that explains the meaningful involvement the Joint Venture partner will provide to the proposed effort. Evidence of meaningful involvement may include a description of the partner’s resources, such as its workforce, facilities, and/or other resources that will be provided or relied upon in the proposed effort. A submission will not be considered unless the offeror successfully establishes meaningful involvement by the partner in the proposed effort.

L.4.1.4.2 Submission Information: Refer to the definition of a Contract above (L.4.1). The offeror’s proposal shall substantiate what distinct effort was required and actually performed under each of the proposed submissions.

L.4.1.4.2.1 The Offeror shall provide a completed Technical Experience Matrix (Attachment 000X), which shall clearly identify which (up to two) submission(s) it proposes to each Subfactor (See L.4.1.3.1, L.4.1.3.2, and L.4.1.3.3)).

L.4.1.4.2.2 For each submission proposed for a Subfactor identified in the Technical Experience Matrix (Attachment 000X), provide the following information:

(a) A copy of the executed contractual instrument’s cover sheet and/or other content that identifies the entities/parties of the proposed submission and the execution date;

(b) A copy of the complete Performance Work Statement (PWS) or Scope of Work (SOW).

In addition, if the proposed submission was issued under or in connection with a related written instrument (e.g. Indefinite Delivery Contracts, BOA, BPA, FSS) and the details of the distinct effort actually performed in order to further substantiate comparability on the proposed submission are further defined within the terms and conditions (e.g. statement of work) of that related written instrument, provide that information and any other necessary information to establish this instruments relationship to the proposed submission. (These documents can be submitted as stand-alone attachments within the proposal volume)

L.4.1.4.2.3 For each Subfactor, The offeror shall provide a separate written narrative that shall not exceed 20 pages. The written narrative shall address each submission separately, and shall describe specifically detail the work performed on the (up to two) proposed submission(s) and the submission(s) comparability to the Subfactor statement of work activity. Offerors are cautioned that the Government will not review any pages beyond the 20 pages.

Note 1: Do not provide a breakdown of comparability of the entire Section C Statement of Work of the current RFP to the proposed submission(s). When citing specific work performed on the proposed submission, provide references to the specific locations within the scope or other substantiating documentation, such as paragraph or page number, when possible. When applicable, in its description, the offeror should specify the location in the proposal (to include filename or document reference with page and/or paragraph number) that further substantiates comparability if stand-alone attachments are submitted in this volume.

Note 2: Any narratives provided in response to L.4.1.4.1 and its subparagraphs above do not count towards this Subfactor comparability written narrative (L.4.1.4.2.3) page limit, and shall be submitted separately.

L.4.2: Sample Task Factor Volume

The Sample Task Factor consists of three Subfactors:

1) Subfactor 1: GVR Sample Task

2) Subfactor 2: SEC Sample Task

3) Subfactor 3: VEA Sample Task

Section L.4.2 and its subparagraphs apply to all Subfactors, unless otherwise stated.

L.4.2.1 Sample Tasks. Each Subfactor consists of one Sample Task. All Subfactor Sample Tasks are detailed in Attachment 0005. The offeror shall submit a separate response addressing all requirements of paragraph 1.0 “Submission Requirements” in each of the three Subfactor Sample Tasks. Each Subfactor Sample Task response shall be limited to a total of 46 pages, which is further divided into page limits for different sections of the required information, as defined in Paragraph 1 of each respective Subfactor Sample Task attachment.

L.4.2.2 Offerors are advised to provide the information required by the Government to assess the offeror’s understanding of sample task requirement(s). Since this information constitutes a basis of the Government's review, it is the offeror's responsibility to submit detailed and complete information as required so the Government may evaluate each of its Sample Task responses, and imperative that the offeror present its response in a clear and complete manner. Failure to provide inadequate detail and/or applicable information may result in an assessment that the offeror lacks an understanding of sample task requirement(s).

L.4.3: Cost/Price Factor Volume

TBD

L.4.4: Small Business Participation Factor Volume

L.4.4.1 Application: The Small Business Participation proposal submission instructions apply to every Offeror (U.S. and non-U.S.), regardless of size, socioeconomic status, or locations of working facilities or headquarters.

L.4.4.2 Small Business Participation Factor Workbook (Attachment XXX1) and Small Business Participation Factor Workbook Instructions (Attachment XXX2):

a. All Offerors, including Offerors who are themselves small business concerns for the North American Industry Classification System (NAICS) code assigned to this requirement, are required to complete the SBP Factor Workbook using the detailed SBP Factor Workbook Instructions.

The Offeror’s submission of the SBP Factor Workbook is the Offeror’s proposed extent of Small Business Participation in each Small Business category.

b. An Offeror shall fill out the SBP Factor Workbook with goals for this solicitation specifically, even if it is an Other-Than-Small-Business (OTSB) submitting a Comprehensive Subcontracting Plan.

c. When filling in the Workbook, the Offeror shall include the dollars for prime contractor participation and subcontractor participation that are a part of the “Total Contract Amount”.

The “Total Contract Amount” for the purposes of this Factor is defined as: TBD. (See Cross Reference in Cost/Price Workbook – Attachment 00XX, Tab XX, Cell XXX.)

d. The Offeror shall use the automatic “Roll-Up” tab in the Workbook to check for consistency between the SBP Factor Submittal and other parts of the proposal (i.e Cost/Price Factor), and (for offerors who are OTSB) the submitted Subcontracting Plan.

L.4.4.3. Registrations, Agreements, and Certifications:

a. The Government may use the System for Award Management (SAM) to verify size, ownership, and any other information provided about the prime and subcontractors listed in the proposal.

The Government may use the Small Business Administration (SBA) Dynamic Small Business Search (DSBS) Database to verify any SBA certifications for 8(a), 8(a) JV, and WOSB/EDWOSB SBs (prime contractor and/or subcontractor). Any proposed HUBZone SBs (prime contractor and/or subcontractor) must be verifiable in the Small Business Administration (SBA) Dynamic Small Business Search (DSBS) Database. Offerors should be aware of how SB concerns are defined (see Small Business Participation Factor Workbook Instructions (Attachment XXX2) and 13 CFR 121, Small Business Size Regulations). Offerors are advised to review 13 CFR 121.103, "How Does SBA Determine Affiliation”; FAR 2.101, “Small Business Teaming Arrangement”; and FAR 19.101, “Affiliates”.

b. Failure to register in SAM for the corresponding NAICS code identified in FAR clause 52.204-8 prior to submitting a proposal for this solicitation may preclude an award being made to your company.

c. Joint Venture Registration. If the Offeror is a small business joint venture, the joint venture shall be registered in SAM under its own name in accordance with 13 CFR 121.103(h). In addition, each member in a small business joint venture shall be registered in SAM for the type of work it does. To be recognized as a small business joint venture and be eligible for award of a contract, the membership arrangements of the joint venture shall be identified and the company relationships fully disclosed in the Offeror’s proposal in accordance with FAR 9.603.

d. Affiliate Registration. If the Offeror is a small business that has first tier affiliates that will be performing work on the proposed contract, each first tier affiliate shall be registered in SAM for the type of work it does.

e. Subcontractor Registration or Certification. According to FAR Clauses 52.219-8 and 52.219-9 in this solicitation, the Offeror may not require subcontractors to be registered in SAM. For any small business subcontractor listed in the SBP Factor Workbook that is not registered in SAM, the Offeror shall provide in accordance with 13 CFR 121.411(g), a Certification Form (Attachment XXX3) from that subcontractor verifying its small business size and socioeconomic status. This certification shall contain, on the same page as the size and status claimed, the signature of the official authorized to sign for the subcontractor.

L.4.4.4 Other Resources/Additional Data: In addition to the data submitted by the Offeror, and the data found in Government systems specifically referenced throughout this L.4.4, the

Government may use other resources to evaluate the Offeror’s SBP Factor Submittal. The Government reserves the right, during clarification or discussion under FAR 15.306, to request additional data to support its assessment.

L.5 Administrative Volume. In addition to the proposal evaluation factor volumes above, provide the following information:

L.5.1 Signature Actions/offeror Fill-Ins. Provide a scanned image of a signed copy of the SF33 cover page, a copy of all completed fill-ins for Sections A through K, and (if applicable) a signed copy of all Amendments to the solicitation. System for Award Management (SAM) certifications need not be separately submitted; however, all offerors must be successfully registered and valid in SAM prior to award.

L.5.1.1 Where certifications and approved systems are required for an offeror, if the proposal is being submitted by a Joint Venture, certifications and approved systems for the principals (partners) of the joint venture will be considered as valid for that offeror providing the necessary documentation from all principals (partners) is provided with the proposal.

L.5.1.2 Joint Venture (JV): To be recognized as a JV and eligible for award, the membership arrangements of the JV must be identified and the company relationships fully disclosed in the offeror's proposal IAW FAR 9.603. A copy of the agreement establishing the JV must contain the signatures of all of the members comprising the JV.

L.5.2 The offeror’s proposal acceptance period in terms of calendar days from the date for receipt of offers specified in the RFP. (See Section L.1.2)

L.5.3 Statement of Acknowledgement. A statement specifying the extent of agreement with all terms, conditions, and provisions of the RFP, and a statement of agreement to furnish and deliver the items or perform services set forth in the RFP in consideration for offeror’s proposed price(s) set opposite each item. Any exceptions taken to the attachments, exhibits, enclosures, or other solicitation terms, conditions, or documents may be determined to be a Deficiency or grounds for the Government to reject the proposal from further consideration in the source selection process (Reference M.2.1).

L.5.4 Assumptions. The offeror shall consolidate and identify all offeror's generated "assumptions" contained anywhere in the proposal. The offeror shall include a statement that none of the "assumptions" contradict or take exception to any terms, conditions, or requirements of the solicitation. Any exceptions taken to the attachments, exhibits, enclosures, or other solicitation terms, conditions, or documents may be determined to be a Deficiency or grounds for the Government to reject the proposal from further consideration in the source selection process (Reference M.2.1).

L.5.5 Organizational Conflict of Interest (OCI). The offeror shall provide an affirmative statement that the offeror does not have an OCI as it applies to this solicitation. (Reference L.2.4)

L.5.6 If Government Property (as defined in 52.245-1) will be utilized in the performance of this contract, provide a description of your property management system, plan, and any customary commercial practices, voluntary consensus standards, or industry-leading practices and standards to be used by you in managing Government property in accordance with 52.245-1.

L.5.7 Small Business Subcontracting Plan.

L.5.6.1. If the offeror is other than a U.S. Small Business concern as defined by the North American Industry Classification System (NAICS) code applicable to this solicitation, the offeror shall submit an acceptable small business subcontracting plan in accordance with FAR Clause 52.219-9 and its ALT II and Defense FAR Supplement (DFARS) Clause 252.219-7003 and provide this plan as part of the proposal submission. Offerors are encouraged to review the DoD checklist at http://business.defense.gov/Acquisition/Subcontracting/. Note that such a plan is not required of offerors that are small businesses.

L.5.7.2. The plan shall be submitted as an Attachment to the offer in response to this solicitation.

L.5.7.3. Each page of the subcontracting plan shall be marked with the solicitation number and date, and may also be marked with other codes or identification symbols to aid in later identification.

L.5.7.4 Dollars: The Small Business Participation Factor includes specific instructions as to what to include in the dollars for the Factor Submittal, for example, specific CLINS, options, task orders, proposed prices, target prices, or weighted average prices, etc. To ensure consistency with the Small Business Participation Factor, the offeror shall follow those same instructions in developing the Small Business Subcontracting Plan dollars.

L.5.7.5. Percentages: The offeror shall submit the Small Business Subcontracting Plan with goals expressed in TWO ways: (a) as a percentage of Total Subcontracting Amount and (b) as a percentage of Total Contract Amount as defined in the Small Business Participation Factor in this Section L.

L.5.7.6. Breakout: The offeror shall note the differences between the Small Business Participation Factor and the Small Business Subcontracting Plan, as explained in the Small Business Participation Factor, including the proper breakout of the Small Business Subcontracting Plan.

L.5.7.7. Failure to submit and negotiate an acceptable subcontracting plan which, in the judgment of the Contracting Officer, provides the maximum practicable opportunity for small business and small disadvantaged business concerns to participate in the awarded contract may render the offeror ineligible for award. In this connection, offerors should be aware of the statutory goal that has been placed on the Department of Defense to award five percent of its total planned subcontracting dollars to small disadvantaged businesses at the prime contract and subcontract levels. In view of this Congressional mandate, the offeror shall provide, within the plan, a specific explanation of any aggregate small disadvantaged business goal of less than five percent of the proposal's total subcontracting dollars.

L.5.7.8. If the offeror participates in the Small Business Subcontracting Plan (Test Program) described in DFARS 219.702, an approved DoD Comprehensive Subcontracting Plan may be submitted with the offer. DFARS 252.219-7004 shall be added to any contract that incorporates a DoD Comprehensive Plan.

L.5.8 Cost Accounting System. Pursuant to FAR 9.104-1(e) and FAR 16.301-3(a)(3), and in order to be considered for award, the offeror must provide evidence that it has adequate financial management and fund tracking procedures to accommodate a cost-reimbursement type contract. The offeror shall provide evidence, which may be in the form of a letter from either DCMA or DCAA that states that the offeror has an adequate accounting system, or other acceptable evidence. If an accounting system has not been determined to be adequate by DCMA or DCAA, the Offeror shall coordinate with the Contracting Officer to obtain an accounting system review prior to submitting a proposal. If an accounting system has not been determined to be adequate by DCMA or DCAA, the offeror shall complete all questions contained in Attachment 00XX, Preaward Survey of Prospective Contractor Accounting System Checklist, and provide an explanation to support the response. The Offeror shall then submit the completed form via email to the Contracting Officer prior to submitting a proposal.

L.5.9 Facility Requirements Documentation.

L.5.9.1 In order to be eligible for award, the offeror shall meet the requirements in Section H.12.1 at time of contract award. The offeror shall provide the following acceptable evidence to demonstrate it can meet the facility requirements in H.12.1 at time of award:

1) Physical address and CAGE code (if applicable) of facility

2) Proof of ownership of proposed physical address. If not owned by the prime offeror, the offeror shall also provide a copy of an actual lease agreement or contingent lease agreement for use of proposed building. The lease agreement must include the following:

a. Include the physical address of the proposed operational facility.

b. State the prime offeror has right of first use of the facilities for performance of the contract resulting from this RFP W56HZV-22-R-0003 at any time necessary to perform in accordance with the individual task order(s).

c. Be valid for the full duration of the contract.

d. Be signed and dated by both parties

3) Provide a certification that the offeror’s proposed operational facility meets the requirements of Section H.12.1.

4) Provide schematics and drawings of the proposed facility that demonstrates the layout and conformance to the following requirements set forth in H.12.1:

a. Three vehicle bays, space claim for three theoretical vehicle that are each 40 ft.

long and 14 ft. wide, SIL bench space, garage door(s), crane, 20 workstations, and conference room space/seating for 14 people.

L.5.9.2 The Government may elect to consider data obtained from internal and external sources other than the offeror’s proposal. If the Government has reason to question the validity of the evidence provided by the offeror, it may result in the offeror being determined ineligible for award.

M.1 Basis of Award

M.1.1 The Government intends to award a Single Award, Indefinite Delivery, Indefinite Quantity, Cost-Plus-Fixed-Fee Contract. An award will be made to the offeror whose proposal represents the best value to the Government in accordance with the criteria set forth below, and is eligible for award.

M.1.1.1 There are four evaluation factors:

a. Technical Experience Factor

b. Sample Task Factor

c. Cost/Price Factor

d. Small Business Participation Factor

The relative order of importance of these Factors are described in Section M.4 below.

M.1.1.2 Proposal selection will be made utilizing the source selection trade-off process, considering the evaluation Factors and their relative order of importance (see Section M.4), to identify the proposal which represents the best value and is most advantageous to the Government.

The Government will weigh the evaluation factors (other than the Cost/Price Factor) against the final evaluated price to the Government. As part of the best value determination, the relative strengths, weaknesses, and risks of each proposal shall be considered in selecting the offer that is most advantageous and represents the best overall value to the Government. The Government reserves the right to choose not to award a contract if such action is in the Government’s best interest.

M.1.1.3 In making the award decision, the Government will review proposals to determine if any other price adjustments (beyond any adjustments already included in the total evaluated price) are required IAW the FAR, DFARS, or clauses or provisions contained within this solicitation. If an additional price adjustment is determined to be applicable, then the Government will develop a final price for those offerors impacted by the adjustment(s) and base the final award decision on this final price. IAW FAR 52.219-4(b)(2), if the HUBZone price adjustment is applicable, then all other price adjustments described in the solicitation shall be applied before the application of the HUBZone price adjustment.

M.1.1.4 Importance of Cost/Price. Award will be made to the offeror whose proposal represents the best value to the Government and is otherwise eligible for award. This may not be the offeror with the lowest evaluated cost/price. However, the closer offeror's evaluations are to each other in those Factors other than the Cost/Price Factor, the more important cost/price becomes in the decision. Notwithstanding the relative order of importance of the evaluation Factors stated herein, cost/price may be controlling when:

a. Proposals are otherwise considered approximately equal in non-price factors; or

b. An otherwise superior proposal is unaffordable; or

c. The advantages of a higher rated, higher priced proposal are not considered to be worth the price premium.

M.1.2 Eligibility for Award. Award will only be made to an offeror who is eligible for award. To be eligible for award:

a. The offeror must be determined responsible (See Section M.3.6)

b. The proposal must not contain a Deficiency(s) (per FAR Part 15.001); and

c. The offeror must be registered in the System for Award Management (SAM) - see provision 52.204-7; and

d. The offeror must have acceptable evidence of an operational facility (See Section L.5.9).

M.2 Rejection of Offers

M.2.1 The Government may reject any proposal if in the Government's best interest at any time after receipt of proposal. Examples include, but are not limited to, the following proposal conditions:

a. The proposal fails to meaningfully respond to the instructions in Section L of this solicitation (e.g. a proposal provides some data but omits significant material data and information required by Section L, the offeror fails to submit pricing Attachment 00XX in accordance with the instructions, the proposal fails to follow key proposal instructions or format requirements in Section L, etc.).

b. A proposal merely offers to perform work according to the solicitation terms or fails to present more than a statement indicating its capability to comply with the solicitation terms and does not provide support and elaboration as specified in Section L of this solicitation.

c. The proposal proposes exceptions to the RFP requirements, attachments, exhibits, enclosures, or solicitation terms and conditions.

d. The proposal contains one or more Organizational Conflicts of Interest (OCIs) that cannot be avoided or mitigated. Refer to Section L paragraph L.2.4 of this solicitation, "Organizational Conflict of Interest."

e. The proposal is unbalanced as to price. See Section M.X.X.

f. The proposal submitted is for less than all the requirements called for by the solicitation.

g. The proposal’s acceptance period does not meet the Government’s required minimum acceptance period, or the offeror fails to provide a proposal acceptance period (Refer to Section L.1.2).

h. The proposal is not in English (American Standard) or in US Dollars.

i. The offeror does not provide valid and/or acceptable evidence of the operational facility as required by L.5.9.

M.3 Source Selection Process

M.3.1 Compliance Review. After receipt of proposals, but prior to the evaluation process, the Government will perform a compliance review of the offeror’s proposal to determine the extent of compliance to the solicitation instructions, and whether the proposal meets any of the conditions listed in M.2, Rejection of Offerors.

M.3.2 Evaluation Process. Selection of the successful offeror will be made following an assessment of each proposal not otherwise rejected, based on the response to the information called for in Section L of this RFP, and against the solicitation requirements and the evaluation criteria described herein. Proposals not otherwise rejected will be evaluated as specified herein, to include developing narrative support for the evaluation conclusions under each Factor.

M.3.3 Source Selection Authority. The Source Selection Authority (SSA) is the official designated to direct the source selection process and select the offeror for contract award. A Source Selection Advisory Council (SSAC) will provide a written comparative analysis of the proposals and an award recommendation for the SSA prior to the selection decision.

M.3.4 Source Selection Evaluation Board (SSEB). An SSEB has been established by the Government to evaluate proposals in response to this solicitation. The SSEB is comprised of technically qualified individuals who have been selected to conduct this evaluation in accordance with the evaluation criteria for this solicitation. All proposals not otherwise rejected will be given careful, full and impartial consideration by a team of Government personnel in the evaluation, pursuant to the criteria in this solicitation.

M.3.5 Award without Discussions. This RFP includes FAR Provision 52.215-1 Instructions to Offerors Competitive Acquisition in Section L which advises offerors that the Government intends to make award without conducting discussions. Where awards will be made without discussions, exchanges with offerors are limited to Clarifications as defined in FAR 15.306(a). Therefore, the offerors initial proposal should contain the offerors best terms from a Price and non-Price Factor standpoint. However, under FAR 52.215-1(f)(4), the Government reserves the right to hold discussions, if necessary. If the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

M.3.6 Determination of Responsibility. Per FAR Part 9.103, a contract will be placed only with the offeror that the Contracting Officer determines to be responsible. Prospective offeror(s), in order to be eligible for award for this acquisition, must be able to demonstrate that they meet standards of responsibility set forth in FAR Part 9.104, or refer the matter to the SBA per FAR 19.602 when applicable. In addition, the Government may assess the offeror's financial and management capabilities to meet the solicitation requirements. The Government reserves the right to conduct a Pre-Award Survey on any or all offeror(s) or their subcontractors to aid the Contracting Officer in the evaluation of each offeror's proposal and ensure that a selected offeror is responsible. No award can be made to an offeror who has been determined to be not responsible by the Contracting Officer. To make sure that you meet the responsibility criteria at FAR Part 9.104, the Government may:

a. Arrange a visit to your facility and/or proposed operational facility (Ref Sec L.5.10) and perform a necessary Pre-Award Survey. The offeror's refusal to authorize the Government to visit the offerors facility may result in a determination that the offeror is not responsible and/or ineligible for award.

And/or

b. Request an offeror provide financial, technical, production, or managerial background information. If the requested information is not submitted within seven calendar days from the date of the receipt of the request, or if an offeror refuses the Government access to its facility, the Government may determine the offeror non-responsible. If the Government visits the offeror's facility, please ensure that current data relevant to the proposal is available for Government personnel to review.

M.3.7 Consistency. Each volume of the offerors proposal shall be consistent with the other proposal volumes and shall demonstrate the understanding and ability to perform according to the statement of work of the contract. The offeror should provide supporting documentation in sufficient detail to permit a complete evaluation of the proposal. The Government may conduct a crosswalk between the information provided in offerors proposal volumes to assess whether the offeror submits consistent proposal information.

M.4 Evaluation Criteria

There are four evaluation factors:

a. Technical Experience Factor

b. Sample Task Factor

c. Cost/Price Factor

d. Small Business Participation Factor

The relative order of importance of these factors is as follows: Technical Experience Factor is slightly more important than Sample Task Factor, which is significantly more than the Cost/Price Factor, which…

This is the start of the file's text. The full file is on GovTribe.

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