Attachment_1_ASLON-45_SRP-O_Section_L_RFI_Final.docx

PART IV – REPRESENTATIONS AND INSTRUCTIONS

SECTION L – INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

FA8818-18-R-0011

Section L

FOR

SMALL ROCKET PROGRAM-ORBITAL (SRP-O)

Mission: Agile Small Launch Operational Normalizer (ASLON)-45

Information to Offerors and Instructions for Proposal Preparation

Basic: DD MMM YYYY

REVISION HISTORY

SECTION L

Instructions, Conditions, and Notices to Offerors or Respondents Program Structure and Objectives General Requirements – The Air Force Space and Missile Systems Center (SMC) anticipates award of a Small Rocket Program-Orbital contract to provide orbital launch services in support of the ASLON-45 mission requirements. The primary purpose of this acquisition is to provide orbital launch services for delivering payloads in support of the Space and Missile Systems Center (SMC), Launch Enterprise (LE), Small Launch and Target Division (LEX) Rocket Systems Launch Program (RSLP). Launch service requirements are defined in the Performance Work Statement (PWS) which includes the Mission Requirements Document (MRD), at Appendix A.

General Instructions Data and Information – The Offeror's proposal must include all data and information requested in this document and must be submitted in accordance with these instructions.

Proposal Format – The Offeror’s proposal shall consist of an oral and visual presentation with a partial written submittal as shown in Table 2-1. All information provided according to RFP instructions is subject to evaluation as described in Section M.

Effective Evaluation – The proposal shall be clear, concise, and 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 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 systems, processes, facilities and experience, and will base its evaluation solely on the information presented in the Offeror's proposal.

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

Valid Proposal Dates – 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 for nine months from the date of submission.

Proposal Retention – In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one hardcopy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

General Information – Point of Contact: The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to:

Alicia Cawley 3548 Aberdeen Ave Kirtland AFB, NM 87117 alicia.cawley@us.af.mil.

Debriefings: The PCO 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.

The PCO 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.

Discrepancies: If an Offeror believes the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale as well as the remedies the Offeror is asking of the PCO. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

Electronic Reference Documents (Bidder’s Library): Bidder’s Library documents for this solicitation will be available from the PCO upon request, per instructions in the FBO posting for this effort. Documents will be released via Compact Disc (CD) to potential bidders on file with the PCO.

Oral Presentations: Oral and visual presentations will be conducted for this acquisition.

Communications:

Exchanges of source selection information between Government and Offerors will be controlled by the PCO. Otherwise, source selection information will be transmitted via certified mail, delivery service, or facsimile (facsimile number will be provided to Offerors after submittal of proposals, as necessary).

Organization/Number of Copies/Page Limits – The Offeror shall prepare the proposal as set forth in the Proposal Organization table below.

Table 21: Proposal Organization

Section

FORMAT

After RFP Release

See Above

See Above

NOTE: All volumes shall be submitted with one paper copy and two electronic copies unless otherwise specified. Electronic copies must conform to the same requirements as the paper copy.

*Refer to FedBizOpps for actual date and time of submission deadlines.

Classified Information: Do not include classified information in this proposal.

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 minimal cross referencing to other proposal volumes. Information required for proposal evaluation 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 cross-referencing conserves space without impairing clarity.

Indexing: Each volume shall contain a more detailed Table of Contents (TOC) to delineate the contents within that volume.

Glossary of Abbreviations and Acronyms: Each volume shall contain a glossary of all abbreviations and acronyms used and an explanation for each.

Binding and Labeling: Each volume of the proposal shall be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror's name. The same identifying data should be placed on the spine of each binder. All document binders shall have a color other than red or other applicable security designation colors. 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.

Electronic Offers – The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD or DVD-ROM the volume number and title. Use separate files to permit rapid location of all portions, appendices, annexes, and attachments, if any. The Offeror shall submit all volumes in electronic format, using read/write CDs or DVD ROMs. Each volume shall be on a different CD or DVD ROM. 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 editable by Microsoft (MS) Office Word 2013, MS Office Excel 2013, MS Office Project 2013, and MS Office Power Point 2013, as applicable.

In the event there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

Distribution – The hard copy of the proposal will be identified as the "original." The proposal shall be addressed to the PCO and mailed or hand carried to:

SMC/ADK

Attn: Alicia Cawley 3548 Aberdeen Ave Kirtland AFB, NM 87117 Proposal Due Date – Proposals received after the date and time specified shall be treated in accordance with FAR 52.215-1.

Volume 0 Non-Governmental Advisors – Per DoD Source Selection Procedures paragraph 1.4.6.2.1, the PCO must ensure that before a non-Government advisor is given access to proprietary information, that the Government has received the consent of the submitting contractor(s) to provide access to the contractor who is to assist in the source selection. Therefore, the Offeror shall expressly state in the Executive Summary (Volume 0) whether or not it consents to the release of its proposal information to The Aerospace Corporation, an FFRDC who will be acting as non-Government advisors.

Table of Contents – Include a master Table of Contents of the entire proposal. The Executive Summary Volume page limit does not include the Table of Contents, and there is no page limitation for this section.

Proposal Correlation Matrix – Appendix A contains a Solicitation Correlation Matrix to be completed as a Proposal Correlation Matrix template. This matrix shall be completed by the Offeror to add the cross-reference correlations between Section L, Section M, the PWS, and the Proposal. This will assist the Government’s evaluation in considering all relevant efforts of the proposal. The Proposal Correlation Matrix shall not contain informational notes, as the content is not evaluated and the Technical Volume provides ample opportunity for discussion and description of the Offeror's approach for evaluation.

Volume I (Factor 1) - Technical Volume General Instructions – The Technical Volume shall be specific and complete. Legibility, clarity, and coherence are very important. The Offeror’s responses will be evaluated against the technical factors defined in Section M, Evaluation Factors. Using the instructions provided below, provide, as specifically as possible, the actual methodology you would use for accomplishing and satisfying these factors. All the requirements specified in the solicitation are mandatory. By the Offeror’s proposal submission, you are representing that the Offeror’s firm will perform all the requirements specified in the solicitation. It is not necessary to state this in the Offeror’s proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

Format and Specific Content – Technical: In the Technical Volume, the Offeror shall address the technical solution for meeting or exceeding the Government’s minimum performance or capability requirements. The Technical Volume/Presentation shall be organized according to Figure 4-1:

Figure 4-1:

(1) Program Management (Oral and Visual)

(a) Work Breakdown Structure (WBS)

(b) Integrated Master Schedule (IMS)

(2) Launch Solution Design (Oral and Visual)

(a) Launch Solution Design Package

(b) Launch Solution Maturity

(3) Mission Design (Oral and Visual)

(a) Design Interface

(b) Design Orbit

(c) Launch Authority

(d) Mission Assurance Plan

Program Management (Oral and Visual) Work Breakdown Structure (WBS): Provide a WBS sufficiently detailed to describe the work proposed to be performed in accordance with the MRD. The WBS should cover the entire scope of the work required to successfully accomplish the mission of this solicitation; i.e. contract execution, design, test, production, mission assurance, logistics, range preparation, payload integration, launch ops, etc. This can be in outline or block format, but should be at least to the 3rd level of detail.

Integrated Master Schedule (IMS): Provide an IMS corresponding to the proposed WBS reflecting the order, duration and dependencies of scheduled tasks. Dates should be nominal and reflect a contract award of 01 January 2019.

Launch Solution Design (Oral and Visual): Describe the Offeror’s launch capability and heritage.

Launch Solution Design: Provide a comprehensive design for the proposed Launch Solution (LS) that meets requirements stated in the MRD. A LS is defined as the Launch Vehicle (LV), support equipment, facilities and associated processes that are utilized to deliver the payload to orbit. The design should be sufficiently detailed to describe the key components of the LS. The LS design package should provide design and performance details on key systems/subsystems of the proposed launch solution as applicable. Examples are provided in Table 4-1. Offerors are encouraged to make use of pre-existing design material if available. Any mission unique design changes required to meet the requirements for this solicitation should be clearly identified.

Table 41: Launch Vehicle Major Systems

Launch Solution Maturity: Demonstrate how the Offeror’s proposed LS design meets the flight history requirements in the MRD.

Provide a system-level design analysis that identifies all subsystems and demonstrates how those subsystems will be integrated and tested to provide the proposed orbital insertion performance; and provide a maturity assessment for each subsystem which identifies the degree to which that subsystem's performance has been verified via test.

Provide the full flight history of the proposed LS. Flight history data should include the mission nomenclature and date of the flight, the orbit parameters required and achieved, and any anomalies/failures observed in the LS. Identify in the flight history any LS configuration differences (e.g., different fairing, alternate insertion stage, etc.) from the proposed LS.

Mission Design (Oral and Visual): In the following sections, demonstrate/describe how the Offeror’s LS (as provided in Section 4.2.2) will be used/configured to successfully accomplish the mission of this solicitation.

Design Interface: Demonstrate how the proposed LS design will interface (ie, mechanical, electrical, environmental, etc.) with the payload characteristics specified in the MRD.

Design Orbit: Demonstrate how the design performance will meet the mission orbital requirements in the MRD.

Launch Authority: Describe the approach for working with the cognizant launch authority for the mission. Identify the approach for coordinating and verifying LS system interfaces to the range, the range safety coordination approach for complying with 14 CFR Part 417 (or equivalent document specified by the proposed range). Identify any proposed tailoring of range safety requirements, and the approach to gaining approval of said tailoring.

Mission Assurance Plan: Describe the Offeror’s internal mission assurance processes as they will be applied to this solicitation. Identify, in relation to the LS’s flight history, how these processes have impacted mission success and any evolution over time. Describe the Offeror’s approach to flightworthiness accreditation and licensing Volume II (Factor 2) - Price: All information relating to the proposed price, including all required supporting documentation must be included in the section of the proposal designated as the Price Volume. Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your price position. Reference the Price Volume as required, but under no circumstances shall this information and documentation be included elsewhere in the proposal.

General Instructions – The Price volume shall contain the information requested in the paragraphs below. The Offeror shall submit other-than-certified pricing data (per FAR 15.403-1(b), 15.403-3(a), and FAR 15.403-5) for the Government evaluation. The proposal must contain sufficient details for the Government evaluation of reasonableness, and for the Government’s best value decision.

Compliance with these requirements is mandatory and failure to comply may result in a determination of non-compliance.

Offerors shall submit the electronic copy of this volume in an unprotected .XLS file format, including formulas.

Use of contractor formats is encouraged, provided that all the required data is made available. This information is not considered certified cost or pricing data and thus certification is not required in accordance with FAR 15.406-2. If, after receipt of proposals, the PCO determines that there is insufficient information available to determine price reasonableness and none of the exceptions at FAR 15.403-1 apply, the Offeror shall be required to submit additional cost or pricing data.

Volume Organization – The Price volume shall consist of the following sections:

(1) Table of Contents

(2) Narrative

(3) Total Proposed Price Table

(4) Glossary Price Detail – Narrative: As an introduction, the Offeror shall provide comprehensive narrative support for the Price proposal for the Price volume explaining the philosophy methodology and assumptions used in proposing the dollar amounts. Summary descriptions of estimating, purchasing, and accounting systems, changes to estimating, accounting practices or Cost Accounting Standards (CAS) Disclosure Statement.

“Buy American” Compliance: Offeror shall include any documentation necessary to show that the proposed LS is in compliance with the “Buy American and Hire American” executive order and with FAR 25.101(a) Manufactured in the United States, and The cost of the LS’s domestic components exceed 50% of the cost of all components.

CLIN Structure: Mission Design, Integration and Launch Services of this mission will be Firm Fixed Price (FFP). The offeror shall include a Firm Fixed Price for an option to award a second launch service using the same LS, which may be exercised within one year of the contract award date. Data CLINs will not be separately priced (NSP). A visual representation of the proposed requirements is shown below.

Table 51: CLIN Structure

FFP

Estimating Techniques and Methods: When responding to the Price Volume requirements in the solicitation, the Offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships (CERs), commercially available parametric cost models, in-house developed parametric cost models, etc.) to develop their estimates.

Rounding: All dollar amounts provided shall be rounded to the nearest dollar.

Volume III - Contract Documentation:

General Instructions – The purpose of this volume is to provide information to the Government for preparing the contract documents and supporting file. The Offeror’s proposal shall include a signed copy of the Model Contract, and Section K.

0. Volume Organization – The Contract Documentation Volume shall consist of the following sections:

Section 1.0 - Standard Form 33. Provide Standard Form 33. The Offeror shall complete blocks 12 through 18. Signature by the Offeror on the SF33 constitutes an offer, which the Government may accept. The “original” copy should be clearly marked.

Section K. Provide RFP Section K. The Offeror shall complete their certification, representation, and other statements.

Other Information:

Exceptions to Terms and Conditions: Exceptions taken to terms and conditions of the model contract, to any of its formal attachments, or to other parts of the solicitation shall be identified. 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 in the table below. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award.

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. Also, provide the name, position, and contact information for the person or persons to be notified of the award decision by the Source Selection Authority or designated representative.

Government Offices: Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Administrative officer, DCAA, and the Government Paying office.

Company/Division Address, Identifying Codes, and Applicable Designations;

Provide company/division’s street address, county and facility code; CAGE code: DUNS code; size of business (large or small); and labor surplus 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.

Organizational Conflict of Interest Plan:

In accordance with FAR 9.5, Organizational and Consultant Conflicts of Interest, the Contracting Officer has analyzed the planned acquisition and determined that no known actual or potential Organizational Conflict of Interest (OCI) situations exist with respect to this solicitation.

The Offeror shall perform its own OCI analysis and submit the results of that analysis as part of its proposal. Specifically, the Offeror shall analyze the planned acquisition for actual or potential OCI situations associated with its or any of its teammate’s or subcontractor’s performance under any contract it or any of its teammates or subcontractors has been or may be awarded by any federal agency or other entity. The Offeror shall describe in detail the methodology used to identify actual or potential OCI issues. If the Offeror identifies any actual or potential OCIs with respect to the performance of itself or its subcontractors or teammates, the Offeror shall provide an Organizational Conflict of Interest (OCI) Mitigation Plan to be incorporated as an attachment to any resulting contract. At a minimum, the plan shall address all of the items identified in the most current version of SMC’s OCI Mitigation Plan Checklist provided as an attachment to this 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.

If award is made to the Offeror, the resulting contract may include an organizational conflict of interest limitation applicable to subsequent Government work, at either a prime contract level, at any subcontract tier, or both. During evaluation of proposals, the Government may, after discussions with the Offeror and consideration of ways to mitigate or avoid identified actual or potential conflicts of interest, insert a clause or term and condition in the resulting contract which disqualifies the Offeror from further consideration for award of future contracts.

Resolution of OCI issues are treated in a manner similar to the Contracting Officer’s contractor responsibility determination. Any communications necessary to resolve OCI issues shall not be considered discussions. As such, the Contracting Officer may issue Evaluation Notices to the Offeror prior to any decision to enter into discussions in order to resolve questions or concerns with the Offeror’s OCI analysis or mitigation plan.

List of Appendices A – Solicitation Correlation Matrix

Appendix A: Solicitation Correlation Matrix

The matrix below provides cross-reference between the RFP Section L, Section M, and Proposal Technical Volume. The purpose of this matrix is to identify to the Offeror where each proposal element required by Section L will be evaluated per Section M. When completed by the Offeror, the Proposal column should reflect the proposal section responding to the cited Section L paragraphs.

SECTION L FA8818-18-R-0011

PAGE L - 4 of 16