02. DRAFT Hemisphere Section L [dRFPv2].pdf

Space Domain Awareness & Combat Power (SDACP) Hemisphere Section L

FA8819-23-R-1000

Hemisphere 3

Section L: Instructions to Offerors 4 for 5

Space Systems Command 6

Space Domain Awareness & Combat Power 7 and 8

Battle Management Command, Control & Communications 9

3 October 2023 18

Table of Contents 1

1 PROGRAM STRUCTURE AND OBJECTIVES ......................................................................................... 4 2

1.1 Overview.................................................................................................................................. 4 3

1.2 Contract Structure.................................................................................................................... 4 4

2 GENERAL INFORMATION ................................................................................................................. 4 5

2.1 Instructions to Offerors ............................................................................................................ 4 6

2.2 Proposal Acceptance Period ..................................................................................................... 5 7

2.2.1 Delivery ............................................................................................................................ 5 8

2.3 Consideration of Alternate Proposals ....................................................................................... 6 9

2.4 Communications ...................................................................................................................... 6 10

2.4.1 Point of Contact................................................................................................................ 6 11

2.4.2 Discrepancies ................................................................................................................... 6 12

2.4.3 Exchanges ........................................................................................................................ 7 13

2.4.4. Debriefings ....................................................................................................................... 7 14

2.4.5. Electronic Documents ....................................................................................................... 7 15

3 PROPOSAL PREPARATION INSTRUCTIONS ........................................................................................ 7 16

3.1 Proposal Organization/Number of Copies/Page Limits.............................................................. 7 17

3.2 Page Limitations ....................................................................................................................... 9 18

3.3 Page Size and Format ............................................................................................................... 9 19

3.4 Indexing ................................................................................................................................... 9 20

3.5 Cross-Referencing .................................................................................................................... 9 21

3.6 Glossary of Abbreviations and Acronyms ................................................................................ 10 22

3.7 Markings ................................................................................................................................ 10 23

4.0 PROPOSAL CONTENT ................................................................................................................. 10 24

4.1 Volume I – Executive Summary .............................................................................................. 10 25

4.1.1 General Instructions ....................................................................................................... 10 26

4.1.2 Executive Summary ........................................................................................................ 10 27

4.1.3 Teaming, Organization, and Management ...................................................................... 10 28

4.1.4 Master Table of Contents and Cross Reference Matrix.................................................... 10 29

4.1.5 Proposal Validity ............................................................................................................. 11 30

4.2 Volume II – Technical ............................................................................................................. 11 31

4.2.1 General Instructions ....................................................................................................... 11 32

4.2.2 Technical Volume Organization ...................................................................................... 11 1

4.2.3 Format and Content ....................................................................................................... 12 2

4.2.4 Evaluation Factor I: Technical/Risk .................................................................................. 12 3

4.2.5 Evaluation Factor II: Small Business Participation ............................................................ 14 4

4.3 Volume III - Contract Responsibility and Documentation ........................................................ 14 5

4.3.1 Standard Form (SF) 33, Solicitation, Offer, and Award .................................................... 14 6

4.3.2 Financial Resources ........................................................................................................ 15 7

4.3.3 Accounting System ......................................................................................................... 15 8

4.3.4 Organizational Conflict of Interest (OCI).......................................................................... 15 9

4.3.5 Small Business Subcontracting Plan ................................................................................ 16 10

4.3.6 Section K, Representations, Certifications, and Other Statements of Offerors ................. 16 11

L1. Sample Government Reference Staffing Matrix ................................................................................ 17 12

L2. SF 1407 Pre-Award Survey of Prospective Contractor ....................................................................... 18 13

L3. OCI Mitigation Plan Checklist ........................................................................................................... 19 14

1 PROGRAM STRUCTURE AND OBJECTIVES 1

1.1 Overview 2

The purpose of this acquisition is to acquire Advisory and Assistance Services (A&AS) for the Space 3 Systems Command (SSC) Space Domain Awareness & Combat Power (SDACP) and Battle Management 4 Command, Control & Communications (BMC3) Program Executive Offices under a Multiple Award 5 Indefinite Delivery Indefinite Quantity (IDIQ) contract called Hemisphere. 6

The Hemisphere contractors will support the entire program executive offices, working with all its 7 programs regardless of location (ref. PWS Para. 5.2). SDACP and BMC3 seek to achieve high levels of 8 efficiency in the allocation of contractor resources and reduce administrative overhead. 9

The successful Hemisphere Offerors must have the necessary resources to provide critical depth and 10 breadth of advisory and assistance services at both the Program Executive Office and program levels. 11

The Government maintains complete oversight, final decision authority, and accountability for all key 12 Hemisphere functional and technical baseline products but assigns the responsibility for key functions 13 and products to the Hemisphere contractors. The Hemisphere contractors will operate in an integrated 14 team environment cooperating with the military, civilian, FFRDCs, and SETA elements of the program 15 function team; however, for all areas described in the PWS, the Hemisphere contractors will be 16 responsible for prescribed PWS products, services, and deliverables. The scope of the Hemisphere 17 contract ranges from administration services to program management and analysis expertise, as well as 18 providing engineering advice and assistance at the system and program level. 19

1.2 Contract Structure 20

This is a best value source selection conducted in accordance with Federal Acquisition Regulation (FAR) 21

15.3 and DoD Source Selection Procedures, 20 August 2022, as supplemented. 22

The Government intends to award a multiple award IDIQ contract in accordance with these Instructions 23 to Offerors (ITO) to all qualifying offerors. The Government reserves the right to not make an award to 24 any offerors. In order to be considered a “qualifying offer,” the offeror must meet the delineated 25 requirements of the solicitation, with the Government determining: 26

1. The Offeror is responsible in accordance with FAR 9.104-1 27

2. The Offeror’s proposal is evaluated to be acceptable by demonstrating it can meet the 28

Government’s staffing, quality assurance, transition plan, and security requirements 29 according to the criteria in Section M 30

This requirement is solicited full and open, under NAICS 541715. The Government will set aside task 31 orders for small business in accordance IAW FAR 19.502-4, agency procedures, and the Hemisphere 32 Ordering Guide. 33

2 GENERAL INFORMATION 34

2.1 Instructions to Offerors 35

The Offerors’ proposal must indicate all data and information requested by these ITO and must be 36 submitted in accordance with these instructions. The offer shall be compliant with the requirements as 37 stated in the Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model 38

Contract. Non-conformance with the instructions provided in these ITO may result in proposal rejection 1 and non-award. 2

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for 3 substantiating the validity of stated claims. The proposal should not simply rephrase or restate the 4 Government’s requirements but rather shall provide convincing rationale to address how the Offeror 5 intends to meet these requirements. Offerors shall assume that the Government has no prior 6 knowledge of their facilities and experience and will base its evaluation on the information presented in 7 the Offeror’s proposal. 8

Elaborate brochures or documentation, detailed artwork, or other embellishments are unnecessary and 9 are not desired. 10

The Offeror’s proposal shall be unclassified. No classified information will be accepted in response to 11 this solicitation. 12

2.2 Proposal Acceptance Period 13

The proposal acceptance period is specified in Section A, Block 12 of the signed Standard Form (SF) 33, 14 Solicitation, Offer, and Award. The Offeror shall make a clear statement in Volume I – Executive 15 Summary, of the proposal, that the offer is valid for 180 days from the proposal due date. 16

2.2.1 Delivery 17

Proposals are due no later than (NLT) 4:00 PM, local Los Angeles, CA time on 30 October 2023. Proposals 18 shall be submitted via the Procurement Integrated Enterprise Environment (PIEE) Solicitation Module. 19 The Offeror must establish a “Proposal Manager Account” in sufficient time to access documents and 20 submit offers. For instructions on how to post an offer, please refer to the Posting Offer demo: 21 https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf. The Offeror shall submit each volume in 22 electronic format, unclassified only. Classified proposal information will not be accepted in response to 23 this solicitation. Offerors will utilize PIEE and will not rely on any other electronic transmission (including 24 transmission by electronic e-mail). Proposals sent through proprietary or third-party File Transfer 25 Protocol (FTP) sites or DoD SAFE will not be retrieved. No hard copies of proposals will be accepted 26 (hand delivered or traditional mail). The proposal volumes should be submitted in a format readable in 27 Adobe PDF except for the staffing matrix, which shall be submitted in Microsoft (MS) Excel. The Offeror 28 shall not embed sound or video files into the proposal files. Electronic files shall be clearly identified for 29 each volume. Offerors shall submit separate documents for each proposal volume. Each volume must be 30 organized to be consistent with each section as identified in Table 3.1, below. The Offeror shall use the 31 following nomenclature for their proposal submissions: [Offeror Name]-[FA8819-23-R-1000]- [Volume #] 32 or [Offeror Name]-[FA8819-23-R-1000]-[Staffing Matrix]. All proposal information is expected to fit into 33 this format. All documents should refer to the original solicitation number, FA8819-23-R-1000. 34

In the PIEE Solicitation Module, Offerors are strongly encouraged to plan accordingly, submit proposals 35 well in advance of the designated submission deadline, and ensure affirmative receipt of proposals. It is 36 the Offeror’s responsibility to be fully knowledgeable and capable regarding PIEE. The Government will 37 not assist Offerors in transmitting proposals within PIEE. It is the Offeror’s responsibility to plan far 38 ahead of the proposal submission deadline, anticipating potential PIEE connectivity delays. 39

After successfully submitting an offer, a success message of the submission will be displayed in the 40 Solicitation Module and the offer display will collapse. The “message of submission,” a red lined box, will 41 be your confirmation and should state: “The offer was submitted on [date] [time] by Proposal Manager. 42 https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf

Please print this page and maintain for your records.” It is the Offeror’s responsibility to retain a copy of 1 this confirmation. The Solicitation Module automatically tracks the date and time of all submissions. All 2 proposals received after the exact time specified for receipt shall be treated as late submissions and will 3 not be accepted by the Government, subject to the provisions of FAR 15.208. 4

All referenced documents for this solicitation can be found on the PIEE Solicitation Module at 5 https://piee.eb.mil/. All vendors can view solicitations in the Solicitation Module by selecting 6 “Solicitation Search” in the Award section or “Solicitation Search” under the Support section at the 7 bottom of the page. Search for FA881923R1000. The Sam.gov website will reference back to this 8 module. 9

The Solicitation Module is a vendor portal for solicitation within the PIEE platform to automate and 10 secure the process for capturing solicitations, Attachments, and responses from industry. The 11 Solicitation Module allows vendors to retrieve and respond to solicitations and communicate directly 12 with solicitation managers in a secure environment. Vendors submitting an offer in the Solicitation 13 module must register in PIEE and submit a request for the Proposal Manager role. Training resources are 14 provided below. 15

Vendor Registration: 16 https://pieetraining.eb.mil/wbt/xhtml/wbt/portal/overview/vendorRegister.xhtml 17

PIEE Solicitation Web-Based Training: 18 https://pieetraining.eb.mil/wbt/xhtml/wbt/sol/solicitation/proposals.xhtml 19

2.3 Consideration of Alternate Proposals 20

Alternate proposals will not be considered. 21

2.4 Communications 22

2.4.1 Point of Contact 23

The Procurement Contracting Officer (PCO), Ms. Melanie Gipson, is the sole point of contact for this 24 acquisition. All questions or concerns must be directed to the PCO via email at 25 melanie.gipson@spaceforce.mil. Questions regarding the solicitation must be in writing and emailed to 26 the PCO no later than ten (10) calendar days prior to the close of the solicitation due date. The 27

Government may choose not to accept any questions after this time. You may confirm receipt of your 28 question by requesting a return email. A copy of the returned email, along with associated metadata, 29 shall be proof of receipt of the question. All answers to questions and any amendments to this 30 solicitation will be posted to SAM.gov website and the PIEE Solicitation Module. Potential Offerors are 31 encouraged to subscribe for real-time e-mail notifications when information has been posted to the 32 website for this solicitation. 33

2.4.2 Discrepancies 34

If an Offeror believes that the requirements in these instructions contain an error, omission, or are 35 otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale as 36 well as the remedies the Offeror is asking the PCO to consider as related to the omission or error. Such 37 notices shall be received no later than ten (10) calendar days from the solicitation posting. Notices 38 received after the ten (10) calendars may not be accepted by the government. 39 https://piee.eb.mil/ https://pieetraining.eb.mil/wbt/xhtml/wbt/portal/overview/vendorRegister.xhtml https://pieetraining.eb.mil/wbt/xhtml/wbt/sol/solicitation/proposals.xhtml

2.4.3 Exchanges 1

All communications between the Government and Offerors will be controlled by the PCO. Email may be 2 used to transmit such information to Offerors only if the email can be sent and received encrypted and 3 includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. In order to 4 facilitate the sending and receiving of encrypted emails, Offerors must use MS Outlook email configured 5 to support encryption or a different email product that is S/MIME compatible and configured to support 6 encryption. To ensure the process is working correctly, send a test encrypted message first (without 7 including any source selection information). The Offeror is responsible for ensuring information is 8 appropriately protected regardless of transmission method. 9

2.4.4. Debriefings 10

The PCO will promptly notify Offerors of any decision to exclude them from the competitive range; 11 whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors 12 excluded from the competitive range may request a pre-award debriefing or they may choose to wait 13 until after the source selection decision to request a post-award debriefing. Offerors are entitled to no 14 more than one debriefing. 15

2.4.5. Electronic Documents 16

All documents for this solicitation are available through the PIEE Solicitation Module at 17 https://piee.eb.mil/. Announcements regarding this solicitation will be made on both SAM.gov and the 18 PIEE Solicitation Module. 19

3 PROPOSAL PREPARATION INSTRUCTIONS 20

3.1 Proposal Organization/Number of Copies/Page Limits 21

A complete proposal will consist of 3 volumes, all of which shall be within the required page limits, 22 specified in Table 3.1. 23

Volume I – Executive Summary 24

Volume II – Technical 25

Volume III – Contract Responsibility and Documentation 26

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 3.1 below). 27 The titles and contents of the volumes shall be as defined in this table, all of which shall be within the 28 required page limits. The contents of each proposal volume are described in the ITO paragraph as noted 29 in the table below. 30

Table 3.1 Proposal Volume Organization

VOLUME SECTION VOLUME SECTION & TITLE PAGE LIMIT

I Executive Summary

3.7 Volume I Cover Page 1 Page

https://cs1.eis.af.mil/sites/afcc/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc#T2101 https://cs1.eis.af.mil/sites/afcc/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b3104 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b15505 https://piee.eb.mil/

3.4 Volume II Table of Contents No Page Limit

4.1.2 Executive Summary 5 Pages

4.1.3 Teaming, Organization, and Management 5 Pages

4.1.4 Master Table of Contents and Cross Reference Matrix No Page Limit

4.1.5 Proposal Validity Statement 1 Page

3.6 Glossary of Abbreviations No Page Limit

II Technical

3.7 Volume II Cover Page 1 Page

3.4 Volume II Table of Contents No Page Limit

4.2.4.1 Completed Staffing Matrix (1 Tab Only) No Page Limit

4.2.4.2 Quality Assurance 5 Pages

4.2.4.3 Transition and Start-Up Plan 5 Pages

4.2.4.4 Security 5 Pages

4.2.5 Small Business Participation 10 Pages

3.6 Glossary of Abbreviations No Page Limit

III Contract Responsibility & Documentation

3.7 Volume III Cover Page 1 Page

3.4 Volume III Table of Contents No Page Limit

4.3.1 Standard Form (SF) 33 Solicitation, Offer, and Award No Page Limit

4.3.2 Financial Resources No Page Limit

4.3.3 Accounting System No Page Limit

4.3.4 Organizational Conflict of Interest (OCI) No Page Limit

4.3.5 Small Business Subcontracting Plan 5 Pages

4.3.6 Section K, Representations, Certifications, and Other

Statements of Offerors No Page Limit

3.6 Glossary of Abbreviations No Page Limit

Note: In accordance with FAR 15.304, cost/price will be evaluated for each Task Order. As a result, 1 Cost/Price information will not be requested with this proposal. 2

3.2 Page Limitations 3

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or 4 considered in the evaluation of the proposal. Page limits do not include coversheets for volumes, tables 5 of contents, glossary of abbreviations and acronyms, indices, and/or title pages. Pages marked “This 6 page is intentionally left blank” will not be counted. Pages will be counted if they contain any other 7 information i.e., diagrams, extraneous data, etc. A cross-reference matrix shall not be counted in the 8 page limits. All pages shall be numbered. 9

Page limitations may be placed on responses to evaluation notices (ENs). The specified page limits for 10 EN responses will be identified in the letters forwarding the ENs to the Offerors. 11

3.3 Page Size and Format 12

A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 13 inches. Pages shall be single spaced. Except for the reproduced sections of the solicitation document, 14 the text size shall be no less than 11-point font, Times New Roman. Tracking, kerning, and leading values 15 shall not be changed from the default values of the word processing or page layout software. Use at 16 least 1-inch margins on the top and bottom and ¾ inch side margins. Pages shall be numbered 17 sequentially by volume. The page size and format restrictions shall apply to responses to both electronic 18 proposals and ENs. 19

Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, 20 systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible 21 and shall not exceed 11 x 17 inches in size. These pages shall count as two (2) pages. 11 x 17 inch pages 22 may only be used for large tables, charts, graphs, diagrams, and schematics not for pages of text. For 23 tables, charts, graphs, and figures, the text shall be no smaller than 10-point font, Times New Roman. 24 Otherwise, text shall be used sparingly to describe the depicted pictures or graphics and shall use single-25 line spacing and be no smaller than 10-point font, Times New Roman. These limitations shall apply to 26 electronic proposals. 27

3.4 Indexing 28

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that 29 volume. Hyperlink indexing shall be used to identify sections and facilitate navigation within the 30 document. 31

The Offeror shall use a common paragraph numbering system consistent with the PWS. 32

3.5 Cross-Referencing 33

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents 34 may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information 35 required for proposal evaluation which is not found in its designated volume will be assumed to have 1 been omitted from the proposal. 2

3.6 Glossary of Abbreviations and Acronyms 3

Each volume shall contain a glossary of all abbreviations and acronyms used, and include an explanation 4 for each. Glossaries do not count against the page limitation for their respective volumes. 5

3.7 Markings 6

Offerors shall apply all appropriate markings including those prescribed in accordance with FAR 52.215-7 1, Instructions to Offerors – Competitive Acquisition, and FAR 3.104-4 Disclosure, Protection, and 8 Marking of Contractor Bid or Proposal Information and Source Selection Information. 9

4.0 PROPOSAL CONTENT 10

4.1 Volume I – Executive Summary 11

4.1.1 General Instructions 12

The purpose of the Executive Summary is to provide an overview of the Offeror’s proposal. In the 13 Executive Summary Volume, the Offeror shall provide the following Information: 14

4.1.2 Executive Summary 15

The Offeror shall provide basic company information such as Name, Address, proposal points of contact 16 (POC), contact information for POCs (job title, phone number, email address), CAGE Code, Unique Entity 17 Identifier (UEI), and business size status. The offeror shall identify itself and its team structure that will 18 perform significant aspects of the contract. Provide a brief summary of the team’s capabilities, how and 19 to what extent they will support future Hemisphere requirements. 20

4.1.3 Teaming, Organization, and Management 21

Teaming arrangements, subcontract, affiliate/sister companies/entities are not restricted. Offerors 22 submitting a proposal as the prime Offerors in response to this solicitation are permitted to submit 23 separate proposals under which they would be a subcontractor, or a team member to another prime. 24 Subcontractors are permitted to support multiple primes. 25

The Offeror shall summarize its organization, management, roles, and responsibilities. The Offeror shall 26 indicate agreements that have been executed (e.g., subcontracts, interdivisional efforts) to allow work 27 to begin at contract award. The Offeror shall provide an organization chart that shows prime, 28 subcontractors, and includes personnel key to the success of the Hemisphere effort, delineating clear 29 lines of authority across each of the entities or divisions. The Offeror shall provide a separate 30 organization chart that depicts how the Hemisphere program fits within the company, clearly identifies 31 the entire chain of command from the Offeror’s Chief Executive officer to the Program Manager, and 32 include key names, titles, division names, and location. The Offeror will clearly identify personnel likely 33 to charge time to multiple Space Systems Command programs. 34

4.1.4 Master Table of Contents and Cross Reference Matrix 35

The Offeror shall provide a master table of contents for the proposal which includes the traceability and 36 interrelationships between volumes and sections of subsections of the overall proposal, and where 37 material may be found for each major element of the evaluations as defined in Section L of this 1 solicitation, in the format shown in Table 4.1.4. 2

Table 4.1.4 – Proposal Correlation Matrix

Evaluation Factor Section L - Instructions to

Offerors

Section M - Evaluation Criteria

PWS Proposal Technical

Paragraphs

4.1.5 Proposal Validity 4

The Offeror shall make a clear statement that the offer is valid for 180 calendar days from the proposal 5 due date. 6

4.2 Volume II – Technical 7

4.2.1 General Instructions 8

The Technical Volume shall be clear, concise, and include sufficient detail for effective evaluation and for 9 substantiating the validity of stated claims in the Offeror’s proposal. The Offeror shall describe its 10 proposed approach for meeting the solicitation requirements addressed by each Technical Subfactor. 11 The Government will evaluate the Offeror’s proposed approach against the Criteria in Section M of this 12 solicitation. 13

By submitting a proposal, the Offeror acknowledges that it will perform all requirements specified in the 14 solicitation. The Proposal should not simply rephrase or restate the Government’s requirements, but 15 rather shall provide a convincing rationale to address how the Offeror intends to meet those 16 requirements. Statements that the Offeror understands, can, or will comply with the Performance Work 17 Statement (PWS) (including referenced publications, technical data, etc.) and phrases such as “standard 18 procedures will be employed” or “well-known techniques will be used,” etc. will be considered 19 unacceptable. The Offeror shall assume that the Government has no prior knowledge of the Offeror’s 20 facilities and experience. The Government will base its evaluation on the information presented in the 21 Offeror’s proposal. Elaborate brochures or documentation, binding, detailed artwork, or other 22 embellishments are unnecessary and are not desired. 23

4.2.2 Technical Volume Organization 24

The Technical Volume shall be organized according to the outline below: 25

• Table of Contents (to include a list of tables, drawings, figures, etc.) 26

• Factor I: Technical/Risk 27

• Subfactor 1: Staffing 28

• Subfactor 2: Quality Assurance Plan 29

• Subfactor 3: Transition and Start-Up Plan 30

• Subfactor 4: Security 31

• Factor II: Small Business Participation 32

4.2.3 Format and Content 1

The following information shall be submitted and used in the evaluation of the Technical Factors and 2 Subfactors (reference Section M, Section 2.1). When not otherwise specified, in Table 3.1, the 3 information shall be included with the page limitations of Volume II – Technical. 4

4.2.4 Evaluation Factor I: Technical/Risk 5

4.2.4.1 Subfactor 1: Staffing 6

The purpose of this evaluation is to ensure that the Offeror demonstrates that they have attracted, 7 recruited, hired, trained, and retained cleared employees with the skillsets required by the Government 8 for the Hemisphere effort. 9

The Offeror shall complete columns G, J, and P in only ONE (1) tab in Attachment L1 – Sample 10 Government Reference Staffing Matrix and fill in the information applicable to the ten (10) positions 11 listed within the tab. The Offeror shall select only ONE (1) tab from Attachment L1 to fill in. The 12 proposed knowledge and experience shall meet or exceed the requirements stated by the staffing 13 matrix and the PWS. The individuals must also meet the security clearance requirements stated within 14 the staffing matrix. 15

The personnel whose names are listed in the staffing matrix must 1) currently be on staff at the 16 Offeror’s company or 2) currently be on staff at a company that the prime Offeror is subcontracted with 17 or has subcontracted with within the past year. The offeror’s signature on the SF 33 will represent that 18 the individuals whose names are provided are currently on the contractor’s staff or are on a teammate’s 19 staff AND meet the security clearance requirements. If the offeror is listing names of individuals from a 20 teammate, ensure they are identified, as required by Paragraph 4.1.3. 21

4.2.4.2 Subfactor 2: Quality Assurance 22

The Government is seeking a quality assurance approach that ensures the Government will receive 23 outstanding performance, which includes but is not limited to consistent surveillance of performance, 24 verification that all customers are receiving the performance levels and personnel qualifications 25 required, verification that individual contractors are working together across multiple contracts, towards 26 a shared goal of accomplishing the SDACP and BMC3 missions, and applicable quality assurance best 27 practices. The Offeror’s Quality Assurance Plan will be incorporated as an attachment in the resultant 28 contract and any Task Order awarded. 29

The Offeror shall provide a detailed plan as to how quality assurance will be achieved through 30 performance of the Hemisphere contract and will describe how quality will be ensured. The Offeror shall 31 describe when and under what circumstances quality assurance will be performed. The Offeror shall 32 describe remedies for performance deemed unsatisfactory to the Government. 33

The Offeror shall submit a Quality Assurance Plan that addresses requirements listed in the Hemisphere 34 PWS, Section 5.9.2 Quality Assurance Plan, and includes roles and responsibilities, details on how the 35 offeror will work collaboratively with fellow support contractors from various companies, performance 36 requirements and assessments (Hemisphere PWS Section 5.9.5), performance reporting, and non-37 conformances (Hemisphere PWS Section 5.9.4). 38

4.2.4.3 Subfactor 3: Transition and Start-Up Plan 39

The Offeror shall provide a proposed Transition and Start-Up Plan detailing how they would staff up to 40 50 FTE as required by PWS 3.6.3 in which the Offeror shall have all critical personnel (assume 30% of 41

FTE) hired and available to support the Government on the contract execution date (day one of work 1 performance), 75% of the positions hired and available to support within thirty (30) days of the contract 2 execution date, and 100% of the positions hired and available to support within 60 days of the contract 3 execution date. The Offeror shall provide a narrative describing their proposed event and task-based 4 plan to staff up to 50 FTE accordingly, to include obtaining security clearances for personnel, obtaining 5 badges and building access, and knowledge transfer from the incumbent workforce, as needed. For the 6 purposes of writing a Transition and Start-Up Plan as part of an Offeror’s proposal, Offerors should 7 assume all positions require access to both Los Angeles Air Force Base, El Segundo and Aerospace 8 Corporation campus, El Segundo. Both locations require a Space Systems Command (SSC) badge to gain 9 access. Positions with a TS//SCI requirement will require access to classified facilities at the Aerospace 10 Corporation campus. Classified facility access will require pre-coordination with Government and 11 Aerospace security staff. The narrative shall include significant accomplishments, accomplishment 12 criteria, risks, and risk mitigation plans, and associated completion dates. 13

The Offeror shall provide a narrative describing how they would identify the products, work in process, 14 and legacy tools that need to be transitioned and provide a plan for how those identified items will be 15 transitioned. The Offeror may give examples of how this has been done on similar efforts in the past. 16 The Offeror shall describe how they will interact with the incumbent contractor to ensure adequate 17 transition, as well as what is needed from the Government and when to assist with a timely and efficient 18 transition. 19

4.2.4.4 Subfactor 4: Security 20

The Offeror shall provide evidence to demonstrate to the Government that they can perform Top 21 Secret//Sensitive Compartmentalized Information (TS//SCI) or Special Access Program (SAP) work on the 22 Hemisphere effort. The Offeror shall provide information on their security office/staff structure and 23 processes. The Offeror shall describe their plan for how their security office/staff will support the 24 Hemisphere effort by citing specific actions and processes that will be put in place. The Offeror shall 25 describe their procedures for obtaining appropriate personnel security clearances and how those 26 clearances are maintained and how those cleared personnel are retained on staff. The Offeror shall 27 describe their plan for how to handle obtaining clearances for multiple personnel simultaneously. The 28 Offeror shall describe their processes for safeguarding classified materials, identify process for ensuring 29 personnel understand and comply with applicable security requirements for a TS//SCI or SAP contract 30 and cite the specific process and policies in place to address security-related issues, to include violations 31 and infractions (including actions taken to address actual violations/infractions in the past, if applicable). 32

In providing this information the Offeror shall cite specific, relevant performance to substantiate the 33 Offeror’s capability to manage a contract with personnel clearance requirements at the TS//SCI or SAP 34 level within the past three (3) years on a prior or current Government contract(s). Provide the scope of 35 the contract, number of FTE, the name of the agency, contract number, and current Government point 36 of contact, as the Government may reach out to verify this experience as part of their evaluation, to the 37 extent practicable with the classification level. 38

The Offeror shall document Satisfactory company security performance by providing Security Review 39 results from oversight inspections by Defense Counterintelligence and Security Agency (DCSA) or other 40 Cognizant Security Authority (CSA) [as shown in the corresponding contract DD Form 254]. 41 Documentation should span (at least) two review cycles immediately prior to the proposal submittal. 42 Offeror can document a lack of prior Security Reviews with a CSA provided/endorsed memorandum 43 documenting the lack of reviews. 44

4.2.5 Evaluation Factor II: Small Business Participation 1

All Offerors, to include small businesses and Comprehensive Subcontracting Plan participants, shall 2 provide a Small Business Participation submission. The Submission and assessment are separate from 3 the FAR requirement for the PCO’s review and acceptance of an Offeror’s Small Business Subcontracting 4 Plan (if applicable for the Offeror). However, the Small Business Participation Submission information 5 must correlate with the Small Business Subcontracting Plan. Any Small Business Participation 6 Submission provisions that coincide with the Small Business Subcontracting Plan must be consistent. 7 Small Business Participation constitutes respective portion(s) of contract effort to be performed by small 8 business(es) at the Prime, 1st tier subcontract levels (i.e., small business Prime contractors, small 9 business subcontractors to the Prime). Portions of work performed by a Small Business Prime 10 contractor will be included when calculating the total amount of work performed by small businesses 11 under contract. 12

The minimum small business participation requirement will be 35% of total (proposed) contract value at 13 the task order level (the estimated total for the base period and all options). 14

The Small Business Participation submission shall include the following information: 15

i. Offeror’s (prime contractor) Size: Indicate the Offeror’s applicable size and 16 socioeconomic categories (check all that apply): 17

{ } Other than Small Business 18 or 19

{ } Small Business also categorized as a 20

{ } Small Disadvantaged Business (SDB) 21

{ } Woman-Owned Small Business (WOSB) 22

{ } Historically Underutilized Business Zone (HUBZone) Small Business 23

{ } Veteran-Owned Small Business (VOSB) 24

{ } Service-Disabled Veteran-Owned Small Business (SDVOSB) 25

The Offeror shall provide a narrative description of how they will meet the Hemisphere small business 26 participation minimum quantitative requirement (MQR) of 35% of the total (proposed) contract value 27 (the estimated total for the base period and all options). Identify the type of work (as it relates to the 28 Performance Work Statement) that is planned for small business participation including a description of 29 products and services to be provided by small businesses. 30

4.3 Volume III - Contract Responsibility and Documentation 31

4.3.1 Standard Form (SF) 33, Solicitation, Offer, and Award 32

The Offeror shall complete blocks 12 through 19 of the Standard Form (SF) 33. If any amendments to 33 this solicitation are issued, the Offeror shall acknowledge each amendment number and date in block 14 34 of the SF 33. The Offeror’s legal name and address in block 15A must match the information for the 35 Offeror in System for Award Management (SAM) (http://www.sam.gov), including the corresponding 36 Commercial and Government Agency (CAGE) Code number and Unique Entity Identifier Number. The 37 name, title, signature, and date identified in blocks 16, 17, and 18, must be an authorized representative 38 with the authority to commit the Offeror to contractual obligations. 39

The offeror shall provide information to complete the contract clauses as required. 1

An official having the authority to contractually bind your company shall sign the SF 33 IAW FAR 4.102. 2 The SF 33 must bear a signature of an authorized representative for the Offeror. 3

The SF33 will not count against page limits. 4

4.3.2 Financial Resources 5

IAW FAR 9.104-1(a) a contractor must have adequate financial resources to perform the contract, or the 6 ability to obtain them. The Offeror shall fill out highlighted portions of Attachment L2, Standard Form 7 (SF) 1407 Preaward Survey of Prospective Contractor (Financial Capability), to help determine adequate 8 financial resources and assist the Contracting Officer in making a responsibility determination. The SF 9 1407 will not count against page limits. 10

4.3.3 Accounting System 11

Offerors shall provide a valid letter or report from the Defense Contract Audit Agency (DCAA)/Defense 12 Contract Management Agency (DCMA) that the Offeror’s accounting system has been approved or is 13 adequate for cost-reimbursement contracts, if available. If the offeror does not have proof of a 14 DCAA/DCMA acceptable accounting system, as defined at DFARS 252.242-7006(a)(1) or is otherwise 15 exempt from DCAA/DCMA acceptable accounting system then, the offeror shall submit documentation 16 explaining the exemptions or an assertion that it will work with DCAA/DCMA to obtain appropriate 17 accounting system approval prior to contract award. Accounting System information does not count 18 against page limitations. 19

Offerors should note that IAW FAR 16.301-3(a)(3) cost reimbursement Contract Line Item Numbers 20 (CLINs) will not be awarded without a DCMA-approved cost accounting system. 21

4.3.4 Organizational Conflict of Interest (OCI) 22

The Offeror shall perform its own OCI analysis and submit the results of that analysis as part of its 23 proposal, in accordance with DAFFARS 5352.209-9001. Specifically, the Offeror shall analyze the planned 24 acquisition for actual or potential OCI situations associated with its or any of its teammates’ or 25 subcontractors’ performance under any contract it or any of its teammates or subcontractors has been 26 or may be awarded by any federal agency or other entity. The Offeror shall describe in detail the 27 methodology used to identify actual or potential OCI issues. If the Offeror identified any actual or 28 potential OCIs with respect to the performance of itself or its subcontractor teammates, the Offeror 29 shall provide an Organizational Conflict of Interest (OCI) Mitigation Plan to be incorporated as an 30 attachment to any resulting contract. At a minimum, the plan shall address all the items identified in 31 Attachment L3 – OCI Mitigation Plan Checklist and include the checklist in the plan. If subcontractors or 32 other teammates submit individual OCI mitigation plans, each subcontractor or teammate OCI 33 mitigation plan shall also include a completed checklist. Any proposed avoidance or mitigation 34 techniques shall be consistent with the FAR 9.5 and the most recent decisions of the Government 35 Accountability Office (GAO) and the U.S. Court of Federal Claims. 36

If a prospective Offeror believes that any conflict of interest exists or may exist (whether organizational 37 or otherwise) or has questions on what constitutes a conflict of interest, the Offeror should promptly 38 raise the issue with the Contracting Officer by sending his/her contact information and a summary of the 39 potential conflict to the Contracting Officer before time and effort are expended in preparing a proposal 40 and mitigation plan and no later than ten (10) days after release of this solicitation. 41

If award is made to the Offeror, the resulting contract may include and OCI limitation applicable to 1 subsequent Government work, at either a prime contract level, at any subcontract tier, or both. During 2 evaluation of proposals, the Government may, after discussions with the Offeror and consideration of 3 ways to mitigate or avoid identified actual or potential conflicts of interest, insert a clause or term and 4 condition in the resulting contract which disqualifies the Offeror from further consideration for award of 5 future contracts such as the one listed at DAFFARS 5352.209-9000 Alt IV, with the paragraphs from Alt I, 6 II, and III included. 7

Resolution of OCI issues is treated in a manner similar to the Contracting Officer’s contractor 8 responsibility determination. Any communications necessary to resolve OCI issues shall not be 9 considered discussions. As such, the Contracting Officer may issue Evaluation Notices to the Offeror 10 prior to any decision to enter into discussions in order to resolve questions or concerns with the 11 Offeror’s OCI analysis or mitigation plan. 12

OCI documentation does not count against page limitations. 13

4.3.5 Small Business Subcontracting Plan 14

All Offerors shall submit a Small Business Subcontracting Plan IAW FAR 52.219-9 including information 15 required in paragraphs (d)(11) through (d)(15) of that subpart. The small business Subcontracting Plan 16 must be determined to be acceptable by the PCO in order for the Offeror to be eligible for contract 17 award. Offerors who participate in the Comprehensive Subcontracting Plan (CSP) program shall provide 18 a copy of their current DCMA-negotiated CSP which will be incorporated into the contract at contract 19 award. 20

The Offeror shall identify the percentage of intended business with each of the following small business 21 socio economic categories: Small Business, Service-Disabled Veteran-Owned Small Business, HUBZone 22 Small Business, Small Disadvantaged Business, and Women-Owned Small Business. All small business 23 goals shall be expressed in terms of percentage goals IAW FAR 19.704. DoD subcontracting goals are not 24 required to be duplicated in each Offeror’s Small Business Subcontracting Plan. Offerors are encouraged, 25 but not required to submit a plan that supports DoD goals except for a minimum 5% Small 26 Disadvantaged Business goal. The DoD subcontracting goals are informational, but the government will 27 use the Subcontracting Checklists when reviewing subcontracting Plans submitted. The intent of this 28 plan is to convince the Government that the individual will successfully be able to perform the work at 29 the alternate location at minimal risk to the Government. 30

The subcontracting plan is limited to 5 pages. 31

4.3.6 Section K, Representations, Certifications, and Other Statements of Offerors 32

The Offeror shall complete all “fill-ins” and provide all the representations, certifications, and 33 statements required by Section K of this solicitation. All certifications and representations required by 34 Section K of the solicitation shall be completed as of the date of contract award. 35

The Offeror shall complete representations, certification, acknowledgments, and statements via the 36 System for Award Management (SAM) (http://sam.gov). A completed copy from SAM and any additional 37 Section K information required by this solicitation shall be included in this volume. Section K shall not 38 count against page count limitations. 39 http://sam.gov/

L1. Sample Government Reference Staffing Matrix 1

L1. DRAFT Sample Gov Ref Staffing Matrix dRFP.xlsx

Remainder of page left intentionally blank. 14

L2. SF 1407 Pre-Award Survey of Prospective Contractor 1

L2. SF 1407

PreAward Survey of Prospective Contractor (Financial Capability) v2.pdf

Remainder of page left intentionally blank. 13

L3. OCI Mitigation Plan Checklist 1

SPACE SYSTEMS COMMAND 2

ORGANIZATIONAL CONFLICTS OF INTEREST (OCI) 3

MITIGATION PLAN CHECKLIST 4

October 2018 5

1 General Considerations Page/Para

1.1 A clear statement of corporate commitment to continuously identify and avoid or mitigate OCI situations for this acquisition signed by senior corporate official (Vice President or above).

1.2 Description of the position of the business unit performing this contract effort within the overall corporate structure.

1.3 Organizational charts for the parent organization and the performing business unit (e.g., division, sector, subsidiary, affiliate).

1.4 Letters of commitment to the prime contractor’s OCI Plan from all teammates and subcontractors or individual OCI Plans from all teammates and subcontractors attached to prime contractor’s OCI Plan.

2 Definitions

2.1 Definition of terms used in the OCI Plan.

2.2 Definitions of acronyms used in the OCI Plan.

3 Management of OCI Plan

3.1 Identification of individual responsible for oversight and administration of the OCI Plan by position and place in company/business unit organizational structure.

3.2 Identification of individual responsible for maintaining documentation related to OCI Plan by position and place in company/business unit organizational structure.

3.3 Location where OCI Plan documentation will be maintained and commitment that the location will be easily accessible by Contracting Officer or Government auditor.

3.4 Identification of corporate OCI-related policies and procedures (policies and procedures shall be attached to the OCI Plan).

3.5 Description of processes and procedures implemented to execute the OCI Plan.

3.6 Commitment to flow OCI Plan requirements down to all teammates and subcontractors. Only those teammates and subcontractors who have committed to the Contractor’s OCI Plan in writing or provided an OCI Plan of their own shall be allowed to commence work on this contract.

3.7 Description of process for advance notification to Contracting Officer of addition, deletion, or changes to subcontractors and teammates. Notification shall include sufficient information for the Contracting Officer to determine whether or not the OCI situation has changed.