Plant assistant mockup: operator, management, sales
Deploy test site / deploy (push) Successful in 24s
Deploy test site / deploy (push) Successful in 24s
docs/plant-assistant.html (test site /demos/plant-assistant/): the plant assistant on vinyl-ai as three roles see it. Operator at the C1 press kiosk in Thai or English with push to talk (non-fill rejects explained from cycle rows, lot change and press hall humidity, the stamper change procedure quoted from the approved version, a lot on hold, a refused price question, a safety question answered word for word); management at a desk (output and yield per press against the plan basis, steam per record against scale.md, orders at risk, the weekly note, payroll refused); sales on a phone (order status and ship window, repress feasibility from archived mothers and the standby calendar, repress leads, a test pressing status, fans' addresses refused). Each answer carries numbered sources; the side panel shows the tool calls (ERPNext as the asker's role, the PostgreSQL replica, VictoriaMetrics, documents, event log) on premises with the internet not used; action buttons create drafts only. Deep links #role=<role>&q=<id>, light and dark theme. Invented data; names match the factory console demo. plant-assistant.md: mockup link; sales and customer service row in "Who asks what"; sales drafts (quotation, CRM opportunity, message). README, site index and site/build.sh link and publish the page.
This commit is contained in:
1 parent
3d9bb9af53
commit
22f04ee9a1
5 files changed
+825
-3
No files matched your search
+12
-3
@@ -20,6 +20,13 @@ asking may see, it can draft but never submit a record, and it never
|
||||
touches a machine. It runs on site on an open-weights model, so it works
|
||||
when the internet does not.
|
||||
|
||||
**Mockup.** [Plant assistant mockup](plant-assistant.html) (test site
|
||||
`/demos/plant-assistant/`) plays the three main uses: an operator at the
|
||||
Classic's kiosk asking in Thai by push to talk, management at a desk and
|
||||
sales on a phone. Each answer carries its sources, the tool calls run
|
||||
beside it, drafts stay drafts, and the refusals the test set expects are
|
||||
shown. Invented data.
|
||||
|
||||
## Who asks what
|
||||
|
||||
| Who | Typical questions | What it uses | Where |
|
||||
@@ -30,7 +37,7 @@ when the internet does not.
|
||||
| Maintenance | "Alarm history of boiler B-1 this month." "Hours since the last oil change on the Duplex hydraulics?" "Page of the manual for the chiller's low-pressure fault." "Is the seal kit in stock?" | alarm history, run hours, ERPNext Asset Maintenance and stock, the vendor manuals attached to the Asset | workshop kiosk, phone |
|
||||
| Cutting and galvanics | "Current density in cell 2 over the last father." "Which mothers of POY013 have sets left?" | rectifier and bath series, metal-part serial numbers | room kiosks |
|
||||
| Management | "Yield and effectiveness per press this week, and why the Classic dropped." "Energy per record against the plan." "Orders at risk of missing their date." "Which gates are waiting on customers?" | ERPNext reports, the machine-data store, the design figures in this repository | office, phone |
|
||||
| Customer service | "Where is order SO-0231, and when will it ship?" | the same records the customer portal shows | office |
|
||||
| Sales and customer service | "Where is order SO-0231, and when will it ship?" "Can we take a 500-copy black repress by the 20th?" "Which customers have metal in the archive and no order for six months?" "What can I tell the customer about their test pressing?" | the records the customer portal shows, the price list, archived metal parts and their stamper sets left, the standby calendar, CRM; never fans' personal data from campaigns | office, phone |
|
||||
| New staff and trainees | "Why must labels be dried before pressing?" | procedures and the training material, never live customer data | training mode |
|
||||
|
||||
## What it knows
|
||||
@@ -97,7 +104,9 @@ the floor's own questions.
|
||||
[production timeline](production-timeline.md)), so the plan learns
|
||||
from the plant.
|
||||
7. **Drafts records**: a Non Conformance, a maintenance request, a
|
||||
ToDo, a revision of a Quality Procedure. A person reviews and submits.
|
||||
ToDo, a revision of a Quality Procedure, and for sales a quotation, a
|
||||
CRM opportunity or a message to a customer. A person reviews and
|
||||
submits or sends.
|
||||
|
||||
## What it never does
|
||||
|
||||
@@ -113,7 +122,7 @@ the floor's own questions.
|
||||
([worker safety](worker-safety.md)).
|
||||
- **Sees more than the asker.** Every tool call runs with the asker's
|
||||
ERPNext role: an operator sees the job, not the customer's price;
|
||||
customer service sees orders, not payroll. The client audio vault and
|
||||
sales sees orders and prices, not payroll or fans' addresses. The client audio vault and
|
||||
customers' artwork are never indexed. Questions that must be refused
|
||||
are part of the test set below.
|
||||
- **Answers from memory.** A figure without a query or a document behind
|
||||
|
||||
Reference in new issue
Block a user