Home/AI Era/ERP System
Enterprise · Construction Ops

ERP System

A modular ERP for project-driven teams — covering projects, packages, sheets, submittals, resource allocation, and analytics. Designed and prototyped end-to-end with Claude AI, shipped as fully interactive HTML prototypes.

Role
Product Designer
Built With
Claude AI
Screens
47+
Year
2026

The Approach

Process · 04 Stages

This ERP was built for a firm specialising in BIM services — a complex, highly specific operation. To get it right, I followed a deliberate four-stage process: gather, systemise, generate, and refine.

01
Stage 01

Ideation

Gathered every requirement directly from the stakeholders — workflows, edge cases, BIM-specific terminology — and consolidated everything into a single living markdown brief.

02
Stage 02

Design System

Built a generic, brand-aligned design system from scratch — tokens, typography, components, states — so every screen that followed would feel cohesive and on-brand.

03
Stage 03

Screen Generation

Used the brief and the design system together to generate the full breadth of screens — projects, packages, sheets, submittals, resourcing, analytics — as interactive HTML prototypes.

04
Stage 04

Refinement

Walked through each screen one by one with the team, surfaced issues, refined flows, fixed inconsistencies, and tightened the visual language until every view was production-ready.

The Business Logic

Overview · Users · Impact

JES ERP manages the full lifecycle of BIM projects for a firm split into two departments — Architecture and MEP — from project setup through task execution, QC, submittals and analytics. It supports two business models in parallel: Lumpsum (fixed-scope delivery with budgets) and Resourcing (skilled workers billed by hours consumed per client stakeholder).

The Problem

Fragmented BIM operations

The firm was running complex, multi-department BIM projects across spreadsheets and siloed tools — no single source of truth for packages, sheets, tasks, reviews, budgets or time. Managers couldn't see utilisation, PLs couldn't trace review time, and submittals / change orders lived outside the system entirely.

The Solution

One table-driven ERP

Every screen is built on one primitive — the data table in Read, Edit, or Input mode — wrapped by seven templates (List, Detail, Dashboard, Form, Modal, Wizard, Kanban). A unified status engine drives projects, tasks, sheets, packages, change orders and submittals through shared lifecycles, visible to each role through row-level security.

Who It's For

A five-role execution chain

The production workflow flows top-down through five roles — Operations Manager → Project Manager → Package Lead → Senior Modeler → Modeler — with a sixth Admin role running system-wide configuration. Each role sees a filtered slice of the same data through a hierarchical RLS model.

The Impact

End-to-end accountability

Biometric check-in/out, per-package coordination time, PL review rollups, planned-vs-actual efficiency, workforce utilisation dashboards and a full submittal + change order pipeline put the entire department's delivery, budget and people metrics in one place — so OMs can run the department, PMs can run projects, and execution roles know exactly what's on their plate.

Five user types · one workflow

Project execution chain
01
Operations Manager
Department

Owns one department end-to-end. Creates projects, monitors utilisation, manages resource allocation, runs submittals and change orders, reviews timesheets across all roles in the department.

02
Project Manager
Projects

Owns individual projects — runs the planning wizard, creates packages and tasks, builds teams, manages weekly resource allocation, handles client contacts and submittals, reviews delivery.

03
Package Lead
Packages

Runs a work package — allocates unassigned tasks, reviews modeling and sheet work, logs BIM coordination time, manages team check-outs, flags rework and drafts change orders.

04
Senior Modeler
Team

Dual role — executes tasks personally while supervising and reviewing Modelers in their team. Handles assignment within the team, self-QC, and internal review of modeling work.

05
Modeler
Self

The execution layer — picks up assigned modeling and sheet tasks, runs self-QC, logs daily time via check-out, and tracks personal efficiency and rework metrics.

+
Admin
System

Superuser running both departments — adds users, configures the calendar, holidays and project settings, manages the BIM library, and serves as the CEO-level cross-department view.

2
Departments
Architecture · MEP
6
Roles
5 execution + 1 admin
10
State machines
projects · tasks · sheets · CO
7
Table templates
one primitive, infinite views
2
Business models
Lumpsum · Resourcing

All Screens

45 prototypes · 6 groups · click to open in canvas
01

Projects & Planning

Project list, detail, creation flow and the planning wizard for the OM team.

6 screens
02

Packages & Sheets

How packages, sheet groups and individual sheets are organised inside every BIM project.

8 screens
03

Tasks & Checkout

The daily core of the ERP — checkout flows for every role plus task allocation and BIM coordination.

13 screens
04

Submittals & Feedback

End-to-end submittal lifecycle plus change requests, descope reviews and feedback loops.

8 screens
05

Resourcing & People

Resource allocation grid, user management and client contact directory.

6 screens
06

System & Analytics

System-wide configuration, calendar, audit trail and the analytics hub for leadership.

4 screens