Getting started · chapter 01 of 08

Understand how InfiIoT turns a signal into an action

Start with the operating outcome, then follow the same identity and data through every part of the platform. This prevents a first dashboard from becoming a disconnected demonstration.

Practical guideOutcome: A one-page model of the asset, its signals, the people who use them, and the first action the system must support.
Chapter outcome

A one-page model of the asset, its signals, the people who use them, and the first action the system must support.

01.1

The platform model

InfiIoT treats the connected asset as the stable object. A device represents the physical or logical source, variables describe measured or calculated values, and dashboards provide views over that shared model.

Events, reports, predictions, and integrations should reuse the same asset and variable identities. Avoid creating a separate copy of the equipment record for every screen or workflow.

  • Asset: the equipment or system the business recognises.
  • Device: the connected endpoint or gateway associated with that asset.
  • Variable: a measured, calculated, state, or location value with units and time.
  • Dashboard: a view designed for a particular operating question.
  • Event: a condition that creates an owned notification or action.
01.2

Follow one signal end to end

The fastest first implementation uses one real signal and proves that its meaning survives transport, storage, display, and action. Expand only after that path is trustworthy.

  1. 01Name the equipment and the decision the signal should support.
  2. 02Define the variable, unit, valid range, and timestamp source.
  3. 03Send one known value and verify it against the source.
  4. 04Display the current value and the useful operating trend.
  5. 05Create one event and confirm acknowledgement and recovery.
01.3

Keep the first scope deliberately small

A useful first pass is one product, one device or gateway, a handful of variables, one dashboard, and one event. That is enough to test identity, transport, time, units, access, and operating ownership without hiding problems inside fleet scale.

Completion check: another team member can identify the asset, explain the data path, and name who acts when the first event occurs.

Connected-product assessment

Bring one product. Leave with a clear next step.

Use 30 minutes to test the fit around one product and one blocked decision. If there is a fit, we will outline the two-week Product Blueprint.

30-minute fit callOne productNo prepared deck