Service Mapping flow
Summarize
Summary of Service Mapping flow
Service Mapping allows users to collaboratively map, review, and monitor an organization's application services. Different roles within the organization participate in a structured workflow to ensure that application services are accurately represented and maintained.
Show less
Key Features
- Configuration: Administrators perform essential configurations to set up Service Mapping.
- Bulk Mapping: Administrators can map application services in bulk or individually.
- Error Management: Errors can be fixed in bulk, followed by individual reviews.
- Review Process: Application service owners review the maps and provide feedback for adjustments.
- Customization: Users with the pdadmin role can customize discovery patterns for devices and applications.
Key Outcomes
By following the Service Mapping workflow, organizations can ensure comprehensive mapping of their application services, enhance accuracy through collaborative reviews, and maintain service integrity. Administrators will finalize services by configuring access and advanced attributes, enabling users to effectively view and manage application service maps.
Learn about high-level tasks users having different roles perform in Service Mapping.
- 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.