Changed: 9/14/2021

UPDATED 14 SEP 2021: THE GOVERNMENT IS NOT GOING TO HOLD AN INDUSTRY DAY FOR THIS SOURCES SOUGHT.

Purpose:

This is a Sources Sought. The Space Systems Command (SSC), Enterprise Corps and Special Programs Directorate located at Los Angeles Air Force Base, California, is seeking information in the form of Statements of Capabilities (SOC) from interested parties in support of the SSC/ECZJ Warfighting Enterprise Division requirement for the Space Electromagnetic Warfare Operating Location (SEWOL) described below.  The Government is conducting early market research to inform its Acquisition Strategy. 

The purpose of this notice is to identify potential sources that can meet SSC/EZCJ’s requirement.  The Government reserves the right to set this acquisition, or portions thereof, aside for small business – to include socially and economically disadvantaged businesses, 8(a) firms, or woman-owned businesses. The Government is seeking contractors interested in and capable of providing all technical and logistical effort required to design, develop, and deliver the SEWOL. 

Background and Description:

Scope:  This effort encompasses all technical and logistical effort required to design, develop and deliver the SEWOL.  It includes but is not limited to: hardware architecture design and development; software architecture design and development; communications/networking design and development; integration of Government Furnished Equipment (GFE) Electromagnetic Warfare (EW) weapon systems; sustainment and logistics program definition and execution; DevSecOps support and execution post initial delivery; and operator training program development and execution. 

Period and Place of Performance:  The period of performance is anticipated to be Q3 2022 – Q3 2027.  This period covers the time from contract award through delivery and the first two years of sustainment and training support.  The design activity may occur at a location selected by the contractor that meets security requirements.  The operationally fielded SEWOL locations are TBD but anticipated to have primary and alternative CONUS locations.

Background:  The SEWOL will be the USSF’s consolidated operating location for the planning, tasking and execution of Space Electromagnetic Warfare (SEW) operations.  The SEWOL will provide four primary functions:

  1. The Space EW Common Operating Picture (SEWCOP)
    • The SEWCOP will display relevant SEW information to the RMT/Meadowlands operators and SEWOL chief
  2. Mission Planning, Execution, and Command & Control (C2) Infrastructure and Applications
    • The tactical C2 infrastructure will include translating the operational level Space Tasking Order into executable tactical instructions, planning weapon-target pairings, & enabling automated control of multiple SEW assets by a single operator
  3. Remote Space EW Physical & Cloud based Infrastructure
    • The SEWOL will remotely operate a scalable number of SEW assets
    • CCS Meadowlands and Remote Modular Terminals (RMTs) remote operations infrastructure will be integrated into SEWOL
  4. Mission Resiliency and Assurance Infrastructure
    • Develop and integrate infrastructure that will enable continuity of operations across all phases of conflict, by using system redundancy or other means.
    • Implement DevSecOps methodology that will allow timely and secured updates to software, such as when new vulnerability or feature is identified.

The SEWOL initial baseline will include the following: the SEWCOP, secure communications with operational C2 for receipt of high-level tasking orders; weapon system control for Meadowlands [also known as Counter Communications System (CCS) Block 10.3] Remote Operations; and remote weapon system control for RMTs.

Both Meadowlands and its remote operations capability were developed by L3Harris Technologies and will be GFE to SEWOL, see attached GFE List.  RMTs will be GFE to SEWOL, provided by a to-be-determined developer.  The SEWOL contractor will integrate the Meadowlands and RMT Remote Operations capability into the SEWOL architecture. 

The SEWOL will have an initial CONUS operating location. It will then expand to include multiple geographically dispersed operating locations. These locations will be able to control a scalable number of assets. In addition, they can be used interchangeably and/or collaboratively to provide high resiliency and operational flexibility. The SEWOL architecture will support SEW systems developed by different contractors and with different capabilities, including both Meadowlands and RMT. The SEWOL network and infrastructure will enable DevSecOps with Continuous Integration and Continuous Delivery (CI/CD) capability enhancements and fulfill USSF operational requirements regarding training and cybersecurity.

A portion of the work done on this effort will be at the Top Secret Special Compartmentalized Information level.  Appropriate certified facilities and cleared personnel will be required.

Performance Objectives:  The SEWCOP will provide a visual, searchable, and interactive near real-time picture of current global SEW activities, availability, and functional status. The SEWCOP will depict the current SEW focused adversary Space Order of Battle (SOB), the current state of SEW tasking, and real-time status of operations.  The information displayed in the SEWCOP will be aggregated from real time intelligence, C2, and operational units.  The information from intelligence will include SOB and Battle Damage Assessment (BDA). Command and control (C2) will provide its information to SEWOL via secure communications. Operational units will provide systems status, electromagnetic support (ES) reporting, Electromagnetic Attack (EA) strike assessment, and remote assets situational awareness (SA).

The SEWOL will provide the infrastructure, cloud based or bare metal, required to manage and remotely operate EW systems from multiple geographic locations.  This includes network infrastructure (NIPRnet, SIPRnet, and JWICS), processing infrastructure for SEW systems, and the development of a Common Operating Interface (COI).  The development and subsequent sustainment model of this infrastructure will be highly scalable.  This infrastructure will be capable of function up to a Top Secret/Sensitive Compartmented Information (SCI) security level.

The SEWOL will be developed in parallel with RMT systems and will be integrated using the DevSecOps model.  The Meadowlands remote terminal will be used to operate the RMTs via the SEWOL infrastructure and will be integrated into the SEWCOP and C2 architecture.  SEWOL will have an initial capability to operate RMT systems and support acceptance testing.

The SEWOL architecture will be scalable and flexible to allow incorporation of future SEW systems. Future SEW systems could have substantially different interfaces from the RMT and Meadowlands systems without a baseline interface, and the development of the COI will help streamline integration of future systems.

Schedule and Key Deliverables: 

Authority to Proceed (ATP) – Contract Award

ATP + 9 Months – Initial operational capability (IOC) – Secure communications to operational C2 elements and Meadowlands Remote Operations co-located.  Connectivity/Interface to higher level C2 authorities — the SEWOL will need to have NIPRnet, SIPRnet, and JWICS terminals.  RMTs Block 0 available to SEWOL integrator.  Connectivity/Interface to enable Meadowlands Remote Operations and acceptance testing of RMTs.  Initial Operator Training.  DevSecOps infrastructure and developers in place.  Sustainment / Logistics processes and capabilities in place.  The initial SEWCOP with critical SA information available to the operator.  Processing infrastructure for SEW systems automation and optimization.

ATP + 27 Months – Full operational capability (FOC) – IOC plus SEWCOP.  Connectivity/Interface to Intel sources.  Title 50 operating area.  Application for SEW systems automation and optimization.  Updated Operator Training. Addition of RMT operations.

ATP + 36 Months – Transition from development to sustainment.

ATP + 60 Months– End of Period of Performance

Response Content:

Interested vendors must submit a Statement of Capability (SOC) in a narrative report that includes both the company information and responses to the questions below. All SOCs are to be submitted in accordance with the administrative requirements identified herein.

SOC Administrative Requirements:

The Government requests a maximum 10 page response with a 3 page limit for Company Information and Corporate Capabilities & Experience.  Please submit via email to all the following points of contact:

         doreen.barnett@spaceforce.mil

         clifford.johnson.6@spaceforce.mil 

         grace.machado@spaceforce.mil

Submitted SOCs must include all of the following information:

Company Information:

1. Company name

2. Company’s ownership and other relevant information

3. Personnel/Business size classification (Small/Large Business, HUB, veteran, etc.)

4. Mailing address

5. Point of Contact (POC) including e-mail and telephone numbers

Corporate Capabilities & Experience:

Describe work your company has performed and company expertise which is relevant to the role of a Prime Contractor. Also provide information related to:

1. History with distributed Ground Radio Frequency (RF) / Other sensor equipment and services

2. Relevant products and services

3. Subcontractor's capabilities, products and services

4. Corporate and teaming experience to procure, produce, integrate and test operational control centers, networks, and other relevant infrastructure

Please answer as many of the following questions in the SOCs:

Technical Questions: 

  1.   What processes and solutions would you use to execute this effort?
  2.   What security architecture would you use to execute this effort?
  3. What experience do you have and/or what approach would you use to interface with multiple-agency networks and data sources?
  4.   How would you implement the infrastructure to support SEWOL?
    1. What technical architecture would you propose?
    2. What processes would you use?
  5.   Are there on-going government efforts which could be leveraged to achieve our goals?
  6.   What do you see as the major challenges (technical, security, programmatic, etc.)?
  7.   What will you need from L3H and the future RMT developer to successfully integrate their delivered Remote Ops software and infrastructure into a cloud-base?
  8.   What Information or GFE will you need from the Meadowlands Program or RMT program to ensure the success of the SEWOL? When will you need that information? (example: Need the ICDs for the RMT 8 months after award?)  Feel free to reply to this directly on the attached GEF list. 
  9.   What critical pieces of the SEWOL have been left out of the description above?
  10. How do you see intel ops integrated with EW ops on the SEWOL Ops floor?
  11. What is the best approach to test and validate this capability for operations?
  12. Describe your approach to migrate and host GFE s/w and network infrastructure into an existing cloud based infrastructure?

Contractual / Business Questions: 

  1.   Do you have any concerns regarding the timeline or Period of Performance?
  2.   Are you a small business? If not, what do you believe would be a good goal for Small Business set aside for this requirement?
  3.   Do you plan to partner with other contractors?
  4.   Respondents are to discuss risk and willingness to deliver under a Fixed-Price Incentive (Firm Target) contract type.
  5. Discuss any key cost and schedule drivers, cost tradeoffs, schedule considerations, and assumptions
  6.   How could the government better incentivize primes, subs, and EW system developers to meet requirements and schedule?
  7.   Do you have any recommendations and rationale for an incentive and payment structure?
  8.   Do you anticipate using any proprietary technology or information as part of proposed solution?
  9.   What other contract vehicles do you have in place with SSC or other government organizations that SEWOL may be able to leverage?
  10.   What support will you need from L3H and the future RMT developer to successfully integrate their delivered Remote Ops terminals/hardware into SEWOL?
  11.   What kind of incentive structure would you recommend to ensure both parties work effectively together?

Response Classification: Narrative and SOC reports may be up to TOP SECRET/SCI/SAP. Materials will be reviewed separately at Los Angeles AFB, CA. If a Contractor plans to submit a SAPs level SOC, submission needs to be coordinated no later than (NLT) one week in advance of submission. All material provided in response to this notice shall be kept non-confidential and non-proprietary to the maximum extent practicable. Firms providing confidential/proprietary information shall separately and clearly identify and mark all confidential/proprietary information. The USSF will take all necessary steps to protect/safeguard any confidential/proprietary information provided. The USSF will NOT be held responsible for any proprietary information not clearly marked.

Disclaimers and Notes – THIS IS A REQUEST FOR INFORMATION ONLY. This notice is issued solely for information and planning purposes. It does not constitute a solicitation (Request for Proposal or Request for Quotations) or a promise to issue a solicitation in the future. This notice does not commit the USSF to contract for any supply or service whatsoever. Furthermore, the USSF is not, at this time, seeking proposals. Responders are advised that the USSF will not pay for any information or administrative costs incurred in response to this notice. The Government will not assume liability for costs incurred by any attendee for travel expenses or marketing efforts. All costs associated with responding to this notice will be solely at the responding party's expense.

The following companies/organizations may review the submitted responses: The Aerospace Corporation, Tyto Corporation, SAIC, RSE, ARK GSI, and Tecolote.  Thes companies are bound by appropriate non-disclosure agreements with the USSF. For further information regarding these agreements, contact the Contracting Officer identified herein.

Appendices:  Appendices B and C to this document are CUI documents that must be controlled appropriately, in compliance with National Industrial Security Program guidance.  To receive all appendices, please email Maj Clifford Johnson, clifford.johnson.6@us.af.mil and Ms. Grace Machado, grace.machado@spaceforce.mil, the appendices will be sent back in an encrypted email once the Contractor has been appropriately vetted. 

  • Appendix B, Charts supporting the Government’s Industry Day briefing
  • Appendix C, List of GFE to be provided to the SEWOL Contractor

Purpose:

This is a Sources Sought. The Space Systems Command (SSC), Enterprise Corps and Special Programs Directorate located at Los Angeles Air Force Base, California, is seeking information in the form of Statements of Capabilities (SOC) from interested parties in support of the SSC/ECZJ Warfighting Enterprise Division requirement for the Space Electromagnetic Warfare Operating Location (SEWOL) described below.  The Government is conducting early market research to inform its Acquisition Strategy. 

The purpose of this notice is to identify potential sources that can meet SSC/EZCJ’s requirement.  The Government reserves the right to set this acquisition, or portions thereof, aside for small business – to include socially and economically disadvantaged businesses, 8(a) firms, or woman-owned businesses. The Government is seeking contractors interested in and capable of providing all technical and logistical effort required to design, develop, and deliver the SEWOL. 

Background and Description:

Scope:  This effort encompasses all technical and logistical effort required to design, develop and deliver the SEWOL.  It includes but is not limited to: hardware architecture design and development; software architecture design and development; communications/networking design and development; integration of Government Furnished Equipment (GFE) Electromagnetic Warfare (EW) weapon systems; sustainment and logistics program definition and execution; DevSecOps support and execution post initial delivery; and operator training program development and execution. 

Period and Place of Performance:  The period of performance is anticipated to be Q3 2022 – Q3 2027.  This period covers the time from contract award through delivery and the first two years of sustainment and training support.  The design activity may occur at a location selected by the contractor that meets security requirements.  The operationally fielded SEWOL locations are TBD but anticipated to have primary and alternative CONUS locations.

Background:  The SEWOL will be the USSF’s consolidated operating location for the planning, tasking and execution of Space Electromagnetic Warfare (SEW) operations.  The SEWOL will provide four primary functions:

  1. The Space EW Common Operating Picture (SEWCOP)
    • The SEWCOP will display relevant SEW information to the RMT/Meadowlands operators and SEWOL chief
  2. Mission Planning, Execution, and Command & Control (C2) Infrastructure and Applications
    • The tactical C2 infrastructure will include translating the operational level Space Tasking Order into executable tactical instructions, planning weapon-target pairings, & enabling automated control of multiple SEW assets by a single operator
  3. Remote Space EW Physical & Cloud based Infrastructure
    • The SEWOL will remotely operate a scalable number of SEW assets
    • CCS Meadowlands and Remote Modular Terminals (RMTs) remote operations infrastructure will be integrated into SEWOL
  4. Mission Resiliency and Assurance Infrastructure
    • Develop and integrate infrastructure that will enable continuity of operations across all phases of conflict, by using system redundancy or other means.
    • Implement DevSecOps methodology that will allow timely and secured updates to software, such as when new vulnerability or feature is identified.

The SEWOL initial baseline will include the following: the SEWCOP, secure communications with operational C2 for receipt of high-level tasking orders; weapon system control for Meadowlands [also known as Counter Communications System (CCS) Block 10.3] Remote Operations; and remote weapon system control for RMTs.

Both Meadowlands and its remote operations capability were developed by L3Harris Technologies and will be GFE to SEWOL, see attached GFE List.  RMTs will be GFE to SEWOL, provided by a to-be-determined developer.  The SEWOL contractor will integrate the Meadowlands and RMT Remote Operations capability into the SEWOL architecture. 

The SEWOL will have an initial CONUS operating location. It will then expand to include multiple geographically dispersed operating locations. These locations will be able to control a scalable number of assets. In addition, they can be used interchangeably and/or collaboratively to provide high resiliency and operational flexibility. The SEWOL architecture will support SEW systems developed by different contractors and with different capabilities, including both Meadowlands and RMT. The SEWOL network and infrastructure will enable DevSecOps with Continuous Integration and Continuous Delivery (CI/CD) capability enhancements and fulfill USSF operational requirements regarding training and cybersecurity.

A portion of the work done on this effort will be at the Top Secret Special Compartmentalized Information level.  Appropriate certified facilities and cleared personnel will be required.

Performance Objectives:  The SEWCOP will provide a visual, searchable, and interactive near real-time picture of current global SEW activities, availability, and functional status. The SEWCOP will depict the current SEW focused adversary Space Order of Battle (SOB), the current state of SEW tasking, and real-time status of operations.  The information displayed in the SEWCOP will be aggregated from real time intelligence, C2, and operational units.  The information from intelligence will include SOB and Battle Damage Assessment (BDA). Command and control (C2) will provide its information to SEWOL via secure communications. Operational units will provide systems status, electromagnetic support (ES) reporting, Electromagnetic Attack (EA) strike assessment, and remote assets situational awareness (SA).

The SEWOL will provide the infrastructure, cloud based or bare metal, required to manage and remotely operate EW systems from multiple geographic locations.  This includes network infrastructure (NIPRnet, SIPRnet, and JWICS), processing infrastructure for SEW systems, and the development of a Common Operating Interface (COI).  The development and subsequent sustainment model of this infrastructure will be highly scalable.  This infrastructure will be capable of function up to a Top Secret/Sensitive Compartmented Information (SCI) security level.

The SEWOL will be developed in parallel with RMT systems and will be integrated using the DevSecOps model.  The Meadowlands remote terminal will be used to operate the RMTs via the SEWOL infrastructure and will be integrated into the SEWCOP and C2 architecture.  SEWOL will have an initial capability to operate RMT systems and support acceptance testing.

The SEWOL architecture will be scalable and flexible to allow incorporation of future SEW systems. Future SEW systems could have substantially different interfaces from the RMT and Meadowlands systems without a baseline interface, and the development of the COI will help streamline integration of future systems.

Schedule and Key Deliverables: 

TBD early October 2021 – Industry Day

Authority to Proceed (ATP) – Contract Award

ATP + 9 Months – Initial operational capability (IOC) – Secure communications to operational C2 elements and Meadowlands Remote Operations co-located.  Connectivity/Interface to higher level C2 authorities — the SEWOL will need to have NIPRnet, SIPRnet, and JWICS terminals.  RMTs Block 0 available to SEWOL integrator.  Connectivity/Interface to enable Meadowlands Remote Operations and acceptance testing of RMTs.  Initial Operator Training.  DevSecOps infrastructure and developers in place.  Sustainment / Logistics processes and capabilities in place.  The initial SEWCOP with critical SA information available to the operator.  Processing infrastructure for SEW systems automation and optimization.

ATP + 27 Months – Full operational capability (FOC) – IOC plus SEWCOP.  Connectivity/Interface to Intel sources.  Title 50 operating area.  Application for SEW systems automation and optimization.  Updated Operator Training. Addition of RMT operations.

ATP + 36 Months – Transition from development to sustainment.

ATP + 60 Months– End of Period of Performance

Response Content:

Interested vendors must submit a Statement of Capability (SOC) in a narrative report that includes both the company information and responses to the questions below. All SOCs are to be submitted in accordance with the administrative requirements identified herein.

SOC Administrative Requirements:

The Government requests a maximum 10 page response with a 3 page limit for Company Information and Corporate Capabilities & Experience.  Please submit via email to all the following points of contact:

         doreen.barnett@spaceforce.mil

         clifford.johnson.6@spaceforce.mil 

         grace.machado@spaceforce.mil

Submitted SOCs must include all of the following information:

Company Information:

1. Company name

2. Company’s ownership and other relevant information

3. Personnel/Business size classification (Small/Large Business, HUB, veteran, etc.)

4. Mailing address

5. Point of Contact (POC) including e-mail and telephone numbers

Corporate Capabilities & Experience:

Describe work your company has performed and company expertise which is relevant to the role of a Prime Contractor. Also provide information related to:

1. History with distributed Ground Radio Frequency (RF) / Other sensor equipment and services

2. Relevant products and services

3. Subcontractor's capabilities, products and services

4. Corporate and teaming experience to procure, produce, integrate and test operational control centers, networks, and other relevant infrastructure

Please answer as many of the following questions in the SOCs:

Technical Questions: 

  1.   What processes and solutions would you use to execute this effort?
  2.   What security architecture would you use to execute this effort?
  3. What experience do you have and/or what approach would you use to interface with multiple-agency networks and data sources?
  4.   How would you implement the infrastructure to support SEWOL?
    1. What technical architecture would you propose?
    2. What processes would you use?
  5.   Are there on-going government efforts which could be leveraged to achieve our goals?
  6.   What do you see as the major challenges (technical, security, programmatic, etc.)?
  7.   What will you need from L3H and the future RMT developer to successfully integrate their delivered Remote Ops software and infrastructure into a cloud-base?
  8.   What Information or GFE will you need from the Meadowlands Program or RMT program to ensure the success of the SEWOL? When will you need that information? (example: Need the ICDs for the RMT 8 months after award?)  Feel free to reply to this directly on the attached GEF list. 
  9.   What critical pieces of the SEWOL have been left out of the description above?
  10. How do you see intel ops integrated with EW ops on the SEWOL Ops floor?
  11. What is the best approach to test and validate this capability for operations?
  12. Describe your approach to migrate and host GFE s/w and network infrastructure into an existing cloud based infrastructure?

Contractual / Business Questions: 

  1.   Do you have any concerns regarding the timeline or Period of Performance?
  2.   Are you a small business? If not, what do you believe would be a good goal for Small Business set aside for this requirement?
  3.   Do you plan to partner with other contractors?
  4.   Respondents are to discuss risk and willingness to deliver under a Fixed-Price Incentive (Firm Target) contract type.
  5. Discuss any key cost and schedule drivers, cost tradeoffs, schedule considerations, and assumptions
  6.   How could the government better incentivize primes, subs, and EW system developers to meet requirements and schedule?
  7.   Do you have any recommendations and rationale for an incentive and payment structure?
  8.   Do you anticipate using any proprietary technology or information as part of proposed solution?
  9.   What other contract vehicles do you have in place with SSC or other government organizations that SEWOL may be able to leverage?
  10.   What support will you need from L3H and the future RMT developer to successfully integrate their delivered Remote Ops terminals/hardware into SEWOL?
  11.   What kind of incentive structure would you recommend to ensure both parties work effectively together?

Response Classification: Narrative and SOC reports may be up to TOP SECRET/SCI/SAP. Materials will be reviewed separately at Los Angeles AFB, CA. If a Contractor plans to submit a SAPs level SOC, submission needs to be coordinated no later than (NLT) one week in advance of submission. All material provided in response to this notice shall be kept non-confidential and non-proprietary to the maximum extent practicable. Firms providing confidential/proprietary information shall separately and clearly identify and mark all confidential/proprietary information. The USSF will take all necessary steps to protect/safeguard any confidential/proprietary information provided. The USSF will NOT be held responsible for any proprietary information not clearly marked.

Industry Day and One-on-One Session Details:

One-on-One Sessions – The Government will host One-on-One sessions following Industry Day. The Contractor will have the opportunity to discuss their SOC, their ability to provide solutions that meet the USSF’s needs and ask the Government any clarifying questions on SEWOL requirements.

Rules of Engagement (ROEs):

  • The purpose of One-on-Ones is for Contractors to better understand the Government’s requirements and for the Government to better understand Contractor capabilities in order to produce a robust acquisition strategy   
  • Information not pertaining to the SEWOL requirement will not be discussed
  • Government Budget will not be discussed
  • Information the government is sharing about SEWOL is pre-decisional to the Acquisition Strategy
  • Details of the requirement are subject to change

Date: TBD early October 2021

Location: TBD El Segundo, CA

Format:  Industry Day will be hosted simultaneously both in-person and Video Tele-Conference (VTC), details will be provided in Appendix A.   The Government will provide a briefing on the vision for SEWOL, this will be followed by 1 hour One-on-One sessions with each Contractor.  The total number of attendees each company may bring to the One-on-One Sessions is limited to five representatives (technical and executive-level representation is desired).  One-on-One presentations shall be kept at the UNCLASSIFIED and/or SECRET levels to the highest extent possible. To request TOP SECRET and above One-on-Ones, email Maj Clifford Johnson, clifford.johnson.6@us.af.mil and Ms. Grace Machado, grace.machado@spaceforce.mil for additional information.

Registration: To register for Industry Day and One-on-One Sessions, complete and submit registration in accordance with Appendix A.

Disclaimers and Notes – THIS IS A REQUEST FOR INFORMATION ONLY. This notice is issued solely for information and planning purposes. It does not constitute a solicitation (Request for Proposal or Request for Quotations) or a promise to issue a solicitation in the future. This notice does not commit the USSF to contract for any supply or service whatsoever. Furthermore, the USSF is not, at this time, seeking proposals. Responders are advised that the USSF will not pay for any information or administrative costs incurred in response to this notice. The Government will not assume liability for costs incurred by any attendee for travel expenses or marketing efforts. All costs associated with responding to this notice will be solely at the responding party's expense.

The following companies/organizations may review the submitted responses and may be in attendance at the One-on-One Sessions: The Aerospace Corporation, Tyto Corporation, SAIC, RSE, ARK GSI, and Tecolote.  Thes companies are bound by appropriate non-disclosure agreements with the USSF. For further information regarding these agreements, contact the Contracting Officer identified herein.

Appendices:  Appendices B and C to this document are CUI documents that must be controlled appropriately, in compliance with National Industrial Security Program guidance.  To receive all three appendices, please email Maj Clifford Johnson, clifford.johnson.6@us.af.mil and Ms. Grace Machado, grace.machado@spaceforce.mil, the appendices will be sent back in an encrypted email once the Contractor has been appropriately vetted. 

  • Appendix A, Industry Day registration instructions
  • Appendix B, Charts supporting the Government’s Industry Day briefing
  • Appendix C, List of GFE to be provided to the SEWOL Contractor