Section J Attachment 10 Instructions to Offerors 21 Oct 21.pdf

FA8630-22-R-4000

Section J, Attachment 10 Instructions to Offerors

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

FOR PREPARATION

1.0 Program Overview

The Air Force Security Assistance and Cooperation (AFSAC) Directorate located at Wright-

Patterson Air Force Base OH manages the Parts and Repair Ordering System (PROS) contract that provides Commercial Buying Services (CBS) for Non-Standard and Difficult to Support

Standard Items. The AFSAC PROS contract is a performance-based service acquisition providing supply, repair, and task order support services. This tri-service capable contract will support Air Force, Navy, and Army Foreign Military Sales (FMS) customers.

1.1 Budget/Funding Information

This is an Indefinite Delivery/Indefinite Quantity contract, including Firm Fixed Price

(FFP) and Cost Reimbursable (CR) Contract Line Item Numbers (CLINs). Contractor fill prices will be charged to a FFP CLIN; pass-through material costs (no profit allowed) will be charged to a CR CLIN. Funding will be provided for each individual Commercial

Transaction using FMS and Foreign Military Financing (FMF). The initial task order will be awarded for the competed price of the Study Proposed FFP at Section J, Attachment 5–

Pricing Matrix which will satisfy the guaranteed minimum amount.

2.0 General Instructions and Information

The Offeror's proposal must include all data and information requested by these Instructions to

Offerors (ITO) and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract

Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements, but rather 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 and experience and will base its evaluation on the information presented in the Offeror's proposal, along with information obtained from other

Government sources.

Elaborate brochures, documentation, detailed art work, or other embellishments are unnecessary and are not desired. Similarly, for oral presentations, elaborate productions are unnecessary and not desired.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain the single digital submission of all unsuccessful proposals.

2.1 Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to

Contracting Officer Michael Logue at michael.logue@us.af.mil.

mailto:michael.logue@us.af.mil

2.2 Debriefings

The CO will promptly notify Offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505.

Offerors excluded from the competitive range may request a pre-award debriefing or a post-award debriefing upon notification of exclusion from the competitive range. However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful Offerors of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.3 Discrepancies

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the Offeror is asking the CO to consider as related to the omission or error. The Offeror is reminded that the Government intends to award this effort based on the initial proposal, as received, but reserves the right to conduct discussions if necessary.

2.4 Electronic Reference Documents

All referenced documents for this solicitation are available on the official U.S. Government website for federal awards at sam.gov/. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.5 Communications

Exchanges of Controlled Unclassified Information (CUI)/Source Selection Information (SSI) between Government and Offerors will be controlled by the CO, utilizing the DoD Secure Access

File Exchange (DoD SAFE) to ensure proper encryption at https://safe.apps.mil/. If the Offeror needs to communicate with the CO regarding non-CUI/SSI information or to request a DoD

SAFE-generated access code and hyperlink to drop-off (upload) non-CUI/SSI information regarding this solicitation, send an email to the points of contact in paragraph 3.2 of this document.

3.0 Volume Organization

3.1 General

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 1. The contents of each proposal volume are described in the ITO paragraph as noted in the table below and should be clearly identified and labeled as such:

TABLE 1 – PROPOSAL ORGANIZATION BY VOLUME

Volume ITO Paragraph

Number Volume Title

Electronic

Submission Page Limit Size Limit

I 3.4 Executive Summary 1 2

8 GB/25

Files for II 3.5 Technical Factor 1 40 https://sam.gov/content/home

III 3.6 Past Performance 1 PPI Tool

Output

Total

Submission

IV 3.7 Price 1 No Limit

V 3.8 Contract Documentation 1 No Limit

3.1.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess pages will be redacted prior to sending to the evaluation team. Each page shall be counted except the following: Cover pages, tables of contents, cross-reference matrix, tabs, glossaries, and Small Business

Subcontracting Plan. Page limitations may be placed on responses to Evaluation Notices

(ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors.

3.1.2 Electronic Page Size and Format

A page is defined as the information contained in one electronic “page” meeting the requirements below. Page size shall be 8.5 x 11 inches, not including displays described in the following paragraph. Pages shall be single-spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12-point Times New Roman font. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom margins and ¾-inch side margins. Pages shall be numbered sequentially by volume.

These page size and format restrictions shall apply to EN responses.

Legible tables, charts, graphs, and figures (i.e., diagrams and schematics) shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size as formatted to print. Any pages exceeding 8.5 x 11 inches may only be used for large tables, charts, graphs, and figures, not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10-point.

3.1.3 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with minimum cross-referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The Offeror shall provide a Cross Reference Matrix, which is a tool that shows critical interrelationships and dependencies among Section L (Instructions to Offerors), Section M

(Evaluation Factors for Award), PWS, CLIN numbers, and CDRL references. All references shall contain the proposal volume, proposal page, and section number. The Cross Reference

Matrix helps ensure compliance with all evaluation criteria and proposal submittal requirements identified in the solicitation. If the Cross Reference Matrix conflicts with any other requirement, direction, or provision of this solicitation, the other requirement, direction or provision shall take precedence over the Cross Reference Matrix.

3.1.4 PWS Changes

Offerors shall provide proposed timelines in the PWS for all areas identified by an X with an asterisk (X*). Timeline inputs shall be made in the PWS and annotated with change bars.

Inputs shall also be consolidated in a spreadsheet with identifiers for PWS Page Number, PWS Paragraph Number, and Number of Days Proposed (X*). All inputs will be considered as part of the proposal evaluation.

Offerors shall provide requirements language in the PWS for all strengths being attempted as part of this solicitation. Offerors shall incorporate the requirements for meeting the proposed strength into the PWS and include change bars for all insertions. Inputs shall also be consolidated in a spreadsheet with identifiers for PWS Page Number, PWS Paragraph

Number, and Proposed Language. All inputs will be evaluated as part of the Technical

Volume, Paragraph 3.5.

3.1.5 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume.

3.1.6 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, as well as, an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

3.1.7 Electronic Offers

The Past Performance Volume shall be submitted via DoD SAFE https://safe.apps.mil/ no later than 5:00 PM EST on 26 November 2021. The remainder of the proposal shall be submitted via DoD SAFE https://safe.apps.mil/ no later than 5:00 PM EST on 09 December

2021. In order to submit via DoD SAFE, a drop-off request is required. In order to receive a

DoD SAFE drop-off, email both the primary and alternate points of contact listed in Section

3.2 no more than 14 days and no less than 3 days prior to proposal submittal date. DoD

SAFE is limited to a single drop-off with a limitation of 8 GB and 25 files. If proposal submission exceeds the DoD SAFE limitations additional submissions are allowed with email notification to both the primary and alternate points of contact listed in Section 3.2.

Electronic submissions should be clearly marked as to volume number, title, solicitation identification, the Offeror's name, and the Commercial and Government Entity (CAGE) code. The same identifying data shall be marked in the electronic document footer. Use separate files to permit rapid location of all volumes, including subfactors within each volume, exhibits, annexes, and attachments, if any. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. Identify "Controlled Unclassified

Information" and "Source Selection Information--See FAR 2.101 and FAR 3.104" on all distributed materials.

The electronic proposal shall be submitted in a format readable by Microsoft (MS) Office.

All MS-Excel attachments shall be submitted in the MS-Excel format (unaltered) in which they are provided by this Request for Proposal (RFP). The Offeror shall not include any formulas or links beyond what is included in the provided format. Macros or other https://safe.apps.mil/ https://safe.apps.mil/ embedded objects or features will be disabled as part of regular security precautions.

Electronic files must be unlocked in order to export the winning Offeror’s information into

Government contract writing systems.

3.2 Distribution

All Offeror proposals shall be addressed to both the Primary and Alternate POCs listed below and delivered via DoD SAFE according to the instructions in Section 3.1.6.

Primary:

Mr. Michael Logue AFLCMC/WFK michael.logue@us.af.mil

Alternate:

Ms. Sarah Harris AFLCMC/WFK sarah.harris.11@us.af.mil

Identify "Controlled Unclassified Information" and "Source Selection Information – FAR 2.101 and

FAR 3.104” on all distributed materials.

3.3 Bid and Proposal Costs

Offerors are advised that costs of any response to, or other costs incurred as a result of responding to this solicitation, are at the Offeror’s own risk. Any costs incurred in preparing a response to this solicitation may be attributable to bid and proposal (B&P) overhead costs, but may not be charged to any resulting awarded contract. B&P costs are indirect costs covered by CAS 420/FAR 31.205-

18.

3.4 Volume I – Executive Summary

3.4.1 Volume Organization

The Executive Summary Volume shall be organized according to the following general outline:

a. Cover page

b. Table of Contents: Include a master table of contents for the entire proposal.

c. Narrative Summary

d. Team Composition & Organizational Structure

e. List of Tables and Drawings

f. Glossary

3.4.2 Narrative Summary

The narrative summary shall be a concise summary of the entire proposal, to include addressing the significant risks, and highlighting any key or unique features, excluding price.

The salient features shall tie in with Section M evaluation factors and subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.4.3 Team Composition & Organizational Structure

The team composition shall only list the Offeror’s planned program team and description mailto:sarah.harris.11@us.af.mil of individual roles to support the requirements of the PWS. The organizational structure shall describe the Offeror’s business structure and hierarchy, to include division, business group, subsidiary company, etc. Specifically applicable to this solicitation, Offerors shall include any considerations for acquisition or merger activities with other companies, including companies that have acquired, been acquired by, or otherwise merged with other companies. Each Offeror is responsible for notifying the CO in writing of any changes to its corporate name, ownership, and/or organizational structure, or that of its subcontractors, joint venture partners, or other team members, which occur between submission of its offer under this RFP and contract award.

3.5 Volume II – Technical Volume

3.5.1 Technical

In the Technical Volume, Offerors shall address their technical solution for meeting or exceeding the Government’s minimum performance or capability requirements of each technical subfactor. The Technical Volume shall be organized according to the following general outline:

The Technical Volume shall be organized according to the following general outline:

a. Cover page

b. Table of Contents

c. List of Tables and Drawings

d. Glossary

e. Cross Reference Matrix

f. System Description

g. Risk Matrix

h. Risk Management

i. Subfactor 1.1: Gate, Approved Contractor Purchasing System

j. Subfactor 1.2: Information Technology

1. Measure of Merit 1: Contractor Technology Solution (CTS)

2. Measure of Merit 2: Technology Demonstration

3. Measure of Merit 3: Technology Solution Study and Implementation

k. Subfactor 1.3: Contract Competition

1. Measure of Merit 1: Vendor Management

2. Measure of Merit 2: Combating Obsolescence

3. Measure of Merit 3: Small Business Participation

3.5.2 Technical Risk

IAW the DoD Risk, Issue, and Opportunity (RIO) Management Guide for Defense

Acquisition Programs (January 2017) Section 3.3, the Offeror shall propose a Risk

Reporting Matrix identifying all “yellow” and “red” Technical Risks and Programmatic

Risks inherent in its specific approach considered to have the potential for disruption of schedule, degradation of performance, the need for increased Government oversight, and/or the likelihood of unsuccessful contract performance. Additionally, Government assessment of technical risk considers the risk associated with the technical approach to meeting the requirement which is manifested by the identification of weaknesses and/or significant weaknesses in Subfactors 1.2 and 1.3. IAW the DoD RIO Management Guide for Defense Acquisitions Programs Section 3, the Offerors shall describe the process for implementing proactive Technical Risk and Programmatic Risk management, to include, but not limited to:

3.5.2.1 An outline of the Offeror’s process for conducting on-going risk management planning, risk identification, analysis, risk monitoring, and risk handling on the program. The Offeror shall include a discussion of any tools or methodologies it uses throughout the risk management process and for risk assessments.

3.5.2.2 Provide rationale for all “yellow” and “red” risks inherent in the specific approach considered to have the potential for disruption of schedule, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: PWS), regardless of whether or not those requirements are identified as subfactors.

3.5.2.3 The Offeror shall propose realistic risk handling and mitigation strategies for each identified risk that will eliminate or reduce risk to an acceptable level.

Post-mitigation ratings shall be provided, along with the identification and classification of any new risks introduced by such risk mitigation and any proposed mitigation measures.

3.5.3 Strengths

Strengths will be contractually binding upon contract award. To incorporate strengths, the Offeror shall identify any strength it is attempting to obtain, substantiate any claim that the proposed approach is eligible for a strength, and make recommendations in the appropriate contractual document(s) to include Section J Attachments with change bars.

The Government reserves the right to assess and award strengths, with or without discussions, and determine the final contract language to incorporate strengths into the contract. Simply repeating Section L, Section M, or PWS language as substantiation will not justify the Government’s evaluation of an approach as a strength.

3.5.5 Subfactor 1.1: Gate, Approved Contractor Purchasing System

The Offeror shall provide documentation of an approved DCMA Final Determination Letter on the Contractor Purchasing System (CPS). DCMA approval shall occur prior to proposal submittal and be current. Subfactor 1.1 is a pass/fail gate used to determine whether an offeror’s proposal will be evaluated.

3.5.5.1 Measure of Merit 1: Gate

The Offeror shall provide the DCMA Final Determination Letter documenting

CPS approval.

3.5.6 Subfactor 1.2: Information Technology

The Offeror shall describe its approach to providing Information Technology.

3.5.6.1 Measure of Merit 1: Contractor Technology Solution (CTS)

The Offeror shall describe a CTS design and implementation approach for automated Commercial Transaction management serving as the official record for population of Digital Dashboards (DDs) and utilization of Independent Document

Exchanges (IDEs), ultimately empowering stakeholders through data-driven decision making with communication and transparency. Total system solution must meet the requirements of the contract at PWS 2.1.7 and reach full operational capability before any Commercial Transactions will process.

Offeror shall specifically identify which strength is being attempted and substantiate all claims of qualification for each strength under this Measure of

Merit. Offeror shall incorporate the requirements for meeting the proposed strength into the PWS and include change bars for all insertions.

3.5.6.2 Measure of Merit 2: Technology Demonstration

The Offeror shall present a CTS demonstration. The demonstration will be presented as an Oral Presentation. FAR 15.102 provides for the use of oral presentations to augment or substitute for portions of an Offeror's written proposal.

Please email Contract Specialist Sarah Harris at Sarah.Harris.11@us.af.mil to schedule your presentation and receive your Microsoft (MS) Teams CTS Oral

Presentation Link, not earlier than 2 weeks prior and not later than 1 week prior to proposal submission. All presentations will occur within the first full week following proposal submission. Upon receipt of CTS Oral Presentation link, it is advisable that the Offerors contact Sarah Harris to schedule and test the link with the PMO to ensure all Offeror attendees can connect via MS Teams and that audio, video, and screen sharing is functional. Pre-recorded presentations will not be accepted.

Presentations must be live, per FAR 15.102(a). No presentation may exceed 1 hour.

The Government will not hold discussions or entertain questions and answers during the presentation. For the Government record, this demonstration will be recorded. The Offeror is encouraged to capture the presentation independently to mitigate any technology issues. The Offeror's independent recording may be requested by the Government.

The presentation shall demonstrate and explicitly identify existing capabilities that meet CTS requirements in accordance with PWS 2.1.7, a conceptual approach to meeting the requirements, or a combination. The Offeror shall, at a minimum, present a walk-through of the life-cycle of a Commercial

Transaction, DD capabilities, IDE capabilities, and automation opportunities

(not limited to CDRLs, Contract File Generation, or Service Summaries).

The Offeror shall deliver an electronic submission of all oral presentation briefing materials with the proposal submittal. These materials will be considered in the

Government's evaluation of the proposal. However, only the materials included/briefed as part of the oral presentation will be evaluated and any material mailto:Sarah.Harris.11@us.af.mil that is not included/briefed during the established time limit will not be considered.

These materials shall also include a brief narrative and detail in writing any proposed strengths specifically identified during the oral presentation. Offerors shall specifically identify which strength is being attempted and substantiate all claims of qualification for each strength proposed as part of the Oral Presentation. Offerors shall incorporate the requirements for meeting the proposed strength into the PWS and include change bars for all insertions.

3.5.6.3 Measure of Merit 3: Technology Solution Study and Implementation

The Offeror shall deliver a Firm Fixed Price (FFP) CTS proposal for accomplishing the CTS study. Offerors shall submit a Project Planning Chart

(PPC), PWS 2.1.1 which captures the core activities and processes necessary to successfully execute the CTS study and final implementation to include major milestones, such as implementation, testing and acceptance, full operational capability, and all associated CDRL deliverables. The starting date shall be contract award. The intent of this section is to obtain an understanding of the proposed approach, providing the Government confidence that the study and implementation are structured to be executable. Offerors shall deliver their PPC, according to DI-MGMT-80507 (https://quicksearch.dla.mil/qsSearch.aspx). The proposal and PPC shall address the following items of particular importance to the

Government:

1. Interfacing technologies - plan and schedule of system testing and

Offeror's CTS deployment. Includes incremental testing, implementation milestones, and test results.

2. System security, hardware/software, and sustainment through life of contract - specifies system capacity, transaction processing, and access to on-line systems.

Offerors shall specifically identify which strength is being attempted and substantiate all claims of qualification for each strength under this Measure of

Merit. Offeror shall incorporate the requirements for meeting the proposed strength into the PWS and include change bars for all insertions.

3.5.7 Subfactor 1.3: Contract Competition

3.5.7.1 Measure of Merit 1: Vendor Management

The Offeror’s approach shall address vendor management tools utilized to provide competition for the types of supply, repair, and task order support required by the

PWS. The Offeror shall address vendor compliance with sourcing restrictions, specifically identification of and awarding to qualified sources, to include OEM traceability. The Offeror shall specifically address processes for Safety of Flight

(SOF), Critical Safety Item (CSI), and Engineering Support Authority (ESA) approved sourcing.

Offeror shall specifically identify which strength is being attempted and substantiate all claims of qualification for each strength under this Measure of

Merit. Offeror shall incorporate the requirements for meeting the proposed strength into the PWS and include change bars for all insertions.

https://quicksearch.dla.mil/qsSearch.aspx

3.5.7.2 Measure of Merit 2: Combating Obsolescence

The Offeror’s approach shall demonstrate obsolescence identification, reporting, and forecasting. The Offeror’s approach shall include examples to address the challenges of obsolescence with today’s technology. The Offeror shall also address any partnering relationships for technology solutions. The Offeror shall address First Article Testing (FAT) for any proposed technology solution to satisfy OEM traceability.

Offeror shall specifically identify which strength is being attempted and substantiate all claims of qualification for each strength under this Measure of

Merit. Offeror shall incorporate the requirements for meeting the proposed strength into the PWS and include change bars for all insertions.

3.5.7.3 Measure of Merit 3: Small Business Participation

The Offeror’s approach shall demonstrate compliance with the requirements at FAR

52.219-8, Utilization of Small Business Concerns, and FAR 52.219-9, Small

Business Subcontracting Plan-Alternate II. The Offeror shall ensure opportunities for small business participation throughout the life of the contract. The Offeror shall describe its current and planned initiatives to assist, promote, and compete all categories of small businesses on the PROS VI program, in accordance with PWS

2.13.

NOTE: Both large and small businesses, regardless of whether or not they are required to submit a Small Business Subcontracting Plan IAW with FAR 52.219-9-

Alternate II, or DFARS 252.219-7003, shall be required to submit opportunities for small business participation as part of their proposal.

3.6 Volume III - Past Performance

3.6.1 General

Each Offeror shall submit a Past Performance Volume with its proposal. This information is required for the prime Offeror. The prime Offeror may submit past performance information

(PPI) for any subcontractor regardless of proposed contract percentage performed, however, PPI is required (to the extent such information is available) for all significant subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 10 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the Offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the evaluation of past performance. Offerors shall utilize the PPI Tool

(See Attachment L-3 and L-4) to identify their Past Performance Citations and PPI.

Along with the information required in this section, the Offeror shall submit a consent letter signed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse PPI to the Offeror so the Offeror can respond to such information (see

Section 3.4). For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror's performance.

Prime Offerors may submit up to three (3) past performance citations, not including subcontractor citations. Offeror may submit up to two (2) past performance citations for each significant or critical subcontractor. A subcontractor is deemed to be a significant subcontractor when it is proposed to perform more than 10% of the work (based on total contract value) on a contract. A subcontractor is deemed to be critical if it performs aspects of the effort the Offeror considers critical to overall successful performance. The

Government will consider performance that has occurred during the past three (3) years from the date of the issuance of this solicitation, or is ongoing with at least six (6) months of performance elapsed. If no relevant past or present performance information exists, do not submit a Volume III. Instead, explain in the Executive Summary that no relevant past performance exists.

3.6.2 Format

This Volume shall provide recent and relevant performance citations in the format requested below:

1. PPI (see paragraph 3.6.3 below)

2. Relevancy Discussion (see paragraph 3.6.4 below)

3. Organizational Structure Change History (see paragraph 3.6.5 below)

4. Consent Letters. Consent letters executed by each joint venture partner and/or significant or critical subcontractor(s), authorizing release of adverse PPI so the

Offeror can respond to such information (see paragraph 3.6.7 below).

5. Client Authorization Letters. Client authorization letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the Offeror’s performance.

6. List of Questionnaire Recipients

3.6.3 Past Performance Information

Offerors shall utilize the PPI Tool (See Attachment L-3 and L-4) to identify their PPI in the

Past Performance Volume.

3.6.4 Relevant Contracts

For each citation, include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining Recency and

Relevancy, see Section M, Paragraph 2.6, Past Performance. Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, because the problems encountered may have been on a more complex program, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the Offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an

Offeror has overcome past problems is required. Categorize the relevant information into the specific technical subfactors used to evaluate the proposal.

3.6.5 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc.

In many cases, these changes have taken place during the time of performance of relevant present or past efforts or between conclusion of recent past efforts and this source selection.

As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a

“roadmap” describing all such changes in the organization of your company. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider PPI provided by other sources as well as that provided by the Offeror(s), your “roadmap” should be both specifically applicable to the efforts you identify and general enough to apply to efforts about which the Government receives information from other sources. Include Commercial and Government Entity (CAGE) codes for any predecessor companies to facilitate Government research.

3.6.6 Past Performance Questionnaires

The Government requests the Offeror send out Past Performance Questionnaires, Attachment L- 3 and L-4, for each citation to at least two Government points of contact. The

Offeror shall send a standard transmittal letter to request the points of contact complete an unclassified Past Performance Questionnaire and submit via email five (5) working days after release of this solicitation. Preferred points of contact are, in order of descending preference: program manager, procurement contracting officer, technical or engineering lead. Completed questionnaires should be submitted directly to the Primary and Alternate

POCs listed in Section L 3.2, no later than 3:00 p.m. Eastern Time on 26 November 2021.

The Offeror is solely responsible for ensuring that questionnaires are submitted in time for use in the evaluation process, and shall make every effort to achieve this objective. Once the

Past Performance Questionnaires are completed, the information contained therein shall be considered sensitive and shall not be released to the Offeror. The Offeror shall verify the

POC information is current and valid. The evaluation team may conduct follow-up discussions with any of the POCs and reserves the right to send out additional questionnaires.

3.6.7 Consent

3.6.7.1 Written Consent

PPI submitted concerning subcontractors and teaming partners, if proposed, cannot be disclosed to a private party without the subcontractor’s or teaming partner’s written consent. Because the Offeror is a private party, the Government requires consent before disclosing subcontractor/teaming partner PPI to the

Offeror during exchanges.

3.6.7.2 Consent Letter

To assist the Government evaluators in assessing past performance relevancy and confidence, request the consent letter (if any) be completed by the major subcontractor/teaming partners identified in your proposal. The written consent(s) should be submitted as part of the Past Performance Volume. Should the Offeror not submit consent, the Government will only discuss PPI directly with the prospective subcontractor or teaming partner that is being reviewed. If there is a problem with the proposed subcontractor’s or teaming partner’s past performance, the Offeror can be notified of a problem, but no details may be discussed without the subcontractor’s/teaming partner’s permission.

3.6.8 Contractor Performance Assessment Reports (CPARs)

Offerors shall identify the existence of PPI in the Past Performance Volume. If this information is located outside the CPAR system, Offerors shall indicate where that information exists and are encouraged to provide additional information regarding the work effort to clearly describe how it relates to the PWS requirements. Also include information on cited contracts that has been captured in any databases other than those used by DoD or other federal agencies. If a CPAR or other evaluation form has been accomplished on the

Offeror’s existing work, but has not yet been posted to an automated system, the Offeror is requested to advise the CO and provide a point of contact and phone number from which the information may be obtained. This information should be provided to the CO at the same time the Past Performance Volume is submitted.

3.7 Volume IV – Price Volume

3.7.1 General Instructions

This section is to assist Offerors in submitting data other than certified cost or pricing data required to evaluate the reasonableness of their proposed price. Compliance with these instructions is mandatory and failure to comply may result in rejection of the proposal. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price Volume. Data beyond what is required by this instruction shall not be submitted, unless considered essential to document or support the Offeror’s price position. Offers should be sufficiently detailed to demonstrate their reasonableness and balance. The burden of proof for credibility of proposed prices rests with the Offeror.

No pricing data or information shall be included in any other volume, including cover letters, unless specifically requested by the Government in the respective volume. If price information is included elsewhere in the documentation, the proposal may be deemed unacceptable and the proposal may not be evaluated. The Offeror shall comply with the intent of the pricing instructions in supplying information that is current, timely, and in full support of the proposal. Exceptions or deviations will not be accepted. The instructions for preparation of the content of the Price Volume shall not take precedence over requirements of other clauses of the contract, Public Law, or the FAR, as supplemented.

3.7.2 Price Data

The CO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the CO will review this determination and if, in the CO’s opinion, adequate price competition exists, no additional cost information will be requested and certification under FAR 15.406-2 will not be required. IAW FAR

15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the

Offeror shall be required to submit cost or pricing data.

3.7.2.1 Rounding

All dollar amounts provided shall be rounded to the nearest dollar.

3.7.2.2 Volume Organization

The Offeror shall submit a proposal to capture prices for all contract line items listed in the Section J, Attachment 5–Pricing Matrix. The Offeror shall not tamper with the provided rows, columns or formulas or add any information to required worksheets, other than what is requested in the Pricing Matrix Instructions. The estimate quantities in the Pricing Matrix are based on actuals since the future quantities are unknown at this time. The Offeror shall develop and input a proposed fill price for each criterion highlighted yellow in the spreadsheets. The total price for the basic and option years of the contract will be automatically calculated based upon the estimated historical quantities and fill prices. Instructions for completing the fill price Pricing Matrix are located within Section J, Attachment 5–Pricing Matrix, and

Instructions Worksheet. The Firm Fixed Price (FFP) Fill Fees and Study proposed in Attachment 5–Pricing Matrix will be contractually binding.

CLIN MATRIX

FIRM FIXED PRICE CLINs:

Fill 0001 – 5001

Cancellation Fill 0002 – 5002

Research / Price and Availability Fill 0003 – 5003

Commercial Transactions 0004 – 5004

Task Orders 0005 – 5005

Data (NSP) 0006 – 5006

Objective Performance Incentive 0007 – 5007

The Offeror shall propose price for the Initial Task Order, FA8630-22-F-4001 - CTS

Study Implementation at PWS 1.2.10 and PWS 2.1.1 IAW Section J, Attachment 5–

Pricing Matrix.

The Offeror shall not propose fill prices for FFP CLINs: Task Orders CLINs 0005 –

5005. The Task Order price will be competed and negotiated at the time of need. The

Government-estimated yearly amounts for these CLINs will be placed on contract and will not be evaluated as part of the Total Evaluated Price (TEP).

The Offeror shall not propose prices for the following CLINs: Commercial

Transactions CLINs 0004 – 5004, Task Orders CLINs 0005 – 5005, Objective

Performance Incentive CLINs 0007 - 5007. The Government-estimated yearly amounts for these CLINs will be placed on contract and will not be evaluated as part of the TEP.

The Offeror shall not propose prices for the Data CLINs 0006 – 5006, as this is a

Not-Separately-Priced (NSP) CLIN that will be utilized for Contract Data

Requirements List (CDRL) reporting.

3.8 Volume V - Contract Documentation

3.8.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the USG for preparing the contract document and supporting file. The Offeror's proposal shall include a signed copy of the Model Contract (SF 33) and any completed attachments from Sections A through J; Section K is contained in the System for Award Management (SAM).

3.8.2 Section A – Solicitation/Contract Form

Completion of Blocks 13, 14, 15, 16, 17, and 18 and signature and date for Blocks 17 and 18 of the SF33. Signature by the Offeror on the SF33 constitutes an offer, which the

Government may accept. The "original" proposal should be clearly marked under separate cover.

3.8.3 Section B – Supplies or Services and Prices

No special instructions. Do not enter prices into Section B, as they will not be evaluated.

Price evaluation will be accomplished via Section J, Attachment 5 – Price Matrix.

3.8.4 Section C – Description/Specs/Work Statement

Performance Work Statement will be a Section J attachment.

3.8.5 Section F – Deliveries or Performance

No special instructions.

3.8.6 Section G – Contract Administrative Data

No special instructions.

3.8.7 Section H – Special Contract Requirements

No special instructions.

3.8.8 Section I – Contract Clauses

No special instructions.

3.8.9 Section J – Attachments

The Offeror shall complete and/or provide the following documents to the USG:

Attachment 3: Small Business Subcontracting Plan

Attachment 5: Pricing Matrix

Attachment 8: Section K, FAR 52.204-24, Representation Regarding Certain

Telecommunications and Video Surveillance Services or Equipment

The USG will provide the following documents to the Offeror:

Exhibit A: DD Form 1423 Contract Data Requirements List (CDRL)

Attachment 1: Performance Work Statement (PWS)

Attachment 2: Reserved (DD Form 254 removed)

Attachment 4: Supply Discrepancy Report (SDR) Process

Attachment 6: Specifications and Standards

Attachment 7: Wage Rate Determination

Attachment 9: AFLCMC/WFK SECTION H PROS VI OBJECTIVE

PERFORMANCE INCENTIVE (OPI) (OCT 2021)

Attachment 10: AFLCMC/WFK PROS VI Instructions to Offerors (OCT 2021)

Attachment 11: AFLCMC/WFK PROS VI Evaluation Criteria (OCT 2021)

Attachment 12: DFARS 252.223-7999 Ensuring Adequate COVID-19 Safety

Protocols for Federal Contractors (Deviation 2021-O0009)

3.8.10 Section K – Representations, Certifications, and other Statements of

Offerors

Offer must provide completed representations, certifications, acknowledgments and statements in System for Award Management (SAM) at www.sam.gov.

3.8.11 Section L – Attachments

The Offeror shall complete and/or provide the following documents to the USG:

Attachment 1: Cross Reference Matrix

Attachment 2: Subcontractor/Teaming Partner Consent Letter for the Release of Past and Present Performance Information to the Prime Contractor (If applicable)

Attachment 3: Client Authorization Letter (If applicable)

The USG will provide the following documents to the Offeror:

Attachment 4: Past Performance Information Tool Instructions

Attachment 5: Past Performance Questionnaire

3.8.12 Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, including, but not limited to, terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 2. The Government reserves the right to reject any exceptions taken to the proposal requirements and consider such offers unacceptable.

TABLE 2 - SOLICITATION EXCEPTIONS

Solicitation

Document

Page/

Paragraph

Requirement/

Portion Rationale

PWS, Model Contract, ITO, etc.

Applicable

Page and

Paragraph

Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement cannot/will not be met

3.9 Other Information Required

3.9.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact who is authorized to make decisions with respect to the proposal, negotiate with the

Government, and obligate the company contractually. Also provide the name, title and telephone number of the CEO, Division President, and/or Vice President.

3.9.2 Government Offices

The contract will be administered locally by the following:

Mr. Michael Logue, Procurement Contracting

Officer

Bldg. 209, 5454 Buckner Road

Wright-Patterson AFB, OH 45433-5337 michael.logue@us.af.mil

937-656-2684

Payments will be made by:

Defense Finance and Accounting Service (DFAS)-

CO/JAK 3390 East Broad Street, Bldg. 21

Columbus, Ohio 43213

3.9.3 Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code; CAGE code; Data

Universal Numbering System (DUNS) number; Tax Identification Number (TIN); size of business (large or small) under North American Industry Classification System code

(NAICS) 541614; 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.

mailto:michael.logue@us.af.mil