Use case
VirtualPlant first, then adapt
Before a real device is connected, a tuning can still be configured and evaluated on the built-in virtual plant.
This page describes current capability, not a delivery. The illustration is a placeholder. Replace it later with a licensed lab or bring-up photo.
What the site does today
While the device is not connected, or while the point table is still changing, people can only discuss the next parameter set on paper. They cannot turn plan, act, wait, and observe into a repeatable experiment.
What the product keeps
VirtualPlant replaces the physical process with a synthetic map for bring-up and test evaluation. The same platform-layer software later connects to that site’s adaptation layer, without changing platform code. The public demo will use VirtualPlant and will not connect a real plant.
Which steps this uses
- Plan: the same algorithm configuration is used on the virtual plant and later on the live control interface.
- Act: write-out goes to VirtualPlant during bring-up, then to the site control interface after adaptation.
- Wait: the virtual plant still has to settle and take effect before the measurement window opens.
- Observe: the same objectives and constraints are evaluated, so bring-up and the live site can be compared.