The sequence

Each phase in order, named as the customer names it.

The part

What it is

Order matters more than completeness. A list of six phases in the right sequence is more useful than twelve in no particular order, because the sequence is what makes timing answerable.

Phases overlap in practice and that is worth recording rather than smoothing away. Where two run in parallel, decisions taken in one constrain the other.

The smallest level

The attributes it carries

Each attribute is one of the framework’s shared types. What a date is, and how it is written, is defined once for the whole model — the note here says what it means in this particular place.

Phase
The customer’s own name for it.
Text shared type
Position
Where it sits in the sequence, so the process can be drawn.
Number shared type
Typical length
How long it usually runs, which is what makes planning possible.
Duration shared type
Segment
Whose process this is. Different segments run different versions of the same industry process.
Reference shared type