08_Attachment_6_Evaluation_Criteria.pdf

PDF 2 MB Posted

Attached to
EELV Phase 1A GPS III Contract Award / AFSPC-8 and AFSPC-12 Contract Award
Solicitation number
FA8811-17-R-0004
Issued by

About this file

08 Attachment 6 Evaluation Criteria

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

Evaluation Criteria FA8811-17-R-0004

Evolved Expendable Launch Vehicle Phase 1A Competitive

Acquisition for GPS III, AFSPC-8, and AFSPC-12 Launch Services

FA8811-17-R-0004

Attachment 6

Evaluation Criteria

29 June 2017

1 RESPONSIBILITY 1

The Procuring Contracting Officer (PCO) will make a responsibility determination after the 2 evaluation of proposals to determine whether an Offeror is eligible for contract award. In addition 3 to the general responsibility matters provided under Federal Acquisition Regulation (FAR) 9.104-1, 4 the PCO will consider directly relevant early integration studies, anomaly findings, and the Space 5 and Missile Systems Center (SMC) Commander's certification of the Offeror's proposed launch 6 system as a certified Evolved Expendable Launch Vehicle (EELV) launch system to determine 7 adequate technical skill, among other standards listed in FAR 9.104-1, to launch National Security 8

Space (NSS) missions. 9

The evaluation of the necessary organization, experience, technical skills, quality assurance, safety 10 programs, and other elements of responsibility is necessarily more rigorous than the responsibility 11 determination for other types of work. Within the evaluation, the PCO will verify an Offeror has an 12

EELV Launch System capable of meeting the mission requirements of this solicitation. Information 13 from the EELV certification process pertaining to an Offeror’s launch system may be considered, 14 which align with the categories provided within the New Entrant Certification Guide (NECG). The 15

NECG lays out a framework providing multiple paths to achieve certification. Launch system 16 certification is an agreed-to process to review the non-recurring portions of the launch system 17 mission assurance process. Launch system certification consists of the validation of launch vehicle 18 and infrastructure design and qualification along with verification of the Launch Vehicle 19

Contractor’s (LVC) engineering, manufacturing, and integration processes. This framework 20 provides a methodology for certification of launch systems based on payload risk classification. The 21

NECG lists the standards and specifications the LVC must satisfy, data the LVC must provide to 22 support the Government’s independent verification and validation process, and the evaluation 23 process SMC uses to determine if launch system certification requirements are satisfied. Therefore, 24 certification requires a rigorous responsibility determination necessary to ensure the high level of 25 organization, experience, technical skills, quality assurance, safety programs, and other elements of 26 responsibility necessary for NSS missions. 27

Below are examples of critical certification assessments made to ensure Offerors can meet 28

Government requirements. 29

Flight Margin Verification—Assesses mass-to-orbit performance margin and three-sigma margin 30 protection of all critical flight parameters, including performance margin, battery life, controls, 31 structures, and dynamics from liftoff through end of mission. 32

Flight Hardware and Software Qualification—Hardware qualification is the verification that a 33 hardware item, subsystem, or system, together with its embedded software, meets all requirements 34 and constraints of the environmental and operating conditions anticipated over its life cycle, 35 including specified margin to the maximum predicted flight environment. Software qualification 36 verifies that all software requirements and constraints can be satisfied using operationally 37 representative data in an operationally representative configuration. 38

Compliance with Orbital Insertion Accuracy—EELV-class launch systems are required to 39 provide three-sigma orbital injection accuracy. The accuracy at the final orbit injection point for 40 each payload mission is defined by variables such as: apogee, perigee, inclination, eccentricity, 41 argument of perigee, longitude of ascending node, and Right Ascension of Ascending Node, with 42 values defined in the NECG. 1

Design and Mission Reliability—Design reliability is the product of structure and mechanical 2 reliability, propulsion and thrust vector control reliability, avionics and guidance reliability, and 3 electrical power subsystem reliability along with the reliability (probability of success) for each 4 staging event. Mission reliability is composed of two components: (1) vehicle design and (2) launch 5 processing. This takes into account the vehicle design reliabilities and the probability that ground 6 operations (including infrastructure) or workmanship will induce a fault which can result in a 7 mission failure. 8

Compliance with Standard Interface Specification—Defines the standard interface between the 9 payload and the launch system. The interface includes mechanical, electrical and avionics interfaces, 10 fluid interfaces and services, thermal environments, contamination control, acceleration load factors, 11 dynamic environments, ground and facilities processing. 12

The SMC Commander is responsible for determining launch system certification. Once certification 13 is determined, the SMC Commander issues a formal EELV Certification Letter detailing any 14 limitations against the certification and conditions for maintaining the certification, including 15 verification of the acceptability of any changes to the vehicle or ground systems, maintenance of the 16 technical data underpinning the certification, and continued process discipline. Launch system 17 certification can be withdrawn at any time by the SMC Commander if a determination is made that 18 requirements upon which certification is based are no longer being satisfied. 19

Launch system certification is a key element to gaining insight into the rigorous technical 20 capabilities and processes that demonstrate the ability to launch NSS missions and contributes to the 21 overall NSS flight worthiness process. Flight worthiness certification for a specific NSS mission is 22 determined prior to launch through the SMC Flight Readiness Review process by the SMC 23

Commander. 24

2 BASIS FOR CONTRACT AWARD 25

This is a best value source selection conducted in accordance with FAR 15.3, Source Selection, as 26 supplemented by the Defense FAR Supplement (DFARS), Air Force FAR Supplement (AFFARS), 27 and Department of Defense Source Selection Procedures dated 31 March 2016. The Government 28 intends to award a contract to one or more Offerors that the Government deems capable of meeting 29

EELV mission requirements (to include all stated terms, conditions, representations, certifications 30 and all other information required by the Instructions to Offerors of this solicitation) based on a best 31 value determination. The Offeror(s) will need to be deemed responsible in accordance with FAR 32

9.1, as supplemented by DFARS and AFFARS, and proposal(s) must conform to the solicitation’s 33 requirements to be eligible for award. While the Government will strive for maximum objectivity in 34 its evaluations, the source selection process, by its nature, is subjective and, therefore, professional 35 judgment is implicit throughout the entire process. 36

The Government reserves the right to award without discussions. However, the Government may 37 conduct discussions with Offerors after establishing a competitive range based on the ratings of each 38 proposal against all evaluation criteria. 39

The Government intends to make three (3) separate award decisions. The Government will make an 40 award decision for (1) the three Global Positioning System (GPS) III missions (winner-take-all), (2) 41

Air Force Space Command (AFSPC)-8, and (3) AFSPC-12. The Government reserves the right to 42 make all award decisions at once or rolling award decisions. Should an Offeror be awarded multiple 1 missions, the missions shall be awarded and executed on one contract. If rolling awards occur, 2 contract modifications may be made to include the additional mission(s). The Total Proposed Price 3

(TPP) will be the price put on contract. 4

For GPS III, AFPSC-8 and AFSPC-12 missions, past performance, performance, and schedule 5 factors are of equal importance. All technical subfactors are of equal importance. Further, past 6 performance, performance, and schedule factors when combined are of equal importance to price. 7

Award shall be made to the Offeror(s) whose proposal is determined to be Acceptable for all sub-8 factors and factors with the lowest Total Evaluated Price (TEP). The Government reserves the right 9 to cross-reference between volumes and sections of volumes, including across missions, to support 10 proposal evaluation. 11

3 GENERAL INSTRUCTIONS 12

The Government will evaluate all information the Offeror provides in accordance with Attachment 5 13

Instructions to Offerors with the exception of the executive summary. It is mandatory for Offerors 14 to respond via a proposal for all missions in this Request for Proposal (RFP). In the event an 15

Offeror cannot technically perform a specific mission, then they can submit a waiver in lieu of a 16 proposal for that specific mission. Submission of insufficient information may result in the Offeror 17 being unresponsive and, therefore, the proposal may be determined to be Unacceptable and 18 ineligible for award. If during the evaluation period, it is determined to be in the best interest of the 19

Government to hold discussions, Offeror responses to Evaluation Notices and the Final Proposal 20

Revision (FPR) will be evaluated. If discussions occur, the Government reserves the right to request 21 proposal updates based on directly relevant early integration study results or anomaly resolution 22 findings, and any proposal updates shall be evaluated according to the evaluation criteria specified 23 herein. 24

4 NUMBER OF AWARDEES 25

The Government intends to award one contract per awardee, which may include multiple missions. 26

However, the Government reserves the right to make no award at all. 27

5 CORRECTION POTENTIAL OF PROPOSALS 28

The Government will consider, throughout the evaluation, the “correction potential” of proposals. 29

The judgment of such “correction potential” is within the sole discretion of the Government. If an 30 aspect of an Offeror's proposal does not meet the Government's requirements and is not considered 31 correctable, the Offeror may be eliminated from the competitive range. 32

6 Reserved. 33

6.1 RESERVED 34

7 EVALUATION OF PAST PERFORMANCE 35

7.1 FACTOR 1: PAST PERFORMANCE 36

The Past Performance evaluation results in Offerors receiving two past performance ratings IAW 37

Table 7-1 at the Factor level, one for the GPS III missions and one for the AFSPC missions. The 38

1 integrated past perfonnance rating for each mission will take into account the quality and relevancy 2 ratings for the effo1is. Offerors must receive a past perfo1mance rating of Acceptable to be eligible 3 for award of the coITesponding mission type (GPS III and AFSPC). Offerors with an Unacceptable 4 rating for GPS relevant past perfo1m ance will be ineligible for award for the GPS missions.

5 Offerors with an Unacceptable rating for AFSPC relevant past perfonnance will be ineligible for 6 award of the AFSPC missions.

7 7.2 RATINGS

8 The Past Perfo1mance Factor rating (one rating per mission type, GPS III and AFSPC) is described 9 in Table 7-1 below.

Table 7-1: Past Performance Evaluation Ratings

Rating Description

Based on the offeror 's perfonnance record, the Government

ACCEPTABLE

has a reasonable expectation that the Off eror will successfully perfo1m the required effo1i , or the Offeror 's perfo1mance record is unknown. (See note below)

Based on the offeror 's perfonnance record, the Government UNACCEPTABLE does not have a reasonable expectation that the Offeror will be able to successfully perfo1m the required effo1i .

Note: In the case of an Offeror without a record of relevant Past Perfo1mance or for whom info1mation on Past Perfonnance is not available or so sparse that no meaningful past perfo1mance rating can be reasonably assigned, the offeror may not be evaluated favorably or unfavorably on Past Perfo1m ance (see FAR 15.305 (a)(2)(iv)) . Therefore, the Offeror shall be dete1mined to have unknown (or Neutral) Past Perfo1mance. In the context of Acceptability/Unacceptability, Neutral shall be considered Acceptable.

7.3 EVALUATION PROCESS

12 The Past Perfo1mance evaluation considers each Offeror's demonstrated recent and relevant record 13 of perfo1m ance in providing launch services as well as contract execution. In conducting the Past 14 Perfonnance evaluation, the Government reserves the right to use both the info1m ation provided in 15 the Offeror 's Past Perfo1mance proposal volume and infonnation obtained from other sources 16 available to the Government, to include, but not limited to, the Past Perfo1mance Information 17 Retrieval System, Federal Awardee Perfo1mance and Integrity Infonnation System, Electronic 18 Subcontract Repo1i ing System, or other databases; interviews and questionnaires with Program 19 Managers, Contracting Officers and Fee Detennining Officials, the Defense Contract Management 20 Agency, and commercial sources.

21 7.4 RECENCY EVALUATION

22 An evaluation of the past perfonnance info1mation (PPI) will be made to dete1mine if it is recent.

23 To be recent, the effo1i must be ongoing or must have been perfo1med during the past 3 years from 24 the date of issuance of this solicitation. PPI that does not meet this definition will not be evaluated.

Evaluation Criteria

FA8811-17-R-0004

1 7.5 RELEVANCY EVALUATION

2 The Government will conduct an evaluation of all recent perfonnance info1mation obtained to 3 detennine whether the launch services and contract execution relate to either the GPS missions 4 and/or the AFSPC missions. A relevancy evaluation rating will be given for each recent effo1t based 5 on its similarity to the scope, magnitude, and complexity of both the GPS missions and the AFSPC 6 missions. There will be two relevancy evaluation ratings for each effort, one evaluation for 7 relevancy to the GPS missions and one evaluation for relevancy to the AFSPC missions. The 8 relevant effort info1mation may include data on effo1ts perfonned by other divisions or teaming 9 contractors, if such resom ces will be brought to bear on, or significantly influence, the perfonnance

10 of the proposed effo1t. In dete1mining the relevancy of effo1t perfonned under individual contracts, 11 the Government will only consider the specific effort or po1tion consistent with that proposed to be 12 completed by the prime, subcontractor, or teaming partner. PPI and info1mation obtained from other 13 som ces (ref. Attachment 6, paragraph 7.3) will be used to establish the relevancy of past 14 perfo1mance. The Government will use the following relevancy definitions in Table 7-2 when 15 assessing recent, relevant effo1ts.

Table 7-2: Past Performance Relevancy Ratings

Rating

RELEVANT

SOMEWHAT RELEVANT

Evaluation Criteria

Description GPS Relevancy: Past or ongoing effo1t that involved launch services for a DoD mission, with a similar launch vehicle system as proposed for the GPS missions, that has flown or will fly to an EELV reference orbit (see SPRD Table 1) or an orbit requiring equivalent perfo1mance.

AFSPC Relevancy: Past or ongoing effort that involved launch services for a DoD mission, with a similar launch vehicle system as proposed for the AFSPC missions, that has flown or will fly to an EELV reference orbit (see SPRD Table 1) or an orbit requiring equivalent perfonnance.

GPS Relevancy: Past or ongoing effo1t that involved launch services for a Government or commercial mission, with a similar launch vehicle system as proposed for the GPS missions.

AFSPC Relevancy: Past or ongoing effo1t that involved launch services for a Government or commercial mission, with a similar launch vehicle system as proposed for the AFSPC missions.

NOT RELEVANT

GPS Relevancy: Past or ongoing effo1t that involved launch services with a dissimilar launch vehicle system as proposed for the GPS missions.

AFSPC Relevancy: Past or ongoing effort that involved launch services with a dissimilar launch vehicle system as proposed for the AFSPC missions.

Notes: GPS =Global Positioning System, DoD = Depaitment of Defense, EELV = Evolved Expendable Launch Vehicle, SPRD = System Perfonnance Requirements Document, AFSPC = Air Force Space Command

7.6 PAST PERFORMANCE QUALITY ASSESSMENT

2 Lastly, the Government will assess the perfonnance quality of only recent and relevant/somewhat 3 relevant effo1ts. For each recent, relevant/somewhat relevant past perfo1mance effo1t, the quality of 4 the work perfo1med will be assessed for perfo1mance and schedule. Pursuant to DF ARS 5 215.305(a)(2), the evaluation will also consider the extent to which the Offeror's evaluated past 6 perfo1mance demonstrates compliance with FAR 52.219-8, Utilization of Small Business Concerns.

7 The quality assessment may result in positive or adverse findings. Adverse is defined as Past 8 Perfonnance Info1mation (PPI) that results in an unsatisfacto1y rating on any evaluation element or 9 any unfavorable comment received from sources without a fo1mal rating system (e.g. , past

10 perfo1mance questionnaires) . For adverse info1mation identified, the evaluation will consider the 11 number and severity of the adverse info1mation, mitigating circumstances, and the effectiveness of 12 coITective actions that have resulted in any sustained improvements. This will result in one (1) 13 quality assessment rating for each effo1t. The Government will use the following quality ratings in 14 Table 7-3 for the quality of recent and relevant effo1ts:

15 8 16 8.1

Table 7-3: Past Performance Quality Ratings

Rating Description

The Offeror's perfo1mance is substantially meeting (or substantially met) contract requirements to include, but not

SATISFACTORY

limited to, Contract Data Requirements List deliverables (as applicable) and schedule. For any issues encountered, the Offeror took effective coITective action with little to no Government or Customer involvement required.

The Offeror's perfonnance is not meeting (or did not meet) contract requirements. For issues encountered, coITective

UNSATISFACTORY action appeai·ed only mai·ginally effective, not effective, or not implemented. Considerable Government or Customer involvement was required.

EVALUATION OF PRICE FACTOR

FACTOR 4: PRICE

17 The Offeror's price for each mission (GPS III, AFSPC-8, and AFSPC-12) will be evaluated for

Evaluation Criteria

Reasonableness and Unbalanced pricing. In the evaluation, the Government may use data, external 1 to the Offeror’s proposal, such as, but not limited to, field pricing reports, industry information, 2

Government estimates, same or similar DoD contracts, and commercial data. The evaluation of 3 options will not obligate the Government to exercise such options. 4

The Offeror’s proposal for each mission will be evaluated for (1) accuracy in calculating the TPP 5 and (2) compliance with the instructions for calculating the TPP. 6

8.1.1 REASONABLENESS 7

Reasonableness of an Offeror’s proposed price will be evaluated using one or more price analysis 8 techniques, as identified in FAR 15.404-1. In accordance with FAR 15.403-1(b) and 15.403-3(a), 9 data other than certified cost or pricing data may be required to support a determination of price 10 reasonableness. If, after receipt of proposals, the PCO determines that there is insufficient data 11 available to determine price reasonableness, the Offeror shall be required to submit additional data 12 other than certified cost or pricing data. 13

8.1.2 UNBALANCED PRICING 14

The Government will evaluate the Offeror’s proposed prices for unbalanced pricing in accordance 15 with FAR 15.404-1(g). 16

8.1.3 COMPETITIVE ADVANTAGE FROM USE OF GOVERNMENT PROPERTY 17

If the Offeror proposes the use of Government Property (GP), the rental equivalency cost of the GP 18 will be incorporated into the TEP based on the unit acquisition cost of each item requested. As 19 defined by FAR 45.1, the Government may assess a different unit acquisition cost of any GP stated 20 by the Contractor if the Government’s evaluation supports another value. 21

8.1.4 TOTAL EVALUATED PRICE 22

For source selection evaluation purposes only, total evaluated price for each individual mission will 23 be determined by adding together the values within each mission-specific Table 10-6, 11-6, and 12-6 24 in Attachment 5. 25

9 RESERVED 26

10 ANNEX 1: GPS III (Three Missions) 27

The Offeror’s proposal will be evaluated utilizing the ratings defined in Table 10-1. 28

Only one technical proposal shall be provided to meet the RFP requirements for the 3 GPS III 29 missions (i.e., only one certified baseline configuration for the proposed launch vehicle system). 30

Technical Rating 31

The technical rating provides an assessment of the acceptability of the Offeror’s solution for meeting 32 the Government’s requirements. All Performance and Schedule sub-factors will receive one of the 33 ratings described in Table 10-1: Technical Acceptable/Unacceptable Ratings per DFARS 215.300. 34

The Performance and Schedule sub-factors will not be rolled up to receive an overall technical 35 rating. 36

Table 10-1: Technical Acceptable/Unacceptable Ratings

Rating Description

Acceptable Proposal meets the requirements of the solicitation.

Unacceptable Proposal does not meet the requirements of the solicitation.

1 The Government will evaluate the Offeror's proposal for compliance with the Perfo1m ance and 2 Schedule sub-factors as set fo1i h in paragraphs 10.1 and 10.2 below. An Unacceptable rating in any 3 sub-factor will result in an unawardable proposal for that specific mission. Any criteria evaluated as 4 "does not meet" will render the sub-factor Unacceptable and, therefore, the proposal will be 5 unawardable for that specific mission. For a sub-factor to be rated as Acceptable, all critieria for that 6 sub-factor must be evaluated as "meets." Only those proposals dete1mined to be Acceptable, either 7 initially or as a result of discussions if held, will be considered for award.

9 10.1 FACTOR2: PERFORMANCE

10 10.1.1 SUB-FACTOR 1: ORBITAL ACCURACY

11 10.1.1.1 Orbital Injection Accuracy: The five Injection Accuracy requirements (apogee altitude, 12 perigee altitude, inclination, right ascension of ascending node, and argument of perigee) are met 13 when the Offeror 's approach to meeting the GPS III 3-sigma injection accuracy (defined as 14 99.73% probability at 50% confidence) utilizing data from Table 10-1 and Table 10-2 of 15 Attachment 5, paragraph 10 .1.1 satisfies the requirements from Attachment 5, paragraph 10 .1.1, 16 Table 10-1: GPS III Orbital Injection Target and Accuracy Requirements.

17 10.1.1.2 Spin Rate: The requirement is met when the Offeror's approach to meeting the GPS III 18 Separation Parameter Spin Rate satisfies the requirements of Table 10-3 of Attachment 5, paragraph 19 10.1.1.2.

20 10.1.1.3 Pointing Accuracy of +Zsv axis: The requirement is met when the Offeror's approach to 21 meeting the GPS III Separation Parameter Pointing Accuracy of +Zsv axis satisfies the requirements 22 of Table 10-3 of Attachment 5, paragraph 10.1.1.2.

23 10.1.1.4 Transverse Angular Rate (Root Sum Square [RSS]) of the rates about the Xsv and Ysv axes 24 (deg/sec): The requirement is met when the Offeror 's approach to meeting the GPS III Separation 25 Parameter Transverse Angular Rate (Root Sum Square [RSS]) of the rates about the Xsv and Ysv 26 axes) (deg/sec) satisfies the requirements of Table 10-3 of Attachment 5, paragraph 10.1.1.2.

27 10.1.1.5 The requirement is met for each historical mission when orbital injection accuracy actual 28 flight data falls within the required 3-Sigma Requirement utilizing data from Table 10-4 of 29 Attachment 5, paragraph 10.1.1.3.

30 10.1.1.6 The requirement is met for each historical mission when orbital injection accuracy actual 31 flight data falls within the 3-Sigma Predictions utilizing data from Table 10-4 of Attachment 5, 32 paragraph 10.1.1.3.

33 10.1.2 SUB-FACTOR 2: MASS-TO-ORBIT

Evaluation Criteria

10.1.2.1 Mass-to Orbit: The requirement is met when the results of the Offeror's analysis, described 1 in Attachment 5, paragraph 10.1.2, demonstrates the capability to lift the total mass provided in 2

Attachment 5 Table 10-5 to the orbit target requirements in Attachment 5 Table 10-1 with a 3 performance margin greater than or equal to zero. The Offeror’s selected “Max Space Vehicle (SV) 4

Mass Used” shall be greater than or equal to the maximum SV mass indicated in the Mission 5

Requirements Annex (MRA) (ref. GPS III Mission Requirements Document [MRD] Section III.K 6

[Mass Properties {separated SV}]) for the Offeror’s selected integration type (vertical or horizontal) 7 with the appropriate adjustment to the SV mass for the Offeror’s selected perigee value. 8

10.1.2.2 Flight Performance Reserve: The requirement is met when the mass-to-orbit analysis 9 includes an upper stage flight performance reserve value calculated using the methodology 10 described in Attachment 5, paragraph 10.1.2.1. 11

10.1.2.3 Space and Missile Systems Center Launch System Directorate (SMC/LE) Reserve: The 12 requirement is met when the Offeror’s analysis includes an SMC/LE Reserve calculated using the 13 methodology described in Attachment 5, paragraph 10.1.2.1.b. 14

10.1.2.4 Upper Stage Disposal: The requirement is met when the mass-to-orbit analysis includes 15 compliance with Orbital Debris Mitigation Standard Practices (ODMSP) and a ≥ 90% probability of 16 success for completing the planned upper stage disposal, as described in Attachment 5, paragraph 17

10.2.2.2. 18

10.1.2.5 Flight Mission Profile: The requirement is met when the GPS III mission profile, as 19 specified in Attachment 5, paragraph 10.1.2.2, is supported by evidence provided for flight 20 demonstrated mission profile portions as well as engineering and risk analyses provided for 21 undemonstrated mission profile portions identifying unproven capabilities, risk analyses, and 22 mitigations as described in Attachment 5 paragraph 10.1.2.3. 23

10.1.2.6 Ground Trace and Impact: The requirement is met when the ODMSP expected casualty 24 requirement of less than one in 10,000 is satisfied and substantiated by the Offeror’s provided 25 analysis description and plots as identified in Attachment 5, paragraph 10.1.2.4. Nominal jettisoned 26 body impacts must occur over water and, as applicable, the upper stage reentry location shall be in a 27 broad ocean area. 28

10.1.2.7 Historical Data: The requirement is met when the historical flight data supports the 29 trajectory predictions or acceptable supporting rationale explains differences between flight results 30 and predictions as described in Attachment 5, paragraph 10.1.2.5. 31

10.1.3 SUB-FACTOR 3: LAUNCH OPERATIONS CONCEPT OF OPERATIONS 32

10.1.3.1 The requirement is met when the Offeror’s approach to launch operations flow from the 34 time the Government provides the GPS III SV to the Offeror as Government property for 35 encapsulation through liftoff, to include any contingency procedures or detailed plans proposed 36 under Attachment 5, paragraph 10.1.3.1, demonstrates compliance with the requirements of the 37

MRA (ref. Section XIV of the GPS III MRD) and is technically sound. 38

10.1.3.2 The requirement is met when the Offeror’s approach to GPS III SV processing and 39 encapsulation procedures proposed under Attachment 5, paragraph 10.1.3.2 demonstrates 1 compliance with the MRA (ref. Section XIV of the GPS III MRD), and is technically sound for the 2

Government-provided processing facility. 3

10.1.3.3 The requirement is met when the Offeror’s approach for contingency offload proposed 4 under Attachment 5, paragraph 10.1.3.3, demonstrates compliance with the requirements of the 5

MRA (ref. GPS III MRD Section XIV. H.) and is technically sound. 6

10.1.3.4 The requirement is met when the Offeror’s approach to execute the data requirements (as 7 described in Attachment 5, paragraph 10.1.3.4) is technically sound. 8

10.2 FACTOR 3: SCHEDULE 9

The criteria for this factor and sub-factors are written with the intent to eliminate proposals with 10 high schedule risk. Any criteria evaluated as “does not meet” will render the sub-factor 11

Unacceptable and, therefore, the proposal will be unawardable. Criteria will be evaluated as “does 12 not meet” if they do not satisfy the minimum requirements of the solicitation. The minimum 13 requirements of the schedule sub-factor criteria have been written with the intent to eliminate 14 proposals with high schedule risk. 15

10.2.1 SUB-FACTOR 1: INTEGRATED MASTER SCHEDULE 16

10.2.1.1 The requirement is met when the results of the Offeror’s schedule risk assessment (SRA) 17 demonstrate at least an 80% probability of meeting the Initial Launch Capability (ILC) or earlier, 18 and, Offeror’s IMS meets all five (5) of the criteria below: 19

10.2.1.2 The requirement is met when the Offeror’s IMS is constructed in accordance with (IAW) 20

Section 10.2.1 Attachment 5, Instructions to Offerors and is deemed credible and reasonable. 21

10.2.1.3 The requirement is met when the Offeror’s IMS is constructed IAW Section 10.2.1.4, 22

Attachment 5, Instructions to Offerors, and, the Offeror’s justifications for all components that fall 23 beyond the guideline thresholds from Section 10.2.1.4, Attachment 5, Instructions to Offerors, are 24 deemed credible and reasonable. 25

10.2.1.4 The requirement is met when the Offeror’s IMS reflects activities sufficient to support the 26

ILC IAW paragraph 10.2.1.2, Attachment 5, Instructions to Offerors. The ILC date for purposes of 27 evaluation is listed for the first of the three GPS III missions in paragraph 10.2.1.2.1, Attachment 5, 28

Instructions to Offerors. 29

10.2.1.5 The requirement is met when the Offeror’s IMS task durations are IAW paragraph 30

10.2.1.1.6 and 10.2.1.1.7, Attachment 5, Instructions to Offerors, and deemed credible based on the 31

Offeror’s historical performance data, rationale and lessons learned, and statements of assumptions. 32

10.2.1.6 The requirement is met when (1) the Offeror’s SRA is performed IAW paragraph 10.2.1.3 33

Attachment 5, Instructions to Offerors; (2) the three-point estimates are deemed credible and 34 reasonable based on the Offeror’s historical performance data, rationale and lessons learned, and 35 statements of assumptions; and (3) the Monte Carlo simulation-based SRA input data is verified to 36 match the Offeror’s proposed SRA. 37

1 10.2.2 SUB-FACTOR 2: RISK MITIGATION PLANS

3 The requirement is met when Offerer provides the FCIL associated with the launch vehicle system 4 proposed IA W CDRL B018, block 4.

6 10.2.2.1 The requirement is met when the Offerer's proposed schedule to complete all open 7 non-recmTing design validation work (NRDV) demonstrates the ability to close by L-12 months.

8 NRDV closme is defined in Attachment 5, paragraph 10.2.2.1 as requiring 4 months following 9 completion of final contractor NRDV effo1is for Government approval and verification/validation.

10 10.2.2.2 The requirement is met when (1) the Offerer's proposed risk mitigation plan(s) for 11 identified "Low-Medium" or higher risks IA W the Technical Issue Resolution Process (TIRP) 12 demonstrates the ability to suppo1i ILC, or Offeror provides written documentation on Government 13 risk acceptance; or (2) the Offerer's updated risk mitigation plans (if requested by the Government 14 during discussions) demonstrates the ability to suppo1i ILC, or Offerer provides written 15 documentation on Government risk acceptance.

16 10.2.2.3 Any risk mitigation or coITective action plans provided due to mishap or flight anomaly 17 IA W Attachment 5, paragraph 10.2.2.3 will be evaluated for impacts of the Offerer's ability to meet 18 perfo1mance and schedule requirements as stated in paragraphs 10.1 and 10.2.

19 10.2.2.4 The requirement is met when the Offerer demonstrates a credible and reasonable plan that 20 (1) meets all mission requirements; (2) does not hann the primaiy mission; (3) does not impact the 21 ILC; (4) demonstrates NRDV risk mitigation plans closure by L-12 months; and (5) does not 22 adversely affect the risk posture of the launch service.

23 11 ANNEX 2: AFSPC-8

24 The Offerer's proposal will be evaluated utilizing the ratings defined in Table 11-1.

25 Technical Rating

26 The technical rating provides an assessment of the acceptability of the Offerer's solution for meeting 27 the Government's requirements . All Performance and Schedule sub-factors will receive one of the 28 ratings described in Table 11-1: Technical Acceptable/Unacceptable Ratings per DFARS 215.300.

29 The Performance and Schedule sub-factors will not be rolled up to receive an overall technical 30 rating.

Table 11-1: Technical Acceptable/Unacceptable Ratings

Rating Description

Acceptable Proposal meets the requirements of the solicitation.

Unacceptable Proposal does not meet the requirements of the solicitation.

32 The Government will evaluate the Offerer's proposal for compliance with the Perfo1mance and

Evaluation Criteria

Schedule sub-factors as set forth in paragraphs 11.1 and 11.2 below. An Unacceptable rating in any 1 sub-factor will result in an unawardable proposal for that specific mission. Any criteria evaluated as 2

“does not meet” will render the sub-factor Unacceptable and, therefore, the proposal will be 3 unawardable for that specific mission. For a sub-factor to be rated as Acceptable, all critieria for that 4 sub-factor must be evaluated as “meets.” Only those proposals determined to be Acceptable, either 5 initially or as a result of discussions if held, will be considered for award. 6

11.1 FACTOR 3: PERFORMANCE 7

11.1.1 SUB-FACTOR 1: Orbital Accuracy 8

11.1.1.1 Orbital Injection Accuracy: The four Injection Accuracy requirements (apogee altitude, 9 perigee altitude, deployment longitude, and inclination) are met when the Offeror’s approach to 10 meeting the AFSPC-8 3-sigma injection accuracy (defined as 99.73% probability at 50% 11 confidence) utilizing data from Table 11-1 and Table 11-2 of Attachment 5, paragraph 11.1.1 12 satisfies the requirements from Attachment 5, paragraph 11.1.1, Table 11-1: AFSPC-8 Orbit 13

Injection Target and Accuracy Requirements. 14

11.1.1.2 SV Rotational Rate at Separation: The requirement is met when the Offeror’s approach to 15 meeting the AFSPC-8 SV Rotational Rate (3-sigma) in X-axis and Y-axis and SV Rotational Rate 16

(3-sigma) in Z-axis in all axes satisfies the requirements of Table 11-3 of Attachment 5, paragraph 17

11.1.1.2. 18

11.1.1.3 SV Pointing Attitude at Separation: The requirement is met when the Offeror’s approach to 19 meeting the AFSPC-8 SV Attitude +XLV, utilizing data from Table 11-3 of Attachment 5, paragraph 20

11.1.1.2, satisfies the requirements of Table 11-3 of Attachment 5, paragraph 11.1.1.2 (3 sigma). 21

11.1.1.4 RESERVED 22

11.1.1.5 The requirement is met for each historical mission when orbital injection accuracy actual 23 flight data falls within the required 3-Sigma orbit injection dispersions utilizing data from 24

Table 11-4 of Attachment 5, paragraph 11.1.1.3. 25

11.1.1.6 The requirement is met for each historical mission when orbital injection accuracy actual 26 flight data falls within the 3-Sigma predictions utilizing data from Table 11-4 of Attachment 5, 27 paragraph 11.1.1.3. 28

11.1.1.7 Undemonstrated Geosynchronous Earth Orbit (GEO) Direct Injection on the ascending 29 node injection accuracy at SV Separation: The requirement is met when the AFSPC-8 mission 30 injection accuracy specified by the Offeror for Attachment 5 Table 11-1 is supported by engineering 31 and risk analyses provided by the Offeror that identify unproven capabilities and risks associated 32 with undemonstrated GEO direct orbit insertion accuracy and corresponding mitigation plans as 33 specified in Attachment 5, paragraph 11.1.1.1. 34

11.1.2 SUB-FACTOR 2: Mass-to-Orbit 35

11.1.2.1 Mass-to Orbit: The requirement is met when the results of the Offeror's analysis, described 36 in Attachment 5, paragraph 11.1.2, demonstrates the capability to lift the total mass provided in 37

Attachment 5 Table 11-5 to the orbit target requirements in Attachment 5 Table 11-1 with a 1 performance margin greater than or equal to zero. 2

11.1.2.2 Flight Performance Reserve: The requirement is met when the Offeror’s analysis includes 3 an upper stage flight performance reserve value calculated using the methodology described in 4

Attachment 5, paragraph 11.1.2.1. 5

11.1.2.3 SMC/LE Reserve: The requirement is met when the Offeror’s analysis includes an 6

SMC/LE Reserve calculated using the methodology described in Attachment 5, paragraph 7

11.1.2.1.b. 8

11.1.2.4 Flight Mission Profile: The requirement is met when the AFSPC-8 mission profile, as 9 specified in Attachment 5, paragraph 11.1.2.2, is supported by evidence provided for flight 10 demonstrated mission profile portions as well as engineering and risk analyses provided for 11 undemonstrated mission profile portions identifying unproven capabilities, risk analyses, and 12 mitigations as described in Attachment 5, paragraph 11.1.2.3. 13

11.1.2.5 RESERVED 14

11.1.2.6 Historical Data: The requirement is met when the historical flight data supports the 15 trajectory predictions, or acceptable supporting rationale explains differences between flight results 16 and predictions, as described in Attachment 5, paragraph 11.1.2.5. 17

11.1.3 SUB-FACTOR 3: Launch Operations Concept of Operations 18

11.1.3.1 The requirement is met when (1) the Offeror’s approach to launch operations flow from the 19 time the Government provides the Space Vehicle Launch Stack (SVLS) to the Offeror as 20

Government property for encapsulation through liftoff, to include any contingency procedures or 21 detailed plans proposed under Attachment 5, paragraph 11.1.3.1, demonstrates compliance with the 22 requirements of the MRA (ref. sections 3.5.2 and 3.5.3 of the AFSPC-8 MRD), and is technically 23 sound; and (2) the Offeror’s approach to accomplish the vertical integration requirements of the 24

SVLS demonstrates compliance with the requirements of the MRA (ref. sections 3.5.2.2.k and 3.5.4 25 of the AFSPC-8 MRD). 26

11.1.3.2 The requirement is met when the Offeror’s approach to SVLS processing and encapsulation 27 procedures proposed under Attachment 5, paragraph 11.1.3.2 demonstrates compliance with the 28

MRA (ref. Section 3.5.2 of the AFSPC-8 MRD) and is technically sound for the 29

Government-provided processing facility. 30

11.1.3.3 The requirement is met when the Offeror’s approach for contingency offload proposed 31 under Attachment 5, paragraph 11.1.3.3, demonstrates compliance with the requirements of the 32

MRA (ref. Section 3.5.3 of the AFSPC-8 MRD) and is technically sound. 33

11.1.3.4 The requirement is met when the Offeror provides a plan that (1) describes managing and 34 processing classified payloads at the Special Access Program/Special Access Required level; (2) 35 includes detailed descriptions with rationale; (3) is demonstrated from previous efforts or, if never 36 demonstrated, provides evidence-based rationale; and (4) is technically sound. 37

11.1.3.5 The requirement is met when the Offeror’s approach to execute the data requirements (as 1 described in Attachment 5, paragraph 11.1.3.5) is technically sound. 2

11.1.4 SUB-FACTOR 4: Acoustic Environment and Shock Environment 3

11.1.4.1 The requirement is met when the Offeror provides a plan that (1) demonstrates compliance 4 with AFSPC-8’s Acoustic Requirements (ref. Section 3.3.4.1 of the AFSPC-8 MRD) and (2) is 5 technically sound. 6

11.1.4.2 The requirement is met when the Offeror provides a plan that (1) demonstrates compliance 7 with AFSPC-8’s Shock Requirements (ref. Section 3.3.4.2 of the AFSPC-8 MRD) and (2) is 8 technically sound. 9

11.2 FACTOR 3: SCHEDULE 10

The criteria for this factor and sub-factors are written with the intent to eliminate proposals with 11 high schedule risk. Any criteria evaluated as “does not meet” will render the sub-factor 12

Unacceptable and, therefore, the proposal will be unawardable. Criteria will be evaluated as “does 13 not meet” if they do not satisfy the minimum requirements of the solicitation. The minimum 14 requirements of the schedule sub-factor criteria have been written with the intent to eliminate 15 proposals with high schedule risk. 16

11.2.1 SUB-FACTOR 1: INTEGRATED MASTER SCHEDULE 17

11.2.1.1 The requirement is met when the results of the Offeror’s SRA demonstrate at least an 90% 18 probability of meeting the ILC or earlier, and Offeror’s IMS meets all five (5) of the criteria below: 19

11.2.1.2 The requirement is met when the Offeror’s IMS is constructed IAW Section 11.2.1.1.1 20 through 11.2.1.1.5, Attachment 5, Instructions to Offerors and is deemed credible and reasonable. 21

11.2.1.3 The requirement is met when the Offeror’s IMS is constructed IAW Section 11.2.1.4, 22

Attachment 5, Instructions to Offerors, and the Offeror’s justifications for all components that fall 23 beyond the guideline thresholds from Section 11.2.1.4, Attachment 5, Instructions to Offerors, are 24 deemed credible and reasonable. 25

11.2.1.4 The requirement is met when the Offeror’s IMS reflects activities sufficient to support the 26

ILC IAW paragraph 11.2.1.2, Attachment 5, Instructions to Offerors. The ILC for purposes of 27 evaluation is provided in paragraph 11.2.1.2.1, Attachment 5, Instructions to Offerors. 28

11.2.1.5 The requirement is met when the Offeror’s IMS task durations are IAW paragraph 29

11.2.1.1.6 and 11.2.1.1.7, Attachment 5, Instructions to Offerors, and deemed credible based on the 30

Offeror’s historical performance data, rationale and lessons learned, and statements of assumptions. 31

11.2.1.6 The requirement is met when (1) the Offeror’s SRA is performed IAW paragraph 10.2.1.3 32

Attachment 5, Instructions to Offerors; (2) the three-point estimates are deemed credible and 33 reasonable based on the Offeror’s historical performance data, rationale and lessons learned, and 34 statements of assumptions; and (3) the Monte Carlo simulation-based SRA input data is verified to 35 match the Offeror’s proposed SRA. 36

1 11.2.2 SUB-FACTOR 2: RISK MITIGATION PLANS

2 The requirement is met when Offerer provides the FCIL associated with the launch vehicle system 3 proposed IA W CDRL B018, block 4.

5 11 .2.2.1 The requirement is met when the Offerer's proposed schedule to complete all open 6 non-recmTing design validation work demonstrates the ability to close by L-12 months. NRDV 7 closme is defined in Attachment 5, paragraph 11 .2.2.1 as requiring 4 months following completion 8 of final contractor NRDV effo1is for Government approval and verification/validation.

9 11.2.2.2 The requirement is met when (1) the Offerer's proposed risk mitigation plan(s) for 10 identified "Low-Medium" or higher risks IA W the Technical Issue Resolution Process (TIRP) 11 demonstrates the ability to suppo1i ILC, or Offeror provides written documentation on Government 12 risk acceptance; or (2) the Offerer's updated risk mitigation plans (ifrequested by the Government 13 during discussions) demonstrates the ability to suppo1i ILC, or Offerer provides written 14 documentation on Government risk acceptance.

15 11 .2.2.3 Any risk mitigation or coITective action plans provided due to mishap or flight anomaly 16 IA W Attachment 5, paragraph 11.2.2.3 will be evaluated for impacts of the Offerer's ability to meet 17 perfo1mance and schedule requirements as stated in paragraphs 11 .1 and 11.2.

18 11 .2.2.4 The requirement is met when the Offerer demonstrates a credible and reasonable plan that 19 (1) meets all mission requirements; (2) does not hann the primaiy mission; (3) does not impact the 20 ILC; ( 4) demonstrates NRDV risk mitigation plans closure by L-12 months; and (5) does not 21 adversely affect the risk posture of the launch service.

22 12 ANNEX 3: AFSPC-12

23 The Offerer's proposal will be evaluated utilizing the ratings defined in Table 12-1 .

24 Technical Rating

25 The technical rating provides an assessment of the acceptability of the Offerer's solution for meeting 26 the Government's requirements. All Performance and Schedule sub-factors will receive one of the 27 ratings described in Table 12-1 : Technical Acceptable/Unacceptable Ratings per DFARS 215.300.

28 The Performance and Schedule sub-factors will not be rolled up to receive an overall technical 29 t ra mg.

Table 12-1: Technical Acceptable/Unacceptable Ratings

Rating Description

Acceptable Proposal meets the requirements of the solicitation.

Unacceptable Proposal does not meet the requirements of the solicitation.

30 The Government will evaluate the Offerer's proposal for compliance with the Perfo1mance and 31 Schedule sub-factors as set fo1ih in pai·agraphs 12.1 and 12.2 below. An Unacceptable rating in any

Evaluation Criteria sub-factor will result in an unawardable proposal for that specific mission. Any criteria evaluated as 1

“does not meet” will render the sub-factor Unacceptable and, therefore, the proposal will be 2 unawardable for that specific mission. For a sub-factor to be rated as Acceptable, all critieria for that 3 sub-factor must be evaluated as “meets.” Only those proposals determined to be Acceptable, either 4 initially or as a result of discussions if held, will be considered for award. 5

12.1 FACTOR 2: PERFORMANCE 6

12.1.1 SUB-FACTOR 1: Orbital Accuracy 7

12.1.1.1 Orbital Injection Accuracy: The three Injection Accuracy requirements (apogee altitude, 8 perigee altitude, and inclination) are met when the Offeror’s approach to meeting the AFSPC-12 9

3-sigma injection accuracy (defined as 99.73% probability at 50% confidence) utilizing data from 10

Table 12-1 and Table 12-2 of Attachment 5, paragraph 12.1.1 satisfies the requirements from 11

Attachment 5, paragraph 12.1.1, Table 12-1: AFSPC-12 Orbit Injection Target and Accuracy 12

Requirements. 13

12.1.1.2 SV Rotational Rate at Separation: The requirement is met when the Offeror’s approach to 14 meeting the AFSPC-12 Rotational Rate in all axes, for both Bluegill and Wide Field of View 15

(WFOV) SVs, satisfies the requirements in Table 12-3 of Attachment 5, paragraph 12.1.1.2. 16

12.1.1.3 SV Pointing Attitude at Separation: The requirement is met when the Offeror’s approach to 17 meeting the Bluegill SV Pointing Attitude at Initiation of the Separation Command at separation 18 satisfies the requirements of Table 12-2 of Attachment 5, paragraph 12.1.1.2. 19

12.1.1.4 RESERVED 20

12.1.1.5 The requirement is met for each historical mission when orbital injection accuracy actual 21 flight data falls within the required 3-Sigma orbit injection dispersions utilizing data from 22

Table 12-4 of Attachment 5, paragraph 12.1.1.3. 23

12.1.1.6 The requirement is met for each historical mission when orbital injection accuracy actual 24 flight data falls within the 3-Sigma predictions utilizing data from Table 12-4 of Attachment 5, 25 paragraph 12.1.1.3. 26

12.1.1.7 Undemonstrated GEO Direct Injection Accuracy at SV Separation: The requirement is met 27 when the AFSPC-12 mission injection accuracy specified by the Offeror for Attachment 5 28

Table 12-1 is supported by engineering and risk analyses provided by the Offeror that identify 29 unproven capabilities and risks associated with undemonstrated GEO direct orbit insertion accuracy 30 and corresponding mitigation plans as specified in Attachment 5, paragraph 12.1.1.1. 31

12.1.2 SUB-FACTOR 2: Mass-to-Orbit 32

12.1.2.1 Mass-to Orbit: The requirement is met when the results of the Offeror's analysis, 33 described in Attachment 5, paragraph 12.1.2 demonstrates the capability to lift the total mass 34 provided in Attachment 5 Table 12-5 to the orbit target requirements in Attachment 5 Table 12-1 35 with a performance margin greater than or equal to zero. 36

12.1.2.2 Flight Performance Reserve: The requirement is met when the Offeror’s analysis includes 37 an upper stage flight performance reserve value calculated using the methodology described in 38

Attachment 5, paragraph 12.1.2.1. 39

12.1.2.3 SMC/LE Reserve: The requirement is met when the Offeror’s analysis includes an 1

SMC/LE Reserve calculated using the methodology described in Attachment 5, paragraph 2

12.1.2.1.b. 3

12.1.2.4 Flight Mission Profile: The requirement is met when the AFSPC-12 mission profile, as 4 specified in Attachment 5, paragraph 12.1.2.2, is supported by evidence provided for flight 5 demonstrated mission profile portions as well as engineering and risk analyses provided for 6 undemonstrated mission profile portions identifying unproven capabilities, risk analyses, and 7 mitigations as described in Attachment 5, paragraph 12.1.2.3. 8

12.1.2.5 RESERVED 9

12.1.2.6 Historical Data: The requirement is met when the historical flight data supports the 10 trajectory predictions or acceptable supporting rationale explains differences between flight results 11 and predictions, as described in Attachment 5, paragraph 12.1.2.5. 12

12.1.3 SUB-FACTOR 3: Launch Operations Concept of Operations and Multi-13

Manifest/Integration Management 14

12.1.3.1 The requirement is met when the Offeror’s approach to launch operations flow from the 15 time the Government provides the Bluegill and WFOV SVs to the Offeror as Government property 16 for encapsulation through liftoff, to include any contingency procedures or detailed plans proposed 17 under Attachment 5, paragraph 12.1.3.1, demonstrates compliance with the requirements of the 18

MRA (ref. sections 4.3 of the Bluegill Interface Requirements Document and sections 2.3 and 2.5 of 19 the WFOV Technical Requirements Document [TRD]), and is technically sound. 20

12.1.3.2 The requirement is met when (1) the Offeror provides a plan that integrates Bluegill and 21

WFOV into an integrated payload stack and is then integrated into an encapsulated assembly (EA) 22 as described in Attachment 5, paragraph 12.1.3.2; (2) the Offeror’s…

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 .