How Vela works
Vela reads the systems you already run, holds one live model of the work, and traces every change to the people and dates it touches.
The operating loop
What Vela does, in the order it does it.
- 01
Connect the project
Vela reads the mail, drawings, schedules, and registers your teams already use. Nothing moves to a new system, and you set the scope before anything connects.
- Nothing migrated, nothing re-entered
- Four systems read today; the directory carries live status
- Reads are scoped and granted per workspace
The connector directory carries every system and its real status: four read today, the rest ship in the order teams ask.
- 02
Build the live project model
What it reads becomes the actual structure of the project: equipment, milestones, vendors, documents, decisions, risks, and owners, all linked.
- Records linked the way the work is linked
- Every value keeps a way back to its source
- Owners are part of the model, not a mailing list
- 03
Trace what changed
When a drawing, supplier position, or register moves, Vela names the fields that changed and follows them through every date, cost, and team downstream.
- Field-level diffs, not a folder of new files
- Contradictions get flagged, never silently overwritten
- Derived numbers show their arithmetic
- 04
Coordinate the response
What needs attention reaches the people responsible, with the updates and decisions already prepared. Reads are automatic. Writes wait for a person.
- Everyone it lands on sees it the same morning
- Drafts arrive filled in, with their sources
- Consequential actions stop at a named owner
One concrete example
One change, traced across the entire project.
A supplier moves a transformer delivery four weeks. Same numbers as every other page of this site.
- 01
Detected
The revised factory slot lands on the supplier thread.
Ready to ship→ 26 OctOn site→ 23 Nov - 02
Linked
The transformer is tied to everything that depends on it.
Rev 7 need-by6 NovMilestones behind itFour - 03
Assessed
Float goes 17 days late, and the stale register is caught.
Register row 12FlaggedFloat17 days late - 04
Prepared
The edit, the chase, and the slot decision go to their owners.
Register editStagedDecisionBy 21 Aug
What comes out the other side
- Energization milestoneAt risk
- Install sequenceExposed
- Register editStaged
- Supplier confirmationDrafted
- Slot-hold decisionFramed, priced
- Procurement and delivery leadsSame morning
Nothing here has been sent or written. Everything stops at the person who owns it.
Desert Ridge Storage, Northstar Energy, and everyone in this example are invented. The arithmetic is consistent so you can check it.
One model, many views
One project state. Different views for every team.
The model stays the same; each person sees what their role needs. One shared operating layer, not another inbox.
Executives
Portfolio risk, critical decisions, and where intervention is needed.
Project teams
Milestones, dependencies, owners, and the current state of the work.
Engineering and procurement
Drawing changes, equipment status, vendor commitments, downstream impacts.
External partners
A controlled view scoped to their work, without an account on everything.
How Vela acts safely
Vela moves the work without taking the controls.
Read
Vela reads the sources you approve, in the scopes you set. Reading changes nothing in your systems.
AutomaticPrepare
It drafts the edits, replies, and decisions: filled in, and traceable to their sources.
ReviewableApprove and commit
Anything that writes back or leaves the project stops at a named owner. They see the draft and its sources, then decide.
A person signs offThe result is a project that responds faster.
Changes get caught earlier. Risk is visible sooner. Decisions reach the right people before the project slips.