How PHASI models structured projects
A project in PHASI starts with what is being delivered. Teams can model assemblies, zones, assets, documents, packages, scopes, service deliverables, supplier packages or other project items.
Each item then moves through reusable work phases on a timeline. These phases can represent requirements, engineering, procurement, fabrication, construction, review, testing, approval, handover or any custom workflow step.
Because phase bars are attached to real project items, completion can be calculated from the model itself. PHASI uses category weights and completed relevant phases to create deliverable-based Percent of Completion instead of a detached manual percentage.
Core features
Project Structure
Build a clear structure of what is being delivered: assemblies, zones, documents, assets, packages, scopes or work items.
Phase Timeline
Plan execution with reusable work phases such as requirements, engineering, procurement, construction, manufacturing, review, testing or approval.
Percent of Completion
Measure progress from project structure, category weights and completed relevant phases.
Timeline Comments
Keep questions, decisions and replies attached to the exact item, phase, owner and date.
How PHASI calculates model-based progress
Percent of Completion in PHASI is calculated from the planning model: project structure, relevant phase bars, category weights and completed work. A completion value is not just a separate opinion field; it is derived from phases that actually exist for each deliverable or work item.
Teams define category weights for the project, such as Requirements, Engineering, Procurement, Construction, Manufacturing, Testing or Approval. The weight for each category is distributed across relevant phases in that category, then rolled up through items, parent items and the top-level project structure.
This keeps progress configurable, but grounded in the plan project controllers maintain. The more accurately the team maintains the structure and timeline, the more accurately PHASI reflects the project’s current state.
The planning model
- 1 Structure
Define the deliverable structure
Create the hierarchy of what belongs to the project: deliverables, components, modules, buildings, zones, documents, packages, assets, scopes or service items.
- 2 Phases
Configure reusable work phases
Create phase categories that describe how work moves from start to completion, such as requirements, engineering, procurement, construction, manufacturing, review, testing, approval or handover.
- 3 Timeline
Schedule phases on the timeline
Place phase bars on the timeline for each project item so teams can see when work is planned, where phases overlap and how the sequence develops.
- 4 Progress
Track model-based completion
Measure progress through relevant phase completion and project-specific category weights at item, parent item and project level.
Adapt to engineering and project-controls vocabularies
PHASI does not require one fixed industry vocabulary. A project item can be an assembly, zone, work package, document, asset, service item, supplier package, scope or maintenance asset. The team defines the vocabulary; PHASI provides the planning model.