Attachment 1 - ABAD Section L.pdf

FA5641-21-R-0001

Attachment 4

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

1.0 Program Structure and Objectives

The purpose of the USAFE-AFAFRICA Air Base Air Defense (ABAD) Indefinite Delivery Indefinite Quantity service contract is to provide the full spectrum of ABAD capabilities for USAFE-AFAFRICA, as well as other strategic and operational partners throughout the United States European Command (USEUCOM) and the United States Africa Command (USAFRICOM) areas of responsibility (AORs) to include: operations & maintenance, systems integration services, and procurement (sensors, kinetic weapons, directed energy, emerging technologies) across the EUCOM and AFRICOM AORs.

The United States Air Force (USAF) directs operations from locations worldwide. ABAD operations are conducted in, from, and through all domains (air, land, maritime, space, and cyberspace), across all phases of operations and environments. The USAF is adapting its power-projection and defense concepts to operate under a greater threat of attack. A variety of products and analysis services, such as Advisory and Assistance Services (A&AS) and the Massachusetts Institute of Technology/Lincoln Laboratory (MIT/LL), currently provide the USAF with the technical expertise necessary to create ABAD requirements. Currently, the Ramstein Air Defense System Integration Lab (RADSIL) is being built by USAFE and MIT/LL to develop the control infrastructure for an ABAD system in the EUCOM and AFRICOM AORs. The USAFE- AFAFRICA is looking for an Industry partner to maintain the RADSIL, help with the development of an ABAD system, and deploy ABAD systems in future locations. This is the intent of the ABAD IDIQ solicitation.

2.0 General Instructions

The estimated contract value of the ABAD IDIQ is $953M, which excludes any contingency costs. The contract will be awarded to a technically acceptable Offeror utilizing subjective tradeoff (price tradeoff with technical scenario approach) source selection procedures as identified in FAR 15.3, the DoD Source Selection Procedures, 31 Mar 2016, and Air Force FAR Supplement (AFFARS) Mandatory Procedures (MP) 5315.3, Source Selection, 2019 Edition.

The anticipated Period of Performance is 17 May 2021 through 16 May 2031, which includes a 120 day phase-in period. The program will be procured as a non-commercial, single-award Indefinite Delivery Indefinite Quantity (IDIQ) contract, with task orders (TOs) issued by location and the content of performance. Contract type will be determined at the TO level and will vary between Firm Fixed Price (FFP), Fixed Price Incentive Fee (FPIF), Cost Plus Fixed Fee (CPFF), Cost Plus Incentive Fee (CPIF), and Cost Reimbursable.

2.1 Proposal Compliance. To ensure timely and equitable evaluation of proposals, each Offeror shall follow these instructions and the Offeror's proposal shall include all data and information requested by this Instructions to Offerors (ITO) and shall be submitted in accordance with these instructions. 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 factors or subfactors. The offer shall be compliant with the requirements as stated in the Request for Proposal (RFP) letter, the Performance Work Statement (PWS) for the Indefinite Delivery Indefinite Quantity (IDIQ) Contract, as well as for the RADSIL Task Order (TO), Model Contract, and all other parts of this solicitation. Failure to comply with the terms and conditions of the solicitation may result in the Government determining the Offeror to be ineligible for award.

Offerors are cautioned to submit the information specified in Section L. Offerors may be asked to clarify certain aspects of their proposal. Communication conducted to resolve minor or clerical errors will not constitute discussions and the Contracting Officer reserves the right to award a contract without the opportunity for proposal revision. Offerors are NOT permitted to take exception to any terms and conditions within the RFP.

2.2 Proposal Clarity. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. Offerors shall assume that the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the Offeror’s proposal.

Offerors shall not submit elaborate brochures or documentation, detailed artwork, or other embellishments.

2.3 RFP Discrepancies/Ambiguities. If an Offeror believes that any portion of this solicitation contains a perceived error, omission, or is otherwise unclear, the Offeror shall immediately contact the Procuring Contracting Officer (PCO) and Contract Specialist via e-mail, clearly describing the portion of the solicitation in question and the impact the discrepancy or ambiguity has on the Offeror’s ability to prepare their proposal. Questions pertaining to the proposal shall be submitted no later than the date and time identified in Paragraph 3.1 below.

2.4 Point of Contact. The PCO is the sole point of contact for this acquisition. Offerors shall address any questions and concerns to the PCO as soon as possible, but no later than 26 calendar days after the posting of this solicitation, which is 4 January, 2020, at 1500 Central European Time (CET). The subject of the email shall be “Questions – FA564121R0001”. Questions shall include a reference to the specific solicitation element to which they pertain. The Government will take into consideration all questions submitted by the deadline set forth above and will answer them via posting to beta.sam.gov. Written requests for clarification and questions shall be sent to the PCO, Capt Alex Cordell at alex.cordell.1@us.af.mil. A courtesy copy shall be sent to the Contract Specialist, Mr. Ian Orton at ian.orton@us.af.mil.

2.5 Communications. All exchanges of source selection information between the Government and the Offerors will be controlled by the PCO. Source selection information will be transmitted to Offerors electronically (e.g., via email, or DoD SAFE site (safe.apps.mil/)). If transmitted via email, the transmission shall be sent and received encrypted and shall include “Source Selection Information – See FAR 2.101& 3.104” in the Subject line.

2.6 Electronic Reference Documents. All referenced documents for this solicitation can be found on beta.sam.gov, the authoritative source for Government Contract Opportunities. Offerors are encouraged to subscribe for real-time email notifications when information & amendments have been posted to the website for this solicitation. Offerors may contact the PCO if they are unable to locate any of the referenced material.

2.7 Proposal Records. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of each Offeror’s proposal.

2.8 Debriefings. The PCO will promptly notify Offerors of any decision to exclude them from the source selection; whereupon, the Offeror may request and receive a debriefing in accordance with FAR 15.505. Offerors desiring a debriefing shall make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable. Offerors are entitled to no more than one debriefing.

2.9.2 Page Size and Format

2.9.2.1 General Page & Slide Instructions. A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches unless stated otherwise within this document. Pages shall be single spaced, and the text size shall be no less than 10 point Times New Roman or Arial Font unless stated otherwise within this document. PowerPoint slides may be in a widescreen format. All proposal text shall be written in English. Offerors shall use at least 1 inch margins on the top and bottom and ¾-inch side margins for all pages unless stated otherwise within this document. Offerors shall use at least ½ margins on all sides for all slides unless stated otherwise within this document. All font, language, and margin requirements shall apply to oral presentation slides as well unless otherwise specified. Pages shall be numbered sequentially by volume, with each volume starting at page one. Pages that do not count towards the page limitation shall be numbered in a manner that clearly identifies the page as a page that does not count toward the page limitation. These page size and format restrictions shall apply to responses to ENs if clarifications are determined necessary.

2.9.2.2 Table, Chart, Drawing, and Graphic Instructions. Legible tables, charts, drawings, and graphics may be used. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. 11 x 17 may only be used for large tables, charts, drawings, and graphics;

they shall not be used for pages of text. For tables, charts, drawings, and graphics the text shall be no less than 8 point Times New Roman or Arial Font, and margins shall be no less than ½ inch on all sides unless stated otherwise within this document. An 11 x 17 inch page, as authorized under this section, will count as one page.

2.9.2.3 Submission Format. The Offeror shall submit each volume in electronic format. The proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2016, MS Office Excel 2016, PowerPoint 2016, or Adobe PDF. Exhibits, annexes, and attachments which are provided in support of a section shall be included in the electronic file for that section. If files are compressed, the necessary decompression program shall be included.

2.9.2.4 Proposal Markings. Proposals shall be marked in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. Offerors shall not include proprietary markings on attachments and documents that will become a part of the contract (i.e. Volume IV documents).

2.9.3 Cross-Referencing. To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with no cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume and/or section will be assumed to have been omitted from the proposal.

2.9.4 Table of Contents. Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tables of contents do not count against the page limitations for their respective volumes.

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

2.10 Teaming Arrangements. Offerors submitting a proposal as the prime Offeror in response to this solicitation are not permitted to submit a separate proposal under which they would be a Subcontractor, or team member to another prime. Subcontractors are permitted to support multiple primes.

2.11 Use of Non-Government Advisors.

(a) Offerors are advised that technical and cost/price data submitted to the government in response to this solicitation may be released to non-government advisors for review and analysis. The non-government advisor support will be provided by:

Massachusetts Institute of Technology Lincoln Laboratory (MIT/LL) Odyssey Systems Consulting Group

(b) Offerors shall complete paragraph (b)(2) or provide written objection to disclosure as indicated in paragraph (b)(1) in accordance with the instructions in Section L 2.11 and Section L 7.2. If the Offeror objects to the disclosure of any part of the proposal, this may result in the Offeror being determined ineligible for award if the evaluation team is unable to reasonably assess the quality of the Offeror’s proposal without the non-government advisors. If the Offeror objects to disclosure of a portion of the proposal, the consent in (b)(2) should be provided for the remainder of the proposal.

(1) Any objection to disclosure*:

(i) Shall be provided in writing to the contracting officer within 10 calendar days of RFP issuance; and

(ii) Shall include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the Offeror objects to disclosure to non-government advisors.

(2) I understand technical and cost/price data submitted to the government in response to this solicitation may be released to non-government advisors. I consent to the release of any (unless objection is provided in (b)(1) above) proprietary, confidential, or privileged commercial or financial data provided by the firm(s) named below in response to this solicitation, to non-government advisors for review and analysis; I will enter into, or have already entered into, a non-disclosure agreement(s) with the non-government advisor(s), and I will submit a copy of any such agreements to the Contracting Officer not later than the date established in this solicitation for receipt of proposals:

Offeror Firm:

Name (individual authorized to commit Offeror firm):

Title:

Date of Execution:

Signature:

* Note: The Government is the final arbiter in the disposition of any disclosure objections. If the Offeror desires to establish non-disclosure agreements with the non-government advisors, contact both the Government Contracting Officer and Government Contract Specialist with any relevant details no later than 10 calendar days prior to the proposal deadline.

2.12 Discussions. The Government intends to award without discussions, but reserves the right to conduct discussions if necessary.

2.13 Organizational Conflict of Interest. Initial notification of any actual, potential, or perceived OCI concerns shall be made to the PCO and Contract Specialist in writing as soon as the concerns become known. OCI issues include but may not be limited to the inability to render impartial assistance or advice to the Government, the inability to objectively perform contract work, or the unfair competitive advantage created by current or previous contractual efforts with the Government.

2.13.1 OCI Analysis. Offerors shall perform their own OCI analysis and submit the results of that analysis with or before proposal submission. An OCI analysis submitted prior to the proposal submission shall still be resubmitted with the proposal itself. Specifically, Offerors shall analyze the planned acquisition for actual, potential, or perceived OCI situations associated with its (or any of its teammate’s or subcontractor’s) performance under any contract it (or any of its teammates or subcontractors) has been or may be awarded by any federal agency or other entity.

The Offeror shall acknowledge all potential OCI concerns it finds that may affect the ABAD contract award even if determined to be inapplicable to the contractor, stating why the OCI does not apply to the Offeror. Offerors shall describe in detail the methodology used to identify actual, potential, or perceived OCIs. The Offeror shall also provide a detailed description of actual or potential OCIs uncovered for itself, its subcontractors, or teammates and include a classification of the OCI as biased ground rules, impaired objectivity or unequal access to non-public information. The Offeror shall directly state whether or not it finds an OCI mitigation plan to be necessary to avoid actual, potential, or perceived OCI concerns.

2.13.2 OCI Mitigation Plan. If the Offeror successfully identifies any actual, potential, or perceived OCIs for itself, its subcontractors, or teammates, the Offeror shall also submit an OCI mitigation plan with all content described by the OCI Mitigation Plan Checklist provided as an attachment to the solicitation. Any proposed avoidance or mitigation techniques shall be consistent with FAR 9.5 and the most recent decisions of the Government Accountability Office and the U.S. Court of Federal Claims. This OCI mitigation plan shall be incorporated into the resulting IDIQ contract. The Government reserves the right to require an OCI mitigation plan from an Offeror if the Government’s own OCI analysis concludes one is necessary. As the Government will accept an OCI Analysis prior to the receipt of a proposal, the requirement to provide a Mitigation Plan in a proposal, whether as a result of the Offeror’s OCI Analysis or as a result of the Government’s direction, shall not be construed as a reason to require the Government to extend the proposal deadline.

3.0 PROPOSAL INSTRUCTIONS

3.1 Proposal Due Date. Proposals are due by 0900 Central European Time (CET), 22 January 2021. Proposals shall include the PowerPoint presentations for the oral proposal.

Proposal submissions for this solicitation will be delivered electronically via email or the DoD SAFE site (safe.apps.mil/) unless the information in the oral proposal PowerPoint is classified;

no paper copies are required. Timely receipt of proposals is the sole responsibility of the Offeror.

All Offerors intending to submit a proposal in response to this solicitation via email submissions need to be addressed to the PCO, Capt Alex Cordell at alex.cordell.1@us.af.mil, and the Contract Specialist, Mr. Ian Orton at ian.orton@us.af.mil. Offerors will receive a confirmation of receipt from the Government within 2 business days. The email request shall include the name of the company, point of contact, phone number and email address. All unclassified volumes of a proposal, to include the oral presentation if no higher classification is required, shall be sent to the PCO and Contract Specialist as identified in this section regardless of whether the Offeror’s oral proposal itself contains classified information. It is the Offeror’s responsibility to follow up with the contracting officer if the Offeror does not receive a confirmation of receipt from the Government. Proposals received after 0900 CET on 22 Jan 2021 will be considered late.

The Government encourages every offeror intending to submit a proposal in response to this solicitation via DoD SAFE to request a DoD SAFE link no later than 7 calendar days prior to the proposal deadline via an email addressed to the PCO, Capt Alex Cordell at alex.cordell.1@us.af.mil, as well as to the Contract Specialist, Mr. Ian Orton at ian.orton@us.af.mil. Requests received within 7 calendar days of the proposal deadline may not be processed in an adequate time for the Offeror to submit a proposal, and the Government assumes no responsibility for late proposals received as a result of this. The email request shall include the name of the company as well as no more than five points of contact, phone numbers and email addresses. It is the Offeror’s responsibility to follow up with the contracting officer if they do not receive a DoD SAFE link. Although the DoD SAFE link will be valid for 14 calendar days after receipt, the proposal due date and time for this solicitation is 0900 CET on 22 Jan 2021. The Government shall consider proposals received after 0900 CET on 22 Jan 2021 to be late.

3.2 Oral Presentations

Each Offeror whose proposal is determined to be technically acceptable by the Government in the ‘Past Experience’ and ‘RADSIL Task Order’ (Ramstein Air Defense System Integration Laboratory) technical subfactors will be requested to present its technical approach to the Scenario section of its proposal Volume II in an oral presentation.

No presentation shall exceed 90 minutes, and each will be limited to 25 PowerPoint Slides. All presentation materials shall be included as a separate file contained in, and considered part of, proposal Volume II as indicated in Table 1. Any presentation materials used for the oral presentation shall be in the PowerPoint format, and are therefore subject to any limitations indicated in Table 1 or Section L, 2.9.2. Offerors shall not use any type of video during the oral presentation, whether as pre-recorded presentations or as part of the Offeror’s briefing materials.

Each Offeror shall be represented by no more than 3 people. All representatives shall be employees of the Offeror and shall be the intended employees on the RADSIL Task Order.

Representatives of subcontractors for the Offeror will be counted as employees of the Offeror and therefore be allowed to participate in the briefing as long as all other criteria for that member’s participation have been met. Furthermore, should an Offeror use a subcontractor as a member of the presentation team, the Offeror shall provide evidence of an agreement or partnership with the subcontractor alongside the proposal that reflects that subcontractor’s participation on the RADSIL Task Order. No external consultants will be allowed to represent an Offeror in oral solicitations. At least one member of the Offeror’s presentation team will be placed as the Program Manager of this contract. A copy of the PowerPoint presentation shall be submitted with the written proposal submission, or submitted on the same calendar day as the written proposal submission in the event a scenario contains classified material and must be transmitted separately. Any additional briefing materials shall not be allowed and will not be considered in the Government's evaluation of the proposal. Note that the Government reserves the right to record or otherwise maintain a record of the presentation. Offerors may be required by the Government to sign statements of understanding prior to the oral presentation to ensure presentation members understand the ground rules of the presentation as stated in this paragraph.

Offerors determined to be technically acceptable in Technical Subfactors 1 and 2 will be notified by phone or email of the date and time of their presentation. The Government is not required to provide an alternate timeslot to an Offeror that cannot present within their notified timeslot.

Within the proposal, the Offeror shall identify the name, phone, and e-mail of the individual to whom the Government should give notice for oral presentations and provide the names of the individuals that will be giving the presentation.

The Government may ask clarifying questions immediately after the conclusion of the Offeror’s presentation. If the Government requires further clarifications on any part of the Offeror’s oral proposal, the Government will contact the Offeror and schedule a date and time for those clarifications.

3.2.1 Classified Information

The Oral Proposal, to include the PowerPoint and the briefing, may include content up to but not to exceed the Secret No Foreign (S//NF) classification level. No other area of the Offeror’s proposal shall contain any classified content. All classified communications and content shall be clearly marked in accordance with (IAW) the applicable Department of Defense Security Classification Guides.

Where the Offeror intends to include classified information in its oral presentation, the Offeror shall provide it as a classified supplement and provided to the PCO at the following email address: alex.m.cordell2.mil@mail.smil.mil. Presentation format shall conform to the same directions as those given in this ITO for unclassified portions.

Should the presentation materials be considered unclassified but the Offeror intends to speak on classified content as part of its oral presentation, this intent shall be explicitly identified within the first two slides of the presentation materials to ensure an appropriate communication channel is being used. This method shall also necessitate the Offeror follow Secure Virtual Conference (S-VTC) instructions as indicated in Section L 3.2.2.

3.2.2 Oral Presentation Format

The Offeror shall provide their presentation to the Government via a Virtual Conference (VTC).

The Offeror shall specify whether the presentation will be provided at the unclassified or classified level. If the VTC is at the unclassified level, the Government will coordinate with the Offeror the meeting information and a technical check prior to the meeting. If the Offeror requires an S-VTC for a classified presentation, the Offeror will be responsible for providing the facility from which they will be conducting the S-VTC at the time of their proposal submission.

If the Offeror does not have access to an S-VTC, the Offeror shall contact the PCO to arrange for an S-VTC to be provided by the Government. Costs incurred by traveling to and from any S- VTC location provided by the Government shall be solely at the Offeror’s expense. The Government is not obligated to extend deadlines as a result of either an Offeror’s inability to procure an S-VTC location, or the Government’s inability to provide an S-VTC location in a timely manner.

3.3 Cost/Price Related Data

In accordance with FAR 15.403-1(b) and 15.403-3(a), the Government shall require data other than certified cost or pricing data to support a determination of price reasonableness and cost realism. Data shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient data available to determine price reasonableness or cost realism and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit additional cost data.

All pricing information shall be addressed in the Cost/Price Volume. The Offeror shall prepare and submit the cost/price proposal in Microsoft (MS) Office Word and Excel 2016 or later native formats. Files received in any other format are unacceptable. The Offeror is encouraged to provide narrative substantiation and rationale in MS Word and any numerical source data, cost summaries, tables, calculations, or similar detailed information in MS Excel. For information submitted in MS Excel, the Offeror shall use formulas and functions to the maximum extent practical and avoid using output type “value only” cells. If links are utilized, the Offeror shall provide those reference files. Spreadsheets and cells within spreadsheets shall not be protected.

Worksheets within spreadsheets shall not be hidden.

Numerical data presented in the MS Word narrative that corresponds to a MS Excel submission must be clearly referenced. Numerical data pasted into MS Word as a picture out of another file is discouraged unless it is clearly referenced to a corresponding MS Excel file or its derivation is unambiguous. The Offeror is responsible for ensuring that the information provided, whether in MS Word or MS Excel, is traceable throughout the Cost/Price Volume and the remainder of the proposal, as applicable.

3.4 Communications

Exchanges of source selection information between the Government and Offerors will be controlled by the PCO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR

2.101 & 3.104” in the Subject line. Otherwise, source selection information will be transmitted via the DoD SAFE site (safe.apps.mil/).

3.5 Organization/Number of Copies/Page Limits

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

Table 1 – Proposal Organization

VOLUME

ITO

Paragraph Number

Proposal Section TITLE PAGE LIMIT

I Executive Summary

4.2 Offeror Company Information No Page Limit

4.3 Financial/Other Resources No Page Limit

2.13 Organizational Conflict of Interest No Page Limit

II

Technical

5.2.1 Subfactor One (Past Experience) 5

5.2.2 Subfactor Two (RADSIL Task Order) 25

5.2.3 Subfactor Three (Scenario) 25 (PowerPoint

Slides)

III

Cost/Price 6.0 Cost/Price Volume No Page Limit

IV

Contract

Documentation

7.1 Accounting System No Page Limit

7.2 Non-Government Advisor Documentation No Page Limit

file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc#T2101 file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc#T2101 file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b3104

3.5.1 Page Limitations

Page and slide limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Each page or slide in a proposal shall be counted towards its respective limitation except the following: Title Pages, Tables of Contents, Statements of Work or Performance Work Statements, Glossary of Abbreviations or Acronyms.

4.0 Volume I - Executive Summary

4.1 Volume I Organization. This volume shall be organized according to Table 1 above.

4.2 Offeror Company Information. The Offeror shall complete Attachment 11, Offeror Company Information Form, as provided with the solicitation. The Offeror shall provide all information on the form. The proposal validity statement shall be valid no less than one calendar year after the proposal deadline. The Offeror shall be registered in the System for Award Management (SAM.gov) prior to award for the duration of the acquisition. If the Offeror’s SAM.gov registration expires prior to the proposal validity date, the Offeror shall assert its intent to renew the registration.

4.3 Other Information. To assist the PCO in making the responsibility determination prior to contract award (in accordance with FAR 9.1, Responsible Prospective Contractors, as supplemented by the DoD FAR Supplement (DFARS) 209.1), the Offer shall provide financial/other resource information.

4.3.1 Financial/Other Resources. In accordance with FAR 9.104-1(a), the Offeror shall provide a written statement explaining the Offeror’s ability to obtain required resources to perform the contract requirements. The Offeror shall also provide evidence to support the explanation.

Evidence may include official letter(s) from (a) financial institution(s) demonstrating that the Offeror has the financial resources required to cover all financial commitment. In accordance with FAR 9.104-1(e), the Offeror shall provide an explanation of the Offeror’s organizational controls and measures. At a minimum, the Offeror shall address their accounting controls, operational controls, quality assurance measures, and safety program. The Offeror shall also provide evidence to support the explanation. Evidence may include a list of organizational policies or Standard Operating Procedures (SOPs) which demonstrates the organizational controls and measures of the Offeror. If a list is provided, the Offeror shall include the title of each policy or SOP, the date of each document, and a brief description of each document. The Offeror shall also define which element of FAR 9.104-1(e) the policy or SOP applies to.

4.3.2 Proposal Information. The Offeror shall complete Attachment 17 – Cross Reference Matrix, to correlate the Offeror’s proposal with the solicitation documentation. The Offeror’s proposal information related to technical Subfactor Three (Scenario) shall reference the associated PowerPoint slide as applicable, however Section M 3.3’s restriction on what slides will be considered for evaluation still applies.

5.0 Volume II - Technical

5.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, Offerors shall provide as specifically as possible the requested information or actual methodology it would use for meeting or exceeding the technical subfactors. All the requirements specified in the solicitation are mandatory. By submitting a proposal, an Offeror is representing that it will perform all the requirements specified in the solicitation. Technical proposals should not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

5.2 Subfactors One, Two, & Three:

5.2.1 Subfactor One (Past Experience)

The Offeror shall submit a minimum of one Past Experience example concerning Integration, one concerning Program Management, and one concerning EUCOM Status of Forces Agreements (SOFA). The Offeror may submit three separate contracts, one contract that includes all three pieces, multiple contracts per Past Experience category, or any combination in between to meet the criteria of Section M 3.1.1., 3.1.2., and 3.1.3.

However, if the same contract is meant to cover more than one Past Experience criteria, that same contract shall be submitted multiple times. For example, if a contract covers all three Past Experience criteria, that contract shall be submitted thrice, once for Integration, once for Program Management, and once for SOFA Experience. If the Offeror submits multiple contracts for a single Past Experience category, the Government may evaluate only the first contracts listed whose periods of performance add up to meet the minimum timeline requirement. For example, if an Offeror submits five contracts, each with a six-month Period of Performance, to meet the criteria of 3.1.1 which requires two years of experience, only the first four contracts submitted may be evaluated. Subsequent contracts may not be evaluated, even if Past Experience examples provided earlier in the Offeror’s documentation fail to meet any other Past Experience evaluation criteria.

Additionally, each Task Order under a contract vehicle may count as a separate instance of Past Experience as long as each individual Task Order meets all other required criteria, to include dollar value. Past Experience submitted to satisfy this requirement may be either from the Offeror or from a subcontractor. However, any subcontractor for whom the Offeror is relying upon for Past Experience shall be a major subcontractor responsible for a minimum of 15% of the total work to be performed on the initial Task Order (“RADSIL Task Order”). If an Offeror is using a subcontractor’s Past Experience, the Offeror must also submit evidence of an agreement or partnership between the Offeror and the subcontractor that would allow the Offeror to utilize such Past Experience.

Each contract listing shall contain the following elements: the contract number and task order number as applicable, contract period of performance, the performance work statement or statement of work for the provided contract, the Offeror’s role in the contract, a description of how the experience falls within the scope of the ABAD requirement, at least one customer points of contact (POC), POC titles, and current POC telephone numbers and e-mail addresses.

5.2.1.1 Integration: The Offeror shall submit evidence of at least 2 years of Past Experience (instances where the Offeror performed as a key subcontractor or a prime) on a contract performed within the previous 5 years from the date of issuance of the solicitation, where the Offeror is or was responsible for at least 2 instances of integrating radar, electro-optical, mobile sensing, and/or multimodal sensor systems into a larger architecture. A “larger architecture” is defined as at least three systems within the scope of the ABAD requirement above networked together in the same command and control architecture. The contract value shall be or have been greater than or equal to $10,000,000. The 2 instances of integration experience do not have to be from one contract, but if each instance submitted is from a separate contract then each contract must meet the $10,000,000 threshold.

5.2.1.2 Program Management: The Offeror shall submit evidence of at least 3 years of contracting experience (instances where the Offeror performed as a key subcontractor or a prime) on an operation and maintenance contract performed within the previous 5 years from date of issuance of solicitation, where the Offeror is or was responsible for performing Program Management duties. “Program Management” is defined as managing the cost, schedule, and performance of a contract. The contract value shall be or have been greater than or equal to $20,000,000.

5.2.1.3 EUCOM SOFA Experience: The Offeror shall submit evidence of at least 2 years of overseas service contracting experience (instances where the Offeror performed as a key subcontractor or a prime) on a contract performed within the previous 5 years from date of issuance of solicitation, where the Offeror is or was responsible for successfully being accorded SOFA status for its personnel from foreign governments in the EUCOM.

The contract value shall be or have been greater than or equal to $5,000,000.

5.2.2 Subfactor Two (RADSIL Task Order)

The technical volume of the RADSIL Task Order proposal should be specific and complete. Legibility, clarity, and coherence are very important. Information the Offeror deems appropriate to address the technical criteria should be included in the proposal in an orderly format and be consistent with the evaluation criteria for award set forth in this solicitation. The Offeror must clearly demonstrate that the Offeror has a thorough understanding of the requirement for the accomplishment of this effort, and as specifically as possible provide the actual methodologies that will be used to accomplish/satisfy the ABAD requirement.

The Offeror shall provide a system engineering plan, a staffing plan, a maintenance and sustainment plan, and an ABAD operation support plan containing the information listed below.

The Offeror shall provide a system engineering plan to include: (1) the Offeror’s plan for understanding of the Ramstein Air Defense System Integration Laboratory (RADSIL),

(2) how the contractor will document the RADSIL, and (3) how they will develop the theater wide ABAD system, (4) a plan for how the Offeror will take the theoretical three phase ABAD plan and turn it into an executable program, (5) how the Offeror will onramp emerging technologies and determine their relevance to mission performance, and (6) the Offeror’s system engineering approach to executing studies.

The Offeror shall provide a staffing plan of necessary personnel, as identified in Section 3 of the RADSIL TO PWS, to include: (1) all necessary personnel with qualifications and a plan on how the personnel will operate and maintain the RADSIL, (2) a personnel mix with qualifications within a personnel matrix that shows all the required skills identified within the RADSIL Task Order PWS are being met, (3) identification of any additional skills being provided that are not identified in the PWS, and (4) a plan to operate and maintain the RADSIL with the necessary manpower to operate and maintain the system during the normal duty day (Monday-Friday from 0730-1630 Central European Time).

The Offeror shall provide a maintenance and sustainment plan of the RADSIL hardware and software architecture, to include: (1) how the Offeror will maintain and sustain the RADSIL hardware and software architecture, (2) how the Offeror will return the system to full mission capability during any hardware or software failures as identified in Sections 3.1.4 and 3.1.5 of the RADSIL TO PWS, and (3) how the Offeror would develop and manage the Obsolescence Management Plan as identified in Sections 3.1.6 and 3.5 of the RADSIL TO PWS. Commercial techniques for provisioning COTS and custom software may be used.

The Offeror shall provide an operations support plan, to include: (1) how the Offeror will support threat system/equipment modifications, upgrades, modernizations, additions, replacements, and removals, (2) how the Offeror will adapt to new techniques and technology to keep the Ramstein ABAD capabilities abreast of mission requirements, and

(3) a description on how the Offeror will meet sections 3.3 and 3.4 of the RADSIL TO

0001 PWS.

5.2.3 Subfactor Three (Scenario)

The Offeror shall present an oral presentation that contains the information necessary to address the requirements of the scenario described in section 5.2.3.1. The presentation shall be in an orderly format. The Offeror shall provide a solution that includes the information provided in section 5.2.3 and meets or exceeds the thresholds provided in Section M 3.3. The presentation shall also demonstrate the Offeror’s thorough understanding and knowledge of the scenario and solution to the scenario, and present as specific as possible the actual methodologies that will be used to meet or exceed the Success Criteria in Section M 3.3. The oral presentation shall include a PowerPoint presentation that shall not exceed 25 slides. The PowerPoint presentation is part of the proposal and shall be submitted at the same time as the written proposal, or on the same calendar day as the written proposal if the information must be transmitted separately due to classified information.

5.2.3.1 The scenario presentation shall include:

• An Operations View (OV) of a base defense network that would be able to respond to and counter the threat.

• A detailed list of the systems the Offeror would use, with a brief description of each system. This can include currently available Commercial Off The Shelf (COTS) systems or any other systems that could be modified or available within the next three years.

• A list of potential software tool/systems that the Offeror would employ to maintain and operate the system.

• A manpower estimate to include necessary personnel to maintain and operate the system and a brief explanation of the required skill sets.

• A simplified cost estimate of this system which shall include the cost to the Government of all proposed equipment, the cost of 1 year of operations and maintenance, along with any other necessary costs. Should the solution incorporate leasing, the duration of the lease in relation to the cost estimate shall not exceed 10 years. Only 1 slide is authorized for the cost estimate. The Government is requesting a cost estimate to determine the affordability of the solution. The cost estimate will not be used for the Cost/Price Factor evaluation.

5.2.3.2 Scenario: A United States Air Force Base located within Germany has received multiple intelligence reports that it is expected to come under attack from multiple airborne threats. Details of the threats are as follows:

Attack 1:

• Within the first hour the base is expecting air intrusions by 15 separate Unmanned

Aerial Systems (UAS). It is anticipated that the UAS systems will be of a Dà- Jiāng Innovations (DJI) variant.

• These UAS have the potential to threaten the base from any direction.

• No more than 3 UAS will penetrate the same section of the base (100 meter section as measured horizontally and extending up to 1,000 meters Above Ground Level (AGL)) at the same time.

• Multiple sections will not be penetrated concurrently.

Attack 2:

• Within the second hour the base is expecting an attack by 5 cruise missiles.

• The cruise missiles are of the AS-23A variant.

• There will be a minimum of 30 seconds between each cruise missile arrival.

• The cruise missiles will strike various sections of the base.

Assumptions:

• The system will be employed on a Main Operating Base (MOB) in Germany and all standard infrastructure available on a base can be utilized by the Offeror (power, fiber, water, facilities, base security).

• The MOB fence line fits within a 10 km diameter circle. (Ref. Figure 1).

• The MOB sits on level earth that is perfectly flat within a 20 km diameter circle.

(Ref. Figure 1).

• Outside the 20 km diameter flat circle, the surrounding terrain is rolling hills with no hill exceeding an elevation of 200M. (Ref. Figure 1).

• The system can be operated by Air Force personnel with a five skill level training equivalent.

• There is no Government Furnished Equipment provided for this system.

Figure 1

6.0 Volume III – Cost/Price Volume

The cost/price volume contains no page limitations. However, all information provided must relate to cost/price. Cost/price information submitted outside of the cost/price proposal volumes will not be evaluated.

The cost/price volume shall consist of the following sections:

6.1 General Information

6.1.1 Table of Contents

6.1.2 Glossary of terms and abbreviations

6.1.3 Estimating System

The Offeror shall provide a summary description of its standard estimating system or methodology. The summary description shall cover separately each major cost element (e.g.

Engineering Labor, Manufacturing Labor, Indirect Costs, Other Direct Costs, Overhead, General & Administrative (G&A)). Identify any deviations from stated standard estimating procedures in preparing this cost proposal volume. Indicate whether Government approval of stated system was obtained and, if so, provide evidence of such approval.

6.1.4 Purchasing System

The Offeror shall provide a summary description of standard purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, and what provision is made to ensure quantity and other discounts). Identify any deviations from stated standard procedures in preparing this proposal. Indicate whether Government approval of stated system was obtained and, if so, provide evidence of such approval.

6.1.5 Cost Accounting Standards (CAS) Disclosure Statement.

6.1.6 Subcontractor Information

The Offeror shall provide a list of all subcontractors, teaming partners, and/or joint venture partners.

6.1.7 Ground Rules and Assumptions

The Offeror shall provide an explanation of ground rules and assumptions necessary to fully understand the cost estimates. Topics to be addressed should include, but are not limited to:

business base, labor and overhead rates, cost-sharing arrangements, prime-subcontractor relationships, and cost/price escalation.

6.2 Ramstein RADSIL Task Order

(1) IAW FAR 15.403-5(b)(2), the Contracting Officer has determined the use of a specific format is not required for the submission of data other than certified cost or pricing data.

Therefore, Offerors may submit data other than certified cost or pricing data in their own unique format to support the proposed cost and fee associated with the Ramstein RADSIL Task Order.

(2) Although not required for data other than certified cost or pricing data, the Government recommends Offerors utilize Table 15-2 -- Instructions for Submitting Cost/Price Proposals When Certified Cost or Pricing Data Are Required, located at FAR 15.408 and the Proposal Adequacy Checklist located at DFARS 252.215-7009 in the development of the Ramstein RADSIL Task Order cost proposal. In the event certified cost or pricing data becomes required, the Offeror shall conform to the Proposal Adequacy Checklist.

(3) Offerors shall submit cost/price proposals in accordance with the tasks required by the Ramstein RADSIL PWS, RFP Attachment 7.

(4) The cost summary submitted by the Offeror shall include: (1) Total Task Order Cost

Summary, (2) Task Order Cost by year Summary, (3) Task Order Cost by CLIN summary, and (4) Task Order Cost by CLIN by year Summary.

(5) The Offeror shall use the CLIN structure below for developing the cost summaries:

o CLINs 013X– Labor (CPFF) o CLIN 054X – Travel (CR) o CLIN 034X – Material (CR) o CLIN 074X – Relocation & Education (CR) o CLIN 085X – Data (NSP)

(6) The Offeror shall use predetermined values for CLINs 0540, 0541, 0542, 0543, 0544

Travel; 0340, 0341, 0342, 0343, 0344 Material; and 0740, 0741, 0742, 0743, 0744 Relocation & Education for evaluation purposes. Offerors shall not apply indirect rates, fee, FCCOM, or any other costs to the predetermined totals listed below. Offerors shall include the cost reimbursable (CR) values below in the task order cost summaries to accurately depict the total proposed cost/price of the initial task order. The predetermined CR CLIN value to be used in Offeror proposals are stated below:

• 0340 Material Base Year $350,000

• 0540 Travel Base Year $135,000

• 0740 Relocation/Education Base Year $300,000

• 0341 Material Option Year 1 $350,000

• 0541 Travel Option Year 1 $145,000

• 0741 Relocation/Education Option Year 1 $200,000

• 0342 Material Option Year 2 $350,000

• 0542 Travel Option Year 2 $155,000

• 0742 Relocation/Education Option Year 2 $200,000

• 0343 Material Option Year 3 $350,000

• 0543 Travel Option Year 3 $165,000

• 0743 Relocation/Education Option Year 3 $200,000

• 0344 Material Option Year 4 $350,000

• 0544 Travel Option Year 4 $175,000

• 0744 Relocation/Education Option Year 4 $200,000

(7) RADSIL TO Labor Hours, Rates, and Escalation. The following provides guidelines for the major cost elements normally associated with the buildup of labor rates and required support documentation for RADSIL TO, which is intended to be CPFF. The following breakout is required from Offerors. Offerors shall provide complete breakouts of proposed labor for RADSIL TO.

a. The Offeror shall propose Cost Plus Fixed Fee (CPFF) labor hours and rates for all labor categories associated with CLINs 0130, 0131, 0132, 0133, and 0134 (as indicated in Attachment 5 ‘RADSIL Task Order’) on the initial task order. Offerors shall not propose any labor category not included in Attachment 14 ‘IDIQ Labor Category List’.