Looking for Guidance: Building Our Service Model

[VictoriaW]

Hello ServiceNow Community,

we're looking for some guidance on service modeling and would appreciate learning from others who have already gone through a similar journey.

We already use ITSM, have a populated CMDB, and are now moving toward a service-oriented operating model. Our goal is to leverage service modeling for:

• Service ownership and accountability
• Impact analysis and change assessment
• Operational governance
• Better visibility into how technology supports business capabilities

While we understand the concepts of Business Services, Technical Services, Application Services and CIs, we are struggling with how to turn the theory into a practical implementation approach.

We're specifically looking for:

• A step-by-step approach to service modeling
• Recommendations on where to start when a CMDB already exists
• Examples of Business Services and CIs and their relationships
• Lessons learned and pitfalls to avoid

Ideally, we'd love to see a real-world examples, for example:

• Email Service or Production label printing
• a more process oriented Service like onboarding a new employee

Has anyone been in a similar situation and can share how you approached the implementation? Any examples, best practices or lessons learned would be greatly appreciated.

Thank you very much in advance!

[boteeuwen]

Lessons learned:

• Don't mistake Application Services for Software CIs: An Application Service is a logical deployment of a system (e.g., "Workday - Prod"). It is not the software asset license or the executable file.
• Teams often spend months arguing over definitions (e.g., "Is this a Business Service or a Technical Service?"). Make a logical decision, document it in your internal governance guide, and move forward. You can always reclassify a service later.
• Manually drawing connections between hundreds of servers and application services creates an unsustainable maintenance burden. Rely on ServiceNow Dynamic CI Groups or Service Mapping (Query-Based/Tag-Based) to keep relationships updated automatically.
•  A service model is only useful if someone maintains it. Do not publish a Business or Technical Service unless it has a designated Owner populated in the ServiceNow record.