five-d-dashboard
/five-d-dashboard
Turn an IFC model, a cost-loaded schedule (P6 XER or MS Project XML) and 4D links into one checked offline 5D HTML dashboard showing money on every element and month. Use when someone wants 5D, cost on a BIM model, a cash-flow view linked to a model, or BC3/BOQ money placed on elements.
- Author
- hamzaabduljabbar ↗
- Repository
- autoConst-5d-dashboard ↗
- Licence
- MIT
- Last repository change
- 05.11.2026
Assessment and security
- Files in this package
- 23
- Scripts
- 13
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 13 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/bc3_read.py, scripts/build_viewer.py, scripts/ifc_export.py, scripts/job_check.py, scripts/line_brief.py, scripts/link_real.py, scripts/merge_models.py, scripts/plan_from_answers.py
What it does and when to use it
Turn an IFC model, a cost-loaded schedule (P6 XER or MS Project XML) and 4D links into one checked offline 5D HTML dashboard showing money on every element and month. Use when someone wants 5D, cost on a BIM model, a cash-flow view linked to a model, or BC3/BOQ money placed on elements.
Original author description
Turn an IFC model, a cost-loaded schedule (P6 XER or MS Project XML) and 4D links into one checked offline 5D HTML dashboard showing money on every element and month. Use when someone wants 5D, cost on a BIM model, a cash-flow view linked to a model, or BC3/BOQ money placed on elements.
How it works
- Steps
- Rules
- What is proven
SKILL.md preview
--- name: five-d-dashboard description: Turn an IFC model, a cost-loaded schedule (P6 XER or MS Project XML) and 4D links into one checked offline 5D HTML dashboard showing money on every element and month. Use when someone wants 5D, cost on a BIM model, a cash-flow view linked to a model, or BC3/BOQ money placed on elements. --- # 5D dashboard Inputs: an IFC model; a cost-loaded schedule (`.xer` or MS Project `.xml`); a links CSV of activity to elements. BOQ lines come from the schedule's costs. A BC3 budget can be read with `scripts/bc3_read.py budget.bc3 outputs/<job>/`. ## Steps 1. Check the three files belong to one job. Compare element counts and quantities with the budget before going further. Tell the user if they do not. 2. Check timing before anything else. Dates come from the planner, never from Claude. - **Real activity schedule:** use it. Ask only about gaps, such as activities with no dates. - **Monthly or no schedule:** `run.py` stops. Do not invent a plan. Run `py scripts/plan_from_answers.py lines.csv answers.csv --questions`, then ask the planner at most six short questions: is this the current approved programme and what are its start and finish; what comes first and what overlaps; dates for each package, biggest value first; how site overheads spread; whether big items are paid when ordered or installed; whether a target curve or payment schedule exists. Put the dates in `answers.csv`, run the script again with `--xer`, show the planner the draft monthly curve, apply corrections, then run `run.py` with `--timing answers`. - **Estimated dates:** only when the user explicitly asks. Use `--timing estimated`. The dashboard then says it is not for cash-flow forecasting. 3. First run, no line map. Pass every discipline model in one go (structure, architecture, MEP); they are exported into `<out>/models/` and joined. Leave rebar geometry out with `--skip IfcReinforcingBar` when the BOQ prices rebar by weight, and set `--currency` (R$, AED, £): `py scripts/run.py structure.ifc architecture.ifc --skip IfcReinforcingBar --schedule loaded.xer --links links.csv --out outputs/<job> --project "Name"` Add `--boq-map`, `--elements`, `--glossary`, `--project-id` where the job needs them. 4. Claude matching. Keyword rules are only a fallback and were poor on real wording. Run `py scripts/line_brief.py` (see its header), read every line, and write `line_map.csv` with columns `line,activity,groups,reason`. Use `*` for all, `NONE` for no model element. Group names must match exactly: the build stops on a group the model does not have. Structural marks (beams, columns, piles) are one group each, so use `*` on structural activities rather than listing marks. Give a reason on every row. Never guess a line: mark it NONE and list it for the user. 5. Rerun step 3 with `--line-map line_map.csv`. Add `--quantities lines.csv` (line, qty, unit) whenever the BOQ has quantities: the job check then compares every matched line with what the model measures. **Job check.** Every build writes `job_check.md`: quantity fit, money on activities with no elements, services with no model, coded names, unpriced elements, date source. Before showing the dashboard: - Read it. Fix what the files already answer: a line whose model quantity is 10x the BOQ is matched too broadly, so narrow its groups; two-sided formwork at x0.5 is expected. - Ask the user at most five questions, biggest money first: which elements a line covers, what a code means (ask for the finishes or wall-type schedule), whether an activity with no elements builds anything, whether MEP models exist (add them with `scripts/merge_models.py`). - Apply the answers, rebuild, and report the before and after of each check. Never hide a REVIEW. - Append a short note to `outputs/<job>/run_notes.md`: what did not fit and how it was settled. If the same issue appears on two jobs, tell the user it belongs in the skill. 6. Open `outputs/<job>/5d.html` and report its Checks tab: money outside the model, undated activities, dead links. ## Rules - `run.py` stops if money does not reconcile with the schedule. Never bypass this; fix the cause. - A blind AI-written plan ran 30 points behind a contractor's real curve at month 5. Never present estimated dates as a forecast. - Say that costs on elements are estimated shares unless the budget's measurements name the elements. - Large models: exports can take 30+ minutes. Models heavy in rebar take longer. - Keep client files private. Dashboards built from licensed sample files stay private unless the licence allows sharing. ## What is proven Job check: model within 20% of the BOQ quantity for 94% of matched money on a building whose budget was measured from its model. On a real tender priced from a standard design it was 51% after the end-to-end run: most misses were lines matched to a whole wall or floor group when the work covers only part of it, which is what the questions are for. Quantities come from the model's own figures (base or layer quantities) when it has them; the mesh is the fallback. Blind tests put 91-96% of money on the right line and element on one building and 99.3% on a viaduct (an easy case). Concrete volumes came within 0.2% of the QS. It has NOT been tested on one real job with a model, a real budget and a real activity-level schedule together. State this limit whenever accuracy is claimed. Results are a checked draft for human review, not a bid figure.
Files in this package (23)
- .gitignore 1 KB
- LICENSE 2 KB
- README.md 4 KB
- SKILL.md 5 KB
- requirements.txt 1 KB
- scripts/bc3_read.py 4 KB
- scripts/build_viewer.py 1 KB
- scripts/glossary_nl.csv 3 KB
- scripts/ifc_export.py 6 KB
- scripts/job_check.py 8 KB
- scripts/line_brief.py 2 KB
- scripts/link_real.py 15 KB
- scripts/merge_models.py 2 KB
- scripts/plan_from_answers.py 3 KB
- scripts/price.py 6 KB
- scripts/rates_demo.csv 3 KB
- scripts/run.py 4 KB
- scripts/scope_demo.csv 1 KB
- scripts/verify.py 4 KB
- scripts/viewer_template.html 30 KB
- scripts/vendor/OrbitControls.js 26 KB
- scripts/vendor/THIRD_PARTY.md 1 KB
- scripts/vendor/three.min.js 594 KB
Versions
The database has no other skills named five-d-dashboard.
Database snapshot: 13.11.2026 · package version 4ba184521521 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90oce-scheduling-4d5d
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. - 90oce-bim-takeoff
CAD/BIM takeoff in OpenConstructionERP: upload Revit/IFC/DWG/DGN models, browse elements, bulk-link them to BOQ lines, measure DWG drawings and PDF plans, and push quantities into the estimate. Use for any model-based quantification workflow. - 82p6-revit-4d
Link a Primavera P6 schedule (XER) to the elements of the open Revit model and write it in as 4D - P6_Task_ID, activity, start/finish, week and month on every element, plus coloured "build by month" and "as of <date>" 3D views and two schedules. Claude reads both sides, maps… - 100threejs-impl-ifc-viewer
Use when loading and viewing IFC/BIM models in a Three.js scene. Prevents the common mistake of using deprecated web-ifc-three, ignoring AGPL-3.0 license implications, or loading large IFC files without streaming. Covers web-ifc (MIT), @thatopen/components (AGPL-3.0), IFC… - 95boq-schedule
Turn a priced Bill of Quantities (BOQ) into a first-draft, cost-loaded construction programme that imports into Primavera P6 (XER) - activities by trade and location, logic learnt from 73 real P6 schedules, the BOQ money and quantity on every activity. Claude reads every BOQ… - 95p6-cost-loader
Load a Bill of Quantities (BOQ) into a Primavera P6 schedule as cost-loaded activity expenses - no typing BOQ lines into P6 by hand. Reads a BOQ workbook (or a folder of division files) and a P6 XER export, matches every BOQ line to the right activity with HIGH/MEDIUM/LOW…