# PTS-P/R Ground Development

**R-2A activity** of project 643728 — Protected Tactical SATCOM  
**Program element:** 1206761SF — Protected Tactical Service (PTS)  
**Component:** U.S. Space Force · **Budget Activity:** 4  
**Vintage:** President's Budget PB2027  
**Canonical URL:** https://hitchintel.com/programs/1206761SF/643728/a4  
**Parent:** https://hitchintel.com/programs/1206761SF/643728

## Summary

This activity requests $16.3M in FY2027, 5.4% of project 643728, up 60% on FY2026. The R-2A exhibit describes it across FY2026–FY2027, including what the FY2027 money is planned to buy.

## What the FY2027 request buys

**FY2027 planned work.** Support the OODT of both PTS-P payloads that launch in FY26. Perform bulk of the development of PTES interface tools by the PTES prime contractor. As PTES interface tools mature, transition PTS-Prototypes from simulators and offline planning tool that enabled manual mission management during OODT activities. Initiate integration efforts for PTS-P and Enhanced PTS-P to leverage the PTES MMS & KMS capabilities to enable autonomous mission management using NSA certified cryptological keys. Plan testing activities to validate the successful PTS-P MMS transfer and integration onto the PTES baseline. Incorporate MMS & KMS changes found in PTES Integration and Test and review effectivity for Enhanced PTS-P ground development efforts.

**FY2026 to FY2027 change.** Increase due to intensive PTES development to support PTS-P integration starting in late FY26 and continuing through FY27.

## Before the request year

**FY2026 plans — current year.** Continue integration efforts for PTS-P and Enhanced PTS-P to leverage the PTES MMS & KMS simulators and the Aerospace Offline Planning Tool to support PTS-P payload and ground integration and test for PTS contractors. Finalize the functional requirements to the PTES MMS that will be modified to support mission planning and management for PTS-P (i.e., the requirements for the PTES MMS enterprise requirement document and scope of a potential offline planning tool for interim operational early use). Plan testing activities such as test scenarios, comm plans, and success criteria for the FY27 PTS-P on-orbit demonstration and test (OODT). Begin procurement of PTES interface tools from PTES prime contractor.

## Funding

| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 4.4 |
| FY2026 | Enacted | 10.2 |
| FY2027 | Request | 16.3 |

> Prior, current and budget year only — an R-2A activity carries no five-year plan. It sums exactly into its project in the request year and not necessarily in any other.

## Other activities in project 643728

- [Enhanced PTS-Prototype](https://hitchintel.com/programs/1206761SF/643728/a2) — FY2027 166.3
- [PTS Prototype Design and Development](https://hitchintel.com/programs/1206761SF/643728/a0) — FY2027 79.0
- PTS-P/R Space Hub End Cryptographic Unit (ECU) — FY2027 9.9
- Technical Baseline Management, System Integration and Test Support — FY2027 9.9
- PTS-P Gateway Development — FY2027 9.9
- Protected Tactical Testbed — FY2027 7.7
- PTS Resilient — FY2027 0.0

## Source & machine access

- **Source:** FY2027 Department of the Air Force RDT&E Budget Justification, Exhibit R-2A, PE 1206761SF project 643728 (PB PB2027). Narrative is the government's own text.
- **No marks, no contractors at this grain** — congressional marks land on the program element and R-3 performers on the project.
- **MCP:** `mcp.hitchintel.com` — `budget_get_activity`.

*HitchAI is an independent intelligence service, not affiliated with the U.S. Department of Defense. Budget figures are requests/estimates, not obligations.*