Attachment 1 - Draft Section L ABAD.docx

SECTION L

Instructions, Conditions, and Notices to Offerors or Respondents

1.0 Program Structure and Objectives

The purpose of this acquisition is to develop, create, integrate, and maintain a new Air Base Air Defense (ABAD) system for USAFE-AFAFRICA. This will be a sole source Indefinite Delivery and Indefinite Quantity contract. Task Orders will be issued off of the IDIQ to support ABAD requirements. The end goal for this acquisition is to emerge with a functional Air Base Air Defense system capable of augmenting the United States’ defensive posture.

2.0 General Instructions

This is a best value source selection conducted in accordance with Federal Acquisition Regulation (FAR) 15.3 as supplemented.

2.1 Proposal Compliance. To ensure timely and equitable evaluation of proposals, each Offeror must 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. 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 Sample ABAD Task Order (TO), Model Contract, and all other parts of this solicitation. If an offer fails to conform to the instructions provided in this ITO, the Government may deem it non-responsive and the Offeror may be deemed ineligible for award.

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 2.4 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 1500 Central European Summer Time (CEST), TBD 2020. The subject of the email shall be “Questions – FA564120R0007”. 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 must 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 has 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. 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 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 or slides. 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. Offerors shall use separate files for each proposal volume. Offerors shall also use separate electronic files for each proposal section listed in Table 1 to permit rapid location of all portions of the proposal. 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) The MITRE Corporation Odyssey Systems Consulting Group

(b) Offerors shall complete paragraph (b)(2) or provide written objection to disclosure as indicated in paragraph (b)(1). 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 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 do not require, 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 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 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. 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 Summer Time, (insert date). 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. 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 they do not receive a confirmation receipt. Proposals received after (insert date and time) will be considered late.

All offerors intending to submit a proposal in response to this solicitation via DoD SAFE shall request a DoD SAFE link no later than (insert date and time) 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. The email request shall include the name of the company, point of contact, phone number and email address. 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 days after receipt, the proposal due date and time for this solicitation is (insert date and time). Proposals received after (insert date and time) will be considered late.

3.2 Oral Presentations

Each offeror that has a proposal deemed technically acceptable by the Government in the ‘Past Experience’ and ‘RADSIL Task Order’ (Ramstein Air Defense System Integration Laboratory) technical subfactors will be contacted 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, 3.2. Offerors shall not use videos during the oral presentation. Each offeror shall be represented by no more than 3 people. All representatives shall be employees of the offeror and will be employees on the RADSIL Task Order. 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 would ensure that member’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 shall intend to 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 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. Only the information and slides covered in the presentation will be evaluated: In other words, any chart that is not briefed during the established time limit will not be evaluated, and any information contained on the slides that was not orally briefed will not be evaluated. Note that the Government reserves the right to record or otherwise maintain a record of the presentation. Offerors may be required to sign statements of understanding prior to the oral presentation to ensure presentation members understand the terms of the presentation.

The Government will notify offerors, deemed technically acceptable in Technical Subfactors 2 and 3, by phone or email of their presentation timeslot. 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 three individuals that will be giving the presentation.

If the Government requires clarifications on any part of the offeror’s oral proposal, the Government will contact the offeror and schedule an additional timeslot 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 IAW the applicable Department of Defense Security Classification Guides.

Where classified information is required in the response, it shall be provided 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 identify if 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 must provide the facility for 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 to compensate for either an offeror’s lack of its own S-VTC location, nor 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), data other than certified cost or pricing data will be required 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 a format other than requested 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

Number

I Executive Summary

II

Technical

III

Cost/Price

IV

Contract Documentation

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 and excess paper copies will be returned to the offeror as soon as practicable. 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. The Offeror shall provide all information on the form. The proposal validity statement shall be valid through TBD 2021. 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.

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, provide as specifically as possible the requested information or actual methodology you would use for meeting or exceeding the technical subfactors. All the requirements specified in the solicitation are mandatory. By submitting a proposal, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for the proposal to tell the Government so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

5.2 Subfactors One, Two, & Three:

5.2.1 Subfactor One (Scenario)

The Offeror shall present an oral presentation that contains the information necessary to address the requirements of the scenario provided in section 5.2.1.1. The presentation shall be in an orderly format and be consistent with the evaluation criteria for award set forth in this solicitation. The Offeror shall include the information provided in section 5.2.1.1 in its solution, and clearly provide a solution that will meet or exceed the thresholds provided in Section M. The Offeror shall also demonstrate that it has a 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. 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.1.1 The scenario presentation shall include:

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

· An overall detail list of the systems that will be used 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 would be employed to maintain and operate the system

· A manpower estimate to include required personnel to maintain and operate the system and a brief explanation of the their required skillset

· One (1) simplified cost estimate of this system to include 1 year of operations and maintenance along with any other necessary costs. Only 1 slide is authorized for the cost estimate. This cost estimate is only to ensure the solution will be affordable to implement, and will not be used for the Cost/Price Factor evaluation.

5.2.1.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 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, but will not be able to achieve an altitude greater than the current capability of a DJI drone

· 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 locations on 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 (power, fiber, water, facilities, base security)

· The MOB fence line fits within a 10 km diameter circle

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

· There is no Government Furnished Equipment available for this system

5.2.2 Subfactor Two (Past Experience)

The offeror shall submit a minimum of one Past Experience example for Integration, one for Program Management, and one for EUCOM Status of Forces Agreements (SOFA) Experience. Should one contract suffice for more than one Past Experience category, that one contract may be used for both or all past experience requirements. However, the Offeror is required to submit the contract multiple times, once for each category. Multiple contracts may be submitted to fulfill the minimum time requirement of each past experience category. 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 from either the Prime or a Subcontractor. However, if an offeror is using a subcontractor’s past experience, the offeror must also submit evidence of an agreement or partnership 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, the offeror’s role in the contract, a description of how the experience is relevant to the solicitation criteria, 1 customer points of contact (POC), POC titles, and current POC telephone numbers and e-mail addresses.

5.2.2.1 Integration: The Offeror shall submit evidence of at least 2 years of contracting experience (instances where the Offeror performed as a key subcontractor or a prime) 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, with a contract value greater than or equal to $10,000,000. The 2 instances of integration experience do not have to be from one contract.

5.2.2.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) within the previous 5 years from date of issuance of solicitation, where the Offeror is or was responsible for performing Program Management duties on an operation and maintenance contract on a $20,000,000 program or greater.

5.2.2.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) within the previous 5 years from date of issuance of solicitation, where the Offeror is or was responsible for successfully obtaining SOFA, or equivalent agency, (e.g., Department of State) in EUCOM on a $5,000,000 or greater program.

5.2.3 Subfactor Three (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 detailed systems engineering plan on how they will understand and document the current Ramstein Air Defense System Integration Laboratory (RADSIL). The offeror shall also define how they will develop the theater wide ABAD system. The systems engineering plan shall provide an understanding of the RADSIL to include a basic understanding of the current architecture, a plan for how the offeror will take the theoretical three phase ABAD plan and turn it into an executable program, how the offeror will onramp emerging technologies and determine their relevance to mission performance, and the offeror’s system engineering approach to executing studies.

The offeror shall provide a staffing plan of necessary personnel, to include their qualifications, to operate and maintain the RADSIL as identified in Section 3 of the TO 0001 PWS. This plan shall include the necessary manpower to operate and maintain the system during the normal duty day (Monday-Friday from 0730-1630). The plan shall include a staffing matrix identifying how all required skills will be provided.

The offeror shall provide a detailed maintenance and sustainment plan of the RADSIL hardware and software architecture and return the system to full mission capability during any hardware or software failures as identified in Section 3.1.4, 3.1.5, 3.1.6, and 3.5 of the RADSIL TO 0001 PWS. Modern techniques for provisioning COTS and custom software may be used.

The offeror shall provide a detailed ABAD operations support plan to support Section 3 sections 3.3 and 3.4 of the RADSIL TO 0001 PWS. The proposal shall support threat system/equipment modifications, upgrades, modernizations, additions, replacements or removals. The contractor shall adapt to new techniques and technology to keep the Ramstein ABAD capabilities abreast of mission requirements.

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 standard estimating system or methods. 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 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 0001

(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 0001.

(2) Although not required for data other than certified cost or pricing data, the Government recommends offerors utilize Table 15-2 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 0001 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:

· CLIN 0001 – Labor (CPFF)

· CLIN 0002 – Travel (CR)

· CLIN 0003 – Material (CR)

· CLIN 0004 – Relocation (CR)

· CLIN 0005 – Data (NSP)

(6) The offeror shall use predetermined values for CLINs 0002 Travel, 0003 Material, and 0004 Relocation for evaluation purposes. The values will be TBD for CLIN 0002, TBD for CLIN 0003, and TBD for CLIN 0004.

(7) TO 0001 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 TO 0001, which is intended to be CPFF. The following breakout is required from prime offerors. Prime offerors shall provide complete breakouts of proposed labor for TO 0001.

a. The offeror shall propose Cost Plus Fixed Fee (CPFF) labor rates for all labor categories associated with CLINs 0001, 0011, 0021, 0031, and 0041 (as indicated in Attachment 5 ‘Task Order 0001’) on the initial task order. The offeror’s cost/price proposal shall indicate the labor rate build up and yearly escalation as indicated below.

b. Base Labor Rates: Show base labor rates associated with each labor category. Base rates are the hourly rates that the employees will be paid for performance under the basic contract. A labor rate shall be proposed for each labor category along with the basis and rationale for all proposed base labor rates. The most common basis for a proposed base rate is the actual rate the employee is currently being paid. When a composite base labor rate is proposed, a separate worksheet that identifies the individuals, their rates, and the weighting assigned to each rate to arrive at the single composite rate shall be provided. If an individual in a particular labor category is currently not employed, a verifiable method used to establish the reasonableness of the proposed rate shall be provided, e.g. Salary.com, quotes, etc. Supporting payroll data and rationale for all position classifications anticipated to be used under the contract shall be submitted as part of the proposal.

c. Base Labor Rate Escalation: Current rates will require adjustment for annual cost of living increases. Base rate adjustments can occur when calculating year one rates if employees would normally receive pay increases prior to the end of the first contract year. Base rates for contract out-years will require escalation adjustments to reflect what employees will receive for those periods. The methodology used to escalate out-year rates shall be provided to include the basis for the escalation factors used and the date that pay increases are effective.

d. Indirect Rates: Common indirect rates are Labor Overhead, Fringe Benefits, General & Administrative (G&A), and Facilities Capital Cost of Money (FCCOM). In the proposal, show each individual rate, as applicable, and describe the allocation base. The allocation base is the cost category that the rate is multiplied by to calculate the indirect dollars. An example is a labor overhead rate applied to direct labor dollars; the latter being the allocation base. If current Forward Pricing Rate Agreements (FPRAs) or approved provisional billing rates are available, provide a copy of the FPRAs or approved provisional billing rates in addition to identifying the cognizant Administrative Contracting Officer (ACO) and his/her location. If a current FPRA or approved provisional billing rates is not available, provide the name and address of any Government audit agency or independent audit firm that has conducted an audit and include a copy of said audit in the cost/price proposal. If no such audit exists, so state.

e. If no indirect rate audit information is available, financial data and the methodology used to calculate the proposed indirect rates shall be submitted. Identify costs not allowed by FAR 31.2 as well as the build-up of the indirect rates, including applicable pools and bases. In addition, provide actual indirect rates for the previous three years.

f. Fee Rates: Fee rates/dollar values shall be indicated separately.

g. Offerors proposing as a Joint Venture (JV) shall use one of the following two methods to propose based upon the JV’s make-up. If the JV is populated with employees from each member of the JV and will be dedicated to the basic contract, then new base labor rates and indirect rates based on that situation would be proposed. If the JV remains as separate entities, then base labor rates and indirect rates would be proposed for each member of the JV.

h. Offerors shall submit a list of the proposed subcontractors, teaming partners, and inter-divisional transfers for the initial Task Order showing (a) the supplier, (b) description of effort, (c) type of contract, (d) price and hours proposed by each, (e) price and hours included in prime’s proposal to the Government, and (f) commercial item/service determination support, if applicable.

i. For subcontracted efforts that are competed, prime offerors shall provide competitive pricing. However, for non-competitive subcontracts, a complete proposal breakdown is required. Prime contractors shall provide clear rationale and proposal evaluation for any subcontracted efforts that are not competed, IAW FAR 15.404-3. In addition to a breakout of labor as described above, non-competitive subcontractors must provide complete breakouts of any other costs anticipated under this effort, i.e. travel, material, lower-tier subcontracts, etc. Subcontractors may provide cost information directly to the Government Contracting Officer.

6.3 General Cost/Price Data Information

(1) Offerors shall submit the cost/price volumes electronically. Electronic copies of supporting documentation must lend themselves to review and analyses by the Government; therefore, the Excel spreadsheets must not be submitted in Portable Document Format (PDF) or with locked spreadsheet cells.

(2) Offerors shall provide a working cost model in Microsoft Excel format to support proposed costs associated with the Ramstein RADSIL CPFF Task Order 0001 cost/price proposal.

(3) Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost position. All data relating to the proposed cost/price, including all required supporting documentation, shall be included in the section of the proposal designated as the cost/price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

(4) All dollar amounts provided shall be rounded to the nearest dollar. All labor rates shall be rounded to the nearest penny.

7.0 Volume IV Contract Documentation

7.1 Accounting System

a. Per Federal Acquisition Regulation (FAR) 16.301-3(a)(3) - A cost-reimbursement contract may be used only when the contractor’s accounting system is adequate for determining costs applicable to the contract. The acceptability of an accounting system is determined based upon a pre-award survey.

b. It is anticipated that CPFF type task orders may be awarded under any resulting contract and Prime contractors must have an accounting system that has been determined adequate by DCAA for accumulating and reporting incurred costs under cost type contracts in order to receive a cost-reimbursement task order.

c. The Offeror shall provide evidence of an adequate accounting system as determined by the DCAA.

d. All offerors should complete the Preaward Survey of Prospective Contractor Accounting System Checklist located at http://www.dcaa.mil under checklist and tools to ensure an understanding of the requirements and to ensure the offeror is ready for DCAA to come in and perform an audit if not yet approved.

e. All offerors shall complete Pre-Award Audit Registration regardless of whether it has an approved accounting system.

f. Information concerning DCAA may be found at http://www.dcaa.mil. Specific information concerning requirements for an acceptable accounting system may be found under the menu titled Guidance, Audit Process Overview, “Information for Contractors.”

g. Offerors without an approved accounting system should contact the Contracting Officer to initiate an accounting system review by DCAA. This request shall be submitted immediately upon receipt of the RFP but no later than 10 days after release of the RFP. Offerors are encouraged to initiate this process immediately.

h. An adequate accounting system is not an evaluation criterion. It is a regulatory requirement with a pass/fail determination. A contract may only be awarded to the Offerors who are determined to have an adequate accounting system.

i. Firms comprising a Joint Venture must follow the guidelines below:

(i) Each firm making up the Joint Venture shall accomplish a Pre-Award Audit Registration,

(ii) Identify which firm’s accounting system will be used for the recording of costs or

(iii) Indicate if a new accounting system will be created for the joint venture. (If a new accounting system is being created for the Joint Venture, a Pre-Award Audit Registration shall be accomplished in addition to each firm making up the Joint Venture.)

FA5641-20-R-0007

Attachment 1