4D Scheduling & 5D Cost Model in OpenConstructionERP

SkillProductivity

4D scheduling and 5D cost modelling in OpenConstructionERP: build task schedules, link tasks to BIM elements and BOQ lines, roll up the cost model over time, and export Gantt/sequence views. Use for schedule-cost integration workflows.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the 4D Scheduling & 5D Cost Model in OpenConstructionERP skill

What this skill tells your AI

The instructions your AI receives, as published by datadrivenconstruction/ddc_skills_for_ai_agents_in_construction in 6_OpenConstructionERP/oce-scheduling-4d5d/SKILL.md and read by ahel’s review.

Concepts

  • 4D = schedule + BIM: every task can reference BIM elements so the sequence is visual.
  • 5D = schedule + cost: cost roll-ups per task/phase from linked BOQ lines.
  • Both live on the same task graph — one source of truth for time and money.

Workflow

  1. Build the task graph — tasks, durations, dependencies (FS/SS/FF), milestones, critical path.
  2. Link BIM elements to tasks (from oce-bim-takeoff) — visual sequencing and progress colouring.
  3. Link BOQ lines to tasks (from oce-estimate-boq) — each task carries its direct cost.
  4. Roll up — phase/project totals, cash-flow curves (cost over time), SPI/CPI views.
  5. Track — daily diary entries and punch items update actuals; variance reports compare plan vs actual.

Key endpoints

  • tasks: create/update, dependencies, assignees, status board
  • scheduling: timeline data for the Gantt, milestone markers
  • cost model: GET-side roll-ups per task/phase; export to XLSX/PDF reports

Integration rules

  • One region/currency per project — the cost model never blends currencies.
  • Quantity changes from BIM re-link update BOQ line quantities, which update the cost model in turn.
  • Re-validate the BOQ after bulk changes; schedule conflicts surface in the timeline.

Best practices

  1. Keep dependencies explicit — the critical path is only as good as the logic.
  2. Use milestones for payments/tender gates, not for activity progress.
  3. Compare plan vs actual weekly; adjust the forecast, not history.
  4. For multi-project portfolios, roll up by project and by currency group (never blended).

Signals

GitHub stars
308
Forks
79
Last commit
Aug 2026
Advanced
Catalog kind
skill
Gateway key
oce-scheduling-4d5d
Source
github.com/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction