SCARS_RFP_Attachment_10_Section_L_-_Amendment_1.pdf

FA8621-18-R-0002

SCARS RFP Attachment 10

SECTION L

Instructions, Conditions, and Notices to Offerors or Respondents

FOR

Simulator Common Architecture Requirements and Standards (SCARS)

Solicitation #FA8621-18-R-0002

14 Jan 2019

Prepared by:

Agile Combat Support Directorate, Simulators Program Office

AFLCMC/WNS

2300 D Street, Bldg. 32 Wright-Patterson AFB, OH 45433-7249

TABLE OF CONTENTS

1. Proposal Format

1.1 General

1.2 Communications

1.3 Foreign-Owned or Foreign-Influenced Companies

1.4 Facility Clearance

2. Volume Organization

2.1 General

2.1.1 Point of Contact

2.1.2 Discrepancies

2.2 Volume I – Executive Summary

2.2.1 General

2.2.2 Narrative Summary

2.2.3 Cross Reference Matrix

2.3 Volume II – Technical

2.3.1 General

2.3.2 Format and Specific Content

2.3.2.1 Subfactor 1: Simulator Common Architecture (SCA)

2.3.2.2 Subfactor 2: SCARS Management Services

2.3.2.3 Subfactor 3: Government Ownership of the Technical Baseline

2.3.2.4 Strengths

2.4 Volume III – Past Performance

2.4.1 General Instructions

2.4.2 Past Performance Required Format

2.4.2.1 Early Proposal Information

2.4.2.2 Relevant Contracts

2.4.2.3 Specific Content

2.4.2.4 Ordering Type Contracts Submission

2.4.2.5 Series of Orders

2.4.3 Subcontractor Consent

2.4.4 Past Performance Questionnaire

2.4.5 Client Authorization Letters

2.4.6 Organizational Structure Change History

2.4.7 Past Performance Information (PPI) Tool Instructions for Offerors

2.5 Volume IV – Price

2.5.1 General Instructions

2.5.2 Volume Organization

2.5.2.1 Completed TEP Spreadsheet

2.5.2.2 Narrative and Methodology

2.5.2.3 Professional Employee Compensation Plan

2.5.3 Pricing Data Requirements

2.5.4 Rounding

2.5.5 Additional Information

2.6 Volume V – Contract Documentation

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

2.6.2 Authorized Offeror Personnel

2.6.3 Cognizant Government Offices

2.6.4 Use of Non-Government Advisors

2.6.5 Completed Model Contract

2.6.5.1 Section A – Solicitation/Contract Form

2.6.5.2 Section B – Supplies or Services and Prices

2.6.5.3 Section C – Description/Specifications/Work Statement

2.6.5.4 Section D – Packaging and Marking

2.6.5.5 Section E – Inspection and Acceptance

2.6.5.6 Section F – Deliveries or Performance

2.6.5.7 Section G – Contract Administration Data

2.6.5.8 Section H – Special Contract Requirements

2.6.5.9 Section I – Contract Clauses

2.6.5.10 Section J – List of Attachments

2.6.5.11 Section K – Representations, Certifications and Other Statements of Offerors

2.6.6 Incorporation of Technical Proposal

2.6.7 Exceptions to Solicitation Requirements

2.6.8 Organizational Conflict of Interest Mitigation Plan

2.6.9 Small Business Subcontracting Plan

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR

RESPONDENTS

1. Proposal Format

1.1 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 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 Simulator Common Architecture Requirements and Standards (SCARS) acquisition as the Government will review only one proposal per Offeror. Proposals shall be addressed to the Contracting Officer (CO) and mailed or hand carried to the following address no later than the date and time specified in the RFP Cover Letter:

AFLCMC/AZA, Building 570, Room 113 ATTN: McKenna Moore, Contracting Officer 1755 Eleventh Street Wright-Patterson AFB, OH 45433-7228 Reference: FA8621-18-R-0002

Offerors are requested to submit Volume III, Past Performance Information, so that it is received ten (10) business days prior to the required due date for proposals. Failure to submit Volume III by the earlier date will not result in Offeror disqualification.

In accordance with (IAW) FAR Subpart 4.8 (Government Contract Files), the Government will retain one paper copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of unsuccessful proposals.

1.2 Communications

Exchanges of source selection information between the Government and Offerors will be controlled by the CO, McKenna Moore, email: mckenna.moore@us.af.mil. Source Selection information will be transmitted via direct mailing or AMRDEC SAFE at https://safe.amrdec.army.mil/safe/guide.aspx. Email through AMRDEC SAFE may be used to transmit such information and must include “Source Selection Information – See FAR 2.101 and 3.104, For Official Use Only (FOUO)” in the subject line of the email.

The CO will promptly notify Offerors of any decision to exclude them from the competitive range;

whereupon, they may request and receive a debriefing IAW FAR 15.505 or 15.506. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to defer the debriefing until after the source selection decision. Offerors excluded from the competitive range are entitled to no more than one debriefing for each Offeror. The CO will notify unsuccessful Offerors in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.506, as applicable.

1.3 Foreign-Owned or Foreign-Influenced Companies

This solicitation excludes foreign-owned or foreign-influenced companies as primes and subcontractors unless they have a facility clearance and a mitigated Foreign Ownership, Control or Influence (FOCI).

The Offeror shall provide appropriate CAGE code as proof.

1.4 Facility Clearance

Offerors shall include, as an attachment to the Technical Volume, a valid U.S. facility clearance of Secret https://safe.amrdec.army.mil/safe/guide.aspx at any facility responsible for classified execution of this effort at proposal submission or the Offeror’s proposal will be rejected. Furthermore, Offerors must still possess a valid U.S. facility clearance of Secret at the time the Source Selection Authority (SSA) makes the award decision in order to be eligible for contract award.

2. Volume Organization

2.1 General

The Offeror shall prepare the proposal as set forth below. The titles and contents of the volumes shall be as defined in this paragraph, all of which shall be within the required page limits and with the number of copies as specified in the table below.

VOL TITLE COPIES PAGE LIMIT ATTACHMENTS

I Executive

Summary 3 Paper 1 Electronic*

10, excluding attachments

• Master Table of Contents

• Cross Reference Matrix

II Technical 3 Paper 1 Electronic*

75, excluding attachments

• Integrated Master Plan (IMP)

• Integrated Master Schedule (IMS)

• Configuration Management Plan

(CMP)

• Open Systems Management Plan

(OSMP)

• Logistics Plan

• Counterfeit Prevention Plan

• Item Unique Identification (IUID)

Marking Plan

• SysML System Model in .xmi format

• U.S. Facility Clearance

• Data Rights assertions

• Small Business Participation

Commitment Document III Past

Performance 3 Paper 1 Electronic*

No more than 8 contract references total. No more than 4 contract references for the prime Offeror and no more than 2 contract references for each proposed critical subcontractor.

36 pages maximum – including introductory information, excluding attachments**

• Consent Letters

• Past Performance Questionnaire

Contact Listing

• Client Authorization Letters (if applicable)

• Organizational Structure Change

History

• Business Relationships PPI Tool

Output

IV Price 3 Paper 1 Electronic*

No Limit*** N/A

V Contract Documentation

1 Paper 1 Electronic*

No Limit N/A

* Proposal volumes shall be submitted in written form (as specified above) and electronic via CD-R or DVD-R (write once/read only) (1 copy per volume) that is “closed” so that no further writes can be made to the media. CD-R/W or DVD-R/W media types are not acceptable. Media must be virus scanned by the Offeror prior to submitting to the Government.

** Offerors shall use the instructions set forth in Past Performance Information (PPI) Tool to electronically submit the Past Performance Information (PPI). Guidance to access the PPI tool will be provided in paragraph 2.4.7.

*** Page limit for Professional Employee Compensation Plan (in Vol. IV) limited to 15 pages.

In all instances the electronic copy will be determined to be the official document and takes precedence over any and all paper copies; one paper copy will be retained for archival purposes.

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

A. The sealed package used to submit the proposal package must show the time and date specified for receipt. 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, etc. Proposals shall be in the English language and all monies shall be proposed in United States dollars.

B. Print shall be no smaller than a font size of 12 and be in Times New Roman font except for tables, charts, graphs and figures for which the font shall be no smaller than 10 point. Paper size shall be 8 1/2” X 11,” excluding any charts, graphs, drawings, diagrams, supporting illustrations, and spreadsheets, etc. Charts, graphs, drawings, diagrams, supporting illustrations, or spreadsheets shall not be greater than 11” x 17.” Foldout pages shall fold entirely within the volume, and will count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. These limitations shall apply to both electronic and paper copy proposals. 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 pages. Each volume within the proposal binder shall be separately tabbed and identified. Margins shall be no smaller than 1 inch top and bottom and ¾ inch on each side. Each page within a volume shall be numbered consecutively. Elaborate formats, bindings, and color presentations are not desired or required.

C. The page limitation for Volume II, Written Technical Proposal is 75 pages. The page limitations include any charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., but exclude the cover sheet, any table of contents, list of abbreviations and acronyms (with an explanation for each), glossaries, and attachments as specified in paragraph 2.1. 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.

D. Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Tables of contents, indexes, and glossaries shall not count against the page limitations for their respective volumes.

E. Each volume of the proposal shall be in its own three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be included in each binder, clearly marked as to volume number, title, copy number, solicitation number, and the Offeror's name. The same identifying data shall be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. All appropriate markings shall include those prescribed IAW 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. Each page shall be identified with the solicitation number, company name, volume, and page number.

F. Offerors shall submit documents only using Microsoft Office 2010 or newer, and Adobe Acrobat

9.0 or newer:

1. Word documents - Set "Save as type" to "Word Document (*.docx)" only.

2. Excel spreadsheets – Set “Save as type” to “Microsoft Excel Workbook (*.xlsx).”

3. Submit any Microsoft Project files in Microsoft Project 2010 or newer. There are no special “save” functions required for later versions of Project.

4. Offerors shall submit PDF documents using only Adobe Acrobat 9.0 or later. Do NOT submit any documents in PDF format that are copied as “images.” When creating PDF files always create to enable textual search and copy functions.

G. All pricing information shall be addressed ONLY in the Price and Contract Documentation Volumes. The Total Evaluated Price (TEP) spreadsheet shall be formatted using Microsoft Excel in .xlsx format, and the electronic file shall be live and contain fully-traceable formulas and shall not contain references to external workbooks, with all equations and functions fully functional, unlocked, and unhidden. At any time during this competition, if the CO determines adequate price competition no longer exists, Offerors may be required to submit information to the extent necessary for the CO to determine the reasonableness of the price.

H. 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.

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

J. 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

K. Submission of the initial proposal packages via electronic mail will not be accepted. Initial proposal packages shall either be mailed or hand-delivered. Offerors are cautioned that Wright- Patterson AFB has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Some delay should be anticipated when hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor pass and arrive at the specified office PRIOR to the time specified for receipt of proposals.

L. Classified Information: Proposals shall not contain classified information.

M. Written questions or requests for clarification may be sent to the CO via email. Offerors are requested to submit questions or clarification requests by 12:00 p.m. EST on 09 January 2019. Answers to questions and clarifications will be provided to all Offerors via the Federal Business Opportunities (FedBizOpps) website at www.fbo.gov. No proprietary information will be released. In the event of conflict between the Government’s response to questions or clarification requests and the RFP, the RFP takes precedence.

2.1.1 Point of Contact

The CO, McKenna Moore, mckenna.moore@us.af.mil, is the exclusive point of contact for this acquisition.

2.1.2 Discrepancies

If an Offeror believes the requirements or 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 proposed remedies the Offeror is asking the CO to consider as related to the omission or error. The Offeror is reminded the Government reserves the right to award this effort based on the initial proposal, http://www.fbo.gov/ mailto:mckenna.moore@us.af.mil as received, without discussions.

2.2 Volume I – Executive Summary

2.2.1 General

Volume I, Executive Summary, shall consist of a narrative summary, a master table of contents for the entire proposal, and a completed Cross Reference Matrix (RFP Attachment 9).

2.2.2 Narrative Summary

The narrative summary shall be a concise summary of the entire proposal and address the significant risks and highlight 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, including the Executive Summary, shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

2.2.3 Cross Reference Matrix

The Offeror shall complete the Cross Reference Matrix (RFP Attachment 9), indicating where in its proposal the information can be found as it relates to the RFP. The Cross Reference Matrix will be utilized as a tool to show critical interrelationships and dependencies among the technical requirements documents, the evaluation factors, Performance Work Statement (PWS), System Requirements Document (SRD), the Contract Line Item Numbers (CLINs), the proposal volume, and proposal page and section number. The Cross Reference Matrix will help an Offeror ensure it has responded to all the 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. Additionally, to the extent the Cross Reference Matrix discloses details as to the manner by which the Government intends to evaluate the Offerors’ proposals for award, references in the Cross Reference Matrix are for informational purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with Section M of the solicitation.

2.3 Volume II – Technical

2.3.1 General

The written technical proposal shall be clear, concise, and include all the information required for effective evaluation. The proposal shall not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the Offeror intends to meet the requirements of the RFP.

Offerors shall assume the Government has no prior knowledge of their capabilities, work processes, facilities, or experience, and will base its evaluation on the information presented in the Offeror’s technical proposal.

The Technical Volume must be specific and complete. Legibility, clarity, brevity, and coherence are important. Offerors’ proposals will be evaluated against the Technical subfactors as defined in Section M.

Using the instructions provided below, Offerors should provide as specifically as possible the actual methodology their firm will use for accomplishing and satisfying every detail of these subfactors.

All the requirements and Terms and Conditions specified within the solicitation are mandatory. Offerors affirm, by their proposal submission, that their firm will perform all the ID/IQ PWS (RFP Attachment 1A) and SRD (RFP Attachment 2) requirements. It is not necessary or desirable for Offerors to address the entire ID/IQ PWS within their proposal.

2.3.2 Format and Specific Content

The following information shall be provided in the written technical proposal and will be evaluated to assess the proposed technical approach and associated technical risk in accordance with Section M, Evaluation Factors for Award (RFP Attachment 11). 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 and SRD.

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

• Table of Contents (not included in the volume page limit)

• List of Tables and Drawings (not included in the volume page limit)

• Glossary/List of Acronyms (not included in the volume page limit)

• Subfactor 1: Simulator Common Architecture (SCA)

• Subfactor 2: SCARS Management Services

• Subfactor 3: Government Ownership of the Technical Baseline (OTB)

• Technical Risk o Subfactor 1: Simulator Common Architecture (SCA) o Subfactor 2: SCARS Management Services o Subfactor 3: Government Ownership of the Technical Baseline (OTB)

The Offeror shall address Technical Risk associated with their proposed technical solution for each subfactor considered to have a probability for disruption of schedule, degradation of performance, need for increased Government oversight, or the likelihood of unsuccessful contract performance. In addition to specifically identifying inherent risks and the associated planned mitigation, the Offeror shall include risk mitigation strategies within their solution. Offerors shall also provide rationale for each risk, including impacts on schedule and performance. Offerors shall 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 or SRD requirements), regardless of whether or not those requirements are identified as subfactors. Offerors shall include within the proposed Technical Solution the mitigations planned to eliminate or reduce the risk which shall not impact accomplishing the requirements of the contract. If no risks or mitigations are identified in the Offeror's proposal, it indicates the Offeror does not consider there to be any risk associated with their proposed approach.

2.3.2.1 Subfactor 1: Simulator Common Architecture (SCA)

The Offeror shall present a technical approach to accomplish the requirements of the ID/IQ PWS, Task Order 001 PWS (RFP Attachment 1B), and SRD. The Offeror's proposal shall provide, with supporting rationale, the following:

a. The proposed hardware and software architecture, supported by the Model Based System Engineering System Model, and the architecture’s ability to support the security domains of the SCARS affiliates, including the Offeror's data storage architecture.

b. The application onboarding and training system integration challenges associated with the Offeror’s SCA design and the disparate SCARS Affiliate training system baselines.

2.3.2.2 Subfactor 2: SCARS Management Services

The Offeror shall, through the use of narrative and diagrams, describe its proposed approach which meets the requirements of the PWS and SRD. The technical proposal shall address each of the following elements:

a. How the Offeror intends to manage SCARS On-Premise Equipment (OPE) integration services IAW ID/IQ PWS 4.2.4, 4.3.5, describing the types of testing, and proposed frequency which addresses testing and resolution associated with SCARS Affiliate hardware and software, including OPE Affiliate application hosting.

b. The Offeror's product support strategy for the SCA inclusive of the ability to provide maintenance and sustainment planning consistent with the Product Support requirements as described in ID/IQ PWS 4.6.9, 6.18.

c. The Offeror’s strategy to stand up an interim Security Operations Center (SOC) hosted by the Offeror IAW ID/IQ PWS 4.2.3, 5 (all sub-para), 6.7, Task Order PWS 3.1, 3.2, including:

(i) Ability to define, design, deliver, and stand up SOC within 180 days of contract award, including acquisition and installation of SOC Equipment and Software and achievement of an Authority to Operate (ATO)

(ii) Management and execution of SCARS Security and Maintenance Events

(iii) Provisioning and maintenance of SOC Network Services

(iv) Management and execution of SCARS help desk operations

(v) Approach to transfer remote scan results from the Offeror-hosted SOC to the Enterprise Mission Assurance Support Service (eMASS) on SIPRNET IAW ID/IQ PWS Para 5.6

d. The Offeror’s staffing plan for transition from the temporary SOC to the Government SOC including the substantiation of the number of full time equivalents, the functional area supported, the certifications/credentials of personnel, and the retention of personnel. For evaluation purposes only, assume the Government SOC will be available in CY 2021 in Orlando, FL.

e. The Offeror shall submit a Small Business Participation Commitment Document (SBPCD) that addresses the requirement to subcontract no less than 15% of the total value of Task Order 001 to qualified small business entities. The SBPCD is a separate and distinct document from the Small Business Subcontracting Plan. In addition, the SBPCD is required from all Offerors, including companies with commercial plans and comprehensive subcontracting plans. However, objectives/goals specifically identified in the proposal must be consistent across the Small Business Subcontracting Plan (if applicable) and the SBPCD. The Offeror shall submit the SBPCD under the Technical Volume of the proposal. Small Business participation only includes small business utilization contributions to contract performance at the 1st and 2nd tier subcontract level; however, a small business proposing as the Prime may also include its own performance.

The SBPCD shall include:

(i) The name of all 1st and 2nd tier Small Business subcontractors to be utilized (including NAICS codes) and the products/services to be provided;

(ii) A description of the type and complexity of the products/services to be provided;

(iii) The extent of utilization quantitatively (percentage) by small business subcontractor;

(iv) The Offeror’s approach to meeting the requirement of no less than 15% small business participation on future task orders, including items (i) and (ii) above.

2.3.2.3 Subfactor 3: Government Ownership of the Technical Baseline In order for the Government to effectively manage life cycle costs, the Government intends to own the technical baseline of the SCARS SCA at a level which allows for incremental expansion and modification throughout the SCA lifecycle.

a) The following elements shall be provided to fulfill the depot level maintenance or follow-on competitive Contractor Logistics Support (CLS) strategy of the Government for its assessment supported by: Open Systems Management Plan (OSMP), a narrative of the Model Based System Engineering (MBSE) System Model supported by the MBSE System Model in .xmi and .html.

The Offeror shall submit:

1) An initial OSMP, following DI-MGMT-82099. Within the OSMP format, the Offeror’s plan shall describe its open systems approach for using: (1) modular design, (2) standards-based interfaces, and (3) widely-supported, consensus-based standards.

2) A narrative of the MBSE System Model expanded from the Government Reference Architecture (GRA), specifying all subsystems & Critical Item/Computer Software Critical

Item level (CI/CSCI-level) components & interfaces. The narrative shall specify the levels (e.g., subsystem and component) at and below which the Offeror intends to control and define interfaces or components by proprietary or vendor-unique specifications.

3) An MBSE System Model in .xmi and .html format which expands the Government Reference Architecture and supports the narrative.

4) Data Rights and Licenses. The Data Rights and Licenses offered shall be provided by completing RFP Attachment 6 and Attachment 7 in accordance with Clauses H001 and H003, respectively.

2.3.2.4 Strengths

In order to address strengths, the Offeror shall adjust the appropriate contractual document(s) with change bars with the contractual commitment in Volume V, Contract Documentation.

2.4 Volume III – Past Performance

2.4.1 General Instructions

Each Offeror shall submit a past performance volume with its proposal, containing Past Performance Information (PPI) of no more than eight (8) contract references total. Offerors shall submit no more than four (4) active or completed contracts (with at least six (6) months of performance history) for the prime Offeror and no more than two (2) for each proposed critical subcontractor in the past five (5) years preceding the issuance date of this solicitation. At least two (2) contracts are requested to be for the prime Offeror, and each proposed critical subcontractor is requested to have at least one (1) contract submitted.

PPI shall include what the Offeror and joint venture member consider relevant in demonstrating their ability to perform the proposed effort in accordance with the organization and format contained in paragraph 2.4.7 Past Performance Information Tool Instructions for Offerors. This information is required on the Offeror and any critical subcontractors, teaming partners, and/or joint venture partners. A critical subcontractor is defined as an entity (subcontractor, teaming partner, and/or joint venture partner), other than the Offeror itself, that will perform aspects of the effort the Offeror considers critical to overall successful performance.

2.4.2 Past Performance Required Format

The requested past performance information shall be provided in a separate volume (i.e., 3-ring binder) labeled "Volume III - Past Performance." Business relationship information shall be provided by following the instructions in paragraph 2.4.7 for the PPI Tool that describes the proposed role of the Offeror, any joint venture member and critical subcontractors. Business relationship information must clearly communicate that the proposed critical subcontractor(s) meet the definition of a critical subcontractor established above.

Efforts submitted for proposed critical subcontractors not meeting the established definition will not be evaluated.

The volume shall contain the following sections:

• Table of Contents

• Consent Letters

• Past Performance Questionnaire Contact Listing

• Joint Venture Information (if applicable)

• Organizational Structure Change History

• Past Performance Information Tool Outputs (including Business Relationships output)

• Glossary

2.4.2.1 Early Proposal Information

In order for the Government to be able to conduct its assessment more efficiently, Offerors are requested to submit their past performance information volume 10 business days prior to the required submission date for the remainder of the proposal. Failure to submit early proposal information will not result in Offeror disqualification. Mere early submission of the Past Performance volume, by itself, is not sufficient to establish that a proposal was timely submitted.

2.4.2.2 Relevant Contracts

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. Submit PPI (reference paragraph 2.4.7 for PPI Tool instructions) on contracts completed or ongoing that you consider most relevant in demonstrating your team’s ability to perform the proposed effort. If an Offeror is submitting a proposal as a joint venture, relevant past performance information from the respective entities forming the joint venture will be considered. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, Evaluation Factors for Award (RFP Attachment 11). Specifically describe and compare the type of work and scope of effort.

Include a description of the breadth and depth of the work performed. Include a description of a relevant Associate Contractor Agreement(s) (ACA).

Not all aspects of relevancy must be included within a single contract; aspects of relevant performance may be from separate contracts. The Offeror’s past performance information shall include information about predecessor companies and subcontractors that will perform major or critical aspects of the requirement when such information is relevant to this acquisition. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, paragraphs 2.3.2.3 and

2.3.2.4. Categories of technical scope of performance and levels of importance within those categories are provided in Section M, paragraph 2.3.2.4.1. The Offeror shall identify relevant performance through a combination of contract references in those categories.

2.4.2.3 Specific Content

Offerors shall provide a narrative explaining 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, since 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.

2.4.2.4 Ordering Type Contracts Submission

If the Offeror submits a contract that 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 or 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 or task order). If a series of orders is submitted, it will count as one (1) contract reference.

When determining what order (or series of orders) to submit for evaluation, Offerors should reference Section M for details on how the Government will evaluate each submitted effort for recency, relevancy, and quality. In order to achieve optimal programmatic and logistical scope, including magnitude of effort and complexities, as described in Section M, 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 demonstrating relevancy to the instant 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 shall 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. Please ensure the information submitted 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 total dollar value, total period of performance, total quantity produced, number of disparate sites managed, and type and complexity of data deliverables for each order in the series. In the PPI Tool, submit a series of orders by entering the details of the basic ordering type contractual vehicle for the Contract Information tab and use the Program Details tab to list the orders and provide the requested information for each order.

2.4.2.5 Series of Orders

When submitting a series of orders for evaluation, the Offeror shall list the orders under the basic ordering type contractual vehicle that demonstrate relevancy, as defined in the Relevancy Matrix in Section M,

2.3.2.4.3. Per Section M, 2.3.2.4.2, Relevancy consists of not only technical complexities, but programmatic and logistical considerations. The programmatic and logistical considerations include the total dollar value, total period of performance, total quantity produced, number of disparate sites managed, and overall type and complexity of data deliverables of the order or series of orders. If an Offeror submits a series of orders for evaluation, the total dollar value of each order (in the series of orders), the period of performance dates of each order (in the series of orders), the total quantity produced on each order (in the series of orders) and the type and complexity of data deliverables for each order (in the series of orders) shall be submitted.

Caution: All orders within the series of orders being submitted should be for the same continuous technical scope demonstrating Relevancy to the instant acquisition. The Government reserves the right to request additional information from the Offeror or Points of Contact provided to verify that the series of orders is for the same continuous technical scope.

2.4.3 Subcontractor Consent

The Offeror shall submit, in addition to the information required in this section, a Subcontractor/Teaming Partner Consent Letter (Attachment L-1), executed by each of its proposed teaming member(s) and/or critical subcontractors, authorizing release of adverse Past Performance Information to the prime Offeror to allow the prime Offeror an opportunity to respond to such information.

2.4.4 Past Performance Questionnaire

The Past Performance Questionnaire (Attachment L-2) will be one means used by the Government to obtain past performance information. Offerors shall send Past Performance Questionnaires directly to the Points of Contact (POCs) for the past efforts identified. All respondents shall be instructed that all responses are to be provided directly to the Government CO. The responsibility to send out and track the completion of the Past Performance Questionnaires rests solely with the Offeror - i.e., it shall not be delegated to any other entity. The Transmittal Letter (Attachment L-3) shall be used by the Offeror in sending out the Past Performance Questionnaires. Offerors should exert their best effort to ensure that at least two (2) POCs per relevant contract submit a completed Past Performance Questionnaire directly to the Government not later than the date established in the RFP for receipt of proposals. POCs may submit their completed Past Performance Questionnaire electronically by sending to mckenna.moore@us.af.mil.

Once the Past Performance Questionnaires are completed by Offerors’ POCs, the information contained therein shall be considered source selection information and shall not be released to Offerors. Therefore, any exchange and/or contact between the Offeror, joint venture member and/or critical subcontractor and its own POCs in regards to comments made on the questionnaire is not permitted.

The Government may conduct questionnaire follow-up with any of the POCs identified in the Offeror’s Past Performance Volume. Pursuant to FAR 15.305(a)(2)(ii), the Government may obtain other information by sending out additional questionnaires and through other sources.

2.4.5 Client Authorization Letters

In the event that commercial contracts are presented as past performance sources of information, an Offeror shall submit a client authorization letter to those commercial POCs requesting/authorizing them to complete a Past Performance Questionnaire. A sample Client Authorization Letter is attached to Section L (Attachment L-4). The Offeror is required to send the client authorization letter(s) with the Past Performance Questionnaire(s) to each POC on commercial contracts. A separate copy of the client authorization letter(s) for each commercial contract shall be included in the Offeror’s Past Performance submission for the Government’s use in case additional questionnaires need to be sent by the Government after the RFP due date.

2.4.6 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 past efforts or between the 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 relevancy determination, Offerors shall include a “roadmap” describing all such changes in the organization of the Offeror’s company. This requirement applies to the prime Offeror and all critical subcontractors. 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 may consider past performance information provided by other sources, as well as that provided by the Offerors, the “roadmap” should be both specifically applicable to the efforts identified, yet general enough to apply to efforts on which the Government receives information from other sources.

2.4.7 Past Performance Information (PPI) Tool Instructions for Offerors Offerors must use the PPI Tool in order to electronically submit the Past Performance Volume in accordance with the RFP.

Downloading the PPI Tool

The PPI Tool can be downloaded by performing the following steps (if you are unable to download the Tool, contact the CO for assistance):

1. Access the FedBizOpps (https://www.fbo.gov/) website.

2. Find the solicitation posting.

3. Locate the “ppi tool” link from the “All Files” column on the solicitation’s “Notice Details” tab .

4. Select the link and save the “ppi tool” to your computer. Name the file as the prime contractor + RFP number + file extension (e.g. XYZCompanyFA861710R6158.mdb).

Note: PPI Tools saved in Microsoft Office versions 2007 and greater will be saved with “.accdb” file extension. Files saved with versions less than Microsoft Office 2007 will be saved with “.mdb” extension.

Entering Information in the PPI Tool

After selecting and saving the tool, enter information by performing the following steps:

1. Open the saved PPI Tool.

https://www.fbo.gov/

2. Select the “Options” button from the “Security Warning” banner, if applicable

. The “Security Alert” pop-up screen displays.

Figure 1: Security Alert Pop-up

Note:

• Files saved using Microsoft Office 2010 will have the “Enable Content” button on the

“Security Warning” banner and therefore will not get a Security Alert pop-up.

• If a “read only” file is opened, in order to populate data in the file, click “Save As” in the

“Read-Only” message bar. Enter the filename as the prime contractor + RFP number + file extension (e.g. XYZCompanyFA861710R6158.mdb).

3. Select the radio button “Enable this content” and then click “OK.” A setup pop-up screen displays.

Figure 2: Setup Pop-Up

4. Select the “Start” button. The “Application Setup” screen displays.

Figure 3: Application Setup Screen

5. Enter the Offeror’s Name and RFP Number and then click the “Next” button. The application setup continues.

Figure 4: Continue the Application Setup

6. Choose the appropriate option by selecting the corresponding radio button and then click the “Next” button. The “Contractor’s Menu” displays.

Figure 5: Contractor’s Menu

7. Click the “Step 1: Set up Business Relationships” button to create a business relationship, if applicable, for each contributing contracting organization before proceeding throughout the PPI Tool. Identify all prime and sub-prime organizations and categorize them according to the appropriate role in the proposed acquisition. The “Business Relationships” screen displays.

Figure 6: Business Relationships

8. Click the “New” button to create a business relationship for the proposed acquisition. An additional “Business Relationships” screen displays.

Figure 7: Enter New Business Relationship

9. Complete the fields as follows (fields marked on the screen with an asterisk ‘*’ are required):

Contractor’s Name: Self-explanatory Role in Proposed Acquisition: Choose one of the four options – Prime, Sub, Joint Venture, or

Other (Explain). An explanation comment box will display when you select “Other.”

Place of Work: Location where contractor will perform work.

Percentage of Work: Identify percentage of work contributed by specified contracting organization.

Responsibilities: Detail responsibilities of specified contracting organization.

10. Select one of the buttons at the bottom of the screen.

Add – Saves the current business relationship and allows for the addition of a new one.

Close – Cancels the current business relationship without saving.

Note: In order to edit or delete an existing business relationship in the list, double-click on it.

11. Select the “Close” button on the “Business Relationships” screen after all of the business relationships has been added.

12. Click the “Step 2: Enter Past Performance Information (PPI)” button to enter the Past Performance Information. The “Past

Performance” screen displays.

Figure 8: Past Performance

13. Click the “New” button to enter Past Performance Information for the proposed acquisition.

An additional “Past Performance” screen displays.

Figure 9: Enter Past Performance Information

14. Complete the fields on each of the tabs as follows (fields on the screen marked with an asterisk ‘*’ are required):

• Contract Information Tab (if submitting a series of orders, provide details for the ordering type vehicle here) Contractor: Select from the dropdown the appropriate contractor.

Cage Code: Self-explanatory.

Contract Number: If you don’t have a contract number, enter “N/A.”

Program Title: Enter full name of program.

Contr Agency/Customer: Enter servicing contracting agency and customer (office symbols suffice).

DUNS Number: Self-explanatory Delivery Task/Order: If the order is provided as a stand-alone reference, enter the task/call/delivery/purchase order number. If submitting a series of orders, provide the order numbers in the Program Details tab.

Contract Type: Enter Firm-Fixed-Price (FFP), Cost Plus Fixed-Fee (CPFF), Indefinite Delivery/Indefinite Quantity (ID/IQ), LH, Blanket Purchase Agreement (BPA), Cost Plus Incentive-Fee (CPIF), Cost Plus Award Fee (CPAF), etc. For additional clarification, click the question mark button.

Short Program Title (i.e., Acronym): Enter abbreviated title for the program or enter “N/A.”

Contract Dollar Value:

o Original: Input total contract dollar value, with all options if applicable, in the amount originally awarded on the referenced contract.

If ID/IQ or BPA, provide total ceiling.

If stand-alone task/call/delivery/purchase, provide amount of the individual contract.

o Current: Input total contract dollar value, with all options if applicable, as the contract stands at time of PPI submission.

If ID/IQ or BPA, provide total ceiling.

If stand-alone task/call/delivery/purchase, provide amount of the individual contract.

• Period of Performance (mm/dd/yy) o Start Date: Input start date of contract.

o Original End Date: Input original end date based on award.

o Current End Date: Input end date, as the contract stands at time of PPI submission.

o Explain the differences in Period of Performance, if applicable: Enter an explanation of the difference between “Original End Date” and “Current End Date.”

A. Program Details Tab

• Brief Description of Effort as:

o Select Prime, Sub, Joint Venture, or Other (Explain). An explanation comment box will display when you select “Other.”

o Provide a brief description of the service provided and actual work performed under this contract reference.

o *** If applicable: Provide information on problems encountered on the identified contracts. At a minimum, briefly describe the problem experienced, actions taken to alleviate the problem, and whether or not the problem was satisfactorily overcome.*** o ***If submitting a series of orders, use this tab to list the orders and provide the details for each order as described in paragraph 2.4.2.4.***

• Explain how your performance on this contract is relevant for each category, as instructed in Section M, paragraph 2.3.2.4.1. Include any unique aspects that demonstrate relevancy in this effort. Provide evidence to support such relevance to the requirements as described in the RFP.

• Include relevant information concerning your compliance with FAR 52.219-8, Utilization of Small Business Concerns, on the contract you are submitting: Enter the information if applicable.

• Identify whether a subcontracting plan was required for the contract you are submitting. If one was required, identify in percentage terms the planned versus achieved goals during contract performance. Explain why goals were not met, if applicable. Enter the information if applicable.

B. POC & Key Individuals Tab

• Key Individuals: This information will not be evaluated.

• Customer Points of Contact: Click the “Program/Site Manager,” “Contracting Officer” or “Admin POC” button for the point of contact that you would like to add, edit, or delete.

Note: For government contracts provide current information on Program Manager, Contracting Officer, and Admin POC, if available. For commercial contracts provide points of contact fulfilling these same roles, if available.

15. Select from the buttons at the bottom of the Past Performance screen:

• Save – Saves the Past Performance Information and displays the “Contract Information” tab on the Past Performance screen.

• Close – Closes the Past Performance screen. If there were any updates, a pop-up window displays asking to save before closing.

• Delete – Deletes the current PPI record. A pop-up window displays, select “Yes” to delete the record or “No” to close the window without deleting the record.

Note: In order to edit or delete an existing PPI record in the list, double-click on it.

16. Select the “Close” button on the “Past Performance Information” screen after all of the PPI records have been added.

Printing Reports and Submitting PPI Tool

In order to print the Business Relationships and PPI reports, perform the following steps:

1. Click the “Step 3: Print Report” button . A pop-up displays asking which report to print.

Figure 10: Select Report to Print

2. Select separately each of the two options, “Business Relationships” or “Past Performance.” The Business Relationships and Past Performance documents will print separately; combine the two to create your Past Performance Volume.

In order to submit the Business Relationships and PPI, perform the following steps:

3. Click the “Step 4: Submit” button .