Unified ingest from E, P, and C. Not another export hunt before every review.
03 / the gap
Programs run on fragments. Downstream work keeps the old basis.
When upstream state changes, downstream teams continue on the old basis until someone manually connects the dots. No system does this automatically.
Plathera replaces the manual synthesis step with a model agents and humans can both query.
symptom / propagation
| Upstream | Downstream | Until |
|---|---|---|
| design basis | procurement package · stale spec | manual review |
| permit condition | field work · old assumption | someone connects it |
| vendor delay | schedule · unchanged float | status meeting |
04 / program data
One relational model across the program.
Ingest from the systems of record you already run - normalize through APIs into one extensible graph. Context engineering on schemas, relationships, ownership, status, and evidence is what makes the assistant useful.
domains / ingested
design coordination
deliverables · permits
PO · invoices
RFIs · submittals
schedule · cost
mail · chat
ingest / E P C → program core
engineering
Folders · coordination · deliverables · actions · permits
procurement
PO flows · vendors · RFP · package status
construction
CA/field docs · RFIs · inspections · field actions
↓ APIs · schemas · relate ↓
program core
Relational model · typed links · context engineering
program hierarchy / links
program register / examples
| Type | Example | Status |
|---|---|---|
| package | Basebuild package · switchgear | released |
| permit | AHJ submittal · fire protection | in plancheck |
| deliverable | 90% design package · discipline set | received |
| action | Design review · structural basis | assigned |
visible infrastructure
Evidence only matters when it is shaped for review.
Knowledge exists in drawings, specs, emails, schedules, and spreadsheets. Not always in the shape the next decision requires.
Plathera compiles the project first: evidence, relationships, constraints, and trace before narrative.
05.1 / work surface
One interface to see and work the program.
Not another silo - the place owner-side teams interact with the unified model, from site to multi-site program.
navigation / example hierarchy
program · North Campus expansion
site · Site A
building · Battery hall 2
project · Electrical upgrade · B2-EU-04
capabilities / same data, two paths
- Scope by site, building, project, or program
- Roll up workload, cost, open actions, deliverables, permits
- Grids and filters - or ask EPC Assistant in natural language
05.2 / trust model
The record has to be defensible before the assistant is useful.
Plathera is designed around governed project evidence: connected sources, permissions-aware intake, typed relationships, audit trails, and human review before controlled outputs leave the system.
source
Connected systems stay the record of origin.Artifacts retain source, date, owner, and link context so a review can trace back to the system that produced the evidence.
permissions
Access follows the project boundary.Program data is only useful if scopes, roles, and review rights are preserved as the model relates records across tools.
review
Outputs remain human-approved.The assistant can assemble briefs, logs, and packets, but leaders keep judgment over decisions, commitments, and external communications.
06 / EPC Assistant
Ask the program to work. On demand.
A reason-and-act assistant over the unified model and connected sources - query, read, write, email, calendar, Teams. It works against structured project context instead of guessing from exports.
Assistant posture: source-aware · evidence-linked · human-reviewed
inbound email→EPC Assistant→triage · extract · log with evidence
program query→EPC Assistant→status or impact brief
vendor timesheet mail→EPC Assistant→hours logged · owner review
07 / roadmap
Integrator layer now. Proactive workflows next.
Plathera starts with the operating layer: ingest, project graph, work surface, and EPC Assistant. Proactive workflows follow when trigger logic, review controls, and task execution are mature enough to trust.
Per-tool features mature inside existing project systems. Plathera consumes the record they leave behind.
Documented capabilities expose artifacts, schedules, cost, correspondence, and workflow state.
Unified model, work surface, and EPC Assistant - Plathera today.
Trigger-aware briefs, impact maps, and task runs - forthcoming after controls mature.
Plathera today · operating layer → controlled workflows
Proactive workflows forthcoming
Depends on EPC Assistant task execution maturing, then trigger logic - hooks, events, schedules. When live: catch-up briefs, impact maps, decision logs, and report packages move from request-driven to controlled workflow.
workflows / designing toward
[01]Catch-up workflow
→ current after time away · evidence and unresolved items attached
[02]Impact workflow
→ cross-domain implication brief when upstream state changes
[03]Decision workflow
→ decisions tied to program objects, owner, date, and evidence
[04]Reporting workflow
→ field note or status package the leader edits, not drafts from scratch