Service Mapping flow

Release version: Yokohama

Updated August 6, 2025

2 minutes to read

Summarize

Summarized using AI

Summary of Service Mapping flow

Service Mapping enables organizations to collaboratively map, review, and monitor application services, ensuring accurate representation of service instances and their components. This process involves multiple user roles working together to configure, map, review, and finalize application service maps, thereby improving service visibility and management.

Show full answer Show less

Key Features

Initial Configuration: Administrators perform essential setup tasks to enable Service Mapping functionality.
Bulk and Individual Mapping: Administrators can map application services in bulk or individually to create service instance maps.
Error Handling: Errors in application service maps are identified and fixed either in bulk or on an individual basis by administrators.
Review Process: Service instance owners review the maps for completeness and correctness, providing feedback or approval.
Fine-Tuning: Administrators refine service maps based on owner feedback to meet organizational requirements before final approval.
Finalization: After approval, administrators complete service maps by configuring access controls and advanced attributes such as criticality.
Pattern Customization: Users with the pdadmin role can customize discovery patterns to better identify devices and applications forming the services, requiring programming knowledge.

Key Outcomes

Accurate and comprehensive application service maps that reflect all major components.
Improved collaboration between administrators and service owners to ensure service map quality.
Enhanced control over service visibility and access through final configurations.
Ability to maintain and analyze application services effectively using Service Mapping.

Learn about high-level tasks users having different roles perform in Service Mapping.

In Service Mapping, users collaborate to map, review, and monitor organization application services.

Note:

For a complete list of Service Mapping roles, see Components installed with Service Mapping.

A typical Service Mapping workflow has the following stages:

The administrator performs basic obligatory configurations to set up Service Mapping. See Configuring Service Mapping for more details.
The administrator maps organization application services in bulk. In addition, the administrator may map some application services individually. See Map multiple application services suggested by classic Service Mapping for more information about mapping services in bulk.
The administrator fixes application service errors in bulk, as described in Fix application service errors in bulk.
The administrator reviews the results of the initial mapping, resolving errors in individual application services. See Fix errors in individual application service maps for more details.
The administrator sends fixed application services to the application service owner for review. See Send application service maps for review for more information.
The service instance owner checks that the service instance maps are complete and all major components comprising it are correctly represented. If necessary, the owner leaves comments, referred to as reject messages, on service instance maps for the Service Mapping administrator to implement. See Review application service maps.
The administrator uses the feedback from the application service owner to fine-tune the application service maps, and then resends them to the owner for review. For more information about fine-tuning an application service map, see Fine-tune application services to implement owner requests.
If the revised service instance maps are satisfactory, the service instance owner approves them. If not, the owner requests further fixes, which the administrator must address. See Review application service maps.
The administrator finalizes the application services by configuring access and setting advanced attributes, such as criticality. To learn more, see Application service completion.
After the service instance definition is complete, the Service Mapping user can view application service maps. To learn more about maintaining the application services using Service Mapping, see Application service analysis and maintenance using classic Service Mapping.

In addition to these tasks, there may be a need to customize patterns that Service Mapping uses to discover devices and applications forming application services. Users must have the pd_admin role to customize patterns. In the base system, the service_mapping_admin role contains the pd_role. Customizing patterns requires basic knowledge of programming.