Skip to main content

The model moves when the schedule moves.

4D Scheduling puts your live Verian schedule beside the project's 3D model, in IFC (Industry Foundation Classes): no export, no re-sync, no second critical path. Play it by date, color it by what the site has reported, and compare it with a scenario or the baseline.

Runs in the browser · Nothing to install · Built for plant-scale models

A depicted 3D model of Northgate Terminal, played from the start of the project to the data date, 4 October 2027.

NORTHGATE TERMINAL · NGT-2 · SCHEDULE REV 13IFC MODEL · 3,601 OBJECTS · WEEK 1 → DATA DATE

Not a copy of the schedule. The schedule.

4D BIM work usually starts from an export that is out of date by the next status update. 4D Scheduling opens the live Verian schedule instead: the same activities, logic and critical path your planners work in, with the scheduler's full toolbar. Drag the focus line in the Gantt to any day and the model follows, or play the job at one, seven, fourteen or thirty days a second.

  1. Focus line: drag it to any day
  2. Colors: build sequence, progress, zones, what moved, late or early
  3. Split view: the live schedule beside a scenario
  4. Viewpoints: reopen exactly what a colleague saw
FIG. 01 —The 4D Workspace, on a depicted project.

Link thousands of objects by rule, not by clicking.

Open an IFC 2x3, IFC4 or IFC4x3 model and 4D Scheduling reads what the file carries: property sets, quantities, types, materials, classifications and systems. Link objects to activities with rules you write, by zone, class or property, or by hand where judgment matters. Each link carries a profile, so construction sequencing reads the way the job is built: new steel rises from the ground, demolished plant comes down, and scaffolding stands while its task runs.

Link rule · by property
ClassIfcPipeSegment
Pset.Area= “A”
Tagstarts “SP-22”
A-1188 Spool install, Area A
Profile: Install · rises bottom to top
312 objects linkedL. Ferreira · 2 min ago
Appearance profiles
FIG. 02 —Five appearance profiles, and one model in six colorings.
Color the model byBuild sequenceProgress statusRegister progressZones — level or tradeWhat moved — against a scenarioLate / early

Synchronized at the data date.

The Digital Twin Consortium describes a digital twin as a virtual representation of real-world entities and processes, “synchronized at a specified frequency and fidelity.” 4D Scheduling is a construction-phase twin in that sense: a twin of the build, not of the finished building. Its frequency is your status cycle. Each time the schedule is statused or a progress register is imported, the model takes the new state, and each import is kept, so a past week can be replayed as it was reported.

What it is

  • Bound to the live Verian schedule
  • Updated from schedule actuals and progress registers, at the data date
  • Replayable from the imports you keep
  • Compared with baselines and scenarios
  • Pushed back to the schedule after approval, and reversible

On a capital project, progress is agreed in registers and status updates. That is where this twin is connected.

REGISTER WK 3606 SEP 2027
T-103 · SHELL COURSE 3/9 · BEING BUILT
NOT OBSERVED BETWEEN UPDATES
REGISTER WK 3820 SEP 2027
T-103 · SHELL COURSE 4/9 · BEING BUILT
NOT OBSERVED BETWEEN UPDATES
REGISTER WK 4004 OCT 2027
T-103 · SHELL COURSE 5/9 · BEING BUILT
FIG. 03 —Tank T-103 at three register imports. The model is not observed between updates.

Definition: Digital Twin Consortium, 2020.

The spreadsheet you already keep becomes the picture.

Drop in the weekly Excel or CSV register your contractor already sends and map its columns once, without code. Each row is matched to its model object, exact matches first and looser ones after, and the doubtful matches go to a person. Your construction sequence and its weights turn rows into earned progress. A row that makes no sense, like a spool installed before it was welded, is flagged and kept, not dropped. This is model-based progress tracking without re-keying the register.

  1. 01Map

    Map the columns once. “YES” means done; “95%” means ninety-five percent.

  2. 02Match

    Each row finds its object in the model. The doubtful matches wait for a person.

  3. 03Show

    Your rules of credit turn rows into earned progress. One click hides what is not yet complete: the view for a client walk.

Weekly register · wk 40
Tag
Area
Welded
Installed
SP-2208
A
YES
YES
SP-2209
A
YES
YES
SP-2210
A
NO
YES
SP-2211
A
YES
NO
SP-2287
B
YES
—
SP-2290
B
NO
NO
  • 1,151 rows matched to the model
  • 33 for a person to check
  • SP-2210 installed before welded: flagged
FIG. 03 —A weekly piping register, matched to the model.

In register mode, each color points back to a row, an import and a date.

The schedule changes when a person approves it.

When the register says work has moved, a planner prepares the push and sees each activity's new start, finish and remaining duration, with the reason, before anything is written. Someone with the authority approves it. It is applied through the schedule's own update rules, rolls back if it fails, and can be rolled back later. Pushing actuals takes two permissions: 4D push and schedule update.

Dates from real productivity, with the working shown.

After a status update, the remaining work is reforecast from what your crews have actually achieved: recent work, the whole history, comparable work or the plan. Each row shows how it was worked out. The dates come from arithmetic you can check, not from a language model. Where the evidence is thin, the row says so, and an override stays on the record.

Push to scheduleRegister wk 40
  1. Prepare pushL. Ferreira · 06 OCT 14:02
  2. Preview12 activities · 3 finish dates move
    A-1188Spool install, Area A18 OCT+3 d
    A-1040PR-1 erection, bents 5–829 OCT+2 d
    A-1310T-103 erection19 NOV+2 d
  3. ApproveS. Okafor · schedule authority
    ApproveEditRejectAwaiting approval
  4. Applied · Rev 15·Roll back
Pushing actuals needs two rights:4D push ✓Schedule update ✓
Reforecast the remaining workData date 04 OCT 2027 · recent window 30 d
  • A-1188
    Spool install, Area A
    MEDIUM
    Forecast finish
    18 OCT 2027
    Rate
    0.85 m/h
    Remaining
    120 m
    How it was worked out · remaining 120 m ÷ 0.85 m/h = 141.2 h · last 30 days: 340 m over 400 working hours
  • A-1040
    PR-1 erection, bents 5–8
    HIGH
    Forecast finish
    29 OCT 2027
    Rate
    1 bent / 5.5 d
    Remaining
    3 bents
    How it was worked out · Recent work · last 30 days: 5 bents over 27 working days
  • A-1210
    T-102 valve set & hook-up
    LOW
    Forecast finish
    12 NOV 2027
    Rate
    —
    Remaining
    14 d planned
    How it was worked out · The plan · No productivity to go on
Methods: Recent work · Whole history · Comparable work · The plan · Set by handOverrides stay on the record
FIG. 04 —A push awaiting approval, and a reforecast with its working.

Two plans, one camera. The difference in days.

Split the view: the live schedule on one side, a scenario or the baseline on the other, seen from the same viewpoint. Color by what moved and the shifted work lights up where it sits, while the readout states the consequence in days. Plan against actual, or one recovery against another, becomes a picture and a number.

LIVE SCHEDULE · REV 13Scenario finishes 6 days earlierSCENARIO S-3
FIG. 06 —The live schedule against scenario S-3, and the baseline against the live schedule.
Date shown in the model04 OCT 2027 · WK 40
DATA DATE 04 OCT
REPORTEDPLANNED

A whole team in one model. A film for everyone else.

Planners, BIM leads and construction managers work in the same 4D workspace. A colleague's saved work is not silently overwritten, saved changes show up for colleagues as they are made, and each change is kept in the project's history. When the audience is a board, a client or a claims team, export a film: MP4 or WebM, frame-exact, up to 2160p, planned beside built with the Gantt in frame. It runs in a browser, with nothing to install.

PRESET · COMPLETED · HIDE WHAT IS NOT DONEVIEWPOINT · TANK FARM, NORTH
DATA DATE · 04 OCT 2027 · WK 402,311 BUILT · 86 BEING BUILT · 1,204 HIDDEN
FILM · SIDE BY SIDE · 1920 × 1080 · 25 FPS · FRAME-EXACTWK 33 → WK 40
WK 33
WK 35
WK 37
WK 38
WK 40
DraftTeams & emailPresentationArchive 4K
Side by side — Planned against built, sharing one camera.
FIG. 07 —Who is here, and a film of the plan beside what was built.

Bring one model and one schedule.

An IFC model and the schedule you already run are enough to start. In a working session we link them with your planners and play your project back to you.