Resources Design guide

Designing hierarchies that survive reorganisations.

Six rules for hierarchies that keep reporting, planning and approvals consistent through a reorganisation, with examples from the catalogue.

THE SIX RULES01Name the levels before the nodes02One live version, dated03Validate the draft against facts04Keep alternate trees separate05Inherited attributes on nodes06Generate the crosswalk
The six rules

Name the levels before the nodesRegion, country, site: a hierarchy with named levels can be validated; one with unnamed levels is a list with indents.
Examples

HierarchyLevelsThe reorganisation it survives
Salesdivision → family → line → producta product line moves between families; last quarter rolls up the old way
Cost centrecontrolling area → area → department → cost centrea department merges; HR, the ERP and planning read the version on the same day
Legalgroup → holding → entity → branchan acquisition; ownership shares sum to 100% per date
Supply networkregion → site → lanesa distribution centre opens; lanes attach to the golden site

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.