As we are maturing in our EA practice, we would like to migrate our approved objects and models to Enterprise folders, as projects are completed. Some of these models will reflect As-is processes for a specific 'Scope' of the company. The Scope could be one or more geographic areas (country, region, state, etc) - but it could also be specific to one or more 'business unit' or division scopes. The scope could even be specific to a particular type of facility - for example manufacturing plants.
We would like to come up with a flexible way to model these various types of Scope - so that as our business changes, we don't have to replicate the same model for additional Scope areas. So of course we would not plan to include the 'Scope' in the name of the model or even in a folder name. We were thinking of defining Scope objects, and linking the Models to the relevant objects.
This can be further complicated by the fact that our high-level models may often be global in nature - but the related drill-down models are more likely to have different Scopes.
Has anyone had experience with this type of modeling need ? Suggestions ? Pitfalls ?
Really appreciate the valuable contributions from this community !