Lookups and forms
- Customer
- A foodservice equipment distributor
- Industry
- Foodservice equipment distribution
- Slides
- 7
- Industry
- Foodservice equipment distribution and service, covering around 10,000 outlets
- Where it stands
- Systems from different vendors connected; agents look data up and fill forms across them
- What was delivered
- Agent configuration (Agent Hub and a website widget) and a knowledge base
- Where the knowledge came from
- System databases into a data lake by ETL, plus knowledge folders
- Timeline
- First phase live in 2025, renewed and extended in 2026
Signing in to each system
- Warehousing, ERP, approvals, HR, the website and dispatch come from different vendors, with unchangeable source code.
- Staff signed in to each in turn and copied between them.
Data lake and knowledge base
- Asgard loads data from each system's database into a data lake by ETL.
- Asgard built semantic models on the data lake, covering approvals, warehousing, HR and repair dispatch records.
- Managers ask Mimir in one sentence about repair trends, stock and attendance.
- The knowledge folders are also a source for the knowledge base.
Operations and approval
- In the Agent Hub each system has its own agent: e-approval, ERP parts and stock, HR analysis, engineering dispatch and warehouse operations. The agents operate those systems the way staff do.
- Before anything is written or sent outside, the agent stops and waits for a person to approve.
Continuous improvement
- Each system's data will keep syncing into the data lake by ETL on a schedule.
- The agents will collect feedback on their answers from staff. The feedback will go to Odin.
- Wrong answers will become tests. A change will be kept only if scores improve.
The customer is de-identified on the slides.
Slide 1 of 7
Click into the deck to use the arrow keys. On a phone, swipe left or right.
Get started
Book a two-hour workshop
AI feasibility review of a live workflow