FA8818-13-R-0021_LSMA_SecL.pdf

FA8818-13-R-0021

Section L

Clause L102 “Information to Offerors and

Instructions for Proposal Preparation”

1.0 Program Structure and Objectives

1.1 General Requirements - The Air Force Space and Missile Systems Center (SMC) anticipates award of a single contract to provide Launch Service Mission Assurance (LSMA) in support of US Government missions. This effort will be a competitive source selection. The annual requirement for the XBM Sustainment service is defined in the Performance Work Statement (PWS), with additional services defined in the PWS to be invoked on a mission-specific basis. Mission-specific information outlining the applicable PWS services will be defined in a Mission Information Document (MID) for each mission, and special study requirements are defined in a Special Study Requirements Document (SSRD) for each effort.

1.2 Offerors must propose services to meet all PWS requirements.

1.3 Sample Missions - The Government has provided a set of sample missions (Appendix A) for Offerors to propose against for evaluation. Each sample mission is identified by a MID, and each sample study is defined by an SSRD. The Government reserves the right to incorporate any or all of the sample missions and special studies in conjunction with the contract award.

1.4 Contract Process – Contracting for MA services is a three-step process:

1.4.1 The first step is the award of the initial contract to the Offeror with the best value LSMA solution. In conjunction with the initial award, the Government may include Contract Line Items (CLIN) for any or all of the Sample Missions or Special Studies.

1.4.2 The second step will occur after the award of the contract. At any time during the period of performance, the Government may exercise the option for an additional period of XBM Sustainment, or for the Transition effort.

1.4.3 The third step is the addition of additional efforts. At any time during the period of performance, the government may issue an RFP in accordance with Section H Technical Services Clauses to modify the contract to add an additional mission effort or special study. These future mods will be negotiated.

1.5 Options – Separate cost proposals for the basic XBM Sustainment award and each option XBM Sustainment period must be submitted. The successful Offeror may be awarded up to four Options for XBM Sustainment at the government’s discretion. At the conclusion of the last exercised XBM Sustainment effort, the government may exercise an additional option for a transition period during which the successful LSMA offeror will support transition of the contract to a follow-on effort.

Section L

2.0 General Instructions

2.1 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.

2.2 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/PWS/Section M cross-reference matrix applicable to the Technical Volume is provided at Appendix B.

2.3 The proposal shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government's requirements but rather 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 system(s), process(es), facility(ies) and experience, and will base its evaluation on the information presented in the Offeror's proposal.

2.4 Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

2.5 The proposal acceptance period is specified in Section A of the solicitation. The Offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

2.6 In accordance with 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.

2.7 General Information

2.7.1 Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Section A of the solicitation, not later than two weeks after release of the solicitation.

2.7.2 Debriefings

The CO 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 postaward 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 CO will notify unsuccessful Offerors in the competitive range https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b15505

Section L 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.7.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 CO in writing with supporting rationale as well as the remedies the Offeror is asking the CO 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.7.4 Electronic Reference Documents

Referenced documents for this solicitation may be available on the Federal Business Opportunities (FedBizOpps) website 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.

2.7.5 Oral Presentations

Oral Presentations will not be conducted for this acquisition.

2.7.6 Communications

Exchanges of source selection information between Government and Offerors will be controlled by the CO. Source selection information may be transmitted via certified mail, delivery service, or facsimile (facsimile number will be provided to Offerors after submittal of proposals, as necessary).

2.8 Organization/Number of Copies/Page Limits

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.8 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 2.8. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The technical appendices may be bound separately, if necessary.

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b15506 http://www.fedbizopps.gov/

Section L

The contents of each proposal volume are described in the paragraph as noted in the table below:

Table 2.8 - Proposal Organization

VOLUME L102

Paragraph

VOLUME TITLE /

Section

PAGE LIMIT

Due ~X Days After RFP Release

0 3.0 EXECUTIVE

SUMMARY 5 45

I 4.0 FACTOR 1:

TECHNICAL - -

I 4.2.3 Tab 3a: Subfactor 1 – TA; XBM Sustainment Engineering

25 45

I 4.2.4 Tab 3b: Subfactor 1 – TA; Launch System

IV&V

80 45

I 4.2.5 Tab 4a: Subfactor 2 – SPM; Management Approach

I 4.2.6 Tab 4b: Subfactor 2 – SPM; Transition Plan

I 4.2.7 Tab 4c: Subfactor 2 – SPM; Key Personnel

I 4.2.8 Tab 4d: Subfactor 2 – SPM; Efficiency Plan

I 4.2.9- 4.2.21

Tab 5: Technical Appendices Unlimited 45

II

5.3.1

FACTOR 2:

PAST PERFORMANCE

Summary

II 5.3.2 Past Performance Information Form

8 for each contract up to 5 contracts. Not to exceed a total of

40 pages.

II 5.3.2

Past Performance Information Form for Partners

8 (additional) for each partner contract, up to 3 contracts per partner, not to exceed a total of 48 pages for all partners.

II 5.3.3 Organizational Structure Change History Unlimited 30

II 5.4 PPQ Tracking Record Unlimited 30

II 5.5

OCI Identification and mitigation plan (if applicable)

Unlimited 30

III 6.0

FACTOR 3:

COST/PRICE

Cost/price Tables

Unlimited 45

IV 7.0 CONTRACT

DOCUMENTATION Unlimited 45

NOTE: All volumes shall be submitted with one paper copy and two electronic copies unless otherwise specified. Electronic copies must conform to the same requirements as paper copies.

* Refer to FedBizOpps for actual date and time of submission deadlines.

Section L

2.8.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 and excess paper copies will be returned to the Offeror as soon as practicable. 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.8. Unless otherwise specified, each page shall be counted except the following: cover pages, tables of contents, tab/divider sheets, glossaries, correlation matrix, technical appendices, past performance questionnaires, organizational structure change histories, consent forms and client authorization letters. A list of table and drawings should not be included in the proposal.

2.8.2 Page Size and Format (applicable to page-count-limited sections only)

2.8.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. 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. These limitations shall apply to both electronic and hard copy proposals.

2.8.2.2 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.

Foldout pages shall fold entirely within the volume, and each 8.5 x 11 inch surface of a foldout shall be counted as a separate 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 shall be no smaller than 8 point. These limitations shall apply to both electronic and hard copy proposals.

2.8.3 Cost or Pricing Related Data

Pricing information will not be included in Section B of the Schedule of the RFP. This information will be included in the Pricing Table which will be referenced in Section B.

Information shall be limited to the items specified in the Pricing Tables.

2.8.4 Classified Information

Do not include classified information in proposals.

2.8.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 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-

Section L referencing within a proposal volume is permitted where cross-referencing conserves space without impairing clarity.

2.8.6 Indexing

Each volume shall contain a table of contents to delineate the sections within that volume. Tabs/dividers are not required.

2.8.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.8.8 Binding and Labeling

Each 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 marked as to volume number, title, solicitation identification, and the Offeror's name. The same identifying data should 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.

2.9 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. In the event that hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

For electronic copies, indicate on each CD or DVD-ROM the volume number and title.

Use separate files to permit rapid location of all portions, including subfactors, appendices, annexes, and attachments, if any. The Offeror shall submit all volumes in electronic format, using recordable CDs or DVD ROMs. Each volume shall be on a different CD or DVD ROM.

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, MS Office Excel 2007, MS Office Project 2007, or MS Office Power Point 2007, as applicable. For Technical Appendices that provide artifact copies of previously existing material, Adobe PDF format is acceptable.

2.10 Distribution - Proposals shall be addressed to the CO and mailed or hand carried to:

SMC/PKTN

Attn: Steve Wells 3548 Aberdeen Ave Kirtland AFB, NM 87117 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.215.doc#b522151 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b31044

Section L

Proposals received after the date and time specified shall be treated in accordance with

FAR 52.215-1.

3.0 Volume 0 - Executive Summary

In the executive summary volume, the Offeror shall provide the following information:

3.1 Offeror Information

Identify the corporate name, correspondence address, CAGE 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

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

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) whether or not it consents to the release of its proposal information to The Aerospace Corporation, who will be acting as non-Government advisors.

3.4 Table of Contents

A Table of Contents is not required for Volume 0.

Section L

4.0 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 responses will be evaluated against the Technical subfactors 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 accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By the Offeror’s proposal submission, you are representing that the Offeror’s 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

This RFP contains the Government prepared PWS and an MID for each sample mission.

The basic tasks covered by this RFP are to provide XBM Sustainment Engineering and MA services for low cost space and/or suborbital launch systems/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: Technical Approach (TA)

(3a) XBM Sustainment Engineering (3a-1) XBM Refurbishment (3a-2) XBM AS and Sustainment Process (3a-3) XBM AS Requirements (3a-4) XBM AS Planning (3a-5) XBM AS Analysis (3a-6) XBM AS Reporting (3a-7) XBM Refurbishment Procedures (3b) Launch System IV&V (3b-1) Launch System IV&V Analysis (3b-2) Launch System IV&V Reporting (3b-3) Launch System Risk Assessment (3b-4) Launch System IV&V Tools (3b-5) Launch System Requirements IV&V (3b-6) Launch System Payload Integration Verification (3b-7) Launch System Range Integration Verification (3b-8) Launch System Interface Verification (3b-9) XBM Motor Utilization (3b-10) Sample Mission Proposals

(4) Subfactor 2: Service Performance Management (SPM) (4a) Management Approach (4a-1) Program Interface (4a-2) Lessons Learned Dissemination

Section L

(4a-3) ASCON Interface (4a-4) Fluctuation Management (4b) Transition Plan (4b-1) 90 Day Attainment (4b-2) PWS Readiness (4b-3) Incumbent Interchange (4b-4) Follow-on Interchange (4c) Key Personnel (4c-1) 5 Key Positions (4c-2) Key Personnel (4c-3) Key Personnel Location (4c-4) Transition Team (4d) Efficiency Plan

(5) Technical Appendices (5a) Correlation Matrix (5b) CWBS w/ CWBS Dictionary (5c) Basis of Estimates (5c-1) XBM Sustainment Engineering (5c-2.x) New Launch System IV&V Sample Missions (5c-3.x) Existing Launch System IV&V Sample Missions (5d) Integrated Schedules (5d-1) XBM Sustainment Engineering (5d-2.x) New Launch System IV&V Sample Missions (5d-3.x) Existing Launch System IV&V Sample Missions (5e) Sample IV&V Kickoff Presentation (5f) Sample IV&V Midterm Presentation (5g) Sample IV&V Final Review (5h) Completed L/M Cross Reference Matrix (5i) AS9100 Certification (if applicable) (5j) Sample Aging Surveillance Analysis (5k) Sample Refurbishment Work Package (5l) Copy of each document referred to in the CWBS dictionary (5m) Tailored Compliance Documents (refer to 7.3.4.3)

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 or defined in the CWBS Dictionary. The Glossary will not be counted against the page count.

4.2.3 XBM Sustainment Engineering

Section L

Describe your technical approach to meet the requirements of XBM Sustainment Engineering. Identify the anticipated challenges, issues, and risks associated with completion of the XBM Sustainment Engineering activities. This description should complement and correlate to the relevant entries of the schedule, WBS, and WBS Dictionary. The offeror should specifically identify any service enhancements inherent to the proposed solution which exceed threshold performance requirements.

4.2.3.1 XBM Refurbishment

Describe the refurbishment process and your approach to effectively support XBM motor refurbishment planning and oversee refurbishment implementation for AS motors in the context of the refurbishment process.

4.2.3.2 XBM AS and Sustainment Process

Describe your overall approach to ensuring effective aging surveillance and sustainment processes, including a methodology for developing reliable useful life estimates, maintaining XBM ordnance in flight qualified status, identification of associated equipment issues, and securing equipment certifications.

4.2.3.3 XBM AS Requirements

Describe your approach to development of efficient aging surveillance test and analysis requirements and identification of alternatives.

4.2.3.4 XBM AS Planning

Describe your approach to identifying and planning support for Government and associate contractor actions to implement effective aging surveillance.

4.2.3.5 XBM AS Analysis

Describe your approach to planning and performing analysis of aging surveillance data, including evaluation techniques for new test data and methods for comparison to historical aging data and previously identified trends.

4.2.3.6 XBM AS Reporting

Describe your approach for reporting of aging surveillance results.

4.2.3.7 XBM Refurbishment Procedures

Describe your overall approach to developing effective XBM motor refurbishment procedures, supporting procedure verification, and securing independent validation assessments.

4.2.4 Launch System IV&V

Describe the general solution proposed to accomplish IV&V of Launch Systems in accordance with the PWS. Identify the anticipated challenges, issues, and risks associated with completion of the IV&V activities. This description should complement, and correlate to, the relevant entries of the schedule, WBS, and WBS Dictionary, and minimize duplication of information presented in those artifacts. The offeror should

Section L specifically identify any service enhancements inherent to the proposed solution which exceed threshold performance requirements.

4.2.4.1 Launch System IV&V Analysis

Describe the approach to accomplish planning of IV&V analysis activities. The description should specifically address the types of analyses planned and the methods by which analysis results will be compared to verify the launch service contractor’s analyses.

4.2.4.2 Launch System IV&V Reporting

Describe the approach to accomplish reporting of results and conclusions from the relevant IV&V activities.

4.2.4.3 Launch System Risk Assessment

Identify the planned approach to overcome challenges, issues, and risks to provide an assessment of residual mission risks to inform launch campaign readiness decisions.

4.2.4.4 Launch System IV&V Tools

Identify the planned approach to develop and use appropriate tools and models to conduct the proposed analyses.

4.2.4.5 Launch System Requirements IV&V

Identify the approach to evaluate launch system compliance with customer, stakeholder and regulatory requirements.

4.2.4.6 Launch System Payload Integration Verification

Identify probable technical issues with payload integration and the approach to evaluate design of the launch vehicle interface with the payload(s) and verify payload integration.

4.2.4.7 Launch System Range Integration Verification

Identify probable technical issues with range integration and the approach to evaluate and verify effective and efficient launch vehicle integration with the range.

4.2.4.8 Launch System Interface Verification

Identify probable technical issues with system interfaces and the approach to evaluate the launch service provider’s interface controls.

4.2.4.9 XBM Motor Utilization

Identify probable technical issues with XBM motor utilization and the approach to effectively support XBM motor utilization on launch systems.

4.2.4.10 Sample Mission Proposals

Identify the unique challenges, issues, and risks associated with completion of the IV&V activities for the designated MA Category (or Construct 2) for each mission, and the planned approach to overcome these to validate system requirements and

Section L verify system compliance with requirements for the sample mission as described in each sample MID.

Section L

4.2.5 Management Approach

Describe the offeror’s Management Approach, including how the offeror plans to define and schedule work activities. This description should complement and correlate to the relevant entries of the schedule, WBS, and WBS Dictionary. The offeror should specifically identify any service enhancements inherent to the offeror’s Management Approach which exceed threshold performance requirements.

4.2.5.1 Program Interface

Describe the approach to reasonably and cooperatively interface with the program’s Government managers. The description should specifically address plans to interface with mission and functional (logistics, engineering) managers, as well as the interface with program and mission leaders.

4.2.5.2 Lessons Learned

Describe the approach to identify and disseminate lessons learned with Government personnel, ASCONs, and launch contractors. The description should specifically address method(s) for identifying, screening, and refining lessons learned, as well as the means by which dissemination will occur.

4.2.5.3 ASCON Interface

Describe the approach to interface with the program’s associate contractors (ASCONs) for program management (currently Aero Thermo Technology), program systems engineering (currently MCR Corp and Aerospace Corp), financial management (currently Tecolote Corp), and aging surveillance (currently ATK and Aerojet). The description should specifically address topics of common interest with each ASCON and the level and scope of plans to interface with each.

4.2.5.4 Fluctuation Management

Describe the approach to manage the contract workforce during fluctuations in reimbursable mission workload. The description should specifically address methods for maintaining core expertise during mission manifest fluctuations and any innovative solutions which maintain performance.

Section L

4.2.6 Transition Plan

The Transition Plan should provide for both rapid incoming transition in which the offeror assumes execution of the XBM sustainment effort and effectively initiates the IV&V efforts proposed, and a smooth outgoing transition during the optional XBM Sustainment Transition Period of Performance in which the XBM sustainment effort will be assumed by a follow-on contract effort. Descriptions should complement and correlate to the relevant entries of the schedule, WBS, and WBS Dictionary. The offeror should specifically identify any service enhancements inherent to the proposed solution which exceed threshold performance requirements.

4.2.6.1 90 Day Attainment Describe the incoming Transition Plan for rapidly attaining XBM sustainment and proposed IV&V effort full execution capacity. The description should specifically address plans to establish personnel, facility, equipment, and process readiness and any planned phasing from short term to long term performance.

4.2.6.2 PWS Readiness

Provide a milestone timeline which demonstrates full capability readiness for each of the following PWS efforts:

3.1 XBM Readiness

3.2.1 Cat 1 MA

3.2.2 Cat 2 MA

3.2.3 Cat 3 MA

3.2.4 Construct 2

3.2.5 XBM Flight Motor Processing

3.2.6 XBM Ground Test Motor Processing

3.3 Special Studies

3.4 Transition

4.2.6.3 Incumbent Interchange

Provide a milestone timeline which demonstrates the significant transition interchanges with the incumbent (See Incumbent Transition PWS Excerpt at Appendix E). Define the methodology that will be used for information and process capture planning in transition interchange meetings.

4.2.6.4 Follow-on Interchange.

Describe the outgoing Transition Plan for transitioning XBM sustainment, including a milestone timeline which identifies the significant transition interchanges with the incoming contractor.

Section L

4.2.7 Key Personnel

Describe the approach to identifying Key Personnel required to perform RSLP XBM Sustainment and Launch System IV&V. Role and responsibility descriptions should complement and correlate to the relevant entries of the schedule, WBS, and WBS Dictionary.

4.2.7.1 5 Key Positions Identify the 5 Key Positions considered essential to the work to be performed under this contract to be covered by the SD/PKT-H005 Clause, and identify the roles, responsibilities and locations of these positions. For each position, identify the minimum qualifications and the minimum education and experience that the offeror will require.

4.2.7.2 Key Personnel

Provide the qualifications of the Key Personnel planned for those positions, and identify the degree of commitment in place for each of those personnel.

4.2.7.3 Key Personnel Location

Describe the planned location of Key Personnel, with role-based rationale for the cited location.

4.2.7.4 Transition Team

Identify the transition team in place that will be assigned responsibility for executing the incoming portion of the Transition Plan. Describe the attributes that qualify each member of the team to provide an effective transition effort in cooperation with the incumbent contractor.

4.2.8 Efficiency Plan

Describe the offeror’s approach to identify and implement efficiencies meet price targets. The offeror’s BoE (see 4.2.11 below) should reflect this approach. The offeror should specifically identify service enhancements inherent to the proposed approach which reduce price targets for the option years of the XBM sustainment effort and future IV&V efforts.

4.2.9 Correlation Matrix

The Offeror shall provide a Correlation Matrix that cross references each paragraph of the PWS to the Contractor Work Breakdown Structure (CWBS) elements which address that PWS paragraph. This matrix shall be an Appendix of the Technical Volume and will not be counted against the page count. An example of an entry in a correlation matrix is shown below. The Correlation Matrix shall not contain informational notes, as the volumes provide ample opportunity for discussion and description of the Offeror's approach.

PWS CWBS Element

1.8.1.5

3.2.2 – Requirements Analysis

3.2.3 – Requirements Verification

1.8.1.6 3.2.4 – Requirements Validation

4.2.10 Contract Work Breakdown Structure (CWBS) and CWBS Dictionary The Offeror shall use the contents of the PWS to develop a Contract Work Breakdown Structure (CWBS) for XBM Sustainment and each IV&V effort, and shall provide a the CWBS to reflect their view of the service to be provided. The CWBS shall serve as the framework for organizing tasks to include in-house, inter-divisional, subcontractor, and associate contractor activities. 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. The Offeror's proposed CWBS and corresponding dictionary shall be provided as part of the proposal. The mapping of CLINs to CWBS elements shall be completely consistent with that shown in Section B of the solicitation.

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 and execution of these tasks shall be reflected in the Integrated Schedules.

Within the CWBS Dictionary the Offeror may specify their key 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 so referenced in a separate Appendix (see below). Each CWBS Dictionary entry shall reference the CDRL items which will be delivered by that task. The proposed CWBS dictionary shall not contain informational notes, as the Technical volume provides ample opportunity for discussion and description of the Offeror's approach.

4.2.11 Basis of Estimate (BoE)

Provide the BoE (hours per Labor Category only, see 6.1.2 for prohibition against including cost/price data in the Technical Volume) for each effort proposed, demonstrating the offeror’s approach to projecting the effort required. This description should complement and correlate to the relevant entries of the CWBS. The intent of this

Section L section is to obtain an understanding of the offeror’s proposal in terms of the scope of work planned for each effort, and to understand the offeror’s cost projection approach.

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 tasks can be easily located in the CWBS Dictionary.

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. Also use the narrative to discuss impacts of any trade-offs included in the approach required to ensure the offeror can execute and integrate vital mission operations while ensuring appropriate levels of risk, support to requirements, and meeting execution goals.

Include a discussion of the alternatives and why the scope associated with any proposed trade-offs in your approach is reasonable. Address your capability to control and mitigate the effort execution due to reasonably expected and moderate emergencies and contingencies.

4.2.12 Integrated Schedules

The intent of this section is to obtain an understanding of the proposal with clear tracks between the technical, schedule, management, etc., in a way that provides the Government confidence that the program is structured to be executable in a timely fashion. The Integrated Schedules provide sequencing and timing of the work effort planned and should be used as the primary tracking tool for technical and schedule status.

The Offeror shall provide Integrated Schedules for each effort proposed, including Transition (Exception: For XBM Sustainment, the Offeror shall only provide an Integrated Schedule for the Basic Period of Performance, at Sustainment Level 6). All WBS Elements in the Integrated Schedule shall demonstrate planned task durations and be logically linked together showing predecessor/successor relationships. The Integrated Schedules, CWBS and CWBS Dictionary shall use a common designation/numbering system so that schedule tasks can be easily located in the CWBS Dictionary.

The schedule shall also identify all milestones and critical events with the expected dates of each. These dates are based on an assumed starting point that occurs at Authority to Proceed (ATP) and the logical flow of dates provided by calculating the duration of tasks using typical schedule networking tools. The schedule tasks will be directly traceable to the CWBS and CLINs. The Integrated Schedule shall identify schedule margin and designate the critical path. The Integrated Schedules shall be included in the Technical Appendices and will not be counted against the page count.

4.2.13 Sample IV&V Kickoff Presentation

Section L

The offeror shall provide a sample IV&V Kickoff Presentation, either for one of the sample missions or from a prior similar effort which the offeror has provided (content may be redacted for programmatic concerns). The sample should communicate the intended format and content to be presented.

4.2.14 Sample IV&V Midterm Presentation

The offeror shall provide a sample IV&V Midterm Presentation for the same mission/effort (as used for the sample Kickoff) which communicates the intended format and content to be presented.

4.2.15 Sample IV&V Final Review

The offeror shall provide a sample IV&V Final Review which communicates the intended format and content to be presented. For the purpose of this review, the offeror should provide the review incorporating three residual risks:

a. The first residual risk is a qualification test that could not be completed for a flight safety system battery.

b. The second residual risk is associated with a payload separation anomaly on a prior flight for which root cause was never determined;

payload separation was successful but the separation dynamics were out of family, and the available data only allowed for fault isolation down to one of three elements.

c. The third residual risk is for a sibling failure related to the third stage motor, which failed to initiate on a prior space launch mission, resulting in loss of mission.

4.2.16 Completed L/M Cross Reference Matrix

The government has provided an L/M Cross Reference Matrix at Appendix B, with the first 3 columns completed to identify a) Section L Technical Volume Tab requirements to

b) related PWS sections and c) Section M Evaluation Criteria. The offeror should complete the last 3 columns of the L/M Cross Reference Matrix at Appendix B, to identify d) the CWBS elements which are relevant to that tab, e) where in their proposal that Proposal Tab is located, and f) the proposed CLIN(s) to which that Proposal Tab is applicable.

4.2.17 AS9100 or other relevant Certification(s) (if applicable) The offeror should provide a copy of significant process certifications relevant to the work to be performed under this contract to support any assertions of independent review of the processes to be used in the proposed solution.

4.2.18 Sample Aging Surveillance Analysis

The offeror shall provide a sample Aging Surveillance Analysis report which demonstrates the format and content of results of the offeror’s application of the proposed XBM Sustainment approach.

4.2.19 Sample Refurbishment Work Package

Section L

The offeror shall provide a sample Refurbishment Work Package which demonstrates the format and content of results of the offeror’s application of the proposed XBM Sustainment approach.

4.2.20 Copy of each document referred to in the CWBS Dictionary The offeror shall include a copy of any key internal document(s) referenced in the CWBS Dictionary for work content detail associated with specific tasks.

4.2.21 Tailored Compliance Documents (refer to 7.3.4.3)

If the offeror proposes any tailoring of compliance documents, a copy of the tailored document and rationale for sufficiency must be provided.

Section L

5.0 Volume II - (Factor 2) - Past Performance

5.1 General

Each Offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Appendix C. This information is required for the Offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform aspects of the effort the Offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the evaluation of past performance.

Along with the information required in this paragraph, the Offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror's performance.

5.2 Early Proposal Information

Each Offeror is requested to submit the information shown in Appendix C for each relevant contract prior to the date set for receipt of proposals, as identified in Table 2.8. Failure to submit early proposal information may negatively impact the government's ability to fully evaluate those aspects of the offeror's proposal.

5.3 Relevant Contracts

5.3.1 Summary

The offeror may provide a Past Performance Summary to facilitate Government understanding of any team construct and how each of the contract citations relate to the solicited effort. This summary information should facilitate review and evaluation of the Past Performance information items submitted.

5.3.2 Past Performance Information Forms (PPIF)

Submit information in accordance with Appendix C: Past Performance Information Form (PPIF) for up to five (5) recent contracts that you consider most relevant in demonstrating the Offeror’s ability to perform the proposed effort, limits as described in Table 2.8. Each task or delivery order of an IDIQ contract may be considered as a separate contract. The Government will not consider performance on a newly awarded contract without a performance history (at least six months), or on an effort that concluded more than five (5) years prior to the release of this RFP. If no relevant past or present performance information exists, do not submit a Past Performance Volume;

instead send a letter stating this fact, within the same time constraints as the Past Performance Volume.

Also include information on up to three (3) recent contracts performed by each of the Offeror’s teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Include rationale supporting the Offeror’s assertion of relevance. For a description of the characteristics

Section L or aspects the Government will consider in determining recency and relevance, see Section M, provision M102 - Evaluation Factors.

Offerors are required to explain what aspects of the work performed are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate.

This may include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the Offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an Offeror has overcome past problems is required. Categorize the relevant information into the specific Technical subfactors used to evaluate the proposal.

5.3.3 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of the Offeror’s company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the Offeror(s), the Offeror’s "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

5.4 Past Performance Questionnaire

Each Offeror with relevant performance information must send a Past Performance Questionnaire (PPQ) (Appendix C) to at least two points of contact for each contract submitted as a relevant contract. Questionnaires must be sent to the Offeror’s customers (if applicable, critical subcontractors, team contractors, and/or joint venture partners) for each relevant contract. The Offeror shall send a PPQ Cover Letter (Appendix C) to request that POCs complete an unclassified PPQ and submit (mail or fax) the questionnaire within five (5) working days from receipt. Preferred points of contact are, in order of descending preference: program manager, PCO, technical or engineering lead. The points of contact shall return completed questionnaires to the POC identified in the PPQ Cover Letter (Appendix C). The Offeror shall track the completion of PPQs and document all exchanges and follow-ups with each of the POCs identified in the Past Performance Information Forms

Section L

(Appendix C). An initial PPQ Tracking Record will be provided with the Past Performance Volume III. The Offeror shall exert its best efforts to ensure that at least two POCs per contract or subcontract submit completed performance questionnaires prior to submittal of Volume III. Offerors may cease contact with their POCs once the tracking record is submitted.

Contract # POC PPQ Follow-up

Sent Delivered Returned Date Notes

123456789 Name Title Organization Phone #

5 Apr

7 Apr 12 11 Apr

10 Apr

Mr Jones plans to return questionnaire tomorrow.

Figure 5.4.1 – PPQ Tracking Record Format The Past Performance Team (PPT) may conduct follow-up discussions with any of the POCs and reserves the right to send out additional questionnaires. The Offeror is solely responsible for ensuring that questionnaires are submitted in time for use in the evaluation process and shall make every effort to achieve this objective. Once the PPQs are completed by the POCs, the information contained therein shall be considered sensitive and shall not be released to the Offeror.

5.5 Identification of any actual or potential Organizational Conflict of Interest and associated mitigation plan IAW Section L 5352.209-9001, Potential Organizational Conflict of Interest. Note: Submission of the OCI identification and mitigation plan (if applicable), is requested to be submitted with Volume II – Past Performance.

5.6 Contents

The past performance volume shall be organized as follows:

(1) Table of Contents

(2) Glossary

(3) Summary

(4) Relevant Past Performance Information Forms (Appendix C) in accordance with paragraph L 5.3

(5) Attachments

a) Initial Past Performance Questionnaire Tracking Record

b) Consent Letters executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information so the Offeror can respond to such information. (Subcontractor/Teaming Partner Consent Letter(s) and/or Client Authorization Letter(s)

c) Transmittal Letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the Offeror's performance.

d) Organization Structure Change History in accordance with paragraph

5.3.2 above.

Section L

e) Identification of any actual or potential Organizational Conflict of Interest and associated mitigation plan IAW Section L 5352.209-9001, Potential Organizational Conflict of Interest.

6.0 Volume III - (Factor 3) – Cost/Price

6.1 General Instructions

6.1.1 Cost/Price Reasonableness and Realism

These instructions are to assist you in submitting information other than cost or pricing data that is required to evaluate the reasonableness, and realism of your proposed cost/price. Compliance with these instructions is mandatory and failure to comply may result in rejection of the Offeror’s proposal. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the Offeror does not understand the requirement(s) or has submitted an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an Offeror’s proposal. Offers should be sufficiently detailed to demonstrate their cost reasonableness and realism. The burden of proof for credibility of proposed prices rests with the Offeror.

6.1.2 Non-Required Data

Data beyond that required by this instruction should not be submitted, unless the Offeror…