Continuous Improvement (Coach)

Q: Is the Coach running on its own?

No. It answers when someone asks inside a case, with no schedule and no event trigger. Like every assistant Agent, it waits to be asked.

Q: Where do its answers come from?

From the case itself: the documents attached to it, and the causes, countermeasures and lessons recorded on similar cases.

Q: Can it close a case or change a record?

No. It drafts and it looks things up. A person writes the case, owns the tasks and closes it.

Q: How is this different from the Investigation Engine?

The Investigation Engine holds the structure: issues, cases, causes, countermeasures and lessons. The Coach helps you fill it in.

Problem statement draftedWeld Line 1 stoppage
Draft: Weld Line 1 stoppage Accept Edit Discard

Improvement coach

Start a case without a blank form

The Coach pulls the context from the issue that opened the case, history included. Then it drafts a problem statement, a scope and a target condition. You accept, change or ignore every suggestion before the case is saved.

Case context pulled from the issue that opened it, with its history
A drafted problem statement, scope, and target condition
You accept, change, or ignore every suggestion before the case is saved

Cycle time above upper limit

Past cases

Look up what caused this before

The Coach pulls causes from the fishbone entries on cases your team has already closed. Each countermeasure comes back with what it was meant to fix. Lessons come with who signed off when that case closed.

Causes retrieved from the fishbone entries on past cases
Countermeasures with what each one was meant to fix
Lessons captured when an earlier case was closed, and who signed it

Answered from the case file Torque procedure TQ-04 Weld spec WS-12
TQ-04, section 3.2

Case files

Ask questions of every document on the case

It reads every document attached to the case together, as one set. Every answer points back to the file and the passage it came from. It works from your case files alone.

Every document on the case read as one set
Answers point back to the file and the passage they came from
Grounded in your case files, never the open internet

Oldest open task: Weld Line 1: bevel gauge setup CASE-0418 5d 1h Verifying

Improvement tasks

Track tasks to done

Raise a task from a case, from an issue, or on its own. Every task has an owner, a due date and a state. Comments stay on the task, with who wrote each one.

Tasks raised from a case, from an issue, or on their own
Owner, due date, and state on every task
Comments stay on the task, with who wrote each one

Open across Brantford Plant 2 Issues 6 Cases 4 Tasks 9
Torque drift traced to CASE-0418

Site overview

See every open issue, case, and task on one screen

Every open issue, case and task for the site sits on one screen, so nothing gets tracked twice. An open issue traces to the case that took it on. Lessons and target conditions stay with the case they came from.

Issues, cases, and tasks for the whole site on one screen
Open issues traced to the case that took them
Lessons and target conditions kept with each case

Suggested countermeasureAsked by P. Villeneuve CASE-0418
Recheck torque at bolt 3 Write to case Discard

Coach scope

Ask it when you want it. It never acts on its own

It has no schedule and no trigger from an event. It sees only what your permissions let you see. A person reviews anything it suggests and writes it into the case.

No schedule and no trigger from an event
Nothing reaches a case until a person reviews it and writes it
It sees only what your permissions let you see

FAQ

Is the Coach running on its own?

Where do its answers come from?

Can it close a case or change a record?

How is this different from the Investigation Engine?