ATS_Section_L_Instructions_15_Oct_2018.pdf

1 | P a g e 1 4 S e p t e m b e r 2 0 1 8

SECTION L

PROPOSAL PREPARATION AND SUBMISSION INSTRUCTIONS

AIR TURBINE STARTER TEST STANDS

SOURCE SELECTION

1.0 PROGRAM STRUCTURE AND OBJECTIVES

The purpose of this effort is to replace three (3) existing Air Turbine Starter (ATS) test stands with two (2) new ATS test stands in accordance with the Statement of Work

(SOW) and Purchase Description (PD) 001. Included in this requirement is the replacement of the existing 300 psi air system with a new 125 psi air systems that meets the requirements of PD 002 and installing a new 300 psi air system that meets the requirements of PD 003.

BUDGET/FUNDING INFORMATION

The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an Offeror for any costs.

GENERAL INSTRUCTIONS

The offeror's proposal must include all data and information requested by this Instruction to Offeror (ITO) and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the SOW, PDs 001, 002, 003 and all other contract terms and conditions. Non-conformance with the instructions provided in this ITO shall 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 shall 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 and experience; and will base its evaluation on the information presented in the offeror's proposal. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

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 solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through 30 August 2019.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the offeror requests otherwise, the

Government will destroy extra copies of unsuccessful proposals.

2 | P a g e 1 4 S e p t e m b e r 2 0 1 8

2.0 GENERAL INFORMATION

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 solicitation and Section

L, 3.6.

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 preaward debriefing or they may choose to wait until after the source selection decision to request a postaward 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. The offeror is reminded that the

Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

2.4 RESTRICTED ACCESS DOCUMENTATION

Offerors may request access to the restricted-access documentation in PD 001, dated 14

September 2018. In order to request access, the offeror must submit their certified DD

Form 2345, Military Critical Technical Data Agreement, to Shawna Dudis at shawna.dudis@us.af.mil and Lyndsay Wilson at lyndsay.wilson@us.af.mil. It is recommended the offeror submit their DD Form 2345 as soon as possible after RFP release in order to have sufficient proposal preparation time.

2.5 COMMUNICATIONS

Exchanges of source selection information between the Air Force and offerors will be controlled by the Contracting Officer. Email may be used to transmit such information to offeror’s 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.

mailto:shawna.dudis@us.af.mil mailto:lyndsay.wilson@us.af.mil

3 | P a g e 1 4 S e p t e m b e r 2 0 1 8

3.0 PROPOSAL ORGANIZATION

The offeror shall prepare the proposal as set forth in Table 1 - Proposal Organization, below. The titles and contents of the volumes shall be submitted as defined in this table, all of which shall be within the required page limits and with the number of copies as specified. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders. The contents of each proposal volume are described in this Section (L) and summarized in the table below:

Table 1 - Proposal Organization

VOLUME TITLE COPIES PAGE LIMIT

I Technical 2 DVD-Rs

6 Hardcopies

II

Contract Documentation

Price shall be included in this volume

1 DVD-R

2 Hardcopies Unlimited

3.1 PAGE LIMITATIONS

Page limitations are identified in Table 1 and explained below. Offerors are advised that the limitations shall be treated as maximums. If exceeded, the excess pages will not be evaluated or considered for award purposes. Page limitations may be placed on responses to Evaluation Notices (ENs), if applicable. Each page shall be counted except cover/title pages, cross-reference matrices, tables of content, tabbed dividers, acronym lists, and glossaries.

3.1.1 PAGE SIZE AND FORMAT

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 typed using single spacing, except for the reproduced sections of the solicitation document, the text size shall be no less than 12point. Font will be Times New Roman. 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 1-inch side margins.

Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

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 x 17 inches in size. Foldout pages shall fold entirely within the volume, and each foldout shall be counted as two pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, and not for pages of text. For tables, charts, graphs and figures, the text shall

4 | P a g e 1 4 S e p t e m b e r 2 0 1 8 be no smaller than 12 point. These limitations shall apply to both electronic and hard copy proposals.

Calculations for system design shall be included as an appendix to the Technical Volume and shall not count against the 75 page limit.

3.2 INDEXING

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

3.3 ABBREVIATIONS AND ACRONYMS

Prior to using any abbreviations and/or acronyms the offeror shall spell out the entire title at the first occurrence followed with the abbreviation and/or acronym in parenthesis – for example - Statement of Work (SOW).

3.4 BINDING AND LABELING

Each volume should be separately bound in a white or black three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be located on the front of each binder, clearly marking the volume number, title, copy number, solicitation number, 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.

Each page within a section shall be numbered consecutively.

3.5 ELECTRONIC OFFERS

The content and page size of electronic copies shall be identical to the hard copies. For electronic copies, indicate on each DVD-R the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. (NOTE: “DVD-RW’s CANNOT BE READ, EVALUATED, OR

CONSIDERED) Each volume shall be in a different directory on a DVD-R. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable and searchable by

Microsoft (MS) Office Word 2016, MS Office Excel 2016, MS Office Project 2016, and

MS Office Power Point 2016, as applicable. If there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

5 | P a g e 1 4 S e p t e m b e r 2 0 1 8

3.6 DISTRIBUTION

Provide to the Contracting Officer, at the address listed below, the offeror’s proposal in accordance with Table 1 above. The "original" proposal shall be identified and signed by the offeror’s authorized representative and the “copy” should be identified. All requested copies must be received by the due date identified on the front page of the

RFP. Proposals shall be addressed to the CO and delivered to:

AFMC OL:H/PZIMB

ATTN: Shawna Dudis

6038 Aspen Ave, Bldg 1289 Upstairs

Hill AFB, UT 84056-5825

Include solicitation number FA8224-18-R-0020 on the address label.

4.0 EVALUATION FACTORS AND SUBFACTORS

4.1 FACTOR 1: TECHNICAL APPROACH

The Technical Approach 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. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.1.1 SUBFACTOR 1: SYSTEM DESIGN

Submit a technical approach for design of a test system which addresses the requirements within all applicable documents (SOW and PDs 001 through 003) and with emphasis on the elements listed below:

Simulated Inertia (PD #001 paragraph 3.3)

Overspeed testing (PD #001 paragraph 3.4)

Pawl Lift-off and Return Testing (PD #001 paragraph 3.5)

Adaptability (PD #001 paragraph 3.11)

4.1.2 SUBFACTOR 2: LIFE CYCLE SUSTAINMENT

Submit a technical approach for life cycle sustainment requirements as described in SOW paragraph 3.8, PD #001 paragraph 3.38, PD #002 paragraph 3.10, and PD #003 paragraph 3.9 with emphasis on the elements listed below:

Warranty (SOW paragraph 10)

Energy Efficiency (PD #001 paragraph 3.12, PD #002 paragraph 3.8, PD #003 paragraph 3.7)

6 | P a g e 1 4 S e p t e m b e r 2 0 1 8

Test Stand Engineering Data (SOW paragraph 4.2)

Data Rights (SOW paragraph 9)

4.1.3 SUBFACTOR 3: SOFTWARE

Submit a technical approach for the test system software with emphasis on the elements listed below:

Data Acquisition and Controls (PD #001 paragraphs 3.8.1 and 3.8.12)

Software Requirements (PD #001 paragraphs 3.10.2, 3.10.3, 3.10.6, 3.10.7, and

3.10.8)

4.1.4 SUBFACTOR 4: WORKLOAD CAPABILITY

Submit a technical approach to meet the daily testing demands, to include calculations, with emphasis on the elements listed below:

• Air Supply System (PD #002 paragraphs 3.1 and 3.2)

• Air Testing Requirements and Hypothetical Day (PD #002, Appendix C)

• Removal and Installation Plan (SOW paragraph 3.3.9)

5.0 CONTRACT DOCUMENTATION AND PRICING

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 proposal shall include a signed copy of the

Model Contract by an authorized representative of the offeror’s firm along with Sections

A through K completed as specified below.

5.1.1 Section A - Solicitation and Model Contract Form

Complete blocks 12, 13, 14, 15A, 15B, 15C, and include signed amendments to the solicitation (if any). Signature by the offeror on the SF 33 constitutes an offer, which the

Government may accept.

5.1.2 Section B – Contract Line Item Pricing

All applicable CLINs identified in Section of B of the solicitation shall be completed with the offeror’s proposed pricing.

7 | P a g e 1 4 S e p t e m b e r 2 0 1 8

5.1.3 Section I - Contract Clauses

Offerors shall complete all required clause fill-ins.

5.1.4 Section K - Representations, Certifications, and other Statements of

Offerors

Complete representations, certifications, acknowledgments and statements. Offeror must have filled out an online FAR provision 52.204-8 Annual Representations and

Certifications (May 2014), Online Reps and Certs at http://www.sam.gov.

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, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 2. If no exceptions are taken, so state.

Table 2 – Solicitation Exceptions

Solicitation Document Page/Paragraph Requirement/Portion Rationale

Cite document, e.g.

SOW, PD 001, etc.

Cite 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.2.1 OTHER INFORMATION REQUIRED

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.