CMDB Business Applications

[W_all_E]

Hi everyone,

In my organization, we have multiple business units — and my team is the unsung hero supporting all the applications they rely on daily to keep things running smoothly.

Right now, I’m managing a sprawling spreadsheet that tracks every app: versions, server locations, database links, application servers, support expiration dates (thankfully, my trusty CoPilot Agent scouts Google for upgrade alerts to me - recently I created), which business unit owns what, the go-to SMEs, installation guides, account details, and license keys.

But here’s the thing — I want to level up and move all this into ServiceNow.

If anyone’s been down this road and successfully migrated or set up something similar, I’d love to hear your war stories and advice on where to start.

I’ve peeked at the CI tables in ServiceNow—there’s cmdb_ci_app and business_app—but honestly, I’m not clear on their differences or best practices for this kind of data.

Could you help guide me on how to kick this off? And feel free to inspire me with your brilliant ideas!

Thanks a ton!

[abt1639]

Kudos for starting this journey! I'd say our organization got serious about this type of management in SN last year, and it is still a work-in-progress. Your peek at the Business Applications table is a great place to start, as that is the table which "represents an overarching, high-level concept of a business application, defining it as an ecosystem of software, hardware, and services that supports a business function. It is used to track strategic information like business owner, cost, and usage, whereas the related cmdb_product_application table tracks the specific software product details like version and vendor. "

Getting your applications defined in that table will lay the groundwork for the rest of your journey. Have you also thought about who besides your team should "own" that table? For us it is our Enterprise Architecture team.