Advisor User Guide

Advisor opens on a single screen:

1. Conversation list on the left - your recent conversations, most recently used first, plus New Thread at the top. On a narrow screen it hides behind the menu button in the header.
2. Header across the top, with the app name and a light/dark toggle. Your account menu sits in the corner above it.
3. Answer area in the middle - your questions and Advisor's answers, including any charts and tables it built.
4. Composer at the bottom, where you type.

Advisor uses your normal OEE IntelliSuite sign-in, and your conversations are private to your account.

A new, empty conversation shows Ask about your data and four starter questions above the box, which you can press instead of typing:

• Show me a table of all devices and their current status
• Chart OEE by line for last week
• What was overall availability yesterday?
• Which machines had the most downtime this month?

They are there to show the range of what Advisor handles - a status list, a chart, a single number, a ranking. Press one and it sends straight away. Once a conversation has messages in it, they go.

Type into the box at the bottom and send. Plain English is the point; you do not need SQL, field names, or a report definition.

Be specific about three things and the answer gets sharper:

• Which machine, line, or area - "Line 14", "the packaging line", or "all devices" if you really do mean the whole plant.
• What time range - "yesterday", "last week", "this month", "between March 3 and March 10". Without a range, Advisor has to guess what you meant.
• Which metric - OEE, availability, performance, quality, downtime, reject counts, cycle time, changeover.

You can also ask for the shape you want: "as a chart", "as a table", "just the number".

One question at a time. While Advisor is working, the send button becomes a stop button, which cancels the answer in progress, and that conversation will not take another question until it finishes. Wait for the answer, or start a new thread for the unrelated question.

A single message can be up to 10,000 characters, which only matters if you paste something large.

Advisor chooses the format from the question and the size of the result:

• A sentence or two when the answer is a number or a short statement. "Availability across all lines yesterday was 82.4 percent."
• A small table written into the answer text when there are only a handful of rows.
• A chart when a trend or a comparison reads better as a picture, or when the result set is large.
• A sortable, paginated table when there are more rows than fit comfortably in the text, or when sorting would help.

When Advisor builds a chart or a table, it does not repeat the same numbers in the text. You get a short sentence framing the result, then the chart or table itself.

Under an answer you will see rows like Used tool: query_pg. That is the tool trail, where Advisor shows its work. Press one to expand it and you see what it sent and what came back - for a database query, the SQL itself and the rows it returned. Long results are shortened while the answer is streaming, and show in full once you reopen the conversation.

If a number looks wrong, open the query and check the date range, the device filter, and the metric it used.

The tools you will see:

• query_pg - runs a read-only query against your production database. This is where the numbers come from.
• get_schema - looks up the tables and columns, so it does not guess at field names.
• get_data_dictionary - looks up what a field actually means, since a column name alone does not say what it holds.
• get_calcs - looks up the canonical Vorne formula for a metric, so OEE means the same thing here as everywhere else in the suite.
• save_memory and recall_memory - store and read back notes about how you work. See What Advisor remembers below.

A question that needs the schema, the dictionary, and a query will show all three, in the order it used them. Building a chart or a table has no row of its own: you get the chart or the table itself instead.

Charts are drawn from the rows the query returned:

• Bar for comparing categories, like OEE by device.
• Line and area for change over time, like availability by day.
• Pie for proportions, like downtime split by reason.

Charts carry a legend and hover detail on the data points, and usually a title. Ask for a type by name if you want a specific one - "chart that as a line" - otherwise Advisor picks the one that suits the data.

When a result has more than about ten rows, Advisor builds a sortable table instead of writing the rows into the answer text:

• Click a column header to sort, and click again to reverse it.
• Pages of 15 rows, with next and previous controls beneath.
• Formatted values where they make sense, so percentages read as percentages and money reads as money.

If you want a different cut of the same data, just ask: "sort by downtime hours", "only the lines in Area 2", "add the job number".

One query returns at most 500 rows, and charts and tables are built from those rows. For anything wider, ask for a summary or a daily total rather than the raw rows.

Everything you ask lives in a conversation, and your recent conversations are saved in the list on the left, most recently used first.

• New Thread starts a fresh conversation.
• A conversation is named automatically from your first question, so the list reads like a list of questions rather than "Chat 1".
• The more menu on a conversation holds Rename, Archive and Delete.

Rename replaces the auto-generated title in place: type over it and press Enter, or press Escape to leave it alone.

Archive clears a conversation out of the main list without losing it. Archived conversations collect under Archived at the bottom of the sidebar, and Unarchive puts one back.

Delete removes a conversation and its answers for good. Nothing about the underlying production data changes.

Working with an answer. Hover an answer and a small row of controls appears under it:

• Copy puts the answer's text on your clipboard.
• Export as Markdown, under the More menu, saves that text as a file you can drop into a report or a shift handover.
• Refresh asks Advisor to answer the same question again. Useful when a query failed or the answer was thin.

Copy and Export take the written answer only. A chart, a sortable table, or the tool trail underneath is not included, so screenshot those if you need to keep them.

On your own messages, Edit lets you re-ask with better wording - add the device you meant, or narrow the dates. Advisor answers the edited question, and the earlier exchange stays in the conversation.

Across conversations, Advisor keeps short notes about how you work: the lines you usually ask about, your role, the shift pattern you care about, the questions you come back to.

It deliberately does not remember numbers, results, or conclusions. Production data changes by the hour, and a remembered number would be wrong almost immediately. Every answer is queried fresh.

You can steer it directly: "remember that I look after the packaging line". A note it has already saved cannot be removed from inside a conversation, so ask your support team if you need one cleared.

Some things Advisor will not do, by design:

• It does not guess. If the data will not support an answer, it says it does not know rather than offering a plausible number. That includes forecasting: if it cannot back an answer with data in your database, it says so.
• It does not tidy up your data. If a result looks impossible - an OEE far above 100 percent, negative counts, a timestamp in the future - it flags what looks wrong and still shows you what is actually stored, rather than quietly correcting it.
• It stays on production topics. OEE, downtime, quality, jobs, parts, devices, shifts, and questions about what your data holds. It declines anything off-topic.
• It does not assess people. Advisor will not compare individual employees or answer HR-style questions about performance.

The button in the top-right of the header switches Advisor between light and dark. Everything renders both ways, including charts and tables, so use whichever suits your screen and the light where you work.