--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Service Mapping flow # Service Mapping flow {#ariaid-title1} * Release version: Yokohama * * Updated August 6, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## 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](https://servicenow-prod.fluidtopics.net/yX0bMB_HcUfkH7E9K8SAsw "Several types of components are installed with activation of the Service Mapping plugin, including tables, user roles, properties, and scheduled jobs."). A typical Service Mapping workflow has the following stages: 1. The administrator performs basic obligatory configurations to set up Service Mapping. See [Configuring Service Mapping](https://servicenow-prod.fluidtopics.net/6~Gv_u6nYAKwi5pxiDXHGg "You get started with Service Mapping by configuring roles, credentials, and MID Server connections.") for more details. 2. 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](https://servicenow-prod.fluidtopics.net/qFTEgnBYmx4N~e7Wi0hmtA "You can map multiple application services identified and suggested by Service Mapping in a single operation. This method suits your organization if you do not have much information about application services.") for more information about mapping services in bulk. 3. The administrator fixes application service errors in bulk, as described in [Fix application service errors in bulk](https://servicenow-prod.fluidtopics.net/AQZZC7bwEONc9WvfM9~Maw "Service Mapping classifies errors by their root cause, for example, missing credentials or task timeout. For a fast and efficient process, fix errors belonging to the same category in bulk."). 4. The administrator reviews the results of the initial mapping, resolving errors in individual application services. See [Fix errors in individual application service maps](https://servicenow-prod.fluidtopics.net/mCyIAds3bqivvs99ielgpg "You can address discovery issues in each application service map individually.") for more details. 5. The administrator sends fixed application services to the application service owner for review. See [Send application service maps for review](https://servicenow-prod.fluidtopics.net/aStpPAiHMPw9hVULLwz~sA "After you map an application service, send it to the application service owner for review to make sure that the map is accurate.") for more information. 6. 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](https://servicenow-prod.fluidtopics.net/CUGQ7_LI4UkMJXDfKsbLBw "As the application service owner for the application service map, you receive an email notification that the application service map is assigned to you for review. Review mapping results for correctness and either provide your feedback or approve the application service map. The review and approval process is available only for discovered and manually created service instances."). 7. 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](https://servicenow-prod.fluidtopics.net/iBl4ZwvZMr6J_fUdsUa1Nw "As an administrator, you tweak and fine-tune maps based on comments from the application service owner."). 8. 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](https://servicenow-prod.fluidtopics.net/CUGQ7_LI4UkMJXDfKsbLBw "As the application service owner for the application service map, you receive an email notification that the application service map is assigned to you for review. Review mapping results for correctness and either provide your feedback or approve the application service map. The review and approval process is available only for discovered and manually created service instances."). 9. The administrator finalizes the application services by configuring access and setting advanced attributes, such as criticality. To learn more, see [Application service completion](https://servicenow-prod.fluidtopics.net/oTiVA8bO~~ejaFfgU_iy9w "After an application service is reviewed and approved, you can define attributes that enhance its discovery, reflect its importance, and control access to it."). 10. 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](https://servicenow-prod.fluidtopics.net/kktVI~k2uB35tKBH_EqH8Q "Service Mapping creates maps to help you see the architecture and organization of application services. These maps are useful for planning change or migration, as well as analyzing the continuity and availability of services."). {#service-mapping-flow__ol_ygd_qcz_41b} Figure 1. Service Mapping flow 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. **Related tasks** * [Control user access to application services](https://servicenow-prod.fluidtopics.net/Tl72BIYyrHnYkttnrTFwVw "Assign user roles to service groups to grant users access to application services in your organization. Your organization may restrict access to some services for security or secrecy reasons.")