BIDLIGHT — DATA CENTER BIM MANAGEMENT
Deliver Data Centers. Track Everything.
Process, deliverables, and platform — from study to closeout
The delivery process that builds data centers in under 8 months — and the intelligence platform that tracks every model change, every contributor, and every dollar across the full project lifecycle.
TeslaAESCSpeedwellThe SphereMicrosoftAmazonGoogle
SECTION 1
Data Center Delivery — Process & Deliverables
How we model, coordinate, and deliver data centers of any tier — from study through closeout
Your BIM Team Is Flying Blind
What You Can't See Today
- Who changed what? Someone moved a duct, nobody knows who. 2-hour coordination meeting wasted.
- Who's behind? You find out at the GC coordination meeting — 3 weeks too late.
- Where are the issues? Scattered in Teams, email, Bluebeam. Nobody can find them.
- What changed between exports/Model sync? Comparing PDFs side-by-side like it's 2005.
- Delays that cost real money. Every week a clash goes unresolved, conduit doesn't get installed. Every missed coordination cycle pushes the schedule. At $15K-$50K per week in field labor standing idle, a 3-week delay costs more than BidLight does for the entire project.
- Field and office aren't talking. The BIM team models one thing, the field installs another. RFI responses sit in email for days. Redlines from the superintendent never make it back to the model. By the time the disconnect surfaces, the concrete is poured and the rework bill arrives.
What This Costs Your Projects — Every Month
$1.8T
Global losses from delays and rework
9/10
DC projects overrun schedule
15-30%
Coordination & Cost overruns
The real cost isn't money — it's trust. When you can't see who did what, accountability disappears. BidLight makes everything visible.
Deliver any data center of any tier, in under 8 months using BidLight system and process
Data Center BIM Delivery — From Study to Field Install
This is how a $50M+ data center electrical scope gets modeled, coordinated, and delivered. Every image below is from an active project. This is the process that BidLight automates, tracks, and makes auditable.
The delivery runs through 5 workstreams in sequence with as-built running live alongside construction: Study & Phase Planning (doc review, constructability, phase splitting — 3-5 weeks), Layout (kickoff, UG layouts, trade-by-trade electrical/mechanical/plumbing routing), Modeling (coordination + site UG first, then rolling detail through Phase 01 → P(N)), MEP Shop Drawings (issued per phase for field install), and MSD/MFG Drawings (fabrication packages per phase for prefab). Once Phase 01 shop drawings hit the field and install begins, as-built modeling kicks off — field updates, RFI responses, vendor-driven changes, and on-site clash resolutions flow back into the model in real time. GC and trade coordination runs on a weekly cadence alongside construction. As-built extends past the final phase for record model closeout. Every workstream involves multiple trades, multiple subs, and hundreds of model changes — each of which needs to be tracked, diffed, and attributed to the right person.
Without BidLight: This schedule lives in a spreadsheet. Nobody knows which phase is actually ahead or behind until the weekly coordination meeting. Model changes between phases go untracked. Cost impact of design changes is discovered at the post-mortem.
TYPICAL DELIVERABLES
BIM Scope of Work — What Gets Delivered on Every Data Center Project
BIM Modeling — LOD 350–500
Creation of LOD 350–500 Electrical BIM from design Revit files, CAD files, and/or PDF drawings. Modeling includes electrical equipment, panels, homerun conduit and any conduit runs 1" and above, slab/wall penetrations, lighting fixtures, racks, cable trays, generators, in-slab conduit, equipment power feeds, switchgear, raceways, and hangers.
Systems included: Branch power (main trunk lines from panels to homerun boxes), fire alarm, security, telecom, lighting, and all associated supports, conduits, and backing.
File deliverables: RVT and NWC files for coordination.
BIM Coordination & Clash Resolution
Revisions to BIM based on clash detection and clash resolution process. Weekly coordination meetings with GC focused on clash detection, scheduling alignment, and priority coordination. Direct internal clash resolution team managing all trades.
Typical duration: 30–50 weeks of active coordination depending on project phases and scope.
Meeting cadence: 2× weekly with GC (clash detection & coordination), 1× weekly with trade partners (schedule alignment & routing).
2D Coordinated Layout Drawings
Issuance of 2D coordinated electrical overhead layout drawings created from the 3D coordinated model after clash resolution is complete and model sign-off. Sheets include equipment/fixture/conduit type and sizing, X/Y dimensions from gridlines, and vertical elevations.
Typical output: 200–400 sheets per project depending on scope.
Includes: Detailing, dimensions, elevations, tagging & sizes of all modeled content, device layouts.
Schedule & Trade Partner Requirements
All work planned and executed in accordance with the approved project schedule and coordination priorities. BIM coordination schedule incorporated upon receipt. Project end date fixed per GC requirements with optimization opportunities identified during study phase.
Trade partner responsibilities: Provide field markups showing routing, sizes, and end locations. Attend weekly meetings to review schedule, routing issues, submittals, deliverable dates, and fabrication details.
Change management: All RFIs and design changes after area/system sign-off are handled through formal change order process.
Scope Boundaries & Clarifications
Included: All raceways 1" and above from panel to first homerun box. All hangers for raceways. Power, lighting, telecom, security, and fire alarm systems. Interior and site sheet creation. Evolve fabrication and detailing discovery.
Excluded: Conduit under 1" (unless homerun or grouped to equal over 1"). Wiring, low voltage systems, power/data outlets & switches. Exterior raceways, vaults, transformers, pull boxes. Device-to-homerun connections handled by trade partner's internal team.
This scope structure is representative of a typical data center BIM engagement. Actual deliverables, duration, and trade coverage are tailored to each project's requirements, phase count, and coordination schedule.
This is what coordination looks like on every data center project today: 7+ people on a Navisworks call staring at a model full of yellow conduits, blue mechanical ducts, and green cable trays — manually reviewing element properties, trying to figure out what changed since last week. This meeting happens 2-3 times per week, 90+ minutes each. That's $2,000-$3,000 in labor per meeting, per project, per week. BidLight's export history and diff inspector eliminate the guesswork — the meeting goes from 90 minutes to 15.
Before any conduit gets modeled, the electrical rooms need to be laid out. MSD boards, ATS units, transformers, and house load panels — all owner-furnished equipment that must be placed and coordinated against the one-line diagram. The red markup highlights where equipment needs to shift. If this coordination issue is missed, it results in a $15K-$50K field rework when the concrete is already poured and the gear can't fit.
Underground duct bank layout — dimensioned conduit routing, manholes, and coordination with civil/structural grids.
Underground skid positioning tracked in Revit — UG progress tracking, prefab tracking, MV heat calcs, and per-romp breakdowns.
Underground is the most time-critical and least forgiving scope. Once concrete is poured, changes cost 10× what they would have cost in the model. Every conduit stub-up location must match the above-grade model exactly. The generator yard is where redundant power paths converge — cable bus risers, conduit racks, and underground duct banks meeting at the building perimeter. Coordination here involves structural (steel supports), civil (duct bank crossings), and electrical (cable bus clearances). A single misalignment delays generator commissioning by weeks. BidLight's export history and diff inspector track every underground element change automatically — so when a stub-up moves, the entire team knows immediately.
Main power feeders — primary electrical distribution modeled in 3D with element-level tracking. Every feeder has a unique Revit element ID that BidLight tracks through every export.
Overhead conduit and hanger modeling — conduit runs with parametric bend properties, trapeze rod lengths, and elevation constraints.
Conduit branching with parametric offsets, bend angles, trapeze rod specifications, and elevation tracking.
Overhead branching power — conduits routed through structural penetrations with element ID tracking.
Branch circuit conduit bends at structural penetrations — multi-element selection for coordination.
Complex conduit routing with 7+ element IDs per selection — this is where coordination failures happen.
Branching power and telecom coordination — electrical conduits vs telecom pathways sharing overhead space.
Overhead conduit routing is where 60-70% of coordination issues originate on a data center project. Hundreds of conduits running at different elevations, sharing overhead space with mechanical ductwork, cable trays, and fire protection piping. Each conduit has parametric properties — bend angles, offset heights, roll distances, coupling types, trapeze rod lengths — that must be coordinated with the hanger design and structural supports. A single conduit moved 2 inches can cascade into 15 downstream clashes.
Electrical conduit stub-ups through floor — vertical penetrations must clear mechanical equipment above and below.
Mechanical feeder hangers — prefab drawing showing trapeze hanger placement relative to conduit routing.
Mechanical vs electrical coordination is where the most expensive field rework happens. When the mechanical sub moves a duct 6 inches, the electrical sub's hangers no longer fit. Without BidLight tracking these changes across exports, the conflict gets discovered at field install — costing $50K-$200K per occurrence. BidLight tracks every element ID through every export, so when something moves, the diff shows exactly which elements were affected and who made the change.
Underground duct bank layout drawing — full site plan with conduit routing, manhole locations, and dimensional coordination across all electrical zones.
Duct bank detail section — conduit spacing, tier arrangement, and concrete encasement dimensions issued for contractor field install.
Pull calculation sheets generated from the model — every conduit run with bend angles, lengths, and wire sizing for the field crew.
Shop drawings for underground duct bank layout — dimensioned and ready for contractor fabrication and install.
Once the model is coordinated, pull calculations and shop drawings are generated directly from Revit. Every time the model changes, these documents need to be regenerated. In the field, a technician verifies conduit stub-up locations using a total station against BIM model coordinates. If the model is wrong, every stub-up is in the wrong place — and reworking underground conduit after the slab is poured costs $5,000-$15,000 per penetration. BidLight's export history tracks which revisions triggered new shop drawing releases, the diff inspector shows which conduit runs changed, and the issue tracker links field-found discrepancies back to the specific model revision and the person who made the change.
Electrical skid assembly — modular switchgear room modeled in 3D with cable bus, conduit connections, and element ID selection for BIM-to-fabrication handoff.
Skid conduit routing detail — 4 conduits routed through the skid frame with offsets and cable tray transitions tracked by element ID.
Manufacturing drawing package — prefabricated electrical assembly with conduit penetration locations, mounting details, and dimensional callouts ready for factory production.
Prefab coordination detail — modular assembly cross-referenced against the BIM model to verify conduit alignments, equipment clearances, and connection points before shipping to site.
Data center electrical skids are modular assemblies — entire switchgear rooms built in a factory and shipped to site. The 3D model must match the fabrication drawings exactly: every conduit penetration, cable tray connection, and equipment mounting point. When the skid design changes, BidLight's diff shows which elements moved and whether the underground stub-ups still align. If they don't, the field install fails — and a 20-ton skid can't be shifted 2 inches.
This is the full lifecycle BidLight tracks: From the initial study and layout → through underground duct banks and generator yard → through overhead conduit routing, branching power, and mechanical coordination → to pull calculations, shop drawings, field layout verification → through as-built markup and shared collaboration → to skid manufacturing and prefab coordination. Every model export is versioned. Every element change is diffed. Every issue is attributed to a person. Every resolution is documented and traceable.
3D model markup — conduit routing directives, clash identification, and redline annotations placed directly on the BIM model with element-level linking.
3D markup with shared collaboration — manhole structure annotated with clash circles, shared with field crew and engineering in real time.
←
MKE-16UMS42-MH01 displacement for crane pad
● Can Edit
✓ Saved 2 min ago☰ History↗ Share
Change History
Mouldi N. Tue 12:46 PM
Added red-line markup — conduit bend directive for Larry & Jon
Steve K. Fri 12:50 PM
Flagged manhole NE corner — 10.9" below spec depth
Steve K. Fri 12:45 PM
Uploaded 3D markup — manhole structure with clash circles
Mouldi N. Fri 12:43 PM
Ran clash on all 4 corners — 1 of them <18" from grade on NE
2D conduit markup drawing — red-line annotations on shop drawings with bend directives, shared directly from BidLight to the field crew.
Field markup — stub-up coordination issues flagged on-site and linked back to the BIM model with photo documentation.
Site-wide coordination overlay — power (red) and fiber (green) routing tracked across the entire campus with every contributor visible. Drone shot annotated directly inside BidLight.
As-built modeling is where most projects fall apart. As construction proceeds in the field, the coordinated model needs to be updated to reflect what's actually installed — RFI responses, field conditions, deviations from design, vendor-driven changes, and clash resolutions done on-site. This runs concurrent with construction of earlier phases while later phases are still being modeled and drawn. It requires tight coordination between the GC and all trades because everyone is feeding field data back into the model simultaneously. A conduit route shifts because of an RFI. A manhole is 10.9" below spec depth. A crane pad displaces underground infrastructure. Today, these changes get communicated through Teams chats, email threads, and Bluebeam sessions that nobody can find 6 months later. BidLight replaces all of that: mark up 3D models, 2D drawings, and drone shots directly inside the platform. Share with anyone — internal or external — with permission-based access. Every annotation is linked to the element, tracked in the issue log, and part of the permanent record model through closeout.
What this replaces: Bluebeam sessions that expire. Teams chats that get buried. Email threads with 15 people CC'd. Shared drives with 47 versions of the same markup. BidLight consolidates all coordination communication into one auditable system — tied to the model, tied to the person, tied to the resolution.
Model Export History — Every Change Tracked with Diffs
Every model export becomes a versioned snapshot. BidLight automatically computes element-level diffs between exports — components added, removed, modified, with category breakdowns and cost impact.
⑂ 62 changes
1,247 Components
Conduit: 342
Cable Tray: 128
Pipe: 89
Duct: 214
+6 more
Exported by:Mouldi Nouri
Revit Version:2024.2
Plugin Version:3.1.4
Total Size:24.8 MB
⬇ Model Data (JSON) 18.2 MB
⬇ 3D Model (GLB) 6.6 MB
20th
January
12:46 pm
2026
⑂ 38 changes
892 Components
Floor Box: 24
Conduit: 186
Panel: 12
+4 more
Exported by:Larry Rodney
Revit Version:2024.2
Total Size:16.4 MB
⬇ Model Data (JSON) 12.1 MB
⬇ 3D Model (GLB) 4.3 MB
15th
January
3:22 pm
2026
✓ Baseline
2,341 Components
Raceway: 456
Manhole: 32
Coupler Pit: 18
Fiber: 284
+8 more
Exported by:Steve Koppa
Total Size:38.1 MB
⬇ Model Data (JSON) 28.4 MB
⬇ 3D Model (GLB) 9.7 MB
16th
January
12:50 pm
2026
3D Markup & Shared Collaboration — Replace Teams & Email
Mark up 3D models, 2D drawings, and drone shots directly inside BidLight. Share with anyone — internal or external — with permission-based access. Full change history with auto-save.
Active Collaborators
Change History
Mouldi N. Tue 12:46 PM
Added red-line markup — conduit bend directive for Larry & Jon
Steve K. Fri 12:50 PM
Flagged manhole NE corner — 10.9" below spec depth
Steve K. Fri 12:45 PM
Uploaded 3D markup — manhole structure with clash circles
Mouldi N. Fri 12:43 PM
Ran clash on all 4 corners — 1 of them <18" from grade on NE
What this replaces ↓
This Teams chat with Steve Koppa? It now lives inside BidLight — linked to the element, tracked in the issue log, searchable forever.
Installation drawing — temp power penetrations at Microsoft CUP Phase 2. Reviewed and approved through BidLight's quality gate.
Site-wide coordination overlay — power (red) and fiber (green) routing tracked across the entire campus with every contributor visible.
Issues Linked to Geometry — Not Lost in Email
Every issue is pinned to a Revit element with an auto-captured 3D screenshot. Assigned by trade, tracked through resolution — with full accountability.
Element:UMS-MH01 (ID: 1847293)
Assigned to:Larry Rodney — Electrical
Due:Jan 25, 2026
Resolution:Move 7' north, add 2× 22° bends
Clash
Coordination
Electrical
3 replies · Last: Mouldi N. 2h ago
Element:UMS71-MH01
Flagged by:Steve Koppa — Field
Finding:NE corner 10.9" — needs min 18" from grade
Spec Violation
Site/Civil
Resolved by:Mouldi Nouri — 2.1 hrs
Resolution:Coupler pit alignment verified against design
Steve's field finding — vault structure needs min 18" below final grade. This markup is now linked to element UMS71-MH01 inside BidLight with full resolution history.
Every issue becomes training data. Over time, BidLight predicts where issues will occur in new projects based on trade, geometry type, and historical patterns from your completed projects.
Team Intelligence — Know Who Delivers
Contribution tracking, issue resolution rates, and Problem Solver Index per team member. See who's ahead, who's behind, and who needs support.
Team Performance — Microsoft CUP Phase 2
MN
Mouldi Nouri
BIM Lead · 148 elem/wk · PSI 94
SK
Steve Koppa
Site Coord · 86 elem/wk · PSI 82
LR
Larry Rodney
Electrical · 112 elem/wk · PSI 88
JF
Jon Falcone
Electrical · 54 elem/wk · PSI 61
Schedule by Employee
Mouldi N.28/30 tasks
On track — 2 remaining
Steve K.22/26 tasks
Slight delay — field hold on NE manhole
Jon F.11/24 tasks
Behind — needs support or reallocation
Larry R.19/20 tasks
Ahead of schedule — available for support
Problem Solver Index (PSI): (issues resolved × complexity) / avg time. Jon at PSI 61 needs pairing with Larry (PSI 88). You see this now, not at the next weekly meeting.
Quality Gate — Every Change Reviewed Before It Goes Live
Every model change passes through automated health checks, naming validation, and clash detection before it reaches the shared model. The cost of catching a clash in the model is $50. The cost of catching it in the field is $5,000-$50,000.
Already built into BidLight: Model Health Checker, Auto-Assignment, Document Control, and Revision Management are production modules today. The Quality Gate connects them into a single review workflow.
The Intelligence Flow — From BIM Commit to Employee Decision
This is how BidLight connects every model export, every cost change, every issue, and every team member into a single intelligence layer. Walk through each step with your team.
These are the questions that cost you money every week: Who changed what? What did it cost? Who's solving problems? Who needs help? What happens next? GCs and subs using BidLight answer all five in under 5 minutes. Without it, you're spending hours in meetings reconstructing the answers from memory.
1
BIM Commits — Every Export Is a Versioned Snapshot
Who exported what, when, with element-level diffs between every revision
What you see:Every revision with component count, diff bars (+12 −3 ~57), milestone badge (DD/CD), and review status.
Who did it:User avatar and name on every export. Daria exported 4 times, Ari only once. That tells you something.
What changed:Green/red/yellow diff bars show added/removed/modified components at a glance. Click "Review diff" for detail.
2
Cost Diffs — See the Dollar Impact of Every Change
Track cost evolution across revisions with per-category, per-user attribution
Estimate History — every revision shows total cost, delta from previous, top cost driver, and the user who triggered the change.
Category × Revision Matrix — follow every cost category across every revision. Green = increase, pink = decrease. Spot drift instantly.
Split-pane breakdown — click any revision to see full category detail with percentage changes, progress bars, and "Open" drill-down per category.
3
Issue Tracking — Every Issue Tagged to a Person and a Revision
Kanban board + revision-grouped view shows who raises issues and who resolves them
Kanban board — Open (3), In Review (2), Resolved (6), Abandoned (1). Each card shows discipline, severity, assignee, comment count, and clash count.
Issues by Revision — see which revisions raised new issues and which ones closed them. R8 raised 2 and closed 2. R9 raised 1, closed 0. That's a signal.
4
Employee Intelligence — The Math That Tells You Who to Keep
Exports grouped by milestone + user attribution = complete performance picture
Exports by milestone — each model upload is paired with the estimate revision it triggered. User avatar shows who did it. You see DL exported R10 (+$312K), JM did R9 (-$19K), RM did R7 (+$92K). The pattern is clear.
The Employee Math — Problem Solver Index
From the data above, BidLight computes a Problem Solver Index (PSI) for each team member:
PSI = (issues closed × severity weight) ÷ avg resolution time
✓ RETAIN & PROMOTE
4 exports, 5 issues closed, 1.8h avg resolution. Resolves urgent clashes 4× faster than team avg. Her revisions save money (R9: -$19K via HVAC). Promote to lead coordinator.
⚠ NEEDS DEVELOPMENT
1 export, raised 4 issues but only closed 1. 7.8h avg resolution (3× team avg). R6 triggered +$25K in cost drift with 34 additions but 8 removals. Pair with Daria for 2 sprints, reassess.
5
Projection — What Happens Next
Data-driven forecast for the next 3 revisions based on historical patterns
| Metric | Current (R10) | R11 (projected) | R12 (projected) | CD Final |
|---|
| Project Total | $4.72M | $4.85M | $4.91M | $5.02M |
| Open Issues | 4 | 2–3 | 1–2 | 0 |
| Avg Team PSI | 69 | 72 | 75 | 78+ |
| Cost Accuracy | 80% | 85% | 88% | 92%+ |
| Schedule Risk | Medium | Medium | Low | Low |
Bottom Line: The project will close CD at approximately $5.02M (vs $4.12M baseline). The +$900K delta is driven by structural scope changes (Concrete +$187K, Steel +$177K) — not estimation errors. Your top performer resolves issues 4× faster than your weakest. Pair them and your team PSI jumps 12 points. BidLight gives you this visibility on Day 1. Without it, you'd discover these patterns at the post-mortem.
BIM Delivery Platform — What GCs and Subcontractors Use to Ship Projects Faster
When your GC is coordinating 8 trades across a 500,000 sq ft data center, and your MEP sub has 12 modelers pushing changes daily — this is how you keep control. Every screenshot below is a production feature your project teams use to deliver on time, on budget, with full accountability.
MODEL EXPORTS
Track every trade.s model submissions — who pushed what, when, and what broke
Export History — Card View
Your MEP sub pushes a new export — BidLight instantly shows what changed: 648 components, +12 added, −3 removed, ~57 modified. The GC.s BIM coordinator sees "Needs review" on Revision 10 and knows Daria from the electrical sub made the push. Without this, your coordination meetings start with "did you upload the latest?" and waste 20 minutes finding out. With BidLight, the answer is on screen before the meeting starts.
Export History — Dense Table
When the GC needs to report to the owner on model progress, this table gives them everything: 7 revisions from Aug-Nov, component growth from 588→648, who pushed each one (Daria 4 times, Ari once — that tells you who.s carrying the load), file sizes for BIM execution plan compliance, and CSV export for the owner.s monthly report.
Split-Pane Inspector — Element-Level Changes
When a sub.s model push triggers a clash spike, the GC coordinator clicks into that revision and sees exactly what happened: 12 added, 3 removed, 57 modified, 579 unchanged. The category breakdown shows Structural had the most churn (+8 −1 ~28). The top changes list names the specific elements — W18x50 Beam on Grid C.4 was modified, two shear walls were added on Level 2. Click "Focus in 3D" to see it in the model. This is how a GC holds subs accountable for their changes.
Project Timeline — Model + Estimate Side by Side
The GC.s project executive sees the full project heartbeat: model uploads from subs on the left, cost estimate revisions on the right, connected by date. When the curtain wall sub pushed R6 with 34 additions and 8 removals but no estimate was triggered — that.s a gap. The PM flags it. When R7 shows a model push paired with a +$92K estimate increase driven by Curtain Wall — that.s a change order conversation with the owner, backed by data, not guesswork.
COST TRACKING
Know the cost impact of every sub.s model change before it becomes a change order
Estimate History — Cost Cards with Category Breakdown
The GC sees the project at $4.72M — up $595K from the $4.12M baseline. But instead of discovering this at the next owner meeting, they see it in real time. Each sub.s push is tagged: Daria.s R10 added +$312K driven by Concrete (+$129K) and Steel (+$84K). Jordan.s R9 actually saved -$19K on HVAC. The GC can now walk into the owner meeting with a revision-by-revision cost narrative, not a lump-sum surprise.
ISSUE MANAGEMENT
Coordination issues assigned to the right trade, tracked to resolution, with documentation
Issue Board — Kanban by Status
The GC.s coordination board: 3 open issues need attention, 2 are in review by subs, 6 have been resolved with full documentation, 1 was abandoned. The structural sub has MK-126 (shear wall penetration not in model) tagged URGENT — it.s been open since R9 with 5 clashes and no assignee. The GC coordinator drags it to "In Review" and assigns it to the structural sub.s BIM lead. The "I didn.t know about that" excuse — which costs GCs an average of $15K-$30K per missed coordination item — is eliminated because every issue is tracked, assigned, and visible to the entire team.
Issue Table — Full Detail, Sortable
Before the weekly GC-sub coordination meeting, the coordinator pulls up this table: 12 issues, sortable by status, priority, discipline, or assignee. They can see that Daria (electrical sub) authored 3 issues and has 2 assigned to her — she.s both finding and fixing problems. Sam (PM) authored 3 issues but has 0 resolved — he.s flagging problems but not following through. The GC uses this table to run a 30-minute coordination meeting instead of a 2-hour one.
Issues Grouped by Revision — Raised vs Closed
The GC tracks which sub deliverables are clean and which create coordination chaos. R8 (Daria, electrical sub) raised 2 issues but also closed 2 — net zero, clean delivery. R9 (Jordan, MEP sub) raised 1 new issue and closed nothing — net negative, that sub needs a conversation. R6 raised 3 and closed 1 — the DD freeze push from the curtain wall sub created more problems than it solved. This is how a GC evaluates sub performance by the data, not by who talks the best game in meetings.
ISSUE RESOLUTION
Verified resolution — 3D diffs, screenshots, and sign-off trail
Resolution View — 3D Before/After with Activity Thread
When the GC flags a column clash with the HVAC duct at Grid C.4, the MEP sub needs to prove they fixed it. BidLight shows BEFORE (R6) and AFTER (R8) in 3D — the column shifted 225mm east, HVAC supply rerouted. Stats confirm: 3 objects moved, 0 new clashes introduced, +$12.8K cost impact. The activity thread shows the full chain: Ari (structural sub) opened it, Daria (electrical sub) confirmed in 3D, Sam (GC PM) approved the structural shift, Daria made the model change and marked resolved. This is the audit trail an owner needs to approve the change order.
Hybrid Resolution — 2D Sheet + 3D Model + Activity + Requirements
The electrical sub flagged that the transformer room clearance was 810mm — code requires 914mm minimum. BidLight shows the 2D sheet markup (E-110 Basement Power Plan) alongside the 3D model with BEFORE/AFTER toggle. The GC coordinator can verify: east wall expanded 400mm, structural slab-edge adjusted, cost impact +$18.2K. The resolution checklist requires: screenshot attached ✓, user tagged ✓, linked model commit ✓. The sub can.t mark it resolved without proving the fix in the model. This is how GCs eliminate "we fixed it in the model" claims that turn out to be false at field install.
Resolution Diff Dashboard — All Resolved Issues at a Glance
At the end of the DD phase, the GC presents this dashboard to the owner: 4 coordination issues resolved, 21 objects moved across 6 model commits, 0 new clashes introduced, +$141.3K total cost impact. Each card shows before/after 3D renders so the owner can visually verify the resolution. This is the closeout documentation that used to take 2 weeks to compile manually — BidLight generates it automatically from the resolution history.
TEAM ANALYTICS
GC oversight dashboard — which subs are delivering, which are behind, which need replacement
Project Activity Dashboard — 8 Weeks of Team Performance
The GC.s weekly sub performance review: 19 issues opened across all trades, 11 resolved (58%), 4.2 day avg resolution time. The per-user table reveals the truth about each sub.s BIM team: Daria (electrical sub) has a 75% close rate with 4 diffs pushed — she.s the strongest contributor. Ravi (structural sub) opened 0 and resolved 0 — effectively invisible. Sam (GC PM) opened 3 but resolved 0 — he.s creating work for others without closing any himself. By milestone: DD phase achieved 67% resolution, CD is at 44% — the GC needs to escalate CD coordination before the next owner milestone review.
Every screen above is production software. Your GC coordinators use the export history and diff inspector to verify sub deliverables. Your subs use the issue board and resolution views to prove their work. Your project executives use the analytics dashboard to evaluate sub performance and make staffing decisions. The GCs and subs already using BidLight are delivering projects with data, accountability, and a full audit trail. The ones who aren't are still running coordination meetings with spreadsheets and hoping nobody moved a duct overnight.
Team Analysis — Know Exactly Who's Carrying the Project
Without this data, you're making staffing decisions based on who talks the loudest in meetings. With BidLight, every commit, every sync, every active day is tracked per team member — and the AI flags who to recognize, who needs support, and who needs a performance conversation. GCs and subs using this are retaining their best people and addressing underperformance before it impacts the project.
CONTRIBUTOR ANALYTICS
91 days of daily commit activity — the GitHub contribution graph for BIM
Team View — 741 Commits Across 5 Contributors Over 90 Days
The GC sees the full team's commit velocity stacked by contributor. 741 total commits, averaging 8.1/day, with a max spike of 18 in a single day. Each color represents a team member — you can immediately see that Daria (dark blue, 197 commits) and Jordan (light blue, 178) are the workhorses, while Ravi (green, 92) contributes less than half. When commit volume drops (late October dip), the GC knows to ask why.
Individual View — Each Contributor's Daily Commit Pattern
Switch to Individuals view and the story gets granular. Each card shows one team member's commit pattern over 91 days:
DL
Daria López — BIM Lead
197 commits · 79 active days · max 6/day. Consistent daily output from Sep through Nov. No gaps longer than 2 days. This is your most reliable sub contributor — she shows up every day and pushes work.
JM
Jordan Mata — Estimator
178 commits · 59 active days · max 5/day. Solid output but with visible gaps — inactive stretches in mid-Oct suggest he was pulled to another project. 59 of 91 days active is good but not great for a lead estimator.
174 commits · 73 active days · max 6/day. High commit count but with a spiky pattern — big bursts followed by quiet days. This suggests deadline-driven work rather than steady delivery. Consistent presence (73 days) but uneven output.
RM
Ravi Mehta — Estimator
92 commits · 36 active days · max 8/day. Lowest output on the team. Only active 36 of 91 days — less than 40%. When he does work, he pushes hard (max 8/day), but the gaps are long. Either underloaded, split across projects, or disengaged. Needs a conversation.
100 commits · 54 active days · max 6/day. Moderate output for a PM. Active 54 of 91 days — reasonable for a coordination role. But cross-reference with the issue data: Sam opened 3 issues and resolved 0. His commits are coordination overhead, not production output.
GitHub-Style Heatmaps — Spot Patterns at a Glance
Switch to Heatmap view and each contributor gets a GitHub-style green grid showing daily commit density across Mon/Wed/Fri rows over 91 days. Darker squares = more commits that day. You can instantly see: Daria has an almost fully dark grid (79 active days). Ravi's grid is mostly empty with scattered green dots (36 active days). This is the visual that makes the staffing conversation undeniable.
Recent Activity Feed — The Audit Trail
Every MODEL export, ESTIMATE revision, and RESOLVED issue in chronological order with user avatars and revision numbers. The GC coordinator scans this feed to see that Daria (DL) dominated R10 — she pushed the model, ran the estimate (+$312.4K, +7.1%), and resolved MK-124 (transformer clearance) all in the same cycle. Meanwhile Jordan (JM) only appears for R9 with a minor estimate adjustment. This feed is the record that replaces "I was working on it" with "here's exactly what you did."
AI TEAM INSIGHTS
BidLight AI analyzes commits, issues, and activity to recommend people decisions
Star Contributors vs Performance Review Needed — AI-Scored
BidLight's AI scores each team member on a 0-100 scale based on issues resolved, issues opened, diffs pushed, commit cadence, and active days. Then it sorts them into three buckets with specific recommended actions:
⭐ STAR CONTRIBUTORS — 3
Daria López (94) — 3 resolved, 4 opened, 4 diffs, 197 commits, 79 active days. Pushed 4 revisions, active 79 of 91 days, 75% of her issues got resolved, authored +$497K in estimate deltas. Action: Recognize in next review. Consider for mentor role.
Jordan Mata (66) — Pushed 3 revisions, steady commit pattern. Star contributor.
Ari Kwon (65) — Active 73 of 91 days, highly consistent. Star contributor.
ⓘ NEEDS SUPPORT — 0
No team members currently flagged for coaching or pairing. This bucket catches people who are active but struggling — high commit count but low resolve rate, or high issue creation without follow-through.
⚠ PERFORMANCE REVIEW — 2
Ravi Mehta (33) — 0 resolved, 0 opened, 1 diff, 92 commits, only 36 active days. "No notable signals in this window." Actions: Performance conversation. Review workload & blockers. Set 30-day improvement plan.
Sam Choi (30) — 0 resolved, 3 opened, 1 diff, 100 commits, 54 active days. "Opened 3 issues but resolved none yet." Actions: Performance conversation. Review workload & blockers. Set 30-day improvement plan.
Human review required. BidLight's AI notes: "These suggestions are pattern-matching across a narrow set of BIM/estimation activity metrics. They do not see mentorship, design work, sick leave, parental leave, stakeholder-facing contributions, or a dozen other things that matter. Treat them as prompts for conversation — never as the basis for termination or promotion." The AI recommends the conversation. The GC makes the decision.
Project Analytics — Your BIM Command Center
This is where everything comes together. One dashboard that shows project health, team performance, issue velocity, cost drift, and AI-recommended next actions — across every revision, every discipline, every team member.
①
Filter by User, Discipline, Milestone, or Time Window
Slice the data any way your executives need to see it
Why this matters for large teams: When you have 5 collaborators across 5 disciplines pushing 10 revisions, you can't track everything manually. This header lets a PM or BIM manager instantly filter to:
- "Show me only Ari's work" — click his avatar, see only his exports, issues, and cost impact
- "Show me only Electrical in DD phase" — filter by discipline and milestone to isolate scope creep
- "What happened last 7 days?" — time filter catches who's been active and who's gone dark
Without BidLight, someone is digging through Revit worksharing logs or asking people in meetings — burning 30 minutes to answer a question that takes 2 clicks here.
②
Project Pulse — KPIs, Activity Chart, and Revision Timeline
See the heartbeat of your project at a glance — issues, diffs, cost delta, and resolve speed
Top-Line KPIs
Five numbers that tell you everything: 8 issues opened, 6 resolved, 5 diffs pushed, +$595K cost delta, and 11.0 day avg resolution time. When issues opened exceeds issues resolved, the backlog is growing — and every unresolved issue is a potential field rework event ($5K-$50K each). When avg resolve time climbs past 7 days, coordination is breaking down. GCs and subs using BidLight check these five numbers every Monday morning — and catch problems weeks before they become change orders.
Activity Chart + Revision Timeline
The weekly activity chart shows opened (orange), resolved (green), and diffs (gray) stacked by week. If green bars are shrinking while orange grows, you have a problem building. The per-revision timeline shows every export and issue event on a single line — SD → DD → CD progression with issue counts per revision. You can see that DD phase had the most issue churn (revisions 4–7), and CD stabilized. That's healthy.
Per milestone breakdown shows SD (0 issues), DD (5/7 resolved, +$301.5K), CD (1/5 resolved, +$293.7K). CD has the highest unresolved ratio — that's where your attention should be right now.
③
Per User & Per Discipline — Who's Delivering, Who's Blocking
The table that answers "which employee should I keep and which one needs coaching"
Per Discipline — Where's the Backlog?
Architecture opened 5 issues but only resolved 2. Structural opened 4, resolved 2. That's a 40% resolution rate — well below the 60% target. Mechanical, Electrical, and Plumbing are all 1:1. The problem is concentrated in Arch and Structural — that's where you allocate review resources this week.
Per User — The Employee Scorecard
This table is what makes BidLight different from every other BIM tool. For each team member you see:
issues opened, issues resolved, diffs pushed, comments authored, and cost impact. Read the data:
- Daria López — 4 opened, 3 resolved, 4 diffs, 23 comments, +$497K cost authored. She's the engine. High output, high resolve rate, high engagement.
- Sam Choi — 3 opened, 0 resolved, 1 diff, 20 comments. Talks a lot but closes nothing. That's a coaching conversation.
- Ravi Mehta — 0 opened, 0 resolved, 1 diff. Near-invisible. Either underloaded or disengaged.
- Ari Kwon — 3 opened, 2 resolved, 1 diff, 21 comments. Active but slow — 3 open issues assigned right now.
Recent Activity Feed
The activity feed at the bottom shows every MODEL export, ESTIMATE revision, and RESOLVED issue in chronological order — color-coded by type with user avatars. You can see that Daria (DL) dominated R10 and R8 — model export, estimate push, and issue resolution all in the same revision. Meanwhile Jordan (JM) only shows up for R9 with a minor estimate change. This is the audit trail that lets you reconstruct exactly who did what and when — The $15K-$30K "I thought you handled that" coordination failures are eliminated because every action is logged with a timestamp and a name.
④
AI Suggested Actions — BidLight Tells You What to Do Next
9 recommended actions prioritized by urgency — the system thinks so your managers don't have to
This is what GCs and subs are paying for without realizing it. Every Monday morning, your BIM managers spend 60-90 minutes reviewing logs, chasing threads, and reconstructing who was supposed to do what. That's $150-$250 in labor per meeting, per project, per week. BidLight computes the recommended actions automatically and sorts them by urgency:
🔴 Urgent — Requires attention today
- Escalate MK-126 — Shear wall penetration not in model. Opened at R9, still open. 5 model refs.
- Escalate MK-123 — Plumbing riser through beam. 6 comments, 3 markups. Nobody's assigned.
- Review cost spike on R10 — +$312K (+7.1%) in a single push. Top driver: Concrete. 57 modified lines.
🟠 Highly Recommended — Address this week
- Architecture backlog growing — 5 opened vs 2 resolved. Resolution rate 40%, below typical 60%.
- Rebalance Sam's queue — Opened 3 issues, resolved 0. 0% resolve ratio. Blocking others.
- Estimate is drifting up — 3 consecutive positive deltas totaling +$209K. Consider design-to-budget review.
🔵 Next Action — Keep momentum
- Publish the next export — Last push was 7d ago. Typical cadence is ~6d. Changes accumulating.
- 1 issue ready for sign-off — MK-127 annotations complete, just awaiting reviewer.
- Follow up with Ari — 3 open issues assigned. A sync could unblock them.
This is what coordination looks like when it's automated. The BIM manager opens the dashboard, sees 3 urgent items, assigns owners with one click — and the entire team has clear direction in 5 minutes. The 90-minute coordination meeting where nobody remembers who was supposed to do what costs $2,000+ in labor every week. Multiply by 52 weeks across 3 active projects — that's $312K/year in meetings that BidLight eliminates.
Featured Project Experience
BidLight has delivered BIM coordination and modeling on projects across data centers, manufacturing, and critical infrastructure — working alongside industry-leading GCs and electrical subcontractors.
Full electrical BIM coordination including site power, underground duct banks, manhole coordination, cable tray systems, and temp power layouts. Multi-discipline clash resolution managed through Procore.
Data CenterElectricalUndergroundProcore
BIM modeling and coordination for electrical distribution, structured cabling, and MEP coordination across building systems.
Data CenterMEP CoordinationElectrical
Electrical raceway coordination, power distribution modeling, and multi-trade coordination for facility expansion.
Data CenterElectricalRaceway
BIM coordination and cost estimation for manufacturing facilities — validating 98%+ accuracy on quantity takeoffs with same-day deployment of estimation workflows.
ManufacturingCost EstimationBIM Coordination
End-to-end BIM services from modeling through cost validation. Automated estimation with 98%+ accuracy on complex industrial systems.
ManufacturingIndustrialEstimation
BIM coordination for one of the most complex entertainment venues ever built — multi-system electrical coordination with tight tolerances and unprecedented geometry.
EntertainmentComplex GeometryElectrical
Clients & Partners
Tech Clients
Microsoft
Amazon
Google
Tesla
AESC
Speedwell Construction
GC Partners
Holder Construction
Walsh Group
Fortis Construction
Rosendin Electric
Cupertino Electric
Electrical Subcontractors
Meade Electric
Bergelectric
Helix Electric
Interstates
Pricing — BIM Management
Structured the way you already bid and budget — per project scope, tied to deliverables.
Per-Project Scope
RECOMMENDED
% of BIM Coordination Budget
10–15%
of the project's BIM coordination line item
Goes straight into your bid as a line item. Scales with project value. Recoverable from the owner.
$30M scope$150K–$225K
$50M scope$250K–$375K
$100M scope$500K–$750K
$200M+ scopeCustom
Per-Project Flat Fee
$200K–$600K
Fixed price · Paid at project milestones
One number in the bid. Paid as you hit milestones: 30% kickoff, 40% modeling, 20% shop drawings, 10% closeout.
Small (1–2 phases)$200K–$300K
Mid (3–5 phases)$350K–$450K
Large (6+ phases)$500K–$600K
Campus / multi-bldg$750K+
Cost per Square Foot
$2.00–$3.50/SF
of data hall area
One line in the cost model. Your estimating team plugs it in the same way they plug in conduit, labor, and cable tray.
100K SF$200K–$350K
200K SF$400K–$700K
500K SF$1M–$1.75M
Every option includes: All 18 BidLight modules, model export history with diffs, 3D markup & shared collaboration, BIM issue tracker, team contribution tracking, quality gate workflow, AI predictive issue flagging, cross-project analytics, API access for ERP/PM tools, dedicated success manager, and 2-week team certification.
Annual & Multi-Year — By Engagement Model
BidLight Platform
Your team, our system
$25,000/mo
$300K/year · Annual or multi-year
Your BIM team runs the platform. Full access to all 18 modules — export history, diffs, 3D markup, issue tracking, team analytics, quality gate. We provide onboarding, certification, and ongoing technical support.
Unlimited users · Unlimited projects
2-week team certification included
Dedicated support channel
Annual: $25,000/mo · 3-year: $20,000/mo
BidLight Platform + Oversight
Your team, our system, our quality control
$35,000/mo
$420K/year · Annual or multi-year
Your BIM team handles the day-to-day. Our team sets up workflows, configures quality gates, runs monthly audits, and joins weekly coordination. We catch what your team misses.
Everything in Platform, plus:
Workflow & quality gate configuration
Monthly model health audits
Weekly coordination call participation
Annual: $35,000/mo · 3-year: $28,000/mo
FULL SERVICE
BidLight Managed
Our team, our system, full delivery
$50,000/mo
$600K/year · Annual or multi-year
BidLight runs your BIM coordination end-to-end. We manage exports, track diffs, flag issues, run coordination, deliver reports, and manage your as-built documentation. You get the outcomes without staffing or training anyone.
Everything in Platform + Oversight, plus:
Full BIM coordination management
Export & diff management
Issue resolution tracking & reporting
As-built documentation management
Annual: $50,000/mo · 3-year: $40,000/mo
The math: A GC running 3 active DC projects carries $800K–$1.5M/year in BIM coordination costs — coordination meetings, field rework from missed clashes, BIM labor across trades. BidLight at $200K–$600K per project delivers 3–7× ROI. The cost is a project line item — billable, recoverable, and already in a budget category your owners recognize.
Deploy This Week
| Step | What Happens | Timeline |
|---|
| 1. Demo | 30-minute live walkthrough on your own Revit model — not slides, not a demo environment | 30 min |
| 2. Pilot | Deploy on one active project — your team, your model, full onboarding support | Same day |
| 3. Certify | 2-week accelerated training — 20 hours, all modules | 2 weeks |
| 4. Rollout | Enterprise deployment across all projects + teams | 30 days |
See Who Built What, When, and Why.
Every GC and sub running BIM coordination without this visibility is paying for it — in rework, in delays, in coordination meetings that produce nothing, and in field clashes that should have been caught in the model.
