What the FY2027 request buys
Verbatim from the R-2A exhibit for project 643728 of PE 1206761SF. This is the budget justification's own description of work that has not happened yet — the one thing no other level of the budget carries.
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.
Increase due to intensive PTES development to support PTS-P integration starting in late FY26 and continuing through FY27.
FY2026: the year under way
Prior-year accomplishments and current-year plans from the same exhibit. Context for the FY2027 plan, not a series — an activity partitions its project exactly in the request year, but can under-cover it in earlier years.
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.
Three years, and no five-year plan
An R-2A activity publishes the prior year, the current year and the budget year. The FYDP outyears exist at project and program-element level and are deliberately absent here rather than inferred. Estimate types are colored and never summed into one figure.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 4.4 |
| FY2026 | Enacted | 10.2 |
| FY2027 | Request | 16.3 |
This activity is 5.4% of project 643728's FY2027 request and 3.6% of PE 1206761SF's. In the request year the activities under a project sum to it exactly; in the current year they under-cover it in about 9% of cases, so an activity's delta can legitimately exceed its parent's and the two must not be compared row to row.
8 activities in project 643728
Every R-2A line of this project, largest FY2027 request first. Linked where the activity has enough of its own narrative to carry a page; the rest are shown in full on the project page.