Use Case (AI System)

What is a use case?

A use case is the top-level record for an AI system on the Asenion platform. It represents the system being governed — along with its stakeholders, assessments, evidence, and reports.

An AI system can be:

Predictive — a traditional ML or statistical model
Generative — an LLM-based application or chatbot
Agentic — an autonomous agent that takes bounded actions

Systems can be built internally or sourced from a third-party vendor.

A use case record holds:

The AI system’s description and classification
Its lifecycle stage
Assigned policies and completed assessments
Models, agents, and datasets linked to it (as sub-records)
Risk status (residual, technology, alignment)
Stakeholder membership and notification preferences
Attached evidence documents (Document Hub)
Generated reports

Who should create a use case?

The AI system owner — typically the product owner or project owner in the organization — creates the use case. During creation, the system wizard guides through:

Basic information and description
Intake conversation (AI-assisted classification that suggests labels and policy recommendations)
Initial screening (Operational Risk Assessment)
Policy assignment based on screening results
Team member invitation

Who has access to a use case?

The Owner who created it has full access by default.
Org Admins can access any use case in their organization.
Other members can only access a use case if they are explicitly added by the Owner or an Org Admin.

Sub-records within a use case

A use case can contain:

Functional Models — the specific AI models or versions deployed within the system
Agents — autonomous agent components
Datasets — datasets the system uses or was trained on
Vendor Models / Vendor Agents — third-party AI components sourced externally

Each sub-record maintains its own assessment and evidence trail while rolling up risk status to the parent AI system.

How to create a use case

See the “Create a new use case” section in the Quick Start Guide.