Section L.pdf

1 (of 10)

SECTION L

INSTRUCTIONS TO OFFERORS (ITO)

SECTION CONTENT

1 – General Instructions 2 – Volume I – Technical Capability 3 – Volume II – Past Performance 4 – Volume III – Contract Documentation

1.0 General Instructions

(a) To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. Failure to meet a requirement may result in an offer being ineligible for award. Offerors are required to satisfy/address all Request for Proposal (RFP) requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Any Offeror who submits an incomplete package may be determined non-responsive and may be eliminated from the competitive range. Offerors must clearly identify any exception to the RFP terms and conditions and provide complete accompanying rationale. The response shall consist of three

(3) separate Volumes:

Volume I – Technical Capability and Program Risk Volume II – Past Performance Volume III – Contract Documentation

(b) The Contracting Officer (CO) has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the (CO) will review this determination and if, in the CO's opinion, adequate price competition exists no additional cost information will be requested in accordance with (IAW) FAR 15.4. However, if at any time during this competition the CO determines that adequate price competition no longer exists, Offerors may be required to submit information to the extent necessary for the CO to determine the reasonableness and affordability of the price offer (IAW) FAR 15.4.

(c) 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 personnel, experience, or facilities and that the Government will base its evaluation solely on the information presented in each Offeror’s proposal.

(d) Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

2 (of 10)

(e) In accordance with FAR 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 such unsuccessful proposals.

1.1 General Information

1.1.1 Point of Contact (POC)

The CO is the sole POC for this acquisition. Questions, concerns, and/or requests for clarification shall be sent in writing to the CO at the address located in Section A of the RFP.

1.1.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 submit their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

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

1.1.4 Electronic Reference Documents

All referenced documents for this RFP are available, with exception of the Performance Specification (PS), on the System for Award Management (SAM) web site at https://beta.sam.gov/. The PS can be obtained by contacting the CO. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this RFP.

1.1.5 Oral Presentations

No oral presentations will be required or accepted.

1.1.6 Exchanges

Exchanges of source selection information between the Government and Offerors will be controlled by the CO.

1.2 Proposal Organization/Structure

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/04.htm http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/15.htm http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/15.htm https://beta.sam.gov/

3 (of 10)

The Offeror shall prepare a proposal as set forth in Table 1 below. Each Volume shall be marked with the RFP number, the Offeror’s name, cage code, and address. Each page shall contain the following legend at the bottom of each sheet: SOURCE SELECTION INFORMATION – SEE FAR 2.101 and 3.104.

Table 1. Proposal Organization

VOLUME TITLE PAGE LIMIT NUMBER OF

ELECTRONIC

COPIES

I Technical Capability and Program Risk

200 2

II Past Performance N/A 2 III Contract Documentation N/A 2

1.2.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation. Each page shall be counted except cover pages, table of contents, list of figures/tables/drawings, cross reference matrix, tabs, engineering drawings, and glossaries. Page limitations may be placed on responses to Evaluation Notices (ENs) if applicable. The specified page limits (if required) for EN responses will be identified in the letters forwarding the ENs to the Offerors.

Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced typed with 0.9 line spacing. Except for the reproduced sections of the RFP document, the font 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 1-inch side margins. Pages shall be numbered sequentially by Volume. These limitations shall apply to the original proposal submittals as well as Interchange Notice (IN) responses if required.

Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems, design layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible (no smaller than 9-point font) and shall not exceed 11 x 17 inches in size. Large page size may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. Assembly drawings of the brake control system design shall be included in an Appendix of Volume I, sized as 11x17.

1.2.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 conserves space without impairing clarity.

The Offeror shall provide a general cross-reference matrix in each Volume, indicating by document/section/paragraph (as applicable), the corresponding proposal paragraph which addresses the referenced requirement. A notional matrix including the Description, RFP Sections L & M, Technical Requirements Document (TRD)/Statement of Work (SOW, http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/02.htm#P14_695 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/03.htm#P122_19753

4 (of 10)

Integrated Master Schedule (IMS), and Contract Data Requirements List (CDRL) is provided in Table 2 below.

Table 2. Notional Cross-Reference Matrix Applicable Document/Section/Paragraph Description Section L Section M TRD/SOW Proposal IMS CDRLs

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

1.2.4 Glossary

Each Volume shall contain a glossary of all abbreviations/acronyms used and include an explanation for each. Glossaries do not count against the page limitations for their respective Volumes.

1.2.5 Hyperlinks

The Table of Contents of all proposal Volumes shall be hyperlinked to the corresponding material within each proposal Volume such that “clicking” the mouse on an item in the Table of Contents shall take the reader to the corresponding section within the body of the proposal Volume. Any heading or sub-heading appearing in the table of contents shall be hyperlinked as described above. Also, any reference within the body of the proposal Volume that refers the reader to another location within the referring document shall be hyperlinked in the manner described above. A hyperlinking reference between different filenames (different proposal Volumes) is not required.

1.2.6 Labeling

A cover sheet shall be included in each Volume, clearly indicating the Volume number, Volume title, RFP number, and the Offeror's name. In addition, apply all appropriate markings 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.

1.2.7 Pricing Information

Pricing details shall be addressed/included ONLY in Volume III (Contract Documentation). References to cost information (including work-hour estimates, material specifics, quantities, etc.) may be used in other Volumes only as appropriate for presenting rationale for alternatives or design decisions.

1.3 Electronic Offers

The Offeror shall submit each proposal Volume in PDF format which must be readable by Adobe Acrobat. The proposals shall be delivered via email (if permitted by file size), on Microsoft Windows-compatible, virus-free CD-ROMs with appropriate labeling, or via DoD

SAFE.

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_215.htm http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/03.htm http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/03.htm

5 (of 10)

If CD-ROMS are provided, each CD-ROM shall be marked with the RFP number. Use separate files/filenames to permit rapid location of each portion of the proposal. If files are compressed, the necessary decompression program must be included on the email or CD-ROM.

DoD SAFE Proposal Submission Process:

DoD SAFE Link: https://safe.apps.mil DoD SAFE Proposal Submission Process:

1) Offeror shall email Ryan Peacock (ryan.peacock@us.af.mil) of their intent to submit a proposal and request a DoD SAFE Drop Off link. Unless otherwise specified in the request, the Government will use the email account from the request to process the drop-off request.

Note: Drop-off requests are only valid for 14 days. It is recommended that this request is submitted no sooner than 14 days and no later than 72 hours prior to the proposal due date and time.

Note: The file limit for drop-off is 25 files. If the Offeror intends to submit more than 25 files, it is the Offeror’s responsibility to request a 2nd drop off link with its request.

2) The Government will send a one-time submission link through the “Request a Drop Off” feature of DoD SAFE. For tracking purposes, the Government will only provide this to a single email account on behalf of the Offeror.

3) The Offeror will receive an email from DoD SAFE with a link that can be used to submit a proposal for this solicitation. The Offeror opens the link and adds the files.

4) If the Offeror chooses to encrypt their submission, a passphrase will need to be created.

This passphrase should be provided to Ryan Peacock (ryan.peacock@us.af.mil) for pick-up.

5) Proposals are not considered submitted until the file drop-off occurs.

Note: It is highly recommended that the Offeror take a screen shot of the Drop Off Completed screen and email it to Ryan Peacock (ryan.peacock@us.af.mil).

6) If the Offeror needs to update its submission prior to the RFP closing date, it shall follow the same steps outline above.

NOTE: In accordance with FAR 15.208, it is the responsibility of the Offeror to ensure the proposal/quote is received by the date and time specified on the cover page of this solicitation.

Please note that when submitting through DoD SAFE, there is no "expected" or "target" length of time for proposal submission; size and content may be factors, therefore Offerors are strongly cautioned when submitting proposals to allow adequate time for submission.

1.4 Delivery

The Offeror shall submit its proposal in accordance with the instructions as detailed in the RFP.

Failure to provide any required submission by the date and time as specified may cause the Offeror’s proposal to be late in accordance with FAR 52.215-1.

Proposals shall be addressed and delivered as specified in the RFP.

1.5 Cost and Software Data Reporting (CSDR)

https://safe.apps.mil/ mailto:ryan.peacock@us.af.mil mailto:ryan.peacock@us.af.mil http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_215.htm#P107_5531

6 (of 10)

The Offeror shall submit a CSDR package in accordance with the four (4) CDRLs (0008AA- 0008AD), Attachments 0001 & 0002, and the CSDR SOW detailed in the RFP. The CSDR package is required, and is not separately priced (NSP) IAW DFAR 252.204-7002; therefore, individual packages will not be a part of the evaluation process. Failure to provide the required submission by the date and time specified may cause the Offeror’s proposal to be late in accordance with FAR 52.215-1. Proposals shall be addressed and delivered as specified in the

RFP.

2.0 Volume I - Technical Capability

The Offeror shall provide the following minimum information in the Technical Capability Volume:

2.1 General

The Technical Capability Volume shall be specific and comprehensive. Legibility, clarity, and coherence are very important. Responses shall be evaluated against the Technical Capability subfactors defined in Section M – Evaluation Factors for Award. In accordance with the instructions provided herein, define as specifically as possible the actual approach/methodology to be used for satisfying these factors/subfactors. Note that all requirements specified in the RFP are mandatory and proposal submittal constitutes the Offeror’s commitment to satisfy all requirements. With that understanding, it is not appropriate to simply reiterate the objectives or reformulate the requirements.

2.2 Volume Organization

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

Table of Contents List of Figures, Tables, and Attachments Glossary of Key Words and Acronyms General Cross-Reference Matrix PS Cross-Reference Matrix Factor 1 – Technical Capability

Subfactor 1 – Program Management Subfactor 2 – System Architecture and Performance Subfactor 3 – Reliability and Maintainability

Factor 2 - Program Risk Attachments (Drawings, Analyses, IMS, etc)

2.3 Performance Specification (PS) Cross-Reference Matrix

In addition to the general cross-reference matrix (Paragraph 1.2.2), the Offeror shall include a PS cross-reference matrix. This matrix shall facilitate proposal review by cross-referencing the proposal with each specific performance specification requirement. The matrix shall include a text summary of each specification requirement that is cross-referenced with proposal page numbers, paragraph numbers, figures, tables, drawings, etc, as applicable.

2.4 Technical Capability and Program Risk Volume

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_215.htm#P107_5531

7 (of 10)

The Technical Capability and Program Risk Volume shall address the factors and sub factors as defined below. With emphasis on these factors and subfactors, the Offeror shall describe its approach for satisfying the full range of contract requirements set forth in the TRD / SOW as identified in the Attachment. To the extent possible, the Offeror shall JUSTIFY ALL CLAIMS by providing actual examples/exhibits/analyses/data, from prior successful programs or based on data/analyses specific to this program, that are relevant to the applicable subfactor.

2.5 Factor 1 - Technical Capability

2.5.1 Subfactor 1 – Program Management

The Offeror shall describe the organizational approach, schedule (IMS), methods, and resources to be used for executing the program. The Offeror shall describe the approach for providing turn-key customer support and resolving systemic performance/reliability problems that surface during flight test, fleet retrofit, system performance tracking immediately following retrofit, and throughout the remaining service life of the aircraft. The Offeror shall identify technical (design, performance) and logistical (material, schedule) requirements which pose the greatest risk (ranked by probability and severity) and shall describe intended actions to mitigate those risks.

2.5.2 Subfactor 2 – System Architecture and Performance

The Offeror shall demonstrate its ability to understand and satisfy all PS requirements. The design strategy and system architecture shall be described in detail. The design shall not require development of new technologies for the Offeror, but it shall incorporate state-of-the-art materials, processes, procedures, and designs that are currently airworthiness-certified and in service. The Offeror shall demonstrate that the brake control/antiskid system is capable of providing the required performance/efficiency over the entire operating range (wet, dry, or icy runway, hot, cold, etc).

2.5.3 Subfactor 3 – Reliability and Maintainability

The Offeror shall demonstrate that its design incorporates appropriate reliability and maintainability features which result in extended service life, simplified component repair, reduced maintenance time (including on-aircraft troubleshooting), etc. The Offeror shall provide evidence that its proposed design, materials, and protections (hydraulic and electrical) provide maximum resistance to operational/environmental impacts/decay over extended service periods.

The Offeror shall provide evidence that its Quality Assurance Program complies with ISO 9001:2015, AS9100, or equivalent, as documented by an independent audit agency.

2.6 Factor 2 - Program Risk

The Offeror shall identify in a detailed program risk mitigation plan what they view as the most critical aspects of the program requirements.

The Offeror shall describe its proposed risk management program and how it will correlate to the Integrated Master Schedule (IMS) requirements identified in the Technical Requirements Document (TRD)/Statement of Work (SOW).

8 (of 10)

The Offeror shall describe how they intend to identify, assess, mitigate, and monitor potential program risks for each factor and subfactor. Critical program risks which may adversely impact cost, schedule or contract performance shall be identified along with proposed risk mitigation methods for all risks identified as moderate or high.

The Offeror shall demonstrate its previous experience in critical requirements and processes and its ability to understand and resolve program risk issues within its organizational structure, including interaction with its subcontractors.

3.0 VOLUME II - PAST PERFORMANCE

The Government shall utilize information submitted by the Offeror and other government/commercial sources to assess past performance (which is a reasonable indicator of anticipated future performance). The Offeror shall support this confidence assessment by providing the following minimum information in the Past Performance Volume:

3.1 Past Performance Information Sheet (PPIS)

The Offeror shall submit a separate PPIS (Attached) for each contract that the Offeror considers relevant in demonstrating its capabilities as required by the RFP, TRD (SOW), and Factor 1- Technical Capabilities. The most relevant contracts include antiskid or brake control system design, development, qualification, production, and sustainment efforts that are highly comparable in scope, magnitude, and complexity to the F-16 BCSR effort. However, contracts that clearly demonstrate design, development, qualification, production, or sustainment efforts that are comparable in scope, magnitude, and complexity to the F-16 BCSR effort will be reviewed. It is important that Offerors explain, in enough detail, their efforts relating to design, development, qualification, production, and sustainment that complexity can be determined.

Only those contracts/efforts where the period of performance was supported/completed within the last five (5) years are eligible for consideration. Assuming positive performance, statistical confidence will be enhanced as the number of PPIS submittals is increased. The Offeror shall submit at least three (3) total PPIS responses; but not more than five (5).

The Offeror shall include relevant information concerning the Offeror’s compliance with FAR 52.219-8, Utilization of Small Business Concerns and/or FAR 52.219-9, Small Business Subcontracting Plan, if these clauses are contained in any of the contract efforts identified in the Offeror’s proposal. Please note that FAR 52.219-8 does apply to ALL Offerors (see FAR 19.708(a) for exceptions). The Offeror shall specify whether or not FAR policy was satisfied in the awarding of subcontracts to small business concerns, veteran-owned small business concerns, service-disabled small business concerns, veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns to the fullest extent consistent with contract performance.

The Offeror shall focus its PPIS responses so they clearly correlate past performance with the required objectives/capabilities required by the Technical Capability subfactors. Each PPIS submitted by the Offeror must clearly describe the technical and programmatic efforts performed by the Offeror on that effort. The Offeror may expand the answering space on the PPIS so that the completed PPIS for each relevant contract includes no more than four (4) http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_215.htm#P1554_245021 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_215.htm#P1554_245021 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_215.htm#P1593_251320 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_215.htm#P1554_245021 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/19.htm#P858_187106 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/19.htm#P858_187106

9 (of 10) pages. The Offeror shall provide the most current information for the POCs identified on each

PPIS.

The Offeror shall provide available information (letters, metrics, customer surveys, independent surveys, etc.) which demonstrates customer satisfaction with overall job performance and quality of completed products for each PPIS. In addition, the Offeror shall explain corrective actions, if any, for prior/current performance problems such as cost overruns, extended performance periods, numerous warranty calls, etc.

If a teaming arrangement is contemplated, the Offeror shall provide complete information as to the arrangement, including any relevant and recent past performance information on previous teaming arrangements with same partner. The offeror shall identify if this is a first-time teaming arrangement and provide a list of past and present relevant contracts for each team member.

3.2 Past Performance Questionnaire (PPQ)

For each PPIS the Offeror plans to submit in their Past Performance Volume it would be highly beneficial to provide the following no later than 45 days after release of the initial RFP: 1) Contract number; 2) the associated Cage Code and DUNS Number for that contract (if applicable); 3) at least one, preferably two POCs, including their name (i.e.; Mr. John Smith) and title (e.g.; CO, Program Manager, Engineer, Etc.), along with a current phone number and email address. This information will be used by the Government to obtain PPQs in support of each PPIS in a more timely fashion. POCs will submit the completed PPQ directly to the Government. The information contained in completed PPQs shall be considered sensitive and shall not be released to the Offeror.

Offerors who choose not to provide the preceding PPIS/PPQ information, shall send a PPQ (Attached) to each POC (COs, Program Managers, Engineers) for each PPIS submitted in the Past Performance Volume. POCs will submit the completed PPQ directly to the Government.

The information contained in completed PPQs shall be considered sensitive and shall not be released to the Offeror. A cover letter for transmitting the PPQ to each POC is provided (Attached).

4.0 VOLUME III - CONTRACT DOCUMENTATION

4.1 General

Volume III shall consist of the completed and signed RFP. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined unacceptable. The Government intends to make an award without discussions.

Discussions, if necessary, will be conducted in accordance with FAR 15.306.

The Offeror shall complete Section A of SF1449 (RFP). In doing so, the Offeror accedes to the contract terms and conditions as written in the RFP Sections A through K. These sections constitute the model contract.

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/15.htm#P286_46346

10 (of 10)

Complete the necessary fill-ins and certifications for Sections C through K. For Sections C through J, the Offeror shall submit only those pages that require a fill-in. Section K shall be returned in its entirety.

If applicable, provide a copy of the letter from the Small Business Administration (SBA) showing proof of Section 8(a) status.

4.2 Pricing

Insert proposed unit and extended prices in Section B for each Contract Line Item Number (CLIN) or SubCLIN (SCLIN), including all option periods. The extended amount must equal the whole dollar unit price multiplied by the number of units.

Proposed prices shall be fully burdened and include all direct costs, indirect costs (Overhead, General and Administrative, etc.) and profit necessary for the performance of the entire requirement.

Prices submitted will be reviewed for completeness, reasonableness, and balance. The Total Evaluated Price (TEP) as identified in Section M of the RFP will be assessed from the Offeror’s pricing provided in this volume.

All total dollar amounts provided shall be rounded to the nearest dollar.