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

Create a Use Case

A use case is a collection of agent orchestrations for the same problem. The best way to use AMESA is to build multiple orchestrations within the same use case using different design patterns and variations. This allows you to iterate and improve for the best possible performance.

All orchestrations within a use case share the same simulator and the same overall KPI.

Create a Use Case in the UI

To create a use case, click on New Use Case in the upper right-hand corner of your dashboard.

You'll be prompted to enter the simulator associated with your use case and then choose your team.

Set KPI and ROI

After you select your simulator and team, you'll be prompted to set the KPI and ROI for your use case.

The KPI is the top-level goal, the most important metric you are trying to optimize that you will use to evaluate the performance of your team of agents. Choose the sensor variable that represents this metric to serve as your KPI.

For benchmark value, enter the current performance level on the KPI. This is the number that your agents will attempt to outperform. Add the benchmark units where prompted.

The ROI section allows you to represent agent performance in terms of financial impact. Enter the value in dollars of a specific percentage improvement in the KPI (either increase or decrease depending on the problem).

After agents are trained, the platform will use this information to provide data and visualizations about the performance on the KPI compared to the benchmark and about the financial return on investment on the Benchmarks page.

Last updated