Request for Information - EPPM (15 Jul 2026).pdf

Space Access

Enterprise Payload Processing Management

Request for Information

The United States Space Force (USSF) Space Access is pursuing an Enterprise Payload Processing Management (EPPM) effort to more efficiently manage USSF Space Vehicle (SV) processing on the Eastern and Western Launch Ranges, as well as other U.S. launch bases. The Government is utilizing this Request for Information (RFI) to solicit Industry feedback regarding the overall technical framework, acquisition strategy, and operational requirements outlined in the EPPM draft RFP. The Government’s objective is to deliver a viable solicitation that aligns with market realities and with emerging industry capabilities to ensure long-term operational success.

I. Background

SV processing is an integral part of the launch segment for all space missions. National Security Space (NSS), civil, and commercial missions all utilize the same commercial facilities for payload processing needs. The Government forecasts demand for these PPFs to greatly increase over the next five years with growing SV requirements for proliferated architectures. Currently, USSF SV program offices secure their own PPF services via individual contracts with commercial PFF providers. As demand increases for these commercial PPFs, NSS faces challenges in availability to meet critical space mission requirements.

Space Access is transitioning to a centralized management model to optimize the use of limited payload processing capacity, and increased schedule insight for commercial PPFs across NSS, civil, and commercial missions. This effort, EPPM, will transition from the ad hoc approach where individual System Program Offices (SPOs) and their SV contractors procure PPF services to a centralized approach where Space Access will schedule and procure PPF services for the USSF SV SPOs. The responses from this RFI will help inform the RFP to support a planned award of the EPPM effort in Calendar Year 2026.

II. EPPM Contract Framework

The EPPM Multiple Award Indefinite-Delivery, Indefinite-Quantity (IDIQ) contracts will feature a five

(5) year basic ordering period. To ensure a competitive and modern industrial base, the Government intends to utilize on-ramp procedures on an annual basis, or when market research identifies new qualified providers. These on-ramps will afford new entrants the opportunity to compete for an IDIQ contract award and receive the initial minimum order for Order Year 1 "Schedule and Technical Insight" Task Order. Additionally, the Government plans to open the IDIQ annually—and dynamically when market research dictates—to allow existing contract holders to add newly available capabilities to their contracts.

Once on the IDIQ basic contract, the IDIQ basic contract holders who meet the minimum IDIQ Payload Processing Task Order qualification criteria will be able to compete for specific mission(s) Payload Processing Services Task Orders.

Payload Processing Task Order mission requirements may be competed individually or in blocks, and each task order proposal must include a fully burdened cost bid (i.e., all costs associated with performing defined mission requirements in the Task Order PWS). All task orders will be issued on a Firm-Fixed- Price (FFP) basis.

All PPF Service Task Orders will require the Standard Service as defined in PWS Section 3 and PWS Appendix A. Based on the requirements for an individual PPF Service Task Order, the Non-Standard Services in PWS Section 4 and PWS Appendix B can be ordered in part as an a la carte menu.

III. Requested Information

While the Government requests a comprehensive review of the Draft RFP solicitation in its entirety, we are seeking focused feedback on the specific areas identified below. For any recommended changes or identified concerns, please provide the underlying technical and contractual rationale to assist the Government in its understanding of industry's position:

1. Location Security & COMSEC Infrastructure: Provide feedback on the feasibility of the Communications Security (COMSEC) requirements currently embedded in the Performance Work Statement (PWS). Does your facility possess the infrastructure and cleared personnel to meet these requirements immediately upon award? If not, please define the compliance gaps, necessary mitigations and the projected timeline to achieve full mission readiness.

2. Roles and Responsibilities: Provide feedback on the proposed division of responsibility between the SV provider and the PPF regarding the handling, storage, and accountability of COMSEC materials. Specifically, does the draft PWS clearly define the chain of custody and the demarcation of requirements for SV unique customer equipment versus PPF provided infrastructure? If ambiguities exist, please provide us with the technical or contractual rationale for proposed clarifications.

3. Priority Rights & Operational Flexibility: Provide feedback on the Priority Right to Use (PRTU) and Right of First Refusal (ROFR) language. Identify specific impacts these clauses have on your ability to support concurrent commercial missions.

4. Scheduling, Delays, and SV Swaps Clause: Provide feedback on the Government’s drafted SSC H01 "Scheduling, Delays, and SV Swaps Clause" logic.

a. Is the notification window sufficient to reallocate resources without significant financial penalty to the PPF providers?

b. What are your commercial delay terms and costs associated with it? Please explain your commercial rules for schedule delays, including the specific costs and fee structures applied when a mission misses its planned processing dates or has unexpected processing extensions.

5. FOPR Response Turnaround for PPF Services Task Orders: The Government intends to utilize a 5 calendar day response window for standard Fair Opportunity Proposal Requests (FOPR) PPF Services Task Orders. Identify any internal corporate restrictions (Legal, Organization Conflict of Interest, or Security) that would preclude a technically acceptable response within this proposed timeframe.

6. IDIQ Standard Services: Review the Standard Services in PWS Section 3 and specific requirements in PWS Appendix A. Please identify any mission essential requirements or baseline operational activities that may have been omitted which should be considered part of the Standard Service offering. Please provide a technical rationale for any recommended additions to the standard baseline.

7. IDIQ Non-Standard Services: Review the Non-Standard Services described in PWS Section 4 and specific requirements in PWS Appendix B. Please identify if the distinction between Standard and Non-Standard services is clearly defined to allow for accurate Task Order pricing. Are there mission unique or specialized services omitted from this section that should be included to ensure the IDIQ can accommodate more complex mission requirements? Please provide a technical and contractual rationale for any proposed additions or clarifications to these service definitions.

8. PWS Section Organization: Please provide feedback on whether the scope within each PWS section, Minimum Order (PWS Section 2), Standard Services (Section 3), and Non-Standard Services (PWS Section 4), is logical. If not, please provide recommendations on how to improve organization of work scope in the abovementioned PWS sections.

9. Government Furnished Property (GFP): Please identify if your PPF typically utilizes GFP to maintain mission readiness.

10. Payment Plan: Does the draft RFP Payment Plan align or differ with your commercial payment terms? Please provide your commercial payment terms for PPF services (standard and non-standard).

11. It is the Government’s intention to execute EPPM with maximum speed and efficiency.

Respondents are invited to submit innovative ideas regarding RFP and contract structure that will facilitate rapid implementation and execution of Payload Processing Services.

12. The Government will incorporate the below terms and conditions into the EPPM Request for Proposal (RFP). The language and its planned location is provided below:

Language Anticipated RFP Location

OMBUDSMAN

a. An ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition. When requested, the ombudsman will maintain strict confidentiality as to the source of the concern. The existence of the ombudsman does not affect the authority of the program manager, contracting officer, or source selection official. Further, the ombudsman does not participate in the evaluation of proposals, the source selection process, or the adjudication of protests or formal contract disputes. The ombudsman may refer the interested party to another official who can resolve the concern.

b. Before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the contracting officer for resolution. Consulting an ombudsman does not alter or postpone the timelines for any other processes (e.g., agency level bid protests, GAO bid protests, requests for debriefings, employee-employer actions, contests of OMB Circular A-76 competition performance decisions).

c. If resolution cannot be made by the contracting officer, the interested party may contact the ombudsman, Col Aaron H.

Thomas, Phone: 310-653-1785, Email:

aaron.thomas.2@spaceforce.mil, Address: SSC/PK, Attn:

Colonel Aaron H. Thomas, 483 N. Aviation Blvd El Segundo, CA 90245. Concerns, issues, disagreements, and recommendations that cannot be resolved at the Center/MAJCOM/FLDCOM/DRU ombudsman level, may

Attachment 8, Instructions to Offerors mailto:aaron.thomas.2@spaceforce.mil be brought by the interested party for further consideration to the Department of the Air Force ombudsman, Associate Deputy Assistant Secretary (ADAS) (Contracting), SAF/AQC, 1060 Air Force Pentagon, Washington DC 20330-1060, phone number (571) 256-2395, facsimile number (571) 256-2431.

d. The ombudsman has no authority to render a decision that binds the agency.

e. Do not contact the ombudsman to request copies of the solicitation, verify offer due date, or clarify technical requirements. Such inquiries shall be directed to the contracting officer.

NOTIFICATION OF GOVERNMENT SECURITY

ACTIVITIES

This contract contains a DD Form 254, DOD Contract Security Classification Specification, and requires performance at a government location in the U.S. or overseas. Prior to beginning operations involving classified information on an installation identified on the DD Form 254, the contractor shall take the following actions:

(a) At least thirty days prior to beginning operations, notify the Information Protection Office shown in the distribution block of the DD Form 254 as to:

1. The name, address, and telephone number of this contract company’s representative and designated alternate in the U.S. or overseas area, as appropriate;

2. The contract number and military contracting command;

3. The highest classification category of defense information to which contractor employees will have access;

4. The Department of the Air Force installations in the U.S. (in overseas areas, identify only the APO number(s)) where the contract work will be performed;

5. The date contractor operations will begin on base in the U.S.

or in the overseas area;

6. The estimated completion date of operations on base in the U.S. or in the overseas area; and,

7. Any changes to information previously provided.

Attachment 1, IDIQ Performance Work Statement

SECURITY INCIDENT REPORTING AND PROCEDURES

(a) The contractor shall follow the below guidance when a contract contains a DD Form 254, DOD Contract Security Classification Specification:

1. The contractor shall notify the Government Contracting Activity (GCA) of any security incident involving the potential or actual loss, compromise, or suspected compromise of Top Secret, Secret, and/or Confidential information, referred to as classified information, when the incident is discovered at the contractor’s location.

a. The contractor shall conduct the requisite inquiry(ies) in accordance with 32 CFR Part 117 and Cognizant Security Office (e.g., Defense Counterintelligence and Security Agency) guidance.

2. Security incidents occurring at government performance locations where the contractor is categorized as a visitor will be processed and reported in accordance with government host security procedures.

3. Security incidents involving the potential or actual loss, compromise, or suspected compromise of Special Access Program and/or Sensitive Compartmented Information is under the jurisdiction of the GCA and the contractor shall follow GCA guidance in lieu of this requirement.

4. This requirement does not relieve the contractor from reporting requirements set forth in 32 CFR Part 117, DFARS 252.204-7012, or as otherwise directed by contract requirements and/or its Cognizant Security Office (e.g., Defense Counterintelligence and Security Agency).

5. This requirement does not relieve the contractor from adhering to security incident guidance set forth by its Cognizant Security Office (e.g., Defense Counterintelligence and Security Agency).

6. The contractor is responsible for ensuring all applicable subcontracts include these security incident reporting requirements.

7. If the lost or compromised information is beyond the jurisdiction of the U.S. Government and cannot be recovered (e.g., media leak, public website posting, or loss in a foreign country), the notification and location of the compromise (e.g., geographic location of unrecoverable equipment) shall be classified commensurate with the classification level of the compromised material to prevent further unauthorized disclosure in accordance with DoDM5200.01 Volume 3, Enclosure 6. The contractor will contact the GCA for instructions on how to communicate the notification prior to submission in all cases where lost or compromised information is beyond the jurisdiction of the U.S. Government and cannot be recovered.

8. The contractor shall ensure all notifications determined to contain classified information are properly transmitted and marked in accordance with derivative classification and overarching marking guidelines in accordance with 32 CFR Part 117.

(b) Initial Notification of Security Incident

1. The contractor shall provide an initial notification of security incident to the GCA within 72 hours of discovery of any incident where classified information may have been subjected to loss, compromise, or suspected compromise for all security incidents involving the contractor’s location unless otherwise directed by contract requirements.

2. The initial notification to the GCA is considered Controlled Unclassified Information (CUI) [CUI category OPSEC, FEDCON Distribution/Dissemination Control] unless otherwise determined by the GCA, marked in accordance with DoDI5200.48, and shall be transmitted to the GCA through authorized means (e.g., encrypted email or DoD

SAFE).

3. If the initial notification contains classified information either by content or through classification through compilation, the contractor will contact the GCA for submission guidance and ensure the notification is properly marked in accordance with derivative classification and overarching marking guidelines in accordance with 32 CFR Part 117.

4. The initial notification shall contain the following information, as available at the time of report:

i. Prime contract number associated with the security incident.

ii. Date of security incident occurrence.

iii. Date of security incident discovery if different from date of occurrence.

iv. Security Classification Guide (SCG) or guidance used to validate classification level of information involved (unclassified title/date); if SCG title is either classified or if listing SCG information will cause the notification to be classified by compilation, do not include and indicate as such in the initial notification.

v. Classification level of information involved (e.g., Top Secret, Secret, or Confidential)

vi. Brief description of incident prompting initial notification. If incident directly or indirectly involved government personnel, include government personnel name(s), email address(s), and office information.

vii. Communicate whether it is possible for the contractor to properly retain and/or provide the suspected information in question for GCA classification review and/or damage assessment.

(c) Final Notification of Security Incident

a. The contractor shall provide a final notification to the GCA 10 business days from date of initial notification. If the final notification cannot be made 10 business days from the date of the initial notification, the contractor shall request an extension and receive approval in writing from the GCA.

b. The final notification to the GCA does not relieve the contractor from reporting requirements set forth by 32 CFR Part 117, DFARS 252.204-7012, or as otherwise directed by contract requirements and/or its Cognizant Security Office (e.g., Defense Counterintelligence and Security Agency).

c. The final notification will be considered CUI [CUI category OPSEC, FEDCON Distribution/Dissemination Control] unless otherwise determined by the GCA, marked in accordance with DoDI5200.48, and sent through authorized means (e.g., encrypted email or DoD SAFE).

d. If the final notification contains classified information either by content or through classification through compilation, the contractor is required to contact the GCA for submission guidance and ensure the notification is properly marked in accordance with derivative classification and overarching marking guidelines in accordance with 32 CFR Part 117.

e. The final notification shall contain the following information:

i. Prime contract number associated with the security incident.

ii. Date of security incident occurrence.

iii. Date of security incident discovery if different from date of occurrence.

iv. Security Classification Guide (SCG) or guidance used to validate classification level of information involved (unclassified title/date); if SCG title is either classified or if listing SCG information will cause the report to be classified by compilation, do not include this information, and indicate as such in the final notification.

v. Classification level of information involved (e.g., Top Secret, Secret, or Confidential)

vi. Detailed description of incident and include the following:

• Sequence of events: When, where, and how did the incident occur?

• What persons, situations, and/or conditions caused or contributed to the incident?

• If incident originated with government personnel, include government personnel name(s), email address(s), and office information.

• Include the name(s), email address(s), and office information of all government personnel involved, either directly or indirectly, as appropriate

• If classified information is alleged to have been physically lost (e.g., lost classified document), what steps were taken to locate the material?

• If security incident was categorized as a data spill, include measures taken to properly sanitize all impacted assets.

vii. Corrective actions taken to prevent future occurrences

viii. Result of inquiry (e.g., loss, compromise, suspected compromise, or no compromise)

ix. A copy of the supporting DD Form 254(s) associated with prime contract. If DD Form 254 cannot be provided, the contractor shall indicate the reasons why in the final report.

(d) Definitions “32 CFR Part 117” means National Industrial Security Program Operating Manual. “Business days” means days that do not include federal holidays or weekends.

“Classified information” means information the government designates as requiring protection against unauthorized disclosure in the interest of national security, pursuant to E.O. 13526, Classified National Security Information, or any predecessor order, and the Atomic Energy Act of 1954, as amended. Classified information includes national security information (NSI), restricted data (RD), and formerly restricted data (FRD), regardless of its physical form or characteristics (including tangible items other than documents).

“Cognizant security agencies (CSAs)” means agencies E.O. 12829, sec. 202, designates as having National Industrial Security Program implementation and security responsibilities for its own agencies (including component agencies) and any entities and non-CSA agencies under their cognizance. The CSAs are: Department of Defense (DoD); Department of Energy (DOE); Nuclear Regulatory Commission (NRC); Office of the Director of National Intelligence (ODNI); and Department of Homeland Security (DHS).

“Cognizant Security Office” means an organizational unit to which the head of a CSA delegates authority to administer industrial security services on behalf of the CSA.

“Compromise” means an unauthorized disclosure of classified information.

“Data spill” means electronic transmission of classified information via unsecure means such as classified information transmitted over an unclassified network.

“DD Form 254” means the Department of Defense Contract Security Classification Specification.

“Derivative classification” means incorporating, paraphrasing, restating, or generating in new form information that is already classified, and marking the newly developed material consistent with the classification markings that apply to the source information.

Includes the classification of information based on classification guidance. The duplication or reproduction of existing classified information is not derivative classification.

“Final Notification of Security Incident” means contractor (or subcontractor) notification to the Government Contracting Activity communicating the results of the inquiry conducted.

“Government Contracting Activity” means an element of a Component designated and delegated by the Component head or designee with broad authority regarding acquisition functions to include the appropriate resources and personnel (e.g., contracting officers or their designees, program managers, program offices, and security personnel) as defined in DoDM 5220.32, Volume 1.

“Initial Notification of Security Incident” means the contractor’s (or subcontractor) notification to the Government Contracting Activity of a security incident occurrence and surrounding details of occurrence.

“Inquiry” means the initial fact-finding and analysis process to determine the facts of any security incident and conducted to determine whether or not there was a loss of classified information or whether or not unauthorized personnel had, or could have had, access to the information.

“Loss” means the inability to physically locate or account for classified information.

“Security classification guide” means a documentary form of classification guidance issued by an Original Classification Authority that identifies the elements of information regarding a specific subject that must be classified and establishes the level and duration of classification for each such element.

“Security Incident” means an incident that results from the mishandling of classified information.

“Suspected Compromise” means when a result of no loss or compromise of classified information cannot be determined with certainty.

ELIMINATION OF USE OF CLASS I OZONE DEPLETING

SUBSTANCES (ODS)

a. Contractors shall not:

1. Provide any service or product with any specification, standard, drawing, or other document that requires the use of a Class I ODS in the test, operation, or maintenance of any system, subsystem, item, component, or process; or

2. Provide any specification, standard, drawing, or other document that establishes a test, operation, or maintenance requirement that can only be met by use of a Class I ODS as part of this contract/order.

b. For the purposes of Department of the Air Force policy, the following products that are pure (i.e., they meet the relevant product specification identified in AFI 32-7086) are Class I ODSs:

1. Halons: 1011, 1202, 1211, 1301, and 2402;

2. Chlorofluorocarbons (CFCs): CFC-11, CFC-12, CFC-13, CFC-111, CFC-112, CFC-113, CFC-114, CFC-115, CFC-

211, CFC-212, CFC- 213, CFC-214, CFC-215, CFC-216,

and CFC-217, and the blends R-500, R-501, R-502, and R- 503; and

3. Carbon Tetrachloride, Methyl Chloroform, and Methyl Bromide.

HEALTH AND SAFETY ON GOVERNMENT

INSTALLATIONS

In performing work under this contract on a Government installation, the contractor shall:

1. Take all reasonable steps and precautions to prevent accidents and preserve the health and safety of contractor and Government personnel performing or in any way coming in contact with the performance of this contract; and

a. Take such additional immediate precautions as the contracting officer may reasonably require for health and safety purposes

2. The contracting officer may, by written order, direct Department of the Air Force Occupational Safety and Health (AFOSH) Standards and/or health/safety standards as may be required in the performance of this contract and any adjustments resulting from such direction will be in accordance with the Changes clause of this contract.

3. Any violation of these health and safety rules and requirements, unless promptly corrected as directed by the contracting officer, shall be grounds for termination of this contract in accordance with the Default clause of this contract.

CONTRACTOR ACCESS TO DEPARTMENT OF THE AIR

FORCE INSTALLATIONS

a. The contractor shall obtain base identification and vehicle passes, if required, for all contractor personnel who make frequent visits to or perform work on the Department of the Air Force installation(s) cited in the contract. Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished, contractor identification badges while visiting or performing work on the installation.

b. The contractor shall submit a written request on company letterhead to the contracting officer listing the following:

contract number, location of work site, start and stop dates, and names of employees and subcontractor employees needing access to the base. The letter will also specify the individual(s) authorized to sign for a request for base identification credentials or vehicle passes. The contracting officer will endorse the request and forward it to the issuing base pass and registration office or Security Forces for processing. When reporting to the registration office, the authorized contractor individual(s) should provide a valid driver’s license, current vehicle registration, valid vehicle insurance certificate, and any additional requirements to comply with local security procedures to obtain a vehicle pass.

c. During performance of the contract, the contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials and vehicle passes for any employee who no longer requires access to the work site.

d. When work under this contract requires unescorted entry to controlled or restricted areas, the contractor shall comply with DAFI 31-101, Integrated Defense and DODMAN5200.02_DAFMAN 16-1405 , Air Force Personnel Security Program citing the appropriate paragraphs as applicable.

e. Upon completion or termination of the contract or expiration of the identification passes, the prime contractor shall ensure that all base identification passes issued to employees and subcontractor employees are returned to the issuing office.

f. The contractor shall provide an after-hours contact number or after-hours email in the Emergency Mass Notification System (EMNS) for each of their personnel, whose normal place of duty is on a DoD installation or within a DoD facility. The contractor shall comply with any additional requirements in DAFMAN 10-206 for emergency operational reporting. Foreign Nationals may participate and may remove themselves from the Emergency Mass Notification System at any time. To update information, personnel can access the globe icon on their system desktop screens and choose the “Access Self-Service” option.

g. Failure to comply with these requirements may result in withholding of final payment.

COMMON ACCESS CARDS (CAC) FOR CONTRACTOR

PERSONNEL

a. For installation(s)/location(s) cited in the contract, contractors shall ensure Common Access Cards (CACs) are obtained by all contract or subcontract personnel who meet one or both of the following criteria:

1. Require logical access to Department of Defense computer networks and systems in either:

i. the unclassified environment; or

ii. the classified environment where authorized by governing security directives.

2. Perform work, which requires the use of a CAC for installation entry control or physical access to facilities and buildings.

b. Contractors and their personnel shall use the following procedures to obtain CACs:

1. Contractors shall provide a listing of personnel who require a CAC to the contracting officer. The government will provide the contractor instruction on how to complete the Contractor Verification System (CVS) application and then notify the contractor when approved.

2. Contractor personnel shall obtain a CAC from the nearest Real Time Automated Personnel Identification Documentation System (RAPIDS) Issuing Facility (typically the local Military Personnel Flight (MPF)).

c. While visiting or performing work on installation(s)/location(s), contractor personnel shall wear or prominently display the CAC as required by the governing local policy.

d. During the performance period of the contract, the contractor shall:

1. Within 7 working days of any changes to the listing of the contract personnel authorized a CAC, provide an updated listing to the contracting officer who will provide the updated listing to the authorizing government official;

2. Return CACs in accordance with local policy/directives within 7 working days of a change in status for contractor personnel who no longer require logical or physical access;

3. Return CACs in accordance with local policy/directives within 7 working days following a CACs expiration date; and

4. Report lost or stolen CACs in accordance with local policy/directives.

e. Within 7 working days following completion/termination of the contract, the contractor shall return all CACs issued to their personnel to the issuing office or the location specified by local policy/directives.

f. Failure to comply with these requirements may result in withholding of final payment.

IV. Submission Instructions

Draft RFP All draft RFP comments shall be sent via email to the Government points of contact identified below in a Comment Resolution Matrix (CRM). Please use the Proprietary CRM for any comments that are proprietary in nature. Any responses submitted through different channels or to a different email address will not be considered.

RFI

All RFI responses shall be sent via email to the Government points of contact identified below in a PDF or Microsoft Word file. Responses to this notice shall include Vendor's Company Name, Address, and Point of Contact Information including name, position, telephone number, and email address. There is no page limit to your RFI submittal, but no more than 25 pages would be an appropriate level of response for the RFI (exclusive of lists of tables, figures, acronyms, etc.) and should use a minimum of 12-point font, single line spacing and 1-inch margins. When submitting an RFI response, please use the subject NSSL EPPM RFI [-Vendor Name]".

All responses to this RFI and draft RFP are requested no later than 1500 Pacific Standard Time on 6 August 2026. Responses received after this time might not be considered in the Government’s analyses.

The Government may subsequently contact respondents for clarification on the information submitted.

POINTS OF CONTACT:

Primary: Secondary:

Isabel Shvartsman Capt Logan Guenthardt Contracting Officer Contracts Specialist isabel.shvartsman@spaceforce.mil logan.guenthardt.1@spaceforce.mil

V. Response Classification

All material provided in response to this RFI shall be submitted in Microsoft Excel, Microsoft Word, or Adobe format and shall be kept UNCLASSIFIED, non-confidential, and non-proprietary to the maximum extent possible. If proprietary information is submitted, it must be appropriately and specifically marked.

It is the submitter's responsibility to clearly define to the Government what is considered confidential/proprietary data. Firms providing confidential/proprietary information shall be separately and clearly identified and mark all confidential/proprietary information with appropriate labels (i.e.

“Proprietary”). The Government will take all necessary steps to protect/safeguard any confidential/proprietary information provided. The Government will NOT be held responsible for any proprietary information that is not clearly marked.

VI. Small Business Consideration

The North American Industry Classification System (NAICS) code and size standard are 336414 and 1,300 employees, respectively. Response from small business is encouraged. Questions relating to small business should be addressed to the Office of Small Business Programs at smallbus@spaceforce.mil.

VII. Disclaimer mailto:isabel.shvartsman@spaceforce.mil mailto:logan.guenthardt.1@spaceforce.mil mailto:smallbus@spaceforce.mil

THIS IS A DRAFT RFP RELEASE AND REQUEST FOR INFORMATION ONLY. This is a draft RFP/RFI issued solely for information and planning purposes; it does not constitute a Request for Proposal (RFP), Request for Quotation (RFQ), or a promise to issue a solicitation in the futures. In accordance with RFO 15.101(c), responses to this draft RFP/RFI are not offers and cannot be accepted by the Government to form a binding contract. The notice does not commit the Government to contract for any supply or service whatsoever. Furthermore, the Government is not seeking proposals at this time. Furthermore, the Government will NOT pay for any information or administrative costs incurred in response to this notice.

All costs associated with responding to this notice will be solely at the responding party’s expense. Space Access will acknowledge receipt of all submissions but is under no obligation to provide feedback.

Responses will be treated as information only and not as a proposal.

Submissions may be reviewed by Government personnel and support contractors bound by appropriate non-disclosure agreements. Intellectual or other privileged or proprietary information contained in responses to this RFI will not be distributed outside of the Department of Defense or United States Government employees from other Government agencies who are working with Space Access on this RFI. SYD 80 has entered into contracts with: The Aerospace Corporation; Alpha Omega Group LLC;

Axient LLC; Boecore, Inc.; Figueroa & Associates, LLC; Integrated Data Services, LLC; Liona Enterprises Inc; ManTech International Corporation; Nynth Company California LLC; OMNI Consulting Solutions LLC; Quantum Space LLC; SAVI, LLC; Stellar Solutions; Tecolote Research, Inc.; and Wallender & Associates. These companies support the program office by performing technical reviews, systems engineering and integration analyses, cost estimation, and other advisory services. Participation in the one-on-one discussions constitutes consent to disclosure of information to these companies, which are required to provide equal protection to non-public information as the Government.