Rules of credit define how much progress a package earns, and on an AWP project they are set per package type and kept objective. Engineering earns credit only when documents are issued for construction, procurement earns it through weighted phases that end at site receipt, and construction earns it when installation work packages close. Each rule is fixed in the procedure, so the same number means the same thing to everyone who reads it.
Credit by Package Type
| Package | How progress is earned |
|---|---|
| Engineering work package (EWP) | Documents issued for construction over total documents in the package. Binary per document, counted against the full register including placeholders |
| Vendor and fabrication engineering (VEWP, FEWP) | Documents received and approved over total |
| Procurement work package (PWP) | Weighted phases across the lifecycle, for example engineering 20%, procurement 25%, fabrication 40%, inspection 5%, and delivery to site 10%. Complete at 100% receipt on site with the purchase order closed |
| Fabrication shop packages | Measurable milestones, from released and material complete through cutting, assembly, welding, and QC to ready to ship |
| Installation work package (IWP) | Complete when scope is executed, QC verified, and closure completed |
| Construction work package (CWP) | Complete when 100% of its IWPs are closed, the punch walkdown is done, and quality documentation is delivered |
Why the Rules Are Binary
Partial credit gets gamed, mostly through optimism, like a drawing that sits at 92% for three months. A document is issued for construction or it is not, and a PWP has 100% receipt or it does not. That is what lets a forecast built on package progress be trusted. Project controls explains how the rules fit the wider controls system.
What the Rules Make Visible
- Skylines. Package status plotted against schedule dates and linked to the Level 3 schedule shows when the document register and the schedule disagree
- Readiness over activity. Engineering readiness is measured by released complete packages and material on site, and model review percentages stay out of it
- One published number. Internal forecasting curves are fine, and only the rule-based number is reported as progress
Construction reporting covers how these figures become weekly reports.
How openAWP Calculates It
openAWP records weighted milestones at the tag or piecemark, with a separate structure per scope type, and rolls progress up automatically through the package hierarchy a project defines. The model colors by percent complete or by a single milestone, and Power BI reports read the same figures.
Our project controls team sets up package-based progress rules and the schedule they report against.