What Edmund is

Edmund is an assistant for the shop floor. Ask it about a machine and it answers from that machine’s own knowledge — its manuals, drawings, PLC programs, maintenance history and connected data — and shows the source behind each answer. It doesn’t guess from the open internet; it works from what your plant has loaded.

Projects are your machines

Edmund

Each machine or production line is a project. A project holds that machine’s knowledge and its chats, so everything you ask is about the machine in front of you. You usually open the right project by scanning its QR code — see Projects & QR codes.

Where answers come from

A project’s knowledge is built from real sources your team loads:

1. Documents — manuals, drawings, part catalogs and other files. See Documents & PLC programs.

2. PLC programs — the machine’s control logic, searchable like any other source.

3. Maintenance journals — a record of operation, faults and repairs. See Maintenance journal.

4. Connected databases — live data such as stock, parts and fault logs. See Data sources.

How you work with it

You ask in plain language in the chat. Edmund’s agents search the real sources, and you can watch which one they’re searching. A document or journal answer cites its source; a database answer comes back as a table. You can rate every answer with a thumbs up or down.

For how to phrase a good question, see Asking good questions; for how answers are built, How Edmund searches and Reading answers & citations.

What it won’t do

If a project’s knowledge doesn’t cover your question, Edmund says so instead of inventing an answer — a clear gap is more useful on the floor than a confident guess. When that happens, tell whoever looks after that machine’s knowledge so they can add the missing manual, drawing or record.