Draft Attch 01 - YR 52.212-1 Addendum 14 Aug 2021.pdf

Attachment 1

14 August 2021 Page 1 of 19

ADDENDUM TO FAR 52.212-1, INSTRUCTIONS TO OFFERORS-COMMERCIAL

ITEMS

1.0 GENERAL INSTRUCTION/INFORMATION

1.1 General Information

This section of the instructions to offerors (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror’s proposal must include all data and information requested by the ITO and submitted IAW these instructions.

Any offeror who submits an incomplete package may be considered ineligible for award. The offer shall be compliant with the requirements as stated in the Request for Proposal (RFP), the Performance Work Statement for Air Force Reserve Command Yellow Ribbon Reintegration Program Event Planner Services (PWS) (RFP Attch 03 – FINAL YRRP Event Planning Services PWS 29 Apr 21), PWS Attachments (RFP Attchs 04 -07), Contract Data Requirements Lists (CDRLs) (RFP Attchs 09 – 17), and the RFP attachments. Nonconformance with the instructions provided in the ITO may result in an unfavorable proposal evaluation or rejection of the proposal in its entirety.

The CO has determined there is a high probability of adequate price competition in this proposed effort so offerors are advised to submit their best pricing and technical information up-front.

Multiple offers will not be accepted. Upon examination of the initial offers, the CO will determine if adequate price competition exists, no additional cost information will be requested and certification under FAR 15.406-2, Certificate of Current Cost or Pricing Data, will not be required.

However, if at any time during this competition the CO determines that adequate price competition no longer exists, offerors may be required to submit information, other than certified cost or pricing data, to the extent necessary for the CO to determine the reasonableness and affordability of the price.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and substantiation of stated claims. The proposal should 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 capabilities and experience, and will base its evaluation on the information presented in the offeror’s proposal. Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

Proposals must demonstrate a comprehensive understanding of the nature and scope of work required. The Government will not search for data to cure problems or address inconsistencies in proposals. Each offeror shall submit a complete proposal in accordance with these instructions.

The Government may consider any failure to comply with these instructions to be indicative of what could be expected from the offeror during performance and may consider it a failure of the proposal. General statements (i.e. "will comply," "noted and understood," "in accordance with industry best practices/standards,") without supporting narrative are not acceptable. Cursory responses or responses that merely reiterate or paraphrase the language contained within the PWS does not satisfy the requirements of the solicitation.

1138287579C Draft

14 August 2021 Page 2 of 19

1.2 Acceptance Period

The Government requires a minimum acceptance period of 120 calendar days from the date of receipt of offers; however, offeror’s may specify an acceptance period exceeding the Government’s minimum requirement. The offeror’s proposal must affirmatively state an acceptance period equal to, or greater than, 120 calendar days.

1.3 Retainability/Disposal

IAW Federal Acquisition Regulations (FAR) Subpart 4.8, Government Contract Files, the Government will retain an electronic copy (e-copy) of all proposals. Unless an offeror requests otherwise, the Government will destroy all hard copies. No destruction certificate will be provided.

1.4 Government Point of Contact

The HQ AFRC Contracting Officer (CO) is the sole point of contact for this proposed effort. Any questions or concerns pertaining to the Request for Proposal (RFP), or any of its attachments shall be submitted in writing to the CO listed below. The deadline for any questions, concerns, and/or requests for clarification is five (5) calendar days after the RFP release. The Government may or may not respond to submissions past the deadline. Contact information is as follows:

Ms. Rachel May, Contracting Officer (CO) E-mail: rachel.may.1@us.af.mil

1.5 Debriefings

The CO will promptly notify offerors of any decision to exclude them from the competition or competitive range if a competitive range is established; whereupon, the offeror may request and receive a debriefing in accordance with FAR 15.505, Pre-award Debriefing of offerors. Offerors excluded from the competition or competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing.

(NOTE: Offerors excluded from the competitive range are entitled to no more than one (1) debriefing for each proposal.) The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506, Post-award Debriefing of offerors. 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, Pre-award Debriefing of Offerors, or FAR 15.506, Post-award Debriefing of Offerors, as applicable.

1.6 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. The notification shall include supporting rationale and remedies the offeror requests the CO to consider as related to the omission or error.

14 August 2021 Page 3 of 19

1.7 Electronic Reference Documents

All referenced documents for this solicitation are available on the SAM website at https://sam.gov/.

Potential offerors are encouraged to “follow,” subscribe for email notifications, and monitor SAM for updates to the website for this RFP.

1.8 Oral Presentation

The Government will not utilize nor consider oral presentations for this solicitation.

1.9 Exchanges with Offerors

Exchanges of source selection information after submission of initial proposal packages between the Government and offerors will be controlled by the CO. Email may be used to transmit such information to offerors and must include “Source Selection Information – See FAR 2.101 & 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via the DoD SAFE website as described in paragraph 1.13 of these instructions. When submitting source selection information via email, file suppression utilities to include, but not limited to zip files, will not be accepted.

1.10 Amendments to the Solicitation

If this RFP is amended, all terms and conditions that are not amended remain unchanged and are in full force and effect. Offerors shall acknowledge receipt of any amendment and provide confirmation upon submission of the offeror’s proposal.

1.11 Submission, Modification, Revision, and Withdrawal of Proposals

Proposals, modifications, and revisions of proposals as well as withdrawal of proposals shall be submitted electronically in DoD SAFE to the CO IAW with the DoD SAFE procedures in paragraph 1.13 of these instruction.

1.12 Organization/Number of Copies/Page Limits

1.12.1 Proposal Organization

The offeror shall prepare the proposal as set forth in Table 1 – Proposal Organization. The titles and contents of the volumes shall be organized as presented in Table 1 – Proposal Organization, and shall be within the specified page limits.

Table 1 Proposal Organization

14 August 2021 Page 4 of 19

VOLUME

ITO Para Number

TITLE PAGE LIMITS

I 2.0 TECHNICAL PROPOSAL

2.3 Table of Contents No Limit

2.4 Team List No Limit

2.5 Sub-factor 1: Technical Approach

2.6 Sub-factor 2: Program Management and Staffing Approach

2.7 Glossary of Abbreviations and Acronyms No Limit

II 3.0 PAST PERFORMANCE

3.4 Table of Contents No Limit

3.5 Recency and Relevancy No Limit

3.6 Glossary of Abbreviations and Acronyms No Limit

III 4.0 PRICE

4.5 Table of Contents No Limit

4.6 Team List No Limit

4.7 CLIN Pricing Schedule (Attch 08) No Limit

4.8 Glossary of Abbreviations and Acronyms No Limit

IV 5.0 SMALL BUSINESS CONCERN UTILIZATION PLAN

5.2 Table of Contents No Limit

5.3 Small Business Concern Utilization Plan No Limit

5.4 Glossary of Abbreviations and Acronyms No Limit

V 6.0 CONTRACT DOCUMENTATION No Limit

6.2 Table of Contents No Limit

6.3 SF 1449 and Amendments No Limit

6.4 Cross Reference Matrix No Limit

6.5 Representations and Certifications No Limit

6.6 Exceptions to Solicitation Requirements No Limit

6.7 Other Information Required No Limit

6.8 Glossary of Abbreviations and Acronyms No Limit

1.12.2 Page Limitation

Refer to Table 1 – Proposal Organization for page limitations. Page limitations shall be treated as maximums. If exceeded, the excess pages occurring after the page limit will be removed and will not be considered. Page limitations may also be placed on responses to Evaluation Notices (EN).

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

14 August 2021 Page 5 of 19 the offerors. Each page shall be counted except the following: title pages, tabs, indexes, and those noted in the proposal organization table as “No Limit”.

1.12.3 Page Size and Format

A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two (2) pages. Page size shall be 8.5” x 11,” not including foldouts. Page line spacing shall be no less than single spacing. Except for the reproduced sections of the RFP document, the font shall be Times New Roman and the text size shall be no less than 12-point 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” margins on the top and bottom and ¾” side margins. Pages shall be numbered sequentially by volume. The page size and format restrictions shall apply to responses to ENs. These limitations shall apply to all electronic copies. Any page(s) that do not meet this requirement will not be considered in the evaluation.

1.12.4 Tables, Charts, Graphs, Figures

Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated and shall not exceed 11” x 17” in size. Foldout pages shall fold entirely within the volume, and count as one page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. For the Technical Volume, text intended for evaluation within all tables, charts, graphs, and figures, to include imbedded images, shall be no less than Times New Roman 8-point font. These limitations shall apply to all electronic copies. Any text within tables, charts, graphs, and figures that do not meet this requirement will not be considered in the evaluation.

1.12.5 Title Page

The title page of each volume must include the solicitation number, volume number, title, version number, name of the offeror, and the offeror’s email address.

1.12.6 Table of Contents

Each proposal volume shall contain a more detailed table of contents to delineate the subparagraphs within that proposal volume. Tab indexing shall be used to identify sections.

Include an indexed list of tables, charts, graphs, figures, and drawings, as applicable. Table of contents pages do not count against the page limitations for their respective volumes.

1.12.7 Team List

A team list of the primary points of contact (POCs) of the offeror, significant subcontractors, teaming partners, and/or mentor-protégé partners shall be submitted in the Technical Volume, and the Price Volume. The list shall include the POC’s full name (first and last), street address, telephone number, facsimile number, and email address. The team list pages do not count against the page limitations for their respective volumes.

14 August 2021 Page 6 of 19

1.12.8 Glossary of Abbreviations and Acronyms

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

1.12.9 Cross-Referencing

Offerors shall write each volume on a stand-alone basis so that the Government may evaluate its contents without 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 when its use would conserve space without impairing clarity. Any instances of cross-referencing within a proposal volume shall include the page number and paragraph number.

1.12.10 Price Information

All pricing information shall be addressed ONLY in the Price Volume and the Contract Documentation Volume of the proposal.

1.13 Electronic (DOD SAFE) Offers

The offeror shall submit an electronic copy of the complete proposal via DoD SAFE (Secure Access File Exchange)** at (https://safe.apps.mil), consisting of all five (5) proposal volumes.

The volumes shall contain all of the Table 1 Proposal Organization required information. The electronic copy shall not be linked to any other document. The electronic copy shall be clearly identified in the “Notes to Recipient” box as to the offeror’s name, solicitation title, and solicitation number. The format shall be Microsoft Office compatible. The electronic copy will be used for proposal evaluation. Offerors shall ensure electronic copy is virus-free. Sound or video (e.g.

MPEG) files shall not be embedded into the proposal files.

**For DoD SAFE delivery method, use a Chrome or Firefox browser, visit the help section of the site early, contact the CO for the Drop-off Request code. Do not wait until the last minute to contact the CO for the Drop-off Request code. It is recommended that you request the Drop-off Request code at least seven (7) calendar days prior to the proposal due date. Drop-off Request codes are valid for up to 14 days; however, submissions uploaded into DoD SAFE after the proposal due date and time will not be accepted. Note that the Drop-off Request code is for a one time use only. If a second Drop-off code is needed, you will need to request a second code before the proposal due date and time. Do not wait until the day proposals are due to request a Drop-off Request code.

1.13.1 Electronic Copy

The electronic copy shall follow the guidelines at paragraph 1.12.3 and 1.12.4 of these instructions.

For the electronic (DoD SAFE) copy, use separate electronic files to permit rapid location of all portions of the proposal, including sub-factors, exhibits, annexes, and attachments. Each file name shall include the volume number and title IAW Table 1, Proposal Organization. The offeror shall

14 August 2021 Page 7 of 19 submit Volumes I through V in electronic format. The electronic (DOD SAFE) copy of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word, MS Office Excel, MS Office Project, and MS Office Power Point.

1.13.2 Conflicting Proposals

In case of a conflict between multiple copies of the proposal/individual files/documents being uploaded into DoD SAFE, the latest date and time stamped electronic copy version will take precedence. Proposals submitted via hand or postal (U.S. Postal Service, United Parcel Service (UPS), FedEx) delivery, or via email or facsimile will not be accepted.

1.14 Distribution

Submit electronic (DoD SAFE) proposals to the email address below:

Ms. Rachel May, Contracting Officer (CO) E-mail: rachel.may.1@us.af.mil

2.0 FACTOR 1 – TECHNICAL PROPOSAL (VOLUME I)

2.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Offerors proposals must address the requirements listed below to allow the Government to evaluate the proposal in accordance with the technical sub-factors as described in the Addendum to FAR 52.212-2, Evaluation – Commercial Items (RFP Attch 02 YR 52.212-2 Addendum 24 May 2021).

Factor 1: Technical

Sub-factor 1: Technical Approach Sub-factor 2: Program Management and Staffing Approach

In the Technical Volume, address the proposed approach and technical solution to meeting the requirements of each Technical sub-factor as well as any technical risk as discussed in paragraph

2.2 of these instructions. The Technical Volume is comprised of several sections to include the two (2) sub-factors. All requirements specified in the solicitation are mandatory. Any information provided that is not specifically requested as part of the sub-factors will not be evaluated or considered in the award determination. By submitting a proposal, offerors are representing their company will perform all the requirements specified in the solicitation.

2.2 Format and Specific Content

2.2.1 In the Technical Volume, offerors shall address their proposed approach and technical solution for meeting the Government’s minimum performance or capability requirements of each technical sub-factor, as well as the following:

14 August 2021 Page 8 of 19

2.2.1.1 As part of the response to each sub-factor, state all assumptions used to prepare the response, if applicable.

2.2.1.2 As part of the response to each sub-factor, address technical risk associated with those aspects of the offerors proposed technical approach that is 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 contract requirements (i.e. PWS attachments, workload, referenced publications, etc.), whether or not those requirements are identified as sub-factors. Propose a realistic “work-around” or mitigations for identified risks that will eliminate or reduce risk to an acceptable level.

2.2.2 The following paragraphs provide instructions for each sub-factor.

2.2.3 Volume Organization

The Technical Volume shall be organized following this general outline:

Section 1: Table of Contents Section 2: Team List Section 3: Sub-factor 1: Technical Approach Section 4: Sub-factor 2: Program Management and Staffing Approach Section 5: Glossary of Abbreviations and Acronyms

2.3 Section 1: Table of Contents

The offeror’s proposal shall include a more detailed table of contents to delineate the subparagraphs within that proposal volume. Tab indexing shall be used to identify sections.

Include an indexed list of tables, charts, graphs, figures, and drawings, as applicable.

2.4 Section 2: Team List

A team list of the primary POCs of the offeror, significant subcontractors, teaming partners, and/or mentor-protégé partners shall be submitted in the Technical Volume. The list shall include the POC’s full name (first and last), street address, telephone number, facsimile number, and email address.

2.5 Section 3: Sub-factor 1: Technical Approach This sub-factor assesses the offeror’s over-arching strategy that demonstrates a clear understanding of the PWS requirements.

2.5.1 The offeror shall propose a technical approach. The approach shall explain how the offeror intends to accomplish the required work to be performed and employ properly trained employees to accomplish all requirements within the PWS. At a minimum, the proposed approach shall address:

a) The offeror’s knowledge and abilities of In-Person or Hybrid Event planning (PWS 1.4- 1.4.1), virtual event planning (PWS 1.5), business understanding, technology planning, and Yellow Ribbon event planning (if any).

14 August 2021 Page 9 of 19

b) The offeror shall provide a defined process and risk assessment demonstrating the capability to find event venue for 1000 attendee event that meet the requirements. (PWS 1.4.1.2, 1.4.2-1.4.13 and PWS Attachment 3)

c) The offeror shall provide a defined process and risk assessment demonstrating the capability to plan and execute multiple events that occur on the same dates in separate locations. (PWS 1.4-1.4.1, 1.4.1.4 and PWS Attachment 3)

d) The offeror shall provide a defined process and risk assessment that includes live streaming room setup diagrams, equipment and personnel support demonstrating the capability to live stream from three (3) live sessions, (one (1) main General Session room and two (2) Hybrid Breakout Rooms), concurrently from a hybrid event to reach a maximum of 1000 online participants that meets requirements. (PWS 1.4.2, 1.4.2.1, 1.4.8.4.3)

e) The offeror shall provide an adult and children meal and refreshment menu that includes all meals and refreshments to be served during an In-Person Event or Hybrid event that demonstrates understanding of the food and beverage requirements. (PWS 1.4.4- 1.4.4.4, Appendix A, Appendix 01 and 02, Appendix B, CDRL A008 and PWS Attachment 1)

f) The offeror shall provide a defined process and risk assessment demonstrating the capability to plan and execute a virtual event for 1000 participants that meet the requirements. (PWS 1.5-1.5.3)

2.6 Section 4: Sub-factor 2: Program Management and Staffing Approach

This sub-factor assesses the offeror’s approach to management that shall ensure all requirements of the PWS are met.

2.6.1 The offeror shall provide an approach that demonstrates a thorough understanding of the roles and qualifications required to meet the PWS requirements. The offeror shall provide proposed staffing for the basic contract period and all option periods. The proposal shall demonstrate an organizational structure that the offeror will employ while performing this effort.

The proposal shall provide rationale used to develop the organizational structure. At a minimum, the proposed approach shall address:

a) Provide appropriate certifications and experience where applicable for various functions including, but not limited to, Certified Meeting Professional (CMP) or Certified Government Meeting Professional (CGMP), child care certification, A/V (PWS 1.4.1.6,

1.4.2 and 1.4.5.1) and plan for back up or reach back capabilities.

b) Provide a plan for facilitating Government-Contractor communications. (PWS 1.4.1.5, 1.4.1.8)

c) Provide a Staffing Plan showing the proper training/certification (Child Care Provider, A/V provider/plan, event management plan) in accordance with the PWS 1.4, 1.4.1.4, 1.4.2 and 1.4.5.

d) Provide offeror’s subcontracting strategy as follows:

i. Subcontracting strategy includes how the offeror intends to manage its subcontracted efforts.

14 August 2021 Page 10 of 19

ii. If significant subcontractors are proposed, the approach clearly identifies the management strategies and approach to ensure the subcontractor performance meets the requirements of the PWS.

iii. Subcontracting strategy places particular emphasis on the performance accountability techniques and measures that will be used by the offeror.

2.7 Section 5: Glossary of Abbreviations and Acronyms

The offeror’s proposal shall contain a glossary of all abbreviations and acronyms used within this volume and provide an explanation for each.

3.0 FACTOR 2 – PAST PERFORMANCE (VOLUME II)

3.1 General

The offeror shall submit past performance information for itself, teaming partner(s) (if any) and significant subcontractor(s) (if any) IAW the following paragraphs. A significant subcontractor is defined as an entity, other than the offeror or teaming partners, that will be responsible for childcare services, audio and visual (AV) services or other services that the offeror is relying on to perform the technical requirements of the PWS.

3.2 Format and Specific Content

In the Past Performance Volume, the offeror shall provide a summary page describing the proposed role of the offeror, teaming partner(s), and significant subcontractor(s). For significant subcontractor(s), the offeror shall provide a description of the nature of work and percentage of overall work to be completed by each significant subcontractor(s). The summary page information must clearly communicate that proposed significant subcontractor(s) meet the definition of a significant subcontractor established in paragraph 3.1 of these instructions. Contract efforts submitted for significant subcontractors not meeting the established definition will not be evaluated.

The offeror, each teaming partner, and each significant subcontractor shall submit past performance information for no more than three (3) recent contract efforts. Recent is defined as an active or completed contract effort performed within the past three (3) years from the issuance date of this RFP and having at least a one (1) year performance history. The efforts may include contracts with the Federal Government, state or local government or their agencies and commercial customers.

In addition to the past performance information provided by the offeror, teaming partner(s), and significant subcontractor(s), the offeror must submit a consent letter (RFP Attch 19 Subcontractor Consent Letter) executed by each of its proposed teaming partner or significant subcontractor authorizing release of adverse past performance information to the prime offeror to allow the offeror an opportunity to respond. The offeror will be held responsible for the consequences of a teaming partner or subcontractor who does not complete the information. The consent letter should be completed by the teaming partner(s) and/or significant subcontractor(s) identified in the

14 August 2021 Page 11 of 19 proposal. The completed consent letters should be submitted as part of the Past Performance Volume.

On the three (3) contract efforts submitted in the Past Performance Volume, include relevant information concerning the offeror’s, teaming partner’s, and significant subcontractor’s compliance with FAR 52.219-8, Utilization of Small Business Concerns or FAR 52.219-9, Small Business Subcontracting Plan, if these clauses are or were contained in the contract. When subcontracting possibilities existed on the contracts submitted by the offeror/teaming partner and/or significant subcontractor, address whether or not the offeror/teaming partner and/or significant subcontractor awarded subcontracts to small business concerns, veteran-owned small business concerns, service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and/or women-owned small business concerns to the fullest extent consistent with efficient contract performance. If none of the submitted contracts included these clauses, whenever subcontracting possibilities existed in the performance of these contracts, address whether or not it was the offeror’s/teaming partner’s and/or significant subcontractor’s policy to utilize small business concerns, veteran-owned small business concerns, service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and/or women-owned small business concerns to the fullest extent consistent with efficient contract performance.

The offeror, teaming partner or significant subcontractor shall focus its information provided so that it clearly correlates past performance with the requirements of this RFP. The information must clearly describe the relevance of the effort to the work proposed. Provide the most current information for the points of contact (POCs) of each past performance effort identified.

If problems were encountered during the performance of the identified contracts, provide evidence of the offeror’s, teaming partner’s or significant subcontractor’s ability to isolate the root causes of the problems and actions taken to resolve the causes of the problem. Problems not addressed in the proposal, but found by the Government during evaluation of the information in the Past Performance Volume will be assumed to still exist.

The Past Performance Questionnaire Sheet (RFP Attch 18) will be one means used by the Government to obtain past performance information. The Government reserves the right to change, alter, and/or supplement the questionnaire without further notice to the offeror. The offeror shall send out and track the completion of the Past Performance Questionnaires to each teaming partner and significant subcontractor points of contact (POCs) identified. The responsibility to send out and track the completion of the Past Performance Questionnaires rests solely with the offeror, the offeror shall not delegate this duty to any other entity. Exert your best effort to ensure that at least two (2) POCs per contract effort submit a completed Past Performance Questionnaire directly to the Government not later than the date established in the RFP for receipt of proposals. The contract effort POCs may submit their completed Past Performance Questionnaire via email to the CO at rachel.may.1@us.af.mil. The email subject shall include the following, “Source Selection Information – See FAR 2.101 and 3.104.”

14 August 2021 Page 12 of 19

Once the Past Performance Questionnaires are completed by your contract effort POCs, the information contained therein is Controlled Unclassified Information and shall be considered source selection information IAW FAR 2.101, Definitions – Source Selection Information, and 3.104, Procurement Integrity, and shall not be released to you, the offeror. Therefore, any exchange/contact between the offeror, teaming partner and/or significant subcontractor and its own contract effort POCs in regards to comments made on the questionnaire is not permitted.

Questionnaires shall be sent to and best efforts made to ensure completion and submission directly back to the Government from the contract effort CO.

The Government may conduct follow-up discussions with any of the individuals identified in the offeror’s Past Performance Volume. The Past Performance Team evaluation is not limited to review of the information provided in the offeror’s Past Performance Volume. The Government may obtain other information by sending out additional questionnaires and/or through other sources. Past Performance information shall be obtained from the Government’s Federal Awardee Performance and Integrity Information System (FAPIIS) and may be obtained from the Past Performance Information Retrieval System (PPIRS). The Government reserves the right to use performance information from other sources such as the Defense Contract Management Agency (DCMA), Fee Determining Officials, or commercial sources. Data from previous sources selections may be used if the data is recent and relevant.

RFP Attachment 18, Past Performance Questionnaire must include the following legend at the top and bottom of each page:

SOURCE SELECTION INFORMATION – See FAR 2.101 and 3.104

CONTROLLED UNCLASSIFIED INFORMATION

3.3 Volume Organization

The Past Performance Volume shall be organized following this general outline:

Section 1: Table of Contents Section 2: Recency and Relevancy Section 3: Glossary

3.4 Section 1: Table of Contents

The offeror’s proposal shall include a more detailed table of contents to delineate the subparagraphs within that proposal volume. Tab indexing shall be used to identify sections.

Include an indexed list of tables, charts, graphs, figures, and drawings, as applicable.

3.5 Section 2: Recency and Relevancy

The offeror shall submit no more than three (3) recent contract efforts for itself, and no more than

(3) contract efforts from each teaming partners (if any), and for each significant subcontractor(s) (if any). Recent is defined as an active or completed contract effort performed within the past

14 August 2021 Page 13 of 19 three (3) years, each having at least a one (1) year performance history, from the issuance date of this RFP. The efforts may include contracts with the Federal Government, state and local governments or their agencies, and commercial customers.

The information provided shall clearly indicate the division or corporate organization that performed or is presently performing the contract.

Offerors where past performance information is not available due to offeror being acquired by, otherwise merged with other companies, and/or reorganized divisions, business groups, subsidiary companies, etc., the offeror will include a ‘roadmap’ describing all such changes in the organization of the offeror’s company. The offeror shall show how these changes impact the relevance of any contract effort you identify for past performance evaluation/performance confidence assessment.

3.6 Section 3: Glossary

The offeror’s proposal shall contain a glossary of all abbreviations and acronyms used within this volume and provide an explanation for each.

4.0 FACTOR 3 – PRICE (VOLUME III)

4.1 General

This section is to assist offerors in submitting other than certified cost or pricing data that is required for the Government to evaluate the completeness, reasonableness, and balance of proposed prices. Compliance with these requirements is mandatory and failure to comply may result in the proposal being ineligible for award. Information beyond that required by these instructions shall not be submitted, unless it is considered essential to support the price position.

Unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Proposals should be sufficiently detailed to demonstrate their reasonableness and balance.

All information relating to the proposed price, including all required supporting documentation, shall be included in the Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal with the exception of the Contract Line Item Number (CLIN) Pricing Schedule of the model contract. Price information in the CLIN Pricing Schedule is the only price information that shall be included in the Contract Documentation Volume. The burden of proof for credibility of proposed prices rests with the offeror.

4.2 Price Information Requirements

The CO has determined adequate price competition is expected for this proposed effort. 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 or pricing data will be requested and certification under FAR 15.406-2, Certificate of Current Cost or Pricing Data, will not be required.

14 August 2021 Page 14 of 19

However, if at any time during this proposed effort the CO determines that adequate price competition no longer exists, or that price reasonableness cannot be determined, offerors may be required to submit cost data to the extent necessary for the CO to determine the price fair, reasonable, and balanced IAW FAR 15.404-1(b), Proposal Analysis Techniques.

4.3 Rounding

All proposed dollar amounts shall be rounded to the nearest dollar. If the Price Volume proposal deviates from this format, the Government will apply the specified format to determine the extended price and total evaluated price (TEP).

4.4 Format and Specific Content

4.4.1 Volume Organization

The Price Volume shall be organized following this general outline:

Section 1: Table of Contents Section 2: Team List Section 3: CLIN Pricing Schedule Section 4: Glossary

4.5 Section 1: Table of Contents

The offeror’s proposal shall include a more detailed table of contents to delineate the subparagraphs within that proposal volume. Tab indexing shall be used to identify sections.

Include an indexed list of tables, charts, graphs, figures, and drawings, as applicable.

4.6 Section 2: Team List

A team list of the primary POCs of the offeror, significant subcontractor(s), teaming partner(s), and/or mentor-protégé partners shall be included in the Price Volume. The list shall include the POC’s full name (first and last), street address, telephone, facsimile number and email address.

4.7 Section 3: CLIN Schedule

Offerors shall ensure that prices entered for each CLIN are exclusive of any costs of other CLINs.

Offerors shall ensure pricing is not duplicated to ensure the calculated aggregate total evaluated price is the offeror’s lowest price for the entire contract. Offerors shall complete and submit with the proposal the CLIN Pricing Schedule Spreadsheet (RFP Attch 08).

CLIN SCHEDULE

Provide all unit prices and extended prices for each CLIN that requires proposed pricing in the CLIN Pricing Schedule (RFP Attch 08) as follows:

14 August 2021 Page 15 of 19

Base Year 0001 – 0023 Option Year One 1001 – 1023 Option Year Two 2001 – 2023 Option Year Three 3001 – 3023 Option Year Four 4001 – 4023 Option Year Five (6 Month Extension) 5001 – 5023

SIX MONTH EXTENSION

Offerors are to provide pricing for the six (6) month extension of services, the value for CLINs 5XXX will be determined IAW FAR 52.217-8, Option to Extend Services.

4.8 Section 4: Glossary of Abbreviations and Acronyms

The offeror’s proposal shall contain a glossary of all abbreviations and acronyms used within this volume and provide an explanation for each.

5.0 SMALL BUSINESS CONCERN UTILIZATION PLAN (VOLUME IV)

5.1 General

The purpose of this volume is to provide information to the Government for preparing the Small Business Concern Utilization Plan.

5.1.1 Volume Organization

The Small Business Concern Utilization Plan Volume shall be organized following this outline:

Section 1: Table of Contents Section 2: Small Business Concern Utilization Plan Section 3: Glossary

5.2 Section 1: Table of Contents

The offeror’s proposal shall include a more detailed table of contents to delineate the subparagraphs within that proposal volume. Tab indexing shall be used to identify sections.

Include an indexed list of tables, charts, graphs, figures, and drawings, as applicable.

5.3 Section 2: Small Business Concern Utilization Plan

The offeror shall submit a Small Business Concern Utilization Plan for itself and any joint venture member, as well as, each proposed significant subcontractor or teaming partner. A significant subcontractor is defined as an entity, other than the offeror or teaming partners, that will be responsible for childcare services, audio and visual (AV) or other services that the prime contractor is relying on to perform the technical requirements of the PWS. The Small Business Concern Utilization Plan is required from all offerors, including small businesses and companies with

14 August 2021 Page 16 of 19

Master, Individual, commercial subcontracting plans and/or comprehensive subcontracting plans.

The offeror/joint venture member and each proposed significant subcontractor or teaming partner shall include only the first tier of subcontractors for this effort. Offerors are advised that the Small Business Concern Utilization Plan is not the same as the Small Business Subcontracting Plan required by FAR 52.219-9, Small Business Subcontracting Plan. Large business offerors shall not utilize the Small Business Subcontracting Plan in the place of the Small Business Concern Utilization Plan. In the performance of this resultant contract, identify the following:

a) The extent of participation of proposed Small Businesses (SB) to include service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and woman-owned small business concerns, when subcontracting possibilities exist; and,

b) The description of the subcontracted work these proposed firms are to perform, the company names and CAGE codes planned for use in the performance of this resultant contract, along with the associated goals expressed in terms of percentages of the total planned subcontracted dollars.

c) If limited or no subcontracting possibilities exist for these Small Businesses and these socio-economic entities, provide rationale for such. Offerors are cautioned against only acknowledging a goal is not met, if applicable. Rather, adequate rationale includes specific reasons why a goal is unmet and any actions being taken to increase any unmet goals.

Additionally, if the offeror/joint venture member, teaming member or significant subcontractor is a small business concern, it should include the work it will be performing when calculating the goals for its Small Business Concern Utilization Plan information. If adequate rationale is provided for not being able to meet the Small Business Utilization Goals, the offeror will be considered acceptable for this factor.

5.4 Section 3: Glossary

The offeror’s proposal shall contain a glossary of all abbreviations and acronyms used within this volume and provide an explanation for each.

6.0 CONTRACT DOCUMENTATION (VOLUME V)

6.1 General

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file.

6.1.1 Volume Organization

The Contract Documentation Volume shall be organized following this outline:

Section 1: Table of Contents Section 2: SF 1449 and Amendments Section 3: Representations and Certifications Section 4: Exceptions to Solicitation Requirements

14 August 2021 Page 17 of 19

Section 5: Other Information Required Section 6: Glossary

6.2 Section 1: Table of Contents

The offeror’s proposal shall include a more detailed table of contents to delineate the subparagraphs within that proposal volume. Tab indexing shall be used to identify sections.

Include an indexed list of tables, charts, graphs, figures, and drawings, as applicable.

6.3 Section 2: SF 1449 and Amendments

Offerors shall provide a signed copy of the SF 1449 and acknowledgement of all posted amendments in this section.

6.4 Section 3: Representations and Certifications

The offeror should complete the annual representations and certifications electronically via the System for Award Management (SAM) at www.sam.gov. After reviewing the SAM database information, the offeror verifies, by submission of this proposal, that the representation and certifications currently posted electronically are correct. Any missing information or incorrect data may render a proposal non-responsive and ineligible for award. This becomes crucial if the Government determines to award without discussions.

To ensure the offeror acknowledges the requirements in FAR 52.204-8(d), Annual Representations and Certifications, we request that the offeror insert ‘none’, if applicable.

6.5 Section 4: Exceptions to Solicitation Requirements

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 sub-factors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall specifically cite a PWS 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, cost, and specific requirements of the solicitation.

6.6 Section 5: Other Information Required

6.6.1 Authorized Offeror Personnel

Provide the name, title, email address, and telephone number of the company/division POC regarding decisions made with respect to the offeror’s proposal and who can obligate the offeror’s company as a signatory on a contract of this magnitude. Also, identify those individuals authorized to negotiate with the Government.

14 August 2021 Page 18 of 19

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

Provide the company/division’s street address, county and facility code, CAGE code, DUNS code, and TIN number. 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.

6.6.3 Financial Capability

In order to determine contractor responsibility IAW FAR 9.104-1, General Standards, the offerors shall explain how they plan to maintain adequate financial capability for a contract of this magnitude and duration. Offerors must provide a letter of authorization for the CO to verify offeror’s financial responsibility. Also include the financial institution’s name, street address, as well as the primary POC full name (first and last), telephone number and email address for each financial institution. Offerors must provide the last three (3) years financial statements and Statement of Cash Flows for the firms or corporations proposed, and year-to-date financial information through the last quarter available. The year-end financial statements must be certified by an independent accounting firm, if practicable, or at least by an authorized officer of the organization.

In addition to the above, offerors shall explain how performance of the resultant contract will be funded. If the offeror intends to rely on internally available working/operations capital, evidence of availability must be submitted. If the offeror plans to rely on financial support from other sources, identify the maximum lines of credit that may be available; include documentation to support the amounts and a POC and phone number for the lender. The maximum line of credit must be based upon the inclusion of this contract effort.

The above information shall be provided for the offeror and relevant subcontractors, joint venture partners, teaming partners, and/or mentor-protégé partners who are proposed to perform on this effort. If the offeror is a combination of firms (including joint venture partners, individual companies which comprise the proposed organization, and/or key and critical subcontractors), discuss the financial responsibilities among the companies. Historical and year-to-date financial data shall be submitted for each company that makes up the offeror, and the ability to fund contract performance shall be addressed for the combined firm.

6.6.4 Teaming Agreement/Letter of Intent

If a teaming arrangement or joint venture is contemplated, provide complete, verifiable information detailing the arrangement, to include any relevant and recent information on previous teaming arrangements/joint venture with same partner. Submit information relative to the formation, organization and operation of the business unit. Additional information to be submitted shall include cost and revenue sharing agreements and any other information which describes the business arrangement. Disclose existing or planned agreements between and among the principals, each company’s responsibility for financial management of the venture, the business systems contemplated for use by the entity and their location. The Government will verify the offeror and

14 August 2021 Page 19 of 19 its first-tier subcontractors or Joint Venture as a whole when a signed Teaming Agreement, Letter of Intent or Joint Venture Agreement committing all parties to performance under this contract are submitted.

6.6.5 Department of Labor Equal Employment Opportunity Clearance (EEOC)

IAW FAR 22.805, Procedures, pre-award clearance for each proposed contract and first-tier subcontract for $10 million or more shall be requested by the CO directly from the appropriate Office of Federal Contract Compliance Programs (OFCCP) regional office. If an offeror, joint venture partner, teaming partner, mentor-protégé partner, or first-tier subcontractor ($10 million or more) is listed in OFCCP’s National Preaward Registry at https://ofccp.dol-esa.gov/preaward/pa_reg.html, offerors shall provide a copy of the database registration for Government verification as part of the proposal submission. If an offeror, joint venture partner, teaming partner, mentor-protégé partner, or first-tier subcontractor ($10 million or more) is not listed in the registry, the CO will request an EEOC review.

6.7 Section 6: Glossary of Abbreviations and Acronyms

The offeror’s proposal shall contain a glossary of all abbreviations and acronyms used within this volume and provide an explanation for each.

(End of Addendum)