Sentinel reads your Primavera P6 schedules exactly, scores them against DCMA and GAO practice, computes earned value, drafts the variance narrative, and puts every project on one axis for the program review — inside your boundary, with no data egress, and without ever touching your database. Built by project managers who run DOE programs, for the project managers who run yours.
Every screen you see is the real Sentinel application running on synthetic demo data — no customer or site information — and the people shown are AI-generated.
The dashboard, schedule health, risk, earned value (EVMS), the assistant, the approval gate, the project report and the DOE Critical Decision gates — in the order a project manager uses them, with the engineers, project controls and the customer along the way.
Want to see it on your own schedule? Request a live demo →
Your schedulers already produce good analysis. What costs them is the assembly — DCMA checks from one spreadsheet, earned value from another, a narrative written by hand, into a report that is stale the day it issues. And the modern AI tools that could help are cloud-only, so the cleared world gets none of it.
Reads XER, PMXML, MSPDI and CSV; recomputes the critical path with Sentinel's own calendar-aware CPM; scores logic, float, constraints and leads/lags against GAO and DCMA practice — with sourced fixes.
Deterministic earned value — CV, SV, CPI, SPI, EAC by the standard methods, VAC, TCPI — rolled up by WBS and control account, with the TCPI-vs-CPI credibility check that flags an optimistic forecast before a reviewer does.
The report everyone hates writing — root cause, impact, corrective action, recovery date — drafted from the numbers by a local model, for a named person to edit, approve, or reject.
The period report generated straight from the data — including what changed since last period with a cause for every move — and sealed with an evidence package of everything it was made from. DOE and DoD report formats are on the roadmap.
Diff two schedules — baseline vs. current, version vs. version, a sub's fragnet vs. the master — and integrate the changes as proposals, each approved and logged.
Statused forecasts from the data date, Monte Carlo finish confidence (P50 / P80 / P90), a risk register with three-point cost impacts and a modelled contingency position, and what-if scenarios — none of it touching the schedule of record.
A program manager walks into the monthly review with one question per project: what needs attention first? Sentinel reads every schedule in the estate and answers it on one page — then the agenda the room actually walks: CPI and SPI, cumulative and this period; the variances; what changed in the schedule and the scope; what finished. Where projects share resources, money, or a handoff, it says so, with the coverage stated on every figure.

Forecast finish, slip, estate float and pushes, EVMS, data date, and one priority-ordered sentence per project — then, for each, the review block: CPI / SPI cumulative and for the period, control accounts in breach, schedule and scope changes applied through the gate, completions. Printable pack and workbook.

Declared links between projects, the driving chain in red, and every push one project puts on another. A program slip scenario shows what a late anchor does to the rest — and writes nothing. Dependencies nobody has acknowledged are filed as Start On or After proposals at the successor's gate, for a person to decide.

Same-named resources stacked across projects from the assignments, with activity-code concurrency as the fallback where a schedule is not resource-loaded. Declare a capacity and the months over it are marked; declare none and the page says the limit is unknown rather than pretending.

Plan against forecast by fiscal year, so a slip reads as the funding-profile change it is. EAC against budget ranked by project, with TCPI and the CPI-based EAC; the standing reserve set against the time-only cost of P80 schedule risk — before a single register risk is counted.
Program views run on the same engine as the project pages, over the schedules already registered — nothing is re-typed. The review block's period is the calendar month of the installation's status date, and its agenda follows the shape of a DOE monthly project review. Screens above are cropped from build v5.23 on the synthetic demo estate — eighteen connected schedules on one fictional site, which one click builds on your own machine.

One action assembles the period’s Project Report from what the engine has already computed: a cover that states the verdict and the six figures a manager reads first, performance at the data date, what changed since last period with a cause for every move, a variance record for every account outside a threshold, schedule and cost risk, and the signature block. PDF, Word or HTML — the view on screen, with its typefaces embedded so it prints the same on any machine.

Ask it what a project manager asks on an ordinary day — what to worry about, why it is late or over budget, any activity or control account by its ID, what changed since last period, a status note for your manager. It answers from the same engine as every page, in plain words, and offers the next step. Ask it to change something and it drafts the change for a person to decide.
One governed cycle sits behind every feature. It is what makes Sentinel trustworthy inside a controlled boundary — and what makes every change attributable to a named reviewer.
Read the schedule or cost export. Read-only — P6 is never opened, never written.
Deterministic engines do the math. The local model drafts the words.
A qualified controller approves, edits, or rejects each row. Nobody approves their own change.
Source, rationale, reviewer, and date on every decision — the review artifact is the change-control record.
A scoped file your scheduler imports through P6's own wizard. Never an auto-push.
The stop is a feature. Sentinel has no "apply to system of record" button. Everything it produces is a proposal at a gate — which is the moment that lands with anyone who has sat through an audit.
Build v5.23 · synthetic demo data · local model · no egress





ALL SCREENS · BUILD v5.23 · SYNTHETIC DEMO DATA · LOCAL MODEL · NO EGRESS
Sentinel runs entirely inside your controlled environment. The install is the product, and it never reaches out. If your site prohibits AI outright, run it with the model off — every calculation, page and deliverable works identically.
Trinity Sentinel is architected for accreditation; the customer's site owns the Authority to Operate. Certifications are pursued with sponsoring customers — we describe the posture accurately and never overstate it.
Buy it once and run it on your own server. A one-time licence, priced by the people who work in it — read-only viewers are always free — and a yearly upkeep that keeps the engine and the rules current. Every project carries a profile (Capital under DOE O 413.3C, Reportable EVM, Operations, Task order), so a task order never carries EVMS overhead and a capital project never goes without it. All four profiles come with every licence.
It converts every open question into an experiment instead of an argument, on your schedule rather than a demo dataset. Your site's software and security review happens inside the pilot's 60 to 90 days, not after it. The full fee is credited against a server licence bought within 12 months. Validation runs on the machine holding the schedule and reports only aggregate metrics — your data never leaves your site, even during evaluation.
Prices in USD, exclusive of taxes. Program Server and Site Server licences are priced in a written proposal, sized to the programs, sites and number of working users you need. Licences are one-time and include the first year of upkeep; from year two upkeep is 22% of the licence each year and brings every new build, ruleset updates as DOE orders, EIA-748 and DCMA thresholds change, a verification record with every build, support by email and phone, and one annual on-site or video health review. If upkeep lapses the software keeps running; it stops receiving updates. A working user is anyone who edits, proposes or approves; viewing is free. A per-seat subscription is available on request for buyers who must use operating funds. Founding sites — the first three production sites — receive 30% off their first server licence and a three-year price lock, in return for serving as a reference. Cleared or air-gapped installs, accreditation support and Sentinel-delivered services — Trinity runs the monthly assessment and delivers the report — are quoted after a scoping call. Sentinel assembles evidence for a contractor's EVMS self-certification; it never certifies a system or approves a Critical Decision.
The public documentation set, all at build v5.25 (19 October 2026), with the licence and notices. Every document is UNCLASSIFIED and built from synthetic demo data. Each one opens in a new tab in your browser's PDF viewer — save it from there.
Every document above is issued against the same build and reissued when the product changes.
Bring a P6 export. We'll show you the schedule-health score, the earned-value roll-up, and a drafted variance narrative — on your data, on a machine that never calls out.