SRP-4_Draft_Section_L.docx

DRAFT

FA8818-16-R-0022

Attachment X

Information to Offeror’s and Instructions for Proposal Preparation

Basic: Feb 2016

REVISION HISTORY

SECTION L-I

TBD

SECTION L-II

TBD

SECTION L-III

Instructions, Conditions, and Notices to Offerors or Respondents Program Structure and Objectives General Requirements - The Air Force Space and Missile Systems Center (SMC) is anticipating the award of multiple Indefinite Delivery/Indefinite Quantity (IDIQ) Small Rocket Program-4 (SRP-4) contracts to provide launch services for delivering payloads, flight hardware and studies in support of US Government missions. This effort will be a competitive source selection with Task Order (TO) competitions for future launch service missions. The ordering period is anticipated to be 7 years. The general requirements to qualify as a launch service contractor to compete for future task orders are defined in Section L. TO launch service capability requirements are defined in the Performance Work Statement (PWS) while mission specific requirements are defined in the Mission Requirements Document (MRD) for each mission.

Missions - The overall capability to be provided by this contract is divided into two groups.

Group 1: Suborbital missions Group 2: Orbital mission 0-400 lbs (181 kg) to LEO or similar capability (e.g., a lighter weight to a higher orbit) Offerors may propose services to meet the requirements of one or the other group. Offerors can compete for future task orders across groups after award of the basic contract.

In Group 1, Suborbital, offerors shall propose launch solutions for sample missions 1-1 and 1-2.

In Group 2, Orbital, offerors shall propose launch solutions for sample missions 2-1 and 2-2.

Credit will be given for offerors who successfully propose an additional sample mission in another group. Pricing is not required for this optional sample mission.

Sample Missions - The Government has provided a set of sample missions (Appendix E) in each group for offerors to propose to. Each sample mission is defined by a MRD. The Government reserves the right to award TO’s for any or all of the sample missions in conjunction with the basic IDIQ contract award, based upon a tradeoff determination.

Minimum Order - If an offeror is selected for award of an IDIQ contract, the offeror will be awarded a special study TO to provide a DoD-specific user’s guide for their primary orbital launch vehicle if the prime award is in that group, in lieu of the award of a sample mission. The user’s guide will provide information on the contracted launch solution necessary for potential satellite or payload developers to understand the interfaces, launch environments, available payload volume, ordnance/command discrete available, power available, etc. necessary to design an Interface Requirements Document and/or decide if the launch solution is capable of placing the satellite/payload into the required orbit/trajectory. Specific requirements for this Launch Service User’s Guide will be included post award of the basic contract. If the prime group is suborbital an analysis special study will be awarded with specific requirements for this study post award of the basic contract in lieu of the award of a sample mission. The award of the TO to produce this DoD-specific user’s guide or special study will constitute the guaranteed minimum amount ordered by the Government under an IDIQ contract.

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. The offer shall be compliant with the requirements as stated in Sec L, PWS, MRD, Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this document may result in an unfavorable proposal evaluation.

Written Proposal - The offeror’s proposal shall consist of a written submittal. All information provided, as long as it is consistent with the constraints of this RFP (e.g. page limitations), 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 system(s), process (es), facility (ies) 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 through this date.

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

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.

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, to include matters of additional or substitute pages of the initial proposal.

Electronic Reference Documents (Bidder’s Library): Bidder’s Library documents for this solicitation may be available on request from the CO. Documents will be released via Compact Disc (CD) to potential bidders on file with the CO.

Oral Presentations: Oral Presentations will not be conducted for this acquisition.

Communications: Exchanges of source selection information between Government and offerors will be controlled by the CO. Email may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information - See FAR 2.101 & 3.104” in the Subject line. Otherwise, source selection information will be transmitted via 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 (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 volumes identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The technical appendices may be bound separately, if necessary. The contents of each proposal volume are described in the paragraph as noted in the table below.

Table 2.2 - Proposal Organization

Section

Due ~X Days After RFP Release

(Overview of Technical Proposal and Technical Risk)

Suborbital or Orbital Capability: 20 [10 per sample mission (2 required missions)]

Optional Additional Sample mission 10

I

4.2.5 4.2.5.1 4.2.5.1.4.1 4.2.5.2 4.2.5.3 4.2.5.4

Technical Appendixes

PMP

QA Certificate Orbital Debris Analysis Sample Mission IS(s) Sample Mission BOE (s)

Unlimited

PAST PERFORMANCE

3 for each contract up to 3 contracts. Not to exceed a total of TBD pages for Volume 5.

COST/PRICE

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 the paper copy.

* Technical Volume is a total of 30 pages for Subfactor 1, 20 pages for the Subfactor 2, an additional 10 pages for the optional sample mission, and unlimited pages for the technical appendices *** Refer to FedBizOpps for actual date and time of submission deadlines.

Page Limits: 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), if necessary. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Unless otherwise specified, each page shall be counted except the following: cover pages, tables of contents, tabs, glossaries, correlation matrix, technical appendices, past performance questionnaires, organizational structure change histories, consent forms and client authorization letters 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 may be single spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 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 also 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, 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 8.5 x 11 inch surface of a foldout shall be counted as a separate 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 10 point. These limitations shall apply to both electronic and hard copy proposals.

Cost or Pricing Related Data: Pricing information will not be included in Section B of the Schedule of the RFP. This information will be in Attachment TBD including rates for the period of performance of the contract and will be referenced in Section B. Information shall be limited to approved direct labor rates and indirect rates.

Classified Information: Do not include classified information in proposals.

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 minimal 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 cross-referencing conserves space without impairing clarity. The offeror shall provide a Solicitation Correlation Matrix that cross references between the Sec L, Sec M, the Contractor Proposal, the Contractor Work Breakdown Structure (CWBS), PWS, MRD and the CDRLs. This matrix shall be attached to the Technical Volume and will not be counted against the page count. An example of an entry in a correlation matrix is shown below. The Correlation Matrix shall not contain informational notes, as the volumes provide ample opportunity for discussion and description of the Offeror's approach.

MRD

CDRL

Sect 3.2

Indexing: Each volume shall contain a more detailed table of contents to delineate the contents within that volume, which does not count against page limitations. Tab indexing shall be used to identify sections.

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.

Binding and Labeling: Each volume of the proposal shall be separately bound in a three-ring, loose leaf binder(s) 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, including subfactors, 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 2010, MS Office Excel 2010, MS Office Project 2010, and MS Office Power Point 2010, as applicable. In the event that hard copies and electronic copies of a proposal are submitted and if 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 CO and mailed or hand carried to:

SMC/ADK

Attn: Cassandra Way 3548 Aberdeen Ave Kirtland AFB, NM 87117 Proposals received after the date and time specified shall be treated in accordance with FAR 52.215-1

Volume 0 - Executive Summary Executive summary volume - The offeror shall provide the following information:

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 cost/price. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

Mission Capability Technical Approach Summary: Offeror shall provide a separate summary narrative on their technical approach for the Mission Capability Subfactor 1. The narrative will be used in preparation for the government’s Proposal Assessment Report (PAR), to characterize the offeror’s approach for this sub-factor. The narrative shall not exceed two paragraphs or 30 lines of text.

Mission Accomplishment Technical Approach Summary: Offeror shall provide a separate summary narrative on their technical approach for the Mission Accomplishment Subfactor 2. The narrative will be used in preparation for the government’s PAR, to characterize the offeror’s approach for this sub-factor. The narrative shall not exceed two paragraphs or 30 lines of text.

Non-Governmental Advisors - Per DoD Source Selection Procedures paragraph 1.4.5.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, who will be acting as non-Government advisors.

Table of Contents - Include a master table of contents of the entire proposal.

Volume I (Factor 1) - Technical Volume General - 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 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 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 - This RFP contains the Government prepared Section L launch capability requirements, a launch service PWS, and a MRD that outlines launch requirements for each sample mission. The basic tasks covered by this RFP are to describe the offeror’s capability and processes to design, build, test, and launch suborbital and orbital launch vehicles, and to describe and provide specific solutions for sample missions per PWS and MRD requirements.

Technical: In the technical volume, the offerors shall address the technical solution for meeting or exceeding the Government’s minimum performance or capability requirements of each technical subfactor.

Volume Organization Technical volume shall be organized according to the following tab outline:

(1) Table of Contents

(2) Glossary

(3) Subfactor 1: Mission Capability

(4) Subfactor 2: Mission Accomplishment For a Suborbital sample mission both are REQUIRED:

For an Orbital sample mission both are REQUIRED:

Optional Sample Mission (Suborbital or Orbital)

(5) Technical Appendices

Factor 1: Technical (Overview of Technical Proposal and Technical Risk). Describe the overarching launch processes and capabilities you are proposing along with any risks. This section should discuss common elements among LV designs and flight heritage.

Subfactor 1: Mission Capability Launch Vehicle Design. Describe the offeror’s approach and capability to design a variety of suborbital and/or small orbital launch vehicles using commercial and/or GFE stages, and other required hardware meeting all technical, mission, and safety requirements. This includes the approach to (a) design launch vehicles based on a range of motors and engines; (b) incorporate different national test range ground and safety requirements into the design of the launch vehicle systems; (c) design, and develop necessary modifications to the booster motor, to include guidance and control hardware and software, and attitude control systems capable of performing post-boost maneuvers.

Manufacturing / Test. Describe the offeror’s approach and capability to fabricate and test necessary components and provide required modifications to the boosters and other required structures. This includes the ability to (a) manufacture and test attitude control hardware capable of performing required post-boost maneuvers; (b) fabricate, modify, integrate, and test guidance and control systems; (c) provide facilities, tooling, support, and test equipment for both hardware and software, which the contractor will maintain and utilize for testing, manufacturing, integration and analysis; (d) provide facilities to safely test individual components and integrated systems; (e) safely transport hardware, including rocket motors and pyrotechnic device; (f) obtain access to a manufacture and testing facility with facility clearance at the SECRET/NOFORN level.

Mission Assurance (MA). Describe offeror’s internal MA process and the offeror’s approach to interfacing with the government’s category one and category two MA processes.

Program Management. Describe the offeror’s approach to provide program management activities, integrating systems engineering and other activities (see para 4.2.5).

Subfactor 2: Mission Accomplishment For Suborbital: Sample Mission 1-1 and 1-2 must be proposed For Orbital: Sample Mission 2-1 and 2-2 must be proposed For a potential credit, one unpriced sample mission from the other group may be proposed.

For each sample mission discuss the offeror’s launch solution and concept of operations for meeting the mission requirements per the MRD. In addition the offeror shall:

Identify the technical performance measures and risk mitigation for the proposed LV that supports the mission requirements and will provide the required insertion/delivery accuracy.

Describe the approach for working with the cognizant range for the mission to include LV system interfaces to the range, the range safety approach for complying with AFSPCMAN91-710 (or equivalent document specified by cognizant range) and any proposed tailoring.

Describe how the offeror plans to conduct orbital debris analysis, end-of-mission de-orbit analysis, and any other analyses necessary to demonstrate compliance with AFI 91-217, for the launch vehicle solution. (Orbital Sample Missions Only) Provide (in Tech Appendices) a separate Integrated Schedule per PWS requirements for each sample mission.

Provide in the Technical Appendices a BOE including task descriptions, labor hours, and materials associated per Sec L, par 4.2.5.4 for each sample mission Technical Appendices Program Management Plan. The PMP shall describe the offeror’s approach and capability to provide program management activities, integrating systems engineering and other activities. This includes (a) process for interfacing with several independent payload contractors, Government agencies, and range safety offices; (b) capability of efficiently integrating systems engineering disciplines such as risk management, configuration management, reliability, quality assurance, safety, manufacturing, etc. and (c) facilities and procedures for processing and handling SECRET/NOFORN data. The PMP shall list and describe the offeror’s requirements documents (Systems Requirement Documents and specifications or similar documents) and internal processes. The events in the PMP will correspond to development and/or production activities required by the contract. It will encompass all steps necessary to satisfy contract objectives and requirements, manage all significant risks, and facilitate Government insight for each event. The PMP shall also include the following sections described below: Contract Work Breakdown Structure (CWBS), CWBS Dictionary, Configuration Management Plan, Quality Assurance Plan, Integrated Test Plan, and a Risk Management Plan. The PMP will be included in the Technical Appendices Section and will have unlimited page count. It will also be added as an attachment to the model contract at award.

Contract Work Breakdown Structure (CWBS). An example Work Breakdown Structure for a generic LV has been provided in Appendix A. The reference document for developing the WBS and dictionary is MIL-HDBK-881C Appendix J. The offeror shall develop a Contract Work Breakdown Structure (CWBS) which reflects their view of the effort. The CWBS shall serve as the framework for organizing SRP-4 to include in-house, inter-divisional, subcontractor, and associate contractor activities. The offeror may add, re-arrange, and/or combine the WBS elements shown in accordance with their approach, but supporting rationale shall be provided. The CWBS shall be developed to a depth (level) and breadth sufficient to accurately describe the offeror's understanding of the effort required for a generic mission.

CWBS Dictionary. The offeror shall use the PWS to propose a CWBS as described above. Each element of the CWBS shall be described in detail in a CWBS Dictionary. A complete definition of the tasks to be accomplished shall be provided in the CWBS Dictionary and execution of these tasks shall be reflected in the sample mission Integrated Schedules. Within the CWBS Dictionary the Offeror shall specify their key internal document(s) that address the work described in each task. Each CWBS Dictionary entry shall reference the CDRL items which will be delivered by that task. The proposed CWBS dictionary shall not contain informational notes, as the Technical volume provides ample opportunity for discussion and description of the Offeror's approach.

Configuration Management Plan. The offeror’s Configuration Management (CM) Plan describes the offeror’s configuration management program. To include how it is organized, how it will be conducted, what are the methods, procedures and controls to include effective configuration identification, change control, status accounting, and audits of the total configuration, including hardware, software and firmware. The principle use is to provide the Government a basis for review, evaluation and monitoring of the CM program and its proposed components.

Quality Assurance Plan. The Quality Assurance Plan (QAP) describes the offeror’s quality assurance program with all of the information, instructions and documentation necessary to produce a quality part, component, equipment, subsystem, or system of high acceptance and in complete conformity with contractual requirements. The QAP will contain measurable quality objectives and the metrics by which they are to be measured. If the offeror’s processes are AS9100 certified (or if you are certified by another national standards organization) provide a copy of this certification. This certification shall be included in the Technical Appendices and will not be counted against the page count.

Integrated Test Plan. The Integrated Test Plan (ITP) describes the offeror’s plans and performance objectives at every level of hardware and software testing on systems or equipment, to include qualification and acceptance level testing. It provides the Government with the test concept, objectives and requirements to be satisfied, test methods, elements, responsible activities associated with the testing, measures required and recording procedures to be used.

Risk Management Plan. The Risk Management Plan (RMP) describes the offeror’s risk management process that establishes risk mitigation strategies, defines risk thresholds, and monitors progress in order to ensure that effects of potential risks are minimized. The RMP shall describe risk management planning, risk identification, risk assessment, risk handling, risk monitoring and control, and process metrics.

Small Business Subcontract Management Plan. Submit a Small Business Subcontracting Plan that meets DoD goals (not required for small business). The offeror's small business goals shall reflect, at a minimum, the goals required by the DoD (TBD% Small Disadvantaged Business, TBD% Women-Owned Small Business, TBD% Hub Zone, and TBD% Small Disadvantaged Veteran-Owned Small Business.) If the offeror has an approved master subcontracting plan (FAR 19.704(b) and 52.219-9(f) or an approved comprehensive subcontracting plan (DFARS 219.702), submit an addendum with its proposal covering any additional information required by this solicitation. The addendum will be incorporated into any resulting contract along with incorporation by reference of the master or comprehensive plan. The offeror's submission must provide sufficient information to support the contracting officer's review of the subcontracting plan to determine if it is acceptable, otherwise an offeror will be ineligible for contract award. Any contract resulting from this solicitation which includes a comprehensive subcontracting plan will include the clause at DFARS 252.219-7004 in lieu of the clauses at FAR 52.219-9; 52.219-16; 52.219-10; and DFARS 252.219-7003. offerors will provide targets of their participation, expressed as dollars and percentages of total contract value. Targets will be incorporated into and become a part of the contract.

LV Orbital Debris Analysis SM 2-1 and 2-2 (Orbital Missions Only). The offeror shall provide a preliminary LV Orbital Debris Analysis that describes any waivers, risks or mitigations required.

Sample Mission IS. The offeror shall provide a complete Integrated Schedule for all sample missions proposed in accordance with the PWS requirements.

Sample Mission BOE Provide the BoE (hours per Labor Category only, see 6.x.x for prohibition against including cost/price data in the Technical Volume) for each effort proposed, demonstrating the offeror’s approach to projecting the effort required. This description should complement and correlate to the relevant entries of the CWBS. The intent of this section is to obtain an understanding of the offeror’s proposal in terms of the scope of work planned for each effort, and to understand the offeror’s cost projection approach. The Offeror shall provide the BoE for each effort proposed, broken out to the CWBS level at which the BoE was developed. The BoE shall use the CWBS designation/numbering system so that tasks can be easily located in the CWBS Dictionary.

Provide narrative to explain your BoE quantities. The narrative shall address how the offeror estimated each major element of the effort and provide rationale for proposed hours and labor mix. Include all assumptions made. Where estimates are based upon past experience, identify the past experience, explain how the past experience relates to the current effort (including similarities and differences), and explain how data available from the past experiences was adapted to the current effort. Also use the narrative to discuss impacts of any trade-offs included in the approach required to ensure the offeror can execute and integrate vital mission operations while ensuring appropriate levels of risk, support to requirements, and meeting execution goals. Include a discussion of the alternatives and why the scope associated with any proposed trade-offs in your approach is reasonable. Address your capability to control and mitigate the effort execution due to reasonably expected and moderate emergencies and contingencies.

Volume II (Factor 2) - Past Performance (NOTE: See Sample questionnaire/assessment format and sample consent and client authorization letters.)

General - Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Appendix C (Attachment 2 to this template). This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform twenty-five (25) (insert percentage) percent or more of the proposed effort based on the total proposed price (or cost, as applicable) or perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

Along with the information required in this paragraph, the offeror shall submit a consent letter, shown in Appendix C, executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter, shown in Appendix C, authorizing release to the Government of requested information on the offeror's performance.

Early Proposal Information - Each offeror is requested to submit the information shown in Appendix C (Attachment 2 to this template) for each relevant contract fourteen (14)(insert number) days prior to the date set for receipt of proposals. Failure to submit early proposal information will not result in offeror disqualification Relevant Contracts - Submit information in accordance with Appendix C (Attachment 2 to this template): Past Performance Information on three (3) recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort. (insert what is considered “recent”, such as ongoing contracts or those completed within three years of the date of issuance of the solicitation) Also include information on one (1) (insert desired number) recent contract performed by each of your teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Include rationale supporting your assertion of relevance.

Specific Content: Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to an unacceptable rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. Submittal of quality performance indicators or other management indicators that clearly support that an offeror overcame past problems is required.

Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company within the past five years from RFP release date. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation. Since the Government intends to consider past performance information provided by other sources as well as that provided by the offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

Volume III (Factor 3) - Price/Cost: TBD Volume V - Contract Documentation: TBD

Appendix A: Sample WBS

The following excerpt from MIL-STD-881C is provided as a sample of a typical LV WBS. It provides sample tasks that reflect the level of detail that is expected at each level of the WBS. Offerors are not required to follow this WBS exactly.

Appendix B: Government Furnished Property List The items listed below are available as of 29 Oct 2015. When current supplies are exhausted no additional units will be available. Contact the POC listed in paragraph 1.2.2 to determine current availability.

Government Furnished Property List - Minutemen

Minuteman

$4,760,440

Other Flight Hardware

NSN: 613-00-819-8074

Transporter/Erector

Note: All Minuteman stages include MMODs, SR19M is converted from SR19

Government Furnished Property List - Peacekeeper

ITEM

AVE

1/2 interstage

2/3 interstage

Other Flight H/W*

W4F Cable Assy

PBPS (PK Stg 4) WD427Cable

GSE

Type II Transporter(s)

1450011181667AI

Oshkosh Tractor(s)

2320011237279AI

Marmon Tractor(s)

Stage 1 Container

8140011201323AI

Stage 2/3 Container

8140011201324AI

Stage I T&H Ring Set**

863T0820000-009 >6

Stage II T&H Ring Set***

863T0830000-009 >6

Stage III T&H Ring Set***

863T0840000-009 >6

863T0960000-009

863T0560000-010, -009

Ground Test

* Other flight Hardware cost is included in the motor costs.

** ILCS cable will not be supplied with motors made available under this contract.

** *Provided with certification for horizontal transport only.

*** Provided with Flight Termination Ordinance System (FTOS), Linear Shaped Charge (LSC), Termination Linear Shaped Charge (TLSC), Thrust Vector Actuator (TVA), Guidance &Control Cable ***** When current supplies are exhausted, no additional cable assemblies will be made available and the LSC will be responsible for supplying this cable assembly.

Appendix C: Past Performance Documents Appendix C is comprised of the following documents which may be found with the RFP on FedBizOpps:

-SAMPLE CLIENT AUTHORIZATION LETTER

-SAMPLE SUBCONTRACTOR/TEAMING PARTNER CONSENT LETTER

-PAST PERFORMANCE QUESTIONNAIRE (PPQ) COVER LETTER

-PAST PERFORMANCE QUESTIONNAIRE (PPQ)

-PAST PERFORMANCE INFORMATION FORM

Appendix D: Pricing Table

TBD

Appendix E: Sample Mission Requirements Documents

Appendix E is comprised of the following documents:

Suborbital Launch Sample Mission 1-1 Suborbital Launch Sample Mission 1-2 Space Launch Sample Mission 2-1 Space Launch Sample Mission 2-2

Suborbital Launch Sample Mission 1-1:

Mission Requirements Document (MRD)

T.O. 000x

REVISION HISTORY

1.0 INTRODUCTION

Overview This document provides the launch vehicle mission requirements for the Sample Mission (SM) 1-1 Suborbital mission, which will be launched under the Small Rocket Program–4 (SRP-4) Contract.

The goals of the SM 1-1 mission are to launch a suborbital demonstration mission to deliver a Re-entry Vehicle (RV) to a specific target location on White Sands Missile Range (WSMR).

The mission responsibility of the Launch Services Contractor (LSC) will end when RV has been deployed.

SM 1-1 is a SRP-4 Mission Assurance Category 2 mission.

Scope This Mission Requirements Document (MRD) is the controlling source and authority for the mission requirements. In addition to specifying mission requirements, this MRD will:

· Identify roles and responsibilities and interfaces among the various contractors and Government agencies supporting the mission.

· Document data provided by the agencies furnishing the RV to be used by the LSC in developing the LV configuration, integrating the RV, targeting the LV, processing the flight hardware, and conducting the mission.

· Identify constraints and environments required by the RV.

· Identify test-and-analysis requirements to verify interfaces between the RV and LV and to verify required RV characteristics.

This MRD will be maintained by the USAF SMC/LEX (RSLP) office. In many cases, the detailed requirements and data will be specified in other documentation, which will be referenced herein. This includes documents such as the SRP-4 Performance Work Statement (PWS) and the LV/RV Interface Control Document (LV/PDV ICD), which identifies detailed RV interface requirements and the range requirements documentation developed in accordance with the Universal Documentation System (UDS).

Roles and Responsibilities The roles and responsibilities of the agencies and contractors that will support the mission are described below:

Payload Program Office (PPO): The PPO provides the RV and down range sensor systems. PPO’s activities and responsibilities include:

· Participation in program management

· Provision of RV range-safety documentation at the request of the USAF

· Shipping the RV to the launch site LEX: The RSLP branch (LEX) of the USAF’s Launch Enterprise Directorate (USAF/SMC/LE), located at Kirtland AFB, NM, is responsible for SRP-4 launch systems and launch operations. Its activities and responsibilities include:

· Participation in program management (lead for launch segment)

· Range support

· LV integration

· PDV interface and mating Mission Assurance Contractor (MAC): A mission-assurance contractor, under contract to the LEX, shall provide Mission Assurance and Independent Verification and Validation support for the LV. Higher-level risks identified by the MAC will be sent to the PPO in monthly status updates provided by the Mission Manager (MM), and overall risk assessments of the program will be addressed in design reviews and readiness reviews.

LSC: A launch-vehicle contractor, under contract to LEX, will provide the LV design, the LV, integration and interface to the PDV, vehicle mating, mission planning, and launch of the LV.

The LSC shall ensure that Associate Contractor Agreements are completed for the following associate contractors:

· METIS contractor

· Arctic Slope Federal Space and Federal

· TASC

· Tecolote Research, Inc If necessary, the LSC shall also ensure that Non-Disclosure Agreements are completed for the above contractors.

2.0 MISSION REQUIREMENTS

Mission Scenario: The launch will be a ballistic trajectory with a nominal ground range of approximately 120 km, apogee of (contractor derived) kilometers depending on Range and target locations.

Performance Error Distribution: For flight performance parameters noted in this document with an indicated acceptable error margin (i.e., +xx), that margin represents a 3-sigma deviation from the expected system performance unless otherwise noted.

Target Description Vehicle Configuration: The final launch vehicle configuration will be a unitary configuration with a non-separating payload using an Mk 11C aeroshell provided GFE.

Payload Integration: Contractor shall integrate the MK11 aeroshell with TBD associated payload Telemetry (TM): The RV TM shall be selectable. The transmitters shall have sufficient power to provide adequate link margins as defined by WSMR Flight Safety Documentation. The launch contractor shall be responsible for all housekeeping, instrumentation, and position data links. Encryption is not required.

Environmental Control: The contractor shall ensure the motors used are maintained within environmental limits in accordance with Air Force Technical Order (TO) specifications for motor exposure, if GFE provided.

Date/Time: The RV mission is scheduled for fourth quarter Fiscal Year 2018 (FY18). There will be no back-up vehicles built for this mission.

Range Coordination: All test operations at the range will be conducted in accordance with an approved Operations Requirement (OR) for the mission (to be published), and applicable range documents.

Trajectory Profile: The mission flight profile will be a ballistic trajectory of 120 km ground range and an apogee of (contractor derived) km. The preliminary aim point is TBD a minimum survivable altitude is 20 km.

Downrange Dispersion: The RV shall have a downrange dispersion at aim point altitude of less than ± 5 km.

Cross-range Dispersion: The RV shall have cross-range dispersion at the aim point altitude of less than ± 5 km.

Terminal Target Flight Dynamics: The contractor shall meet the terminal velocity of 1500 +/- 150 m/sec.

Measurements: Vehicle status consisting of guidance, GPS and attitude data, environmental data (to include thermocouple data), and housekeeping functions shall be measured via telemetry. The RV position, velocity, and attitude shall be measured on-board throughout the flight via the RV inertial measurement unit (IMU) and shall be displayed real-time at WSMR via RV telemetry (TM).

Data Handling/Distribution: Handling and distribution of telemetry data will be as described in the OR.

Post processed Target Trajectory Measurements Kinematic Instrumentation: Instrumentation to provide accurate reporting of the position, velocity, and acceleration, of the payload are required. Acceptable tolerances on this instrumentation are 1.0 m per axis in position, 1.0 m/sec per axis in velocity, and 1.0 m/sec2 per axis in acceleration. Acceptable tolerance for post launch pointing data is 2.5 degrees per axis. This data required at a data rate of 50 Hz or better.

Payload MK11 Aeroshell: Integrate a MK11 Aeroshell with TBD payload for a unitary mission.

· RV Payload mass <3700 lbs.

· RV CG: 36 in from base

GPS Receiver (or equivalent): The RV mission shall incorporate an onboard GPS position source or a differential GPS ground system capable of 1 m accuracy (1 sigma) post-launch, for best estimate trajectory determination.

C-Band Beacon: A C-band beacon capability shall be incorporated into the RV front section.

Weather Proofing: The launch vehicle is required to survive up to two hours unsheltered and exposed to the normal/average weather conditions for WSMR , e.g. rain, fog, hail, snow, etc., during the planned launch window.

Launch Campaign Transportation: The Launch Contractor is required to ship all RV Target mission hardware, including mission related experiment and GFE hardware (excluding GFE motors), to and from WSMR. The launch contractor is required to ensure the GFE Booster environmental protection requirements are satisfied, if required.

Option for Modal Survey: This option is for a modal survey characterizing the launch vehicle for bending modes and frequencies. The survey shall include the entire front section and/or the entire vehicle with a GFE inert motor. All data and test procedures will be reviewed and approved by the government. If the proposed launch vehicle has been previously characterized for bending modes and frequencies, available data from applicable sources may be used in place of new analyses. The data must be justified and its applicability substantiated.

Option for Pathfinder at WSMR: This option is for a complete mechanical and electrical checkout of the RV with the range to include the launch pad and stool, Launch Control Center, telemetry, flight termination system, TE, and processing. An inert GFE motor will be provided. Note the pathfinder vehicle will be mechanically and electrically equivalent of the flight vehicle.

3.0 ACRONYM LIST

Suborbital Launch Sample Mission 1-2:

REVISION HISTORY

This…