Tutorial: Set Up a First Blueprint

Overview

Blueprints define reusable structure for new Projects.

Blueprints reduce setup time and standardize governance.

Key Concepts

• Blueprint: reusable configuration for new Projects
• Processes: reusable process map used for navigation and reporting
• Systems: reusable application inventory linked to processes
• Segmentation: Segment Types and Segments used for scoping and reporting

Segment Types and Segments are scoped to the Organization level.

How It’s Used

Use a Blueprint before creating many Projects.

Use one Blueprint per line of business when delivery patterns differ.

Benefits

• Standard structure across Projects
• Faster onboarding for delivery teams
• Cleaner reporting and traceability

Setup Steps

1

Create the Blueprint

1. Navigate to Blueprints.
2. Select New blueprint.
3. Enter a name aligned to the line of business.
4. Select Create.

Related: Creating Blueprints

2

Define Processes

1. Open Processes in the Blueprint.
2. Add a small process set, such as 10–30 entries.
3. Add parent processes when rollups are needed.

Related: Processes Related: Process Hierarchy

3

Define Systems and System Types

1. Open Systems in the Blueprint.
2. Create System Types for consistent classification.
3. Add Systems and link Systems to Processes.

Related: Create Systems Related: System Types

4

Define Segmentation (optional)

1. Open Segmentation.
2. Define Segment Types aligned to reporting needs.
3. Add Segments for the Organization structure.

Related: Segmentation

Best Practices

• Start small. Expand after teams start delivering work.
• Standardize naming for Processes and Systems.
• Keep Segment Types stable to protect reporting continuity.

Summary

Next action:

• Create a Project from the Blueprint: Create a Project