Atch 1 - Section L - Instructions to Offerors (ITO).pdf

PDF 224 KB Posted

Attached to
AFSOC - MC-12 - Tactical System Operators (TSO) Training Support Services Federal contract opportunity
Solicitation number
FA002122R0008
Issued by
Department of the Air Force Materiel Command Installation and Mission Support Center Installation Contracting Agency

About this file

This document contains instructions to offerors for a federal solicitation seeking tactical system operator training support services. The contractor will provide all personnel, supervision, transportation, and other items and services necessary to train Air Force Special Operations Command tactical system operators on MC-12W/BE-300 ISR variant aircraft. Training support includes providing mission aircrew, scheduling, registration, and opposing force/mission rehearsal services. The work will be performed at Will Rogers National Guard Base in Oklahoma City, Oklahoma. Offerors must submit proposals in four volumes by the closing date of July 22, 2022 following detailed formatting and content instructions provided. The proposal must demonstrate technical capability, past performance, and propose pricing using the required worksheet.

View the file

Other files for this federal contract opportunity

Show all 18

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

SECTION L

INSTRUCTIONS TO OFFERORS (ITO)

8 JULY 2022

Notices to offeror(s):

Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The government reserves the right to cancel this solicitation, either before or after the closing date. In the event the government cancels this solicitation, the government has no obligation to reimburse an offeror for any costs.

During the duration of this contract, funding may be provided incrementally, reference DFARS 252.232-7007, Limitation of Government s Obligation.

A. GENERAL INSTRUCTIONS

1. To assure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation and render the proposal ineligible for award. Offerors must clearly identify any exceptions to the solicitation terms and conditions and provide complete accompanying rationale for the exception. Documents submitted in response to this RFP must be fully responsive to, and consistent with, the requirements of the RFP, Performance Work Statement, and evaluation factors for award in Section M of this RFP.

2. Points of Contract. The Contracting Officers (COs) listed below are the points of contact for this acquisition.

Table L-1: Contracting Officers

Steven Rawcliffe Contracting Officer

Kevin Miller Contracting Officer

AFICC/765th ESF AFICC/765th ESF

427 Cody Ave, Bldg. 90333, Ste 130 Hurlburt Field, FL 32544

427 Cody Ave, Bldg. 90333, Ste 130 Hurlburt Field, FL 32544

E-mail: steven.rawcliffe@us.af.mil

Email: kevin.miller.4@us.af.mil

3. Submission of Questions. Questions submitted after the response date/time specified will not be answered. Submit all questions concerning this solicitation in writing via e-mail to BOTH Contracting Officers listed above utilizing the Question Format (Attachment 4) no later than SEVEN (7) business days after issuance of this solicitation.

4. Discrepancies. If an offeror believes the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify contracting officer in writing with supporting rationale as well as the remedies the offeror is asking the contracting officer to consider as related to the omission or error.

5. Electronic Submission of Proposals. All proposals shall be submitted in electronic format and shall follow the instructions in Paragraph C, Volume Preparation Instructions, below. Do not email proposals directly to the Contracting Officers. Paper copies of proposals will not be evaluated, will be rejected, and will not be considered for award.

5.1. Offerors are responsible for submitting their proposal to reach the Contracting Officer designated above by the date and time specified. Submit all proposals electronically to the Government via ‘Drop-off’ found on the DoD SAFE website at https://safe.apps.mil/ no later than the solicitation closing date and time referenced in Block 9 of the Standard Form (SF) 33.

5.2. The title of the files submitted shall include the offeror’s CAGE code, volume number, and volume title. (i.e., “CAGE CODE Volume #, Volume Title”). Specific how-to instructions for submitting documents via DoD SAFE can be found on the DoD SAFE website listed above.

Offerors shall submit proposals via DoD SAFE, allowing sufficient time for upload to be completed by the solicitation closing date and time.

5.3. It is the sole responsibility of the Offeror to ensure that all electronic files submitted are virus free. Proposal submissions shall not be locked, encrypted, zipped, or otherwise contain barriers to opening. Microsoft (MS) Excel files provided as template shall be submitted as MS Excel files. The Offeror shall not modify, adjust, or change any part of the MS Excel files required submission of this solicitation unless authorized by the Contracting Officer and annotated on proposal. Any unauthorized changes to MS Excel files shall make the proposal unresponsive.

5.4. Files shall not contain any classified data and must adhere to the page limitations required in the solicitation.

6. Only one (1) proposal per company will be accepted. Proposals received after the date/time will be handled in accordance with FAR 52.215-1(c) (3), Submission, Modification, and Revision of Proposals.

7. Pre-proposal Conference/Site Visit. A pre-proposal site visit will not be conducted for this solicitation.

B. PROPOSAL SUBMISSION INSTRUCTIONS

1. The following instructions prescribes the format for proposals and describes the approach to be used for the development and presentation of the proposal data. The proposal shall include all of the information requested in the specified instructions. Failure to include all information requested may adversely affect the evaluation and may result in a determination that the proposal is ineligible for award.

https://safe.apps.mil/

2. Proposals shall be clear, concise, and shall contain sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government’s requirements but shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the government has no prior knowledge of their facilities, capabilities, and experience and will base its evaluation on the information presented in the offeror’s proposal.

2.1. Elaborate formats, binding, detailed artwork, or other embellishments are unnecessary and are not desired or required.

3. Proposals shall be complete and consist of four (4) separate volumes consisting of the number of electronic copies as follows:

Table L-2: Proposal Volumes

Volume Title Number of Electronic Copies I Contract Documentation One (1) Unredacted

II Factor 1 – Technical Capability One (1) Unredacted and One (1) Redacted

III Factor 2 – Past Performance One (1) Unredacted and One (1) Redacted

III Factor 2 – Price One (1) Unredacted

3.1. Redacted copies shall be submitted in the same manner as original copies. Information to be redacted includes all references to the offeror’s company, i.e., company names/key personnel names and company logos/symbols/identifiers.

C. VOLUME PREPARATION INSTRUCTIONS

1. Proposal Organization/Number of Copies/Page Limits. The offeror shall organize each volume as identified in the Table L-2: Proposal Volumes and in accordance with the instructions provided below.

1.1. Each volume shall be written on a standalone basis so that its contents may be evaluated with no requirement to cross reference to other volumes of the proposal.

1.2. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. The PCO may also place page limitations on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the EN form. Unless otherwise indicated in the volume details, each page shall be counted except for cover pages, table of contents and indexes, blank pages, glossaries, and cross reference matrices.

1.3. A page is defined as each face of an 8 ½ x 11-inch document containing information. Page margins shall be a minimum of 1-inch each for the top, bottom and sides. Except for the reproduced sections of the solicitation document and footnotes, the text size shall be no less than 12-point in Times New Roman or Arial font. Tracking, kerning, leading values, and footnote font size shall not be changed from the default values of the word processing or page layout software.

1.4. Charts, illustrations, tables, or diagrams shall not exceed 11 x 17 inches. For page count purposes, this page will count as two (2) 8 ½ x 11-inch pages and shall only be used for graphics and exhibits. All information (except for document numbers, page numbers, etc.) shall be provided with an image area of 9 x 15 inches. Text used for call-outs on graphics and exhibits shall be no smaller than 8-point Times New Roman or Arial, after final reductions. Call-outs may be single-spaced.

1.5. Cross Referencing. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Offerors are responsible for the accuracy of their proposals and the Government will NOT search for information that is not provided in the required Volume.

2. VOLUME I – CONTRACT DOCUMENTATION

Table L-3: Volume I – Contract Documentation

Volume Title Page Limit

Volume I – Contract Documentation

Section 1: Table of Contents

No page limits

Section 2: Solicitation (SF33) / Amendments (SF30) Section 3: Completed DD254 Section 4: Contractor Team Organization Section 5: Certifications and Representations Section 6: Exceptions to Solicitation Requirements (If Applicable) Section 7: Financial Responsibility Document Section 8: Glossary of Abbreviations and Acronyms

2.1. Section 1 - Table of Contents. A detailed table of contents delineating the subparagraphs within the volume.

2.2. Section 2 - Solicitation (SF33) / Amendments (SF30). Offerors shall complete Block 12s, 13, 14, 15A-15C, 16, 17, and 18 of the solicitation. Offerors shall provide signed copies and acknowledge all amendments to the solicitation. Signatures must be of an individual authorized to negotiate on behalf of the Offeror.

2.2.1. Proposal Acceptance Period. The proposal acceptance period is a minimum of 240 calendar days after the proposal due date. Insert the number of calendar days in Block 12 of the SF33. 2.7. Offerors may specify a longer acceptance period than the Government’s minimum 240 days by inserting its proposed acceptance period in Block 12 of the SF33.

2.3. Section 3 – Completed DD 254, In order to safeguard the release of classified information, DD254, Contract Security Classification Specification, is a requirement at time of proposal submission. The offeror, subcontractors, teaming partners, joint venture members, and any other company that will perform work on this contract must possess a facility clearance equal to the highest classification as indicated on the DD254 attached to this solicitation (Attachment 5) in accordance with DoDD 5220.22-M, National Industrial Security Program Operating Manual

(NISPOM).

2.3.1. Offerors shall complete blocks 6a-7c of the DD254, DoD Contract Security Classification Specification and submit National Industrial Security System (NISS) screenshots demonstrating proof of current U.S. Facility clearance at the SECRET level for the offeror, subcontractors, teaming partners, joint venture members, and any other company that will perform work on this contract. The SECRET facility clearance must be current at time of proposal submission.

2.3.1.1. For those Offerors submitting a proposal as a newly formed partnership, joint venture, or limited liability company, this requirement can be satisfied through the submittal of NISS screenshots evidencing the fact that each partner or member of the partnership currently possesses the required SECRET Facility Clearance. The SECRET facility clearance must be current at time of proposal submission.

2.3.1.2. If the Offeror and its subcontractors, teaming partners, joint venture members, or any other company that will perform work on this contract does not submit their current NISS screenshots or lacks the proper SECRET facility clearance classification, the offer will be eliminated from further consideration.

2.4. Section 4 - Contractor Team Organization

2.4.1. The Offeror shall complete Table L-4, Offeror Summary Table below.

Table L-4: Offeror Summary Table

Contractor Name (Indicate Prime, Joint

Venture Team Member or Sub)

Place of Performance

Cage Code

/DUNS #

Brief Work Description and/or

Program Responsibility

% of Total

Proposed Price

2.4.2. The Offeror shall include all subcontractors and Joint Venture team members who will be involved with the performance of the contract and list all sites where the work will be performed.

If a Joint Venture teaming or subcontracting arrangement is proposed, identify the work share, distribution elements, and ratios that each contractor will perform using the table below. Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship.

2.4.3. The Offeror shall provide a written explanation if multiple CAGE codes/DUNS for the same physical location are provided in the Offeror Summary Table. The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes/DUNs at the same physical location for where the work is being performed or from where the work is being directed. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason.

2.4.4. Offeror shall provide all Teaming Arrangements and Letters of Intent for Team Members to receive credit for performing as a team. A business entity can participate in this acquisition on one proposal only. During this evaluation, if a company is identified as a prime contractor or teaming partner/subcontractor on any proposal for this acquisition, then that company cannot participate on any other offeror’s proposal. It is the offeror’s responsibility to ensure teaming partners and subcontractors are not teamed with other offerors.

2.5. Section 5 - Certifications and Representations. The offeror shall provide the following certifications/representations:

2.5.1. Authorized Offeror Personnel: Provide the name, title, and telephone number of the offeror point of contact regarding decisions made with respect to the Offeror’s proposal and who can obligate the Offeror contractually. Also, identify those individuals authorized to negotiate with the Government along with the name, title, and telephone number of the CEO, Division President, Vice President, or similar person of the Offeror for notification purposes.

2.5.2. Company/Division Address, Identifying Codes, and Applicable Designations: provide Company or division’s street address, county and facility code; CAGE code; DUNS code; TIN;

and labor surplus area designation.

2.5.3. Joint Venture certifications: If the Offeror is a Joint Venture, the Offeror shall provide a copy of the Small Business Administration (SBA) approved Joint Venture certification documentation.

2.5.4. Size of business; and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

2.6. Section 6 - Exceptions to Solicitation Requirements.

2.6.1. Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors shall clearly identify any exceptions to the terms and conditions of the solicitation/contract. While offerors may propose exceptions to the solicitation requirements, the Government is not obligated to accept or consider such exceptions. Further, exceptions could result in an offer being ineligible for award. Any change to the requirement as a result of accepting an exception shall be reflected within the resultant contract.

2.6.2. Exceptions taken to terms and conditions of the solicitation/contract, to any of its formal attachments, or to other parts of the solicitation shall be identified.

2.6.3. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken.

2.6.4. This information shall be provided in the format and content of Table L-5 below. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award.

Table L-5: Solicitation Exceptions

Solicitation Document

Paragraph/Page Requirement/Portion Rationale

Contract clause, solicitation paragraph, ITO, etc.

Applicable page and paragraph numbers

Identify the requirement or portion to which exception is taken

Justify why the requirement will not be met

2.6.5. In the event the offeror takes no exception to the stated requirements, a statement to this effect is required in this volume.

2.7. Section 7 - Financial Responsibility Documentations. This information will be used to determine the offeror’s responsibility pursuant for FAR 9.104-1. Offeror shall submit a financial capability letter from offeror’s financial institution or Certificate of Competency (COC) issued by the Small Business Administration (SBA).

2.7.1. Send Financial Responsibility Questionnaire (Attachment 6), to one or more banking/lending institutions the Offeror does business with and have a representative complete the questionnaire and return to the POC of this solicitation no later than proposal due date.

2.7.2. Financial responsibility will not be evaluated as a separate cost/price subfactor. However, it is a basic contract requirement with a pass/fail determination thus it will be evaluated during the source selection process. A contract may only be awarded to the Offerors who are deemed responsible in accordance with the Federal Acquisition Regulation (FAR).

3. VOLUME II – FACTOR 1: TECHNICAL CAPABILITY.

Table L-6: Volume II – Factor 1: Technical Capability

Volume Title Page Limit

Volume II Factor 1 – Technical Capability

Section 1: Table of Contents

30 pages Section 2: Factor 1: Technical Capability; Subfactor 1 – Mobilization Plan & Recruiting, Hiring, and Retention Plan.

Section 3: Glossary of Abbreviations and Acronyms

3.1. Section 1 - Table of Contents. A detailed table of contents delineating the subparagraphs within the volume. The Table of Contents does not count against the page limitations for Volume

II.

3.2 Section 2 – Factor 1: Technical Capability. The Technical Proposal should be specific and complete. Legibility, clarity, and coherence are very important. The offeror’s responses will be evaluated against the technical evaluation criteria in Section M, Evaluation Factors for Award. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation, but instead discuss how the offeror plans to accomplish each of the requirements.

Exceptions to any requirements shall be documented in Volume I – Contract Documentation, Section 6. The total combined page limit for Volume II is 30 pages.

3.2.1 The Technical Capability volume shall address the following factors:

- Subfactor 1: Mobilization Plan & Recruiting, Hiring, and Retention Plan.

3.3 Section 2 – Technical Subfactor 1: Mobilization Plan & Recruiting, Hiring, and Retention Plan. The Offeror shall provide an in-depth, relevant, complete, and effective strategy and technical approach showing a direct relationship between the proposed approach and meeting the Performance Work Statement (PWS) objectives. The Offerors technical proposal shall include at a minimum the following:

3.3.1. Mobilization Plan. Offerors shall expediently mobilize and be ready to fully perform all contract requirements within 30 calendar days of the performance start date. Offerors shall submit their mobilization plan detailing how the offeror intends to manage, staff, schedule, and complete all necessary start-up tasks within 30 calendar days of the performance start date. The mobilization plan shall include at a minimum:

3.3.1.1. A mobilization schedule, the schedule shall include chronological milestones as it pertains to contract startup and mobilization. At a minimum, the schedule shall include specific milestones for recruitment, placement, training, and the projected timeframe for each milestone to achieve full compliance with the PWS.

3.3.1.2. Offers shall identify potential start-up performance risks and their subsequent proposed risk mitigation strategies.

3.3.1.3. Staffing. Offers shall provide the labor category and number of personnel to be staffed in performance of the contract. Estimated workload requirements are identified in Appendix B of the PWS. Offerors shall include timelines and rationale for staffing the contract with the number of personnel and labor categories proposed at specific milestone events. Offerors shall be fully staffed within 30 days after the start of the period of performance.

3.3.2. Recruiting, Hiring, and Retention Plan. Offerors shall describe their approach to recruitment, hiring, and retaining personnel. The narrative shall demonstrate the offeror’s ability to continuously provide qualified personnel who have the required security clearances and possess the required education, experience, qualifications, and/or certifications while minimizing employee turnover. The Recruiting, Hiring and Retention Plan shall include at a minimum:

3.3.2.1. The offeror’s approach to recruiting, hiring, and retaining personnel. The plan shall address the offeror’s approach on how it will meet or exceed contract requirements while experiencing turnover of workforce.

3.3.2.2. The offeror’s historical ability to recruit, hire, and retain personnel.

3.3.2.3. Specific hiring considerations and retention concept(s) for the performance location (Oklahoma City, OK).

3.3.2.4. Candidate Assessment. Provide the offeror’s methodology that demonstrates an effective process to verify and validate qualifications against PWS requirements to ensure the submission of complete and accurate resumes and qualification packages for its workforce prior to the start of performance, and in a timely manner during employee turnover.

3.3 Section 4 - Glossary of Abbreviations and Acronyms. Include a glossary of abbreviations and acronyms used throughout the volume. The Glossary of Abbreviations and Acronyms does not count toward the Volume II page limitations.

4.0. VOLUME III – FACTOR 2: PAST PERFORMANCE. Volume III shall be prepared as follows:

Volume III Factor 2 -

Past Performance

Section 1: Table of Contents

3 pages per contract submitted in Section 2

Section 2: Recent and Relevant Past Performance Information Section 3: Subcontractor or Teaming Partner Consent and Client Authorization Section 4: Contractor Performance Assessment Reports Section 5: Glossary of Abbreviations and Acronyms

4.1. Section 1 – Table of Contents. A detailed table of contents delineating the subparagraphs within the volume. The Table of Contents does not count against the page limitations for Volume

III.

4.2. Section 2 – Recent and Relevant Past Performance Information. Submit a list of no more than three (3) recent and relevant contracts performed for Federal agencies or commercial customers as a prime contractor that demonstrates the ability to successfully perform the scope and breadth of the requirements as described in the PWS for this solicitation. Any past performance references in excess of the first three submitted will not be evaluated. If a teaming arrangement/Joint Venture is contemplated, include any relevant and recent performance information on previous teaming arrangements/Joint Ventures with the same partner or as this entity (CAGE). If this is a first time joint effort, each party to the arrangement must provide a list of no more than three (3) contracts each. The total page limit is three pages per contract.

4.2.1. Recency. Refer to Section C, paragraph 5.7 in Section M of the solicitation.

4.2.2. Relevancy. Refer to Section C, paragraphs 5.8 through 5.8.5 in Section M of the solicitation.

4.2.3. Reserved.

4.2.4. Submit the following information for each contract submitted for past performance evaluation:

4.2.4.1. Company/Division name

4.2.4.2. Description of Services Provided

4.2.4.3. Contracting Agency/Customer

4.2.4.4. Contract Number

4.2.4.5. Total Contract Dollar Value (of offeror’s portion if performing as a subcontractor)

4.2.4.6. Period of Performance

4.2.4.7. Verified, up-to-date name, address, e-mail address, telephone number of the Government evaluator, contracting officer or customer POC responsible for procuring your services.

4.2.4.8. If offeror has performed as a major subcontractor, include the specific services and percentage of the contract performed.

4.2.4.9. Explanation of how the scope of the referenced contract is relevant to the PWS in this solicitation. Include rationale supporting the offeror’s assertion of relevance and how it was determined that the work performed was the same or similar in nature, size, and complexity to the work specified in paragraph 4.2.2 above. Identify the number of aircrew support and staffing full time equivalent (FTE) positions recruited, qualified, managed, and retained, whether flight services were provided for Special Operations Forces (SOF), DoD or other Federal agencies, the number of sorties flown per month, and whether flight operations or training in actual aircraft occurred.

4.2.4.10. Comments regarding compliance with contract terms and conditions.

4.2.4.11. Comments regarding any known performance deemed unacceptable by the customer, or not in accordance with the contract terms and conditions, the resolution(s) implemented and results

4.2.4.12. If the offeror is submitting Past Performance information for, or in any way regarding, predecessor companies, key personnel who have relevant experience, or subcontractors that will perform major or critical aspects of the requirement, the offeror shall provide details as to what the predecessor companies, key personnel, or subcontractors participation was in the example past performance being provided, and precisely detail how the predecessor companies, key personnel, or subcontractors will perform in this effort.

4.2.5. If the offeror claims there is no past performance, notification of this fact must be included in Volume III, Past Performance.

4.3. Section 3 - Subcontractor or Teaming Partner Consent and Client Authorization.

4.3.1. Subcontractor or Teaming Partner Consent Letter (if required): Past performance information pertaining to a subcontractor or teaming partner cannot be disclosed by the prime contractor without the subcontractor’s/teaming partner’s consent. Provide with the proposal a letter from all subcontractors (Attachment 7) that will perform major or critical aspects of the requirement, consenting to the release of their past performance information to the prime contractor. The Subcontractor or Teaming Partner Consent Letter does not count toward the Volume III page limitations.

4.3.2. Client Authorization Letter (if required): Each offeror, subcontractor, teaming partner, and/or joint venture partner shall execute a Client Authorization Letter for commercial customers similar to Attachment 7 to this solicitation.

4.4. Section 4 - Contractor Performance Assessment Reports (CPARs). Offerors, including teaming partners or subcontractors proposed to perform 20% or more, shall submit a copy of their CPARs for their recent and relevant contracts submitted in paragraph 4.2 above. CPARS do not count toward the Volume III page limitations.

4.4.1. Adverse Past Performance Information. If adverse performance information exists (i.e.

Marginal or Unsatisfactory ratings), then the offeror shall submit with its proposal a response to the adverse performance review. It is the contractor’s responsibility to ensure it addressed adverse performance ratings on their recent and relevant performance record. Failure to do so may render the evaluation team to accept performance record as written in the CPARS.

4.5. Section 5 - Glossary of Abbreviations and Acronyms. Include a glossary of abbreviations and acronyms used throughout the volume. The Glossary of Abbreviations and Acronyms does not count toward the Volume III page limitations.

4.6. Past Performance Questionnaires. The Offeror shall send a copy of Attachment 8 – Past Performance Questionnaire (PPQ) to the Contracting and Technical POCs identified by the Offeror for each contract reference. When sending PPQs to each contract reference, the offeror should courtesy copy the Contracting Officers identified in paragraph A.2 above. If the contractor received a CPARS rating for the past performance effort being submitted, the contractor may attach a copy of the finalized CPARs in lieu of the PPQ. The POCs shall submit the PPQs by email directly to the Contracting Officers identified in Section A, paragraph 2 above.

4.6.1. Offerors shall ensure the PPQ is sent to allow sufficient time for the POCs to complete and provide back to this office prior to the closing date and time of this RFP. It is the Offeror’s responsibility to encourage the POCs to complete and submit the PPQ in a timely manner. If PPQs or CPARS assessments are not received by this office by the closing date, the Government is not obligated to make additional attempts to obtain the information.

4.6.2. Offerors shall indicate at Volume III, Past Performance, which technical/Contracting Officer POC the questionnaire was transmitted to and confirm that the questionnaire was received.

4.7. Early Past Performance Submission. To permit the past performance evaluation team to conduct its assessment more efficiently, offerors are requested to submit their past performance volume five

(5) calendar days prior to the solicitation closing date and time. Failure to submit past performance information early will not result in offeror disqualification. As the past performance questionnaires direct respondents to submit responses directly to the Contracting Officer, the past performance volume shall only include information up to Section 5 of Volume III as identified above.

5.0. VOLUME IV – FACTOR 3: PRICE. Volume IV shall be prepared as follows:

Volume IV – Factor 3 –

Price

Section 1: Cover Letter

No page limit Section 2: Table of Contents Section 3 Price Proposal Support Section 4: Price Proposal Worksheet (Attachment 9)

5.1. Offerors must ensure that pricing information is included in Volume IV. Do NOT include pricing information in Volumes II and III.

5.2. Section 1 – Cover Letter. Offerors shall include a single page cover letter with their price proposal signed by an authorized negotiator with signatory authority for the Offeror. The cover letter shall include:

5.2.1. Offeror’s CAGE Code.

5.2.2. Offeror’s DUNS and TIN/EIN number.

5.2.3. Offeror’s DCAA and/or DCMA points of contact to include: name, phone number, email address.

5.2.4. Name and DUNS number of any subcontractors anticipated to work under the contract.

5.3. Section 2 – Table of Contents. A detailed table of contents delineating the subparagraphs within the volume.

5.4. Section 3 - Price Proposal Support

5.4.1. The burden of proof for credibility of proposed costs/prices rests with the offeror. To support price reasonableness, offerors shall describe and provide the basis for their proposed direct and indirect rates and factors and provide narrative support for all elements. This includes all direct and indirect factors to include profit for the prime and all teaming members. Offerors must, if used, include the escalation factors used from the base year to all out year periods.

5.4.2. The narrative of the method to develop the basis of proposed prices shall be fully explained so that the government can readily identify how each computation was made. All indirect rates and factors should be fully explained as to the method and base of application.

Offerors are expected to use their customary formats and calculations consistent with their normal accounting practices to develop the burdened rates.

5.4.3. Certified Cost or Pricing Data. As this is a competitive acquisition with adequate price competition anticipated, certified cost or pricing data in accordance with FAR 15.403-1 is not required. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors. Further, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2.

If subcontractors are proposed, they shall provide the same information required for the prime contractor, unless otherwise noted. If only one offer is received, DFARS 252.215-7008 Only One Offer, will apply.

5.5. Section 4 - Price Proposal Worksheet, Attachment 9 to this solicitation.

5.5.1. Offerors shall complete and submit Attachment 9 – Price Proposal Worksheet. This worksheet calculates the offeror’s Proposed Price and Total Evaluated Price (TEP) (Monthly, Annual, and Total). Offerors shall use its proposed fully burdened labor rates, man hours, and Contractor Manpower Equivalents (CME) to assist in calculation of the TEP.

5.5.2. All unit and extended prices provided shall be rounded to no more than two positions after the decimal point. Extended prices must be divisible by the number of units proposed.

5.5.3. Missing or incomplete cost/pricing data may result in proposal rejection.

5.5.4. Offerors shall ensure their price proposal is consistent with the technical proposal in all respects since the price proposal will be used during the technical evaluation as an aid to determine the Offerors’ understanding of the requirements. Discrepancies may be viewed as a lack of understanding and may result in proposal rejection. Price proposals deemed excessively low and/or excessively high may be rejected.

7. Pre-proposal Conference/Site Visit. A pre-proposal site visit will not be conducted for this solicitation.

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