Before You Adopt a PMIS, Fix the Master Codes — Why WBS·CBS Standardization Decides Success
1. What Master Codes Are — A Project's Common Language
A large project moves through many departments, subcontractors, and systems at once. If they call the same work by different names and numbers, the data never merges. Master codes are the common language that prevents this. Three axes matter.
| Code structure | What it classifies |
|---|---|
| WBS (Work Breakdown Structure) | 'What work' — decomposes the work into a hierarchy |
| CBS (Cost Breakdown Structure) | 'What it costs' — classifies cost by item |
| RBS (Resource Breakdown Structure) | 'What it takes' — labor, equipment, materials |
Schedule (P6) runs on WBS; cost (Unifier) runs on CBS. Only when the two are mapped to each other can you see "how much did this activity cost" in one place. Master codes are the reference point for that mapping.
2. Why It Comes Before the System
The most common failure pattern is the wrong order. Install the system first and try to fix codes later, and the data already entered is inconsistent — so it collapses at the integration stage. McKinsey finds large construction projects run ~20% longer than planned and up to 80% over budget, and scattered data is at the root. When codes don't line up, everything downstream breaks.
- No integration — schedule and cost can't be viewed in one model.
- EVM breaks — no basis to compute earned value (EV), so CPI/SPI become fiction.
- Manual roll-ups — different codes per department, reconciled by hand at month-end.
3. The Cost of a Bad Code Structure
A code structure fails if it's too granular and if it's too coarse. Too fine, and field input burden grows until the data is empty; too simple, and it can't be analyzed for decisions. The key is the balance between enterability and analyzability.
Once a code structure sets, it's hard to change. So designing the standard first and putting the system on top of it is far cheaper than improvising one mid-project.
4. How Standardization Works — Four Stages
| Stage | Core |
|---|---|
| ① Assess | Map current WBS·CBS·RBS, data usage and gaps |
| ② Design | Define the standard code system — including schedule·cost·contract mapping |
| ③ Cleanse & migrate | Cleanse existing data, migrate to the new system |
| ④ Embed | Prevent input/output human error; establish code governance |
5. Takeaway
PMIS and EVM run on data, not tools — and the skeleton of that data is the master code. If you're evaluating a new system, the first question isn't "which product" but "can our code structure withstand integration?"
DT Solution assesses, designs, migrates, and embeds WBS·CBS·RBS code structures, and builds PMIS (Primavera Unifier·P6·Aconex) on top. With standardization know-how proven on large EPC and shipbuilding sites, we design a code structure right-sized for you. Talk to us.