07_Attachment_5_Instructions_to_Offerors_and_Appendixes.pdf
PDF 5 MB Posted
- Solicitation number
- FA8811-17-R-0004
About this file
Attachment 5: Instructions to Offerors
View the file
Other files
Show all 26
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions to Offerors FA8811-17-R-0004
Evolved Expendable Launch Vehicle (EELV) Phase 1A
Competitive Acquisition for GPS III, AFSPC-8, AFSPC-12, and AFSPC-52 Launch
Services
FA8811-17-R-0004
Attachment 5
Instructions to Offerors
03 May 2017
1 PROGRAM STRUCTURE AND OBJECTIVES 1
The Air Force Space and Missile Systems Center (SMC) anticipates multiple awards for launch 2 services delivering multiple missions to orbit, detailed in Annexes 1–4. The general 3 requirements for the launch services are defined in the Performance Work Statement (PWS) and 4 Contract Data Requirements List (CDRL), while mission-specific requirements are defined in the 5 mission-specific Mission Requirements Annex (MRA). Requirements in the PWS with specific 6 National Reconnaissance Office-only references and CDRLs with specific National 7 Reconnaissance Office-only references are not applicable and appear in grey text. 8
2 GENERAL INSTRUCTIONS 9
The Offeror's proposal must include all data and information requested by this Request for 10 Proposal (RFP) and shall be submitted in accordance with (IAW) these instructions. In 11 developing the proposal, the Offeror shall ensure that its proposed offer complies with all the 12 requirements contained in the RFP, to include the PWS, MRAs, and CDRLs. Noncompliance 13 with the instructions provided in this RFP may result in a determination that the proposal is 14 nonresponsive and unawardable. 15
The Offeror’s proposal shall be clear and concise and shall include sufficient detail for effective 16 evaluation and for substantiating the validity of stated claims. The proposal should not simply 17 rephrase or restate the Government's requirements, but shall provide convincing rationale to 18 address how the Offeror intends to meet these requirements. Offerors shall assume that the 19 Government has no prior knowledge of its capabilities and experience and will base its 20 evaluation on the information presented in the Offeror's proposal. If the Government enters into 21 discussions, it reserves the right to make a written request for proposal updates to incorporate 22 any directly relevant information from ongoing early integration studies, mishap and anomaly 23 findings, and updates to the joint work plan schedules or launch vehicle certification(s). 24 Elaborate brochures or documentation, detailed art work, or other embellishments are 25 unnecessary and are not desired. The proposal validity date must be specified and the proposal 26 must be valid for at least 180 days after date of submission. IAW Federal Acquisition 27 Regulation (FAR) Subpart 4.8 (Government Contract Files), the Government will retain one 28 copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will 29 destroy extra copies of such unsuccessful proposals. 30
This RFP includes six missions consisting of three GPS III missions, Air Force Space Command 31 (AFSPC)-8, AFSPC-12, and AFSPC-52. This RFP is organized such that the Small Business 32 factor and the Past Performance factor are overarching criteria that will be evaluated once and 33 applied to each mission. Annex 1 contains mission-specific criteria for the GPS III missions, 34 Annex 2 contains mission-specific criteria for AFSPC-8, Annex 3 contains mission-specific 35 criteria for AFSPC-12, and Annex 4 contains mission-specific criteria for AFSPC-52. Each 36 mission annex is represented within the Instructions to Offerors (Attachment 5) and Evaluation 37 Criteria (Attachment 6). 38
Unless otherwise agreed to by the Contracting Officer, it is mandatory for offerors to respond via 39 a proposal or request for waiver to each mission. In the event there arises legitimate reasons for 40 an offeror not to submit a proposal for a particular mission (e.g. limited capacity to perform, 41 excessive performance capability, or inability to achieve certification by award date) the 42
Contracting Officer may waive the requirement for proposal submission for that mission(s). All 1 waivers must be approved prior to proposal submittal. 2
The Government intends to make multiple award decisions: individual award decisions for (1) 3 the three GPS III missions (winner-take-all), (2) AFSPC-8, (3) AFSPC-12, and (4) AFSPC-52. 4 The Government reserves the right to make all award decisions at once or rolling award 5 decisions. Should an Offeror be awarded multiple missions, the missions shall be awarded and 6 executed on one contract. Four separate award decisions shall be made to the Offeror(s) that 7 receives an acceptable rating in the relevant factors and sub-factors, with the lowest reasonable 8 and balanced Total Evaluated Price. The Total Proposed Price (TPP) will be the price put on 9 contract. 10
3 GENERAL INFORMATION 11
3.1 POINT OF CONTACT 12
The Procuring Contracting Officer (PCO), Ms. Dzung Dom, is the sole point of contact for this 13 acquisition. Address any questions or concerns you may have to the PCO at 14 dzung.dom@us.af.mil or 310-653-3696. Written requests regarding this RFP may be sent to the 15 PCO at the address for Launch Enterprise contracting office (SMC/LEK) located on the front 16 page of the model contract/solicitation. 17
3.2 DEBRIEFINGS 18
The PCO will promptly notify Offerors of any decision to exclude them from the competitive 19 range, whereupon they may request and receive a debriefing IAW FAR 15.505. In addition, the 20 PCO will notify unsuccessful Offerors of the source selection decision IAW FAR 15.506. Upon 21 such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring 22 a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as 23 applicable. 24
3.3 DISCREPANCIES 25
If an Offeror believes that the requirements in this RFP contain an error or omission, or are 26 otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting 27 rationale as well as the remedies the Offeror is asking the PCO to consider as related to the 28 omission or error. 29
3.4 ELECTRONIC REFERENCE DOCUMENTS 30
Referenced documents for this solicitation are available at http://www.fedbizopps.gov. Potential 31 Offerors are encouraged to subscribe for real-time e-mail notifications when information has 32 been posted to the website for this solicitation. 33
3.5 EXCHANGES 34
Exchanges of source selection information between the Government and Offerors will be 35 controlled by the PCO. Source selection information will be transmitted in person or via 36 certified mail, delivery service, or facsimile. 37
3.6 DISCUSSIONS 1
The Government reserves the right to award without discussions by mission. However, the 2 Government may conduct discussions with Offerors after establishing a competitive range by 3 mission based on the ratings of each proposal against all evaluation criteria. Discussions may be 4 held on a mission-by-mission basis. 5
3.7 USE OF NON-GOVERNMENT ADVISORS 6
Offerors are advised that data submitted to the Government in response to this solicitation will be 7 released to individuals who work for the following companies as non-Government advisors for 8 review and analysis: 9 Company Name Address 12 The Aerospace Corporation PO BOX 92957, Los Angeles, CA 90009-2957 13 Tecolote Research, Inc 2120 E. Grand Avenue, Suite 200, El Segundo, CA 90245 14
Offerors are advised that data submitted to the Government in response to this solicitation may 15 be released to individuals who work for the following companies as non-Government advisors 16 for administrative support. 17
Company Name Address 18 Business and Technology Solutions 3572 Dayton-Xenia Rd, Suite 210, Beavercreek, 19
OH 45432 20
ARRAY Information Technology 7474 Greenway Center Dr, Suite 600, Greenbelt, 21
MD 20770 22
Individuals from the above support contractors have signed individual non-disclosure agreements 23 with the Government, which strictly prohibits any release or disclosure of information outside of 24 the source selection team. 25
3.8 ALTERNATIVE PROPOSALS 26
Alternative proposals will not be considered. Alternative proposals are those that do not meet 27 the terms and conditions of the RFP, including attachments. 28
4 PROPOSAL FORMAT/LIMITS 29
4.1 ORGANIZATION/NUMBER OF COPIES/PAGE LIMITS 30
The Offeror shall prepare the proposal as set forth in Table 4-1: Proposal Organization. The 31 titles and contents of the volumes shall be as defined in this table, all of which shall be within the 32 required page limits. The Volumes identified in the table shall be separately bound in three-ring, 33 loose-leaf binders, plus each Volume’s electronic copy shall be saved on a separate compact disc 34 (CD) or digital video disc (DVD). For Volume IV, provide page separation tabs for each sub-35 factor. The Offeror shall provide two hard copies of the proposal and two electronic copies of 36 the proposal on CDs or DVDs. The contents of each proposal volume are described in the 37 paragraph as noted in the table below: 38
IVa GPS III Factor 3:
Performance Subfactor 1: Orbital Accuracy 2 2 175
Subfactor 2: Mass-to-Orbit
Subfactor 3: Launch Operations (CONOPS)
Factor 4: Schedule Subfactor 1: Integrated Master Schedule 2 2 Unlimited
Subfactor 2: Risk Mitigation Plans
IVb AFSPC-8 Factor 3:
Performance Subfactor 1: Orbital Accuracy 2 2 175
Subfactor 2: Mass-to-Orbit
Subfactor 3: Launch Operations (CONOPS)
Factor 4: Schedule Subfactor 1: Integrated Master Schedule 2 2 Unlimited
Subfactor 2: Risk Mitigation Plans
IVc AFSPC-12 Factor 3:
Performance Subfactor 1: Orbital Accuracy 2 2 175
Subfactor 2: Mass-to-Orbit
Subfactor 3: Launch Operations (CONOPS)
Factor 4: Schedule Subfactor 1: Integrated Master Schedule 2 2 Unlimited
Subfactor 2: Risk Mitigation Plans
IVd AFSPC-52 Factor 3:
Performance Subfactor 1: Orbital Accuracy 2 2 175
Subfactor 2: Mass-to-Orbit
Subfactor 3: Launch Operations (CONOPS)
Factor 4: Schedule Subfactor 1: Integrated Master Schedule 2 2 Unlimited
Subfactor 2: Risk Mitigation Plans
Va GPS III Factor 5: Price 2 2 Unlimited
Vb AFSPC-8 Factor 5: Price 2 2 Unlimited
Vc AFSPC-12 Factor 5: Price 2 2 Unlimited
Vd AFSPC-52 Factor 5: Price 2 2 Unlimited
VI Model Contract 2 2 Unlimited
Note: AFSPC = Air Force Space Command
4.2 PAGE LIMITATIONS 2
Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or 3 considered in the evaluation of the proposal, and excess paper copies will be shredded. If the 4 Government issues Evaluation Notices (EN) for discussions, page limitations may be placed on 5 responses to EN. The specified page limits for EN responses will be identified in the letters sent 6 along with the EN to the Offerors. Unless otherwise specified, each page shall be counted except 7 the following: cover pages, table of contents, tabs, and glossaries. Additionally, for Schedule 8 Factors the Offeror may include an unlimited narrative to articulate the proposed schedule. 9
4.3 PAGE SIZE AND FORMAT 1
A page is defined as each face of a sheet of paper containing information. When both sides of a 2 sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 by 3 11 inches (in.), not including foldouts. Except for the reproduced sections of the solicitation 4 document, the text size shall be no less than 12 point using Times New Roman font type. 5 Tracking, kerning, and leading values shall not be changed from the default values of the word 6 processing or page layout software. Use at least 1 in. margins on the top and bottom and ¾ in. 7 side margins. Pages shall be numbered sequentially by volume. These page size and format 8 restrictions shall also apply to responses to EN. 9
Legible tables, charts, graphs, and figures shall be used wherever practical to depict 10 organizations, systems and layout, implementation schedules, plans, etc. These displays shall be 11 uncomplicated and legible, and shall not exceed 11 by 17 in. in size. Foldout pages shall fold 12 entirely within the volume, and each face of the foldout containing information will be counted 13 as a single page. Foldout pages may only be used for large tables, charts, graphs, and figures, 14 not for pages of text. For tables, charts, graphs, and figures, the text may be in the Offeror’s 15 preferred format. 16
4.4 CLASSIFIED INFORMATION 17
The Government does not expect that classified information will be required. If you require 18 classified information in your proposal, please contact the PCO as soon as possible but no later 19 than 14 calendar days prior to the deadline for proposal receipt. 20
4.5 CROSS-REFERENCING 21
Each volume shall be written on a stand-alone basis so that its contents may be evaluated without 22 cross-referencing to other volumes of the proposal. Information required for proposal evaluation 23 that is not found in its designated volume will be assumed to have been omitted from the 24 proposal and may result in the proposal being deemed unawardable. 25
4.6 INDEXING 26
Each volume shall contain a table of contents with more detail than the master table of contents 27 included in the Executive Summary Volume, to delineate the subparagraphs within that volume. 28 Tab indexing shall be used to identify sections. 29
4.7 GLOSSARY OF ABBREVIATIONS AND ACRONYMS 30
Each volume shall contain a glossary of all abbreviations and acronyms used with a definition 31 for each. 32
4.8 BINDING AND LABELING 33
Each volume of the proposal shall be separately bound in a three-ring, loose-leaf binder, 34 permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be 35 bound in each volume, clearly marked as to volume number, title, copy number, solicitation 36 identification, and the Offeror’s name. The same identifying data shall be placed on the spine of 37 each binder. All unclassified document binders shall have a color other than red or other 38 applicable security designation colors. Be sure to apply all appropriate markings including those 39 prescribed IAW FAR 52.215-1(e) (Restriction on disclosure and use of data) and FAR 3.104-4 1 (Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source 2 Selection Information). 3
4.9 ELECTRONIC OFFERS 4
The content and page size of electronic copies must be identical to the hard copies. All CDs 5 shall be placed in plastic sleeves that open on the top in one separate binder, with the volume 6 number and title indicated on each disc. Hypertext links shall be used to facilitate navigation 7 within the document. Use separate files to permit rapid location of all portions, including 8 factors, exhibits, annexes, and attachments, if any. If files are compressed, the necessary 9 decompression program must be included. The electronic copies of the proposal shall be 10 submitted in a format readable by Microsoft (MS) Office Word 2007/2010, MS Office Excel 11 2007/2010, MS Office Project 2007/2010, and MS Office Power Point 2007/2010, as applicable; 12 exception applies to the Executive Summary and the Model Contract. In the event there are 13 discrepancies between the hard copies and the electronic copies of the proposal, the electronic 14 copies will be used for evaluation. The “original” hardcopy and electronic copy of the proposal 15 shall be identified. 16
4.10 DISTRIBUTION 17
Delivery of proposals shall be coordinated with the PCO at least 24 hours in advance of the due 18 date and time. Early deliveries of proposals shall also be coordinated with the PCO. Electronic 19 and hard copies of proposals are due TBD. Proposals shall be addressed to the PCO and mailed 20 or hand carried to: 21
SMC/LEK 22
Attn: Ms. Dzung Dom 23 483 N. Aviation Blvd. 24 El Segundo, CA 90245 25
Proposals received after the date and time specified will be treated IAW FAR 52.212-1(f). 26
5 VOLUME I – EXECUTIVE SUMMARY 27
The purpose of the Executive Summary Volume is to provide a complete overview of the 28 Offeror’s proposal. The Executive Summary Volume will not be evaluated, scored, or used to 29 clarify other discrepant information in other volumes. Any summary material presented in the 30 Executive Summary Volume will not be considered as meeting the requirements for any portions 31 of other volumes of the proposal. Do not include cost information. The Offeror shall provide 32 the following information in the Executive Summary: 33
5.1 NARRATIVE SUMMARY 34
The narrative summary of the entire proposal shall be concise, to include addressing any risk 35 areas and mitigations, and highlighting any key or unique features. The salient features shall tie 36 in with the evaluation factors in Attachment 6, Evaluation Criteria. 37
5.2 OFFEROR’S PROPOSED TEAM 1
The Offeror shall briefly identify the Offeror’s team to include major subcontractors. 2
5.3 MASTER TABLE OF CONTENTS 3
The Offeror shall include a master table of contents of the entire proposal. 4
5.4 CROSS REFERENCE MATRIX 5
The Offeror shall fill in the proposal column of the cross reference matrix below with the 6 volume, sections, and paragraph numbers from their proposal that correspond with the paragraph 7 numbers from Attachment 5 and Attachment 6 listed below. 8
Cross Reference Matrix
Volume
Attachment 5:
Instructions to
Offerors
Attachment 6: Evaluation
Criteria
Counted
Towards
Maximu m Page
Limitatio n (Y/N)
Proposal
Volume, Section, Paragraph s
Volume I:
Executive
Summary
5.1 N/A Y *
5.2 N/A Y *
5.3 N/A N *
5.4 N/A N *
Volume II:
Small Business
6.1 6.1 N *
Volume III:
Past
Performance
7.1.3 7.4 Y *
7.1.3 7.5 Y *
7.1.4 7.6 N *
Volume IV:
Price
8 8.1 N *
10.3 8.1 N *
11.3 8.1 N *
12.3 8.1 N *
Annex 1:
GPS III
10.1.1 10.1.1.1 Y *
10.1.1.1 10.1.1.1 Y *
10.1.1.2 10.1.1.2 Y *
10.1.1.2 10.1.1.3 Y *
10.1.1.2 10.1.1.4 Y *
10.1.1.3 10.1.1.5 Y *
10.1.1.3 10.1.1.6 Y *
10.1.2 10.1.2.1 Y *
10.1.2.1 10.1.2.2 Y *
10.1.2.2 10.1.2.3 Y *
10.1.2.3 10.1.2.4 Y *
10.1.2.4 10.1.2.5 Y *
10.1.2.5 10.1.2.6 Y *
10.1.3.1 10.1.3.1 Y *
10.1.3.2 10.1.3.2 Y *
10.1.3.3 10.1.3.3 Y *
10.1.3.4 10.1.3.4 Y *
10.2.1.1.1–10.2.1.1.5 10.2.1.2 N *
10.2.1.4 10.2.1.3 N *
10.2.1.2 10.2.1.4 N *
10.2.1.1.6–10.2.1.1.7 10.2.1.5 N *
10.2.1.3 10.2.1.6 N *
10.2.2.1 10.2.2.1 Y *
10.2.2.2 10.2.2.2 Y *
10.2.2.3 10.2.2.2 Y *
10.3 8.1 N *
Annex 2:
AFSPC-8
11.1.1 11.1.1.1 Y *
11.1.1.1 11.1.1.1 Y *
11.1.1.2 11.1.1.2 Y *
11.1.1.2 11.1.1.3 Y *
11.1.1.3 11.1.1.5 Y *
11.1.1.3 11.1.1.6 Y *
11.1.1.1 11.1.1.7 Y *
11.1.2 11.1.2.1 Y *
11.1.2.1 11.1.2.2 Y *
11.1.2.2 11.1.2.3 Y *
11.1.2.3 11.1.2.4 Y *
11.1.2.4 11.1.2.5 Y *
11.1.2.5 11.1.2.6 Y *
11.1.3.1 11.1.3.1 Y *
11.1.3.2 11.1.3.2 Y *
11.1.3.3 11.1.3.3 Y *
11.1.3.4 11.1.3.4 Y *
11.1.3.5 11.1.3.5 Y *
11.2.1 11.2.1.1 N *
11.2.1.1.1–11.2.1.1.5 11.2.1.2 N *
11.2.1.4 11.2.1.3 N *
11.2.1.2 11.2.1.4 N *
11.2.1.1.6–11.2.1.1.7 11.2.1.5 N *
11.2.1.3 11.2.1.6 N *
11.2.2.1 11.2.2.1 N *
11.2.2.2 11.2.2.2 N *
11.2.2.3 11.2.2.2 Y *
11.3 8.1 Y *
Annex 3:
AFSPC-12
12.1.1 12.1.1.1 Y *
12.1.1.1 12.1.1.1 Y *
12.1.1.2 12.1.1.2 Y *
12.1.1.2 12.1.1.3 Y *
12.1.1.3 12.1.1.5 Y *
12.1.1.3 12.1.1.6 Y *
12.1.1.1 12.1.1.7 Y *
12.1.2 12.1.2.1 Y *
12.1.2.1 12.1.2.2 Y *
12.1.2.2 12.1.2.3 Y *
12.1.2.3 12.1.2.4 Y *
12.1.2.4 12.1.2.5 Y *
12.1.2.5 12.1.2.6 Y *
12.1.3.1 12.1.3.1 Y *
12.1.3.2 12.1.3.2 Y *
12.1.3.3 12.1.3.3 Y *
* To be filled in by Offeror 1
6 VOLUME II – SMALL BUSINESS 2
6.1 FACTOR 1: SMALL BUSINESS PARTICIPATION 3
The Offeror shall provide a Small Business Participation Commitment Document (SBPCD) per 4 mission that will include information on how the Offeror will meet the small business 5
12.1.3.4 12.1.3.4 Y *
12.1.3.5 12.1.3.5 Y *
12.1.3.6 12.1.3.6 Y *
12.1.4.1 12.1.4.1 Y *
12.2.1 12.2.1.1 N *
12.2.1.1.1–12.2.1.1.5 12.2.1.2 N *
12.2.1.4 12.2.1.3 N *
12.2.1.2 12.2.1.4 N *
12.2.1.1.6–12.2.1.1.7 12.2.1.5 N *
12.2.1.3 12.2.1.6 N *
12.2.1.1.8 12.2.1.7 N *
12.2.2.1 12.2.2.1 N *
12.2.2.2 12.2.2.2 N *
12.2.2.3 12.2.2.2 Y *
12.3 8.1 Y *
Annex 4:
AFSPC-52
13.1.1 13.1.1.1 Y *
13.1.1.1 13.1.1.1 Y *
13.1.1.2 13.1.1.2 Y *
13.1.1.2 13.1.1.3 Y *
13.1.1.3 13.1.1.5 Y *
13.1.1.3 13.1.1.6 Y *
13.1.1.1 13.1.1.7 Y *
13.1.2 13.1.2.1 Y *
13.1.2.1 13.1.2.2 Y *
13.1.2.2 13.1.2.3 Y *
13.1.2.3 13.1.2.4 Y *
13.1.2.4 13.1.2.5 Y *
13.1.2.5 13.1.2.6 Y *
13.1.2.6 13.1.2.7 Y *
13.1.3.1 13.1.3.1 Y *
13.1.3.2 13.1.3.2 Y *
13.1.3.3 13.1.3.3 Y *
13.1.3.4 13.1.3.4 Y *
13.1.3.5 13.1.3.5 Y *
13.2.1 13.2.1.1 N *
13.2.1.1.1–13.2.1.1.5 13.2.1.2 N *
13.2.1.4 13.2.1.3 N *
13.2.1.2 13.2.1.4 N *
13.2.1.1.6–13.2.1.1.7 13.2.1.5 N *
13.2.1.3 13.2.1.6 N *
13.2.2.1 13.2.2.1 N *
13.2.2.2 13.2.2.2 N *
13.2.2.3 13.2.2.2 Y *
13.3 8.1 Y * participation Minimum Quantitative Requirement of 4% of each mission (including all options). 1 The Offeror shall complete Attachment 3B, SBPCD, for each mission. 2
The Offeror shall provide evidence of at least one (1) arrangement with, or the extent of the 3 commitment to use, small businesses (e.g., contractual documentation or letter of intent) with the 4 small business concerns identified within the subcontracting plan submitted IAW FAR clause 5
19.7 and 52.219-9. 6
The Offeror shall provide the Small Business Subcontracting Plan as required by FAR 19.7 and 7 52.219-9. The SBPCD is a separate document than the Small Business Subcontracting Plan. 8 Both documents will be evaluated per the evaluation criteria. The SBPCD and the Small 9 Business Subcontracting Plan will be incorporated into the contract as attachments. 10
7 VOLUME IV – PRICE 11
7.1 FACTOR 5: PRICE 12
The Offeror shall fill in prices for Tables 10-6 GPS III, 11-6 AFSPC-8, 12-6 AFSPC-12, and 13-13 6 AFSPC-52, as instructed in paragraphs 8.1 through 8.4 below. The Offeror shall not include 14 price information in any other portion of the proposal, except the Price Volume or Model 15 Contract. When completing Tables 10-6 GPS III, 11-6 AFSPC-8, 12-6 AFSPC-12, and 13-6 16 AFSPC-52, the Offeror shall fill in the same rate as those proposed in the model contract for all 17 applicable Contract Line Item Numbers (CLINs) ,which are included in the Total Proposed 18 Price; this also includes the Quick Reaction/Anomaly Resolution rate. 19
7.2 MISSION UNIQUE REQUIREMENTS AND OPTIONS 20
The Offeror shall provide a proposed total price for each mission unique requirement and option 21 listed in Tables 10-6 GPS III, 11-6 AFSPC-8, 12-6 AFSPC-12, and 13-6 AFSPC-52; reference 22 Tables 3.1-1, 3.1-2, 3.2-1, 3.2-2, 3.3-1, 3.3-2, 3.4-1, and 3.4-2 in the MRA for a list of mission 23 unique requirements and options. Note that unit pricing shall be provided in the Model Contract. 24 Additionally, the Offeror shall provide an itemized list of individual mission-unique 25 requirements with corresponding prices. 26
7.3 QUICK REACTION/ANOMALY RESOLUTION 27
For Quick Reaction and Anomaly Resolution, the Offeror shall complete Table 8-1 as shown 28 below and provide the resulting number (Total Proposed Dollars) for Tables 10-6, 11-6, 12-6, 29 and 13-6. For the model contract, the Offeror shall provide one composite rate which will be 30 effective towards all missions awarded. The maximum number of hours in SMC/LR-H005 will 31 reflect the sum of the hours associated with the mission(s) awarded. 32
8.5 CONTRACT DOCUMENTS, EXHIBITS AND ATTACHMENTS 1
8.5.1 ATTACHMENT 3A: SUBCONTRACTING PLAN 2
The offeror shall provide a subcontracting plan IAW FAR 52.219-9 and Air Force Federal 3 Acquisition Regulation Supplement 5319.704. The subcontracting plan will be incorporated into 4 the contract. 5
8.5.2 ATTACHMENT 3B: SMALL BUSINESS PARTICIPATION COMMITMENT DOCUMENT 6
The offeror shall provide SBPCD IAW section 6.3. The SBPCD will be incorporated into the 7 contract. 8
8.5.3 ATTACHMENT 8: GOVERNMENT PROPERTY 9
If the Offeror requires the use of GP, the Offeror shall complete and submit Attachment 8, 10 Government Property, IAW procedures and definitions detailed in DFARS 245.103-72 and 11 245.201-70. For more information, see the Department of Defense Procurement Toolbox at 12 http://www.dodprocurementtoolbox.org/site/detail/id/26. Failure to complete each applicable 13 data field in Attachment 8 may render the Offeror non-responsive and unawardable. For each 14 item of GP requested, the “Use As Is” column shall be filled in as “true.” 15
For each item of GP requested, the Offeror shall provide a written authorization of availability 16 from the cognizant Administrative Contracting Officer (ACO). GP proposed without an 17 authorization from the cognizant ACO may render the Offeror non-responsive and unawardable. 18 All supporting documentation associated with GP shall be submitted outside of the model 19 contract but within Volume IV. 20
8.5.4 ATTACHMENT 9: PAYMENT PLAN 21
The Offeror shall fill in the dollar amount associated with each payment milestone in Table 1 of 22 Attachment 9, Payment Plan. There are two payment plans, one for missions with multi-23 manifests and one for missions without multi-manifests. The applicable payment plan will be 24 filled out for each mission. These plans will become an attachment to the contract if the mission 25 is awarded. IAW FAR 32.204 alternative financing terms shall not be accepted. 26
8.5.5 POTENTIAL ORGANIZATIONAL CONFLICT OF INTEREST (OCI) 27
1. IAW FAR 9.5, Organizational and Consultant Conflicts of Interest, the Contracting 28 Officer has analyzed the planned acquisition and determined that no known actual or 29 potential OCI situations exist with respect to this solicitation. 30
2. The Offeror shall perform its own OCI analysis and submit the results of that analysis as 31 part of its proposal. Specifically, the Offeror shall analyze the planned acquisition for 32 actual or potential OCI situations associated with its or any of its teammate’s or 33 subcontractor’s performance under any contract it or any of its teammates or 34 subcontractors has been or may be awarded by any federal agency or other entity. The 35 Offeror shall describe in detail the methodology used to identify actual or potential OCI 36 issues. If the Offeror identifies any actual or potential OCIs with respect to the 37 performance of itself or its subcontractors or teammates, the Offeror shall provide an OCI 38 Mitigation Plan to be incorporated as Attachment 10 to any resulting contract. At a 39 minimum, the plan shall address all of the items identified in the most current version of 1 SMC’s OCI Mitigation Plan Checklist provided in the Bidder’s Library. Any proposed 2 avoidance or mitigation techniques shall be consistent with FAR 9.5 and the most recent 3 decisions of the Government Accountability Office and the United States Court of 4 Federal Claims. 5
3. If award is made to the Offeror, the resulting contract may include an organizational 6 conflict of interest limitation applicable to subsequent Government work, at either a 7 prime contract level, at any subcontract tier, or both. During evaluation of proposals, the 8 Government may, after interactions with the Offeror and consideration of ways to 9 mitigate or avoid identified actual or potential conflicts of interest, insert a clause or term 10 and condition in the resulting contract which disqualifies the Offeror from further 11 consideration for award of future contracts. 12
4. Resolution of OCI issues are treated in a manner similar to the Contracting Officer’s 13 contractor responsibility determination. Any communications necessary to resolve OCI 14 issues shall not be considered discussions. As such, the Contracting Officer may issue 15 Evaluation Notices to the Offeror prior to any decision to enter into discussions in order 16 to resolve questions or concerns with the Offeror’s OCI analysis or mitigation plan. 17
8.6 SOLICITATION PROVISIONS 18
All representations and certifications must be completed IAW FAR 52.212-3 deviation in the 19 model contract, Offeror Representations and Certifications- Commercial Items. 20
8.7 SIGNATURE 21
The Offeror’s signature on the SF 1449 constitutes an offer, which the Government may or may 22 not accept. Proposals without manual wet signatures may warrant a rejection of the proposal 23 submittal. Offerors are required to meet all solicitation requirements, including terms and 24 conditions, representations and certifications, and technical requirements. Therefore, any 25 tailoring to the solicitation is not allowed and may warrant a rejection of the proposal. 26
i. End of mission for upper stage, where end of mission is defined as the completion 1 of passivation with no further planned maneuvers, or through upper stage impact 2 after controlled reentry 3
Additionally, the Offeror shall provide orbital parameters (as defined in Table 10-1 for the 4 selected plane/date) of the SV at separation (including the effects of separation ∆V). 5
9.1.2.3 The Offeror shall provide data for any portion of the GPS III mission profile that has 6 been flight demonstrated (T-0 to disposal burn) by the proposed or relevant current family of 7 launch vehicle system. Examples of data could include a table of demonstrated burn durations 8
vs. planned burn durations, demonstrated coast durations vs. planned, and re-entries achieved vs. 9 planned. The Offeror shall also identify on which flight the mission profile portion was 10 demonstrated. The Offeror shall identify any portion of the mission profile that has not yet been 11 flight demonstrated by proposed or relevant current family of launch vehicle system. 12 Undemonstrated portions of a mission profile may include, but are not specifically limited to 13
a. Total proposed mission duration from launch to End of Mission as defined in Section 14 10.1.2.2.i above is greater than 10 minutes longer than a previously flown mission 15
b. Number of proposed upper stage engine relights is greater than previously flown 16
c. Coast duration between upper stage engine relights is greater than 5 minutes from a 17 previously flown mission 18
d. Booster or upper stage throttle settings are outside the range of previously flown throttle 19 settings 20
e. Proposed CCAM or upper stage disposal solution have not been previously flown (per 21
Evolved Expendable Launch Vehicle System Performance Requirements Document 22 [EELV SPRD], Rev. A) 23
f. Radiation environments not previously demonstrated 24
If any of the Offeror’s previous flights do not demonstrate portions of the GPS III mission 25 profile to include, but not limited to 10.1.2.3 a–f, then the Offeror shall provide a detailed 26 engineering and risk analysis of the affected launch vehicle subsystems and components, and 27 any risks or limiting factors associated with the design or configuration of the affected 28 subsystems. The Offeror shall provide a mitigation approach that addresses the identified risks 29 associated with the undemonstrated portion of the proposed mission profile. 30
9.1.2.4 The Offeror shall provide the ground trace and instantaneous impact point trace through 31 end of mission or through upper stage impact if conducting a controlled reentry, with 32 identification of nominal jettisoned body impacts. The nominal jettisoned body impacts shall 33 occur over water. Nominal jettisoned bodies include those planned under a controlled recovery 34 operation. If the Offeror plans to de-orbit the upper stage, they shall provide the impact ellipse. 35 The upper stage reentry location shall be in a broad ocean area. Casualty expectation value, if 36 applicable, and supporting analysis including mission reliability and failure scenarios shall be 37 provided. 38
9.1.2.5 The Offeror shall provide historical data, from liftoff through upper stage disposal, on 39 the final mission design trajectory predictions and flight data for mission profiles (including 40 sequence of events and Payload [PL] orbital parameters at separation), and for vehicle 41 acceleration comparison plots for the four most recent launches of a launch vehicle system 42 similar to the proposed launch vehicle system, or as many as have been launched if fewer than 43 four launches have taken place. Individual acceleration plots shall be provided for each burn of 1 each stage. If historical flight data does not corroborate predictions, the Offeror shall provide 2 detailed supporting rationale to explain differences. 3
9.1.3 SUB-FACTOR 3: LAUNCH OPERATIONS CONCEPT OF OPERATIONS (CONOPS) 4
9.1.3.1 The Offeror shall provide a Launch Operations CONOPS that includes a description of 5 the proposed launch operations flow from the time the Government provides the GPS III SV to 6 the Offeror as Government property for encapsulation through liftoff, to include any contingency 7 procedures. 8
9.1.3.2 The Offeror shall provide a Launch Operations CONOPS that includes the PL 9 processing and encapsulation plans, which are oriented to the processing facility the Launch 10 Service Provider proposes to use for an East Coast launch. 11
9.1.3.3 The Offeror shall provide a Launch Operations CONOPS that includes a description 12 and diagrams of propellant-compatible interface plumbing and aspirator in order to comply with 13 contingency propellant offload requirements, including access to the GPS III Fuel Service 14 Valves (+Y and Center) as identified in the MRA, GPS III MRD section XIV.H. 15
9.1.3.4 The Offeror shall provide a Launch Operations CONOPS that includes a description of 16 how the Offeror plans to execute the requirements of PWS paragraphs 1.2.5 , 3.1.1, and 17
3.5.1.15.3.2. 18
9.2 FACTOR 4: SCHEDULE 19
9.2.1 SUB-FACTOR 1: INTEGRATED MASTER SCHEDULE (IMS) 20
The Offeror shall provide one (1) Microsoft Project Integrated Master Schedule (IMS) and 21 Schedule Risk Assessment (SRA) integrating the first GPS III launch service proposed. The 22 proposed IMS and SRA shall correspond with the earliest GPS III ILC, for proposal purposes 23 assume an ILC of 15 Dec 2019, which will suffice for the remaining two (2) GPS III missions 24 within this RFP. The IMS and SRA shall be provided IAW the following: 25
9.2.1.1 The Offeror shall construct the GPS III IMS as follows: 26
The IMS shall include elements a-h listed below at a minimum. Additionally, the 27 IMS shall include all non-recurring design validation (NRDV) activities, including, but not 28 limited to: Management Systems, Flight Experience, System Design Validation, Design 29 Reliability, Manufacturing & Operations and Systems Engineering Process Validation, System 30 Safety, Test and Verification, Quality Systems/Processes, Flight Hardware and Software 31 Qualification, Launch Vehicle Analysis, Risk Management, Integrated Analysis, Launch 32 Complex, and Air Force EELV Requirements. The source selection team reserves the right to 33 pull in program office risk assessments, anomaly analysis, and other schedule risks as 34 appropriate. 35
a. Discrete tasks consistent with all proposed work; 36
b. Task durations based on an approximation of required resources; 37
c. Relationships/dependencies that identify how predecessor and successor tasks and 38 milestones are logically linked; 39
d. Milestones; 40
e. Total float/slack; 41
f. Task and milestone descriptions that clearly identify the scope and deliverable of the 1 work being accomplished, including Level of Effort (LOE) tasks; 2
g. Identified Critical Path 3
h. Identified Near Critical Path 4
The IMS shall be an integrated, logically driven network constructed at the lowest 5 level of tasks that form the network to identify a valid critical path. 6
The IMS shall identify the three (3) Critical Path(s), primary, secondary, and tertiary. 7 Each Critical Path shall have a different critical driver. 8
The IMS tasks shall have traceability to the Work Breakdown Structure (WBS) with a 9 text field which maps the task to the WBS section (Appendix A). For every WBS section in the 10 IMS, the level of detail shall be at least one level lower than the lowest WBS element to create 11 an integrated network of tasks to support the full scope of work of the proposed GPS III launch 12 services WBS. 13
The Offeror shall identify all schedule margin within the IMS. 14
The IMS task durations shall be supported by the resource-loading of workforce 15 (labor) resources, except for NRDV work closure plan tasks if applicable (see paragraph 16
10.2.1.2.4 below). The task durations shall be based on the Offeror’s estimation of the personnel 17 and skillsets required to accomplish the scope of each task. The resource sheet (within Microsoft 18 Project) shall identify the specific workforce resources at the lowest level required to 19 demonstrate credibility of the task duration with a description of the personnel and skillsets 20 required for each task. The Offeror shall not assign resources to milestone events. 21
The Offeror shall support IMS task durations excluding LOE tasks, Schedule 22 Visibility Tasks and milestones with at least one or more of the following: actual historical 23 performance data or rationale and lessons learned. To support the credibility of task durations, 24 the Offeror may provide statement(s) of assumptions. The Offeror shall provide a summary of 25 historical performance data, and rationale and lessons learned used to determine all task 26 durations. The Offeror shall provide actual data and basis of estimation (historical performance 27 data, rationale and lessons learned, and statements of assumptions) for all Critical Path and near 28 Critical Path within the schedule narrative. 29
9.2.1.2 The IMS shall reflect the following activities sufficient to support the GPS III launch 30 services as follows: 31
The IMS shall reflect either a start date no earlier than 2 years prior to Initial Launch 32 Capability (ILC) or the date needed to begin procurement of the longest lead hardware, and 33 support the ILC for the first of the three GPS III missions: 15 January 2020. 34
The IMS shall encompass all tasks required to accomplish the GPS III launch services 35 proposed from contract award to contract completion, to include activities to accomplish the 36 tasks in the PWS, Program Milestone Reviews (PWS, Appendix H), and CDRLs, IAW the 37
WBS. 38
The IMS shall identify all critical events to include but not limited to the following: 39 LV production with identification of the longest lead hardware; testing at the component, 40 subsystem, system, and integrated level; major reviews; encapsulation; transport; integrated 41 testing; LV/PL mate; and, ILC. 42
If applicable, the IMS shall include tasks sufficient to accomplish the non-recurring 1 design validation work as described in paragraph 10.2.2.1 in support of the GPS III launch 2 services, to include appropriate durations. To support task durations, the Offeror shall provide at 3 least one of the following within the schedule narrative: actual historical performance data, 4 rationale, or lessons learned. Non-recurring design validation work closure plan tasks do not 5 need to be resource loaded. 6
The Offeror’s proposal shall include the ILC of the Offeror’s forecasted launches 7 during the timeframe of contract start to the GPS III ILC as part of the schedule narrative. The 8 Offeror’s proposal shall also provide a summary of critical milestone events (booster, upper 9 stage, and fairing ship dates) for the Offeror’s other launches during the timeframe of contract 10 start to ILC for the GPS III launch services proposed as part of the schedule narrative to include 11 the exercising of the two GPS III options to launch in fiscal year 2021. For evaluation purposes, 12 assume ILC dates of October 2020 and April 2021 for the two GPS III options. 13
9.2.1.3 Schedule Risk Assessment – The Offeror shall perform a SRA of the GPS III launch 14 services IMS to predict the probability of project completion to support the GPS III ILC IAW the 15 sub-criteria below: 16
The Offeror shall perform a 10,000-iteration Monte Carlo simulation-based SRA, and 17 provide the results of the SRA in the Schedule Narrative. 18
The SRA results shall provide a cumulative probability distribution (S-curve) for ILC 19 including specific completion dates for every 10th percentile from 10% to 90%. 20
The Offeror shall develop individual three-point estimates (best case, most likely, and 21 worst case) for all tasks on the Critical Path, near Critical Path, non-recurring design validation 22 work IAW paragraph 10.2.2.1, and low-medium, medium, or high risk tasks captured in the 23 Offeror’s Risk Mitigation Plan IAW paragraph 10.2.2.2 below. The Offeror shall provide fields 24 within the Microsoft Project File listing the three-point estimates. 25
The three-point estimates shall be supported by the Offeror’s actual historical 26 performance data if the task has been previously performed. If the task has not been previously 27 performed, the Offeror shall provide rationale to justify three-point estimates. The Offeror shall 28 provide a summary within the schedule narrative to explain the use of historical performance 29 data, rationale, lessons learned, and assumptions used to determine all three-point estimates. 30
9.2.1.4 Defense Contract Management Agency (DCMA) 14 Point Schedule Assessment – The 31 Offeror shall construct the IMS IAW with the DCMA 14 Point Schedule Assessment guidelines 32 as described in paragraphs 10.2.1.4.1–10.2.1.4.10 excluding Invalid Dates, Resources, Missed 33 Tasks, and Baseline Execution Index. The Offeror shall provide justification for each 34 component of the IMS that falls beyond the guideline thresholds. This analysis shall exclude 35 Completed Tasks, LOE tasks, Summary Tasks, and Milestones. 36
Logic – The number of activities that are missing a predecessor, a successor or both 37 shall not exceed the threshold of 5% of the activities within the Offeror’s IMS. Provide 38 justification for the use of predecessor/successor relationships beyond the 5% threshold of all 39 activities within the Offeror’s IMS. 40
Leads – The number of activities with leads (negative lag) shall not exceed the 41 threshold of 0% of the activities within the IMS. Provide a justification for each lead 42 relationship used in the IMS. 43
Lags – The total number of activities with lags shall not exceed the threshold of 5% 1 of the activities within the Offeror’s IMS. Provide justification for the use of lag relationships 2 beyond the 5% threshold for all activities within the Offeror’s IMS. 3
Relationship Types – The total number of activities with Finish to Start (FS) logic 4 links shall be at least 90%. Tasks with all other logic links [Start-to-Start (SS); and Finish-to-5 Finish (FF)] should be less than the threshold of 10% of total tasks within the IMS. Provide 6 justification for the use of logic links other than (FS) relationships beyond the 10% threshold for 7 all activities within the Offeror’s IMS. 8
Hard Constraints – The number of activities with hard constraints [Must-Finish-On, 9 Must-Start-On, Start-No-Later-Than, & Finish-No-Later-Than] shall not exceed the threshold of 10 5% of the activities within the Offeror’s IMS. Provide a justification for the use of hard 11 constraints beyond the 5% threshold for all activities within the Offeror’s IMS. If soft 12 constraints are needed other than As-Soon-As-Possible [Start-No-Earlier-Than and Finish-No-13 Earlier-Than] the Offeror shall provide a field within the Microsoft Project File that contains a 14 summary justification of these constraints used in the IMS. 15
High float – The number of activities with a total float greater than two (2) months 16 (44 working days) shall not exceed the threshold of 5% of the activities within the Offeror’s 17 IMS. Provide justification for the use of activities with a total float greater than 2 months 18 beyond the 5% threshold of the activities within the Offeror’s IMS. 19
Negative Float – The number of activities with a total float of less than zero (0) days 20 shall not exceed the threshold of 0% of the activities within the Offeror’s IMS. Provide 21 justification for the use of activities with a total float of less than 0 days within the Offeror’s 22
IMS. 23
Long Duration – The number of activities with a duration greater than two (2) months 24 (44 working days) shall not exceed the threshold of 5% of the activities within the Offeror’s 25 IMS. Provide justification for the use of activities with a duration greater than 2 months that 26 exceeds the 5% threshold of the activities within the Offeror’s IMS. 27
Critical Path Test – When an activity’s duration on the critical path is intentionally 28 slipped by “X” amount of days (assuming zero float), where “X” is equal to a gross increase in 29 duration (e.g., 600 days), the critical path within the Offeror’s IMS shall demonstrate a 30 corresponding extension of “X” amount of days to the project completion date and to the ILC. 31 Provide justification if either the project completion date or the ILC are not delayed in direct 32 proportion to the amount of intentional slip that is introduced into the critical path. 33
Critical Path Length Index – The Critical Path Length Index (CPLI) is equal to the 34 Critical Path Length (CPL) in days + the Total Float (TF) in days divided by the CPL in days. 35 The ratio of the critical path length plus the total float to the critical path length within the 36 Offeror’s IMS shall = 1, with > 1 being favorable, and < 1 being unfavorable. Provide 37 justification if the CPLI of the Offeror’s IMS is < 1. 38
9.2.2 SUB-FACTOR 2: RISK MITIGATION PLANS 39
9.2.2.1 As stated in section 10.2.1.2.4, the Offeror shall provide a schedule with task durations 40 to complete all remaining open NRDV work and obtain Government approval by L-12 months. 41 Reference the PWS, Appendix A: Glossary of Terms, for the NRDV definition. For the purposes 42 of this proposal, the Contractor shall assume that Government approval of the open NRDV work 43 will be obtained 4 months following completion of final contractor NRDV efforts. The Offeror 1 shall also identify NRDV tasks on the critical path for this mission. Should the Government 2 enter into discussions with the Offeror(s), the Government reserves the right to request an 3 updated detailed description of the Offeror’s progress toward completing all remaining open 4 NRDV work (to potentially include requesting an updated IMS). 5
9.2.2.2 The Offeror shall provide a risk mitigation plan for the proposed launch vehicle 6 configuration to address any jointly identified risks (Low-Medium, Medium, and High) to 7 include risks identified by the Joint Work Plan, EELV Engineering Review Boards, EELV Flight 8 Readiness Reviews, other technical reviews, and any other self-identified risks to the Offeror’s 9 proposed launch vehicle configuration. Risk ratings are defined by the Technical Issue 10 Resolution Process (TIRP). The Offeror shall identify any Low-Medium risks previously 11 accepted by the Government via EELV Spaceflight Worthiness Certification in lieu of a risk 12 mitigation plan. For jointly identified risks that are in the process of having its risk rating 13 reassessed by the Government, the Offeror shall assume the risk applies to the proposed launch 14 system and include the risk mitigation plan if the original risk rating is “Low-Medium” or higher. 15 The risk mitigation plan shall support low risk rating as defined by the TIRP prior to ILC. Should 16 the Government enter into discussions with the Offeror(s), the Government reserves the right to 17 request an updated detailed description of the Offeror’s progress towards the closure of identified 18 risks. Additionally, should the Government enter into discussions, updated risk mitigation plans 19 and IMS may be required during discussions. 20
9.2.2.3 The Offeror shall provide the status of the following: (1) ongoing mishap or anomaly 21 investigations, (2) any root cause data, and (3) determination and associated corrective actions to 22 support ILC. Should a mishap or flight anomaly be opened or under investigation after the 23 receipt of proposals, the Government reserves the right to require a risk mitigation corrective 24 action plan specifically for that mishap or flight anomaly. 25
9.3 FACTOR 4: PRICE 27
The Offeror shall provide their proposed price for the launch service allocated to categories 28 shown in Table 10-6. This allocation shall conform to the following WBS element to CLIN 29 mapping, and PWS paragraph to CLIN mapping: 30
a. CLIN X000, Launch Vehicle Production, consists of WBS elements 1.6, 1.8.1.1, 1.8.1.2, 31 1.8.1.3, 1.8.2.1, 1.8.2.2, 1.8.3, 1.8.4, 1.8.5, 1.8.6, 1.8.7, 1.9, and 1.10, and all subsections 32 therein; and consists of PWS paragraph 3.3, and all subsections therein. 33
b. CLIN X001, Mission Integration/Launch Ops/Spaceflight Worthiness Certification, 34 consists of WBS elements 1.1.1, 1.2, 1.3, 1.5.1, 1.5.2, 1.5.3, and 1.7, and all subsections 35 therein; and consists of PWS paragraphs 3.1, 3.2, 3.4, 3.5, and 3.6, and all subsections 36 therein. 37
c. CLIN X002, Mission Unique Activities, consists of WBS elements 1.1.2, 1.4, 1.8.2.3, 38 and all subsections therein; and consists of PWS paragraph 3.8, and all subsections 39 therein. 40
d. CLIN X003, Options, consists of WBS elements 1.1.2, 1.4, 1.8.2.3, and all subsections 41 therein; PWS paragraph 3.8, and all subsections therein; and MRA, Table 3.1-2. 42
h. Upper stage disposal initiation 1
i. End of mission for upper stage, where end of mission is defined as the completion 2 of passivation with no further planned maneuvers, or through upper stage impact 3 after controlled reentry 4
Additionally, the Offeror shall provide orbital parameters (as defined in Table 11-1) of the 5 PL at separation (including the effects of separation ∆V). 6
10.1.2.3 The Offeror shall provide data for any portion of the AFSPC-8 mission profile that has 7 been flight demonstrated (T-0 to disposal burn) by the proposed or relevant current family of 8 launch vehicle system. Examples of data could include a table of demonstrated burn durations 9
vs. planned burn durations, demonstrated coast durations vs. planned, and re-entries achieved vs. 10 planned. The Offeror shall also identify on which flight the mission profile portion was 11 demonstrated. The Offeror shall identify any portion of the mission profile that has not yet been 12 flight demonstrated by proposed or relevant current family of launch vehicle system. 13 Undemonstrated portions of a mission profile may include, but are not specifically limited to: 14
a. Total proposed…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .