Type: how-to · Last reviewed: 2026-07-10
Applies to: Pulse Historian · Pulse Copilot (application UI)
🚧 Scaffold — pending frontend access. The steps below are inferred from the APIs and product copy, not yet verified against the live UI. Steps marked
[VERIFY-UI]and every🖼️ [SCREENSHOT: …]/📊 [GRAPH: …]placeholder need a human with the running app to confirm and fill in.
Goal: view your plant's live data and alarms in the Pulse app, and ask Pulse Copilot a question in plain English — without touching an API.
Prerequisites:
https://<plant-server>:3030) and a user account.Uses the canonical unit acme-power / plant-1 / boiler-2.
Open the app URL and sign in with your email and password. Your role (admin / read-write / read-only) controls what you can change. [VERIFY-UI]
🖼️ [SCREENSHOT: login screen]
The left navigation follows the scope hierarchy organization → site → unit — expand acme-power → plant-1 → boiler-2. [VERIFY-UI]
🖼️ [SCREENSHOT: org→site→unit navigation tree]
Open the unit's dashboard to see live trend panels for its tags (e.g. steam_pressure, steam_temp). [VERIFY-UI]
🖼️ [SCREENSHOT: boiler-2 dashboard with trend panels]
📊 [GRAPH: example steam_pressure trend over the last hour]
Open the alarms view to see active alarms raised by monitor rules; select one to see detail and acknowledge it. [VERIFY-UI]
🖼️ [SCREENSHOT: alarms list with an active alarm selected]
Open the Copilot chat and ask in plain English, e.g. "Why did boiler-2 steam pressure drop in the last hour?" Copilot answers with the trends and context behind the answer (powered by Clarity AI). [VERIFY-UI]
🖼️ [SCREENSHOT: Pulse Copilot chat with an example question and answer]
You can see live values updating on a dashboard, and Copilot returns an answer grounded in your unit's data.