FA8691-20-R-3010 Section L.pdf

FA8691-20-R-3010

Section L

SECTION L –

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

for

Technically Acceptable Multiple Award - Indefinite Delivery Indefinite Quantity (MA IDIQ)

Program:

Engineering Assessment, Procurement, Integration, & Contractor Logistics Support (EPIC)

Intelligence, Surveillance, Reconnaissance (ISR) Sensors Division

Foreign Military Sales (FMS) Sensors and Aircraft Integration Branch (WINI) & Advanced ISR and FMS Planning Branch (WINN)

ISR & Special Operations Forces Directorate Air Force Life Cycle Management Center (AFLCMC)

WPAFB, OH 45433

1 PROGRAM INFORMATION

The Government intends to award contract(s) and subsequent first order as part of a Multiple Award (MA) Indefinite Delivery/Indefinite Quantity (ID/IQ) contract to cover Engineering assessments, Procurement of hardware and spares, full aircraft and ISR sensor Integration, and Contractor Logistics Support (EPIC).

All sections of the basic contract Statement of Work could be applicable to each delivery order/task order as called out in the individual Fair Opportunity Proposal Request (FOPR). Each FOPR will have detailed and tailored requirements. While the government anticipates the utilization of this MA IDIQ by the WINI/WINN program offices, the award of the contract(s) and subsequent first order does not guarantee any FOPRs will be released; nor does it obligate the government outside of the contractual obligation of the first order.

The Period of Performance (PoP) for the contract will be thirteen (13) years total with a ten (10)-year ordering period and an additional three (3)-year performance period. There will be an on/off ramp option five (5) years into the PoP where contractors could be added to the basic ID/IQ. Contractors in the award pool may choose to exit the ID/IQ at that time. If a contractor wants to exit the ID/IQ at the 5-year point, they must inform the contracting officer in writing 30 days ahead of time.

If an offeror is selected for award under the EPIC MA IDIQ, there is no obligation to submit proposals under FOPRs, nor does it guarantee any further award under the EPIC MA IDIQ.

2 GENERAL INSTRUCTIONS

The offeror's proposal must include all data and information requested by these Instructions to Offerors (ITO) and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Statement of Work (SOW), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but, rather, shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities or experience and will base its evaluation on the information presented in the offeror's proposal.

Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

The proposal acceptance period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. The Government will destroy extra copies of such unsuccessful proposals, unless the offeror requests otherwise within 10 days of contract award.

2.1 Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Section A of the model contract/solicitation.

2.2 Debriefings

The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505.

Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing.

However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.3 Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error.

2.4 Electronic Reference Documents

All referenced documents for this solicitation are available on the contract opportunities Governmentwide Point of Entry website at https://www.beta.sam.gov/. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.5 Communications

Exchanges of source selection information between Government and offerors will be controlled by the CO. Electronic communications will be done via DoD SAFE to ensure proper encryption <https://safe.apps.mil/>. If the offeror needs to communicate with the CO, send an email to the points of contacts in section 3.7 to request a Drop Off Request. Any electronic communication from the CO will be transmitted via DoD SAFE.

3 PROPOSAL PREPARATION INSTRUCTIONS

http://farsite.hill.af.mil/vffara.htm http://farsite.hill.af.mil/vffara.htm http://farsite.hill.af.mil/vffara.htm https://www.beta.sam.gov/ https://safe.apps.mil/

3.1 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 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 2.2.

The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table 3.1- Proposal Organization

VOLUME ITO Paragraph

Number

VOLUME/SECTION TITLE COPIES

PAGE

LIMIT

I 4.1 Executive Summary 1 2 II 4.2.4 Technical Factor: Subfactor 1 –

Engineering Assessment 1 10

II 4.2.5 Technical Factor: Subfactor 2 – Integration

1 20

II 4.2.6 Technical Factor: Subfactor 3 – Contractor Logistics Support

1 20

III 4.3.4 Management Factor: Subfactor 1 - Subcontractor Management

1 7

III 4.3.5 Management Factor: Subfactor 2 - Small Business Participation

1 3

3.1.2 Page Limitations

Page 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 shall be counted except the following: Cover pages, tables of contents, cross-reference matrix, tabs, glossaries, and Small Business Subcontracting Plan.

3.1.3 Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single spaced. Except for the reproduced sections of the solicitation document, the font shall be Times New Roman and the text size shall be no less than 11 - point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs.

(b) Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 11 - point.

3.2 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 a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The offeror shall fill out the Solicitation Cross Reference Matrix at Attachment 1 of this ITO indicating the proposal reference information as it relates to the ITO, SOW/SOO/PWS, CLIN numbers, and CDRL references found therein.

3.3 Indexing

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

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

3.5 Labeling

Each volume of the proposal should be separated by a cover sheet clearly marking the volume number, title, copy number, solicitation identification, the offeror's name, and CAGE Code. Be sure to apply all appropriate markings including those prescribed 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.

3.6 Electronic Offers

The proposal shall be submitted via DoD SAFE <https://safe.apps.mil/> no later than 12:00 PM EDT on 25 August 2020. In order to submit via DoD SAFE, a drop-off request is required. In order to receive a DoD SAFE drop-off, email both the primary and alternate points of contact listed in section 3.7 below no more than 14 days and no less than 3 days prior to proposal submittal date.

https://safe.apps.mil/

3.7 Distribution

The "original" proposal shall be identified. Proposals shall be addressed to the CO and delivered via DoD SAFE.

Primary:

Ms. Grace Smith-Heit

AFLCMC/WINK

Grace.smith-heit@us.af.mil

Alternate:

Mr. Eric Filion

AFLCMC/WINK

Eric.filion@us.af.mil

4 PROPOSAL ORGANIZATION

4.1 Volume I - Executive Summary

In the Executive Summary volume, the offeror shall provide the following information:

4.1.1 Narrative Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

4.1.2 Table of Contents

Include a master table of contents of the entire proposal.

4.2 Volume II - Technical Volume

4.2.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your 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 actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By responding to this solicitation, an offeror is affirming the firm will perform all the requirements specified; however, the Government does not require the offeror to address each task identified in the SOW in the response – the contents of the proposal shall only address the criteria as detailed below. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.2.2 Technical

In the technical volume, address your technical solution for meeting the Government’s minimum performance or capability requirements of each technical subfactor.

4.2.3 Volume Organization

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

(1) Table of Contents

(2) List of Table and Drawings

(3) Glossary

(4) Cross Reference Matrix

(5) Subfactor One - Engineering Assessment

(6) Subfactor Two - Integration

(7) Subfactor Three - Contractor Logistics Support

4.2.4 Subfactor One – Engineering Assessment

Provide a narrative and timelines associated with your approach to conduct an engineering assessment for the following scenario:

In an effort to bolster Botswana’s economy and position in the region, South Africa has decided to gift to Botswana two (2) used PAC P-750 XSTOL aircraft. These aircraft were used by a privately owned sky-diving school in South Africa since 2007. Botswana would like to convert these aircraft to perform dual mission-sets of border surveillance and agricultural surveys. As these were not former FMS cases with the U.S., there has been no U.S. Government or Contractor oversight. The PAC P-750 XSTOL aircraft are currently owned by the company and reside in South Africa. Botswana is awaiting an agreement with the U.S. Government before formally accepting them. This Engineering Assessment will inform the U.S. Government position. All flight and maintenance manuals were delivered to the company by the manufacturer in English. However, the manuals were also translated to Afrikaans and maintenance records have been kept in Afrikaans. Botswana intends to keep manuals in both English and Setswana and maintenance records in Setswana. Upon discussions with a few contractors who have been engaged in discussions with Botswana, it was indicated that maintenance records were kept to a South African Civil Aviation standard.

In addition to the PAC P-750 XSTOL, the Botswana Defence Force (BDF) currently owns and operates one (1) CASA/IPTN CN-235 as a cargo transport aircraft. As part of this effort, the country would like to add Intelligence, Surveillance and Reconnaissance (ISR). This aircraft was purchased directly from the manufacturer by Botswana and aircraft and records have been maintained to the Botswana Civil Aviation Authority standards for continued airworthiness. All flight and maintenance manuals were delivered to the BDF in English and were translated to Setswana. Maintenance records have been kept in Setswana.

4.2.5 Subfactor Two – Integration

Provide a narrative that details your approach to procure weapon system components from OEMs, including a new aircraft, an EO/IR sensor system that is releasable and a UHF/VHF radio for both the airborne and ground station subsystems. Include in your approach; business and technical considerations for conducting the integration, including facilities, partnerships, special tools and test equipment required, as well as your plan to control supply chain risk. Also include in your approach any existing airworthiness certifications that are intended to be used and considerations and limitations in certifying modifications as airworthy through both the FAA and Military Certification process and authorities. Include in the narrative your approach to ship and ferry the aircraft and equipment, including export licenses held and required. If export licenses are required, identify your approach to acquire them. Assume that the aircraft cannot ferry with equipment installed. In addition, detail your approach to and considerations for conducting performance validation within the continental United States (CONUS) as well as installation and check-out activities outside the continental United States (OCONUS). Identify any special tools or test equipment/ranges required, any limitations and any dependencies on or assistance required from the U.S. Government.

4.2.6 Subfactor Three – Contractor Logistics Support

Provide a narrative that details your approach to perform Contractor Logistics Support (CLS) for integration, site standup, and sustainment of airborne and ground ISR mission equipment to foreign partners in austere locations. Include in your approach the maintenance concept such as flightline, backshop repair and return processes, and touch-labor field service representatives to ensure availability of critical system components. Also include in your approach the supply support approach to support a fleet of six or fewer aircraft including ensuring availability, management, and tracking of spares, consumables, and equipment. Include in the narrative your approach for providing basic life support and evacuation (if needed) for in-country contractor personnel in austere locations. Include your approach to obsolescence planning and management from integration to sustainment to identify obsolescence and provide notifications and recommendations to mitigate impacts. Also include in your approach the transportation arrangements to ensure all required items are transported CONUS and OCONUS (as required) on-time, safely, securely, and in compliance with export control requirements. Identify the approach to minimize the need for additional support equipment and provide any new support equipment that is required. Include the approach to provide initial training, in English, for operations and maintenance of program parts and equipment to foreign partners with English language barriers.

4.3 Volume III – Management Volume

4.3.1 General

The management volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Management subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By responding to this solicitation, an offeror is affirming the firm will perform all the requirements specified; however, the Government does not require the offeror to address each task identified in the solicitation in the response – the contents of the proposal shall only address the criteria as detailed below. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.3.2 Management

In the Management volume, address your management solution for meeting the Government’s minimum performance or capability requirements of each Management subfactor.

4.3.3 Volume Organization

The Management volume shall be organized according to the following general outline:

(1) Table of Contents

(2) List of Table and Drawings

(3) Glossary

(4) Cross Reference Matrix

(5) Sub-factor One – Subcontractor Relationships

(6) Sub-factor Two – Small Business Participation

4.3.4 Subfactor One – Subcontractor Relationships

Provide a narrative on your process for establishing and sustaining subcontractor relationships.

Include how your firm proactively plans for problems and fixes them if they occur.

4.3.5 Subfactor Two – Small Business Participation

Provide a narrative of how your firm intends to encourage small business participation in the acquisition.

If the offeror is other than a small business, the offeror shall submit a Small Business Subcontracting Plan in accordance with FAR 52.219-9 that also identifies and specifies the extent of offeror's commitment to the participation of small businesses (SB), historically black colleges or universities (HBCU) and minority institutions (MI), whether as joint venture members, teaming arrangement partners, or subcontractors. If applicable, submit a copy of your approved Master Plan. In the event the offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, the offeror must submit the information that identifies and specifies the extent of its commitment to the participation of SB, HBCU and MI. The Small Business Subcontracting Plan will not be included as part of the page count.

5.0 Volume V - Contract Documentation

5.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the Model Contract, and Sections A through K. The model contract/formal solicitation is attachment 2 of this section.

5.1.1 Section A - Solicitation/Contract Form

The offeror shall complete blocks 13-16 and signature and date for blocks 17 and 18 of the SF33 for FA8620-20-R-3010. Signature by the offeror on the SF33 for FA8620-20-R-3010 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

5.1.2 Section B - Supplies or Services and Prices

No costs or pricing is required at the time of basic award and will not be evaluated. Do not submit any information for Section B.

5.1.3 Section F - Deliveries or Performance

No delivery or performance criteria will be evaluated at the time of basic award. Do not submit any information for Section F.

5.1.4 Section I - Contract Clauses

With the exception of the provisions found in Section K, Representations and Certifications, any clauses requiring tailoring or fill-ins by the contractor or contracting office will be tailored or filled-in on each individual order. These clauses are intentionally blank for the purposes of this RFP.

5.1.5 Section K - Representations, Certifications, and other Statements of Offerors Complete representations, certifications, acknowledgments and statements.

5.2 Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 5.2.

Table 5.2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion Rationale

SOW, Model Contract, ITO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

5.3 Other Information Required

5.3.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

5.3.2 Government Offices

Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

5.3.3 Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county and facility code; CAGE code; DUNS code;

TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

5.3.4 Attachments to the Model Contract

The offeror shall provide the following as attachments to the model contract:

5.3.4.1 Subcontracting Plan - Participation of Small Businesses (SB), Historically Black Colleges and Universities, or Minority Institutions (HBCU/MI) If the offeror is other than a small business, the offeror shall submit a Small Business Subcontracting Plan in accordance with FAR 52.219-9 that also identifies and specifies the extent of offeror's commitment to the participation of SB, HBCU and MI, whether as joint venture members, teaming arrangement partners, or subcontractors. If applicable, submit a copy of your approved Master Plan. In the event the offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, the offeror must submit the information that identifies and specifies the extent of its commitment to the participation of SB, HBCU and MI.

5.3.4.5.2 Applicable Documents

A list of Applicable Documents has been provided to the offerors as an annex to the SOW attachment in the solicitation, which includes a minimum list of Government Compliance Documents. The offeror shall provide a list of any offeror, industry, commercial, and tailored Government standards, specifications, processes, and/or practices selected as compliance documents. The offeror shall also provide a list of all Government compliance documents intended to be used as compliance documents during the course of this contract. The offeror shall submit a list of these documents, including any tailoring instructions, as an annex to the proposed SOW. The offeror shall submit the completed Proposed Compliance Documents as a separately bound document.

6.0 List of Attachments: Section L attachments listed below are provided as separate files.

Attachment 1: Cross Reference Matrix Attachment 2: Model Contract / Solicitation