A planning assistant

Industry: Optical lens manufacturing
Where it stands: Knowledge base complete, the planning assistant live, ERP and shop floor connected read-only
What was delivered: Agent configuration and a planning knowledge base
Where the knowledge came from: Each department's documents, spreadsheets, procedures and records, plus the ERP and shop floor systems
Timeline: About 11 days to build the knowledge base; about 3.5 days from first system connection to go-live

Answers outside the systems

Which surface treatment machines can substitute for each other existed only as a spreadsheet cell's fill colour.
How cutting time is calculated when one person runs two machines was known only to experienced hands.

Asgard read each department's documents, spreadsheets, procedures and records. The originals stay read-only.
Asgard used the rows of history to find how the work is really done.
Asgard wrote vocabulary, rules, exceptions and ownership into the company wiki.
Asgard organised machine capability, tooling, cutting time and surface treatment chemicals into reference tables. Anyone who edits a cell by hand records a reason and a date.
Asgard moved the substitute machine rule from the cell colour into a reference table. The agent can query it. A new hire can read it.
Asgard wrote what to divide cutting time by when one person runs two machines into the time estimation procedure.
Asgard turned anything in the records nobody could read into a question ticket for the responsible department.
Example: a cavity count in the tooling table read "1+1". The tooling department answered that two pieces are produced at once. Asgard wrote the answer into the tooling reference table and the skills that use it.
Asgard records the provenance of every rule: which department answered, on what date, and what changed.
Asgard turned a list the tooling department maintained by hand into the tooling master record.

Asgard wrote the procedures into skills for the planning assistant: lookup, scheduling, time estimation and procedure search.
The planning assistant connects to the ERP and shop floor systems read-only, and writes nothing back. It queries live numbers such as stock, orders, yield and today's schedule through semantic models each time.

When a department answers a ticket or revises a reference table, the knowledge base will change with it.
The planning assistant will collect feedback on its answers from users. The feedback will go to Odin.
Wrong answers will become tests. A change will be kept only if scores improve.
Knowledge base updates will reach the planning assistant every 6 hours, with no redeployment.

Get started

AI feasibility review of a live workflow