One creating function per data entity across the operating model Every entity is created by exactly one business function, so ownership is never contested: capacity measurement is created once and never updated, because telemetry is evidence, and Customer never reaches the publish column, keeping personal data out of open data by design.
One creating function per data entity across the operating model
A Data Entity to Business Function matrix worked for London Grid Distribution, the TOGAF artifact at the boundary of Phase B and Phase C. Six data entities label the rows and six business functions title the columns, with a calm accent-tinted header strip. Each cell holds C, R, U and D marks for create, read, update and delete, and every creating C is set in accent so the one-creating-function-per-row rule is legible. A faint accent tint runs along the Customer row and the Publish network data column, and a legend under the grid names that tint: their empty crossing keeps personal data out of open data by design.
Customer CRUD R RU Connection application CRUD R R R Network asset R RU CRU R R Capacity measurement R CR R R Outage record CRU RU R R R Settlement charge R R CRUD
C create, R read, U update, D delete. Bold marks the creating function per row.
Tinted: the Customer row and the Publish network data column, whose empty crossing keeps personal data out of open data.
Source: TOGAF Standard 10, Phase B and C artifacts
