Outage windows and what they gate
A missed window can push a project by seasons. Vela keeps each window beside the equipment, crews, and permissions it depends on, and flags the risk while there is time to act.
Utilities and grid infrastructure
Grid projects run on drawings, outage windows, long-lead equipment, and permissions that all have to line up. Vela holds each project's record as one model, from the first design set to the evidence that closes it out.
- ScopeThe line or station and what it serves
- DesignPackages, standards, and revisions
- EquipmentTransformers and breakers on vendor clocks
- Outage windowThe days the work can actually happen
- EnergizedCloseout with the evidence attached
What this team asks Vela.
Will the equipment make the outage window?
What changed in the latest package?
What evidence is still missing for closeout?
Vela answers from the project’s own record, and every answer names the document it came from.
Long-lead equipment on the record
Transformers and breakers move on vendor clocks that rarely match the outage plan. Vela reads the threads against the registers and raises the conflicts early.
Completion evidence as you go
Test reports, inspection records, and as-builts pile up at closeout. Vela files each piece against its milestone as the work happens, so closeout is a review instead of a hunt.
A breaker letter squeezes the outage.
The window was negotiated months ago and the equipment is chasing it, followed from the letter to the crew plan.
What arrivesVendor correspondenceBreaker delivery letterDelivery lands inside the window instead of before it
What movedDeliveryBefore the windowInside the windowTest timeFullCompressed
What it touchesOutage window Days the system agreed to give up onceCrew plan Contractors booked around the outage
Where it stopsProgram managerOwns the call between compressing the test and moving the window. Both drafts wait on their signature.Waiting on sign-off
How a program moves through Vela
The mechanism is the same on every page of this site, because it is the product. What changes is what it reads for you.
Connect what the work already produces
Vela reads the mail, drawing sets, registers, and calendars a project generates in the systems where they already live. Nothing gets moved and nothing gets re-entered.
The live model builds itself
Records, milestones, equipment, decisions, and owners get mapped into one operating picture. Every value keeps a way back to its source.
A change is traced to what it touches
When a source moves, Vela follows the change through the records and milestones that depend on it and flags the risk before the schedule slips.
A person signs off before anything moves
Vela stages the exact updates and drafts the replies, then stops. Nothing is written and nothing is sent until someone on your team approves it.
What Vela reads for a grid program
Vela connects to the systems the program already runs on and keeps every project's file current.
Reading and writing stay separate. Vela reads the scopes you grant, and writing anything back is its own permission with a named person signing off.
Sources
Read-only
Program inboxTransformer and breaker vendor threads, contractor letters, and outage requests
Program driveDesign packages, relay setting records, and factory test reports
Tracking sheetsThe transformer and breaker register, outage tabs, and closeout evidence trackers
Program calendarOutage windows, delivery dates, and witness testsArtifacts stay where they live. Vela reads them in place and keeps a way back to every source. The Google systems read today; the rest of the catalog ships in the order teams ask for it.
Who works out of it.
One model, read four ways. Each seat sees the records and decisions its own work depends on, without creating a second version of the project.
Program management
Answers for the capital plan and what has actually been delivered against it.
Engineering
Owns the design packages, the standards, and every revision that moves the field.
Field operations
Needs the current drawing, the work history, and the materials for the job in front of them.
Regulatory and reporting
Connects approved programs to completed work when the question comes.
Also in utilities and grid infrastructure
All industriesElectric UtilitiesUnify capital-project information across planning, engineering, procurement, construction, field operations, and regulatory reporting.See the pageLarge-Load Interconnection TeamsCoordinate applications, studies, customer requirements, network upgrades, agreements, and energization milestones.See the pageGrid Modernization ProgramsCreate a live view of distributed projects, infrastructure upgrades, vendors, schedules, risks, and regulatory commitments.See the page
Pick one project mid-outage-season.
We will model its windows, equipment, and evidence and show what surfaces first.