# Your First Inference

> Seed a model, enable a datasource, and watch live predictions appear on the dashboard.

After install, run one end-to-end loop: **seed a model → enable a datasource → see
predictions**. This is the quickest way to confirm the runtime is working.

Each step below has a dedicated guide if you want the full detail. This page is the
happy-path walkthrough.

1. ### Sign in

   Open the dashboard URL printed during install and sign in with your admin account.

2. ### Upload a model

   Go to **Models** and upload your ONNX model. Note its **window size** and
   **feature count** — they must match the datasource you pair it with.

   See [Deploying Models](/configure/models/) for formats and versioning.

3. ### Add an input datasource

   Go to **Datasources → Input** and add a source — for example an MQTT topic or an
   OPC-UA endpoint. Map each sensor tag to a model input channel, and set the
   **window size** to match the model.

   See [Connecting Input Datasources](/configure/input-datasources/) for the full
   per-protocol walkthrough.

4. ### Pair the model with the datasource

   On the datasource, pair the model you uploaded. The platform runs a compatibility
   check — `window size × feature count` must agree on both sides. If it fails,
   adjust the datasource window size or regenerate the model.

5. ### Enable, then start streaming

   Toggle **Enable** on the datasource row. Enabling validates the configuration,
   loads the paired model, and connects the adapter — but it does **not** start
   streaming yet. Click **Start** to begin inference.

   
**Enable and Start are two steps**

   Enable prepares the runtime (loads model, connects the source). Start begins the
   data stream. Only one input datasource can be enabled at a time — enabling a new
   one disables the previous.
   

6. ### Watch predictions

   Open the **Dashboard**. Within about 20 seconds (once the first window of samples
   arrives) the predictions card updates in real time, and the sensor cards show
   live readings.

## Inspect results

The monitoring view shows latency (p50 / p95 / p99), throughput, error rate, and the
active execution provider. See [Monitoring](/operate/monitoring/) to read the KPIs.

## If something goes wrong

- Pairing rejected, datasource won't enable, or no predictions appear — see the
  [Troubleshooting](/troubleshooting/) runbook.

## Next steps

  - [Send results out](/configure/output-datasources/) — Write predictions back to a PLC or broker.
  - [Monitor the runtime](/operate/monitoring/) — Latency, throughput, and drift.