Demo path (demo-food)

Use factory code demo-food, username admin, password demo-food-admin only on systems that still use demo passwords. If ops created the factory in production, use the one-time password from create.

Keep the DEMO pill visible. Say the word simulator out loud.

25-minute script

1. Sensors (/) — live cards, machines, lines. Trigger a scenario only if admin on a demo plant (cold-room, vibration). Explain that live plants do not have these buttons.
2. Alerts — ack as operator would; resolve as maintenance.
3. Machine page — state, attached sensors. Do not invent a fault if the machine is idle.
4. Production + OEE — if OEE is N/A, say insufficient evidence. Never round a missing value to 80%.
5. Energy — intensity needs production and kWh. Zero production is not 0.00 kWh/kg.
6. Command Center — plant operational picture.
7. Executive — admin only. If you are in operator, you will not see it. Switch or use ops-enter.
8. Copilot — ask “What is OEE for this factory today?” Expect evidence or an insufficient answer. Copilot must not invent KPIs.

What not to click in a customer demo

• Token rotate unless you can restore it
• Pause factory
• Switching telemetryMode to live on a shared demo
• Fabricating Excel exports with typed numbers

If the room asks “does this talk OPC?”, open Connect and say: connector types exist; native vendor drivers are not in the box; we land on MQTT/HTTP.