GridBuild Controls Platform / Early access
B4seline is a production-control layer for utility-scale energy: generation, storage, transmission and substations—built from installed quantities, not subjective percent complete.
PV
50 MW–1 GW+
BESS
50 MWh–2 GWh+
T&D
Lines + substations
Also serving mission-critical loads—data center and zone infrastructure—where the same production controls apply.
Grid delivery / Status cycle
OFFLINE READY
Production overview
Data date
09 SEP 2026
Installed
12,712
Rate30
248
Forecast
+4 days
Rules of credit
PF
1.06
The Phase 1A operating layer
B4seline is designed to be the place where field-installed work becomes a status signal your project team can approve, map, forecast, and report.
01
Measure foundations, civil, structural steel, ductbank, cable, equipment setting, and commissioning work against approved baseline quantities. Rules of credit turn physical completion into an auditable production signal.
02
Map production units to schedule activities and cost codes so progress, hours, productivity factor, and forecast dates speak the same language.
03
Capture quantities offline by unit, location, step, and crew. Supervisors review the same production record before it becomes the project truth.
04
Turn a production rate into a forecast finish, then into days early or late against the contract milestone and its liquidated-damages terms.
05
Use site maps to see what is installed, who is working, and which inspections, punch items, delays, or deliveries are blocking the next move.
06
Start with an auto-drafted daily report, tie delay evidence to the record, and keep notice clocks visible before a contractual deadline disappears.
The operating model
The platform is being built around a weekly rhythm that respects the systems already running the job—and gives the team a clear control point before progress becomes schedule or contract risk.
01
Create the production units, locations, rules of credit, and milestones that define a defensible plan.
02
Enter installed quantity offline, attach the record to a crew and location, then route it for approval.
03
Prepare the P6 file workflow and HCSS read crosswalk so approved status can be reviewed in context.
04
Monitor rates, milestone forecasts, LD exposure, daily reports, delay evidence, and notice deadlines in one operating rhythm.
Integration posture
B4seline's Phase 1A workflow prepares a file-based P6 status cycle and reads HeavyJob data for cost codes, crews, equipment, and approved time cards. The crosswalk makes the handoffs explicit while P6 remains the schedule authority and HCSS remains the hours and job-cost authority.
Early access is focused on reviewed file workflows and mapped data—not a promise of live API automation.
Product vision
Production, schedules, owner commitments, quality gates, commissioning, and turnover should be connected by the work actually installed. That is the operating system B4seline is building.
Early access / GridBuild Controls Platform
Walk through your current production, P6, and HCSS workflows with B4seline. We'll identify the first status cycle worth controlling.
