Draft Section L.pdf
PDF 658 KB Posted
- Attached to
- Rocket Systems Launch Program Mission Assurance (RSLP MA) DRAFT RFP FOR COMMENT Federal contract opportunity
- Solicitation number
- FA8818-18-R-0003
About this file
This document is a request for comments on a draft Request for Proposal for the Rocket Systems Launch Program Mission Assurance contract. The key details are as follows:
The Air Force is seeking industry feedback on the draft RFP to improve its quality prior to a planned release on March 1, 2020. Feedback is requested on evaluation criteria, fee structure, incentives, the draft Performance Work Statement, Contract Data Requirements Lists, adequacy of proposal preparation time and information. The contract involves systems engineering, risk management, technical analysis, verification and validation, and quality assurance for launch programs as well as logistics planning for assets like motors. Interested parties can access the Bidders' Library containing necessary reference documents by requesting it from the Contracting Officer by February 11. The small business set-aside contract involves services for the Department of the Air Force Space Command.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Draft Section M.pdf | ||
| Draft Model Contract FA8818-18-R-0003.pdf | ||
| RSLP MA draft RFP CRM.xlsx | XLSX spreadsheet | |
| Draft Section J Exhibits (CDRLs).pdf | ||
| Draft Section J Attachments.pdf |
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
PART IV – REPRESENTATIONS AND INSTRUCTIONS
SECTION L – INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS
SECTION L
Section L RSLP Mission Assurance Information to Offerors
And Instructions for Proposal Preparation
Basic: 15 Jan 2020
REVISION HISTORY
REVISION DATE SECTION AFFECTED COMMENTS
DRAFT 15 Jan 2020 N/A N/A
INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS
Program Structure and Objectives:
1.1 General Requirements: Rocket System Launch Program Mission Assurance (RSLP MA) will provide Mission Assurance (MA) services after the expiration of the current Launch Services Mission Assurance (LSMA) contract on 13 June 2020. The purpose of this acquisition is to provide MA services for the Space and Missile Systems Center (SMC), Launch Enterprise (ECL), Small Launch and Targets Division (ECLX) procured space launch and suborbital missions, as well as for Decommissioned Excess Ballistic Missile (DXBM) activities. This acquisition will result in a single award Indefinite Delivery / Indefinite Quantity contract (IDIQ) with a maximum ordering period of nine (9) years. The proposed contract includes a basic ordering period of five (5) years with four (4) one-year option periods.
1.2 Initial Minimum Award: A minimum initial award Task Order (TO), represented by Task Order Information Document 0001 (TOID 0001) will be issued which will consist of program and cost management functions necessary for the overall daily operation of the entire contract function (referred to as the Core Effort) for the basic ordering period. Additional one-year options for these functions may be exercised for continued performance of the contract up to a total of a 9 year ordering period. Task Orders will be issued for all additional work as needed to meet funded program requirements in accordance with the Rocket Systems Launch Program Mission Assurance Task Order Ordering Guide, Attachment 3 to the basic contract.
1.3 Task Order Information Documents and Aging Surveillance Testing Recommendation Scenario: The Government has provided six (6) Task Order Information Documents (TOIDs) in Appendix A for Offerors to reference when preparing their Technical and Cost volumes.
Documents referenced in these TOIDs (i.e., Mission Requirements Documents (MRD’s) and PWS documents from RSLP’s launch contracts) are available in the Bidder’s Library. Task orders for one, all, none or any combination of the TOIDs may be awarded within six (6) months of award of the basic contract depending on funds availability and mission requirements. Offerors must also respond to TOIDs 4 and 6 with sample presentations that will be used in determining the Offeror’s capabilities. Failure to respond to all elements described in section 4 is considered a failure to meet a material requirement of the solicitation and may be grounds for elimination from the competition.
The Government has also provided notional data on the status of select elements of its DXBM fleet, as well as a notional Aging Surveillance (AS) testing budget in Appendix B. Interactive Excel Spreadsheets to be used to complete the Test Plan recommendation are provided in the Bidder’s Library (copies of the format are provided in Appendix B). Offerors will be expected to respond with a recommendation for the AS Testing Plan for the coming years. Failure to include any of these elements in the Offeror’s proposal is considered a failure to meet a material requirement of the solicitation and will be grounds for elimination from the competition.
1.4 RSLP Mission Forecast: Table 1 below reflects the projected launch mission workload for this contract, including option years. It is cross referenced by RSLP’s launch programs: Orbital Services Program (OSP-4) and the two Small Rocket Programs (SRP-4 and SRP-O). It also provides the anticipated MA Category for each mission. This information is being provided for informational purposes only and should not be construed as a guaranteed number of mission TOs to be awarded.
Table 1 - Projected Number of Launch mission awards by Program/MA Category
General Instructions: The Offeror's proposal must include all data and information requested in this document and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the PWS, Contract Data Requirements List (CDRL), and solicitation. Non-conformance with the instructions provided in this document may result in an unfavorable proposal evaluation and/or a determination that the proposal is unawardable.
Proposals shall be unclassified and no classified information will be accepted in response to this solicitation.
The Offeror’s proposal shall consist of a written submittal. All information provided, as long as it is consistent with the constraints of this RFP (e.g. page limitations), is subject to evaluation as described in Section M. To assist Offerors with proposal preparation and evaluation respectively, a Section L/Section M cross-reference matrix applicable to the Technical Volume is provided at Appendix C.
The proposal shall be clear and concise, and 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 provide convincing rationale to address how the Offeror intends to meet the requirements. Elaborate brochures, corporate background and promotional/marketing-type information, detailed artwork, or other embellishments are unnecessary and are not desired. All claimed technical, management, performance, and schedule capabilities to meet Government requirements shall be realistic and are subject to verification by the Government. For the purpose of this solicitation, the Offeror shall assume that the Government has no prior knowledge of its facilities, capabilities, and experience. The Government will not assume the Offeror will do anything that is not expressly stated in its proposal.
The proposal acceptance period is specified in Block 12 of Section A of the solicitation. The Offeror’s proposal shall make a clear statement within the Executive Summary that the proposal is valid through this date. In accordance with FAR Subpart 4.8 (Government Contract Files), the
Government will retain one electronic copy of all unsuccessful proposals. The Government will destroy all extra copies of unsuccessful proposals.
2.1 General Information
2.1.1 Point of Contact: The Procuring Contracting Officer (PCO), Alicia Cawley, is the sole point of contact for this acquisition. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO at the address located in Block 7 of Section A.
2.1.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. Offerors excluded from the competitive range may request a preaward debriefing or they may request a post-award debriefing; however, Offerors excluded from the competitive range must make their request within 3 days of notification of the exclusion from competitive range in either case, and are entitled to only one debriefing. The PCO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Within 3 days of notification, unsuccessful Offerors may request a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.
2.1.3 Discrepancies: If an Offeror believes that the requirements in these instructions contain an error, 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. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.
2.1.4 Electronic Reference Documents: Referenced documents for this solicitation are available at https://beta.sam.gov/ or the bidder’s library (available from the PCO upon request). Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. In order to complete portions of this solicitation, Offerors must request the bidder’s library from the PCO.
2.1.5 Communication: Exchanges of source selection information between Government and Offerors will be controlled by the PCO. Source selection information may be transmitted in person or via email, certified mail, delivery service, or facsimile (facsimile number will be provided to Offerors after submittal of proposals, as necessary).
2.1.6 Notification to Offerors: In accordance with FAR 52.232-18, funds are not presently available for this effort. No award will be made under this solicitation until funds are available.
The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an Offeror for any costs.
2.1.7 Discussions: The Government reserves the right to award without discussions. However, if it is in the Government’s best interest to hold discussions, then the Government may conduct discussions with Offerors after establishing a competitive range of the most highly rated proposals based on the ratings of each proposal against all evaluation criteria.
https://beta.sam.gov/
The Offeror’s Final Proposal Revision shall capture any information provided in responses to Evaluation Notices (ENs) that impact the Offeror’s proposal. The Government reserves the right to incorporate a “strength” process or feature as a requirement into the awarded contract.
2.1.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.
2.1.9 Cost or Pricing Data: The contracting officer has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the contracting officer will review this determination and if, in the contracting officer's opinion, adequate price competition exists, no additional cost information will be requested and certification under FAR 15.406-2 will not be required. However, if at any time during this competition the contracting officer determines that adequate price competition does not exist, Offerors may be required to submit information to the extent necessary for the contracting officer to make determination of a fair and reasonable price.
2.2 Organization/Format/Number of Copies/Page Limits: The Offeror shall prepare the proposal as set forth in Table 2, Proposal Organization. The Offeror shall submit all volumes in hard copy (physical printed paper) as well as electronic format, using recordable Compact Discs (CDs) or Digital Versatile Disk Read Only Memory (DVD ROM). Only one hard copy of the proposal shall be submitted. The content and the page size of hard copies must be identical to the electronic copies. Each electronic volume shall be on a different CD or DVD ROM. The volume number and title shall be indicated on each CD or DVD-ROM. Use separate files to permit rapid location of all portions, including subfactors, appendices, annexes, and attachments, if any.
The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2016, MS Office Excel 2016, MS Office Project 2016, or MS Office Power Point 2016, as applicable.
The contents of each proposal volume are described in the table below:
Table 2 - PROPOSAL ORGANIZATION
VOLUME Section L Paragraph
VOLUME TITLE /
SECTION
PAGE LIMIT
0 3.0 EXECUTIVE
SUMMARY 3
I 4.0
FACTOR 1:
COMBINED
TECHNICAL/RISK
I 4.2.3 Subfactor 1:
Core/DXBM 46 Total
VOLUME Section L Paragraph
VOLUME TITLE /
SECTION
PAGE LIMIT
I 4.2.3.1 Core Effort (TOID 0001) 8
I 4.2.3.3 DXBM AS Test Recommendation Scenario (Sect L, App B)
I 4.2.3.4 DXBM Sustainment
(TOID 0002) 5
I 4.2.3.5 DXBM Aging Surveillance
(TOID 0003) 20
I 4.2.4 Subfactor 2:
Launch IV&V
115 Total
I 4.2.4.1 STP-XS1* Kickoff Presentation (TOID 0004) 50 Slides
I 4.2.4.2 STP-XS1 Mission IV&V
(TOID 0004) 5
I 4.2.4.3 RSCD** Mission IV&V
(TOID 0005) 5
I 4.2.4.4 HTVI Mission IV&V
(TOID 0006) 5
I 4.2.4.5 HVTI*** Final Presentation (TOID 0006) 50 Slides
II 5.0 FACTOR 2:
COST Unlimited
III 6.0 Contract Documentation Unlimited
Notes: Refer to https://beta.sam.gov/ for actual date and time of submission deadlines.
All proposal volumes/documents are due 30 days after RFP release.
* Space Test Program Experimental Spacelift (STP-XS1) **Hypersonic Vehicle Test Initiative (HVTI) ***Rapid Space Capability Demonstration (RSCD)
2.2.1 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. If the Government https://beta.sam.gov/ determines that it is necessary to conduct discussions, page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. During Final Proposal Revision, the specified page limits for ENs will not affect the page limitations as set forth in Table 2. Unless otherwise specified, each page shall be counted except the following:
cover pages, tables of contents, tab/divider sheets, glossaries, correlation matrixes, and technical appendices. A list of tables and drawings should not be included in the proposal.
2.2.2 Page Size and Format (applicable to page-count-limited sections only):
2.2.2.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 x 11 inches, not including foldouts. Pages shall be single spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point font. 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. If the Government determines that it is necessary to enter into discussions, these page size and format restrictions shall also apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.
2.2.2.2 For presentation material required in 4.2.4.1 and 4.2.4.5, a Slide is defined as a single slide in Microsoft PowerPoint or equivalent software. Slides shall be in standard (4:3) size. The text size on slides shall be no less than 14 point. The “Notes” section of each slide will not be considered as part of the Offeror’s proposal and therefore should not include any information. If information is included in the “Notes” section, these slides may be removed before evaluation. Slides shall be numbered sequentially within each presentation. If the Government determines that it is necessary to enter into discussions, these slide size and format restrictions shall also apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.
2.2.2.3 Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems, layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. For tables, charts, graphs and figures, the text shall be no smaller than 12 point. These limitations shall apply to both electronic and hard copy proposals.
2.2.3 Cost or Pricing Related Data: Cost information should be included in the Cost/Price volume only.
2.2.4 Classified Information: Do not include classified information in proposals.
2.2.5 Cross Referencing: To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with minimal 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 cross-referencing conserves space without impairing clarity.
2.2.6 Indexing: Each volume shall contain a table of contents to delineate the sections within that volume.
2.2.7 Glossary of Abbreviations and Acronyms: Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.
2.2.8 Binding and Labeling: Each hard copy (physical printed paper) volume of the proposal shall be separately bound in a three-ring, loose leaf binder(s) permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each book, clearly mark the volume number, title, solicitation identification, and the Offeror's name.
The same identifying data should be placed on the spine of each binder. 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.
2.3 Distribution: The proposal shall be addressed to the PCO and mailed or hand carried to:
SMC/PKT-KT
Attn: Alicia Cawley 3548 Aberdeen Ave Kirtland AFB, NM 87117
Proposals received after the date and time specified shall be treated in accordance with
FAR 52.215-1.
Volume 0 – Executive Summary
3.1 Offeror Information: Identify the corporate name, correspondence address, Commercial and
Government Entity (CAGE) program code, NAICS code(s), and contact information to include phone number and email address for POCs authorized to discuss the Offeror’s proposal terms with the Government’s contracting officer. Include substantiation that the Offeror currently meets the Small Business criteria, including any applicable Small and Disadvantaged Business designations available.
3.2 Narrative Summary: Executive summary material will not be evaluated or considered as meeting the requirements for any portion of other volumes of the proposal. DO NOT INCLUDE ANY COST INFORMATION IN THE EXECUTIVE SUMMARY. The narrative summary of the entire proposal should characterize the Offeror’s technical approach in a concise fashion, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The Offeror shall provide the following information:
3.2.1 DXBM Technical Approach Summary: Provide a summary characterizing the technical approach for providing DXBM support.
3.2.2 Launch IV&V Technical Approach Summary: Provide a summary characterizing the technical approach for providing IV&V of orbital and sub-orbital launches.
3.2.3 Teaming Arrangements: Identify any contractor teaming arrangements that you plan to employ in the conduct of this effort. Provide a list of teaming partners, their participating divisions and locations, and a description of the work for which each is responsible.
3.3 Non-Governmental Advisors: Per DoD Source Selection Procedures paragraph 1.4.5.2.1, the PCO must ensure that before a non-government advisor is given access to proprietary information, that the Government has received the consent of the submitting contractor(s) to provide access to the contractor who is to assist in the source selection. Therefore, the Offeror shall expressly state in the Executive Summary (Volume 0) if there are any objections/restrictions on the release of its proposal information to The Aerospace Corporation, who will be acting as non-government advisors, as well as explanation of the parameters of those restrictions.
3.4 Table of Contents: A Table of Contents is not required for Volume 0
3.5 Completed L/M Reference Matrix: The Government has provided an L/M Cross Reference
Matrix at Appendix C, with the first 3 columns completed to identify a) Section L Technical Volume Tab requirements to b) Section M Evaluation Criteria and c) associated PWS paragraphs. The Offeror should complete the last column of the L/M Cross Reference Matrix at Appendix C, to identify d) where in their proposal that Proposal Tab is located. This appendix is used only to provide the Government team with a reference to where the Offeror has placed the required information, to assist with the evaluation process only, and will not be evaluated and does not count against the page count.
Volume I (Factor 1) - Technical Volume:
4.1 General: The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. The Offeror’s response will be evaluated against the technical evaluation criteria defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible, the actual methodology you would use for satisfying all of the requirements included in this solicitation. All the requirements specified in the solicitation are mandatory. By submitting a proposal, the Offeror is representing that their firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in the Offeror’s proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.
4.2 Format and Specific Content: The basic tasks covered by this RFP are to provide technical support for DXBM motors and Launch IV&V services for spacelift and/or suborbital launch services.
The Technical volume shall be organized according to the following tab outline, in accordance with the content instructions which follow:
(1) Table of Contents
(2) Glossary
(3) Subfactor 1: Core/DXBM
(a) Core Effort (TOID 0001)
(b) DXBM AS Test Recommendation Scenario (Appendix B)
(c) DXBM Sustainment (TOID 0002)
(d) DXBM Aging Surveillance (TOID 0003)
(4) Subfactor 2: Launch IV&V
(a) STP-XS1 Kickoff Presentation (TOID 0004)
(b) STP-XS1 Mission IV&V (TOID 0004)
(c) RSCD Mission IV&V (TOID 0005)
(d) HTVI Mission IV&V (TOID 0006)
(e) HVTI Final Presentation (TOID 0006)
4.2.1 Table of Contents: The Table of Contents should provide only section headings and page numbers; it is not required to identify tables or figures. The Table of Contents will not be counted against the page count.
4.2.2 Glossary: The Glossary should only identify terminology and/or acronyms that are specific to the Offeror’s proposal. It is not necessary to define terms or acronyms used in the RFP. The Glossary will not be counted against the page count.
4.2.3 Subfactor 1 – Core Effort/DXBM:
4.2.3.1 Core Effort Key Positions and Program/Cost Management Approach – The
Offeror shall provide a narrative to identify the positions that are key to fulfilling the Core Effort requirements that specifically address the following (PWS 3.2):
- The Title, Location and Minimum Qualifications/Expertise of each key position proposed and explanation of why these roles are key to managing the entire effort,
- Define the role of each Key Position in Program and Cost Management.
- The Offeror's approach to and understanding of how to ensure availability of personnel at contract start, retain personnel, and identify and hire new personnel.
- The Offeror's approach of how to ensure that staffing is adequate to perform Mission Assurance for multiple launches concurrently (reference Table 1 for RSLP’s projected launch schedule), with varying degrees of complexity and performance schedule fluctuations.
- The Offeror's approach of how to ensure that all personnel maintain the technical proficiencies/certifications required to knowledgeably perform the requirement.
NOTE: The Offeror’s proposal which results in award, will contain the key positions and related information in the resultant contract’s PWS.
4.2.3.2 DXBM Aging Surveillance Test Recommendation Scenario: The Offeror shall describe their approach to developing recommendations for a 5-year Aging Surveillance (AS) test plan that ensures DXBM motors are safe to store, supports flight worthiness certification for identified launches, and takes into account the information and constraints provided by the Aging Surveillance Test Recommendation Scenario provided at Appendix B.
The Offeror’s proposal shall contain the following:
A completed Table B-1, showing the Offeror’s recommended AS test plan, as described in Appendix B paragraph a.
A completed Table B-2, showing the Offeror’s Useful Life Estimates, as described in Appendix B paragraph b.
Narrative describing technical approach and methodologies, as described in
Appendix B, paragraph c.
4.2.3.3 DXBM Sustainment: The Offeror shall describe their approach for executing the
Sustainment efforts as prescribed in TOID 0002 in Appendix A. The requirements for this proposal are detailed in the TOID. These are stand-alone requirements and should not be confused with or reflect the Offeror’s recommendation provided in paragraph
4.2.3.2 above. The Offeror must specifically address PWS paragraphs 3.4.1.3, 3.4.1.7, 3.4.1.9, 3.4.1.12, and 3.4.1.13.
4.2.3.4 DXBM Aging Surveillance: The Offeror shall describe their approach for executing the Aging Surveillance effort as prescribed in TOID 0003 in Appendix A. The requirements for this proposal are detailed in the TOID. These are stand-alone requirements and should not be confused with or reflect the Offeror’s testing recommendation provided in paragraph 4.2.3.2 above. The Offeror must specifically address PWS paragraph 3.4.2.4.
4.2.4 Subfactor 2 - Launch IV&V:
4.2.4.1 STP-XS1 Kickoff Presentation: The Offeror shall provide a sample launch IV&V
Kickoff Presentation for the STP-XS1 Mission described in TOID 0004, Appendix A.
The sample should communicate the intended format and include content reflecting the Offeror’s proposed approach. The presentation shall constitute a sample of the brief described in PWS paragraph 3.3.2.25.1 subparagraphs 1-5 and 7-9.
4.2.4.2 STP-XS1 Mission IV&V: The Offeror shall describe their approach for executing the effort as prescribed in TOID 0004, Appendix A. Within this description, the Offeror must specifically address their planned methodology for conducting the Knowledge Development Gap Analysis required by PWS paragraph 3.6.2.
4.2.4.3 RSCD Mission IV&V: The Offeror shall describe their approach for executing the effort as prescribed in TOID 0005, Appendix A. Within this description, the Offeror must specifically address their planned methodology for ensuring that lessons learned that are specifically related to MA on rapid launch activities will be gathered in support of the Concept Analysis required by PWS paragraph 3.5.
4.2.4.4 HVTI Mission IV&V: The Offeror shall describe their approach for executing the effort as prescribed in TOID 0006, Appendix A. Within this description, the Offeror must specifically address their planned methodology for supporting Flight Motor Refurbishment and Processing for the M55, SR19, and SR73 motors as well as Ground Test Motor processing for the M55 and SR73 motors as described in PWS paragraphs 3.3.5.1, 3.3.5.14, 3.3.5.15, 3.3.5.18, 3.3.6.1, and 3.3.6.6.
4.2.4.5 HVTI Final Presentation: The Offeror shall provide a sample launch IV&V Final Review for the mission described in TOID 0006, Appendix A, which communicates the intended format and includes content reflecting the Offeror’s proposed approach.
The sample shall specifically contain the content required of this brief in PWS paragraph 3.3.2.25.3.
For the purpose of this evaluation: The Offeror should assume that the LSC provided the necessary information to support IV&V. Notional or previous data/results may be used to illustrate the Offeror’s intended approach to meeting the requirements and communicating the outcome of their IV&V efforts.
Also for the purpose of this evaluation: Incorporate the following three residual risks:
The first residual risk is a qualification test that could not be completed for a flight safety system battery.
The second residual risk is for a sibling failure related to the second stage engine, which failed to initiate on a prior space launch mission, resulting in loss of mission.
The third residual risk is for the results of a mission assurance contractor-run Monte Carlo simulation for structural integrity of a second stage oxidizer tank.
MAC results don’t agree with the LSC’s analysis for the same component and indicate less margin.
Volume II – (Factor 2) – Cost
5.1 General Instructions: The Cost Factor volume shall contain the information requested in the paragraphs below. The Offeror shall submit other-than-certified cost or pricing data (per FAR 15.403-1(b), 15.403-3(a), and FAR 15.403-5) for the Government evaluation. The proposal must contain sufficient details for the Government evaluation of reasonableness, realism, and unbalanced pricing for the Government’s calculation of the Most Probable Cost which will become part of the Total Evaluated Price for the best value decision. The burden of proof for cost credibility of proposed costs rests with the Offeror. Compliance with these requirements is mandatory and failure to comply may result in a determination of non-compliance and/or rejection of the Offeror’s proposal. Unreasonably high and unrealistically low proposed costs or prices may be grounds for eliminating a proposal from the competitive range either on the basis that the Offeror does not understand the requirement or, that the Offeror has made an unrealistic proposal. Offerors shall submit the electronic copy of this volume in an unprotected .XLS file format with working formulas. Use of contractor formats is encouraged, provided that all the required data is made available. This information is not considered certified cost or pricing data and thus certification is not required in accordance with FAR 15.406-2. If, after receipt of proposals, the PCO determines that there is insufficient information available to determine price reasonableness and none of the exceptions at FAR 15.403-1 apply, the Offeror shall be required to submit additional cost or pricing data. The CLIN structure of the IDIQ is provided in Table 3 below.
Table 3 - IDIQ Contract Line Item Number (CLIN) Structure CLIN CLIN Description CLIN Contract Type 0001 Core Effort (CY1-CY5) CPIF 0003 Mission Support CPIF 0005 Logistics Support CPIF 0007 Concept Analysis CPFF 0009 Knowledge Development CPIF 0011 Transition CPIF
0013 Core Effort - Option
(CY6) CPIF
0015 Core Effort - Option
(CY7) CPIF
0017 Core Effort - Option
(CY8) CPIF
0019 Core Effort - Option
(CY9) CPIF
*Note: CY refers to contract year.
5.2 Volume Organization: The Cost Volume shall consist of the following sections, organized into tabs:
1. Table of Contents
2. Narrative
3. Labor Category Requirements
4. Task Order Rates for the basic IDIQ ordering period
5. TOID 0001 through 0006 Cost Element Summaries, including CLIN pricing as outlined in the
TOIDs. (Basis of Estimate)
6. Total Evaluated Price Table (TOID 0001(basic and all option years) and TOIDs 0002-0006)
5.3 Cost Detail:
5.3.1 Table of Contents: Provide a detailed table of contents for this volume. Provide a glossary of all abbreviations and acronyms used, with an explanation for each. However, use of abbreviations and acronyms should be limited. Provide definitions as necessary.
5.3.2 Narrative: As an introduction, the Offeror shall provide comprehensive narrative support for the Cost proposal in the Cost volume explaining the philosophy, methodology, and assumptions used in proposing the dollar amounts. Please include summary descriptions of estimating, purchasing, and accounting systems. Provide a summary description of your standard estimating system or methods, current policies, and/or new policies. State whether you have Government approval of your estimating system and if so, provide evidence of such approval. Provide any known/cited estimating system deficiencies. Also, identify any deviations from the Offeror’s established/standard estimating procedures used in preparing this proposal.
5.3.3 Labor Category Requirements and Task Order Rates Table: Identify each labor category to be used in the execution of the contract, and identify any education and experience requirements for the labor category. Provide direct and indirect costs to support fully burdened labor rates, for each labor category, for each year of the initial five-year ordering period (CY1-CY5) and each of the four option years, plus an additional two years to complete execution of all issued task orders, CY6, CY7, CY8, CY9, CY10, and CY11 using the format specified in Table D-1 in Appendix D, for the Prime Contractor as well as any teaming partners or applicable subcontractors.
5.3.4 Cost Elements Summaries: The Offeror shall provide a Cost Element Summary for TOID 0001(basic and all option years) and TOIDs 0002-0006, to include any applicable teaming partner’s and/or major subcontractors’ contributions. The TOIDs at Appendix A define the scope of PWS work and other specifics applicable to each task order required to complete the BoE, and the Cost Element Summary for each Task Order must correlate to and be traceable to the BoE for that Task Order. Task Order 0001 Core Effort is the minimum guaranteed award on the IDIQ contract. The Option Year Core Efforts are pre-priced options which the Government may exercise at its discretion upon completion of the initial Core Effort. The Government reserves the right to award one or more of the TOIDs within 6 months of IDIQ contract award as RSLP and/or customer Government Agency funding allows.
Task Order 0001 – Core Effort (CLIN 0001, CLIN 0013, CLIN 0015, CLIN 0017 and
CLIN 0019)
Task Order 0002 –DXBM Sustainment (CLIN 0005) Task Order 0003 –DXBM Aging Surveillance (CLIN 0005) Task Order 0004 - STP-XS1 Mission IV&V (CLIN 0003 and CLIN 0009) Task Order 0005 - RSCD Mission IV&V (CLIN 0003) Task Order 0006 - HVTI Mission IV&V (CLIN 0003 and CLIN 0007)
5.3.4.1 The Cost Element Summary must show at least the following information, as applicable: Labor hours and dollars, indirect labor costs (e.g. fringe, overhead, G&A), materials, travel, other direct costs (identify components making up other direct costs), Facilities Capital Cost of Money (FCCOM), and profit/fee. The format should be base times rates equals dollars, by Offeror’s accounting year, and consistent with the Offeror’s rate structure. Offeror’s accounting year is the 12-month period in which the company’s rates are defined (e.g., Oct-Sep, Jul-Jun, or Jan-Dec). The Offeror shall define the time period for the company’s accounting year. The Offeror shall provide adequate explanation for each proposed cost element. The base upon which the rate is applied should be clearly traceable and explained. Submit the Cost Element Summaries, in MS Excel, with working formulas. Table D-2 is provided as an example cost element summary in Appendix D.
5.3.4.2 Basis of Estimate (BoE): Provide a BoE for each of TOID 0001(basic and all option years) and TOIDs 0002-0006, to include any applicable teaming partner’s and/or major subcontractors’ contributions, and projecting the effort required to execute that approach. The Offeror must inform their BoE with the provision of a Contract Work Breakdown Structure (CWBS) to serve as the framework for organizing tasks to include in-house, inter-divisional, subcontractor, and associate contractor activities.
Details for what should be provided in the CWBS is described below. The BoE and CWBS will assist the Government with understanding the Offeror’s estimation approach and demonstrate the Offeror’s approach in terms of the scope of work required for each TOID. The BoE inform the cost evaluation and assist in the realism determination.
The Offeror shall provide the BoE for each effort proposed, broken out to the CWBS level at which the BoE was developed. The BoE shall use the CWBS designation/numbering system so that corresponding tasks for the effort proposed can be located in a CWBS Dictionary. Please ensure the hours in the Basis of Estimate (BOE) are fully and clearly traceable to the hours in the cost element summary, and provide visibility in how the bases for these cost elements were developed. The BOE shall clearly identify the types, quantities, skill mix of proposed labor hours, and detailed rationale and justification for the estimates used. The labor hours must be separated out by the different types of labor, and time-phased by Contract Year (CY).
Provide narrative to explain your BoE quantities. The narrative shall address how the Offeror estimated each major element of the effort and provide rationale for proposed hours and labor mix. Include all assumptions made. Where estimates are based upon past experience, identify the past experience, explain how the past experience relates to the current effort (including similarities and differences), and explain how data available from the past experiences was adapted to the current effort. Each BoE should complement and correlate to the relevant entries of the CWBS.
5.3.4.2.1 CWBS to Inform the BoE: The Offeror shall use the contents of the PWS to develop a CWBS for all efforts to reflect their view of the service to be provided.
The CWBS shall be developed to a depth and breadth sufficient to accurately describe the Offeror's understanding of the effort required for the specific service.
Typically, a CWBS is developed to Level 3. The CWBS only informs the BoE and will not be evaluated.
5.3.4.2.2 CWBS Dictionary: Each element of the CWBS shall be described in detail in a CWBS Dictionary. A complete definition of the tasks to be accomplished shall be provided in the CWBS Dictionary. Within the CWBS Dictionary the Offeror may specify internal document(s) that detail the work content associated with the task, in lieu of re-stating that detail in the CWBS itself. The Offeror shall provide a copy of each document referenced in a separate Appendix. The proposed CWBS dictionary shall not contain informational notes. The CWBS Dictionary only informs the CWBS and will not be evaluated.
5.3.4.2.3 CWBS Correlation Matrix: The Offeror shall provide a Correlation Matrix that cross references each paragraph of the PWS to the CWBS elements which address that PWS paragraph. This matrix shall be an Appendix of the Cost Volume and will not be counted towards the page count. An example of an entry in a correlation matrix is shown below in Table 4. The Correlation Matrix shall not contain informational notes, as the volumes provide ample opportunity for discussion and description of the Offeror's approach. The Correlation Matrix only informs the cost evaluation by assisting the evaluation team with vectors to the CWBS, and will not be evaluated.
Table 4 - EXAMPLE CORRELATION MATRIX
PWS CWBS Element
3.1.1
3.2.2 – Requirements Analysis
3.2.3 – Requirements Verification
3.1.2 3.2.4 – Requirements Validation
5.3.5 Cost Tables: The Offeror shall provide Cost tables for TOIDs 1-6 and Core Effort Options CY6-CY9 identifying the Target Cost and Fee for each effort, summed to develop proposed Target Costs. Table D-3 is provided as an example in Appendix D.
5.3.6 Total Proposed Price: The Offeror shall provide a Total Proposed Price (TPP) as the sum of proposed costs for TOIDs 1-6 and Core Effort Options CY6-CY9). Table D-4 is provided as an example in Appendix D.
5.4 General Guidance
5.4.1 Non-Required Data: Data beyond that required by this instruction should not be submitted, unless the Offeror considers it essential to document or support the Offeror’s price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price volume. Under no circumstances shall this cost/price data and documentation be included elsewhere in the proposal.
5.4.2 Cost or Pricing Information Requirements: In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness if, after receipt of proposals, the PCO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit additional cost or pricing data.
5.4.3 Other Direct Costs (ODC(s)): The Government shall include the amount estimated for travel and material in each TO.
5.4.4 Rounding: All dollar amounts provided shall be rounded to the nearest dollar.
Volume III Contract Documentation: The purpose of this volume is to provide information to the Government for preparing the contract document (and supporting file) and to assist in the contracting officer’s responsibility determination. Per FAR 9.103, the contracting officer must make an affirmative determination of the Offeror’s responsibility to make an award. Failure to meet a requirement as outline in this solicitation may result in a proposal being ineligible for award.
6.1 The Offeror's proposal shall include a signed copy of the contract form, and Sections A through K. This includes:
6.1.1 Section A – Solicitation/Contract Form: Completion of blocks 12, 14 (if applicable), 15A, 15B, 15C (if applicable), 16, and signature and date for blocks 17 and 18 of the Standard Form 33. Signature by the Offeror on the Standard Form 33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked.
6.1.2 Section K – Representations, Certifications, and other Statements of Offerors:
Completed representations, certifications, acknowledgements and statements shall be included in Volume III.
6.2 Small Business Contract Performance: The RSLP MA contract is a total small business set-aside. In accordance with 52.219-14(c)(1), the Offeror shall self-certify that it will not pay more than 50 percent of the amount paid by the Government for contract performance to subcontractors that are not similarly situated entities. Any work that a similarly situated entity further subcontracts will count toward the 50 percent subcontract amount that cannot be exceeded. All Offerors must complete the Small Business Contract Performance Table in Section L Appendix E demonstrating that they meet this requirement based on the TPP.
6.3 Professional Employee Compensation Plan: The Offeror and subcontractors/teaming partners who will be providing a meaningful number of total number of professional employees are required to submit a Professional Employee Compensation Plan (PECP) for all professional employee labor categories. The PECP submitted in response to the solicitation will be evaluated in accordance with FAR clause 52.222-46. The prime Offeror should instruct its subcontractors to submit their total compensation plan directly to the contracting officer. The prime Offeror shall also submit a list of subcontractors to include points of contact and phone numbers who will be submitting PECPs to the Government. The Compensation Plan will be relied upon as one of the elements in determining if an Offeror is responsible (IAW FAR 9.1) and will subsequently factor into the Contracting Officer’s determination of the apparent successful Offeror’s eligibility for award. The total compensation plan submitted in the proposal will not become part of the awarded contract.
The PECP should identify/provide:
a) The Standard Occupational Classification (SOC) code for each labor category using the
Bureau of Labor Statistics SOC system. The labor categories shall be identified by geographic location of contract performance. Provide the corresponding unburdened salary and quantified fringe benefits (e.g., a compensation, in addition to an employee’s regular wage and salary that includes vacation, sick leave, holidays, employee insurance) for each labor category.
b) The recent surveys and studies from professional, public, and private organizations (e.g., Watson & Wyatt, Economic Research Institute, Bureau of Labor Statistics, etc.) used to support the proposed salaries and fringes. Identify the source with the provided surveys and studies. If not suing one of the sources listed above, explain the credibility of the source selected for providing the surveys and studies.
c) Consistent information provided in the PECP(s). The Government expects the information to be consistent. If the information is inconsistent, the contractor shall explain the difference and provide reasons as to why the inconsistency should be accepted by the Government. The Offeror is also responsible for demonstrating that the proposed unburdened salaries and quantified fringe benefits are reasonable and well supported.
6.4 Exceptions to Solicitation Requirements: Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation criteria. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Since the Government intends to award without discussions Offerors are advised that taking exception to any of the requirements specified in this solicitation may result in the proposal being found unacceptable without clarification. The Government recommends that clarification of any requirements or notice of any contractor exceptions or assumptions be handled by submitting a question/recommended change prior to proposal submittal. All assumptions/clarifications must be finalized prior to Final Proposal Revisions, if there are discussions conducted. If the Offeror still finds it necessary to take exception to any of the requirements specified in this solicitation, clearly indicate each exception in the appropriate volume along with a complete explanation of why the exception was taken and what benefit accrues to the Government.
All exceptions to the solicitation requirements (Sections A through M, and all attachments) and supporting rationale shall be identified as such and consolidated into an overview section of the subject volume using the format and content of Table 5 below. An overview section is only required if the Offeror takes exception to any requirement in the solicitation. The overview section will not be included in the proposal page limitation.
Table 5 - Solicitation Exceptions Solicitation Document
Page/ Paragraph
Requirement/ Portion Rationale
PWS, MRD, L102,
etc.
Applicable Page and Paragraph Numbers
Identify the requirement or portion to which exception is taken
Describe why the requirement can/will not be met
6.5 Organizational Conflict of Interest Plan: 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 Organizational Conflict of Interest (OCI) situations exist with respect to this solicitation.
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 have 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 Organizational Conflict of Interest (OCI) Mitigation Plan to be incorporated as an attachment 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 as an attachment to this solicitation. 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.
If award is made to the Offeror, the resulting contract may include an OCI 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.
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.
6.6 Other Information Required:
6.6.1 Authorized Offeror Personnel: Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to the Offeror’s proposal and who can obligate the Offeror’s company contractually. Also, identify those individuals authorized to negotiate with the Government.
6.6.2 Government Offices: If the Offeror has other Government contracts, provide the mailing address, telephone and fax numbers, and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office.
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 .