Environments in the CMDB Part 2.
So, based on the kind comments of a number of people and a bit of pondering we came up with the following solution.
1. Each service model will be oriented around a single Application Environment (PROD, UAT, SYS, DEV) and then will include dependent CIs such as virtual and physical servers, database instances, application servers, etc.. Each dependent CI will be related to the Application CI using a direct impact type relationship. (Our topology tools will find the dependency relationships between CIs and also add those to the CMDB).
2. The application CI which is being modeled will have a name like [application]-[environment] (e.g. app1-prod). This will provide a unique name for each application instance as it exists in different environments.
So, the environment is a unique part of the CI name and could be easily reported out using %Like% type queries. At some point we may also add an attribute to the Application CI but it is not critical path.
