08_20190430_MOSSAIC_Atch08_Sec_L_RevA_Chg4.pdf

SECTION J, ATCH 08, SECTION L Rev. A, Chg 34

SOLICITATION NO: FA8823-19-R-0005 pg. 1

SECTION L: INSTRUCTIONS TO OFFERORS

FOR

MAINTENANCE OF SPACE SITUATIONAL AWARENESS INTEGRATED

CAPABILITIES (MOSSAIC)

CONTRACT

10 30 APRIL 2019

SOLICITATION NO.: FA8823-19-R-0005

ATTACHMENT 08

Ground Based Space Surveillance (GBSS) Division

Space Superiority Systems Directorate

SMC/SYG

1050 East Stewart Ave.

Peterson AFB, CO 80914

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD Contractors only;

administrative/operational use; 31 May 2018. Other requests for this document shall be referred to the SMC/SYGI, 1050 E. Stewart Ave., STE 2025, Peterson AFB, CO 80914.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, USC, Sec 2751, et.

seq.) or the Export Administration Act of 1979, as amended, Title 50, USC., App. 2401, et. seq. Violations of these export laws are subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.25.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Solicitation No: FA8823-19-R-0005 pg. 2

CHANGE CONTROL SUMMARY

Revision (Rev). A revision should be used to consolidate all changes into a new basic document with a new basic date. It should be used to clean up the document when it begins to become confusing with too many changes. It is the Data Managers (DM) decision when to revise the document. Number the revision and include a summary of the revisions in the change table. DM will remove all change bars when the document is revised since the revised document takes all previous changes into account. Do not remove changes from the change table when the document is revised since they may lend important historical value.

Version (Ver). A change that is administrative in nature does not require the document to be re-staffed. Changes that remove or add items periodically assessed or affect items assessed in frequency of assessment or thresholds must be re-staffed for approval. Consolidate changes when possible. Include a summary of the changes incorporated in the change table. Ensure change bars have been inserted after initial release.

Rev./Ver. Eff. Date Description

1.0 31 May 18 First draft for Industry review and comments.

1.1 29 Jun 18 Updated as a result of Industry comments and internal reviews.

• Rewrote paragraph 3.2.1.1.2 on page 18.

• Updated to address industry comments.

• Updated after SAW review and comments.

1.2 20 Jul 18 Updated Table 1-4 Non-Government Advisors on page 13.

Updated Para 4.2.1.2 providing instructions for Offeror’s Business Systems on pages 21-22 Updated Para 5.1.20 for FAR 52.222-46 Professional Employee Compensation instructions on page 32

2.0 6 Sep 18 3-ltr SRB Coordination Updates

2.1 18 Sep 18 Fixed format issues and TOC.

Reworked Section 5.0

3.0 19 Oct 18 Updated to address Industry comments and Internal on draft.

3.1 2 Nov 18 Moved Professional Employee Compensation to Contracts Volume;

changed Transition from CPFF to CR; revised realism instructions

4.0 11 Dec 18 Incorporated SRB comments.

4.1 19 Dec 18 Approved version at Delta-SRB.

4.2 16 Jan 19 New Solicitation Number.

4.3 30 Jan 19 SF5 Revisions as result of Jan ’19 One-on-One Feedback; OCI

Provision Updates as result of OCI D&F approval; Professional Employee Compensation provision clarification.

4.4 19 Feb 19 Accepted all changes for draft RFP release to Industry.

4.5 28 Feb 19 Removed Cross-Reference Matrix from 3.1.4; Change to Table 4-3;

and Updated Annex D with current S/W listing.

A 18 Mar 19 Final RFP Release.

A, Chg1 26 Mar 19 Paragraph 4.2.3.1 changed for clarification.

A, Chg 2 3 Apr 19 Adjusted to add clarifications based on industry comments A, Chg 3 10 Apr 19 Paragraph 1.7 updated with new due date of 20 May 2019.

A, Chg 4 30 Apr 19 Updated Annex D to include the Sustainment Software.

Solicitation No: FA8823-19-R-0005 pg. 3

TABLE OF CONTENTS

Para Page

1. Instructions to Offerors (ITO) and Information for Proposal Preparation

1.1. Program Structure and Objectives

1.1.1. System Baseline for Proposal Preparation Purposes

1.2. General Information

1.2.1. Point of Contact

1.2.2. Communications

1.2.3. Debriefings

1.2.4. Discrepancies, Errors, and Omissions

1.2.5. Consideration of Alternate Proposals

1.2.6. Electronic Reference Documents

1.3. General Instructions

1.3.1. Description of Section L

1.3.2. Compliance with Instructions

1.3.3. Non-conformance

1.3.4. Proposal Clarity

1.3.5. Embellishments and Elaborate Presentations

1.3.6. Acceptance Period

1.3.7. Records Retention

1.3.8. Task References

1.4. Organization and Format of Proposals

1.4.1. Page Limitations

1.4.2. Page Size and Format

1.4.3. Pricing Related Data

1.4.4. Classified Documents

1.4.5. Cross-Referencing

1.4.6. Indexing

1.4.7. Glossary of Abbreviations and Acronyms

1.4.8. Binding and Labeling

1.5. Electronic Submittals

1.5.1. Electronic Format

1.5.2. Handling of Version Conflicts

1.6. Use of Non-Government Advisors

1.7. Proposal Delivery

2. Volume I – Executive Summary

2.1. General

2.1.1. Offeror’s Proposed Team

2.1.2. Volume Organization

3. Volume II – Technical Volume

3.1. General

3.1.1. Technical Approach Rating

3.1.2. Technical Risk Rating

3.1.3. Format and Specific Content

3.1.4. Volume Organization

3.2. Technical Subfactor Sections

3.2.1. Subfactor 1 – Portfolio Management

3.2.2. Subfactor 2 – Rapid Modifications

Solicitation No: FA8823-19-R-0005 pg. 4

TABLE OF CONTENTS - Continued Para Page

3.2.3. Subfactor 3 – Sustainment Services

3.2.4. Subfactor 4 – Transition

4. Volume III – Cost/Price

4.1. General Instructions

4.1.1. Cost/Price Reasonableness, Realism and Balance

4.1.2. Estimating Techniques and Methods

4.1.3. Cost/Price Data

4.1.4. Cost/Price Data Requirements

4.1.5. Rounding

4.1.6. Electronic Files

4.2. Volume Organization

4.2.1. Main Body

4.2.2. Price Template

4.2.3 Basis of Estimates (BOE)

5. Volume IV – Contract Documentation

5.1. Purpose

5.1.1. Section A – Solicitation Contract Form

5.1.2. Section B - Supplies or Services and Costs and Price

5.1.3. Section C – Description/Specifications/Statement of Work

5.1.4. Section D – Packaging and Marking

5.1.5. Section E - Inspection and Acceptance

5.1.6. Section F - Deliveries or Performance

5.1.7. Section G - Contract Administrative Data

5.1.8. Section H – Special Contract Requirements

5.1.9. Section I - Contract Clauses

5.1.10. Section J - List of Documents, Exhibits & Attachments

5.1.11. Section K - Representations, Certifications, and Other Statements of Offerors

5.1.12. Exhibit A: Contract Data Requirements List

5.1.13. Attachment 1: Performance Work Statement (PWS)

5.1.14. Attachment 2: GEODSS Upgrade TMRR Statement of Work (SOW)

5.1.15. Attachment 3: GEODSS Upgrade EMD SOW

5.1.16. Attachment 4: Work Breakdown Structure (WBS)

5.1.17. Attachment 5: Contract Security Classification Specification (DD 254)

5.1.18. Attachment 6: Incentive Plan

5.1.19. Attachment 7: Rights In Data

5.1.20. Attachment 8: Section L “Instructions, Conditions, and Notices to Offerors”

5.1.21. Attachment 9: Section M “Evaluation Factors for Award”

5.1.22. Attachment 10: Government Furnished Property (GFP) List

5.1.23. Attachment 11: Price Template

5.1.24. Attachment 12: Reserved

5.1.25. Attachment 13: Organizational Conflict of Interest (OCI) Disclosure and Analysis Form and

Checklist

5.1.26. Attachment 14: Reserved

5.1.27. Attachment 15: BOE Template

5.1.28. Attachment 16: Small Business Participation Commitment Document

5.1.29. Attachment 17: OCI Mitigation Plan

Solicitation No: FA8823-19-R-0005 pg. 5

TABLE OF CONTENTS - Continued Para Page

5.1.30. Attachment 18: Small Business Subcontracting Plan

5.1.31. Attachment 19: System Modification BOE

5.1.32. Attachment 20: Software Version Release (SVR) Execution Instructions

5.2. Other Information Required

5.2.1. Authorized Offeror Personnel

5.2.2. Government Offices

5.2.3. Company Address, Identifying Codes, and Applicable Designations

5.2.4. Professional Employee Compensation Plan

ANNEX A: SVR Scenario ANNEX B: Prime Mission Product (PMP) Modification Scenario ANNEX C: GEODSS Upgrade BOE Assumptions ANNEX D: Software License and Maintenance Agreement Listing

Solicitation No: FA8823-19-R-0005 pg. 6

1. Instructions to Offerors (ITO) and Information for Proposal Preparation

1.1. Program Structure and Objectives

The Maintenance of Space Situational Awareness Integrated Capabilities (MOSSAIC) acquisition will provide sustainment services for current and future ground-based Space Situational Awareness (SSA) sensors, SSA Command and Control (C2) systems, and Space Battle Management Command and Control (BMC2) capabilities in the SYG portfolio. These systems are identified in Table 1-1.

Current SSA sensors are the Ground-based Electro Optical Deep Space Surveillance (GEODSS) systems, the Eglin Radar (AN/FPS-85) in Florida, the C-Band Radar in Australia, and the C-Band Radar on Ascension. Additionally, MOSSAIC scope includes sensor systems that are transitioning into the MOSSAIC portfolio as described in Tables 1-1 and 1-3. These are the Space Surveillance Telescope (SST), Space Fence, and European Bi-static Radar (EBR).

Current SSA C2 and Space BMC2 systems are the Distributed Space Command and Control system – Dahlgren (DSC2-D) at Dahlgren, VA, and the National Space Defense Center (NSDC) at Schriever AFB, Colorado (CO). DSC2-D includes several tools and systems that are geographically separated from DSC2-D and are also within the MOSSAIC scope of responsibility.

These are identified in Table 1-2. Command and Control capabilities (normally applications) are continuously being developed for the NSDC will also be supported from a Product Support Integrator perspective, sustained and/or modified under MOSSAIC.

Other systems are expected to be added over time (e.g., the Deep Space Advanced Radar Capability (DARC) system). Very limited support is included in the Performance Work Statement (PWS) scope for the DARC radar. It is currently limited to providing mothball maintenance for the prototype at WSMR for a 12-month period in Option Year (OY) Two (2), (PWS para 5.12).

Any systems and/or additional tasks (not included in the current PWS) added to MOSSAIC responsibility after award will be through a bilateral contract modification.

Additionally, MOSSAIC provides for sustainment and modernization of associated test and integration infrastructure capabilities supporting the SYG portfolio. These are identified in Table 1-1.

Finally, the MOSSAIC contract scope will include modifications and upgrades for all MOSSAIC systems that it sustains, or will sustain (e.g., the GEODSS Upgrade Acquisition Category [ACAT III] Program). The term “GEODSS Upgrade” and “Ground Based Optical Sensor System (GBOSS)” are used interchangeably throughout the RFP to refer to the ACAT III GEODSS Upgrade acquisition program.

The MOSSAIC strategy is to meet program requirements through a competitively awarded contract to a single Offeror who is deemed responsible in accordance with (IAW) the Federal Acquisition Regulation (FAR), as supplemented, whose proposal conforms to the solicitation’s requirements and is judged, based on the evaluation factors for award identified in Section M, to represent the best value to the Government.

The MOSSAIC contract will cover sustainment services, Software Version Releases (SVR) and system modification requirements. Tables 1-3 and 1-4 show the time-phased MOSSAIC sustainment services and SVR responsibility versus system. The dates for Option Years in Table 1-3 are for proposal purposes only. The dates may change based on actual contract award date.

Solicitation No: FA8823-19-R-0005 pg. 7

Table 1-1. MOSSAIC-Covered Systems for Sustainment Current Operational Systems

System Location(s) Type Nomenclature Mission C-Band Ascension Radar AN/FPQ-15 SSA C-Band Exmouth, WA, Australia Radar AN/FPS-134 SSA DSC2-D Dahlgren, VA; (see Table 1-2) C2 N/A SSA/C2, Space BMC2 Eglin Site C-6 Eglin AFB, FL Radar (PA) AN/FPS-85 SSA European Bi-static Radar (EBR)

TBD (Italy) Not a current system. See Table 1-3 for transition timeline

Radar TBD SSA

GEODSS systems Site 1: White Sands Missile Range

(WSMR), NM

Site 2: Diego Garcia, British Indian Ocean Territory

Site 3: Maui, HI Site 4: Australia (future site) Site 5: Europe (future site)

Electro-Optical AN/FSD-3 SSA

National Space Defense Center (NSDC) Capabilities Integration Office (NCIO)

Schriever AFB, CO C2 N/A Space BMC2

Space Fence Kwajalein Atoll, Republic of Marshall Islands Not a current system. See Table 1-3 for transition timeline

Radar (PA) TBD SSA

Space Surveillance Telescope (SST)

Exmouth, WA, Australia and No. 1 Remote Sensing Unit (1RSU), Royal Australian Air Force (RAAF) Base Edinburgh, Adelaide, Australia.

System being activated in Australia.

See Table 1-3 for transition timeline

Electro-Optical AN/FSQ-241 SSA

Current System Integration Labs (SIL) System Location(s) Type Nomenclature Mission

DSC2-D Development Network (DevNet) and Test Network (TNet)

Dahlgren, VA C2 N/A Dev & Test

Eglin SIL Harris Facility, Colorado Springs, CO Radar (PA) N/A Dev & Test GEODSS SIL Harris Facility, Colorado Springs, CO Electro-Optical N/A Dev & Test GEODSS Test Bed

(GTB)

Yoder, CO Electro-Optical N/A Test

Space Battle Management Lab

(SMBL)

Colorado Springs, CO C2 N/A Space BMC2

NSDC Shadow Ops Lab

Colorado Springs, CO C2 N/A Space BMC2

PA=Phased Array, SSA=Space Situational Awareness, WSMR=White Sands Missile Range

Solicitation No: FA8823-19-R-0005 pg. 8

Table 1-2. DSC2-D Systems and Capabilities DSC2-D Systems and Capabilities

System Ops Location(s) SIL Location Astrodynamic Support Workstation (ASW) Vandenberg AFB, CA Colorado Springs, CO (Govt

Facility) Common Framework Equipment (CFE) Dahlgren, VA, Vandenberg

AFB, CA, Schriever AFB, CO None

Integrated Space Situational Awareness (ISSA) Dahlgren, VA, Schriever AFB, CO

Schriever AFB, CO (Govt Facility)

Mission Processing System (MPS) Dahlgren, VA Dahlgren, VA & Colorado Springs, CO (Govt Facility)

Non-Traditional Data Pre-Processor (NDPP) Vandenberg AFB, CA Colorado Springs, CO (Govt Facility)

Special Perturbation Tasker (SPT) Vandenberg AFB, CA Colorado Springs, CO (Govt Facility)

SSA Data Library (under development) Dahlgren, VA Colorado Springs, CO

Table 1-3. MOSSAIC Sustainment Services Phasing

Table 1-4. MOSSAIC Software Version Releases

The content described above identifies the specific systems and capabilities that are in the MOSSAIC portfolio. The sustainment services, SVR, and modification tasks are clearly identified

Duration Start Stop Eglin GEODSS DSC2 NSDC C-Band

Australia C-Band

Ascension EBR Space Fence SST

12 mo 2/1/2020 1/31/2021 Full Full Full Full Full Full 1 month

Transition-In 6 months

Transition-In Specific PWS

Tasks

12 mo 2/1/2021 1/31/2022 Full Full Full Full Full Full 12 month

Transition-In

3 months Transition-In; 9 months Full 12 months

Transition-In 12 mo 2/1/2022 1/31/2023 Full Full Full Full Full Full Full Full Full 12 mo 2/1/2023 1/31/2024 Full Full Full Full Full Full Full Full Full 12 mo 2/1/2024 1/31/2025 Full Full Full Full Full Full Full Full Full 12 mo 2/1/2025 1/31/2026 Full Full Full Full Full Full Full Full Full 12 mo 2/1/2026 1/31/2027 Full Full Full Full Full Full Full Full Full 12 mo 2/1/2027 1/31/2028 Full Full Full Full Full Full Full Full Full 12 mo 2/1/2028 1/31/2029 Full Full Full Full Full Full Full Full Full 12 mo 2/1/2029 1/31/2030 Full Full Full Full Full Full Full Full Full 3 mo 2/1/2030 4/30/2030 Full Full Full Full Full Full Full Full Full 3 mo 5/1/2030 7/31/2030 Full Full Full Full Full Full Full Full Full

Sustainment Services OY10 Extension of Services 1 Extension of Services 2

Description

Full sustainment services (as defined by PWS for each system) -- see PWS Task Applicability

Sustainment Services OY1

Sustainment Services OY2 Sustainment Services OY3 Sustainment Services OY4 Sustainment Services OY5 Sustainment Services OY6 Sustainment Services OY7 Sustainment Services OY8 Sustainment Services OY9

System Eglin

GEODSS

DSC2-D

EBR

C-Band Aus C-Band Asc Space Fence

SST

Each OY SVR starts 1st day of March and ends last day of February (e.g., For OY1, SVRs start 3/1/2020 and end 2/28/2021)

Number of SVRs Per Sustainment Services Option Year Per System 56 Total SVRs

0 1 1

OY8 OY9 OY10

1 1 1

OY1 OY2 OY3 OY4 OY5 OY6 OY7

Solicitation No: FA8823-19-R-0005 pg. 9 in the PWS, and many of the provided workload factors are identified at the system and/or capability level.

However, the MOSSAIC PWS also includes portfolio level management tasks. The Government requires that the MOSSAIC portfolio be managed as an enterprise, rather than just a collection of independent systems. This adds complexity and challenges that must be considered when selecting a management approach. Two examples of challenges that are already beginning to impact the SYG portfolio are provided below. These examples are not meant to be inclusive of all the challenges anticipated. Rather, they are just representative of the types of challenges expected.

First, in as much as the SSA, SSA C2, and Space BMC2 missions, supported by the systems and capabilities in the MOSSAIC portfolio, are becoming more interdependent, the MOSSAIC systems and capabilities are becoming more interdependent. This interdependency adds challenges to maintain compatibility and interoperability during concurrent modifications. This challenge is expected to be exacerbated by two additional factors: (1) 20 or more MOSSAIC portfolio modifications could occur concurrently in any given year, and (2) rapid, agile software development (especially on C2 systems) is expected where multiple external developers may be simultaneously developing applications that must work with each other and within the host system architecture and operating system, etc.

Second, there are well understood metrics and analysis tools to quantify the improvement, at the system level, for planned modifications or non-materiel changes (e.g., increases system Ao, improves sensor sensitivity). Assessing and quantifying what impact those system level improvements have on SSA, SSA C2, and Space BMC2 mission effectiveness is significantly more complicated. However, being able to effectively assess and quantify the operational return on investment (ROI), at the mission level, is critical to enable prioritization of Government investments to maximize the mission capability of the portfolio.

1.1.1. System Baseline for Proposal Preparation Purposes

System baselines are established through a series of documents contained in the Bidders’ Library.

Instructions on how to gain access to the Bidders’ Library are posted in the general information area of the MOSSAIC posting on the Federal Business Opportunities website (www.fbo.gov).

Additional information regarding the mission systems and test assets can be found in the PWS and in the Bidders’ Library.

The Offeror’s proposal shall be based on the requirements outlined in the PWS.

1.2. General Information

Offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors.

The response shall consist of the following volumes: Volume I – Executive Summary; Volume II - Technical Volume; Volume III - Price Volume; and Volume IV – Contract Volume. Proposals shall be delivered in hard copy and electronic form, as further discussed in Table 1-5 and in paragraph 1.5 below. All Proposal volumes shall be submitted by the date provided in section 1.7.

http://www.fbo.gov/

Solicitation No: FA8823-19-R-0005 pg. 10

1.2.1. Point of Contact

The Procuring Contracting Officer (PCO) is the sole official point of contact for this acquisition.

Address any questions or concerns to the PCO and copy the Contract Negotiator and Program Manager (PM). Written requests for clarification may be sent to the PCO, with copy to Contract Negotiator and PM, at the addresses below:

• PCO, Seneca J. Alvarado: (719) 556-7889 seneca.alvarado@us.af.mil

• Contract Negotiator, Stephanie Rosenthal: (719) 556-2258 stephanie.rosenthal@us.af.mil

• PM, Ronald Dion, Major: (719) 556-2554 ronald.dion@us.af.mil

1.2.2. Communications

After release of RFP, all exchanges of information between the Government and Offerors will be controlled by the PCO.

1.2.3. 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 IAW FAR 15.505, “Pre-award Debriefing of Offerors.” Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing IAW FAR 15.506, “Post-award Debriefing of Offerors.” However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal.

Offerors that were within the competitive range but were ultimately unsuccessful will be notified of the source selection decision by the PCO IAW FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW FAR 15.505 or 15.506, as applicable.

1.2.4. Discrepancies, Errors, and Omissions

If an Offeror believes that the requirements in these instructions lack clarity or contain a discrepancy, 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 discrepancy, error or omission. Notifications and content of any solicitation amendments will be posted to the Federal Business Opportunities (FBO) website, www.fbo.gov. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without conducting discussions.

1.2.5. Consideration of Alternate Proposals

Alternate proposals will not be considered.

1.2.6. Electronic Reference Documents

All reference and technical documents for this solicitation are available in the MOSSAIC Bidders’ Library to assist in preparation of the proposal.

mailto:seneca.alvarado@us.af.mil mailto:stephanie.rosenthal@us.af.mil mailto:ronald.dion@us.af.mil http://www.fbo.gov/

Solicitation No: FA8823-19-R-0005 pg. 11

1.3. General Instructions

1.3.1. Description of Section L

Section L of this solicitation is the instructions, conditions, and notices to Offerors for the source selection. This section is written IAW FAR Part 15, “Contracting by Negotiation”, as supplemented by the DoD Source Selection Procedures issued 1 Apr 2016, and Air Force FAR Supplement (AFFARS) Mandatory Procedures 5315.3, “Source Selection”.

1.3.2. Compliance with Instructions

The Offeror’s proposal must include all data and information requested by this Instruction to Offerors (ITO) and be submitted IAW these instructions. The offer shall be compliant with the requirements as stated in the Sustainment Services PWS, the GEODSS Upgrade TMRR and EMD Statements of Work (SOW), Compliance and Reference Documents, Contract Data Requirements List (CDRL), and with all the requirements contained in the solicitation.

1.3.3. Non-conformance

Non-conformance with the instructions provided in the solicitation may result in exclusion from the competitive range or an otherwise unfavorable proposal evaluation. The Government intends to award the contract without discussions, but reserves the right to conduct discussions if necessary. Offerors are cautioned not to submit a proposal with exceptions to the solicitation.

1.3.4. Proposal Clarity

The proposal should provide detailed descriptions with sound supporting rationale. Any stated claims must be substantiated. The proposal shall not simply rephrase or restate the Government's requirements, but rather should provide sound rationale to address how the Offeror intends to meet or exceed these requirements. Offerors shall assume that the Government has no prior knowledge of either their facilities or experience and will base its evaluation on the information presented in the Offeror's proposal.

1.3.5. Embellishments and Elaborate Presentations

Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and will count against the overall page count.

1.3.6. Acceptance Period

The proposal acceptance period is specified in Section A of the solicitation. By signing block 17 of Standard Form 33 of the solicitation, the Offeror represents that its offer is valid for 365 calendar days from the proposal due date.

1.3.7. Records Retention

IAW FAR Subpart 4.8 (Government Contract Files), following contract award, the Government will retain one copy of all proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of proposals.

1.3.8. Task References

When specific tasks are referenced, the Offeror shall provide the paragraph number(s) as found within the PWS or SOWs, Work Breakdown Structure (WBS), and within the proposal.

Throughout Section L, these will be referred to as the PWS, SOWs, and WBS respectively.

Solicitation No: FA8823-19-R-0005 pg. 12

1.4. Organization and Format of Proposals

The Offeror shall prepare the proposal as set forth in the Table 1-5, Proposal Organization, 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. The contents of each proposal volume are described in the ITO paragraph as noted.

Table 1-5. Proposal Organization

Volume

ITO

Paragraph Number Title

Electronic Copies

Hard Copies Page Limit

I 2.0 Executive Summary 2 2 5 II 3.0 Technical

Main Body (4 sections—95 Total Pages) Section 1. Portfolio Management Section 2. Rapid Modifications Section 3. Sustainment Services Section 4. Transition

2 2 95

Attachment T1: Sustainment Services Labor Table 2 2 Unlimited III 4.0 Cost/Price

Main Body 2 2 Unlimited Attachment PC1: Price Template 2 2 Unlimited Attachment PC2: Transition BOEs 2 2 Unlimited Attachment PC3: SVR BOEs 2 2 Unlimited Attachment PC4: PMP Modification BOE 2 2 Unlimited Attachment PC5: GEODSS Upgrade TMRR BOEs 2 2 Unlimited Attachment PC6: GEODSS Upgrade EMD BOEs 2 2 Unlimited

IV 5.0 Contract Documentation 2 2 NA

1.4.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 practical. Page limits do not apply to indexes, tables of contents, tabs, cover pages, glossaries or requested information identified with an “Unlimited” in Table 1-5.

1.4.2. Page Size and Format

Except for the reproduced sections of the solicitation document, font shall be Times New Roman and font size shall be no less than 12 point. 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. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Margins shall be at least 1 inch on the top and bottom and ¾-inch on the sides. Pages shall be numbered sequentially by volume.

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, or similar items. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size, with no smaller than 10 point

Solicitation No: FA8823-19-R-0005 pg. 13 font. Foldout pages shall fold entirely within the volume. Each printed side of an 11 x 17 inch fold out page shall be considered one page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; they may not be used for pages of text. All MS Excel spreadsheets shall be supplied in "active" format with all formulas and data sources included and fully functional so the Government may use them during the evaluation. Any formulas used shall be provided in the spreadsheets. These limitations shall apply to both electronic and hard copy proposals.

1.4.3. Pricing Related Data

All cost/pricing data shall be addressed ONLY in the Price and Contract Documentation Volumes, unless otherwise specified in these instructions. Price trade off information (application of planned resources that affect prices), work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for trade off decisions.

1.4.4. Classified Documents

The Offeror’s proposal shall be unclassified. If an Offeror needs to submit classified information in support of Section L paragraphs 3.2.1.5 and/or 3.2.2.1, the PCO shall be notified not later than five (5) business days after release of the RFP, such that arrangements can be made to receive and store the information, and to ensure personnel with appropriate access are available to review the information. If PCO notification is not received by the cut-off date (listed above), then no classified information may be submitted. The Government will use its best efforts to accommodate inclusion of classified information in the technical evaluation record, but handling and/or access restrictions may preclude our ability to receive, store, view or evaluate the input, which is why early notification is imperative. If the Government cannot confirm its ability to receive, store, view or evaluate the classified information, the Offeror will be informed within five (5) business days of the request. For any classified submittals, the Offeror shall identify what volume the classified submittal is related to. Classified submittals will count against the page count as described in Section L, paragraph 1.4 and Table 1-5.

1.4.5. Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so its contents may be evaluated without cross-referencing other volumes of the proposal. The Government will assume any information required for proposal evaluation, which is not found in its designated volume, has been omitted.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

1.4.6. Indexing

Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

1.4.7. Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of abbreviations and acronyms used, with an explanation for each.

Solicitation No: FA8823-19-R-0005 pg. 14

1.4.8. Binding and Labeling

Offeror’s will submit proposals IAW the following binding and labeling instructions:

1.4.8.1 Each volume will be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open.

1.4.8.2 Do not use staples.

1.4.8.3 Include a cover sheet on each book, clearly identifying the volume number, title, copy number, solicitation identification, and the Offeror's name.

1.4.8.4 Include the same identifying data on the spine of each binder.

1.4.8.5 Do not use security designation colors (e.g., red) for binder colors.

Offerors shall ensure appropriate markings are applied, including those prescribed IAW 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.

1.5. Electronic Submittals

1.5.1. Electronic Format

In addition to the hard copies, the Offeror shall submit electronic copies using CDs or DVDs.

Each volume should be in a different directory on the CD or DVD. If files are compressed, the necessary decompression program (e.g., WINZIP) shall be included. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any.

Electronic copies of the proposal shall be submitted in a format readable by Adobe Acrobat, Microsoft (MS) Office Word 2016, MS Office Excel 2016, MS Office Project 2016, MS Office Power Point 2016, or compatible as applicable. The proposal shall include the native file (e.g., .doc) with full edit rights. The content and page size of electronic copies must be identical to the hard copies.

Each electronic file shall be clearly marked to show the proposal volume number, solicitation number, and Offeror's name. Hypertext links may be used to facilitate navigation within the document.

1.5.2. Handling of Version Conflicts

In the event a discrepancy exists between the hard copy and the electronic copy, the hard copy will be used for evaluation.

1.6. Use of Non-Government Advisors

Offerors are advised that data submitted to the Government in response to this solicitation will be released to individuals who work for companies identified in Table 1-6 as non-government advisors for review and analysis during the evaluation process. Per DoD Source Selection Procedures (1 April 2016) paragraph 1.4.6.2 and IAW FAR 9.505-4(b), the Offeror must enter into their own non-disclosure agreement with the companies identified below BEFORE submitting their MOSSAIC proposals. Offerors shall expressly state in a letter to the PCO within 10 business days after the date of RFP release that: (1) they have entered into non-disclosure agreements with the companies listed below, and (2) they consent to provide access to its proprietary information to the non-Government advisors or the company that employs the non-government advisors.

Solicitation No: FA8823-19-R-0005 pg. 15

Offerors shall also include a confirming statement in the Executive Volume (Volume I) of their proposal.

Table 1-6. Non-Government Advisors Company Name Contact Info

Odyssey Systems Consulting Group Jon (JD) Dowling jondowling@odysseyconsult.com 719-355-2204

The Tech 7 Company Nadine Echeverry nadine@gotech7.com 562-746-2678

ManTech Pamela S. Kelley pamela.kelley@mantech.com 703-674-2922

Tecolote Judy Roddey JRoddey@Tecolote.com 310-640-4700x52091

FFRDC (Aerospace) Kien T. Le Kien.t.le@aero.org 310-336-6242

FFRDC (MITRE)

Beth Blakney blakney@mitre.org 719-556-8745

The individuals participating in the review and analysis of proposals during the evaluation process will be required to sign individual nondisclosure agreements with the Government, which strictly prohibits any release or disclosure of information outside of the source selection team, before having access to any proposals or source selection data or information.

These companies' contracts also contain an "Associate Contractor Agreement" requirement that directs contractors to work with any other contractors to obtain agreements deemed necessary to carry out their work. Offerors are encouraged to engage early (before formal RFP release) with these contractors to obtain any agreements needed to permit access for the non-government advisors.

1.7. Proposal Delivery

Proposals shall be received by the PCO no later than 5:00 PM (Mountain Time), 20 May 2019.

Proposals received after the cutoff date shall be treated IAW FAR 15.208. The entire proposal package must be physically delivered to the PCO or designated POC at:

SMC/SYK - Building 2025 Lobby Attn: 1050 E. Stewart Ave. (Bldg 2025) Peterson AFB, Colorado 80914

Offerors hand-carrying proposals to Building 2025 Lobby are notified that individuals not affiliated with the installation must obtain visitor passes at the Visitor Control Center located on W. Stewart Ave (West Gate entrance) just before the West Gate on Peterson Air Force Base. Offerors should allow sufficient time to obtain visitor passes in order to arrive at Building 2025 Lobby prior to the time established for the receipt of proposals. If using a courier, the Government requests, but does not require, that the Offeror submit to the PCO the name of the individual hand-carrying volumes 24-hours in advance.

mailto:jondowling@odysseyconsult.com mailto:nadine@gotech7.com mailto:pamela.kelley@mantech.com mailto:JRoddey@Tecolote.com mailto:Kien.t.le@aero.org mailto:blakney@mitre.org

Solicitation No: FA8823-19-R-0005 pg. 16

All proposal deliveries shall be coordinated with the PCO; early deliveries will not influence the evaluation. The Offeror should notify the PCO of an approximate time of delivery no later than three business days prior to proposal delivery and provide a point of contact to coordinate delivery.

A transmittal letter to the PCO may be used, but will not be evaluated. A jointly signed receipt will document the delivery and receipt of proposals.

2. Volume I – Executive Summary

2.1. General

The Executive Summary Volume is provided for informational purposes only and is not evaluated or scored. Do not include cost or price information in this volume. A letter of transmittal or executive cover letter shall be included in this volume. This cover letter shall not be counted against the page limitations of the volume. The letter shall not exceed two pages in length. The Executive Summary Volume shall include the following sections:

2.1.1. Offeror’s Proposed Team

The Offeror shall provide an organizational chart that identifies the Offeror’s team including the prime and associate organizations and identifies the facility location(s) where work will be performed. The term “associate organizations” is used throughout the RFP to mean any proposed team member other than the prime (e.g., subcontractors, teammates, partners, inter-divisional support, and organic depots). Small businesses shall be identified as part of the Offeror’s proposed team structure. The Offeror shall provide another organizational chart that identifies the prime contractor’s Cost Center for the project (i.e., the business center where project costs are collected and reported) and depicts how the Offeror’s program fits within the company, including titles, division names, locations and other relevant identifying information.

The Offeror shall provide a narrative summary describing its organization and management structure, as well as the roles and responsibilities of all the participants. The Offeror shall indicate, in the narrative summary, agreements that have been, or will be, executed with other associate organizations to allow work to begin at contract award.

2.1.2. Volume Organization

The Offeror shall provide a master table of contents of the entire proposal and shall clearly and concisely describe the physical structure of the proposal to include the presentation structure, the interrelationships between volumes and sections or subsections of the overall proposal, and where material may be found for each evaluation area as defined in Section L. None of the information provided to comply with this paragraph (2.1.2) counts against the page count limitations.

3. Volume II – Technical Volume

3.1. General

In Volume II and using the instructions provided in this section (Section L), the Offeror shall describe their proposed technical approach for meeting or exceeding the solicitation requirements specified by Subfactors 1, 2, 3, 4 and 5. The Technical Volume shall be specific and complete.

Legibility, clarity, and coherence are very important. Responses shall be evaluated against the Technical Subfactors defined in Section M of this RFP, Evaluation Factors for Award.

Solicitation No: FA8823-19-R-0005 pg. 17

3.1.1. Technical Approach Rating

Section M defines specific evaluation methodologies, definitions, and ratings.

3.1.2. Technical Risk Rating

Section M defines specific risk evaluation methodology, definitions, and ratings.

3.1.3. Format and Specific Content

By submitting a proposal, the Offeror is representing that they shall perform all the requirements specified in the solicitation. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. Using the instructions outlined below, the Offeror shall provide the actual approach that would be used for satisfying the Subfactor requirements.

The Offeror’s proposed solution shall reflect the proposed work and careful consideration should be made to thoroughly address all the information requested in each of the Subfactors listed.

3.1.4. Volume Organization

The Technical Volume shall be organized according to the following general outline:

• Table of Contents

• List of Tables and Figures

• Glossary

• Main Body o Section 1: Portfolio Management (Technical Subfactor 1) o Section 2: Rapid Modifications (Technical Subfactor 2) o Section 3: Sustainment Services (Technical Subfactor 3) o Section 4: Transition (Technical Subfactor 4)

3.2. Technical Subfactor Sections

The Technical Factor is divided into five subfactors. Each subfactor will be evaluated IAW Section M. The narrative provided in the following subsections, unless requested as an attachment, will be part of the Main Body of the Technical Volume.

3.2.1. Subfactor 1 – Portfolio Management

In addressing Portfolio Management, the Offeror shall provide information in Section 1 of the Technical Volume on their technical approach to meet or exceed the criteria in Section M. The Offeror shall provide a detailed description, with supporting rationale, of:

3.2.1.1 The Space Situational Awareness (SSA), SSA Command and Control (C2), and Space

Battle Management and Control (BMC2) missions and their interdependencies.

3.2.1.2 The challenges associated with managing a portfolio of interdependent systems (e.g., executing multiple concurrent system modifications where interoperability must be maintained).

3.2.1.3 A sound approach to address those challenges (Identified in paragraph 3.2.1.2) and efficiently manage the MOSSAIC portfolio as an enterprise, rather than an aggregation of independent systems.

Solicitation No: FA8823-19-R-0005 pg. 18

3.2.1.4 A sound approach to develop and prioritize annual investment recommendations based on quantifiable mission level metrics (e.g., Space BMC2 decision timeline, global persistence) in addition to system level performance metrics (e.g., Ao, sensor sensitivity) such that portfolio mission effectiveness can be maximized.

3.2.1.5 At least one example of actual performance where the approach (Section L paragraphs

3.2.1.3 and 3.2.1.4) was successfully applied to manage a portfolio of interdependent systems, rather than an aggregation of independent systems.

3.2.2. Subfactor 2 – Rapid Modifications

In addressing Rapid Modifications, the Offeror shall provide information in Section 2 of the Technical Volume on their technical approach to meet or exceed the criteria in Section M.

3.2.2.1. The Offeror shall provide at least one example, of a combined hardware and software modification, where they successfully executed (through operational acceptance) a rapid system modification. Integral to the example(s), the Offeror shall describe the development approach(es) used (e.g., concurrent engineering, DevOps, rapid prototyping) and how the approach(es) were able to accelerate operational acceptance.

3.2.2.2. The Offeror shall provide a detailed description of a sound approach, with supporting rationale, of how their investment prioritization and recommendation process (3.2.1.4), coupled with their rapid modification experience and development approaches (3.2.2.1), can be applied to MOSSAIC system modifications to reduce cycle time (requirements identification to operational acceptance).

3.2.2.3. The Offeror shall provide a detailed description of a sound approach, with supporting rationale, to execute the GEODSS Upgrade and Relocation Program (GBOSS). Integral to the detailed approach description, the Offeror shall:

3.2.2.3.1 Identify, with supporting rationale, technical and programmatic risks the Offeror deems to be Moderate (yellow) and High (red). When identifying risks, the Offeror shall use the Likelihood and Consequence criteria and 5x5 Life Cycle Risk Management (LCRM) matrix in Air Force Pamphlet 63-128, Integrated Life Cycle Management, paragraph 12.2, dated 10 July 2014;

3.2.2.3.2 Explain, with supporting rationale, of how the Offeror will mitigate and burn-down each identified High (red) risk and the top 10 Moderate (yellow) risks (do not include more than top 10); and

3.2.2.3.3 Suggest opportunities to improve program execution (e.g., reduce cost, application of rapid modification approaches (3.2.2.2) to reduce schedule, improve system performance).

3.2.3. Subfactor 3 – Sustainment Services

In addressing Sustainment Services, the Offeror shall provide information in Section 3 of the Technical Volume on their technical approach to meet or exceed the criteria in Section M. The Offeror shall provide a detailed description of a sound approach, with supporting rationale, to:

3.2.3.1. Execute the requirements in PWS paragraph 5.2.

Solicitation No: FA8823-19-R-0005 pg. 19

3.2.3.2. Execute Sustainment Services (includes all tasks identified in the PWS as applicable to Sustainment Services); including but not limited to:

3.2.3.2.1 Describe any unique and/or innovative elements of the approach (e.g., that lower cost, improve execution efficiency, improve contractor performance), and

3.2.3.2.2 Identify all labor categories, skill levels, and hours proposed for Sustainment Services CLINs (at the level of detail defined below in Table 3-1) in Attachment T1 for the Offeror and all associated businesses.

Table 3-1. Sustainment Services Labor Hour Matrix

3.2.3.2.3 Offeror shall describe the sustainment services organizational structure, including all proposed business associates, with a description of the sustainment services roles and responsibilities.

3.2.4. Subfactor 4 – Transition

In addressing Transition, the Offeror shall provide information in Section 4 of the Technical Volume on their technical approach to meet the criteria in Section M.

3.2.4.1 The Offeror shall provide a detailed description of a sound approach, with supporting rationale, to execute the PWS Transition Tasks 2.1, 2.4, 2.5, 2.6, 2.7 and 2.8. The Offeror shall explain how the approach provides uninterrupted support to the fielded weapon systems, minimizes risk of damage to the SIL equipment, and minimizes transition cost.

3.2.5. Subfactor 5 – Small Business (SB)

3.2.5.1 Small Business Participation Commitment Documentation

3.2.5.1.1 General Instructions. All Offerors, to include Small Businesses, shall submit Small Business Participation Commitment Documentation (SBPCD) in Attachment 16 of the Contracts Volume. The Government will use the submitted SBPCD to evaluate whether the Offeror has demonstrated they will meet the small business participation requirement in PWS paragraph 3.15 for Sustainment Services Option Year 1 (CLINs 0101 and 0111).

3.2.5.1.2 The SBPCD and assessment is separate from the FAR requirement for the PCO’s review and acceptance of an Offeror’s Small Business Subcontracting Plan (if applicable for the Offeror). However, the SBPCD must correlate with the Small Business Subcontracting Plan. Any SBPCD provisions that coincide with the Small Business Subcontracting Plan must be consistent. Small Business Participation constitutes respective portion(s) of contract effort to be performed by small business(es) at the Prime and 1st tier

Labor Category Skill Level OY1 OY2 OY3 OY4 OY5 OY6 OY7 OY8 OY9 OY10 EOS 1 EOS 2 1 # # # # # # # # # # # #

A # # # # # # # # # # # # X # # # # # # # # # # # # 1 # # # # # # # # # # # #

X # # # # # # # # # # # # 1 # # # # # # # # # # # #

X # # # # # # # # # # # # X # # # # # # # # # # # #

Proposed Labor Hours

OY = Sustainment Services Option Year; EOS = Extension of Services (EOS 1 is first 3 months, EOS 2 is second 3 months)

Solicitation No: FA8823-19-R-0005 pg. 20 subcontract levels (i.e., small business Prime contractors and small business subcontractors to the Prime). Portions of work performed by a Small Business Prime contractor will be included when calculating the total amount of work performed by small businesses under contract.

3.2.5.1.3 The SBPCD will be incorporated into any resulting contract, with its elements specified below:

3.2.5.1.3.1 The small business concerns (SBC) as defined in FAR Part 19 used in the Offeror’s proposed approach to satisfying the requirements of this solicitation, for Sustainment Services Option Year 1 Total Contract Value (sum of CLINs 0101 and 0111), including company name, business category(ies), description of products or services to be provided, NAICS code to be provided by each SBC (NAICS code shall be based on the nature of SBC products or services to be provided and is not limited to the overall NAICS code identified for this solicitation), and the nature of the proposed agreement with the SBC (i.e., joint ventures, mentor protégé agreements, other agreement). Use the table/format shown below in Tables 3-2 and 3-3 in proposing this required information.

Table 3-2. Small Business Concerns

Small Business Concerns

Company Name

Small Business Category(ies)

(SB, WOSB,

SDB, VOSB,

SDVOSB)

Product(s)/Service(s) to be Provided

NAICS

Code Nature of Commitment

3.2.5.1.3.2 All Offerors shall propose quantitative participation relative to the total proposed dollar value for Sustainment Services Option Year One Total Contract Value (sum of CLINs 0101 and 0111). Use the table below in proposing this required information. Offerors shall provide detailed explanations and documentation (e.g., agreements between the Prime and its’ proposed SBC partners) to support this quantitative small business participation.

Table 3-3. Small Business Participation

Small Business Participation

Business Category Dollar Value % of Total Value

Total Proposed Sustainment Services (OY1) Total Contract Value (Sum of CLINs 0101 and 0111) $ Small Business A $ % Small Business B $ % Total Proposed Small Business $ %

Solicitation No: FA8823-19-R-0005 pg. 21

4. Volume III – Cost/Price

4.1 General Instructions

In developing proposed CLIN prices and the Cost/Price Volume, Offerors shall assume a MOSSAIC contract start date of 1 October 2019. Additionally, Offerors shall assume the following performance periods for the GBOSS TMRR and EMD CLINs:

CLIN Noun Start Date End Date…