> For the complete documentation index, see [llms.txt](https://docs.primeur.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.primeur.com/panorama-2.0.1/operational-resilience/example-use-cases/monitor-and-optimize-the-operational-risk-surface.md).

# Monitor and optimize the Operational Risk Surface

### Scenario

The ICT team regularly reviews the Operational Risk Surface to keep the Data Mover environment clean, efficient, and aligned with actual system usage. By identifying inactive or unused components, the team reduces operational complexity and minimizes configuration-related risks.

### Objectives

Using the Operational Risk Surface cards, the ICT team can:

* Identify actors that have not generated traffic within a specified time period.
* Detect unused flow models, servers, endpoints, and FELs that may be candidates for cleanup.
* Highlight obsolete or redundant configurations that no longer contribute to business operations.

### Flow overview

#### Capability

Operational Risk Surface monitoring

#### Description

This capability provides visibility into system usage and highlights inactive or unused components to support configuration optimization and governance.

#### Scope

* Actors
* Flow models
* Servers
* Endpoints
* FELs

### Activities

#### Identify inactive actors

* Open the **Inactive Actors** card
* Set the **Inactive since (days)** threshold
* Review actors with no recent activity

#### Review unused components

Use the following cards:

* **Unused Flow Models**
* **Unused Servers**
* **Unused Endpoints**
* **Unused FELs**

#### Validate findings

Classify each item as:

* Temporarily inactive
* No longer required
* Misconfigured

Validation must be performed with business and technical owners.

#### Apply optimization actions

* Remove or archive obsolete components
* Update ownership information
* Exclude non-relevant components from monitoring where applicable

### Validation

* Identified components are reviewed and classified
* Decisions are validated by responsible owners
* Actions are executed and documented

### Outcome

The Data Mover environment remains aligned with actual usage, with reduced operational complexity and improved configuration govern