07_Attachment_5_Draft_Instructions_to_Offerors_(updated_15_Jul_15).pdf
PDF 213 KB Posted
- Attached to
- EELV Phase 1A GPS III Launch Services Federal contract opportunity
- Solicitation number
- 15-102
View the file
Other files for this federal contract opportunity
Show all 38
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions to Offerors FA8811-15-R-0001
Evolved Expendable Launch Vehicle (EELV) Phase 1A Competitive Acquisition for GPS III Launch Services
Attachment 5
Instructions to Offerors
15 July 2015
1 PROGRAM STRUCTURE AND OBJECTIVES
The Air Force Space and Missile Systems Center (SMC) anticipates the award of a launch services contract for delivering the Global Positioning System III (GPS III), to orbit. The general requirements for the launch services are defined in the Performance Work Statement (PWS) while mission-specific requirements are defined in the Mission Requirements Annex (MRA). This contract is for the procurement of the GPS III mission only; therefore, requirements in the PWS and Contract Data Requirements List (CDRL) with specific NRO-only references are not applicable and appear in grey text.
2 GENERAL INSTRUCTIONS
The Offeror's proposal must include all data and information requested by this Request for Proposal (RFP) and must be submitted in accordance with these instructions. In developing the proposal, the Offeror shall ensure that their proposed offer complies with all the requirements contained in the RFP, to include the PWS, MRA, & CDRLs. Non-conformance with the instructions provided in this RFP may result in an unfavorable proposal evaluation.
The Offeror’s proposal shall be clear and concise and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their capabilities and experience and will base its evaluation on the information presented in the Offeror's proposal. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired. The proposal validity date must be specified and the proposal must be valid for at least 180 days after date of submission. In accordance with Federal Acquisition Regulation (FAR) Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals.
Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.
3 GENERAL INFORMATION
3.1 POINT OF CONTACT
The Procuring Contracting Officer (PCO), Ms. Dzung Dom, is the sole point of contact for this acquisition. Address any questions or concerns you may have to the PCO at dzung.dom@us.af.mil or 310-653-3696. Written requests for clarification may be sent to the PCO at the address for SMC/LRK located on the front page of the model contract/solicitation.
3.2 DEBRIEFINGS
The PCO will promptly notify Offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with FAR 15.505. In addition, the PCO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.
3.3 DISCREPANCIES
If an Offeror believes that the requirements in these instructions contain an error or omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale as well as the remedies the Offeror is asking the PCO to consider as related to the omission or error.
3.4 ELECTRONIC REFERENCE DOCUMENTS
Referenced documents for this solicitation are available at http://www.fedbizopps.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.
3.5 EXCHANGES
Exchanges of source selection information between the Government and Offerors will be controlled by the PCO. Source selection information will be transmitted in person or via certified mail, delivery service, or facsimile.
3.6 DISCUSSIONS
The Government reserves the right to award without discussions if it is in the best interest of the Government. However, the Government may conduct discussions with Offerors after establishing a competitive range based on the ratings of each proposal against all evaluation criteria.
3.7 USE OF NON-GOVERNMENT ADVISORS
Offerors are advised that data submitted to the Government in response to this solicitation will be released to individuals who work for the following companies as non-Government advisors for review and analysis:
Company Name Address The Aerospace Corporation PO BOX 92957, Los Angeles, CA 90009-2957 Tecolote Research, Inc 2120 E. Grand Avenue, Suite 200, El Segundo, CA 90245
Individual advisors from the above support contractors participating in the review and analysis of proposals have signed individual non-disclosure agreements with the Government which strictly prohibits any release or disclosure of information outside of the source selection team.
3.8 ALTERNATIVE PROPOSALS
Alternative proposals will not be considered. Alternative proposals are those that do not meet the terms and conditions of the RFP, including attachments.
4 PROPOSAL FORMAT/LIMITS
4.1 ORGANIZATION/NUMBER OF COPIES/PAGE LIMITS
The Offeror shall prepare the proposal as set forth in Table 4-1: Proposal Organization. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits. The Volumes identified in the table shall be separately bound in three-ring, loose-leaf binders, plus each Volume’s electronic copy shall be saved on a separate compact disc (CD). For
Volume II, provide page separation tabs for each Performance subfactor. The Offeror shall provide two hard copies of the proposal and two electronic copies of the proposal on CDs. The contents of each proposal volume are described in the paragraph as noted in the table below:
Table 4-1: Proposal Organization
Volume Title Hard
Copies Electronic
Copies Page Limit
I Executive Summary 2 2 10
II
Performance Volume 2 2 100
Schedule Volume 2 2 Unlimited
III Price Volume 2 2 Unlimited
IV Model Contract Volume 2 2 Unlimited
4.2 PAGE LIMITATIONS
Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal, and excess paper copies will be returned to the Offeror as soon as practicable. If the Government issues Evaluation Notices (ENs) for discussions, page limitations may be placed on responses to ENs. The specified page limits for EN responses will be identified in the letters sent along with the ENs to the Offerors. Unless otherwise specified, each page shall be counted except the following: cover pages, table of contents, tabs, and glossaries.
4.3 PAGE SIZE AND FORMAT
1. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 by 11 inches, not including foldouts. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point using Times New Roman font type. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall also apply to responses to ENs.
2. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated and legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume and each face of the foldout containing information will be counted as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics, not for pages of text. For tables, charts, graphs, and figures, the text may be in the Offeror’s preferred format.
4.4 CLASSIFIED INFORMATION
The Government does not expect that classified information will be required. If you require classified information in your proposal, please contact the PCO as soon as possible but no later than 14 calendar days prior to the deadline for proposal receipt.
4.5 CROSS-REFERENCING
To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal.
Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.
4.6 INDEXING
Each volume shall contain a table of contents, with more detail than the master table of contents included in the Executive Summary Volume, to delineate the subparagraphs within that volume.
Tab indexing shall be used to identify sections.
4.7 GLOSSARY OF ABBREVIATIONS AND ACRONYMS
Each volume shall contain a glossary of all abbreviations and acronyms used, with a definition for each.
4.8 BINDING AND LABELING
Each volume of the proposal shall be separately bound in a three-ring, loose-leaf binder, permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each volume, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror’s name. The same identifying data shall be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e) (Restriction on disclosure and use of data) and FAR 3.104-4 (Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information).
4.9 ELECTRONIC OFFERS
The content and page size of electronic copies must be identical to the hard copies. All CDs shall be placed in plastic sleeves that open on the top in one separate binder, with the volume number and title indicated on each disc. Hypertext links shall be used to facilitate navigation within the document. Use separate files to permit rapid location of all portions, including factors, exhibits, annexes, and attachments, if any. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2007/2010, MS Office Excel 2007/2010, MS Office Project 2007/2010, and MS Office Power Point 2007/2010, as applicable. In the event that hard copies and electronic copies of a proposal are submitted and there are discrepancies between the hard copies and the electronic copies of the proposal, the electronic copies will be used for evaluation.
4.10 DISTRIBUTION
The "original" proposal shall be identified. Proposals received after the date and time specified will be treated in accordance with FAR 52.212-1(f). Delivery of proposals shall be coordinated with the PCO at least 24 hours in advance of the due date and time. Early deliveries of proposals shall also be coordinated with the PCO. Electronic and hard copies of proposals are due DD MMM YY, by 10:00 am Pacific Daylight Time. Proposals shall be addressed to the PCO and mailed or hand carried to:
SMC/LRK
Attn: Ms. Dzung Dom 483 N. Aviation Blvd.
El Segundo, CA 90245
5 VOLUME I – EXECUTIVE SUMMARY
The purpose of the Executive Summary Volume is to provide a complete overview of the Offeror’s proposal. The Executive Summary Volume will not be evaluated, scored, or used to clarify other discrepant information in other volumes. Any summary material presented in the Executive Summary Volume will not be considered as meeting the requirements for any portions of other volumes of the proposal. Do not include cost information. The Offeror shall provide the following information in the Executive Summary:
5.1 NARRATIVE SUMMARY
The narrative summary of the entire proposal shall be concise, to include addressing any risk areas and mitigations, and highlighting any key or unique features. The salient features shall tie in with the evaluation factors in Attachment 6, Evaluation Criteria.
5.2 OFFEROR’S PROPOSED TEAM
The Offeror shall briefly identify the Offeror’s team, including the prime and teammates.
5.3 MASTER TABLE OF CONTENTS
The Offeror shall include a master table of contents of the entire proposal.
5.4 CROSS REFERENCE MATRIX
The Offeror shall fill in the proposal column of the cross reference matrix below with the volume, sections, and paragraph numbers from their proposal that correspond with the paragraph numbers from Attachment 5 and Attachment 6 listed below.
Cross Reference Matrix
Attachment 5:
Instructions to
Offerors
Attachment 6:
Evaluation
Criteria
Counted Towards
Maximum Page Limitation (Y/N)
Proposal Volume, Section, Paragraphs
5.1 N/A Y *
5.2 N/A Y *
5.3 N/A N *
5.4 N/A N *
6.1.1 6.1.1.1 Y *
6.1.1 6.1.1.2 Y *
6.1.1 6.1.1.3 Y *
6.1.1 6.1.1.4 Y *
6.1.1 6.1.1.5 Y *
6.1.1 6.1.1.6 Y *
6.1.1 6.1.1.7 Y *
6.1.1 6.1.1.8 Y *
6.1.1 (3) 6.1.1.9 Y *
6.1.2 6.1.2.1 Y *
6.1.2 6.1.2.2 Y *
6.1.2 6.1.2.3 Y *
6.1.2 (3) 6.1.2.4 Y *
6.1.2 6.1.2.5 Y *
6.1.2 6.1.2.6 Y *
6.1.2 6.1.2.7 Y *
6.1.2 6.1.3.1 Y *
6.1.3 6.1.3.1 Y *
6.1.3.1 6.1.3.1 Y *
6.1.3.2 6.1.3.1 Y *
6.1.3.3 6.1.3.1 Y *
6.1.3.4 6.1.3.1 Y *
6.2.1 6.2.1 Y† *
6.2.2 6.2.2 N *
7.1 7.1 N *
* To be filled in by Offeror † Any narrative portion of the Offeror’s integrated schedule will be counted against the page limitations, but the Integrated Master Schedule itself will not.
6 VOLUME II – PERFORMANCE VOLUME FOR EVALUATION (GPS III)
The Performance Volume addresses the Offeror’s technical approach and technical solution for meeting the Government’s threshold performance or capability requirements for each Technical subfactor. The Offeror shall describe their proposed approach to meeting the requirements of each subfactor within the Technical factor. Legibility, clarity, and coherence are very important. Offeror responses will be evaluated against the Technical criteria defined in Attachment 6, Evaluation Criteria, Section 6.
6.1 FACTOR 1: PERFORMANCE
6.1.1 SUBFACTOR 1: ORBITAL ACCURACY
The Offeror shall complete the Proposed GPS III 3-Sigma Injection Accuracy column in Table 6-1 for the proposed launch vehicle system of the GPS III mission. 3-sigma for Injection Accuracy is defined as 99.73% probability at 50% confidence. Should the Offeror propose a perigee greater than 1,000 km, then the Offeror shall state in their proposal what perigee value they chose.
Table 6-1: GPS III SV Osculating Orbit Insertion Requirement and Accuracies1
Parameter Requirement Accuracy Proposed GPS III 3-sigma Injection Accuracy
Apogee Altitude (km)2 20,181 ± 100
Perigee Altitude (km) ≥1,000 ± 25
Inclination (deg) 55 deg ± 0.08 Right Ascension of Ascending Node (deg)
296.23 deg (Plane A)3 ± 0.25
Argument of Perigee (deg) 270 deg ± 0.5
(1) Orbital parameters correspond to SV following separation including the effects of separation delta-V
(2) The apogee altitude is the altitude of the SV at first apogee after transfer orbit injection
(3) For the purposes of this proposal only, the Offeror shall use target Plane A, and assume a launch date of 1 Jan 2017at 0000Z. The reference date is 1 December 1991 00:00 UTC (Ref 1) with a RAAN rate of -0.04009345 degrees/day.
1. The Offeror shall provide a detailed description, anchored to the demonstrated performance of the proposed launch system, of their approach to meet the orbital insertion targets and accuracy requirements described in Table 6-1, while complying with the separation parameters detailed in Table 6-3. The description shall include:
a) Identification of the launch vehicle system proposed.
b) Approach to meeting a Right Ascension of the Ascending Node (RAAN) accuracy requirement as described in Table 6-1.
c) A detailed description of the methodology(ies) (Monte Carlo and/or Covariance) used to establish the injection accuracies. If Monte Carlo methodology is chosen, a minimum of 10,125 runs must be performed.
d) Complete Table 6-2: Dispersions List, of all dispersions used in the methodology for establishing the injection accuracies, including justifications.
Dispersions are defined as variations on performance and navigation input parameters (e.g., thrust, Isp, sensor bias/scale factors, etc.) used to generate injection accuracy results. A sensitivity is defined as the variation of an output parameter divided by the variation of the associated input parameter. Dispersions shall be listed in Table 6-2 with required data to describe the dispersions used, including statistical distribution type (e.g., Gaussian, uniform, etc.) and resulting sensitivity.
Table 6-2: Dispersions List
Dispersion -3 sigma value Nominal
+3 sigma value
Statistical Distribution
Type
Apogee Altitude
(kilometers/ parameter units)
Perigee Altitude
(kilometers/ parameter units)
Inclination Sensitivity (degrees/ parameter units)
Arg. of Perigee Sensitivity (degrees/ parameter units)
RAAN
Sensitivity (degrees/ parameter units)
Parameter (subscript i)
Parameter 2 (subscript i=n)
2. The offeror shall complete the proposed GPS III separation parameter accuracy column in Table
6-3 for the proposed launch vehicle system of the GPS III mission with the assumptions that:
a) The spin direction shall be from -Ysv axis to +Xsv axis, about +Zsv axis
b) Pre-SV Separation Visibility ≥ 25 min after 5 deg elevation angle line of sight from any AFSCN asset.
Table 6-3: GPS III Separation Parameters
At separation the LV shall be capable of orienting the SV positive Z-axis (+Zsv) to any of the attitudes listed below. There are two possible separation attitudes to cover injections on any date or plane. The two attitudes are:
Negative Ecliptic Normal (NEN) Positive Ecliptic Normal (PEN) The desired attitude for a specific mission will be provided after each SV call-up. The separation attitudes are defined in the MRA. For the purposes of this proposal only, the Offeror shall use a NEN separation attitude. There is no constraint on the orientation of the SV X-axis or Y-axis at separation.
3. The Offeror shall provide a completed Table 6-4: Historical Orbital Injection Accuracy, for each of the 4 most recent elliptical transfer orbit launches, of the proposed launch vehicle system. If the launch history does not include four elliptical transfer orbit launches, then the Offeror shall complete Table 6-4 with data from as many elliptical transfer orbit launches as flown and supplement with data for the most
Parameter Requirement Accuracy Proposed GPS III Separation Accuracy
Spin Rate (deg/sec) + 0.6 ± 0.3
Pointing Accuracy of +Zsv axis (deg) NEN ≤ 5
Transverse Angular Rate (Root Sum Square (RSS) of the rates about the Xsv and Ysv axes) (deg/sec)
0 ≤ 1.8 recent launches, for a total of 4 missions. The Offeror shall provide detailed supporting rationale behind any changes to the dispersions or methodology used in generating the predicted accuracies for either the historical elliptical transfer orbit launches or the most recent launches.
Table 6-4: Historical Orbital Injection Accuracy
Reference Missions Apogee
Altitude (km)
Perigee Altitude
(km)
RAAN
(deg)
Inclination (deg)
Argument of
Perigee (deg)
Requirement (Min, Target, Max)
Prediction (Min, Mean, Max)
Actual
6.1.2 SUBFACTOR 2: MASS-TO-ORBIT
Based on launching from the Eastern Range, proposed mission profile, upperstage disposal approach, and the injection parameters proposed in Table 6-1, the Offeror shall provide a detailed description of the mass-to-orbit capability associated with the proposed launch vehicle system for the GPS III mission. The Offeror shall include their proposed mission profile, to include: Upper stage disposal approach, Ec associated with disposal (if applicable), computation of Ec (if applicable), identification of proposed launch site, significant Sequence of Events (SOE) (items 6.1.2 [2.a)-i)]), osculating orbital parameters for items 6.1.2 [2 a)-i)], for which SV separation will include the effects of separation delta-V. Profile is not limited to items a-i. The Offeror shall provide a high fidelity analysis and a description of the methodology used to generate the final mass-to-orbit for the GPS III mission. At a minimum, the launch vehicle shall have the capability of injecting the Total Mass, described on Table 6-5, to the orbit defined on Table 6-1.This analysis and methodology shall be based on either demonstrated flight performance or analysis. The analysis and methodology description shall include:
1. Upper stage performance margin to the GPS III orbit detailed in Table 6-1 with the Total Mass as defined in Table 6-5. The Offeror shall fill in the vehicle specific payload equivalent masses in Table 6-5. The Offeror shall also provide the reserves as specified below.
a) 3-sigma Flight Performance Reserve value (defined as 99.865% probability at 50% confidence) calculated by Monte Carlo methodology with a minimum of 10,125 runs performed.
b) Description and quantification of any additional reserves held
Table 6-5 Mass-to Orbit
Description Mass Units
Max SV Mass Used lbs
Payload Adapter Mass - lbs
2% Propellant Mass Margin - lbs
Instrumentation Margin 75 lbs
Total Mass - lbs
Note 1: Payload Adapter (PLA) Mass is the mass of the PLA hardware and all associated harnesses.
Note 2: 2% Propellant Mass Margin is 2% of the proposed launch vehicle system performance capability to the reference orbit in Table 6-1 with ODMSP compliance.
2. Planned GPS III Mission Profile including upper stage disposal approach (Orbital Debris Mitigation Standard Practices – ODMSP compliance is not waiverable). Casualty expectation and its computation shall be provided (if applicable). The mission profile shall include the proposed launch site and significant sequence of events, as well as, the following listed events (a-i); plus, osculating orbital parameters (as defined in Table 6-1 for the selected plane/date) of the SV at separation (including the effects of separation ∆V).
a) Main engine start
b) Solid rocket motor burnout and jettison sequence (if applicable)
c) Engine cutoff and separation for each stage
d) Payload fairing jettison
e) Upper stage engine burn ignition(s),cutoff(s) and coast time(s)
f) Upper stage and SV separation
g) Initiation of upper stage Contamination and Collision Avoidance Maneuvers (CCAMs)
h) Upper stage disposal initiation
i) End of mission for upper stage, where end of mission is defined as the completion of passivation with no further planned maneuvers, or through upper stage impact after controlled reentry
3. The Offeror shall provide evidence for any portion of the mission profile that has been flight demonstrated (T-0 to disposal burn) by the proposed launch vehicle. Examples of evidence could include a table of demonstrated burn durations vs. planned burn durations;
demonstrated coast durations vs. planned; re-entries achieved vs. planned; etc. The Offeror shall also identify on which flight the mission profile portion was demonstrated.
The Offeror shall identify any portion of the mission profile that has not yet been flight demonstrated by proposed launch vehicle system. Undemonstrated portions of a mission profile include, but are not specifically limited to:
a) Total proposed mission duration from launch to End of Mission as defined in Section 6.1.2 [2. i)] upper stage is greater than 10 minutes longer than a previously flown mission
b) Number of proposed upper stage engine relights is greater than previously flown
c) Coast duration between upper stage engine relights is greater than 5 minutes from a previously flown mission
d) Booster or upper stage throttle settings have not been previously flown
e) Proposed CCAM or upper stage disposal solution have not been previously flown (per EELV System Performance Requirements Document (SPRD), Rev. A)
f) Radiation environments not previously demonstrated
If any of the Offeror’s previous flights do not demonstrate portions of the GPS III mission profile, to include but not limited to 3. a-f, then the Offeror shall provide a detailed engineering and risk analysis of the affected launch vehicle subsystems or components and any risks or limiting factors associated with the design or configuration of the affected subsystems. The Offeror shall also describe how the proposed mitigation approach addresses the identified risks associated with the undemonstrated portion of the proposed mission profile.
4. Trajectory ground rules and assumptions regarding:
a) Launch vehicle system
b) Launch Range/Complex
c) Listing of system-level vehicle constraints and values (e.g., dynamic pressure (Q), Q-alpha, acceleration, etc.)
d) Listing of Range-related (instantaneous impact point and tracking station) constraints, as applicable
5. Ground trace and instantaneous impact point trace through end of mission or through upper stage impact after controlled reentry, with identification of nominal jettison body impacts.
Nominal jettisoned body impacts must occur over water and, as applicable, the upper stage reentry location shall be in a broad ocean area.
6. The Offeror shall provide historical data and/or engineering analysis, from T-0 launch through upper stage disposal, on the final mission design trajectory predictions and flight data for mission profiles (including sequence of events and osculating SV orbital parameters at separation) and for vehicle acceleration comparison plots for the 4 most recent launches of the launch vehicle system proposed, or as many as have been launched if fewer than 4 launches have taken place. Individual acceleration plots shall be provided for each burn of each stage.
7. If the Offeror plans to de-orbit the upper stage, they shall provide the impact ellipse corresponding to the Controlled Reentry conditions.
6.1.3 SUBFACTOR 3: LAUNCH OPERATIONS CONCEPT OF OPERATIONS (CONOPS)
The Offeror shall provide a Launch Operations CONOPS which includes the following elements:
6.1.3.1 A description of the proposed launch operations flow from the point the Space Vehicle
(SV) contractor agrees to turn over responsibility of the SV for encapsulation through liftoff, to include any contingency procedures;
6.1.3.2 SV processing and encapsulation procedures which are oriented to the processing facility the USG has required the Offeror to use for an East coast launch;
6.1.3.3 An access provision report and technical drawings showing access platforms to the payload fairing access doors on the integrated LV/SV stack IN ACCORDANCE WITH the requirements defined in the MRA, paragraph XIV section E, G, and H; and
6.1.3.4 A description and diagrams of propellant-compatible interface plumbing and aspirator in accordance with the contingency offload requirements defined in the MRA, paragraph XIV section G, and H.
6.2 FACTOR 2: SCHEDULE
6.2.1 SUBFACTOR 1: INTEGRATED SCHEDULE
The Offeror shall provide a resource-loaded Microsoft Project Intermediate (approximately 500 or fewer tasks/activities as defined in paragraph- 3.7.1.3.3 of DI-MGMT-81861) integrated schedule for the GPS III mission. The schedule shall reflect a start date for procuring the longest lead hardware and support an Initial Launch Capability (ILC) of May 2018. The integrated schedule shall follow Format 6 of the Data Item Description DI-MGMT-81861; disregarding Integrated Master Plan (IMP), Organizational Breakdowns Structure, Control Accounts, Planning Packages, and Actual or Budgeted Cost of Work Performed (AWCP, BCWP) references in the following paragraphs; 3.7.1.3, 3.7.1.3.4, 3.7.1.3.4.1, 3.7.1.3.4.2, 3.7.1.3.4.3, 3.7.1.3.5.4, 3.7.1.3.7.2, 3.7.1.3.7.3,
3.8.4 and 3.8.5. The integrated schedule shall identify all critical events, to include but not limited to, LV production (with identification of the longest lead hardware) and testing at component, subsystem, system, and integrated level, major reviews, encapsulation, transport, integrated testing, LV/SV mate, and ILC. The integrated schedule shall encompass all activities and tasks sufficient to account for the GPS III launch services proposed, including activities to accomplish the tasks in the PWS, CDRL and NRE Work Closure Plan (per paragraph 6.2.2), as well as:
1) Logically linked predecessor/successor relationships, horizontally and vertically, to include all interdependencies
2) A software-generated critical path from procuring the longest lead hardware, through Authority to Proceed to ILC, documenting and justifying assumptions, constraints, leads, and lags.
3) A summary of all critical milestone events for the Offeror’s other launches during the timeframe and the sensitivity of the GPS III schedule to perturbations in other launch flows.
4) Offerors shall provide a Schedule Risk Assessment according to DID MGMT-81861 paragraph 3.7.1.3.6
5) For activities that are not consistent with historical data, previously not performed, or on the critical path, Offerors shall provide the basis and the estimating rationale for task/activity durations and associated levels of effort in the resource-loaded schedule in accordance with the Schedule Basis Template (Appendix A).
6.2.2 SUBFACTOR 2: WORK CLOSURE PLANS
The Offeror shall provide Government-accepted NRE Work Closure Plan(s) for completing the remaining open non-recurring work with identified risks (Low-Medium, Medium, and High) in accordance with the Technical Issue Resolution Process (TIRP).
The Offeror shall provide a Government-accepted Work Closure Plan(S) for open flight and qualification anomalies.
All Work Closure Plans shall support closure of open items by L-12 months, unless an exception for specific tasks was pre-coordinated with the Government. Should the Government enter into discussions with the Offeror(s), the Government reserves the right to request an updated detailed description of the Offeror’s progress towards the closure of identified risks in accordance with the Government-accepted Work Closure Plans. Additionally, should the Government enter into discussions; updated Work Closure Plans will be required at Final Proposal Revision.
7 VOLUME III – PRICE
7.1 FACTOR 3: PRICE
The Offeror shall not include price information in any other portion of the proposal, except the Price Volume or Model Contract. When completing Table 7-1, the Offeror shall fill in the same prices as those proposed in the model contract for CLINs 1000, 2000, and 3000.
Table 7-1
CLIN DESCRIPTION PRICE
1000 LAUNCH VEHICLE PRODUCTION
MISSION INTEGRATION/LAUNCH OPS/
SPACEFLIGHT WORTHINESS CERTIFICATION
3000 MISSION UNIQUE
QUICK REACTION/ANOMALY RESOLUTION (H005)
__________ (FIXED PRICE RATE) * 10,000 HOURS
GOVERNMENT PROPERTY OF GOVERNMENT PROPERTY
TOTAL EVALUATED PRICE
7.2 QUICK REACTION/ANOMALY RESOLUTION
For Quick Reaction/Anomaly Resolution, the Offeror shall provide a wrap rate within SCM/LR- H005 of the model contract. The same rate shall then be filled in on Table 7-1, and multiplied by 10,000 hours for the total Quick Reaction / Anomaly Resolution Price.
7.3 GOVERNMENT PROPERTY (GP)
7.3.1 GP IN TOTAL EVALUATED PRICE
If the Offeror requires the use of GP, the Offeror shall complete Table 7-2 in Microsoft Excel format using the acquisition cost information from Attachment 8 and the rental equivalency method described in FAR 52.245-9(e)(2) (the hourly rental charge is calculated by multiplying 2 percent of the acquisition cost by the hours of rental time, and dividing by 720). The Offeror shall multiply the acquisition cost stated in column (B) by 2% and list the dollar value in column (C). For column (D), the Offeror shall list the hours of use required rounded to the next highest hour. For column (E) the Offeror shall multiply the values in column (C) and column (D). For column (F), the Offeror shall divide the value in column (E) by 720.
Table 7-2: Government Property
(A) Item #
(B) Acquisition
Cost ($)
(C) 2% of
Acquisition Cost ($)
(D) Hours of Use
Required
(E)
Subtotal
(F) Rental
Equivalency (Divide by 720) example $100,000 $2,000 4000 $8,000,000 $11,111
Total Proposed Rental Equivalency Cost
7.4 ROUNDING
All dollar amounts provided shall be rounded to the nearest dollar. All labor rates shall be rounded to the nearest dollar.
8 VOLUME IV – MODEL CONTRACT
8.1 GENERAL INSTRUCTIONS
The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The Offeror’s proposal shall include one (1) signed and dated copy of the Standard Form (SF) 1449, delivered with the SF1449 Continuation pages, the Addendum, the Contract Documents, and Exhibits and Attachments. The original should be clearly marked and should be provided without any punched holes. The SF1449 shall not have any proprietary markings.
Fill in all blanks in the Solicitation. Specifically, complete the following:
8.2 SF1449 SOLICITATION/CONTRACT FORM
The Offeror shall complete blocks 12, 17, and 30 on the Standard Form (SF) 1449 – Solicitation/Contract/Order for Commercial Items. The Offeror shall use the SF 1449 Continuation in place of completing blocks 19, 20, 21, 22, and 23. The signature by the Offeror on the SF1449 constitutes an offer, which the Government may accept. The “original” copy shall be clearly marked under separate cover and shall be provided without any punched holes.
8.3 SF1449 CONTINUATION SUPPLIES OR SERVICES AND COSTS/PRICES:
The Offeror shall provide prices on all CLINs except for CLIN 9000, which is not separately priced.
8.4 ADDENDUM
For SMC – H005 QUICK REACTION AND ANOMALY RESOLUTION, the Offeror must propose a fixed price composite hourly rate.
8.5 CONTRACT DOCUMENTS, EXHIBITS AND ATTACHMENTS
8.5.1 ATTACHMENT 3: SUBCONTRACTING PLAN
The Offeror shall provide a subcontracting plan in accordance with FAR 52.219-9 and AFFARS 5319.704, which must include an established goal for small business with a minimum participating level of 4% of the total contract value. This plan will become an attachment to the contract.
8.5.2 ATTACHMENT 8: GOVERNMENT PROPERTY
If the Offeror requires the use of GP, the Offeror shall complete and submit Attachment 8, Government Property, in accordance with procedures and definitions detailed in DFARS 245.103-72 and 245.201-70. For more information, see the DoD Procurement Toolbox at http://www.dodprocurementtoolbox.org/site/detail/id/26. Failure to complete each applicable data field in Attachment 8 may render the Offeror non-responsive and unawardable. For each item of GP requested, the “Use As Is” column shall be filled in as “true.”
For each item of GP requested, the Offeror shall provide a written authorization of availability from the cognizant Administrative Contracting Officer (ACO). GP proposed without an authorization from the cognizant ACO may render the Offeror non-responsive and unawardable. All supporting documentation associated with GP shall be submitted outside of the model contract but within Volume IV.
8.5.3 ATTACHMENT 9: PAYMENT PLAN
The Offeror shall fill in the dollar amount associated with each payment milestone in Table 1 of Attachment 9, Payment Plan. This plan will become an attachment to the contract.
8.5.4 POTENTIAL ORGANIZATIONAL CONFLICT OF INTEREST (OCI)
1. In accordance with FAR 9.5, Organizational and Consultant Conflicts of Interest, the Contracting Officer has analyzed the planned acquisition and determined that no known actual or potential OCI situations exist with respect to this solicitation.
2. The Offeror shall perform its own OCI analysis and submit the results of that analysis as part of its proposal. Specifically, the Offeror shall analyze the planned acquisition for actual or potential OCI situations associated with its or any of its teammate’s or subcontractor’s performance under any contract it or any of its teammates or subcontractors has been or may be awarded by any federal agency or other entity. The Offeror shall describe in detail the methodology used to identify actual or potential OCI issues. If the Offeror identifies any actual or potential OCIs with respect to the performance of itself or its subcontractors or teammates, the Offeror shall provide an OCI Mitigation Plan to be incorporated as Attachment 10 to any resulting contract. At a minimum, the plan shall address all of the items identified in the most current version of SMC’s OCI Mitigation Plan Checklist provided in the Bidder’s Library. Any proposed avoidance or mitigation techniques shall be consistent with FAR 9.5 and the most recent decisions of the Government Accountability Office and the U.S. Court of Federal Claims.
3. If award is made to the Offeror, the resulting contract may include an organizational conflict of interest limitation applicable to subsequent Government work, at either a prime contract level, at any subcontract tier, or both. During evaluation of proposals, the Government may, after discussions with the Offeror and consideration of ways to mitigate or avoid identified actual or potential conflicts of interest, insert a clause or term and condition in the resulting contract which disqualifies the Offeror from further consideration for award of future contracts.
4. Resolution of OCI issues are treated in a manner similar to the Contracting Officer’s contractor responsibility determination. Any communications necessary to resolve OCI issues shall not be considered discussions. As such, the Contracting Officer may issue Evaluation Notices to the Offeror prior to any decision to enter into discussions in order to resolve questions or concerns with the Offeror’s OCI analysis or mitigation plan.
8.6 SOLICITATION PROVISIONS
All representations and certifications must be completed in accordance with FAR 52.212-3, Offeror Representations and Certifications- Commercial Items.
8.7 SIGNATURE
The Offeror’s signature on the SF 1449 constitutes an offer, which the Government may or may not accept. Proposals without signatures may warrant a rejection of the proposal submittal. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements. Therefore, any tailoring to the solicitation is not allowed and may warrant a rejection of the proposal.
Appendix A – Schedule Basis Template
Task/Summary Task ID Number:
Task Summary Task Title:
Task Start-Stop Date:
Task Activity Duration (Calendar Days):
Task/Activity Description
Duration and Level of Effort Basis or Rationale
File details come from the government source that posted it. Updated .