Custom dashboards and workflow portals
Development and interconnection, engineering, procurement, and construction and commissioning do not want the same screen. Each one gets a portal built around the decisions it makes.
Everyone is looking at the same project and asking a different question.
The interconnection lead wants to know whether energization still holds. The owner's engineer wants to know which revision is current. Procurement wants to know whether the quote still stands. The superintendent wants to know what this stage needs captured before it closes. A dashboard that tries to answer all four ends up as noise to all four.
- One portal per discipline
- All four read the same model, so the numbers agree
- Describe a view in plain language and get it
- Outside firms get a view without getting an account
Procurement portal
ComposingAna's procurement portal, mid-build: milestones, approvals, and registers placed, risks on its way in. Each discipline composes the view it works out of — interconnection, engineering, and the field each get their own.
How a view gets built
Say what you want on it.
A view is a sentence. What to show, what to sort by, what to leave out. Vela runs it against the project model itself, so the board is current the moment a source moves. When the question changes you edit the sentence. You do not file a ticket and wait.
- Describe it in plain language and it builds
- It reads the live model, so it is current the moment a source moves
- Derived fields show the arithmetic behind them
New view
Draft“Every long-lead item with less than three weeks of float, and who owns each one.”
Development and interconnection
Does the date we gave the utility still hold?
The interconnection portal is built backwards from energization. Every milestone in front of it, the float left in each, and whichever long-lead item is currently binding the path. When a delivery moves at the factory this is the first board it appears on, because this is the board where it costs something.
- Milestones ordered by what is binding energization
- Float shown on each milestone, so a tight one is visible
- Utility commitments held against real dates
Development and interconnection
At riskProcurement
Does the quote still stand?
The procurement portal keeps the commercial clock next to the delivery one. Q-40218 holds its price until 21 Aug 2026, two months before the revised ship date, so the slot decision cannot wait for the machine to exist. The portal shows the decision, the premium and the person it is waiting on.
- Quotes held against their validity dates
- Supplier threads sit next to the register they contradict
- Open decisions show what they block and who they wait on
Procurement
Clock runningThe price hold runs out two months before the machine ships. The portal keeps that clock in view.
Construction and commissioning
What does this stage need before it closes?
The field portal follows the stage. It knows which captures this stage needs, which are still open, and which drawing revision added one. A firewall pier arriving in Rev 7 turns up as an open item on the foundation checklist, instead of as a drawing somebody was supposed to read.
- Checklists that follow the stage instead of a fixed template
- A revision that adds a requirement opens the capture for it
- Evidence lands on the record it belongs to
Construction and commissioning
FoundationsRev 7 added the pier. The checklist picked it up. Nobody had to notice and pass it on.
Who works out of what
Four audiences, one model underneath.
Every view reads the same live operating model, so the number leadership quotes is the number the field captured. What differs is the question each audience is there to answer.
Leadership and program teams
Portfolio status, critical risks, major decisions and cross-project dependencies. Dana Whitfield sees the slot-hold decision and the energization date it protects, not the thread it came from.
Project teams
Milestones, ownership, blockers and changes. GSU-01 on site belongs to Ana Duarte, the path behind it is drawn, and a moved date arrives as a change, not a surprise.
Functional teams
The records, workflows and decisions specific to the role. Procurement sees the quote and its price hold. Engineering sees Rev 7 and what it changed on the ground.
External partners
A controlled view of the documents, requests, approvals and commitments in their scope. Saguaro Line Engineering reads the drawing set and the requests aimed at it, and nothing beside them.
The rest of the platform
AI-native execution layer
The systems, documents and teams behind a project, reading into one place where the work moves.
ExploreAgent builder
Describe the job in plain language. Vela builds the agent that does it, against your live project.
ExploreProject brain
One source of truth for the project, and somewhere a document is still findable years later.
ExploreTell us which screen your team hates.
Bring the report somebody rebuilds by hand every Monday. We'll build the portal that replaces it against a project you already know.