07_Attachment_5_Instructions_to_Offerors_and_Appendices.pdf
PDF 7 MB Posted
- Solicitation number
- FA8811-17-R-0004
About this file
07 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, and AFSPC-12 Launch Services
FA8811-17-R-0004
Attachment 5
Instructions to Offerors
29 June 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–3. 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, MRA, 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 240 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 five missions consisting of three Global Positioning System (GPS) III 31 missions, Air Force Space Command (AFSPC)-8, and AFSPC-12. This RFP is organized such 32 that the Past Performance factor is overarching criteria that will be evaluated once for the GPS 33 III missions and once for the AFSPC missions. Annex 1 contains mission-specific criteria for 34 the GPS III missions, Annex 2 contains mission-specific criteria for AFSPC-8, and Annex 3 35 contains mission-specific criteria for AFSPC-12. Each mission annex is discussed within the 36 Instructions to Offerors (Attachment 5) and Evaluation Criteria (Attachment 6). 37
All Offerors shall respond via a proposal for all missions in this Request for Proposal (RFP). In 38 the event an Offeror cannot technically perform a specific mission, then the Offeror shall submit 39 a waiver in lieu of a proposal for that specific mission. 40
The Government intends to make multiple award decisions: individual award decisions for (1) 41 the three GPS III missions (winner-take-all), (2) AFSPC-8, and (3) AFSPC-12. The Government 42 reserves the right to make all award decisions at once or rolling award decisions. Should an 1 Offeror be awarded multiple missions, the missions shall be awarded and executed on one 2 contract. Three separate award decisions shall be made to the Offeror(s) that receives an 3 acceptable rating in the factors and sub-factors, with the lowest reasonable and balanced Total 4 Evaluated Price. The Total Proposed Price (TPP) will be the price put on contract. 5
3 GENERAL INFORMATION 6
3.1 POINT OF CONTACT 7
The Procuring Contracting Officer (PCO), Ms. Dzung Dom, is the sole point of contact for this 8 acquisition. Address any questions or concerns you may have to the PCO at 9 dzung.dom@us.af.mil or 310-653-3696. Written questions or concerns regarding this RFP may 10 be sent to the PCO at the address for the Launch Enterprise contracting office (SMC/LEK) 11 located on the front page of the model contract/solicitation. 12
3.2 DEBRIEFINGS 13
The PCO will promptly notify Offerors of any decision to exclude them from the competitive 14 range, whereupon they may request and receive a debriefing IAW FAR 15.505. In addition, the 15 PCO will notify unsuccessful Offerors of the source selection decision IAW FAR 15.506. Upon 16 such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring 17 a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as 18 applicable. 19
3.3 DISCREPANCIES 20
If an Offeror believes that the requirements in this RFP contain an error or omission, or are 21 otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting 22 rationale as well as the remedies the Offeror is asking the PCO to consider as related to the 23 omission or error. 24
3.4 ELECTRONIC REFERENCE DOCUMENTS 25
Referenced documents for this solicitation are available at http://www.fedbizopps.gov. Potential 26 Offerors are encouraged to subscribe for real-time e-mail notifications when information has 27 been posted to the website for this solicitation. 28
3.5 EXCHANGES 29
Exchanges of source selection information between the Government and Offerors will be 30 controlled by the PCO. Source selection information will be transmitted in person or via 31 certified mail, delivery service, or facsimile. 32
3.6 DISCUSSIONS 33
The Government reserves the right to award without discussions by mission. However, the 34 Government may conduct discussions with Offerors after establishing a competitive range by 35 mission based on the ratings of each proposal against all evaluation criteria. Discussions may be 36 held on a mission-by-mission basis. The Government reserves the right to record audio 37 telecommunications with the Offerors during the source selection. 38
3.7 USE OF NON-GOVERNMENT ADVISORS 1
Offerors are advised that data submitted to the Government in response to this solicitation will be 2 released to individuals who work for the following companies as non-Government advisors for 3 review and analysis: 4
Company Name Address 5 The Aerospace Corporation PO BOX 92957, 6 Los Angeles, CA 90009-2957 7
Tecolote Research, Inc 2120 E. Grand Avenue, Suite 200, 8 El Segundo, CA 90245 9
Science Applications International Corporation (SAIC) 3030 Old Ranch Pkwy #200, 10 Seal Beach, CA 90740 11 Offerors are advised that data submitted to the Government in response to this solicitation may 13 be released to individuals who work for the following companies as non-Government advisors 14 for administrative support. 15
Company Name Address 16 Business and Technology Solutions 3572 Dayton-Xenia Rd, Suite 210, Beavercreek, 17
OH 45432 18
ARRAY Information Technology 7474 Greenway Center Dr, Suite 600, Greenbelt, 19
MD 20770 20
Individuals from the above support contractors have signed individual non-disclosure agreements 21 with the Government, which strictly prohibits any release or disclosure of information outside of 22 the source selection team. 23
3.8 ALTERNATIVE PROPOSALS 24
Alternative proposals will not be considered. Alternative proposals are those that do not meet 25 the terms and conditions of the RFP, including attachments. 26
4 PROPOSAL FORMAT/LIMITS 27
4.1 ORGANIZATION/NUMBER OF COPIES/PAGE LIMITS 28
The Offeror shall prepare the proposal as set forth in Table 4-1: Proposal Organization. The 29 titles and contents of the volumes shall be as defined in this table, all of which shall be within the 30 required page limits. The Volumes identified in the table shall be separately bound in three-ring, 31 loose-leaf binders, plus each Volume’s electronic copy shall be saved on a separate compact disc 32 (CD) or digital video disc (DVD). The Executive Summary and Price Volumes may be 33 combined into one (1) binder. Volume IIIa, IIIb, and IIIc shall be separate binders. For all 34 Volume III binders, page separation tabs for each sub-factor shall be provided. The Offeror shall 35 provide two hard copies of the proposal and two electronic copies of the proposal on CDs or 36 DVDs. The contents of each proposal volume are described in the paragraph as noted in the 37 table below: 38
1 TABLE 4-1: PROPOSAL ORGANIZATION
Volume Title Sub-factors Hard Electronic
Page Limit Copies Copies
I Executive
2 2 10 Sununaiv
II
Factor 1: Past
2 2
Performance pages/contract
Sub-factor 1: Orbital Acctu·acy
Factor 2 :
Sub-factor 2: Mass-to-Orbit 175
Performance illaGPSID Sub-factor 3: Launch Operations (CONOPS) 2 2
Factor 3: Schedule Sub-factor 1: Integrated Master Schedule
Unlimited Sub-factor 2: Risk Mitigation Plans
Sub-factor 1: Orbital Acctu·acy
Factor 2 :
Sub-factor 2: Mass-to-Orbit
Performance Sub-factor 3: Launch Operations (CONOPS)
IIIb AFSPC-8 Sub-factor 4: Acoustic Envirnnment and 2 2
Shock Environment
Factor 3: Schedule Sub-factor 1: Integrated Master Schedule
Unlimited Sub-factor 2: Risk Mitigation Plans
Sub-factor 1: Orbital Acctu·acy
Factor 2 : Sub-factor 2: Mass-to-Orbit
Performance
Sub-factor 3: Launch Operations (CONOPS) Ille AFSPC-12 2 2
Sub-factor 4: Acoustic Environment
Factor 3: Schedule Sub-factor 1: Integrated Master Schedule
Unlimited Sub-factor 2: Risk Mitigation Plans
IVaGPSm Factor 4: Price 2 2 Unlimited
IVbAFSPC-8 Factor 4: Price 2 2 Unlimited
IVcAFSPC-12 Factor 4: Price 2 2 Unlimited v Model Contra.ct 2 2 Unlimited
Note: AFSPC = Air Force Space Colllllland, CON OPS = Concept of Operations, GPS = Global Positioning System
2 4.2 PAGE LIMITATIONS
3 Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or 4 considered in the evaluation of the proposal, and excess paper copies will be shredded. If the 5 Government issues Evaluation Notices (EN) for discussions, page limitations may be placed on 6 responses to EN. The specified page limits for EN responses will be identified in the letters sent 7 along with the EN to the Offerors. Unless othe1wise specified, each page shall be counted except 8 the following: cover pages, table of contents, tabs, and glossaries. Additionally, for the Schedule 9 Factor, the Offeror may include an unlimited naiTative to aii iculate the proposed schedule.
Instrnctions to Off erors
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. However, cross-referencing within a 23 proposal volume is permitted where its use would conserve space without impairing clarity. 24 Information required for proposal evaluation that is not found in its designated volume will be 25 assumed to have been omitted from the proposal and may result in the proposal being deemed 26 unawardable. 27
4.6 INDEXING 28
Each volume shall contain a table of contents with more detail than the master table of contents 29 included in the Executive Summary Volume, to delineate the subparagraphs within that volume. 30 Tab indexing shall be used to identify sections. 31
4.7 GLOSSARY OF ABBREVIATIONS AND ACRONYMS 32
Each volume shall contain a glossary of all abbreviations and acronyms used with a definition 33 for each. 34
4.8 BINDING AND LABELING 35
Each volume of the proposal shall be separately bound in a three-ring, loose-leaf binder, 36 permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be 37 bound in each volume, clearly marked as to volume number, title, copy number, solicitation 38 identification, and the Offeror’s name. The same identifying data shall be placed on the spine of 39 each binder. All unclassified document binders shall have a color other than red or other 1 applicable security designation colors. Be sure to apply all appropriate markings including those 2 prescribed IAW FAR 52.215-1(e) (Restriction on disclosure and use of data) and FAR 3.104-4 3 (Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source 4 Selection Information). 5
4.9 ELECTRONIC OFFERS 6
The content and page size of electronic copies must be identical to the hard copies. All CDs 7 shall be placed in plastic sleeves that open on the top in one separate binder, with the volume 8 number and title indicated on each disc. Hypertext links shall be used to facilitate navigation 9 within the document. Use separate files to permit rapid location of all portions, including 10 factors, exhibits, annexes, and attachments, if any. If files are compressed, the necessary 11 decompression program must be included. The electronic copies of the proposal shall be 12 submitted in a format readable by Microsoft (MS) Office Word 2007/2010, MS Office Excel 13 2007/2010, MS Office Project 2007/2010, and MS Office Power Point 2007/2010, as applicable; 14 exception applies to the Executive Summary and the Model Contract. In the event there are 15 discrepancies between the hard copies and the electronic copies of the proposal, the electronic 16 copies will be used for evaluation. The “original” hardcopy and electronic copy of the proposal 17 shall be identified. 18
4.10 DELIVERY INSTRUCTIONS 19
Delivery of proposals shall be coordinated with the PCO at least 24 hours in advance of the due date and time. Early deliveries of proposals shall also be coordinated with the PCO. Electronic and hard copies of proposals are due 14 August 2017 at 1600 Pacific Time. Proposals shall be addressed to the PCO and mailed or hand carried to: 23
SMC/LEK 24
Attn: Ms. Dzung Dom 25 483 N. Aviation Blvd. 26 El Segundo, CA 90245 27
Proposals received after the date and time specified will be treated IAW FAR 52.212-1(f). 28
5 VOLUME I – EXECUTIVE SUMMARY 29
The purpose of the Executive Summary Volume is to provide a complete overview of the 30 Offeror’s proposal. The Executive Summary Volume will not be evaluated, scored, or used to 31 clarify other discrepant information in other volumes. Any summary material presented in the 32 Executive Summary Volume will not be considered as meeting the requirements for any portions 33 of other volumes of the proposal. Do not include cost information. The Offeror shall provide 34 the following information in the Executive Summary: 35
5.1 NARRATIVE SUMMARY 36
The narrative summary of the entire proposal shall be concise, to include addressing any risk 37 areas and mitigations, and highlighting any key or unique features. The salient features shall tie 38 in with the evaluation factors in Attachment 6, Evaluation Criteria. 39
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
Maximum
Page
Limitation
(Y/N)
Proposal
Volume, Section, Paragraphs
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: Past
Performance
7.1.5 7.4 Y *
7.1.5 7.5 Y *
7.1.6 7.6 N *
Volume IVa-
Vc: Price
8 8.1 N *
10.3 8.1 N *
11.3 8.1 N *
12.3 8.1 N *
Annex 1:
Volume IIIa -
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.1 10.1.2.3 Y *
10.1.2.2 10.1.2.4 Y *
10.1.2.2 10.1.2.5 Y *
10.1.2.3 10.1.2.5 Y *
10.1.2.4 10.1.2.6 Y *
10.1.2.5 10.1.2.7 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.2 N *
10.2.1.1.2 10.2.1.2 N *
10.2.1.1.3 10.2.1.2 N *
10.2.1.1.4 10.2.1.2 N *
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.5 N *
10.2.1.1.7 10.2.1.5 N *
10.2.1.3 10.2.1.6 N *
10.2.2 10.2.2 N *
10.2.2.1 10.2.2.1 N *
10.2.2.2 10.2.2.2 N *
10.2.2.3 10.2.2.3 N *
10.2.2.4 10.2.2.4 N *
Annex 2:
Volume IIIb -
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.1 11.1.2.3 Y *
11.1.2.2 11.1.2.4 Y *
11.1.2.3 11.1.2.4 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.1.4.1 11.1.4.1 Y *
11.1.4.2 11.1.4.2 Y *
11.2.1 11.2.1.1 N *
11.2.1.1.1 11.2.1.2 N *
11.2.1.1.2 11.2.1.2 N *
11.2.1.1.3 11.2.1.2 N *
11.2.1.1.4 11.2.1.2 N *
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.5 N *
11.2.1.1.7 11.2.1.5 N *
11.2.1.3 11.2.1.6 N *
1.2.2 11.2.2 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.3 N *
11.2.2.4 11.2.2.4 N *
Annex 3:
Volume IIIc -
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.1 12.1.2.3 Y *
12.1.2.2 12.1.2.4 Y *
12.1.2.3 12.1.2.4 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 *
6 RESERVED 1
6.1 RESERVED 2
7 VOLUME II – PAST PERFORMANCE 4
7.1 FACTOR 1: PAST PERFORMANCE 5
7.1.1 PAST PERFORMANCE INFORMATION (PPI) FORMS 6
7.1.1.1 Each Offeror shall submit a past performance volume with its proposal, containing past 7 performance information IAW the format contained in Appendix B. 8
7.1.1.2 In order for an Offeror to complete the documentation required for submittal of this 9 Past Performance volume, each Offeror must access the FedBizOps automated Past Performance 10 Information (PPI) tool. For the specific detail, see Section L Attachment 07b “Past Performance 11 Information Instructions”. 12
7.1.1.3 The Government will use data provided by each Offeror in this volume as well as data 13 obtained from other sources in its evaluation of past performance. 14
7.1.2 VOLUME ORGANIZATION 15
The Past Performance volume shall be organized according to the following general outline: 16
(1)Table of Contents 17
(2) Relevant Contracts 18
(2.1) Business Relationships (use format from the Past Performance Information 19 (PPI) tool submitted as hardcopy printout and on CD) 20
12.1.3.3 12.1.3.3 Y *
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.2 N *
12.2.1.1.2 12.2.1.2 N *
12.2.1.1.3 12.2.1.2 N *
12.2.1.1.4 12.2.1.2 N *
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.5 N *
12.2.1.1.7 12.2.1.5 N *
12.2.1.3 12.2.1.6 N *
12.2.2 12.2.2 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 N *
12.2.2.4 12.2.2.4 N *
* To be filled in by Offeror
Notes: AFSPC = Air Force Space Command, GPS = Global Positioning System
(2.2) Past Performance Information (use format from the PPI tool submitted as 1 hardcopy printout and on CD) 2
(3) Attachments (Section L Attachment 07c, Section L Attachment 07d, Section L 3 Attachment 07e) 4
7.1.3 FORMAT 6
The information for the Past Performance Volume will be submitted on two different CDs. The 7 past performance information from the PPI tool shall be on a separate CD than other items in the 8 Past Performance Volume II. 9
Formatting for the volume shall be in accordance with the page size and formatting shown for 10 the over proposal above in paragraph x.x.x.x; except the formatting for the hardcopy print out 11 pages from the PPI tool will be as automatically produced by the tool in the following format: 12
Font: Times New Roman 13
Font Size: 12pt 14
Page Margins: 1” top, bottom, left, and right 15
Page Size: 8.5”x11” 16
Line Spacing: 1 17
Header/Footer: “Source Selection Information – See FAR 2.101 and 3.104. For Official 18 Use Only” 19
7.1.4 CONSENT/AUTHORIZATION LETTERS 21
Along with the PPI required in this section, the Offeror shall submit a consent letter, Appendix 22 C, executed by each subcontractor, authorizing release of adverse past performance information 23 to the Offeror so the Offeror can respond to such information. For each identified effort for a 24 customer, the Offeror shall also submit a client authorization letter, Appendix D, authorizing 25 release to the Government of requested information on the Offeror's performance. 26
7.1.5 RECENT AND RELEVANT CONTRACTS 27
Offeror’s shall submit information IAW Appendix B: Past Performance Information Instructions, 28 on four recent and relevant contracts that demonstrate its ability to perform the proposed effort; 29 reference Attachment 6, Sections 7.4 (Recency Assessment) and 7.5 (Relevancy Assessment), 30 for recency and relevancy definitions. Offeror’s shall submit at least one effort relevant to the 31 GPS missions and at least one effort relevant to the AFSPC missions. If no recent or relevant 32 past performance information exists, notify the PCO in writing by the date specified in Section 33
4.10 (Delivery Instructions). 34
7.1.5.1 SPECIFIC CONTENT 35
Offerors are required to explain what aspects of the contracts are deemed relevant to 36 the proposed effort and to what aspects of the proposed effort they relate. This may include a 37 discussion of efforts accomplished by the offeror to resolve problems encountered on prior 38 contracts as well as past efforts to identify and manage program risk. Merely having problems 39 does not automatically equate to an unacceptable rating, because the problems encountered may 40 have been on a more complex program, or an Offeror may have subsequently demonstrated the 41 ability to overcome the problems encountered. If the Offeror has encountered problems on 1 previous efforts, then the Offeror is required to clearly demonstrate management actions 2 employed in overcoming those problems and the effects of those actions in terms of 3 improvements achieved or problems rectified. This may allow the Offeror to be considered more 4 favorably than without evidence of problem resolution. 5
Offerors shall provide the narrative within Appendix B to support how the past 6 performance information submitted for evaluation demonstrates the offeror's ability to meet the 7 PWS requirements. 8
7.1.6 PAST PERFORMANCE QUESTIONNAIRES (PPQS) 9
The Offeror shall forward the PPQ template, Appendix E, to each contract POC identified in the 10 PPIs. 11
7.1.6.1 The Offeror should monitor the completion of the questionnaires and make every effort 12 to ensure that at least two POCs per contract submit completed questionnaires by the submission 13 deadline. 14
7.1.6.2 Questionnaire respondents shall email completed PPQs directly to the following POC 15 listed below by the proposal submittal date. Submission of contact information for previous 16 relevant contracts IAW Attachment 5 is due via email no later than 14 August 2017. The 17 information to be submitted shall include customer name with two points of contact (name and 18 title, email, phone number, and address). Information contained in a completed PPQ shall be 19 considered source selection information and shall not be released to the offeror. 20
Los Angeles Air Force Base 21 Attn: SMC/LE, Ms. Dzung Dom 22 483 N. Aviation Blvd 23 El Segundo, CA 90245 24 E-Mail to: dzung.dom@us.af.mil 25
7.1.6.3 Even though the assessment of Past Performance is separate and distinct from 26 Determination of Responsibility required by FAR 9, past performance information evaluated 27 during source selection may be used to support the Determination of Responsibility for the 28 successful awardee. 29
7.1.7 SMALL BUSINESS SUBCONTRACTING HISTORY 30
7.1.7.1 Pursuant to Defense Federal Acquisition Regulation System (DFARS) 215.305, all 31 Offerors (large and small businesses) shall provide a narrative describing its use of small 32 business concerns over the past three (3) years on the recent, relevant efforts submitted for 33 Government consideration under this factor. Proposals shall describe the actual use of small 34 businesses as subcontractors, joint venture/teaming partners and demonstrate the extent of 35 compliance with FAR 52.219-8, Utilization of Small Business Concerns, the Offeror's small 36 business subcontracting plans (large businesses only), and any related contract incentives. Large 37 business Offerors shall specifically describe the small business goals for all categories of small 38 business and the extent to which the goals were achieved in contracts that required 39 subcontracting plans for the past three years. To supplement the narrative summary, large 40 business Offerors shall provide the most recent Individual Subcontracting Reports or Summary 41 Subcontract Reports for each relevant contract IAW paragraph 7.1.3 that required submission of 42 such reports. These subcontracting reports will not count against the page limitations for the Past 1 Performance volume. 2
7.1.7.2 If necessary to meet the report requirement, Offerors may include subcontracting reports 3 associated with contracts other than those for which past performance information sheets were 4 submitted. In such cases, the proposal shall clearly state the reason(s) for not providing small 5 business data associated with the contracts otherwise cited as relevant for past performance 6 consideration hereunder. 7
8 VOLUME IV – PRICE 8
8.1 FACTOR 4: PRICE 9
The Offeror shall fill in prices for Tables 10-6 GPS III, 11-6 AFSPC-8, and 12-6 AFSPC-12, as 10 instructed in paragraphs 8.1 through 8.4 below. The Offeror shall not include price information 11 in any other portion of the proposal, except the Price Volume or Model Contract. When 12 completing Tables 10-6 GPS III, 11-6 AFSPC-8, and 12-6 AFSPC-12, the Offeror shall fill in the 13 same price as those proposed in the model contract for all applicable Contract Line Item 14 Numbers (CLINs), which are included in the Total Proposed Price; this also includes the Quick 15 Reaction/Anomaly Resolution rate. 16
8.2 MISSION UNIQUE REQUIREMENTS AND OPTIONS 17
The Offeror shall provide a proposed price for each mission unique requirement and option listed 18 in Tables 10-6 GPS III, 11-6 AFSPC-8, and 12-6 AFSPC-12; reference Tables 3.1-1, 3.1-2, 3.2-19 1, 3.3-1, 3.3-2, and 3.3-3 in the Mission Requirements Annex (MRA) Frontmatter for a list of 20 mission unique requirements and options. Note that unit pricing and maximum quantity order 21 prices shall be provided in the Model Contract. The Offeror shall provide these proposed prices 22 as an itemized list which corresponds to the mission unique requirements and options in the 23 referenced tables. TEP shall be priced at the maximum quantity proposed in the Model Contract 24 CLINs. 25
8.3 QUICK REACTION/ANOMALY RESOLUTION 26
For Quick Reaction and Anomaly Resolution, the Offeror shall complete Table 8-1 as shown 27 below and provide the resulting number (Total Proposed Dollars) for Tables 10-6, 11-6, and 28 12-6. For the model contract, the Offeror shall provide one composite rate which will be 29 effective towards all missions awarded. The maximum number of hours in SMC/LR-H005 will 30 reflect the sum of the hours associated with the mission(s) awarded. 31
1 TABLE 8-1: Q UICK REACTION AND ANOMALY RESOLUTION C ALCULATION
(C) (D) Other Mission and (A) (B) Proposed Comments
Mission Hours Years
Hours Proposed Rate Annual Dollars (A*B)
GPS III 2018 2,000
(Missions 1 2019 8,000 through 3) 2020 15,000
30,000 Hours 2021 5,000 Total 3 Total GPS III Proposed Dollars Fill in Table
Missions 10-6 2018 5,000
AFSPC-8
2019 7,500 2020 12,500
25,000 Hours Total AFSPC-8 Proposed Dollars Fill in Table
11-6 2018 5,000
AFSPC-12
2019 7,500 2020 12,500
25,000 Hours Total AFSPC-12 Proposed Dollars Fill in Table
12-6 Column (C) Column (C)
Calculation for SMC/LE H-0005 Total Total /80,000 hours
2 8.4 GOVERNMENT PROPERTY (GP)
3 If th e Offeror requires the use of GP, the Offeror shall complete Table 8-2 for each mission in 4 Microsoft Excel fon nat using the acquisition cost info1mation from Attachment 8 an d the rental 5 equivalency method described in FAR 52.245-9( e )(2) as laid out below:
6 • In Column (A), identify the requested GP 7 • In Column (B), identify th e acquisition cost from Attachment 8 an d list the dollar 8 value
9 • In Column (C), multiply column (B) by 2% (round to the nearest dollar) to 10 dete1mine th e monthly acquisition cost of the item and list the dollar value
11 • In Column (D), divide column (C) by 720 to detennine the hourly rental rate 12 (round to the nearest cents) and list the dollar value
13 • In Column (E), propose the rental time required (round to the nearest whole hour) 14 and list th e value; "rental time" is defined in 52.245-9(a)
15 • In Column (F), multiply column (D) by (E) (round to the nearest dollar) to 16 dete1mine the total rental charge for the requested item and list the dollar value
17 • Add the sum of Rental Charges per mission in Column (F) an d include in Table 18 10-6, 11-6, andl2-6.
Instrnctions to Off erors
1 TABLE 8-2: RENTAL EQUIV ALENCY FOR GOVERNMENT PROPERTY USE
(A) (C) (D) (E) (F)
(B) Hourly Rental Rental Item Acq Cost
Monthly Acq Cost Rate Time
Rental Charge Requested ($) (Multiply B *2 0/o)
(Divide C by 720) (per (Multiply D*E)
($) ($) mission)
Item A $100,000 $2,000 $2.78 400 $1,112
Item B $77,777 $1,556 $2.16 250 $540
Sum of Rental Charges for All GP Items: $1,652 (Insert Sum into Tables 10-6, 11-6, and 12-6)
2 *Notional cost figures are included in the table as examples only
3 9 VOLUME V - MODEL CONTRACT
4 9.1 GENERAL INSTRUCTIONS
5 The pmpose of this volume is to provide info1mation to the Government for preparing the 6 contract document and suppo1i ing file . The Offeror 's proposal shall include one (1) signed and 7 dated copy of the Standard Fo1m (SF) 1449, delivered with the SF1449 Continuation pages, the 8 Addendum, the Contract Documents, and Exhibits and Attachments. The original shall be 9 clearly marked and shall be provided without any punched holes. The SF1449 shall not have any
10 proprietaiy markings. Fill in all blanks in the Solicitation. Specifically, complete the following:
11 9.2 SF1449 SOLICITATION/CONTRACT FORM
12 The Offeror shall complete blocks 12, 17, and 30 on SF 1449 - Solicitation/Contract/Order for 13 Commercial Items. The Offeror shall use the SF 1449 Continuation in place of completing 14 blocks 19, 20, 21, 22, and 23. The signature by the Offeror on the SF 1449 constitutes an offer, 15 which the Government may accept.
16 9.3 SF1449 CONTINUATION SUPPLIES OR SERVICES AND COSTS/PRICES:
17 The Offeror shall provide prices on all CLINs. For mission unique options, provide both unit 18 prices and total maximum quantity prices. The Offeror shall provide the proposed launch vehicle 19 configuration within all CLINs descriptions.
20 9.4 ADDENDUM
2 1 For SMC/LE --H005 QUICK REACTION AND ANOMALY RESOLUTION, the Offeror must 22 propose a fixed price composite hourly rate.
23 9.5 DEFENSE PRIORITIES AND ALLOCATIONS SYSTEM RATING OF CONTRACT
24 Under Defense Priorities and Allocations System (DPAS) (15 CFR 700), the GPS missions ai·e 25 rated DO and the AFSPC missions are rated DX. Should an Offeror be awai·ded multiple 26 missions with separate DPAS ratings, the overall contract DPAS rating will be the highest 27 mission rating.
Instrnctions to Off erors
9.6 CONTRACT DOCUMENTS, EXHIBITS AND ATTACHMENTS 1
9.6.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
9.6.2 RESERVED 6
9.6.3 ATTACHMENT 8: GOVERNMENT PROPERTY 7
If the Offeror requires the use of GP, the Offeror shall complete and submit Attachment 8, 8 Government Property, IAW procedures and definitions detailed in DFARS 245.103-72 and 9 245.201-70. For more information, see the Department of Defense Procurement Toolbox at 10 http://www.dodprocurementtoolbox.org/site/detail/id/26. Failure to complete each applicable 11 data field in Attachment 8 may render the Offeror non-responsive and unawardable. For each 12 item of GP requested, the “Use As Is” column shall be filled in as “true.” 13
For each item of GP requested, the Offeror shall provide a written authorization of availability 14 from the cognizant Administrative Contracting Officer (ACO). GP proposed without an 15 authorization from the cognizant ACO may render the Offeror non-responsive and unawardable. 16 All supporting documentation associated with GP shall be submitted outside of the model 17 contract but within Volume V. 18
9.6.4 ATTACHMENT 9: PAYMENT PLANS 19
The Offeror shall fill in the dollar amount associated with each payment milestone in Table 1 of 20 Attachment 9, Payment Plan. There are two payment plans, one for missions with multi-21 manifests and one for missions without multi-manifests. The applicable payment plan will be 22 filled out for each mission. These plans will become an attachment to the contract if the mission 23 is awarded. IAW FAR 32.204 alternative financing terms shall not be accepted. 24
9.6.5 POTENTIAL ORGANIZATIONAL CONFLICT OF INTEREST (OCI) 25
1. IAW FAR 9.5, Organizational and Consultant Conflicts of Interest, the Contracting 26 Officer has analyzed the planned acquisition and determined that no known actual or 27 potential OCI situations exist with respect to this solicitation. 28
2. The Offeror shall perform its own OCI analysis and submit the results of that analysis as 29 part of its proposal. Specifically, the Offeror shall analyze the planned acquisition for 30 actual or potential OCI situations associated with its or any of its teammate’s or 31 subcontractor’s performance under any contract it or any of its teammates or 32 subcontractors has been or may be awarded by any federal agency or other entity. The 33 Offeror shall describe in detail the methodology used to identify actual or potential OCI 34 issues. If the Offeror identifies any actual or potential OCIs with respect to the 35 performance of itself or its subcontractors or teammates, the Offeror shall provide an OCI 36 Mitigation Plan to be incorporated as Attachment 11 to any resulting contract. At a 37 minimum, the plan shall address all of the items identified in the most current version of 38 SMC’s OCI Mitigation Plan Checklist provided in the Bidder’s Library. Any proposed 39 avoidance or mitigation techniques shall be consistent with FAR 9.5 and the most recent 40 decisions of the Government Accountability Office and the United States Court of 1 Federal Claims. 2
3. If award is made to the Offeror, the resulting contract may include an organizational 3 conflict of interest limitation applicable to subsequent Government work, at either a 4 prime contract level, at any subcontract tier, or both. During evaluation of proposals, the 5 Government may, after interactions with the Offeror and consideration of ways to 6 mitigate or avoid identified actual or potential conflicts of interest, insert a clause or term 7 and condition in the resulting contract which disqualifies the Offeror from further 8 consideration for award of future contracts. 9
4. Resolution of OCI issues are treated in a manner similar to the Contracting Officer’s 10 contractor responsibility determination. Any communications necessary to resolve OCI 11 issues shall not be considered discussions. As such, the Contracting Officer may issue 12 Evaluation Notices to the Offeror prior to any decision to enter into discussions in order 13 to resolve questions or concerns with the Offeror’s OCI analysis or mitigation plan. 14
9.7 SOLICITATION PROVISIONS 15
All representations and certifications must be completed IAW FAR 52.212-3 deviation in the 16 model contract, Offeror Representations and Certifications- Commercial Items. 17
9.8 SIGNATURE 18
The Offeror’s signature on the SF 1449 constitutes an offer, which the Government may or may 19 not accept. Proposals without signatures may warrant a rejection of the proposal submittal. 20 Offerors are required to meet all solicitation requirements, including terms and conditions, 21 representations and certifications, and technical requirements. Therefore, any tailoring to the 22 solicitation is not allowed and may warrant a rejection of the proposal. 23
1 10 ANNEX 1: VOLUME Illa - GPS III (THREE MISSIONS)
2 Annex 1 addresses the Offeror's technical approach and solution for meeting the Government's 3 requirements for the Perfo1mance and Schedule sub-factors . The Offeror shall describe their 4 proposed approach to meeting the requirements of each sub-factor. Offeror responses will be 5 evaluated against the Perfonnance and Schedule criteria defined in Attachment 6, Evaluation 6 Criteria, Annex 1. Only one technical proposal shall be provided to meet the RFP requirements 7 for the 3 GPS III missions (i.e. only one launch vehicle system, baseline configuration, block).
8 The Offeror shall provide only one (1) Orbital Insertion Accuracy, one (1) Mass-to-Orbit, one (1) 9 Launch CONOPS, one (1) Integrated Master Schedule (IMS) and one (1) Schedule Risk
10 Assessment (SRA) con esponding to the first GPS III ILC and the provided IMS and SRA will 11 suffice for the remaining two (2) GPS III missions within this RFP. No IMS or SRA is required 12 for the remaining two (2) GPS III missions within this RFP.
13 10.1 FAC TOR 2: PERFORMANCE
14 10.1.1 S UB-FAC TOR 1: ORBITAL I NSERTION A CCURACY
15 The Offeror shall complete the Proposed GPS III 3-Sigma Inse1iion Accuracy column in Table 16 10-1 for the proposed launch vehicle system of the GPS III mission. Three-sigma for Inse1iion 17 Accuracy is defined as 99.73% probability at 50% confidence.
18 TABLE 10-1: GPS Ill ORBIT I NSERTION TARGET AND A CCURACY REQUIREMENTS (SEE
19 NOTES)
Target Accuracy Proposed GPS III 3-sigma Parameter (see note 1) Requirement Requirement Insertion Accuracv Aoogee Altitude (km) (see note 2) 20,181 km ± 100 km
Perigee Altitude (km) (see note 4) 2:1,000 km ±25km
Inclination ( de2:) 55 deg ±0.1 deg Right Ascension of Ascending 245.63 deg (Plane A) - 5 I + 6.25 Node (deg) (see note 3) deg
Arnument of Perigee (de2:) 270 deg ± 0.5 deg Note 1: Orbital parameters coffespond to SV following separation including the effects of separation delta-V Note 2: The apogee altitude is the altitude of the SV at first apogee after transfer orbit inse1tion Note 3: RAAN target of245.63 deg coffesponds to Plane A in the GPS ill MRD adjusted to 15 December 2019 at OOOOZ.
Note 4: Perigee altitude must be ::'.::1000 km after accounting for proposed 3-sigma insertion acctu·acy Note 5: deg = degree{s), km = kilometer(s)
20 10.1.1.1 The Offeror shall provide a detailed description of their approach to meet all orbital 21 inse1iion targets and accuracy requirements described in Table 10-1 while complying with all 22 separation parameters detailed in Table 10-3. The description shall provide clear linkages 23 between the approach to meet requirements and the demonstrated perfo1mance of the proposed 24 or relevant cunent family of launch vehicle system. The description shall also include the 25 following:
26 a. Identification of the launch vehicle system, baseline configuration, and block 27 proposed.
28 b. A detailed description of the methodology(ies) (Monte Carlo or Covariance) used to 29 establish the inse1i ion accuracies from Table 10-1.
30 c. If Monte Carlo methodology is chosen, a minimum of 10,125 rnns must be
Instrnctions to Off erors
1 perfo1med. If the Covariance methodology is chosen, the offerer shall provide four 2 historical missions in which the covariance methodology analytical predictions are 3 compared to the actual flight orbital inse1tion.
4 d. Complete Table 10-2 with a list of all significant dispersions (e.g., engine 5 shutdown impulse) used in the methodology for establishing the inse1tion 6 accuracies and separation parameters from Table 10-1 and 10-3 respectively, 7 including justifications in a separate na1rntive paragraph.
8 Dispersions are defined as variations on perfonnance and navigation input parameters (e.g., 9 thmst, Isp, sensor bias/scale factors) used to generate inse1tion accuracy and separation parameter
10 results . Dispersions shall be listed in Table 10-2 with required data to describe the dispersions 11 used, including statistical distribution type (e.g., Gaussian, unifo1m).
12 TABLE 10-2: DISPERSIONS LIST
-3 sigma +3 sigma Statistical Dispersion value Nominal value Distribution Type
Parameter (subscript i)
Parameter 2 (subscript i=n)
13 10.1.1.2 The Offerer shall complete the Proposed GPS III Separation Parameter Accuracy 14 column in Table 10-3 for the GPS III mission with the following assumptions:
15 a. The spin direction shall be from -Ysv axis to + Xsv axis, about +Zsv axis 16 b. Pre-Space Vehicle (SV) Separation Visibility :::: 25 minutes after 5 degrees elevation angle 17 line of sight from any AFSCN asset.
Tar2et Accuracy Proposed GPS III Parameter Requirement Requirement
Separation Parameter Accuracv
Spin Rate (deg/sec) + 0.6 ±0.3
Pointing Accuracy of+ Zsv axis (deg) NEN :S 5
Transverse Angular Rate (Root Sum Square [RSS]) of the rates about the 0 :S 1.8 Xsvand Ysvaxes) (deg/sec)
Note: deg = degree{s), NEN = Negative Ecliptic No1mal, deg/sec = degrees per second
18 TABLE 10-3: GPS III SEPARATION PARAMETERS
19 At separation the Launch Vehicle (L V) shall be capable of orienting the SV positive 20 Z-axis (+Zsv) to any of the attitudes listed below. There are two possible separation 21 attitudes to cover inse1tion on any date or plane. The two attitudes are:
22 • Negative Ecliptic No1mal (NEN)
Instmctions to Off erors
1 • Positive Ecliptic Nonnal
2 The desired attitude for a specific mission will be provided after each SV call-up. The 3 separation attitudes are defined in the GPS III Mission Requirements Document [MRD].
4 For the purposes of this proposal only, the Offerer shall use a NEN separation attitude.
5 There is no constrnint on the orientation of the SV X-axis or Y-axis at separation.
6 10.1.1.3 The Offerer shall provide a completed Table 10-4, Historical Orbital Inse1i ion 7 Accuracy, for each of the four most recent (as of final RFP posted date) elliptical transfer orbit 8 launches of a launch vehicle system similar to the proposed launch vehicle system. If the launch 9 histo1y does not include four elliptical transfer orbit launches, then the Offerer shall complete
10 Table 10-4 with data from as many elliptical transfer orbit launches as flown and supplement with 11 data for the most recent launches (as of final RFP posted date). Historical launches shall not 12 include those that had a bmn-to-depletion mission design for spacecraft inse1i ion. The Offerer 13 shall provide detailed suppo1i ing rationale behind any changes to the dispersions (from Table 10- 14 2) or changes to the methodology used in generating the predicted accuracies for both the 15 historical elliptical transfer orbit launches or the most recent launches (as of final RFP posted 16 date).
17 TABLE 10-4: H ISTORICAL O RBITAL INSERTION ACCURACY
Apogee Perigee Argument
RAAN Inclination of Reference Missions Altitude Altitude
(deg) (deg) Perigee
(km) (km) (deg)
3-Sigma Requirement (Min, Target, Max) 3-Sigma Prediction (Min, Mean, Max)
!Actual Notes: deg = degrees, km = kilometers, RAAN = Right Ascension of Ascending Node
18 10.1.2 SUB -FACT O R 2: MAss-To-ORBIT
19 The Offerer shall provide a detailed description of the mass-to-orbit capability associated with the 20 proposed launch vehicle system for the GPS III mission, based on launching from the Eastern 21 Range for the Target and Accuracy Requirements in Table 10-1 . The Offerer shall provide an 22 analysis and a description of the methodology used to generate the final mass-to-orbit for the GPS 23 III mission. At a minimmn, the launch vehicle shall have the capability of inse1i ing the Total 24 Mass, described in Table 10-5, to the Target Requirements (including the accuracy specified) 25 defined in Table 10-1. The Offerer's proposed launch vehicle must lift the maximum SV launch 26 mass (reference the attached GPS III MRD to the MRA). The Offerer shall account for mission 27 unique requirements (excluding options) which reduce mass to orbit capability. This analysis and 28 methodology shall be based on either demonstrated flight perfonnance or engineering data.
29 10.1.2.1 The Offerer shall provide the upper stage perfo1m ance margin to the GPS III Target 30 Requirements detailed in Table 10-1 with the Total Mass as defined in Table 10-5. The Offerer 31 shall fill in the vehicle-specific payload equivalent masses in Table 10-5. The "Max SV Mass 32 Used" in Table 10-5 shall be greater than or equal to the maximum SV mass indicated in the 33 MRA (ref. GPS III MRD Section III.K [Mass Prope1i ies {separated SV}]) for the Offerer's
Instrnctions to Off erors
FA88 11-17-R-0004
1 selected integration type (vertical or horizontal) with the appropriate adjustment to the SV mass 2 for the Offeror's selected perigee value. The Offeror shall also provide the perfo1mance reserves 3 as specified below.
4 a. 3-sigma Flight Perfo1mance Reserve value (defined as 99.865% probability at 50% 5 confidence) calculated by Monte Carlo methodology with a minimlllll of 10,125 rnns 6 perfo1med to the GPS III Target Requirements detailed in Table 10-1 with the Total 7 Mass as defined in Table 10-5
8 b. SMC/LE Reserve (defined as the sum of 2% of the proposed launch system perfo1mance 9 capability to the reference orbit in Table 10-1 with Orbital Debris Mitigation Standard
10 Practice (ODMSP) compliance plus 75 pounds mass (lbm) of upper stage diy mass for 11 instillillentation reserve, converted to upper stage propellant equivalent mass)
12 c. Description and quantification of any additional reserves held
13 d. Any additional perfo1mance margin
14 TABLE 10-5 MASS-TO ORBIT
Description Mass Units
Max SV Mass Used lbs
Payload Adapter Mass (See Note 1) lbs
Total Mass lbs 15 Note 1: Payload Adapter (PLA) Mass is the mass of the PLA hardware including all 1 6 associated harnesses, the separation system, and attached hardware required for flight.
17 Note 2: lbs = pounds, SV = space vehicle
18 10.1.2.2 The Offeror shall provide the planned GPS III Mission Profile, including upper stage 19 disposal approach (Orbital Debris Mitigation Standard Practices - ODMSP compliance is not 20 waiverable) . The Offeror shall provide methodology and results demonsti-ating ~ 90% probability 21 of success for completing the planned upper stage disposal. The mission profile shall include the 22 proposed launch site and significant sequence of events to include times with respect to liftoff. At 23 a minimum, the sequence of events shall include the following mission profile events listed below 24 (a-i). If event is not applicable, the Offeror shall provide suppo1i ing rationale.
25 a. First stage engine staii 26 b. Solid rocket motor burnout and jettison sequence (if applicable) 27 c. First stage engine cutoff and separation 28 d. Payload fairing jettison 29 e. Upper stage engine bum ignition(s),cutoff(s) , and coast time(s) 30 f. Upper stage and SV separation 31 g. Initiation of upper stage Contamination and Collision Avoidance Maneuvers (CCAMs) 32 h. Upper stage disposal initiation 33 i. End of mission for upper stage, where end of mission is defined as the completion 34 of passivation with no fmiher planned maneuvers, or through upper stage impact 35 after conti-olled reentiy
Instructions to Off erors
Additionally, the Offeror shall provide orbital parameters (as defined in Table 10-1 for the 1 selected plane/date) of the SV at separation (including the effects of separation ∆V). 2
10.1.2.3 The Offeror shall provide data for any portion of…
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 .