From work to what it produces
A rail-project example puts a work/process hierarchy beside a product hierarchy. Expand a branch, then select an item to follow its explicit “produces” relationship across the two trees. The structures organise different views of the same example.
Illustrative legacy dataset. HS2 place names and all original sample amounts, progress values and statuses are retained for exploring the model. They are unverified teaching inputs, with no reliable reporting date. This is not a current HS2 dashboard, approved baseline or source of project facts.
How to use · terminology · limits
Choose Overall Project or a phase to change the KPI cards and sample narrative. The trees continue to show the whole example. Expand branches individually, or use Expand all. Hover or focus an item to preview its linked counterpart; select it to keep the highlight, reveal linked branches and open its details. Press Escape or Close to dismiss the details.
The left tree is an illustrative process/work hierarchy. The old app called it a WBS, but a WBS is normally organised around deliverables; see PMI’s explanation of WBS practice. The right tree organises products and supporting outputs. A tree’s parent/child relation is distinct from a cross-tree “produces” link.
Links are explicitly supplied, not inferred from matching names. Some nodes have no direct link; that means “not modelled”, not “no real output”. Progress and cost are supplied separately at each level and are not rolled up, reconciled, earned value measures or forecasts. Status colours are accompanied by text. The legacy phase narratives below are preserved as unverified sample descriptions.
Sample narrative
Select a work item or product to inspect its links.
Work / process hierarchy
What work is organised here?
Product / output hierarchy
What does the work produce?