Appearance
Smart Assist: using the wizard
Last updated
The wizard has five steps, shown along the top: Select Device, Machine Info, Scanning, Review, Done.
Step 1 — Select a Device
Cards list every enabled device except Local Tags, with its address and driver. Click one, then Next. If the list says "No enabled devices found. Add a device first.", add or enable the device on the Devices page first — Smart Assist needs a device that is connected and returning tags.
Step 2 — Machine Information
| Field | Default | What it does |
|---|---|---|
| Machine Purpose | CNC Milling | Chooses which roles are looked for and which keywords count extra. Options: CNC Milling, CNC Turning, CNC Grinding, CNC EDM, Laser Cutting, Injection Molding, Press / Stamping, Extrusion, Assembly, Welding, Packaging, 3D Printing, Heat Treatment, Robot Cell, Testing / Inspection, Other |
| Average Cycle Time (seconds) | 60 | Sets how long a Quick (auto) scan watches live values: 2.5 × the cycle time, up to 15 minutes. 60 s gives a 2½-minute scan; any cycle time above 360 s gives the 15-minute maximum, and the page suggests Extended (durable) instead. It has no other effect |
| Monitoring Duration | Quick (auto) | Quick (auto) watches for 2.5 cycles while you wait. Extended (durable) records to the historian for 5 min, 15 min, 30 min (default), 1 hr, 2 hr or 8 hr — see Extended observation |
| Tag Keywords (optional) | empty | Comma-separated words in your tag names, e.g. Weld, Leak, RPM, Load, Gage, Weight. A tag whose name contains one is given a role guessed from its own name |
| Dashboard Name | "device name Dashboard" | Name of the dashboard to create. Required |
| AI-Enhanced Analysis | Off | For Quick (auto) scans: offer an AI check of the results before you create the dashboard. No data leaves the appliance until you confirm on the Review step. Extended observations always offer deep AI analysis instead |
Next needs a purpose, a cycle time above 0 and a dashboard name. It starts the scan.
Tip: Run Smart Assist while the machine is producing. A machine sitting idle gives counters that never count and cycles that never cycle, and the result falls back to guessing from tag names.
Step 3 — Scanning
A progress display shows the phase (Browsing available tags..., Monitoring live data..., Classifying tags...), elapsed time and how many tags were found.
- Demo, Simulator, MTConnect and Fanuc FOCAS devices have known tag layouts, so their results are ready at once. Machine purpose, keywords and cycle time are not used for them.
- Other drivers (PLCs, OPC UA, Modbus, MQTT …) are browsed, then up to 500 candidate tags are read once a second for the scan period.
- A quick scan runs in the appliance's memory and is lost if the appliance restarts. Its results stay available for 30 minutes after monitoring ends.
- Back leaves this step. For a quick scan it returns to Machine Information and the scan is abandoned. For an extended observation it returns to step 1 and the capture keeps running — reopen it from Extended observations there. Stop & analyze now ends an extended capture early and analyzes what was recorded.
- If the scan is refused (for example "Insufficient permissions") or fails, the page returns to Machine Information with the error shown.
Step 4 — Review
The Detected Tags table lists what was found ("N tags detected — review and adjust").
| Column | Meaning |
|---|---|
| Checkbox | Whether the tag goes on the dashboard. All start ticked |
| Tag Path | The device tag. A sparkle marks a tag the AI changed; raw I/O marks a bare hardware address ("Bare hardware address — usually aliased to a more readable tag"); "+ N duplicate tag(s) collapsed" means identical tags were merged into this one |
| Role | What it was classified as. Change it with the dropdown |
| Why | The evidence, e.g. name "PartCount" matched · increments monotonically. (name only) means the behavior did not confirm the name |
| Confidence | high, medium or low |
| Widget | gauge, value or status — the widget it will get. It follows the role |
| Value | The current value |
Changing the Role also changes the Widget to the one that role gets: a tag changed from Unclassified to Temperature becomes a gauge.
Above the table, depending on the mode, you may see Machine Insights, the Enhance classification with AI? card or the Deep AI analysis card — see How tags are classified and Extended observation. Rescan discards the results and runs the same scan again (an extended observation starts again from the beginning).
Untick anything you do not want and press Create Dashboard.
What Create Dashboard does
- Creates a tag subscription for each ticked tag that is not already subscribed: polling 1000 ms, enabled, history on, display name set to the role (Machine Running, Part Count, Spindle Speed …).
- Creates a dashboard (light theme) with one widget per ticked tag, two per row, each half the width of the grid.
- Configures each widget from its role:
| Role | Widget and settings |
|---|---|
| Spindle Speed | Gauge 0–15,000 RPM, warning 12,000, critical 14,000 |
| Spindle Load | Gauge 0–100 %, warning 70, critical 90 |
| Temperature | Gauge 0–500 °C, warning 400, critical 480 |
| Pressure | Gauge 0–3,000 psi, warning 2,500, critical 2,800 |
| Force | Gauge 0–1,000 kN, warning 800, critical 950 |
| Power | Gauge 0–10,000 W, warning 8,000, critical 9,500 |
| Torque | Gauge 0–500 Nm, warning 400, critical 480 |
| Running, Coolant | Status: green (or cyan) for true/1, gray for false/0 |
| Mode | Status badge: AUTO green, MANUAL amber, MDI blue |
| Alarm | Status badge: empty = No Alarm (green), anything else = ALARM (red) |
| Pass / Fail | Status badge: pass/PASS/ok/OK/1/true green; fail/FAIL/NG/0/false red |
| Part Count, Reject Count | Value in "parts" |
| Feed Rate, X/Y/Z Position, Cycle Time, Speed, Voltage, Flow Rate, Measurement | Value with unit (mm/min, mm, s, m/min, V, L/min, mm) |
The gauge ranges and units are generic starting points, not read from the machine. Edit them on the dashboard to match your equipment — a press measured in tonnes is not in kN. See Dashboards.
- Records which roles you accepted (ticked) and rejected (unticked). Later deep analyses for the same driver type and machine purpose use these as examples.
Step 5 — Done
"Dashboard Created!" with the widget count. View Dashboard opens it; Run Again returns to step 1 and clears the previous run's results, AI recommendations and banners.