Insights
Computed from data already recorded — nothing here needs extra tracking. Ordered by what usually wants acting on first.
Who may need a call
A customer rarely phones at the first sign of trouble — they ask the assistant, read a document, ask again, involve a colleague, and call once production is affected. Every step before that call is already recorded. This surfaces the pattern while it is still cheap to help.
Escalations sent
What was sent, to whom, and whether the mail provider accepted it. An alerting path that has never been exercised is an assumption — use the test button after any change to the recipient list.
Corpus additions
MillWise does not learn from questions. This is the only way something worked out in a conversation reaches a customer — and it only gets there when you approve it. Approved entries are live immediately; export folds them into the built corpus permanently.
Process data sent by customers
What a customer said was wrong, captured when they started the upload. The
file itself is in WorkDrive — the portal never touches the bytes — so each
row links to that plant's folder.
A row with no matching Zoho notification means the description arrived and the
file did not: a plant firewall can block the upload, and so can closing the tab.
"Our alert sent" is NOT proof the file arrived. It says only that our own
notification email was accepted, at the moment the customer pressed Continue — before
any bytes reach Zoho. This screen cannot see WorkDrive at all. To know a file landed,
open the plant's folder and look; Zoho's own arrival mail is a second witness but
it lands in Trash, which a default mail search excludes.
Launchpad
Everything outside this console — customer hubs, mill HMIs, backends and third-party dashboards.
Shipping portal
TrendWise Downloads
Current build of TrendWise (the desktop signal-trend viewer built in
pws-clx-verifier) and its user guides. A Windows or macOS build link stays live
for 30 days after it is published; past that the download is refused
here and by the server. Nothing is deleted from storage — re-publish the build
to reset the clock. Published with tools/publish_trendwise_build.py.
| Platform | File | Version | Published | Size | Status |
|---|
Full downloads on downloads.processwise-solutions.com
Everyone on any customer's approved list can sign in there. They get the demo installers and manuals by default; the addresses below get the full ones. Until demo items are published, demo users see only the samples (every full build names Arconic, so it never falls back to them). The simulator samples are shown to everyone. PWS staff see everything.
Demo activations -- one computer per person
A demo build activates on the first computer it is opened on; the same computer activates again (a reinstall or a newer build), and any other computer is refused and listed under Refused below -- a demo being shared. Only the people listed here can activate at all. Release clears a person's computer so their next one activates: when they genuinely change computers, or after you test their build.
Refused (a second computer)
All time
Adoption — every customer, every surface
Counted from verified activity only — a signed-in person, not a pageview. Unverified hits are overwhelmingly scanners, and counting them would read as adoption. The denominator is people provisioned: “2 of 7 have ever opened it” is the number that says whether a rollout landed.
People — new arrivals and recent activity
Verified activity only, same basis as the grid above. A session is activity by one person with no gap longer than 30 minutes, derived from timestamps — usage_events carries no session id. Engagement time is summed dwell where events report it, otherwise the measured span of the session.
Sessions
Sessions & questions
Geography (sessions)
Device class
Operating system
Browser
Per-user activity
| User | Sessions | Questions | Cost (USD) | Last seen |
|---|
ProcessWise staff & assistant profiles
This is not where customers get access. Customer sign-in is granted on the Customer tab (access requests) and in People & Access; those people never appear here. This table decides exactly two things: who is a ProcessWise admin (tier “admin”, enabled), and which corpus View As falls back to for a staff address that has no customer record. Tier “admin” grants every plant — never set it for anyone outside ProcessWise.
Add new user
All users
| Name | Tier | View-As profile | Status | Last seen |
|---|
User detail
Lifetime totals
Last 30 days — sessions / questions / cost
Activity heatmap (hour × day, last 90d)
Countries / Devices
Recent sessions (last 50)
Recent events (last 100)
Recent Q&A (last 50)
Domain map
Every hostname, the Pages project serving it, and the store behind it.
Navy is PWS-internal, steel is customer-facing, red marks a gap or an open
decision. Regenerate with
shared-knowledge/diagrams/build_domain_map.py — it is built
from live configuration, so it goes stale if the estate changes and the
script is not re-run.
Loading the map…
Health — credentials and bindings
Every key and binding this project depends on, tested against the real provider and reporting the provider's own error. Nothing here sends email or writes data — Resend is validated by listing domains, Anthropic by a one-token call. To actually send, use Escalations → Send test alert.
Estate — the whole domain
Every customer side by side, plus what this view cannot see and where that data lives. A dashboard that quietly omits half the estate reads as “all quiet” when it means “I cannot see it”.
Cross-customer view. Every plant is on this screen at once, and a drill-down puts one customer’s question text beside the others’ numbers. Do not screenshot or share it with a customer — use the Customer tab for anything they will see.
Customer
Everything for one customer in one place — who they are, what they asked, what they read, and who is actually active. PWS activity excluded unless shown.
MillWise — what each customer's assistant is configured with
Read-only. The system prompt is what keeps one customer's assistant from
discussing another, so it lives in version control rather than in a field
anyone can edit at 11pm. Changing it means an edit to
functions/_lib/millwise-plants.js and a deploy.
MillWise — conversations & status
View as a user
Open a customer hub rendered exactly as this person would see it — including someone who has never signed in. Read-only: every write is refused while active, and the session is recorded against you, never against them.
Activity — all customers, all assistants
Merges portal usage (pageviews, doc opens, sign-ins) with assistant questions. Rows marked unverified predate server-verified identity and must not be read as attributed to a person.
Recent Q&A
Unauthorized attempts
Refusals are never hidden by the staff filter. A PWS address being turned away is an access fault on our side, not our own traffic inflating a count.
| Time | Reason | Country |
|---|
Recent activity (last 50 events)
| Time | User | Event | Country |
|---|