Getting Started

Service Mapping helps you understand how your IT environment supports the business, sometimes referred to as IT Governance.

It lets you describe and connect different contexts such as IT Services, Vendors, Customers, Applications, or Countries, and link them to assets automatically discovered by vScope, such as servers, databases, file systems, deployments, backups, switches, and more.

You get a clear, collaborative view of how everything in your IT delivery fits together.

What Service Mapping Does

Each Entity (e.g., IT Service, Vendor, Application, Customer) is documented on a Card, a single place to describe what the entity does, who owns it, and what other entities or assets it depends on.

For example, the IT Service “Email” card might include:

• Its purpose and main users
• Key contacts or service owners
• Linked systems such as Exchange servers, user groups, and backup solutions
• Updated details about supporting assets, eg. server, database and web certificate
• Related services like “Identity Management” or “Monitoring”

Together, these cards form your governance or service catalog, a structured overview of how technology supports your organization and the business perspective of your IT delivery.

How It Works

vScope automatically collects information about assets from your IT environment using Asset Discovery.
With Service Mapping, you can connect those discovered assets to a business context. This means your documentation will always include up-to-date information about every connected asset.

Tip

If you already use Discovery, you don’t need to install or scan anything new. Service Mapping uses the information vScope already knows about your environment.

Information is added to Cards using Layouts — templates that define what to document for each entity type.
You can customize layouts to fit your organization’s governance and documentation standards. Each Entity Type (IT Service, Application, Vendor, etc.) can have its own layout to make the documentation more relevant and specific.

Tip

vScope includes bundled layouts to help you get started. You can customize them freely – they’re just templates.

When to Use Service Mapping

Use Service Mapping to:

• Build and maintain a governance or service catalog that everyone can understand and collaborate on
• Enable data-driven documentation with detailed, automatically updated information about assets
• Document dependencies and relationships between systems and services
• Clarify ownership and responsibilities
• Support change management, audits, and risk analysis with clear documentation

Service Mapping works best when used together with vScope Asset Discovery — ensuring every card always contains the latest information about your IT environment.