UnitedRhino 联犀
Book a demoStart now

IoT / Foundation

Put device data into the interfaces people actually use.

Reuse platform data in business dashboards through editor, component bindings, preview, and publishing, with a path to digital twins.

IoT SIM guide ↗Back to the foundation →

THE CUSTOMER PROBLEM

Start with the connectivity management problem.

Filling a screen with charts is easy. Helping users find the right device, understand a field, and take an appropriate action is harder. Visualization must explain how a view is edited, where data comes from, what interactions do, and how a published view is updated.

MECHANISM / REASON / TRADE-OFF

See how the capability works through the interface.

01

The editor lays out a view; data sources provide values

Canvas, components, and layers organize the interface. IoT bindings select devices and thing-model properties, while supported data sources can organize queries.

Choice and trade-off
Components do not automatically understand every field. Confirm interfaces, scope, and refresh behavior.
02

Verify bindings before interaction and publishing

Editing, preview, and publishing are separate stages. Component events and page interactions follow their configuration; check query permissions, empty values, and state updates.

Choice and trade-off
A dashboard does not replace business-system authorization. Public display capability does not make all business data public.
03

A digital twin adds spatial relationships, not just 3D

A 3D scene can link models, points, devices, and data state. Development tools support integration; see the digital-twin product page for details.

Choice and trade-off
A static model is not a complete digital-twin delivery. Check template version, fields, and runtime environment.
Configuration template editorA historical test-template editor from the documentation site. Its charts are template content, not measured field energy.

A CONCRETE EXAMPLE / MECHANISM EXAMPLE

From a temperature field to a deliverable dashboard

An editor and binding workflow example. The screenshots show separate documentation interfaces, not one recorded publishing session.

  1. Confirm the business layout and devices to display
  2. Bind thing-model fields and verify units and missing-value states
  3. Preview interactions and access scope, then publish as agreed

READY TO INTEGRATE

Confirm these points before connecting.

IoT SIM guide ↗
  • Devices are connected and their fields are defined
  • Confirm target screen, access roles, and refresh needs
  • For a digital twin, prepare drawings, spatial data, and point mappings

CONTINUE WITH THE FOUNDATION

Explore more of the same foundation.

All cases →

Connectivity and Protocols →

Connect new devices, legacy protocols and gateways; verify both directions.

Device Data and Time Series →

Distinguish latest values, history and aggregate results.

Visualization and Scenes →

Bind device data to dashboards, layouts and spatial views.

Back to the IoT overview →