Sources Sought for PEREGRINE Sentry.pdf

SOURCES SOUGHT ANNOUNCEMENT

The Space Development Agency (SDA) seeks sources for the Performance Enhanced Real-time

Ground Environment (PEREGRINE) Sentry effort.

CONTRACTING OFFICE ADDRESS: Space Development Agency

1670 Air Force Pentagon

Washington, DC 20330

INTRODUCTION:

THIS IS A SOURCES SOUGHT ANNOUNCEMENT to identify potential sources that can provide PEREGRINE Sentry capabilities. PEREGRINE Sentry will support the SDA resilient missile warning and tracking (RMWT) low Earth orbit (LEO) operational mission within the

PWSA Ground Program. The government intends to evolve the current PWSA ground segment into a loosely-coupled Modular Open Systems Architecture (MOSA)-compliant ground segment framework (GSF) and a secure, multi-tenant common development environment (CDE).

The potential contractor will serve as the lead platform integrator responsible for ingesting new and existing third-party application developer (3PAD) capabilities, working with ground segment contractors, and managing the software ecosystem framework lifecycle on the GSF. The contractor will work in collaboration with mission partners and under the governance of the government’s enterprise system’s engineering and integration team, establishing the technical baseline using model-based systems engineering (MBSE) as the authoritative source of truth

(ASOT), and executing a low-risk legacy capability transition under a strict “do no harm” paradigm.

SDA seeks sources with demonstrated technical capabilities in the core areas outlined below, with a specific preference for respondents with demonstrated, production-proven experience architecting and operationalizing systems for distributed space or ground environments that can serve as the foundation for the PEREGRINE Sentry ecosystem:

• Hybrid Cloud Infrastructure & Edge Compute: Designing, provisioning, and managing resilient platforms spanning native Commercial Cloud Enterprise (C2E) resources and on-premises physical footprints. This includes physical hardware provisioning, network transport design, and Contractor-Furnished Equipment (CFE) edge compute configuration at Operations Centers to ensure continuous data synchronization and

Continuity of Operations (COOP).

• Modern Software & Modular Open System Architecture (MOSA): Architecting loosely-coupled microservices architectures.

• Common Development Environment (CDE) & DevSecOps Automation: Developing and operating scalable CDEs/Software Factories with automated CI/CD pipelines. This includes aggressive use of Infrastructure and Configuration as Code (IaC/CaC), "Golden

Path" pipeline deployments, and C2E resource optimization utilizing Well-Architected

Frameworks (WAF) and FinOps cost controls.

• Multi-Level Security (MLS), Cross-Domain & cATO: Implementing Zero Trust architectures, NSA-approved Cross-Domain Solutions (CUI to SECRET), and automated compliance telemetry to support a Continuous Authorization to Operate (cATO). This includes establishing an MLS foundation capable of secure network connectivity and data sharing with external partners (including Coalition and FVEY) across varying trust domains.

• Enterprise Data Architecture & MLOps: Building scalable Data Lakehouses, data-centric architectures, and automated MLOps pipelines ready to support Artificial

Intelligence/Machine Learning (AI/ML) lifecycle management across the enterprise.

• Third-Party Application Developer (3PAD) Ecosystem & Simulation: Operating multi-tenant developer portals, self-service tools, SDKs, and comprehensive governance models to rapidly onboard 3PADs. This includes the provisioning and upkeep of a High-

Fidelity Simulation and Telemetry/Mission Data Emulation Environment to validate third-party integration prior to operational release.

• Digital Engineering (MBSE) & Agile Systems Management: Utilizing Model-Based

Systems Engineering (MBSE) and Digital Engineering as the Authoritative Source of

Truth (ASOT) for all requirements and architectures. Executing Agile program management to include collaborative PI Roadmaps, strict automated "Definitions of

Done," and continuous integration with existing Government Configuration Management

(CM) tools.

• Enterprise Integration, Transition, & Sustainment: Executing phased, parallel operations to migrate highly complex legacy ground applications under a strict "Do No Harm" paradigm. This includes cross-agency interoperability, continuous operational user value assessment, and full-lifecycle Operations, Maintenance, and Sustainment (O&M), encompassing Tier 1/2/3 ITSM service desk support

In accordance with FAR Part 10, Market Research, the Space Development Agency seeks information on potential sources for the PEREGRINE Sentry effort.

The Government anticipates awarding an 18-month firm-fixed-priced (FFP) Other Transaction

Agreement (OTA) prototype contract followed by a subsequent FFP OTA production contract with a three (3) year base period of performance from the effective date of award, and two (2), three (3)-year option periods.

Security Requirements. The potential Performer must have the ability to obtain and maintain active Secret and TS/SCI clearances for the duration of the contract period beginning at contract award. Sufficient staff must be cleared at the Secret and TS/SCI levels at contract start to successfully execute the contract. This includes facility clearance sufficient to receive (i.e., JWICs enabled network access), process, and store Secret and Top Secret material at the intended Prime Contractor’s facility.

Anticipated CLIN Structure: The Government is contemplating the use of an OTA with firm-fixed-price, payable milestones. Industry feedback on industry standard contract type is desirable.

1.1 SOURCES SOUGHT INFORMATION:

1.2 DISCLAIMER: THIS SOURCES SOUGHT IS FOR INFORMATIONAL PURPOSES

ONLY. THIS IS NOT A REQUEST FOR PROPOSAL (RFP), REQUEST FOR QUOTE (RFQ)

OR AN INVITATION FOR BID (IFB). IN ACCORDANCE WITH FAR 15.201(e), THIS NOTICE DOES NOT CONSTITUTE A SOLICITATION AND SHALL NOT BE

CONSTRUED AS A COMMITMENT BY THE GOVERNMENT. RESPONSES IN ANY

FORM ARE NOT OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION TO

AWARD A CONTRACT AS A RESULT OF THIS ANNOUNCEMENT.NO FUNDS ARE

AVAILABLE TO PAY FOR PREPARATION OF RESPONSES TO THIS

ANNOUNCEMENT. ANY INFORMATION SUBMITTED BY RESPONDENTS TO THIS

TECHNICAL DESCRIPTION IS STRICTLY VOLUNTARY. THE GOVERNMENT MAY

USE THE INFORMATION OBTAINED FROM RESPONSES TO THIS NOTICE IN

DETERMINING ITS ACQUISITION APPROACH. THE ISSUANCE OF THIS NOTICE

DOES NOT RESTRICT THE GOVERNMENT ACQUISTION APPROACH.

1.3 REQUIRED CAPABILITIES: Interested firms should submit information as to the capabilities, capacity, and experience to perform the requirements described in the core areas above.

The technical capabilities statement should describe relevant contract experience offered to

Government and commercial customers, include a reference to the contract number, magnitude, place of performance and points of contact for each example provided (i.e., name, POC, mailing address, email, telephone number, the company’s web page (if applicable)). Submitted information shall be UNCLASSIFIED.

1.4 NORTH AMERICAN INDUSTRY CLASSIFICATION SYSTEM CODE. (NAICS):

The anticipated NAICS Code is 541715 – Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology); the corresponding

Small Business size standard is 1,000 employees . Respondents may comment or suggest an alternative NAICS Code that they consider better suited to the effort for consideration.

1.6 SUBMISSION DETAILS: Vendors interested in responding to this announcement should submit unclassified technical capabilities statement via email NLT, 23 October 2026, 1700 ET, to the Contract Specialist and Contracting Officer at ussf.pentagon.sda.mbx.sn-26- 0016@mail.mil. NO PHONE CALLS OR FAXES WILL BE ACCEPTED. CLASSIFIED information will NOT be accepted. The Government will not award a contract solely based on this Sources Sought, nor will it reimburse the contractor for any costs associated with preparing mailto:ussf.pentagon.sda.mbx.sn-26-0016@mail.mil mailto:ussf.pentagon.sda.mbx.sn-26-0016@mail.mil or submitting a response to this notice. Responses shall be limited to six (6) pages. Font in normal text shall be no smaller than Times New Roman 12pt. Font in tables and figures shall be no smaller than Times New Roman 10pt.

Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned. It is the submitter’s sole responsibility to verify the e-file was received and can be viewed.

All information received that is marked Proprietary will be handled accordingly. All

Government and contractor personnel reviewing sources sought responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described in 41 USC 423. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified.

1.7 RESPONSES SHALL INCLUDE:

a) Business name and address;

b) Name of company representative and their business title;

c) Business Size and Type of Small Business (if applicable);

d) Cage Code;

e) DUNS Number;

f) Technical Capabilities statement package (no more than six (6) pages) demonstrating standard methodologies and organizational capability to perform in accordance with the Core Areas, paragraphs 1.3 and 1.4 above.

g) Statement regarding whether, as a prime contractor, you can maintain an active Top Secret clearance for the anticipated duration of the contract period, and as a prime contractor, can you maintain a Top Secret FCL for the anticipated duration of the contract to receive (i.e., through JWICS), process and store classified material at your facility;

h) Information regarding teaming arrangements or information regarding your plans to use a joint venture. Any response involving teaming arrangements should delineate between the work that could be accomplished by the prime and the work that could be accomplished by the teaming partner(s);

i) An appendix of no more than five (5) pages, providing a description of similar services offered to the Government or to commercial customers within the past three years, and provide an assessment on if this effort can be accomplished commercially;

j) Industry standard contract line-item number (CLIN) arrangements best suited for these services;

k) Notional contract type/s best suited for these services based on industry standards

l) Other suggestions to ensure this contract requirement and contents are best suited for these service;.

m) Any major performance, schedule, or cost risk anticipated at this time.

1.8 QUESTIONS: Questions regarding this announcement shall be submitted in writing by email to the Contracting POCs stated in Para 1.6 above. Questions are to be submitted NLT

06 October 2026, 1700 ET. Verbal, phone or fax questions will NOT be accepted. Answers to questions will be posted on SAM.gov website. Questions shall NOT contain proprietary or classified information.

1.9 INDUSTRY DAY: The Government is considering hosting an Industry Day to provide additional context on the PEREGRINE Sentry operational concepts and foster transparent communication with potential industry partners. Details regarding the date, time, format (virtual or in-person), and registration instructions will be provided in a forthcoming amendment to this

Sources Sought announcement or a separate SAM.gov posting.

1.10 Consideration of Potential Organizational Conflict of Interest (OCI): The Government is evaluating a potential Organizational Conflict of Interest (OCI) related to the PEREGRINE

Sentry prime contractor role. To ensure objectivity and a fair competitive environment, the

Government is contemplating an approach where the prime contractor may be precluded from developing or holding contracts for mission applications that would be integrated into the

PEREGRINE Sentry ecosystem. Respondents should consider this restriction when evaluating their interest in this effort.