That is, you don't want any discontinuity in the Concepts (Row 2) or the Logic (Row 3). It is conceivable that you might want to implement in more than one Technology (Row 4), but now you have a synchronization problem that you will have to manage.
In terms of Row 6:Operations Instances, there can by "n" of those, but you want each instance to trace back to the Components Transformation (Row 5), the Physics Transformation (Row 4), the Logic Transformation (Row 3), and the Concept Transformation (Row 2), and probably the Scope Transformation (Row 1) as well. That is how you insure that the reality of the Enterprise is consistent with the Enterprise Architecture. And when the "Systems" say there are 423 Employees in stock, there are actually 423 Employees in stock, etc., etc... and when we say the Concept "Employee" (Row 2:Business Concepts), it means the same across the entire Enterprise and that all the Employee instances (Row 6:Operations Instances) obey that authorized Enterprise Concept (Row 2:Business Concepts) definition.
If you did this, you could actually manage the Enterprise.
"If you get really honest and search all of history, seven thousand years of known history of humankind, to find how humanity has learned to cope with two things, complexity and change ... there is one game in town, ARCHITECTURE.
How do you think they build hundred story buildings, or Boeing 747's, or IBM supercomputers... or even simple things like a one-bedroom house or a Piper Cub or the PC on your desk? Somebody had to write it down... at excruciating levels of detail... ARCHITECTURE. Now, if you want to change any of those things (with minimum time, disruption and cost), how do you change them? You go to what you wrote down... ARCHITECTURE.
The key to complexity and change is ARCHITECTURE.
In the Industrial Age, we had to learn what architecture was relative to physical objects (products) in order to deal with product complexity and product change.
In the Information Age, it is the Enterprise that is complex and changing and therefore, now we are having to learn what architecture is relative to the Enterprise ... Enterprise Architecture.
This is what is making the Framework for Enterprise Architecture so significant in the Enterprise community as we move into the Information Age. The Framework is putting some definition around Enterprise Architecture."