Attachment 11 - Addendum to FAR 52.212-1.docx

Addendum to FAR 52.212-1 Instructions to Offerors – Commercial Products and Commercial Services

Proposal Requirements

I. Proposal Format

A. General: The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined to be not eligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. Offerors shall submit only one proposal for the AFRC Enterprise IT as the Government will review only one proposal per offeror. Proposals must be submitted via DoD SAFE to Mr. Craig Keelen, HQ AFRC/PK, Robins AFB GA, no later than the date and time specified on the Standard Form 1449, Solicitation/Contract/Order for Commercial Items, Block 8, of the RFP.

B. Communications: Exchanges of source selection information between Government and offerors will be controlled by the Contracting Officer. Email may be used to transmit such information only if the email can be sent encrypted and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via direct mailing or facsimile. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit your source selection information via encrypted email, you will need to contact the Contracting Officer indicated on the face page of the solicitation prior to that first submittal in order to exchange certificates used for encryption. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information). Otherwise, source selection information will be transmitted via direct mailing or DoD SAFE at https://safe.apps.mil .When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted.

II. Volume Organization

A. General: Proposals shall be submitted to the Government via DoD SAFE in four separate volumes as set forth below:

I N/A 1 electronic Completed RFP, to include Teaming Arrangement Agreement IAW FAR 9.6 (if applicable), and Voluntary Protection Program Information

* Page limit for Voluntary Protection Program Information is reflected below (See II.B.2).

In addition to the page limitations set forth above, proposal volumes shall comply with the following format:

1. Each volume shall be marked with the RFP number and the offeror’s name and address, and the number of the Volume, i.e. I, II, III, or IV. Proposals shall be in the English language and all monies shall be proposed in United States dollars.

2. Print shall be no smaller than a font size of 12. Paper size shall be 8 1/2” X 11”. Each volume shall be separately identified. Margins shall be no smaller than 1 inch on all sides and each page within a volume shall be numbered consecutively. Elaborate formats and/or color presentations are not desired or required.

3. The page limitation for Volume II, Written Technical Proposal is no more than 32 pages total, which shall include no more than 20 pages for a written Technical Narrative, no more than five (5) pages for a Personnel Plan, no more than five (5) pages for a written narrative accompanying the task order proposal, and no more than two (2) pages for a Mission Essential Services Continuation Plan. The page limitations include charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., but excludes any cover pages, table of contents, list of acronyms (if utilized). Also excluded from the page count is the Task Order Proposal spreadsheet (Attachment 9 – TO Proposal Worksheet). Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and either retained in the contract file without being considered in the evaluation, or, sent back to the offeror.

4. Page limitations may be placed on responses to Evaluation Notices (ENs), if issued. The specified page limits for EN responses will be identified in the letters forwarding the ENs to offerors or on the EN form itself.

5. Each page containing proprietary information should be so marked.

6. Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

7. Submission of the initial and any revisions to the proposal packages via electronic mail (email), direct mailing, and/or hand delivery will not be accepted. Initial and any revisions to the proposal packages shall be submitted via DoD SAFE.

B. Volume I, Completed Request For Proposal (RFP)

1. General: Volume I shall consist of the completed and signed RFP, to include acknowledgment of any amendments issued, with a cover letter delineating any exceptions taken to the RFP terms and conditions with accompanying rationale. However, offerors are cautioned that any noncompliance with the terms and conditions of the RFP will cause their proposal to be determined unacceptable and therefore not considered eligible for award. Also shall include any necessary Teaming Agreement documents if applicable. Offerors shall ensure that all clauses and provisions that require “fill in” information are appropriately completed and submitted.

2. Teaming Arrangement Agreement: If applicable, the teaming arrangement agreement will be evaluated for conformance and completeness, and to verify the prime offeror’s compliance with FAR Subpart 9.6, Contractor Team Arrangements. Offeror will not be eligible for award when teaming arrangement documentation is found to be noncompliant.

3. Voluntary Protection Program Information: Air Force Voluntary Protection Program (VPP) requirements are applicable to this acquisition as work on an Air Force installation will be required by contractor employees working 1,000 hours or more in any calendar quarter and the employees are not directly supervised by the Air Force installation. As part of Volume I, for each of the past three (3) calendar years immediately prior to the calendar year in which this solicitation is being issued (i.e., calendar years 2019, 2020, and 2021), submit your Total Case Incidence Rates (TCIR) and Day Away, Restricted, and or Transfer Case Rates (DART) for the standard Industrial Classification System (SIC) code or North American Industrial Classification Systems (NAICS) code for the applicable industry as identified on the face page of this solicitation. If TCIR/DART rates are not maintained, submit comparable rates. This VPP information shall be no more than two (2) pages. Note: This VPP information pertains to the offeror. If an unpopulated joint venture is formed (a joint venture in which the employees are employed by the joint venture partners and not the joint venture itself), each joint venture partner must submit these rates. Any proposed subcontractor with employees working 1,000 or more hours in any calendar quarter on an Air Force installation whose subcontractor employees are not directly supervised by the Air Force installation must submit these rates as well. For information on TCIR/DART rates, visit the following VPP site: https://www.osha.gov/dcsp/vpp/index.html.

4. Cross Referencing: Each volume shall be written on a stand-alone basis so that its contents may be evaluated with no cross-referencing to other volumes of the proposal. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal.

C. Volume II, Written Technical Proposal

1. General: The written technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. 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 the Government has no prior knowledge of their capabilities, work processes, facilities, and experience and that the Government will base its evaluation on the information presented in the offeror’s technical proposal.

2. Mission Essential Services Continuation Plan: Mission-essential services as identified in the PWS consisting of Infrastructure and Engineering Field Support (See PWS, 2.1.1.), HQ AFRC and AFRC Host Base Cyber Transport Support (See PWS, 2.1.2.2.), Mobile Application Infrastructure Support (See PWS, 2.1.3.), Virtualization Engineering and Management Support (See PWS, 2.1.4.), Enterprise File/Storage Support Services (See PWS, 2.1.9.), AFRC Wide Area/I-COOP File Server Storage Support Services (See PWS, 2.1.10.), SharePoint Architecture and Server Support (See PWS, 2.1.16.1.), and Service Desk/Communications Focal Point (See PWS, 2.2.). In accordance with DFARS 237.7602 and DFARS PGI 207.105(b)(20)(C)(3), offerors shall submit a written Mission Essential Services Continuation Plan, not to exceed two (2) pages, for how it will provide the continuity of essential services. AFRC will be responsible for facilities and equipment required for continuity of operations, to include an Information Continuity of Operations (ICOOP) capacity, therefore the offeror’s plan must address providing continuity of manpower to continue these services. The sufficiency of the offeror’s plan will be considered and evaluated by the Government in conjunction with the technical evaluation of offers (Technical Subfactor Four).

3. Format and Specific Content: The following information shall be provided in the written technical proposal and will be evaluated to assess technical acceptability in accordance with addendum to FAR 52.212-2 Evaluation Factors for Award (Attachment 12, Addendum to FAR 52.212-2 – Evaluation – Commercial Products and Commercial Services). The written technical proposal shall address each of the following subfactors to describe the offeror’s proposed approach to performing the requirements set forth in the PWS.

Subfactor One – Personnel Plan: Offeror shall provide a written narrative, not to exceed five (5) pages, that describes procedures for building and maintaining a qualified team to meet the scope and scale required to meet the requirements of the PWS. These procedures should also include approaches to manage any subcontractor(s) or other teaming partner(s) arrangements. Submission should focus on ability to recruit and manage a team that spans multiple states, ability to maintain continuity and expertise in the technologies described in the PWS, oversight processes to ensure qualifications are met and maintained, and management/oversight structure for each location (see PWS, 1.3 Place of Performance). If subcontractors are to be used, submission should also describe rationale for selection of subcontractor(s) anticipated division of labor, and procedures for ensuring the prime will serve as the single focal point for the Government.

Subfactor Two – Technical Narrative: Offeror shall provide a written narrative, not to exceed 20 pages, that describes the offeror’s approach based on its application of reasonable IT industry methods and techniques to accomplish the full range of tasks in the entire PWS. This description shall include the use and management of key technologies, tools, and systems as listed in the PWS as required within the AFRC IT environment, as well as any offeror-specific capabilities, technologies, or tools expected to automate or increase efficiency of the services described in the PWS.

Subfactor Three - Initial Task Order Proposal. Offeror shall submit a completed Task Order Proposal Worksheet (Attachment 9 – TO Proposal Worksheet) to identify the mix of labor categories and hours to be provided to accomplish the requirements of each CLIN in the initial task order, which will be issued at time of contract award. Offeror will also submit a written explanation describing the basis for the proposal, to include any labor efficiencies expected to be gained from the offeror’s approach (e.g., utilizing existing corporate capabilities at no cost to the Government, utilizing automation or proprietary capabilities that would significantly change industry-standard IT support ratios, etc.), as well as an explanation of any proposed labor category titles that differ from those listed on the Rate Sheet template (Attachment 8 – Rate Sheet).

Subfactor Four - Mission Essential Services Continuation Plan. Offeror will provide a plan that describes how the offeror proposes to maintain the mission essential services in section as listed in section II.C.2 in the event of significant disruptions to normal operations such as natural disasters, pandemics, etc.

D. Volume III, Present/Past Performance

1. General: The offeror/joint venture shall submit Present and Past Performance Information for itself, as well as for each proposed critical subcontractor(s) and/or teaming partner(s) using the FACTS Sheet (Attachment 5 – FACTS Sheet) and the following paragraphs. A critical subcontractor is defined as an entity (subcontractor and/or teaming partner contractor), other than the offeror itself that has been determined by the offeror to be directly responsible for the majority of work for any one or more of the following services: virtualization engineering and management support (See PWS 2.1.4), mobile application infrastructure support (See PWS 2.1.3), enterprise file/storage support services (See PWS 2.1.9), cyber transport support (See PWS 2.1.2), enterprise architecture program (See PWS 2.6), service desk/communications focal point (See PWS 2.2), enterprise Microsoft SharePoint support (See PWS 2.1.16), VTC, program management, spectrum management, or cybersecurity.

2. Past Performance Submission:

(a) Summary Page: Offerors shall provide a summary page that describes how the present/past performance aligns (by PWS paragraph number) to the proposed role of the offeror/joint venture, critical subcontractor and/or teaming partners and the nature of work. The summary page information must clearly communicate how each proposed critical subcontractor meets the definition of a critical subcontractor as defined in II.D.1. above. Contract efforts submitted for the present/past performance evaluation of proposed critical subcontractors that do not meet the definition of a critical subcontractor as defined in section II.D.1. above will not be evaluated.

(b) FACTS Sheets: Each offeror/joint venture shall complete a separate FACTS Sheet (Attachment 5 – FACTS Sheet) for up to five (5) active or completed recent contracts. Recency is defined as active or completed efforts performed for at least six (6) months within the past three (3) years from the issuance date of the RFP, that the offeror/joint venture considers relevant in demonstrating its ability to perform this acquisition. For each critical subcontractor included in the offeror/joint venture proposal, a FACTS Sheet for up to three (3) of the critical subcontractor’s recent and relevant contracts shall also be submitted. The offeror’s/joint venture or critical subcontractor’s past performance information may include data on efforts performed by other predecessor companies, affiliates, other divisions or corporate management if such was provided for evaluation and if the offeror’s past performance volume demonstrates the company, affiliate, or division will provide the offeror with resources for this acquisition, such as workforce, management, facilities, or other capabilities demonstrating direct and meaningful involvement in the performance of this acquisition. The FACTS Sheet shall clearly indicate the division or corporate organization that performed or is presently performing the contract. Contracts listed may include those with the Federal Government, state and local governments or their agencies, and commercial customers.

3. Ordering Type Contracts Submission: If the contract submitted is an ordering type contractual vehicle, for example, including but not limited to, an Indefinite Delivery “D” type contract per FAR 16.5, only after issuance of a delivery/task order does performance occur. Given this, an individual order (or series of orders) under the basic ordering contract shall be submitted, in lieu of just the basic ordering contract itself. All information provided to the Government, for an ordering type contractual vehicle, shall be at the order level (i.e., a delivery/task order).

When determining what order (or series of orders) to submit for evaluation, please reference Attachment 12 – Addendum to FAR 52.212-2 – Evaluation – Commercial Products and Commercial Service, paragraph II.D.1. for details on how the Government will evaluate each submitted effort for recency, relevancy, and quality. In order to achieve optimal scope, complexity and magnitude, as described in Addendum to FAR 52.212-2, paragraph II.D.4, Present/Past Performance Relevancy Matrix chart, the offeror should consider submitting a series of orders, if possible. However, a series of orders should only be submitted if the series of orders is for continuous technical scope with the same customer, demonstrating relevancy to this acquisition. Not all ordering type contractual vehicles will have series of orders that meet this criteria. In this instance, only the single order demonstrating relevant technical scope should be submitted for evaluation.

When submitting an individual order (or series of orders) under an ordering type contractual vehicle, it is important that the offeror’s past performance information be accurate, complete, and in the correct format. If the information is not submitted in the correct format, the Government will not be able to evaluate the effort for recency, relevancy, and quality. There are specific places for submission of this information in the FACTS Sheet. Please ensure the information submitted, in the FACTS Sheet, is for each order (or series of orders), in lieu of just the basic ordering contract itself. This includes, but is not limited to, information such as the dollar value, period of performance, and scope, for each order or series of orders. See II.D.3.1 Series of Orders, below for further information on how to submit series of orders.

3.1 Series of Orders: When submitting a series of orders for evaluation, the offeror should list the orders under the basic ordering type contractual vehicle that demonstrate relevancy, as defined in the relevancy definitions in Addendum to FAR 52.212-2, paragraph II.D.3. Relevancy Definitions. If an offeror submits a series of orders for evaluation, the total dollar value of each order (in the series of orders) and the period of performance dates of each order (in the series of orders), shall be submitted. The total dollar value of each order (in the series of orders) shall be added up to calculate the Total Dollar Value to be used in the evaluation, for the submitted effort. The total period of performance of each order (in the series of orders) shall be added up to calculate the Total Period of Performance to be used in the evaluation, for the submitted effort. In order to calculate the annual cost for the magnitude as described in paragraph II.D.3 of the Addendum to FAR 52.212-2, the number of months in the total period of performance (PoP) would be divided by twelve (12) to arrive at a whole year number. The total dollar value would then be divided by the whole year number to arrive at an annual value.

Caution: All orders within the series of orders, being submitted, should be for the same continuous technical scope demonstrating relevancy to this acquisition. The Government reserves the right to request additional information from the offeror or Points of Contacts provided to verify that the series of orders is for the same continuous technical scope.

4. Key Personnel: The evaluation of the offeror’s/joint venture present/past performance WILL NOT include the present/past performance of any key personnel, even though they may perform major or critical aspects of this requirement.

5. Subcontractor Consent Letter: In addition to the information provided in the FACTS Sheet for each entity as required by II.D.1. above, the offeror must submit a Consent Letter executed by each of its proposed teaming partner(s) and/or critical subcontractor(s) authorizing release of past performance information, to include adverse present/past performance information, to the prime offeror to allow the prime offeror an opportunity to respond. A sample Subcontractor Consent Letter is attached to this RFP (Attachment 4 – Subcontractor Consent Letter). The Subcontractor Consent Letter shall be completed by critical subcontractor(s) identified in the offeror’s proposal. Offerors shall submit all completed Consent Letters in its Volume III Past Performance.

6. FACTS Sheet: The offeror/joint venture, critical subcontractor(s) and/or teaming partner(s), if applicable, shall focus its FACTS Sheet responses so that the information provided clearly correlates the present and past performance to the requirements of this acquisition. The FACTS Sheet responses must clearly describe the relevancy of the work performed to the work in this acquisition. Provide the most current information for the Respondent identified on each FACTS Sheet. Responses shall be provided by at least one of the following respondents in descending order of government preference:

(a) Procuring Contracting Officer/Contract Negotiator or equivalent

(b) Program/Project Manager, or equivalent

(c) Administrative Contracting Officer/Contract Administrator or equivalent

(d) Other (As specified in your FACTS Sheet)

If problems were encountered during the performance of the identified contracts, provide evidence of the ability to isolate the root causes of problems and include in the FACTS Sheet a description of programs or actions taken to resolve those causes. Problems not addressed in the FACTS Sheet but found by the Government during the evaluation of the information in this volume, will be assumed to still exist. Note: In the case of Contractor Performance Assessment Report System (CPARS), if your input has already been provided and the rationale/circumstances have not changed, DO NOT repeat them here.

7. Past Performance Questionnaire: The Present/Past Performance Questionnaire (Attachment 6 – Past Performance Questionnaire) will be one means used by the Government to obtain present/past performance information. The Government reserves the right to change, alter, and/or supplement the questionnaire without further notice to the offeror(s). The offeror/joint venture shall send out and track the completion of the Present/Past Performance Questionnaires to each of the offeror’s/joint venture, critical subcontractors’ and/or teaming partner(s) (i.e., each entity’s) Respondent identified in each FACTS Sheet. The responsibility to send out and track the completion of the Present/Past Performance Questionnaires rests solely with the offeror. Offerors shall not delegate this responsibility to any other entity. When sending out the Present/Past Performance Questionnaire, offerors are to include the Client Authorization Letter (Attachment 7 – Client Authorization Letter). Offerors should exert their best effort to ensure that at least two Respondents per relevant contract submit a completed Present/Past Performance Questionnaire directly to the Government not later than the date established in the RFP for receipt of proposals. Respondents must submit their completed Present/Past Performance Questionnaire electronically by e-mailing to: craig.keelen@us.af.mil, and michelle.henderson.8@us.af.mil. Please ensure respondents encrypt the e-mail in accordance with the requirements detailed in paragraph I.B. above.

Once the Present/Past Performance Questionnaires are completed by your Respondents, the information contained therein shall be considered source selection sensitive and shall not be released to you, the offeror. Therefore, any exchange/contact between the offeror/joint venture, critical subcontractor(s) and/or teaming partner(s) and its own respondents in regard to comments made on the questionnaire is not permitted.

8. Client Authorization Letter: Offerors that submit present/past commercial contract information shall use the Client Authorization Letter (Attachment 7 – Client Authorization Letter). Offerors shall send the Client Authorization Letter to the point of contact (POC) for each of the commercial efforts submitted requesting/authorizing them to complete a Present/Past Performance Questionnaire. Offerors are required to send the client authorization letter(s) with the Present/Past Performance Questionnaire(s) to each commercial contract POC. Offerors shall submit a copy of all Client Authorization Letter(s) in its Volume III Present/Past Performance for the Government’s use in case additional questionnaires need to be sent by the Government to any POC listed on a FACT Sheet after the RFP due date.

9. Follow-up Discussions: The Government may conduct follow-up discussions with any of the people identified in the FACTS Sheets or in the offeror’s Volume III Present/Past Performance. Pursuant to FAR 15.305(a)(2)(ii), the Government may obtain other information by sending out additional questionnaires and through other sources, other than those listed within the FACTS Sheets.

E. Volume IV, Price Proposal: Offerors shall submit a rate sheet, in MS Excel format, using Attachment 8 – Rate Sheet, in support of their proposed price. The rate sheet submitted shall be attached to the awarded contract and will be used for the entire period of performance. Offerors shall input their fully burdened rates for each labor category listed. If deviations in labor categories are necessary, place notes in the worksheet to explain. All loaded labor rates shall be rounded to the nearest penny.

21-Sep-22