08_Attachment_6_Evaluation_Criteria.pdf
PDF 1 MB Posted
- Solicitation number
- FA8811-17-R-0004
About this file
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 19
Acquisition 20 for GPS III, AFSPC-8, AFSPC-12, and AFSPS-52 Launch 21
Services 22
FA8811-17-R-0004 27
Attachment 6 28
Evaluation Criteria 29
03 May 2017 33
RESPONSIBILITY 1
The Procuring Contracting Officer (PCO) will make a responsbility determination after the 2 evaluation of proposals to determine whether an Offeror is eligible for contract award. In addition to 3 the general responsibility matters provided under Federal Acquisition Regulation (FAR) 9.104-1, the 4
PCO will consider directly relevant early integration studies, anomaly findings, and the Space and 5
Missile Systems Center (SMC) Commander's certification of the Offeror's proposed launch system 6 as a certified Evolved Expendable Launch Vehicle (EELV) launch system to determine adequate 7 technical skill, among other standards listed in FAR 9.104-1, to launch National Security Space 8
(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 informs 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. 43
Design and Mission Reliability—Design reliability is the product of structure and mechanical 1 reliability; propulsion and thrust vector control reliability; avionics and guidance reliability and 2 electrical power subsystem reliability along with the reliability (probability of success) for each 3 staging event. Mission reliability is composed of two components: (1) vehicle design and (2) launch 4 processing. This takes into account the vehicle design reliabilities and the probability that ground 5 operations (including infrastructure) or workmanship will induce a fault which can result in a 6 mission failure. 7
Compliance with Standard Interface Specification—Defines the standard interface between the 8 payload and the launch system. The interface includes mechanical, electrical and avionics interfaces, 9 fluid interfaces and services, thermal environments, contamination control, acceleration load factors, 10 dynamic environments, ground and facilities processing. 11
The SMC Commander is responsible for determining launch system certification. Once certification 12 is determined, the SMC Commander issues a formal EELV Certification Letter detailing any 13 limitations against the certification and conditions for maintaining the certification, including 14 verification of the acceptability of any changes to the vehicle or ground systems, maintenance of the 15 technical data underpinning the certification, and continued process discipline. Launch system 16 certification can be withdrawn at any time by the SMC Commander if a determination is made that 17 requirements upon which certification is based are no longer being satisfied. 18
Launch system certification is a key element to gaining insight into the rigorous technical 19 capabilities and processes that demonstrate the ability to launch NSS missions and contributes to the 20 overall NSS flight worthiness process. Flight worthiness certification for a specific NSS mission is 21 determined prior to launch through the SMC Flight Readiness Review process by the SMC 22
Commander. 23
The PCO will make a responsibility determination prior to contract award. 24
1 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 will need to be deemed responsible in accordance with FAR 9.1, 32 as supplemented by DFARS and AFFARS, and its proposal 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 multiple award decisions: individual award decisions for (1) the 40 three GPS III missions (winner-take-all), (2) AFSPC-8, (3) AFSPC-12, and (4) AFSPC-52. The 41
Governement reserves the right to make all award decisions at once or rolling award decisions. 42
Should an Offeror be awarded multiple missions, the missions shall be awarded and executed on one 1 contract. Four separate award decisions shall be made to the Offeror(s) whose proposal is 2 determined to be acceptable for all subfactors and factors with the lowest Total Evaluated Price 3
(TEP). All factors (small business, past performance, performance, schedule, and price) and 4 subfactors are of equal importance. The Total Proposed Price (TPP) will be the price put on 5 contract. 6
2 GENERAL INSTRUCTIONS 7
The Government will evaluate against all information the Offeror provides in accordance with 8
Attachment 5 Instructions to Offerors with the exception of the executive summary. The Offeror 9 shall submit proposals for all launch services to be considered responsive to this RFP. If the Offeror 10 determines they are not technically capable to meet certain requirements of a specific launch service, 11 the Offeror is not required to submit a proposal for the specific launch service. However, the 12
Offeror shall provide a letter detailing the reasons for not being able to meet the requirements. 13
Submission of insufficient information may result in the Offeror being unresponsive, and therefore 14 the proposal may be determined to be unacceptable and ineligible for award. If during the evaluation 15 period, it is determined to be in the best interest of the Government to hold discussions, Offeror 16 responses to Evaluation Notices and the Final Proposal Revision (FPR) will be evaluated. If 17 discussions occur, the Government reserves the right to request proposal updates based on directly 18 relevant early integration studies or anomaly resolution findings, and any proposal updates shall be 19 evaluated according to the evaluation criteria specified herein. If the Offeror’s proposal has been 20 evaluated as acceptable at the time discussions are closed, any changes or exceptions in the FPR are 21 subject to evaluation and may introduce risk that the Offeror’s proposal may be determined 22 unacceptable and ineligible for award. 23
3 NUMBER OF AWARDEES 24
The Government intends to award one contract per awardee, which may include multiple missions. 25
However, the Government reserves the right to make no award at all. 26
4 CORRECTION POTENTIAL OF PROPOSALS 27
The Government will consider, throughout the evaluation, the “correction potential” of proposals. 28
The judgment of such “correction potential” is within the sole discretion of the Government. If an 29 aspect of an Offeror's proposal does not meet the Government's requirements and is not considered 30 correctable, the Offeror may be eliminated from the competitive range. 31
5 EVALUATION OF SMALL BUSINESS 32
5.1 FACTOR 1: SMALL BUSINESS PARTICIPATION 33
6.1.1 RATINGS 34
The Small Business Participation Factor will receive a rating of “Acceptable” or “Unacceptable” as 35 described in the DoD Source Selection Procedures, Table 6, Small Business Rating Method. The 36
Small Business Participation Commitment Document (SBPCD) focuses on the Offeror’s 37 performance in the utilization of small business concerns and its evaluation will be included within 38 the rating of the Small Business Participation Factor. 39
Note: In the case of an Offeror without a record of relevant Past Performance or for whom information on Past Performance is not available or so sparse that no meaningful past performance rating can be reasonably assigned, the offeror may not be evaluated favorably or unfavorably on Past Performance (see FAR 15.305 (a)(2)(iv)). Therefore, the Offeror shall be determined to have unknown (or “neutral”) Past Performance. In the context of
Acceptability/Unacceptability, “Neutral” shall be considered “Acceptable.”
7.3 EVALUATION PROCESS 2
The Past Performance evaluation considers each Offeror’s demonstrated recent and relevant record 3 of performance in providing launch services as well as contract execution. In conducting the Past 4
Performance evaluation, the Government reserves the right to use both the information provided in 5 the Offeror’s Past Performance proposal volume and information obtained from other sources 6 available to the Government, to include, but not limited to, the Past Performance Information (PPI) 7
Retrieval System, Federal Awardee Performance and Integrity Information System, Electronic 8
Subcontract Reporting System, or other databases; interviews and questionnaires with Program 9
Managers, Contracting Officers and Fee Determining Officials, the Defense Contract Management 10
Agency, and commercial sources. 11
7.4 RECENCY EVALUATION 13
An evaluation of the PPI will be made to determine if it is recent. To be recent, the effort must be 14 ongoing or must have been performed during the past 3 years from the date of issuance of this 15 solicitation. PPI that does not meet this definition will not be evaluated. 16
7.5 RELEVANCY EVALUATION 18
The Government will conduct an evaluation of all recent performance information obtained to 19 determine whether the launch services and contract execution relate to either the GPS missions and 20 the AFSPC missions. A relevancy evaluation rating will be given for each recent effort that is 21 similar to the scope, magnitude, and complexity of either the GPS missions or the AFSPC missions. 22
There will be two relevancy evaluation ratings, one for the GPS relevant missions and one for the 23
AFSPC relevant missions. The relevant effort information may include data on efforts performed by 24 other divisions or teaming contractors, if such resources will be brought to bear on, or significantly 25 influence the performance of the proposed effort. In determining the relevancy of effort performed 26 under individual contracts, the Government will only consider the specific effort or portion 27 consistent with that proposed to be completed by the prime, subcontractor, or teaming partner. PPI 28 and information obtained from other sources will be used to establish the relevancy of past 29 performance. The Offeror shall provide at least one recent, relevant contract as it relates to the GPS 30 missions and one recent, relevant contract as it relates to the AFSPC missions. The Government will 31 use the following relevancy definitions in Table 7-2 when assessing recent, relevant contracts. 32
Separation Parameter accuracy utilizing data from Table 10-3 of Attachment 5, paragraph 10.1.1.2 1 satisfies a Spin Rate requirement of +0.6 deg/sec and an accuracy of ± 0.3 deg/sec. 2
10.1.1.3 Pointing Accuracy of +Zsv axis: The requirement is met when the Offeror’s approach to 3 meeting the GPS III Separation Parameter accuracy utilizing data from Table 10-3 of Attachment 5, 4 paragraph 10.1.1.2 satisfies a Pointing Accuracy of +Zsv axis requirement of Negative Ecliptic 5
Normal and an accuracy of ≤ 5 deg. 6
10.1.1.4 Transverse Angular Rate (Root Sum Square [RSS]) of the rates about the Xsv and Ysv axes 7
(deg/sec): The requirement is met when the Offeror’s approach to meeting the GPS III Separation 8
Parameter accuracy utilizing data from Table 10-3 of Attachment 5, paragraph 10.1.1.2 satisfies the 9
Transverse Angular Rate requirement of 0 deg/sec and an accuracy of ≤ 1.8 deg/sec. 10
10.1.1.5 The requirement is met for each historical mission when orbital injection accuracy actual 11 flight data falls within the required 3-Sigma orbit injection dispersions utilizing data from Table 12
10-4 of Attachment 5, paragraph 10.1.1.3. 13
10.1.1.6 The requirement is met for each historical mission when orbital injection accuracy actual 14 flight data falls within the 3-Sigma predictions utilizing data from Table 10-4 of Attachment 5, 15 paragraph 10.1.1.3. 16
10.1.2 SUBFACTOR 2: MASS-TO-ORBIT 18
10.1.2.1 Mass-to Orbit: The requirement is met when the results of the Offeror's analysis, described 19 in Attachment 5, paragraph 10.1.2, demonstrates the capability to lift the total mass provided in 20
Attachment 5 Table 10-5 to the orbit target requirements in Attachment 5 Table 10-1 with a 21 performance margin greater than or equal to zero. The Offeror’s selected “Max SV Mass Used” 22 shall be greater than or equal to the maximum SV mass indicated in the MRA (ref. GPS III MRD 23 section III.K (Mass Properties [separated SV])) for the Offeror’s selected integration type (vertical 24 or horizontal) with the appropriate adjustment to the SV mass for the Offeror’s selected perigee 25 value. 26
10.1.2.2 Flight Performance Reserve: The requirement is met when the mass-to-orbit analysis 27 includes an upper stage flight performance reserve value calculated using the methodology 28 described in Attachment 5, paragraph 10.1.2.1. 29
10.1.2.3 Upper Stage Disposal: The requirement is met when the mass-to-orbit analysis includes 30 compliance with Orbital Debris Mitigation Standard Practices (ODMSP) and a ≥ 90% probability of 31 success for completing the planned upper stage disposal, as described in Attachment 5, paragraph 32
10.2.2.2. 33
10.1.2.4 Flight Mission Profile: The requirement is met when the GPS III mission profile, as 34 specified in Attachment 5, paragraph 10.1.2.2, is supported by evidence provided for flight 35 demonstrated mission profile portions as well as engineering and risk analyses provided for 36 undemonstrated mission profile portions identifying unproven capabilities, risk analyses, and 37 mitigations as described in Attachment 5 paragraph 10.1.2.3. 38
10.1.2.5 Ground Trace and Impact: The requirement is met when the ODMSP expected casualty 39 requirement of less than one in 10,000 is satisfied and substantiated by the Offeror’s provided 1 analysis description and plots as identified in Attachment 5, paragraph 10.1.2.4. Nominal jettisoned 2 body impacts must occur over water and, as applicable, the upper stage reentry location shall be in a 3 broad ocean area. 4
10.1.2.6 Historical Data: The requirement is met when the historical flight data supports the 5 trajectory predictions or acceptable supporting rationale to explain differences between flight results 6 and predictions as described in Attachment 5, paragraph 10.1.2.5. 7
10.1.3 SUB-FACTOR 3: Launch Operations Concept Of Operations 8
10.1.3.1 The requirement is met when the Offeror’s approach to launch operations flow from the 9 time the Government provides the GPS III SV to the Offeror as government property for 10 encapsulation through liftoff, to include any contingency procedures or detailed plans proposed 11 under Attachment 5, paragraph 10.1.3.1, demonstrates compliance with the requirements of the 12
MRA (ref. section XIV of the GPS III MRD) and is technically sound. 13
10.1.3.2 The requirement is met when the Offeror’s approach to GPS III SV processing and 14 encapsulation procedures proposed under Attachment 5, paragraph 10.1.3.2 demonstrates 15 compliance with the MRA (ref. section XIV of the GPS III MRD), and is technically sound for the 16 processing facility the launch service provider proposes to use for an East Coast launch. 17
10.1.3.3 The requirement is met when the Offeror’s approach for contingency offload proposed 18 under Attachment 5, paragraph 10.1.3.3, demonstrates compliance with the requirements of the 19
MRA (ref. GPS III MRD section XIV. H.) and is technically sound. 20
10.1.3.4 The requirement is met when the Offeror’s approach to execute the data requirements (as 21 described in Attachment 5, paragraph 10.1.3.4) is technically sound. 22
10.2 FACTOR 4: SCHEDULE 23
An offeror shall meet all schedule criteria for an acceptable schedule. The Government believes a 24 schedule that does not meet all schedule criteria is a high risk schedule. While there is not a separate 25 risk evaluation, high-risk schedules are not awardable. A high-risk schedule is an IMS that is likely 26 to cause significant disruption of schedule and is unlikely to overcome any difficulties even with 27 special contractor emphasis and close Government monitoring. The criteria for this factor and sub-28 factors are written with the intent to eliminate proposals with high schedule risk. Any criteria 29 evaluated as “does not meet” will render the subfactor unacceptable, and therefore the proposal will 30 be unawardable. Criteria will be evaluated as “does not meet” if they do not satisfy the minimum 31 requirements of the solicitation. The minimum requirements of the schedule sub-factor criteria have 32 been written with the intent to eliminate proposals with high schedule risk. The government 33 considers a high-risk schedule to be unacceptable. An Offeror’s schedule is considered 34 unacceptable if it is unable to meet the requirement specified in sub-factor 1, Paragraph 10.2.1. 35
Additionally, an unacceptable rating in any of the following schedule criteria constitutes a high-risk 36
IMS, and the Offeror’s proposal will be considered unawardable. 37
10.2.1 SUB-FACTOR 1: INTEGRATED MASTER SCHEDULE (IMS) 38
10.2.1.1 The requirement is met when the results of the Offeror’s schedule risk assessment (SRA) 1 demonstrate at least an 90% probability of meeting the Initial Launch Capability (ILC) or earlier; 2 and, Offeror’s IMS meets all five (5) of the criteria below: 3
10.2.1.2 The requirement is met when the Offeror’s IMS is constructed IAW section 10.2.1 4
Attachment 5, Instructions to Offerors and is deemed credible and reasonable. 5
10.2.1.3 The requirement is met when the Offeror’s IMS is constructed IAW section 10.2.1.4, 6
Attachment 5, Instructions to Offerors; and, the Offeror’s justifications for all components that fall 7 beyond the guideline thresholds from section 10.2.1.4, Attachment 5, Instructions to Offerors, are 8 deemed credible and reasonable. 9
10.2.1.4 The requirement is met when the Offeror’s IMS reflects activities sufficient to support the 10
ILC IAW paragraph 10.2.1.2, Attachment 5, Instructions to Offerors. The ILC date for purposes of 11 evaluation is listed for the first of the three GPS III missions in paragraph 10.2.1.2.1, Attachment 5, 12
Instructions to Offerors. 13
The requirement is met when the Offeror’s IMS task durations are IAW paragraph 10.2.1.1.6 and 14
10.2.1.1.7, Attachment 5, Instructions to Offerors, and deemed credible based on the Offeror’s 15 historical performance data, rationale and lessons learned, and statements of assumptions. 16
10.2.1.5 The requirement is met when the Offeror’s SRA is performed IAW paragraph 10.2.1.3 17
Attachment 5, Instructions to Offerors, and the three-point estimates are deemed credible and 18 reasonable based on the Offeror’s historical performance data, rationale and lessons learned, and 19 statements of assumptions. 20
10.2.2 SUB-FACTOR 2: RISK MITIGATION PLANS 21
10.2.2.1 The requirement is met when the Offeror’s proposed schedule to complete all open non-23 recurring design validation work (NRDV) demonstrates the ability to close by L-12 months. NRDV 24 closure is defined in Attachment 5, paragraph 10.2.2.1. 25
10.2.2.2 The requirement is met when (1) the Offeror’s proposed risk mitigation plan(s) for jointly 26 identified and self-identified “Low-Medium” or higher risks IAW the TIRP demonstrates the ability 27 to support ILC, or Offeror provides written documentation on Government risk acceptance; and 28 when (2) the Offeror’s updated detailed description of the progress towards the closure of identifed 29 risks either matches the previously provided schedule or provides credible justification for any 30 schedule delays. Additionally, Offeror’s proposal demonstrates progress towards closure in 31 accordance with the risk mitigation plans and Attachment 5, paragraph 10.2.2.2. 32
10.2.2.3 Any proposal updates from mishaps or flight anomalies resolution findings shall be 33 evaluated as applicable to Attachment 5 and Attachment 6. 34
11.1.1.4 RESERVED 1
11.1.1.5 The requirement is met for each historical mission when orbital injection accuracy actual 2 flight data falls within the required 3-Sigma orbit injection dispersions utilizing data from 3
Table 11-4 of Attachment 5, paragraph 11.1.1.3. 4
11.1.1.6 The requirement is met for each historical mission when orbital injection accuracy actual 5 flight data falls within the 3-Sigma predictions utilizing data from Table 11-4 of Attachment 5, 6 paragraph 11.1.1.3. 7
11.1.1.7 Undemonstrated GEO Direct Injection Accuracy at SV Separation: The requirement is met 8 when the AFSPC-8 mission injection accuracy specified by the Offeror for Attachment 5 Table 11-1 9 is supported by engineering and risk analyses provided by the Offeror that identify unproven 10 capabilities and risks associated with undemonstrated GEO direct orbit insertion accuracy and 11 corresponding mitigation plans as specified in Attachment 5, paragraph 11.1.1.1. 12
11.1.2 SUB-FACTOR 2: Mass-to-Orbit 13
11.1.2.1 Mass-to Orbit: The requirement is met when the results of the Offeror's analysis, described 14 in Attachment 5, paragraph 11.1.2, demonstrates the capability to lift the total mass provided in 15
Attachment 5 Table 11-5 to the orbit target requirements in Attachment 5 Table 11-1 with a 16 performance margin greater than or equal to zero. 17
11.1.2.2 Flight Performance Reserve: The requirement is met when the Offeror’s analysis includes 18 an upper stage flight performance reserve value calculated using the methodology described in 19
Attachment 5, paragraph 11.1.2.1. 20
11.1.2.3 Upper Stage Disposal: The requirement is met when the Offeror’s analysis includes 21 compliance with ODMSP and a ≥ 90% probability of success for completing the planned upper 22 stage disposal, as described in Attachment 5, paragraph 11.1.2.2. 23
11.1.2.4 Flight Mission Profile: The requirement is met when the AFSPC-8 mission profile, as 24 specified in Attachment 5, paragraph 11.1.2.2, is supported by evidence provided for flight 25 demonstrated mission profile portions as well as engineering and risk analyses provided for 26 undemonstrated mission profile portions identifying unproven capabilities, risk analyses, and 27 mitigations as described in Attachment 5, paragraph 11.1.2.3. 28
11.1.2.5 Ground Trace and Impact: The requirement is met when the ODMSP expected casualty 29 requirement of less than one in 10,000 is satisfied and substantiated by the Offeror’s provided 30 analysis description and plots as identified in Attachment 5, paragraph 11.1.2.4. Nominal jettisoned 31 body impacts must occur over water and, as applicable, the upper stage reentry location shall be in a 32 broad ocean area. 33
11.1.2.6 Historical Data: The requirement is met when the historical flight data supports the 34 trajectory predictions, or acceptable supporting rationale is provided to explain differences between 35 flight results and predictions, as described in Attachment 5, paragraph 11.1.2.5. 36
11.1.3 SUB-FACTOR 3: Launch Operations Concept Of Operations 1
11.1.3.1 The requirement is met when the Offeror’s approach to launch operations flow from the 2 time the Government provides the Space Vehicle Launch Stack (SVLS) to the Offeror as 3 government property for encapsulation through liftoff, to include any contingency procedures or 4 detailed plans proposed under Attachment 5, paragraph 11.1.3.1, demonstrates compliance with the 5 requirements of the MRA (ref. sections 3.5.2, 3.5.3, and 3.5.4 of the AFSPC-8 MRD), and is 6 technically sound. 7
11.1.3.2 The requirement is met when the Offeror’s approach to SVLS processing and encapsulation 8 procedures proposed under Attachment 5, paragraph 11.1.3.2 demonstrates compliance with the 9
MRA (ref. section 3.5.2 of the AFSPC-8 MRD) and is technically sound for the processing facility 10 the launch service provider proposes to use for an East Coast launch. 11
11.1.3.3 The requirement is met when the Offeror’s approach for contingency offload proposed 12 under Attachment 5, paragraph 11.1.3.3, demonstrates compliance with the requirements of the 13
MRA (ref. section 3.5.3 of the AFSPC-8 MRD) and is technically sound. 14
11.1.3.4 The requirement is met when the Offeror provides a plan that (1) describes managing and 15 processing classified payloads at the Special Access Program/Special Access Required level; (2) 16 includes detailed descriptions with rationale; (3) is demonstrated from previous efforts, or, if never 17 demonstrated, provides evidence-based rationale; and (4) is technically sound. 18
11.1.3.5 The requirement is met when the Offeror’s approach to execute the data requirements (as 19 described in Attachment 5, paragraph 11.1.3.5) is technically sound. 20
11.2 FACTOR 2: SCHEDULE 21
High-risk schedules are not awardable. A high-risk schedule is an IMS that is likely to cause 22 significant disruption of schedule and is unlikely to overcome any difficulties even with special 23 contractor emphasis and close Government monitoring. The criteria for this factor and sub-factors 24 are written with the intent to eliminate proposals with high schedule risk. Any criteria evaluated as 25
“does not meet” will render the subfactor unacceptable, and therefore, the proposal will be 26 unawardable. Criteria will be evaluated as “does not meet” if they do not satisfy the minimum 27 requirements of the solicitation. The minimum requirements of the schedule sub-factor criteria have 28 been written with the intent to eliminate proposals with high schedule risk. The government 29 considers a high-risk schedule to be unacceptable. An Offeror’s schedule is considered 30 unacceptable if it is unable to meet the requirement specified in sub-factor 1, Paragraph 11.2.1. 31
Additionally, an unacceptable rating in any of the following schedule criteria constitutes a high-risk 32
IMS, and the Offeror’s proposal will be considered unawardable. 33
11.2.1 SUB-FACTOR 1: INTEGRATED MASTER SCHEDULE (IMS) 34
11.2.1.1 The requirement is met when the results of the Offeror’s SRA demonstrate at least an 80% 35 probability of meeting the Initial Launch Capability (ILC) or earlier, and Offeror’s IMS meets all 36 five (5) of the criteria below: 37
11.2.1.2 The requirement is met when the Offeror’s IMS is constructed IAW section 11.2.1.1.1 1 through 11.2.1.1.5, Attachment 5, Instructions to Offerors and is deemed credible and reasonable. 2
11.2.1.3 The requirement is met when the Offeror’s IMS is constructed IAW section 11.2.1.4, 3
Attachment 5, Instructions to Offerors; and, the Offeror’s justifications for all components that fall 4 beyond the guideline thresholds from section 11.2.1.4, Attachment 5, Instructions to Offerors, are 5 deemed credible and reasonable. 6
11.2.1.4 The requirement is met when the Offeror’s IMS reflects activities sufficient to support the 7
ILC IAW paragraph 11.2.1.2, Attachment 5, Instructions to Offerors. The ILC for purposes of 8 evaluation is provided in paragraph 11.2.1.2.1, Attachment 5, Instructions to Offerors. 9
11.2.1.5 The requirement is met when the Offeror’s IMS task durations are IAW paragraph 10
11.2.1.1.6 and 11.2.1.1.7, Attachment 5, Instructions to Offerors, and deemed credible based on the 11
Offeror’s historical performance data, rationale and lessons learned, and statements of assumptions. 12
11.2.1.6 The requirement is met when the Offeror’s SRA is performed IAW paragraph 11.2.1.3 13
Attachment 5, Instructions to Offerors, and the three-point estimates are deemed credible and 14 reasonable based on the Offeror’s historical performance data, rationale and lessons learned, and 15 statements of assumptions. 16
11.2.2 SUB-FACTOR 2: RISK MITIGATION PLANS 17
11.2.2.1 The requirement is met when the Offeror’s proposed schedule to complete all open non-18 recurring design validation work demonstrates the ability to close by L-12 months. NRDV closure is 19 defined in Attachment 5, paragraph 11.2.2.1. 20
11.2.2.2 The requirement is met when (1) the Offeror’s proposed risk mitigation plan(s) for jointly 21 identified and self-identified “Low-Medium” or higher risks IAW the TIRP demonstrates the ability 22 to support ILC, or Offeror provides written documentation on Government risk acceptance; and 23 when (2) the Offeror’s updated detailed description of the progress towards the closure of identifed 24 risks either matches the previously provided schedule or provides credible justification for any 25 schedule delays. Additionally, Offeror’s proposal demonstrates progress towards closure in 26 accordance with the risk mitigation plans and Attachment 5, paragraph 11.2.2.2. 27
11.2.2.3 Any proposal updates from mishaps or flight anomalies resolution findings shall be 28 evaluated as applicable to Attachment 5 and Attachment 6. 29
12 ANNEX 3: AFSPC-12 30
The Offeror’s proposal will be evaluated utilizing the ratings defined in Table 12-1. 31
The Government will evaluate the Offeror’s proposal for compliance with the Performance and 32
Schedule sub-factors as set forth in paragraphs 12.1 and 12.2 below. An Unacceptable rating in any 33 sub-factor will result in an unawardable proposal. Any criteria evaluated as “does not meet” will 34 render the sub-factor unacceptable and therefore, the proposal will be unawardable. For a sub-factor 35 to be rated as acceptable, all aspects for that sub-factor must be evaluated as “meets.” If any aspect 36 is evaluated as “does not meet,” then the entire sub-factor will be evaluated as unacceptable. Only 37 paragraph 12.1.1.3. 1
12.1.1.7 Undemonstrated GEO Direct Injection Accuracy at SV Separation: The requirement is met 3 when the AFSPC-12 mission injection accuracy specified by the Offeror for Attachment 5 Table 12-4
1 is supported by engineering and risk analyses provided by the Offeror that identify unproven 5 capabilities and risks associated with undemonstrated GEO direct orbit insertion accuracy and 6 corresponding mitigation plans as specified in Attachment 5, paragraph 12.1.1.1. 7
12.1.2 SUB-FACTOR 2: Mass-to-Orbit 8
12.1.2.1 Mass-to Orbit: The requirement is met when the results of the Offeror's analysis, 9 described in Attachment 5, paragraph 12.1.2 demonstrates the capability to lift the total mass 10 provided in Attachment 5 Table 12-5 to the orbit target requirements in Attachment 5 Table 12-1 11 with a performance margin greater than or equal to zero. 12
12.1.2.2 Flight Performance Reserve: The requirement is met when the Offeror’s analysis includes 14 an upper stage flight performance reserve value calculated using the methodology described in 15
Attachment 5, paragraph 12.1.2.1. 16
12.1.2.3 Upper Stage Disposal: The requirement is met when the Offeror’s analysis includes 18 compliance with ODMSP and a ≥ 90% probability of success for completing the planned upper 19 stage disposal, as described in Attachment 5 paragraph 12.1.2.2. 20
12.1.2.4 Flight Mission Profile: The requirement is met when the AFSPC-12 mission profile, as 22 specified in Attachment 5, paragraph 12.1.2.2, is supported by evidence provided for flight 23 demonstrated mission profile portions as well as engineering and risk analyses provided for 24 undemonstrated mission profile portions identifying unproven capabilities, risk analyses, and 25 mitigations as described in Attachment 5, paragraph 12.1.2.3. 26
12.1.2.5 Ground Trace and Impact: The requirement is met when the ODMSP expected casualty 28 requirement of less than one in 10,000 is satisfied and substantiated by the Offeror’s provided 29 analysis description and plots as identified in Attachment 5, paragraph 12.1.2.4. Nominal jettisoned 30 body impacts must occur over water and, as applicable, the upper stage reentry location shall be in a 31 broad ocean area. 32
12.1.2.6 Historical Data: The requirement is met when the historical flight data supports the 34 trajectory predictions or acceptable supporting rationale is provided to explain differences between 35 flight results and predictions, as described in Attachment 5, paragraph 12.1.2.5. 36
12.1.3 SUB-FACTOR 3: Launch Operations Concept Of Operations And Multi-38
Manifest/Integration Management 39
12.1.3.1 The requirement is met when the Offeror’s approach to launch operations flow from the 40 time the Government provides the Bluegill and WFOV SVs to the Offeror as government property 41 for encapsulation through liftoff, to include any contingency procedures or detailed plans proposed 42 under Attachment 5, paragraph 12.1.3.1, demonstrates compliance with the requirements of the 43
MRA (ref. sections 3.1.1.8, 3.2.2, 3.2.3, 3.3, and 4.3 of the Huron IRD and sections 2.3, 2.4, and 2.5 44 of the WFOV TRD), and is technically sound. 1
12.1.3.2 The requirement is met when the Offeror provides a plan that integrates Bluegill and 2
WFOV into an integrated payload stack (IPS) and is then integrated into an encapsulated assembly 3
(EA) as described in Attachment 5, paragraph 12.1.3.2. The requirement is met when the Offeror’s 4 approach to Bluegill SV and WFOV SV processing and encapsulation procedures proposed under 5
Attachment 5, paragraph 12.1.3.2 demonstrates compliance with the MRA (ref. sections 3.1.1 and 6
3.2 of the Huron IRD, and sections 2.3 and 2.5 of the WFOV TRD) and is technically sound for the 7 processing facility the launch service provider proposes to use for an East Coast launch. The 8 requirement is met when the Offeror provides a plan and Concept Of Operations that (1) includes 9 detailed descriptions with rationale; (2) is demonstrated from previous efforts, or, if never 10 demonstrated, provides evidence-based rationale; and (3) is technically sound. 11
12.1.3.3 The requirement is met when the Offeror provides a plan that (1) integrates the EA to the 12 launch vehicle as described in Attachment 5, paragraph 12.1.3.3; (2) includes detailed descriptions 13 with rationale; (3) is demonstrated from previous efforts, or, if never demonstrated, provides 14 evidence-based rationale; and (4) is technically sound. 15
12.1.3.4 The requirement is met when the Offeror provides a plan that (1) describes managing and 16 processing classified payloads at the Special Access Program/Special Access Required level; (2) 17 includes detailed descriptions with rationale; (3) is demonstrated from previous efforts, or, if never 18 demonstrated, provides evidence-based rationale; and (4) is technically sound. 19
12.1.3.5 The requirement is met when the Offeror provides a plan and process (as described in 20
Attachment 5, paragraph 12.1.3.5) that (1) accommodates the final Bluegill configuration up to 21
Launch (L)-12 months; (2) includes detailed descriptions with rationale; (3) is demonstrated from 22 previous efforts, or, if never demonstrated, provides evidence-based rationale; and (4) is technically 23 sound. 24
12.1.3.6 The requirement is met when the Offeror’s approach to execute the data requirements (as 25 described in Attachment 5, paragraph 12.1.3.6) is technically sound. 26
12.1.4 SUB-FACTOR 4: Acoustic Environment 27
12.1.4.1. The requirement is met when the Offeror provides a plan that (1) demonstrates 28 compliance with WFOV TRD’s Acoustic Requirements (ref. section 3 of the WFOV TRD); (2) 29 includes detailed descriptions with rationale; (3) is demonstrated from previous efforts, or, if never 30 demonstrated, provides evidence-based rationale; and (4) is technically sound. 31
12.2 FACTOR 2: SCHEDULE 32
High-risk schedules are not awardable. A high-risk schedule is an IMS that is likely to cause 33 significant disruption of schedule and is unlikely to overcome any difficulties even with special 34 contractor emphasis and close Government monitoring. The criteria for this factor and sub-factors 35 are written with the intent to eliminate proposals with high schedule risk. Any criteria evaluated as 36
“does not meet” will render the subfactor unacceptable, and therefore, the proposal will be 37 unawardable. Criteria will be evaluated as “does not meet” if they do not satisfy the minimum 38 requirements of the solicitation. The minimum requirements of the schedule sub-factor criteria have 39 been written with the intent to eliminate proposals with high schedule risk. The government 1 considers a high-risk schedule to be unacceptable. An Offeror’s schedule is considered 2 unacceptable if it is unable to meet the requirement specified in sub-factor 1, Paragraph 12.2.1. 3
Additionally, an unacceptable rating in any of the following schedule criteria constitutes a high-risk 4
IMS, and the Offeror’s proposal will be considered unawardable. 5
12.2.1 SUB-FACTOR 1: INTEGRATED MASTER SCHEDULE (IMS) 6
12.2.1.1 The requirement is met when the results of the Offeror’s SRA demonstrate at least an 80% 7 probability of meeting the Initial Launch Capability (ILC) or earlier, and Offeror’s IMS meets all 8 five (5) of the criteria below: 9
12.2.1.2 The requirement is met when the Offeror’s IMS is constructed IAW section 12.2.1.1.1 11 through 12.2.1.1.5, Attachment 5, Instructions to Offerors and is deemed credible and reasonable. 12
12.2.1.3 The requirement is met when the Offeror’s IMS is constructed IAW section 12.2.1.4, 14
Attachment 5, Instructions to Offerors; and the Offeror’s justifications for all components that fall 15 beyond the guideline thresholds from section 12.2.1.4, Attachment 5, Instructions to Offerors, are 16 deemed credible and reasonable. 17
12.2.1.4 The requirement is met when the Offeror’s IMS reflects activities sufficient to support the 19
ILC IAW paragraph 12.2.1.2, Attachment 5, Instructions to Offerors. The ILC for purposes of 20 evaluation is provided in paragraph 12.2.1.2.1, Attachment 5, Instructions to Offerors. 21
12.2.1.5 The requirement is met when the Offeror’s IMS task durations are IAW paragraph 23
12.2.1.1.6 and 12.2.1.1.7, Attachment 5, Instructions to Offerors, and deemed credible based on the 24
Offeror’s historical performance data, rationale and lessons learned, and statements of assumptions. 25
12.2.1.6 The requirement is met when the Offeror’s SRA is performed IAW paragraph 12.2.1.3 27
Attachment 5, Instructions to Offerors, and the three-point estimates are deemed credible and 28 reasonable based on the Offeror’s historical performance data, rationale and lessons learned, and 29 statements of assumptions. 30
12.2.2 SUB-FACTOR 2: RISK MITIGATION PLANS 32
12.2.2.1 The requirement is met when the Offeror’s proposed schedule to complete all open non-33 recurring design validation work demonstrates the ability to close by L-12 months. NRDV closure is 34 defined in Attachment 5, paragraph 12.2.2.1. 35
12.2.2.2 The requirement is met when (1) the Offeror’s proposed risk mitigation plan(s) for jointly 36 identified and self-identified “Low-Medium” or higher risks IAW the TIRP demonstrates the ability 37 to support ILC, or Offeror provides written documentation on Government risk acceptance; and 38 when (2) the Offeror’s updated detailed description of the progress towards the closure of identifed 39 risks either matches the previously provided schedule or provides credible justification for any 40 schedule delays. Additionally, Offeror’s proposal demonstrates progress towards closure in 41 accordance with the risk mitigation plans and Attachment 5, paragraph 12.2.2.2. 42
12.2.2.3 Any proposal updates from mishaps or flight anomalies resolution findings shall be 43 evaluated as applicable to Attachment 5 and Attachment 6. 1
Attachment 5, paragraph 13.1.1.2, satisfies the requirements of Table 13-3 of Attachment 5, 1 paragraph 11.1.1.2 (3 sigma). 2
13.1.1.4 RESERVED 4
13.1.1.5 The requirement is met for each historical mission when orbital injection accuracy actual 6 flight data falls within the required 3-Sigma orbit injection dispersions utilizing data from 7
Table 13-4 of Attachment 5, paragraph 13.1.1.3. 8
13.1.1.6 The requirement is met for each historical mission when orbital injection accuracy actual 10 flight data falls within the 3-Sigma predictions utilizing data from Table 13-4 of Attachment 5, 11 paragraph 13.1.1.3. 12
13.1.1.7 Undemonstrated Injection Accuracy at SV Separation: The requirement is met when the 14
AFSPC-52 mission injection accuracy specified by the Offeror for Attachment 5 Table 13-1 is 15 supported by engineering and risk analyses provided by the Offeror that identify unproven 16 capabilities and risks associated with undemonstrated orbit insertion accuracy and corresponding 17 mitigation plans as specified in Attachment 5, paragraph 13.1.1.1. 18
13.1.2 SUB-FACTOR 2: Mass-to-Orbit 20
13.1.2.1 Mass-to Orbit: The requirement is met when the results of the Offeror's analysis, described 21 in Attachment 5, paragraph 13.1.2, demonstrates the capability to lift the total mass provided in 22
Attachment 5 Table 13-5 to the orbit target requirements in Attachment 5 Table 13-1 with a 23 performance margin greater than or equal to zero. 24
13.1.2.2 Flight Performance Reserve: The requirement is met when the Offeror’s analysis includes 25 an upper stage flight performance reserve value calculated using the methodology described in 26
Attachment 5, paragraph 13.1.2.1. 27
13.1.2.3 Upper Stage Disposal: The requirement is met when the Offeror’s analysis includes 28 compliance with ODMSP and a ≥ 90% probability of success for completing the planned upper 29 stage disposal, as described in Attachment 5 30 paragraph 13.1.2.2. 31
13.1.2.4 Flight Mission Profile: The requirement is met when the AFSPC-52 mission profile, as 32 specified in Attachment 5, paragraph 13.1.2.2, is supported by evidence provided for flight-33 demonstrated mission profile portions as well as engineering and risk analyses provided for 34 undemonstrated mission profile portions identifying unproven capabilities, risk analyses, and 35 mitigations as described in Attachment 5, paragraph 13.1.2.3. 36
13.1.2.5 Ground Trace and Impact: The requirement is met when the ODMSP expected casualty 37 requirement of less than one in 10,000 is satisfied and substantiated by the Offeror’s provided 38 analysis description and plots as identified in Attachment 5, paragraph 13.1.2.4. Nominal jettisoned 39 body impacts must occur over water and, as applicable, the upper stage reentry location shall be in a 40 broad ocean area. 41
13.1.2.6 Historical Data: The requirement is met when the historical flight data supports the 1 trajectory predictions, or acceptable supporting rationale is provided to explain differences between 2 flight results and predictions, as described in Attachment 5, paragraph 13.1.2.5. 3
13.1.2.7 Coupled Loads Analysis (CLA): The requirement is met when adequate structural margins 4 are verified for all SV components based on SV contractor evaluation of CLA results. 5
13.1.3 SUB-FACTOR 3: Launch Operations Concept Of Operations 6
13.1.3.1 The requirement is met when the Offeror’s approach to launch operations flow from the 7 time the Government provides the AFSPC-52 payload to the Offeror as government property for 8 encapsulation through liftoff, to include any contingency procedures or detailed plans proposed 9 under Attachment 5, paragraph 13.1.3.1; demonstrates compliance with the requirements of the 10
MRA (ref. sections TBD of the AFSPC-52 MRD); and is technically sound. 11
13.1.3.2 The requirement is met when the Offeror’s approach to AFSPC-52 payload processing and 12 encapsulation procedures proposed under Attachment 5, paragraph 13.1.3.2 demonstrates 13 compliance with the MRA (ref. section TBD of the AFSPC-52 MRD) and is technically sound for 14 the processing facility the launch service provider proposes to use for an TBD Coast launch. 15
13.1.3.3 The requirement is met when the Offeror’s approach for contingency offload proposed 16 under Attachment 5, paragraph 13.1.3.3 demonstrates compliance with the requirements of the MRA 17
(ref. sections TBD of the AFSPC-52 MRD) and is technically sound. 18
13.1.3.4 The requirement is met when the Offeror provides a plan that (1) describes managing and 19 processing classified payloads at the Special Access Program/Special Access Required level ; (2) 20 includes detailed descriptions with rationale; (3) is demonstrated from previous efforts, or, if never 21 demonstrated, provides evidence-based rationale; and (4) is technically sound. 22
13.1.3.5 The requirement is met when the Offeror’s approach to execute the data requirements (as 23 described in Attachment 5, paragraph 13.1.3.5) is technically sound. 24
13.2 FACTOR 2: SCHEDULE 25
High-risk schedules are not awardable. A high-risk schedule is an IMS that is likely to cause 26 significant disruption of schedule and is unlikely to overcome any difficulties even with special 27 contractor emphasis and close Government monitoring. The criteria for this factor and sub-factors 28 are written with the intent to eliminate proposals with high schedule risk. Any criteria evaluated as 29
“does not meet” will render the subfactor unacceptable and therefore, the proposal will be 30 unawardable. Criteria will be evaluated as “does not meet” if they do not satisfy the minimum 31 requirements of the solicitation. The minimum requirements of the schedule sub-factor criteria have 32 been written with the intent to eliminate proposals with high-schedule risk. The government 33 considers a high-risk schedule to be unacceptable. An Offeror’s schedule is considered 34 unacceptable if it is unable to meet the requirement specified in sub-factor 1, Paragraph 13.2.1. 35
Additionally, an unacceptable rating in any of the following schedule criteria constitutes a high-risk 36
IMS, and the Offeror’s proposal will be considered unawardable. 37
13.2.1 SUB-FACTOR 1: INTEGRATED MASTER SCHEDULE (IMS) 1
13.2.1.1 The requirement is met when the results of the Offeror’s SRA demonstrate at least an 80% 2 probability of meeting the Initial Launch Capability (ILC) or earlier; and Offeror’s IMS meets all 3 five (5) of the criteria below: 4
13.2.1.2 The requirement is met when the Offeror’s IMS is constructed IAW section 13.2.1.1.1 5 through 13.2.1.1.5, Attachment 5, Instructions to Offerors and is deemed credible and reasonable. 6
13.2.1.3 The requirement is met when the Offeror’s IMS is constructed IAW section 13.2.1.4, 7
Attachment 5, Instructions to Offerors; and the Offeror’s justifications for all components that fall 8 beyond the guideline thresholds from section 13.2.1.4, Attachment 5, Instructions to Offerors, are 9 deemed credible and reasonable. 10
13.2.1.4 The requirement is met when the Offeror’s IMS reflects activities sufficient to support the 11
ILC IAW paragraph 13.2.1.2, Attachment 5, Instructions to Offerors.
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 .