Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Systems Management

Define Systems and System Types in a Blueprint, then link Systems to Processes.

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 document scope and ownership. Use System Types to standardize reporting across Projects.

Benefits

  • Clearer scope definition across delivery teams

  • Better reporting through consistent system classification

  • Faster impact analysis when changes affect multiple Processes

Setup Steps

1

Create Systems

2

Define System Types

3

Link Systems to Processes

Link Systems to Processes for traceability.

Best Practices

  • Create separate System records for separate environments.

  • Standardize System Type names across Blueprints.

  • Keep System names stable and human-searchable.

Summary

Systems Management defines the technology scope for a Blueprint. System Types and process links support reporting and traceability.

Last updated