Create Systems

Add Systems to a Blueprint, then link Systems to Processes for traceability.

Overview

Systems represent applications and platforms in scope for delivery work. Linking Systems to Processes supports traceability and reporting.

Key Concepts

System: application, platform, or service in scope
System Type: classification used for filtering and reporting
Environment: production, test, or sandbox context for a System record

How It’s Used

Use Systems to define technology scope alongside Processes. Use System Types to standardize reporting across Projects.

Benefits

Clearer technology scope for delivery teams
Better reporting through consistent classification
Faster impact analysis through links to Processes

Setup Steps

1

Add a System to a Blueprint

Navigate to Blueprints.
Open a Blueprint.
Open Systems (or Systems Management).
Select Add system.

2

Define core fields

Required:

Name: stable internal name, such as ERP — Production

Optional fields when enabled:

System Type: such as ERP, CRM, Data, Integration
Environment: Production, Sandbox, UAT, Dev
Owner / Admin
URL / login
Description

3

Link Systems to Processes

Linking is many-to-many. One Process can run on several Systems.

For example:

Procure-to-Pay → ERP — Production
Customer lifecycle → CRM — Production
Data integration → Integration platform

Best Practices

Create separate System records for separate environments.
Keep System Types small and stable.
Avoid generic System names without environment context.

Summary

Systems define technology scope for a Blueprint. Links to Processes support traceability and reporting.

Troubleshooting

System cannot be linked to a process

Confirm both items are active. Confirm Blueprint edit permission exists.

System does not appear in a Project

Confirm the System exists in the Blueprint. Confirm the Project was created after the System was added.

Related:

What Are Blueprints?
Processes
Process Hierarchy
Systems Management
System Types

Last updated 7 months ago