Service Mapping Implementation practices

[ChandanK0753855]

Hello,

We have an active CMDB with ServiceNow Discovery already implemented and running successfully in our Production instance. We are now planning to implement Service Mapping.

Looking for guidance on the following:

1. What are the recommended steps and best practices for implementing Service Mapping in an environment where Discovery is already operational?

2. Since Discovery is active only in Production and Dev does not have CI data being populated, is cloning Production to Dev the recommended approach for building and testing Service Maps?

3. Once Service Maps are created in Dev, what is the recommended way to move them to Production?

4. During Service Mapping implementation, what configurations/artifacts are captured in Update Sets, and what needs to be migrated manually?

5. Service Mapping approval requests need to be sent to Service Owners, but email is enabled only in Production. How is approval process followed in the non-production environments?

Any recommendations, lessons learned, or implementation experiences would be greatly appreciated.

[vaishali231]

Hey @ChandanK0753855 

Since Discovery is already implemented and running successfully in Production, I would recommend treating Service Mapping as an extension of the existing CMDB rather than as a separate discovery solution.

1. Recommended approach for Service Mapping implementation

I would follow these steps:

Validate the existing CMDB

Confirm Discovery is populating the required CI classes.

Validate CI identification and reconciliation.

Check that CI relationships are being created correctly.

Verify MID Server health and Discovery credentials.

Confirm that the applications/servers required for mapping are being discovered correctly.

Configure Service Mapping

Configure the required MID Server capabilities and credentials.

Review Service Mapping patterns and identification rules.

Define application services and appropriate entry points.

Start with a small pilot, rather than mapping all applications at once.

Validate and tune the maps

Review the discovered topology.

Correct missing or incorrect relationships.

Validate the map with the respective Service Owner.

Once the approach is stable, gradually onboard additional application services.

2. Should Production be cloned to Dev?

In this specific scenario, I would consider a controlled Production-to-Dev clone a reasonable approach because Dev currently does not have representative CI data.

Service Mapping depends heavily on the CMDB and Discovery data. If Dev has no CI data, it becomes difficult to properly build and test realistic Service Maps.

However, after the clone, I would carefully review/disable Production-specific configurations such as:

Discovery schedules

MID Server configuration

Credentials

Integrations

Outbound communication

Email

Scheduled jobs

Production-specific system properties

The important point is that the clone should be used to provide a representative CMDB baseline for development/testing. It should not be considered a replacement for Discovery in the target environment.

3. How should Service Maps be moved to Production?

I would avoid treating a Service Map as simply a static configuration that is exported from Dev and imported into Production.

The recommended approach would be:

Dev
→ Build and tune the Service Mapping configuration
→ Validate the application service and topology
→ Promote the required configuration

Production
→ Ensure Production Discovery/CMDB is healthy
→ Create/validate the application service and entry point
→ Run Service Mapping against the actual Production environment
→ Validate the resulting topology
→ Obtain Service Owner approval

This is important because Production should ultimately contain the topology generated from the actual Production infrastructure and CMDB data.

4. What is captured in Update Sets?

I would separate this into configuration and runtime/CMDB data.

Configuration/customization that can generally be promoted through the normal deployment process includes items such as:

Service Mapping configuration

Customized Discovery Patterns

Identification/Reconciliation configuration

Custom scripts

Business Rules

Script Includes

Relevant system properties

Other configuration customizations

However, I would not treat the following as normal Update Set configuration:

1. Discovery-generated CI records
2. Discovery results
3. Current CI relationships generated from Discovery
4. Runtime CMDB data
5. The actual topology generated from the Production environment

Therefore, after promoting the configuration, Service Mapping should be executed in Production against the Production CMDB to generate/validate the actual topology.

I would also verify the exact Service Mapping artifacts in the specific ServiceNow release being used, rather than assuming every related record is automatically captured by an Update Set.

5. How to handle approvals when email is disabled in Dev/Test?

Email is mainly a notification mechanism. The approval/review task itself can still be tested through the ServiceNow UI.

In non-production:

Send for Review
→ Review task is created
→ Test/Service Owner opens the task from Service Mapping/My Tasks
→ Reviews the map
→ Approves or rejects

Therefore, I would not enable Production email just to test the approval process in Dev.

In Production, once email is enabled, the Service Owner can receive the notification and access the review task through the notification/link.

Recommended overall approach

I would use the following model:

Production Discovery + CMDB
→ Controlled Prod Clone to Dev
→ Build/Tune Service Maps in Dev
→ Promote Configuration
→ Validate in Test/UAT
→ Run Service Mapping against Production CMDB
→ Service Owner Review/Approval

The key principle is: promote configuration, but let Production Service Mapping build/validate the topology against the actual Production CMDB and infrastructure.

*************************************************************************************************************************************

If this response helps, please mark it as Accept as Solution and Helpful.

Doing so helps others in the community and encourages me to keep contributing.

Regards

Vaishali Singh

Servicenow Developer
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb