Difference between revisions of "Location"
Jump to navigation
Jump to search
(table added) |
|||
Line 4: | Line 4: | ||
Locations are an important expression of the uniqueness of an organization on its infrastructure. They form a high-level representation of the specific, often unique, business requirements that act upon the infrastructure facilities. | Locations are an important expression of the uniqueness of an organization on its infrastructure. They form a high-level representation of the specific, often unique, business requirements that act upon the infrastructure facilities. | ||
<br style="clear: both" /> | <br style="clear: both" /> | ||
+ | ==Example locations in this repository== | ||
+ | |||
+ | {| {{prettytable}} | ||
+ | |Location||Owner||Maturity | ||
+ | |- | ||
+ | {{#ask: [[Category:Location]][[Page maturity::>0]][[Page maturity::<9]] |sort=Brief description|format=template|link=none|template=TableRowLocations}} | ||
+ | |} |
Revision as of 12:49, 3 March 2013
Introduction
The OIAm dimension "Location" signifies a subdivision of infrastructure utilities that appear in a single "logical location". The purpose of this dimension is the grouping of external influences and/or the resulting demands and quality requirements that operate in a specific business context. In practice, one sees that "logical location" for a large part corresponds with actual physical location.
Locations are an important expression of the uniqueness of an organization on its infrastructure. They form a high-level representation of the specific, often unique, business requirements that act upon the infrastructure facilities.
Example locations in this repository
Location | Owner | Maturity |
Not specified | J.A.H. Schoonderbeek | 1 |
Office | S.A.D. Jumelet | 4 |