LTLINE TWIN
●   SIMULATED DATA
CUSTOMER DEMONSTRATION

Bottling & packaging

Loading your line…

COUNT POINT OUTPUT0Filler · product units
CURRENT RATE0/ minAt the count point
MACHINES RUNNING0 / 6Ready to start
ACTIVE FAULTS0No faults injected
▪   LIVE DIGITAL TWIN 00:00
Drag to orbit · Scroll to zoom · Click to select
RunningFaultStarvedBlockedStopped
Representative machine models
COUNT POINT RATE

Production through the demonstration

Last 5 minutes · simulated rate00:00
SESSION TIMEMACHINEEVENTALARM ID
LINE DESIGN

Build your customer's line

Position the blocks to match the site. OUT → IN defines product flow.
0 machines

Splits share product evenly unless you specify percentages. Merges combine incoming product.
INTEGRATION

Connect to PerformOEE

LINE TWIN→AZURE IoT HUB→PerformOEE

Messages accepted by the transport are reported below. Confirm their arrival and interpretation in PerformOEE.

Match these to the IoT Gateway agent on the customer's Kepware server. Narrow sends only tags whose value changed, each with its own sample time, buffered between publishes. Wide sends every tag on every publish.

Device symmetric key or SAS token. Credentials are never saved with a line.

Connects the way the Kepware MQTT Client agent does: client ID = device ID, username = <hub>/<device ID>, password = device SAS token, topic as above. Only the JSON body is sent, with no extra message properties.

Remembered in this tab for reloads. Clear the field to forget it.

Signal mapping & authentication

Kepware modes emulate the IoT Gateway Standard Template: {"timestamp":<publish ms>,"values":[{"id","v","q","t"}]}. timestamp is publish time; t is the tag's sample time. Edit each machine's tag prefix in the builder. State is text; counts, Speed and AlarmID are numbers; Running, AlarmActive and Alarm01–05 are Booleans.

Azure uses a device SAS token over TLS, generated for the session from a symmetric device key or supplied directly. Certificate authentication and Kepware Advanced Templates are not configured in this version.

Match tag names and types to your PerformOEE configuration. A Hub connection alone does not verify that mapping.

Preview only. No data is being sent.
Messages accepted0
Session remaining30:00
Last accepted—

One presenter per connection · 30 minutes / 1,800 messages maximum. Simulation continues when disconnected.
WORKSPACE

Your lines

Start with a reference line
MODEL CATALOGUE

Choose what your team presents

Remove models from the catalogue or replace their appearance with a better GLB. Existing line instances retain their models until you choose to update them.

From line to insight

  1. Build the line. Place equipment, set machine speeds and buffers, connect flow and choose a count point.
  2. Run and demonstrate. Inject a fault. Downstream machines consume their buffers; upstream machines continue until their buffers fill.
  3. Connect when ready. Match tag prefixes and payload format, then connect your demonstration IoT device.
  4. Show the result in PerformOEE. Compare count gaps, machine states and alarm numbers with received data.

Rates and buffers use one common product unit. Packaging conversions, rework and assembly bills of material are not modelled. Models are representative; import OEM CAD converted to GLB for the customer's visual identity.

Use server save or a line export to share your work. Connected simulations run on the server, so you can switch to PerformOEE. Use Disconnect when finished; a live session ends automatically after 30 minutes. Offline preview pauses when hidden.