07_Attachment_5_Instructions_to_Offerors_Combined.pdf

Evolved Expendable Launch Vehicle (EELV) Phase 1A-6 15

Competitive Acquisition 16 for NROL-85, NROL-87, SILENTBARKER, SBIRS GEO-5, 17 and AFSPC-44 18

FA8811-18-R-0001 21

Attachment 5 22

Instructions to Offerors 23

31 January 2018 25

Instructions to Offerors FA8811-18-R-0001

PROGRAM STRUCTURE AND OBJECTIVES 1

1.1 The Air Force Space and Missile Systems Center (SMC) anticipates making multiple awards 2 of launch services through this solicitation. Specifically, SMC anticipates making an individual 3 award for each launch service mission: NROL-85, NROL-87, SILENTBARKER (NROL-107), 4 SBIRS GEO-5, and AFSPC-44. The general requirements for the launch services are defined in the 5 Performance Work Statement (PWS) and Contract Data Requirements List (CDRL), while mission-6 specific requirements are defined in the mission-specific Interface Requirements Document (IRD) 7 for National Reconnaissance Office (NRO) missions and Mission Requirements Annex (MRA) for 8 Air Force missions. Requirements in the PWS and CDRLs with specific SILENTBARKER and 9 NRO-only references appear in grey text. Within the grey text, double-underlined references apply 10 to both NRO and Space-Based Infrared System (SBIRS) missions. 11

GENERAL INSTRUCTIONS AND MODEL CONTRACT 1

2.1 GENERAL INSTRUCTIONS 2

The Offeror's proposal shall include all data and information requested by this Request for 3

Proposal (RFP) and shall be submitted in accordance with (IAW) these instructions. This RFP is 4 organized such that the Model Contract is applicable to each mission. In developing the proposal, 5 the Offeror shall ensure that its proposed offer complies with all the requirements contained in the 6 RFP, to include the PWSs, IRDs, MRAs, and CDRLs. Noncompliance with the instructions 7 provided in this RFP may result in a determination that the proposal is nonresponsive and 8 unawardable. 9

The Offeror’s proposal shall be clear and concise and shall include sufficient detail for 10 effective evaluation and for substantiating the validity of stated claims. The proposal should not 11 simply rephrase or restate the Government's requirements, but shall provide convincing rationale to 12 address how the Offeror intends to meet these requirements. Offerors shall assume that the 13 Government has no prior knowledge of its capabilities and experience and will base its evaluation on 14 the information presented in the Offeror's proposal. 15

If the Government enters into discussions, it reserves the right to make a written request for 16 proposal updates to incorporate any directly relevant information from ongoing early integration 17 studies, mishap and anomaly findings, and updates to the joint work plan schedules or launch 18 vehicle certification(s). 19

The proposal validity date must be specified and the proposal must be valid for at least 365 20 days after date of submission. IAW Federal Acquisition Regulation (FAR) Subpart 4.8 21 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. 22 Unless the Offeror requests otherwise, the Government will destroy extra copies of such 23 unsuccessful proposals. 24

This RFP includes five missions consisting of NROL-85, NROL-87, SILENTBARKER, 25 SBIRS GEO-5, and AFSPC-44. Annex 1 contains mission specific criteria for NROL-85, Annex 2 26 contains mission specific criteria for NROL-87, Annex 3 contains mission specific criteria for 27 SILENTBARKER, Annex 4 contains mission specific criteria for SBIRS GEO-5, and Annex 5 28 contains mission specific criteria for AFSPC-44. Each mission annex is discussed within the 29 Instructions to Offerors (Attachment 5) and Evaluation Criteria (Attachment 6). 30

All Offerors shall respond via a proposal for all missions in this Request for Proposal (RFP). 31 In the event an Offeror cannot technically perform a specific mission, then the Offeror shall submit a 32 waiver for Government approval in lieu of a proposal for that specific mission. The waiver shall be 33 submitted no later than the proposal due date. The Government will evaluate the waiver to 34 determine whether the Offeror’s waiver demonstrates that the Offeror cannot technically perform the 35 mission. If the Government does not approve the waiver the Offeror’s proposal may be 36 unawardable for all missions. 37

The Government intends to make multiple award decisions: individual award decisions for 38

(1) NROL-85, (2) NROL-87, (3) SILENTBARKER, (4) SBIRS GEO-5, and (5) AFSPC-44. The 39 Government reserves the right to make all award decisions at once or rolling award decisions. 40 Should an Offeror be awarded multiple missions, the missions shall be awarded and executed on one 41 contract. Awards shall be made to the Offeror(s) that is evaluated, based on the evaluation factors 42 and Sub-factors, as the best value to the Government. 1

2.2 VOLUME VI – MODEL CONTRACT 2

GENERAL INSTRUCTIONS 3

2.2.1.1 The purpose of this volume is to provide information to the Government for preparing the 4 contract document and supporting file. The Offeror’s proposal shall include one (1) signed and 5 dated copy of the Standard Form (SF) 1449, delivered with the SF 1449 Continuation Pages, the 6 Addendum, the Contract Documents, and Exhibits and Attachments. The original shall be clearly 7 marked and shall be provided without any punched holes. The SF 1449 shall not have any 8 proprietary markings. Fill in all blanks in the Solicitation. Specifically, complete the following: 9

SF1449 SOLICITATION/CONTRACT FORM 10

2.2.2.1 The Offeror shall complete blocks 12, 17, and 30 on SF 1449 – Solicitation/Contract/Order 11 for Commercial Items. The Offeror shall use the SF 1449 Continuation Pages in place of completing 12 blocks 19, 20, 21, 22, and 23. The signature by the Offeror on the SF 1449 constitutes an offer, 13 which the Government may accept. 14

SF1449 CONTINUATION SUPPLIES OR SERVICES AND COSTS/PRICES: 15

2.2.3.1 The Offeror shall provide prices on all CLINs. For mission unique options, provide both unit 16 prices and total maximum quantity prices. The Offeror shall provide the proposed launch vehicle 17 configuration within the X001 description of launch vehicle production services. 18

DEFENSE PRIORITIES AND ALLOCATIONS SYSTEM RATING OF CONTRACT 19

2.2.4.1 Under Defense Priorities and Allocations System (DPAS) (15 CFR 700), NROL-85, NROL-20 87, SILENTBARKER, SBIRs GEO-5 are rated DX. Under DPAS (15 CFR 700), AFSPC-44 is 21 rated DO. If an Offeror is awarded multiple missions, the highest mission DPAS rating will be on 22 block 13B of the overall contract. 23

CONTRACT DOCUMENTS, EXHIBITS AND ATTACHMENTS 24

2.2.5.1 Attachment 3A: Small Business Subcontracting Plan 25

2.2.5.1.1 The Offeror shall provide a Small Business Subcontracting Plan IAW FAR 52.219-9 26 and Air Force Federal Acquisition Regulation Supplement 5319.704. The subcontracting plan will 27 be incorporated into the contract. 28

2.2.5.2 Attachment 3B: Small Business Participation Commitment Document (SBPCD) 29

2.2.5.2.1 The Offeror shall provide SBPCD IAW Paragraph 6.1 (Factor 1: Small Business 30 Participation). The SBPCD will be incorporated into the contract. 31

2.2.5.3 Attachment 7: Mission Requirement Annex (MRA) 32

2.2.5.3.1 If the Offeror proposes the use of excess performance margin, the Offeror shall 33 complete and submit Attachment 7, MRA Frontmatter, Table 3-0: Proposed Excess Performance 34 Margin. 35

2.2.5.3.2 Attachment 7, MRA, along with the proposed plan to use excess performance margin 36 as Appendix A, will be incorporated into the awarded contract. 37

2.2.5.4 Attachment 8: Government Property (GP) 38

2.2.5.4.1 If the Offeror requires the use of Government Property, the Offeror shall complete 1 and submit Attachment 8, Government Property, IAW procedures and definitions detailed in 2 DFARS 245.103-72 and 245.201-70. For more information, see the Department of Defense 3 Procurement Toolbox at http://www.dodprocurementtoolbox.org/site/detail/id/26. Failure to 4 complete each applicable data field in Attachment 8 may render the Offeror non-responsive and 5 unawardable. For each item of GP requested, the “Use As Is” column shall be filled in as “true.” 6

2.2.5.4.2 For each item of GP requested, the Offeror shall provide a written authorization of 7 availability and confirmation of the acquisition cost from the cognizant Administrative Contracting 8 Officer (ACO). GP proposed without an authorization from the cognizant ACO may render the 9 Offeror non-responsive and unawardable. All supporting documentation associated with GP shall be 10 submitted outside of the model contract within Volume VI. 11

2.2.5.5 Attachment 9: Payment Plans 12

2.2.5.5.1 The Offeror shall fill in the dollar amount associated with each payment milestone in 13 Table 1 of Attachment 9, Payment Plan. There are two payment plans, one for missions with multi-14 manifests and one for missions without multi-manifests. The applicable payment plan will be filled 15 out for each mission. These plans will become an attachment to the contract if the mission is 16 awarded. IAW FAR 32.204 alternative financing terms shall not be accepted. 17

2.2.5.6 Attachment 10: Flight Critical Items List (FCIL) 18

2.2.5.6.1 The Offeror shall identify the launch vehicle system, baseline configuration, and 19 block/build sequence proposed. The Offeror shall also provide an initial Flight Critical Items List 20 (FCIL) associated with the launch vehicle system proposed IAW CDRL BX18, block 4 and block 21

16. The FCIL will be incorporated into the contract as Attachment 10 upon award. 22

2.2.5.7 Attachment 11: Potential Organizational Conflict of Interest (OCI) 23

2.2.5.7.1 IAW FAR 9.5, Organizational and Consultant Conflicts of Interest, the Contracting 24 Officer has analyzed the planned acquisition and determined that potential OCI situations exists with 25 respect to this solicitation. 26

2.2.5.7.2 The Offeror shall perform its own OCI analysis and submit the results of that analysis 27 as part of its proposal and provide an OCI plan to be incorporated as Attachment 11 to any resulting 28 contract, if there is an actual or potential OCI. Specifically, the Offeror shall analyze the planned 29 acquisition for actual or potential OCI situations associated with its or any of its teammate’s or 30 subcontractor’s performance under any contract it or any of its teammates or subcontractors has 31 been or may be awarded by any federal agency or other entity. The Offeror shall describe in detail 32 the methodology used to identify actual or potential OCI issues. At a minimum, the OCI plan shall 33 address all of the items identified in the most current version of SMC’s OCI Plan Checklist provided 34 in the Bidder’s Library. Any proposed avoidance or mitigation techniques shall be consistent with 35 FAR 9.5 and the most recent decisions of the Government Accountability Office and the United 36 States Court of Federal Claims. 37

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

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

2.2.5.8 Attachment 12: Security Plan 7

2.2.5.8.1 The Offeror shall provide a detailed security plan to manage and process classified 8 payloads (Special Access Program/Special Access Required for the classified missions), and handle 9 and protect classified mission data (requirements, analysis inputs and results) IAW the Security 10 Classification Guide (SCG) as referenced in the classified mission IRDs. The proposed plan shall be 11 supported by previously demonstrated efforts and a description of how previously demonstrated 12 efforts will be applied or modified for this mission. If applicable, the proposed plan shall document 13 impacts due to the secondary objectives outlined in the model contract and risks associated with 14 program protection for the specific launches. If never demonstrated, the Offeror shall provide 15 evidence-based rationale to support the proposed plan. The security plan, and supporting rationale (if 16 applicable), shall be attached to the contract as Section J, Attachment 12. Failure to provide the plan 17 or failure to demonstrate the plan is supported by previously demonstrated efforts or evidence-based 18 rationale may render the proposal non-responsive and unawardable. 19

SOLICITATION PROVISIONS 20

2.2.6.1 All representations and certifications must be completed IAW FAR 52.212-3 deviation in the 21 model contract, Offeror Representations and Certifications - Commercial Items. 22

SIGNATURE 23

2.2.7.1 The Offeror’s signature on the SF 1449 constitutes an offer, which the Government may or 24 may not accept. Proposals without signatures may warrant a rejection of the proposal submittal. 25 Offerors are required to meet all solicitation requirements, including terms and conditions, 26 representations and certifications, and technical requirements. Therefore, any tailoring to the 27 solicitation is not allowed and may warrant a rejection of the proposal. 28

3 GENERAL INFORMATION 1

3.1 POINT OF CONTACT 2

The Procuring Contracting Officer (PCO), Captain Ashley Cunningham, is the sole point of 3 contact for this acquisition. Address any questions or concerns you may have to the PCO at 4 ashley.cunningham.4@us.af.mil or 310-653-3537. Written questions or concerns regarding this 5 RFP may be sent to the PCO at the address for Launch Enterprise contracting office (SMC/LEK) 6 located on the front page of the model contract/solicitation. 7

3.2 DEBRIEFINGS 8

The PCO will promptly notify Offerors of any decision to exclude them from the competitive 9 range, whereupon they may request and receive a debriefing IAW FAR 15.505. In addition, the 10 PCO will notify unsuccessful Offerors of the source selection decision IAW FAR 15.506. Upon 11 such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a 12 debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable. 13

3.3 DISCREPANCIES 14

If an Offeror believes that the requirements in this RFP contain an error or omission, or are 15 otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting 16 rationale as well as the remedies the Offeror is asking the PCO to consider as related to the omission 17 or error. 18

3.4 ELECTRONIC REFERENCE DOCUMENTS 19

Referenced documents for this solicitation are available at http://www.fedbizopps.gov. 20

Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information 21 has been posted to the website for this solicitation. 22

3.5 EXCHANGES 23

Exchanges of source selection information between the Government and Offerors will be 24 controlled by the PCO. Source selection information will be transmitted in person or via certified 25 mail, delivery service, or facsimile. 26

3.6 DISCUSSIONS 27

The Government reserves the right to award any or all missions without discussions. 28

However, the Government may conduct discussions with Offerors after establishing a competitive 29 range based on the ratings of each proposal against all evaluation criteria. Discussions may be held 30 on a mission-by-mission basis. The Government reserves the right to record audio 31 telecommunications with the Offerors during the source selection. 32

3.7 USE OF NON-GOVERNMENT ADVISORS 33

Offerors are advised that data submitted to the Government in response to this solicitation 34 will be released to individuals who work for the following companies as non-Government advisors 35 for review and analysis: 36

Company Name Address 37 The Aerospace Corporation PO BOX 92957, 38 Los Angeles, CA 90009-2957 39

Tecolote Research, Inc 2120 E. Grand Avenue, Suite 200, 1 El Segundo, CA 90245 2 Booz Allen Hamilton 8283 Greensboro Drive, 3 Mclean, VA 22102 4 Science Applications International Corporation (SAIC) 3030 Old Ranch Pkwy #200, 5 Seal Beach, CA 90740 6 Linquest 5140 West Goldleaf Circle, Ste 400 7 Los Angeles, CA 90056 8 Stellar Solutions 250 Cambridge Ave Ste 204, 9 Palo Alto, CA 94306 10

Offerors are advised that data submitted to the Government in response to this solicitation 11 may be released to individuals who work for the following companies as non-Government advisors 12 for administrative support. 13

Company Name Address 14 Business and Technology Solutions 3572 Dayton-Xenia Rd, Ste 210, 15

Beavercreek, OH 45432 16 ARRAY Information Technology 7474 Greenway Center Dr, Ste 600, 17

Greenbelt, MD 20770 18 Individuals from the above support contractors have signed individual non-disclosure 19 agreements with the Government, which strictly prohibits any release or disclosure of information 20 outside of the source selection team. 21

Proposal submission constitutes written consent for the Government to release data 22 submitted in response to this solicitation to the above-named companies. 23

3.8 ALTERNATIVE PROPOSALS 24

Alternative proposals will not be considered. Alternative proposals are those that do not 25 meet the terms and conditions of the RFP, including attachments. 26

PROPOSAL FORMAT/LIMITS 1

4.1 ORGANIZATION/NUMBER OF COPIES/PAGE LIMITS 2

The Offeror shall prepare the proposal as set forth in Table 4-1: Proposal Organization. The 3 titles and contents of the volumes shall be as defined in this table, all of which shall be within the 4 required page limits. The Volumes identified in the table shall be separately bound in three ring, 5 loose-leaf binders, plus each Volume’s electronic copy shall be saved on a separate compact disc 6 (CD) or digital video disc (DVD). Volumes I, II, and VI may be combined into one (1) binder. All 7 other Volumes shall be separate binders. For Volume IV and V, page separation tabs for each sub-8 factor shall be provided. The Offeror shall provide two hard copies of the proposal and two 9 electronic copies of the proposal on CDs or DVDs (unclassified only). All classified sections of the 10 proposal response will be provided in accordance with Paragraph 4.4. The contents of each proposal 11 volume are described in the paragraph as noted in the table below: 12

Table 4-1: Proposal Organization 14

Volume Title Hard Copies

Electronic Copies Page Limit

I Executive Summary 2 2 10 II Factor 1: Small Business 2 2 Unlimited III Factor 2: Past Performance 2 2 8 pages/contract

IVa NROL-85 Factor 3: Performance 2 2 250

Factor 4: Schedule 2 2 Unlimited Va NROL-85 Factor 5: Price 2 2 Unlimited

IVb NROL-87 Factor 3: Performance 2 2 250

Factor 4: Schedule 2 2 Unlimited Vb NROL-87 Factor 5: Price 2 2 Unlimited

IVc SILENTBARKER Factor 3: Performance 2 2 250

Factor 4: Schedule 2 2 Unlimited Vc SILENTBARKER Factor 5: Price 2 2 Unlimited

IVd SBIRS GEO-5 Factor 3: Performance 2 2 250

Factor 4: Schedule 2 2 Unlimited Vd SBIRS GEO-5 Factor 5: Price 2 2 Unlimited

IVe AFSPC-44 Factor 3: Performance 2 2 250

Factor 4: Schedule 2 2 Unlimited Ve AFSPC-44 Factor 5: Price 2 2 Unlimited

VI Model Contract 2 2 Unlimited

4.2 PAGE LIMITATIONS 1

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be 2 read or considered in the evaluation of the proposal, and excess paper copies will be shredded. If the 3 Government issues Evaluation Notices (EN) for discussions, page limitations may be placed on EN 4 responses. The specified page limits for EN responses will be identified in the letters sent along 5 with the EN to the Offerors. Unless otherwise specified, each page shall be counted except the 6 following: cover pages, table of contents, tabs, and glossaries. Additionally, for the Schedule Factor 7 the Offeror may include a narrative to articulate the proposed schedule. Elaborate brochures or 8 documentation, detailed art work, or other embellishments are unnecessary and are not desired. 9

4.3 PAGE SIZE AND FORMAT 10

A page is defined as each face of a sheet of paper containing information. When both sides 11 of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 by 11 12 inches (in.), not including foldouts. Except for the reproduced sections of the solicitation document, 13 the text size shall be no less than 12 point using Times New Roman font type. Tracking, kerning, 14 and leading values shall not be changed from the default values of the word processing or page 15 layout software. Use at least 1 in. margins on the top and bottom and ¾ in. side margins. Pages 16 shall be numbered sequentially by volume. These page size and format restrictions shall also apply 17 to EN responses. 18

Legible tables, charts, graphs, and figures shall be used wherever practical to depict 19 organizations, systems and layout, implementation schedules, plans, etc. These displays shall be 20 uncomplicated and legible, and shall not exceed 11 by 17 in. in size. Foldout pages shall fold 21 entirely within the volume, and each face of the foldout containing information will be counted as a 22 single page. Foldout pages may only be used for large tables, charts, graphs, and figures, not for 23 pages of text. For tables, charts, graphs, and figures, the text may be in the Offeror’s preferred 24 format. 25

4.4 CLASSIFIED INFORMATION 26

The Offeror shall provide unclassified proposal responses to the Government to the greatest 27 extent possible. Contact the SMC/LEK PCO no later than seven (7) calendar days prior to the 28 proposal due date for classified data submission. 29

If classified information is provided as part of the proposal response, it shall be provided 30 electronically via appropriate communication channels and as a single classified addendum. No 31 bound hard copies will be required. The electronic classified addendum shall be submitted 32 according to the applicable security regulations as follows: DoD 5220.22M, the EELV Security 33 Classification Guide, NRO Classification Guide pg 8, NRO IPG and the DD Form 254. Each entry 34 in the classified addendum shall be referenced to the proposal volume, Factor/Sub-factor, page 35 number, and paragraph number to which it applies. Similarly, a reference shall be placed in the 36 unclassified volume where the classified insert applies, giving the page and paragraph numbers 37 within the addendum where it can be found. Pages in a classified addendum will be included in the 38 page count for the applicable volume. 39

4.5 CROSS-REFERENCING 40

Each volume shall be written on a standalone basis so that its contents may be evaluated 41 without cross-referencing to other volumes of the proposal. However, cross-referencing within a 42 proposal volume is permitted where its use would conserve space without impairing clarity. 1

4.6 INDEXING 2

Each volume shall contain a table of contents with more detail than the master table of 3 contents included in the Executive Summary Volume, to delineate the subparagraphs within that 4 volume. Tab indexing shall be used to identify sections. 5

4.7 GLOSSARY OF ABBREVIATIONS AND ACRONYMS 6

Each volume shall contain a glossary of all abbreviations and acronyms used with a 7 definition for each. 8

4.8 BINDING AND LABELING 9

Each volume of the proposal shall be separately bound in a three-ring, loose-leaf binder, 10 permitting the volume to lie flat when open. Volumes I, II, and VI may be combined into one (1) 11 binder. All other Volumes shall be separate binders. Staples shall not be used. A cover sheet shall 12 be bound in each volume, clearly marked as to volume number, title, copy number, solicitation 13 identification, and the Offeror’s name. The same identifying data shall be placed on the spine of 14 each binder. Be sure to apply all appropriate markings including those prescribed IAW FAR 15 52.215-1(e) (Restriction on disclosure and use of data) and FAR 3.104-4 (Disclosure, Protection, 16 and Marking of Contractor Bid or Proposal Information and Source Selection Information). 17

4.9 ELECTRONIC OFFERS 18

The content and page size of electronic copies must be identical to the hard copies. All CDs 19 shall be placed in plastic sleeves that open on the top in one separate binder, with the volume 20 number and title indicated on each disc. Hypertext links shall be used to facilitate navigation within 21 the document. Use separate files to permit rapid location of all portions, including factors, exhibits, 22 annexes, and attachments, if any. If files are compressed, the necessary decompression program 23 must be included. The electronic copies of the proposal shall be submitted in a format readable by 24 Microsoft (MS) Office Word 2007/2010, MS Office Excel 2007/2010, MS Office Project 25 2007/2010, and MS Office Power Point 2007/2010, as applicable; exception applies to the Executive 26 Summary and the Model Contract. In the event there are discrepancies between the hard copies and 27 the electronic copies of the proposal, the electronic copies will be used for evaluation. The 28 “original” hardcopy and electronic copy of the proposal shall be identified. 29

4.10 DELIVERY INSTRUCTIONS 30

Delivery of proposals shall be coordinated with the PCO at least one (1) business day in 31 advance of the due date and time. Early deliveries of proposals shall also be coordinated with the 32 PCO. Electronic and hard copies of proposals are due 16 April 2018 by 4:00 pm Pacific Standard 33 Time. Proposals received after the date and time specified will be treated IAW FAR 52.212-1(f). 34 Proposals shall be addressed to the PCO and mailed or hand carried to: 35

SMC/LEK 36

Attn Primary: Capt Ashley Cunningham 37 Attn Alternate: Ms. Dzung Dom 38 483 N. Aviation Blvd. 39 El Segundo, CA 90245 40

VOLUME I – EXECUTIVE SUMMARY 1

5.1 The purpose of the Executive Summary Volume is to provide a complete overview of the 2 Offeror’s proposal. The Executive Summary Volume will not be evaluated, scored, or used to 3 clarify other discrepant information in other volumes. Any summary material presented in the 4 Executive Summary Volume will not be considered as meeting the requirements for any portions of 5 other volumes of the proposal. Do not include cost information. The Offeror shall provide the 6 following information in the Executive Summary: 7

5.2 NARRATIVE SUMMARY 8

The narrative summary of the entire proposal shall be concise, to include addressing any risk 9 areas and mitigations, and highlighting any key or unique features. The salient features shall tie in 10 with the evaluation factors in Attachment 6, Evaluation Criteria. 11

5.3 OFFEROR’S PROPOSED TEAM 12

The Offeror shall briefly identify the Offeror’s team to include major subcontractors. 13

5.4 MASTER TABLE OF CONTENTS 14

The Offeror shall include a master table of contents of the entire proposal. 15

5.5 CROSS REFERENCE MATRIX 16

The Offeror shall fill in the proposal column of the cross reference matrix below with the 17 volume, sections, and paragraph numbers from their proposal that correspond with the paragraph 18 numbers from Attachment 5 and Attachment 6 in Table 5-1 listed below. 19

Table 5-1: Cross Reference Matrix 1 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 VI: Model Contract 2.2 N/A N

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 6 N Volume III: Past Performance 7.1 7.1 Y Volume IV: IMS 8.1 8.4.1 N Volume IV: Risk Mitigation Plans 8.2 8.4.2 N Volume V: Price 9.1 9.1 N Volume IVa: NROL-85 10.1 10.1 Y Volume Va: NROL-85 Price 10.7 9.1 N Volume IVb: NROL-87 11.1 11.1 Y Volume Vb: NROL-87 Price 11.6 9.1 N Volume IVc: SILENTBARKER 12.1 12.1 Y Volume Vc: SILENTBARKER Price 12.7 9.1 N Volume IVd: SBIRS GEO-5 13.1 13.1 Y Volume Vd: SBIRS GEO-5 Price 13.7 9.1 N Volume IVe: AFSPC-44 14.1 14.1 Y Volume Ve: AFSPC-44 Price 14.6 9.1 N

VOLUME II – SMALL BUSINESS 1

6.1 Small Business Subcontracting Plan 2

The Government anticipates certain portions of this effort being subcontracted to small 3 businesses in order to meet statutory goals. Large businesses shall consider, to the highest extent 4 possible, subcontracted opportunities with small businesses. 5

All Offerors (except small businesses proposing as a Prime Contractor) shall provide the 6 below information: 7

Total dollars anticipated to be subcontracted to small businesses $ _________ 8 Total proposed contract value $ _________ 9 % anticipated to be subcontracted to small business (4% min) _____% 10 Offerors shall ensure that the information provided above is consistent with the information 11 included in the Small Business Subcontracting Plan submitted in accordance with FAR 52.219-9. 12 The Small Business Subcontract Plan will be included into the contract as Attachment 3A. 13

6.2 SMALL BUSINESS PARTICIPATION COMMITMENT DOCUMENT 14

IAW DFARS 215.304(c)(i), the extent to which Offerors identify and commit to small 15 business participation shall be evaluated in other than lowest priced technically acceptable 16 acquisitions. The Offeror shall submit a Small Business Participation Commitment Document 17 (SBPCD) which specifies the Offeror’s level of commitment to small business utilization in 18 performance of this requirement. A SBPCD is required from all Offerors, including companies with 19 commercial plans and comprehensive subcontracting plans. The SBPCD shall address the following: 20

6.2.1.1 The extent to which the Offeror will utilize small business, small disadvantaged business, 21 women-owned small business, historically underutilized business zone (HUB Zone) small business, 22 veteran-owned small business, and service-disabled and veteran owned small business. 23

6.2.1.2 Level of commitment to use such firms 24

6.2.1.3 Types of work the small business firms are to perform 25

6.2.1.4 Statement of quantitative degree to which small businesses (including small businesses in all 26 socio-economic categories) will participate in the acquisition relative to the total value of the 27 acquisition. (A minimum quantitative requirement (MQR) of 4% or better of the total contract value 28 for small business concerns participation is required. Small business primes performance is included 29 in the 4% or better participation). 30

6.2.1.5 Detailed explanations/documentation supporting the proposed participation commitment and 31 qualitative degree of participation. (Note: this information will not be incorporated into the resultant 32 contract) 33

The SBPCD will be included into the contract as Attachment 3B. 34

PAST PERFORMANCE 1

7.1 VOLUME III, FACTOR 2: PAST PERFORMANCE 2

PAST PERFORMANCE INFORMATION (PPI) FORMS 3

7.1.1.1 Each Offeror shall submit a past performance volume with its proposal, containing past 4 performance information IAW the format contained in Attachment 5 Appendix B. 5

7.1.1.2 The Government will use data provided by each Offeror in this volume as well as data 6 obtained from other sources in its evaluation of past performance. 7

VOLUME ORGANIZATION 8

7.1.2.1 The Past Performance volume should be organized according to the following general 9 outline: 10

a. Table of Contents 11

b. Recent and Relevant Missions (Attachment 5 Appendix B) 12

c. Attachments (Attachment 5 Appendix C, Attachment 5 Appendix D, and Attachment 5 13

Appendix E) 14

d. Glossary of Abbreviations and Acronyms 15

CONSENT/AUTHORIZATION LETTERS 16

7.1.3.1 Along with the PPI required in this section, the Offeror shall submit a consent letter, 17 Attachment 5 Appendix C, executed by each subcontractor, authorizing release of adverse past 18 performance information to the Offeror so the Offeror can respond to such information. For each 19 identified mission for a customer, the Offeror shall also submit a client authorization letter, 20 Attachment 5 Appendix D, authorizing release to the Government of requested information on the 21 Offeror's performance. 22

RECENT AND RELEVANT MISSIONS 23

7.1.4.1 Offeror’s shall submit information IAW Appendix B: Past Performance Information 24 Instructions (PPI), on five recent missions that demonstrate its ability to perform the proposed 25 mission; reference Attachment 6, Paragraphs 7.3 (Recency Evaluation) and 7.4 (Relevancy 26 Evaluation), for recency and relevancy definitions. Offeror’s Past Performance submittal shall 27 provide at least one mission relevant to each of the missions. If no recent or relevant past 28 performance information exists, notify the PCO in writing by the date specified in Paragraph 4.10 29 (Delivery Instructions). 30

7.1.4.2 Specific Content 31

7.1.4.2.1 Offerors are required to explain what aspects of the missions are deemed relevant to 32 the proposed mission and to what factor/Sub-factor they relate to. The Offeror is responsible for 33 ensuring that all information provided in the Past Performance Volume is current, accurate, 34 complete and properly classified. This may include a discussion of the missions accomplished by 35 the Offeror to resolve problems encountered on prior contracts as well as past missions to identify 36 and manage program risk. If the Offeror has encountered problems on previous missions, then the 37 Offeror is required to clearly demonstrate management actions employed in overcoming those 38 problems and the effects of those actions in terms of improvements achieved or problems rectified. 39

7.1.4.2.2 Offerors shall provide the narrative within Appendix B to support how the past 1 performance information submitted for evaluation demonstrates the offeror's ability to meet the 2 scope of this contract. 3

PAST PERFORMANCE QUESTIONNAIRES (PPQS) 4

7.1.5.1 The Offeror shall forward the PPQ template, Attachment 5 Appendix E, to each mission 5 POC identified in the PPIs. 6

7.1.5.2 The Offeror should monitor the completion of the questionnaires and make every effort to 7 ensure completed questionnaires are submitted by the submission deadline. 8

7.1.5.3 Questionnaire respondents shall email completed PPQs directly to the following POC listed 9 below. PPQs should be emailed by proposal submission date. Submission of contact information 10 for previous relevant missions IAW Attachment 5 is due via email no later than 16 April 2018. The 11 information to be submitted shall include customer name with two points of contact (name and title, 12 email, phone number, and address). The PPQs shall be considered source selection information and 13 shall not be released to the Offeror. 14

Los Angeles Air Force Base 15 Attn Primary: Capt Ashley Cunningham 16 E-Mail to: ashley.cunningham.4@us.af.mil 17 Attn Alternate: Ms. Dzung Dom 18 E-Mail to: dzung.dom@us.af.mil 19 483 N. Aviation Blvd 20 El Segundo, CA 90245 21

7.1.5.4 Even though the assessment of Past Performance is separate and distinct from Determination 22 of Responsibility required by FAR 9, past performance information evaluated during source 23 selection may be used to support the Determination of Responsibility for the successful awardee. 24

SMALL BUSINESS SUBCONTRACTING HISTORY 25

7.1.6.1 Pursuant to Defense Federal Acquisition Regulation System (DFARS) 215.305, all Offerors 26 (large and small) shall provide a narrative describing its use of small business concerns over the past 27 three (3) years on the recent, relevant missions submitted for Government consideration under this 28 factor. Proposals shall describe the actual use of small businesses as subcontractors, joint 29 venture/teaming partners and demonstrate the extent of compliance with FAR 52.219-8, Utilization 30 of Small Business Concerns, the Offeror's small business subcontracting plans (other than small 31 businesses only), and any related contract incentives. Other than small business, Offerors shall 32 specifically describe the small business goals for all categories of small business and the extent to 33 which the goals were achieved in contracts that required subcontracting plans for the past three 34 years. To supplement the narrative summary, other than small business, Offerors shall provide the 35 most recent Individual Subcontracting Reports or Summary Subcontract Reports for each relevant 36 contract that required submission of such reports. These subcontracting reports will not count 37 against the page limitations for the Past Performance volume. 38

VOLUME IV, FACTOR 4: SCHEDULE 1

This volume addresses the Offeror’s technical approach and solution for meeting the Government’s 2 requirements for each Schedule sub-factor. The Offeror shall describe their proposed approach to 3 meeting the requirements of each sub-factor. Factor 4: Schedule is evaluated in two Sub-factors, 4 section 8.1.1, Sub-factor 1, Integrated Master Schedule and section 8.2.1, Sub-factor 2, Risk 5 Mitigation Plans. Offeror responses will be evaluated against the Schedule criteria defined in 6 Attachment 6, Evaluation Criteria, Paragraph 8.1. 7

8.1 SUB-FACTOR 1: INTEGRATED MASTER SCHEDULE (IMS) 8

The Government expects the proposal response to Factor 4, Schedule to be unclassified. For 9 each launch service proposed (NROL-85, NROL-87, SILENTBARKER, SBIRS GEO-5, and 10 AFSPC-44), the Offeror shall provide a separate Microsoft Project IMS (including hard copies) and 11 Schedule Risk Assessment (SRA). The source selection team reserves the right to use program 12 office risk assessments, anomaly analysis, and other schedule risks, as appropriate, in proposal 13 evaluation. The Offeror shall construct all of the RFP 1A-6 mission’s IMS as follows: 14

8.1.1.1 Each IMS shall include elements a-g listed below at a minimum. Additionally, the IMS shall 15 include all open non-recurring design validation (NRDV) (Reference the PWS, Appendix A: 16 Glossary of Terms, for the NRDV definition) activities applicable to the as-proposed launch vehicle 17 configuration and launch pad that relate to the following: Management Systems, Flight Experience, 18 System Design Validation, Design Reliability, Manufacturing & Operations and Systems 19 Engineering Process Validation, System Safety, Test and Verification, Quality Systems/Processes, 20 Flight Hardware and Software Qualification, Launch Vehicle Analysis, Risk Management, 21 Integrated Analysis, Launch Complex, and Air Force EELV Requirements. Additionally, the 22 Offeror shall identify risks where the Risk Management plans tasks precede NRDV, are a part of 23 NRDV, or do not require NRDV. 24

a. Discrete tasks consistent with all proposed work; 25

b. Task durations based on an approximation of required resources; 26

c. Relationships/dependencies that identify how predecessor and successor tasks and milestones 27 are logically linked; 28

d. Milestones; 29

e. Total float/slack; 30

f. Task and milestone descriptions that clearly identify the scope and deliverable of the work 31 being accomplished, including Level of Effort (LOE) tasks; 32

g. Identified Critical Paths 33

8.1.1.2 Each IMS shall be an integrated, logically driven network constructed at the lowest level of 34 tasks that form the network to identify a valid critical path. 35

8.1.1.3 Each IMS shall identify three Critical Paths: primary, secondary, and tertiary. Each Critical 36 Path shall have a different critical driver (e.g, long lead activity, non-recurring activity, discrete 37 production activity) based upon the sequence of activities which represent the longest path between 38 the activities’ start and finish dates. 39

8.1.1.4 Each IMS shall have tasks with traceability to the WBS, providing a text field that maps the 40 task to each WBS sections IAW Appendix A. For every WBS section in the IMS, the level of detail 41 shall be at least one level lower than the lowest WBS element to create an integrated network of 42 tasks to support the full scope of work of each proposed mission’s launch service WBS. 1

8.1.1.5 The Offeror shall identify all schedule margin within each IMS. 2

8.1.1.6 The IMS task durations shall be supported by the resource-loading of workforce (labor) 3 resources. The task durations shall be based on the Offeror’s estimation of the personnel and 4 skillsets required to accomplish the scope of each task. The resource sheet (within Microsoft 5 Project) shall identify the specific workforce resources at the lowest level required to demonstrate 6 credibility of the task duration with a description of the personnel and skillsets required for each task 7 IAW CDRL AX06, block 4 and block 16. The Offeror shall not assign resources to milestone 8 events (defined as key programmatic events which represent progress and completion of the 9 contract). 10

8.1.1.7 The Offeror shall support IMS task durations excluding LOE tasks (defined as activities 11 which are typically related to management and other oversight that continues until the detailed 12 activities they support have been completed), Schedule Visibility Tasks (SVTs) are defined as 13 tasks/activities or milestone events in the IMS which increase management visibility and 14 functionality of the schedule for items not related to the Performance Measurement Baseline) and 15 milestones with at least one or more of the following: actual historical performance data, rationale 16 and/or lessons learned. The use of LOE tasks, SVTs, and milestones shall be IAW DI-MGMT-17 81861A/T. To support the credibility of task durations, the Offeror may provide statement(s) of 18 assumptions. The Offeror shall provide a summary of historical performance data, rationale and 19 lessons learned used to determine all task durations. The Offeror shall provide actual data and basis 20 of estimation (historical performance data, rationale, lessons learned, and statements of assumptions) 21 for all tasks on the Critical Paths within the schedule narrative. 22

Each IMS shall reflect the following activities sufficient to support the proposed launch 23 service as follows: 24

8.1.2.1 The IMS for each mission shall reflect a start date no earlier than the following according to 25 each mission ILC: 26

a. NROL-85: ILC: 1 Aug 2021 (30 months integration required) 27

b. NROL-87: ILC: 1 Apr 2021 (30 months integration required) 28

c. SILENTBARKER: ILC: 1 Jan 2022 (30 months integration required) 29

d. SBIRS GEO-5: ILC: 1 Jan 2021 (24 months integration required) 30

e. AFSPC-44: ILC: 1 Oct 2020 (24 months integration required) 31

8.1.2.2 Each mission’s IMS shall encompass all tasks required to accomplish the proposed launch 32 service from contract award to contract completion, to include activities to accomplish the tasks in 33 the PWS, Program Milestone Reviews (PWS, Appendix H), and CDRLs, IAW the WBS. 34

8.1.2.3 Each IMS shall identify all critical events to include but not limited to the following: LV 35 production with identification of the longest lead hardware; testing at the component, subsystem, 36 system, and integrated level; major reviews; encapsulation; transport; integrated testing; LV/PL 37 mate; and ILC. 38

8.1.2.4 If applicable, each mission’s IMS shall include tasks sufficient to accomplish the non-39 recurring design validation work and Risk Mitigation Plans as described in paragraph 8.2.2 and 8.2.3 40 to include appropriate durations. For the purposes of this proposal, the Contractor shall assume that 41 Government approval of the open NRDV work will be obtained 2 months following completion of 42 final contractor NRDV efforts. To support task durations, the Offeror shall provide at least one of 1 the following within the schedule narrative: actual historical performance data, rationale, or lessons 2 learned. All Non-recurring design validation work and Risk Mitigation Plan tasks shall be resource 3 loaded. 4

8.1.2.5 The Offeror’s proposal shall include the ILC of the Offeror’s forecasted launches during the 5 timeframe of contract start to the proposed launch service ILC (NROL-85, NROL-87, 6 SILENTBARKER, SBIRS GEO-5 and AFSPC-44) as part of the schedule narrative. The Offeror’s 7 proposal shall also provide a summary of critical milestone events (booster, upper stage, and fairing 8 ship dates) for the Offeror’s other launches during the timeframe of contract start to ILC for the 9 NROL-85, NROL-87, SILENTBARKER, SBIRS GEO-5 and AFSPC-44 launch services proposed 10 as part of the schedule narrative. 11

Schedule Risk Assessment (SRA)– The Offeror shall perform a SRA of the proposed launch 12 services IMS (NROL-85, NROL-87, SILENTBARKER, SBIRS GEO-5 and AFSPC-44) to predict 13 the probability of project completion to support the ILC IAW the sub-criteria below. Additionally, 14 the Government reserves the right to run the Monte Carlo simulation-based SRA input data to 15 evaluate (provide creditability) SRA results utilizing a tool called the Full Monte. 16

8.1.3.1 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

8.1.3.2 The Offeror shall report the SRA results in the following formats: (1) cumulative probability 19 in the form of an S-curve, (2) probability density in the form of a histogram, (3) probability density 20 in the form of a Triangular Distribution Function sized to approximate the probability density 21 histogram, and (4) the specific completion dates for every 10th percentile from 10 to 90 percent. The 22 Triangular Distribution Function shall be constructed as described in the Air Force Acquisition 23 Excellence & Change Office (AQXC) Schedule Risk Assessment (SRA) Process Reference 24 Document 25

8.1.3.3 The Offeror shall develop individual three-point estimates (best case, most likely, and worst 26 case) for all tasks on the Critical Paths, non-recurring design validation work and tasks which are 27 low-medium, medium, or high risk captured in the Offeror’s Risk Mitigation Plan. The Offeror 28 shall provide fields within the Microsoft Project File listing the three-point estimates. If the Offeror 29 cannot provide three-point estimates, the Offeror shall use the standard global editing percentages 30 for minimum and maximum durations as follows: Low Risk (85-110%), Medium Risk (90-115%), 31 and High Risk (95-125%) (Refer to Air Force Acquisition Excellence & Change Office (AQXC) 32 Schedule Risk Assessment (SRA) Process, Global Editing / Risk Banding). The Offeror shall 33 provide a summary within the schedule narrative to explain the rationale and assumptions for the 34 three-point estimates. 35

Three-point estimates shall be supported by the Offeror’s actual historical performance data 36 if the task has been previously performed. If the task has not been previously performed, the Offeror 37 shall provide rationale to justify three-point estimates. The Offeror shall provide a summary within 38 the schedule narrative to explain the use of historical performance data, rationale, lessons learned, 39 and assumptions to include, if applicable, standard global editing percentages for minimum and 40 maximum durations to determine all three-point estimates. 41

DCMA 14 Point Schedule Assessment – The Offeror shall construct the IMS IAW the 42 DCMA 14 Point Schedule Assessment guidelines, excluding Invalid Dates, Resources, Missed 43

Tasks, and Baseline Execution Index. The Offeror shall provide justification for each component of 1 the IMS that falls beyond the guideline thresholds. This analysis shall exclude Completed Tasks, 2 LOE tasks, Summary Tasks (tasks made up of subtasks which show their combined information), 3 Milestone events, Space Vehicle Contractor (SVC) tasks, and SVTs. 4

8.1.5.1 Logic – The number of activities that are missing a predecessor, a successor, or both shall 5 not exceed the threshold of 5% of the activities within the Offeror’s IMS absent credible and 6 reasonable justification for the use of predecessor/successor relationships beyond the 5% threshold 7 of all activities within the Offeror’s IMS. 8

8.1.5.2 Leads – The number of activities with leads (negative lag) shall not exceed the threshold of 9 0% of the activities within the IMS absent credible and reasonable justification for each lead 10 relationship used in the IMS. 11

8.1.5.3 Lags – The total number of activities with lags shall not exceed the threshold of 5% of the 12 activities within the Offeror’s IMS absent credible and reasonable justification for the use of lag 13 relationships beyond the 5% threshold for all activities within the Offeror’s IMS. 14

8.1.5.4 Relationship Types – The total number of activities with Finish-To-Start (FS) logic links 15 shall be at least 90 percent. Tasks with all other logic links Start-To-Start (SS) and Finish-To-Finish 16 (FF) should be less than the threshold of 10% of total tasks within the IMS absent credible and 17 reasonable justification for the use of logic links other than (FS) relationships beyond the 10% 18 threshold for all activities within the Offeror’s IMS. 19

8.1.5.5 Hard Constraints – The number of activities with hard constraints (Must-Finish-On, Must-20 Start-On, Start-No-Later-Than, & Finish-No-Later-Than) shall not exceed the threshold of 5% of the 21 activities within the Offeror’s IMS absent credible and reasonable justification for the use of hard 22 constraints beyond the 5% threshold for all activities within the Offeror’s IMS.