Skip to main content
A useful Atlas AI agent use case needs judgment, draws on more than one data source, and depends on data you can document. The sections below are how you decide whether a workflow fits an agent, and how narrow to make that agent’s scope. For what Atlas AI is, see About Atlas AI.
Atlas AI agents query data stored in CDF’s Data Modeling Service (DMS). Your CDF project must use DMS before you can configure an agent that queries the knowledge graph.

Use case fit

Not every workflow benefits from an agent. Good use cases involve questions that require judgment, draw on multiple data sources, and rely on accurate, well-documented data. These dimensions help you assess whether a problem is suitable for an agent before you start building.

Accuracy

Language models can give different answers to the same question. Any use case that requires every answer to be exactly right, such as payroll calculations or safety-critical permit approvals, is not suitable for a fully autonomous agent. This does not prevent using agents as part of those workflows, but critical decision points require your review. Workflows where some variation is acceptable, or where you review the output before acting, are more suitable.

Risk

Consider what happens when the agent is wrong. Some tasks have a low tolerance for error but also low consequences if something goes wrong, making them suitable for early experimentation. For tasks where an error could affect safety, regulatory compliance, or production, you should review the agent’s output before taking action.

Volume and availability

Agents are most useful for high-volume or always-on tasks. Tasks like reviewing maintenance procedures, interpreting inspection reports, or extracting specific parameters from large volumes of vendor documentation are suitable for an agent. Tasks that require 24/7 availability, such as monitoring operational logs or supporting control room questions, also work well.

Predictability

Predictable, repeatable processes typically work better with traditional automation. Agents are most useful in open-ended workflows where inputs vary and each question requires different steps to answer.

Documentation and data readiness

Agents have no built-in knowledge of your organization. You need to give the agent context through clear documentation that describes the task, the relevant data, and the rules that apply. Use cases that rely on undocumented knowledge are unlikely to work. The data the agent queries must also be accurate and well-structured. Data quality is not optional. Agents can handle specific parts of many real-world processes, even when you still need to monitor the overall workflow. Identifying those parts can be more practical than trying to automate the entire process.

Scope and instructions

Each agent should focus on one workflow or question type, such as equipment fault diagnosis, work order triage, or document Q&A. Keeping the agent’s mission narrow makes it easier to test, maintain, and trust. The skills that support that mission can be as detailed as the domain requires. The agent’s instructions define how it behaves in every interaction. Good instructions cover four things. Scope and identity defines what the agent does and what it should decline to handle. Universal rules apply to every question regardless of topic, such as stating assumptions when data is ambiguous. Output expectations describe what a complete response looks like. Boundaries establish what the agent must not do without user confirmation. Workflow-specific knowledge belongs in skills, not instructions.

Next steps

Last modified on November 17, 2026