skip to content
← cd ../projects

case study

EverythingPM

Full stack engineer: platform architecture, API, data model and web app

problem
Construction teams plan in Primavera P6, model in BIM tools and track cost and progress in spreadsheets. Changes in one never show their effect on the others, re-importing a revised programme can duplicate cost, and approved baselines get overwritten.
outcome
EPPM, an early-access platform where a P6 programme, IFC model, £370m cost-loaded budget, site progress, risks and documents for a demo project sit on one data model, with dashboards whose every figure opens the records behind it.
the platform
  • Programme: Primavera P6 (XER) import with validation; each new revision is compared with the current one (added, deleted and moved activities, finish variance in days) and reviewed before publishing. Approved baselines, restore of earlier revisions and a Gantt view with critical and near-critical activities.
  • BIM & 4D: IFC upload with versioning and a browser-based 3D viewer. Model elements link to activities by rule (storey, type or a property holding the Activity ID) or by hand, and are coloured by delivery status at any date.
  • Cost & earned value: approved control budget, cost-loaded programmes, commitments and actuals from Excel or CSV matched by reference so re-imports update instead of duplicating, reconciliation warnings, and PV, EV, AC, CPI, SPI and estimate at completion.
  • Site progress: quantities, labour hours and photo evidence from site; a second person approves each submission before it changes the official % complete and earned value.
  • Risk & change: risks, early warnings, compensation events, RFIs and delay events linked to the activities they affect; cost and time estimates are recorded without touching the approved budget or programme.
  • Documents: ISO 19650 register with revision and suitability codes, where uploading is kept separate from authorising, linked to activities and model elements.
  • Reporting: portfolio and project dashboards filterable by contractor or WBS, where every figure opens the records behind it, plus monthly snapshots and an Activity 360 page that brings logic, dates, cost, progress, model elements, risks and documents together.
  • Access: ten project roles from director to subcontractor, organisation-level isolation, a tamper-evident audit trail and a one-click demo project for new accounts.
ownership
  • Designed the multi-tenant data model and built the NestJS API, Next.js app and all import pipelines, with end-to-end tests for each of the specification’s acceptance criteria.
  • Built Primavera P6 (XER) import with revision comparison before publishing, approved baselines, a Gantt view and restore of earlier revisions.
  • Built cost loading and earned value, site progress with photo evidence and approval, a risk and delay-event register, an ISO 19650 document register and an IFC model viewer linked to activities.
architecture
  • Postgres row-level security isolates each organisation in the database itself; the API runs every request as a restricted role with the user and organisation set.
  • Programme revisions are immutable and activities keep stable IDs across revisions (matched by P6 GUID, then Activity ID), so baselines can never be overwritten by an import.
  • Cost is held as integer minor units and read from a single programme revision, so repeated imports cannot double-count; the duplicate-cost acceptance test keeps a £370m budget intact.
  • Every dashboard figure is one SQL condition over a shared scoped activity set, so a filtered number and its drill-through list cannot disagree.
  • Hash-chained, append-only audit trail; IFC parsed with web-ifc on the server and rendered with Three.js in the browser.
trade-offs
  • Modular monolith (one NestJS API) instead of microservices, to keep a small team fast while module boundaries stay clean.
  • Supabase for Postgres, auth and storage instead of Azure plus a separate identity provider: much lower running cost and setup, with standard Postgres underneath for a later move.
  • File-based P6 and IFC import first rather than live integrations, matching what each tool reliably supports today.
  • Construction status colouring per date in the 3D viewer before full 4D playback, which is planned for the next phase.
stack
TypeScript · Next.js · NestJS · PostgreSQL · Supabase · web-ifc · Three.js · Railway · Vercel