Applications in the CMDB

[Brian Lancaster]

I have not had a lot of experience when it comes to best practice with CMDB.  I'm working for a new company and they are starting out building out the ServiceNow Environment.  So here we have application and each application has several modules.  We will be using Incident management to start with and will eventually use Problem and Change management.  Each application module will have a different approver for change management so we need these pick able as a CI.  We also need these for incident and problem so we can determine ware an issue lies (example instead of the issue possibly being on the server maybe it was related to the code that was pushed out of a particular module).  So my question is what table do I put these applications and their modules in?  I was thinking of use Business Applications for the overall application and then Application Services for the specific modules within the applications but the CSDM white paper says not to use CIs in the business service table as operational CIs.

[Darin2]

Brian, I highly recommend following the Crawl state in the whitepaper. This will set you up for expanding and maturing in the future. The Application Service record is the key to setting up your processes in Incident, Problem, Change, etc when you are first getting started. On the App Service record, you can identify things like Assignment Group, Owner Group, Resolver Group and enable all of your other processes. 

[Brian Lancaster]

Yes but where do I put these CIs?  We need them for incident.  Our ServiceNow partner wants to put them in cmdb_ci_appl but i'm not sure that is the correct place as that is a parent table that contains CIs from child tables like Web Servers.

[Darin2]

[Darin2]

the cmdb_ci_appl is NOT the correct table to use. This picture shows the correct table structure for each element of the CSDM. This should be followed whenever possible.