Demo Dataset
OpSee ships an optional evaluation dataset: the Riverside Brewery (a small ISA-88 site tree with one bottling line, live OPC-UA simulator tags, two reason trees, materials, floor plans, a running production order, six Kaizen cards and a pre-built OEE cockpit). It is loaded either by the installer's --demo-data flag or from the first-login wizard.
Since the demo is just data in your database, you can also remove it or re-create it later, without reinstalling.
Where
Navigate to Admin → Platform Settings → Status. The Demo dataset card sits below the host-system section. It is only shown to users holding perm:system:admin.
The card shows whether the demo is present, the state of the DEMO_SEEDED flag, and one row per component with its row count and whether it can be removed right now.
Components
| Component | What it contains | Removed by default |
|---|---|---|
| History | Tag values, OEE events, segments, alarms and other time-series rows generated for the demo tags, line and orders | yes |
| Production orders | PO-DEMO-0001 / PO-DEMO-0002 and their execution segments | yes |
| Kaizen cards | The six seeded PDCA cards, comments and history | yes |
| Equipment | The Demo Brewery tree, its OEE configuration, plans and regions, tag and material links | yes |
| Tags | The six DemoBrewery_* tags and their sources | yes |
| Cockpit | The shared Demo Brewery OEE dashboard | no |
| Simulator server | The nodered-sim OPC-UA server row | no |
| Reason trees | Demo Brewery Downtime and Demo Brewery Waste, and the reasons only they use | no |
| Materials | The brewery material classes and materials | no |
Some components are unchecked by default on purpose: reason trees, materials, the simulator server and the cockpit are often reused for a customer's own lines during an evaluation. Removing the equipment or tags always removes their history as well (the history rows reference them).
Removing
- Click Remove….
- Tick the components to delete. Rows that cannot be removed are greyed out and explain why, for example reason tree "Demo Brewery Downtime" is bound to the availability config of "Line 3". Unbind or delete the referencing item first, then reopen the dialog.
- Check the summary line ("will delete N rows in M tables"), type
remove demoand confirm.
Deletion runs in the background. Large history is deleted in batches so ingestion is not blocked; the card shows the step and the running counts, and reloads when the job is done. When the equipment component is removed the DEMO_SEEDED flag is reset, so the wizard's Seed demo action becomes available again.
Re-creating
Re-create removes every component that is currently removable and then runs the bundled seeds again. Use it after an upgrade to pick up newer demo content (for instance the four-level reason trees and updated floor plans introduced in a later release). If any component is blocked, the dialog says which and nothing is deleted.
Kaizen cards created by the seed are owned by the admin who ran the action.
Provenance
OpSee keeps a small registry of which rows belong to the demo (m_demo_seed_row). Removal deletes only registered rows and never anything created by hand. Installs seeded before this registry existed are back-filled automatically on upgrade by matching the demo's fixed names (the Demo Brewery subtree, DemoBrewery_* tags, nodered-sim, the two trees, the material codes, the cockpit name).
Every seed, remove and re-create action is written to the audit trail.
Related
- Closed release deployment — how the demo is bundled and the
--demo-dataflag - Kaizen Board