/USE EDMUND

Your first answer

Stand at the machine, scan its code, and ask Edmund one question. This page gets you to a cited answer in a couple of minutes.

Operator / maintenance technician

Each machine or line is one project in Edmund, and most machines carry a printed QR code. Scanning that code opens the right project straight away, so Edmund already knows which machine you’re asking about. You only need to sign in the first time — your account is set up for you before you start.

Get to an answer

Scan the machine’s code. Point your phone camera at the QR code on the machine. It opens that machine’s project directly, so you don’t have to find it in a list.
Sign in once. If you’re asked to sign in, use the login your administrator set up for you. After the first time, your phone usually stays signed in.
Confirm the project. Edmund opens the machine the code pointed to. Check the name matches the machine in front of you before you ask. (If you open Chat without scanning, Edmund asks you to pick the project first.)
Ask your question. If you’re not sure how to start, tap one of the Suggestions — these are ready-made starter questions. Otherwise tap the input that reads Type your message for Edmund here and type it, use the microphone to speak it, or use the paperclip to attach a photo of the fault.
Read the answer and follow up. Edmund replies using that machine’s own knowledge and shows where each part of the answer comes from. Tap one of the suggested follow-up questions to go deeper without having to phrase it yourself.
Rate it. Use the thumbs-up or thumbs-down on the answer. That’s how the people who look after the machine find weak spots and improve what Edmund knows.

Tip

If your first answer is thin, or Edmund says it doesn’t have that, the machine just doesn’t have enough loaded yet — it isn’t a mistake on your part. Tell whoever looks after that machine’s knowledge (the expert), and it gets better the next time you ask.

What makes a good question

Edmund answers best when you tell it what you’d tell a colleague who can’t see the machine. A good question usually includes:

The symptom — what’s actually happening or what stopped.
The machine state — running, stopped, starting up, in a particular mode.
Any fault or alarm code shown on the panel, written exactly as it appears.

Keep one problem to one chat. If a new, unrelated fault comes up, start a fresh chat for it so each answer stays focused on a single issue.