Skip to content
Fiscal Receipts

Service-Wide Support (Not Otherwise Accounted For)

Air ForceRDT&EReconciledPE1201212SF
What it is
Service-Wide Support (Not Otherwise Accounted For) (1201212SF) is an Air Force research & development line funded in the Research, Development, Test, and Evaluation, Space Force account. Its J-book detail breaks the line into 1 project.
What changed
No FY25→26 comparison — endpoints unavailable or on different bases.
Who gets it
No company is linked to this line. Award records do not carry the program element, so the crosswalk is silent here — why.

Budget figures

FY24 Actuals
$0J-book detail · PB2026
FY25 Enacted
$0J-book detail · PB2026
FY26 Request
$18.5MR-1 TOA · PB2026
FY25→26 Change
No comparison: endpoints unavailable or on different bases
Data coverage

FY2026 award data is a partial year — USAspending reports awards on a rolling basis, and this corpus runs through 2026-09-04. why partial FY2026 data? →

Budget trajectory

The program's 3 summary figures for FY24 to FY26, plotted in fiscal-year order: this line ends higher than it starts. The points are the summary cards above, not a separate derivation; the table beside the chart carries each figure with its own citation.
The program's 3 summary figures for FY24 to FY26, plotted in fiscal-year order: this line ends higher than it starts. The points are the summary cards above, not a separate derivation; the table beside the chart carries each figure with its own citation.FY24: $0FY25: $0FY26: $18.5MFY24FY25FY26
Budget trajectory: one row per fiscal year, carrying the summary figure the sparkline plots. Every figure opens its own citation.
Fiscal yearAmount
FY24$0J-book detail · PB2026
FY25$0J-book detail · PB2026
FY26$18.5MR-1 TOA · PB2026

Decade view

P-1/R-1 workbook TOA basis, shown compact in $B/$M (the workbook records USD thousands); each figure cites its own President's Budget edition

One fiscal year of this program as published: a line through the actuals (filled dots), with the enacted (hollow circles) and request (diamonds) markers each edition reported. Read it for direction, not for precision — this program's actuals line is too short to show a direction. The grid below is the same data as text, one cited figure per cell.
One fiscal year of this program as published: a line through the actuals (filled dots), with the enacted (hollow circles) and request (diamonds) markers each edition reported. Read it for direction, not for precision — this program's actuals line is too short to show a direction. The grid below is the same data as text, one cited figure per cell.FY2026 request — PB2026 editionFY26

● actuals (line)  ·  ○ enacted  ·  ◇ request — gaps are editions the program is absent from, never interpolated.

Decade series values by fiscal year and President's Budget edition: one row per series (actuals, enacted, request), one column per fiscal year. Every figure opens its own citation.
SeriesFY26
Request$18.5M

blank = series not published for this year; – = absent from that edition.

Program lineage

No predecessor/successor lineage was recorded for this program element — no FY-to-FY transfer into or out of this line was stated in the ingested J-books, and none was inferred from the program structure.

Description

Mission — Datalake & UI/UX Development

"This is a new start and critical initiative activity to implement Personnel Management Act (PMA) Human Resource (HR) Information Technology (IT) Automation and develop a data layer within the existing Air Force Human Resources structure that can be utilized to meet current and future Space Force needs. In December 2023 the 2024 National Defense Authorization Act established the Space Force Personnel Management Act, a five-year term for USSF to define and implement policy, process, and system actions for a single component USSF that defines all Guardians in one of two statuses: fulltime or parttime. The CSO has directed SF/S1, with the support of SAF/SQ, to undertake the task of researching various pathways and start early development and testing of an optimized platform for use by Guardians across the service. To meet the constrained timeline, SF/S1 has developed a novel solution utilizing existing AF/A1 structures to establish a flexible data layer using an agile approach to limit development cost and allow for a customizable modular solution. In the near term the CSO has expressed concern over the loss of critical human capital as members depart military service in favor of the private sector, with no ability to retain talent within a reserve component. As a solution, the CSO has directed the required mechanisms (policy, procedures, technology) be developed and put in place by 2026 to demonstrate ability to retain guardians in a part time posture with the option to return to full time status at a later date. To meet the intent of this directive, the SF/S1 has built a pilot program to be able to demonstrate a viable solution by overhauling the current Air Force HR data infrastructure to better automate and streamline the critical pathways and deliver the functionality needed to process Reservist into a component less part-time status by Jan 2026. In the out years, additional functionality will be delivered to the system in incremental sprints to solve the problem in an efficient solution space. Agile sprints allow for better accounting for cost schedule and performance metric tracking delivering a critical HR too to the force as quickly as possible. " This program is in Budget Activity 7, Operational System Development because this budget activity includes development efforts to upgrade systems that have been fielded or have received approval for full rate production and anticipate production funding in the current or subsequent fiscal year.

Justification

Accomplishments & Planned Programs (1)

Datalake and UI/UX Development

Develop and prototype Datalake and UI/UX systems including studies, analyses, risk reduction, and technology maturation of human capital management sytems.

Budget line items(workbook-cited)

P-1/R-1 workbook Total Obligation Authority basis (USD thousands) · PB2026.

Exhibit R-1

AccountOrgTypeAmount
Research, Development, Test, and Evaluation, Space ForceFFY26 Disc. Request$18.5M
Research, Development, Test, and Evaluation, Space ForceFFY26 Total$18.5M

Budget Details(R-2/P-40 facts)

J-book detail basis (R-2/P-40, USD millions) · PB2026 — a different accounting basis from the P-1/R-1 workbook TOA above; where the two disagree, the reconciliation strip under Budget figures shows both.

Wider than this screen — swipe the table sideways for the remaining fiscal-year columns.

ProjectAll Prior YearsFY24 ActualsFY25 TotalFY26 BaseFY26 Request
Program Element$0$0$0$18.5M$18.5M
670220: Datalake & UI/UX Development$0$0$0$18.5M$18.5M

Follow the dollar

No follow-the-dollar view — this program's awards haven't been crosswalked at high confidence (flows cover 312 of 1,938 programs). why coverage is partial? →

Awards

No awards are linked to this program element at high or medium confidence — the budget→award crosswalk only asserts links it can defend, and this line has none yet.

Lobbying mentions

No Senate LDA lobbying filing in the tracked data mentions this program element by code or alias.

Oversight

Department-level designation (not specific to this program)

GAO lists 5 high-risk areas for DOD as a whole. That designation covers the department, not Service-Wide Support (Not Otherwise Accounted For). No program-specific GAO finding for this line is in the ingested data. See the DOD oversight record.

Program dossier

No research dossier for this program — dossiers cover 50 of 1,938 programs, the largest fully J-book-detailed lines by FY2026 requested dollars. why no dossier here? →

Primary sources

Open any budget figure for its exact receipt. Verified line items lead with the highlighted government PDF; original spreadsheets download with their budget edition and exhibit in the filename.

Budget totals · TOA sources

Detailed budget justification

The related TOA spreadsheets above use a different accounting basis from R-2/P-40 detail. Their amounts are not assumed to match these detailed sources.