MatrixIQ User Manual

MatrixIQ is an industrial SCADA & IoT platform for energy monitoring and reporting. It connects to field devices (PLCs, energy meters, sensors) over standard industrial protocols, collects their data in real time, stores it, and lets you build live dashboards, alarms, automation and reports — all configured from the web, with no coding required for everyday use.

What you can do with MatrixIQ

• Connect to devices using Modbus TCP/RTU, OPC-UA, BACnet, DNP3, IEC-61850/104, Siemens S7, Allen-Bradley, Generic MQTT and more.
• Monitor live values on customizable drag-and-drop dashboards built from 80+ widgets (gauges, charts, tables, status indicators…).
• Automate with scripts, schedulers and rules that react to tag values.
• Alarm & notify via alarm rules, escalation, email and app notifications.
• Report with scheduled Excel/PDF reports, downtime analysis and KPIs.
• Manage tickets, integrate with Node-RED & external APIs, and expose data over an OPC-UA server.

Key Concepts

A few terms are used throughout MatrixIQ. Understanding this hierarchy makes everything else easier:

Getting Started

Signing in

Open MatrixIQ in your browser and go to the sign-in page.

1. Enter your Email / User ID and Password.
2. Choose your User Type:
   • Admin — full access to configuration, devices, scripting, users and licensing.
   • User — access to the dashboards and features granted by an administrator. Users get 3 login attempts.
3. Click Sign in.

From this page you can also use Forgot password?, Sign Up (request a new account) and Update Licence (apply or renew a licence key).

The main screen

After signing in you land on your home dashboard. The interface has three regions:

• Left sidebar — the navigation menu, grouped into modules (see below).
• Top bar — the menu toggle and your profile/greeting on the right.
• Content area — the active screen (e.g. Connection Management).

Navigation map

The sidebar groups every feature. This is the map for the rest of this manual:

Connections Admin

A Connection defines how MatrixIQ talks to a system — which protocol/driver it speaks and the transport settings (IP, serial port, broker URL, OPC-UA endpoint…). Everything else — devices, polls and tags — hangs off a connection, so this is almost always the first thing you set up.

1 2 3 4 5 6 7

• 1 Connections menu — under System Configuration in the sidebar.
• 2 Create Connection — add a new connection (name + driver type).
• 3 Type — the protocol/driver of each connection (WT-400, Modbus RTU/TCP, Power Modbus, Generic MQTT…).
• 4 Connection Status — Active / Deactive (whether MatrixIQ keeps the link up).
• 5 Status — the live link state: Online / Offline / None.
• 6 Connection Settings (gear) — open the driver's transport settings (IP/port, serial, broker, OPC-UA…).
• 7 Edit / Delete — the pencil edits a connection's name/status; the bin removes it.

The Connections screen

Open System Configuration → Connections. The table lists each connection with:

Row actions: the red bin deletes a connection, the blue pencil edits its name/status.

Which protocols are available?

The Select Connection Type list is driven by your license — only the drivers your installation is licensed for appear. MatrixIQ ships with a broad set of industrial drivers:

Creating a connection

1. Click Create Connection (top-right).
2. Enter a Connection Name. It is forced to UPPERCASE and may not contain a hyphen (-); names must be unique.
3. Pick the Connection Type from the licensed list (this cannot be changed later — only the name/status can be edited).
4. Set Status to Active (link will be attempted) or Deactive.
5. Save. The connection appears in the list; open its gear → Connection Settings to enter the transport details.

Driver-wise setup — the 3-stop journey

Getting live data into MatrixIQ is always the same three-stop journey — only what you fill in at each stop changes with the driver:

1. Connection — open the door to the network (the protocol + its transport settings).
2. Device — name the unit sitting behind that door (its identity/address on the protocol).
3. Tags — pick the individual values to read from that unit.

Below is one recipe card per driver showing exactly what's unique at each stop. They're also listed under Driver Reference in the navigation menu (click to expand). Common to every device: an optional Template to pre-load its polls/tags, and a Status option (a Status Tag + Check Time) that tracks whether the device is alive.

Modbus TCP & Power Modbus

Modbus RTU

DNP3

MQTT — Generic, WT-400-MQTT, Robustel MQTT

OPC-UA (client)

S7-200 SMART (Siemens)

AB MicroLogix (Allen-Bradley)

IEC-104

IEC-61850

BACnet/IP

Schneider PME (SE PME DB)

WT-400 (WIMAN-400)

Devices & Polls Admin

A Device is a single unit you read from, sitting under a connection (e.g. one energy meter on a Modbus bus). Polls are the read instructions — they tell MatrixIQ what registers to read from that device and how often.

1 2 3 4 5 6 7 8

• 1 Devices menu — under System Configuration.
• 2 Search Devices — filter the list by name.
• 3 Import Device — bulk-add devices from a file.
• 4 Create Device — add one device (connection + name + optional template).
• 5 Device Type — the device model/type (e.g. MFM443, EM6400, PUMP, SOLAR).
• 6 Template Status — Bind (a template is applied) or Unbind.
• 7 Poll / Tag — open the device's polls & tags.
• 8 Row actions — delete, edit, duplicate and export/download the device.

Adding a device

1. Open System Configuration → Devices and click Create / Add Device.
2. Choose the parent connection, give the device a name, and (optionally) apply a template to pre-load its polls/tags.
3. Save. Use the search box to filter devices and the column header to sort by name.

Configuring polls

Open a device → Polls → Create. A poll groups a contiguous block of registers read in one request:

Tags Admin User

A Tag is one data point — one meaningful value such as Voltage L-N or Run Status. Every tag carries a live value, date/time, status (online/offline) and a data type. Most tags read from a device, but not all — a tag's value can also be set internally or computed by a script (see Tag types below).

1 2 3 4 5 6 7

• 1 Tags menu — under System Configuration.
• 2 Totals — Total / Online / Offline tag counts at a glance.
• 3 Search — filter by tag/device name, or type online / offline to filter by status.
• 4 Delete Tags — remove selected tags.
• 5 Value — the tag's current live value (with its Date Time = last update beside it).
• 6 Status — the online/offline indicator dot.
• 7 Parameter — the logical parameter this tag is linked to.

• Tag Management (System Configuration → Tags) shows every tag with totals for Online / Offline and a search box — type a tag/device name, or online / offline to filter by status.
• Per-poll tags are managed from inside the poll; per-device tags from the device's Tags screen.

Tag types

When you create a tag under a device, the first choice is its type — this decides where the value comes from. The tag editor shows different fields for each:

Settings common to device tags

• Tag Name and an optional Parameter link (so dashboards/reports/templates resolve it across devices), plus a Unit label.
• Active — when ticked, the tag's values are saved to the database (historian) for trends and reports; untick to keep it live-only and save storage.
• Write — when ticked the tag is writable (operators/scripts can send values to it); unticked = read-only.
• Alarm thresholds — optional Hi / HIHI / Low / LOWLOW limits (these feed the Alarms module).

Tag data type & register format

Each tag is fundamentally a Number, String or Binary value. For register-based drivers (Modbus TCP/RTU, Power Modbus, WT-400-MQTT) you also choose how the raw registers are decoded — the word/byte order matters and must match the device:

Other drivers offer their own data-type lists in the tag editor, e.g. Generic MQTT → Number/String; AB MicroLogix → Number/String/Binary; S7-200 Smart → Binary/Byte/Word/DWord/DInt/Real; DNP3 / IEC-104 → Number/Binary. The editor only shows the types valid for that tag's connection.

Scaling, units & alarm thresholds

Inside the tag editor you can turn raw register values into engineering units and attach limits:

• Linear scaling — map a raw range (minRaw…maxRaw) onto an engineering range (minScale…maxScale), or apply a simple multiplier and offset. You can even upload a Raw_value,Scale_value CSV for a custom curve.
• Unit — a label (V, A, kW, °C…) shown alongside the value on widgets and reports.
• Alarm thresholds — optional Hi / HIHI and Low / LOWLOW set-points that feed the Alarms module.
• Binary aliases — for Binary tags, give the two states friendly names via True Alias / False Alias (e.g. Running / Stopped).
• Parameter link — bind the tag to a logical Parameter (see Tag alias note) so templates and dashboards resolve the right tag automatically.

Tag Groups Admin

A Tag Group bundles related tags under one name so you can reuse them as a set — in reports, dashboards and scheduled emails — instead of picking the same tags over and over. Open System Configuration → Tag Groups, create a group, and add the tags you want (e.g. "Feeder-1 Electrical" = its V, A, kW, PF tags).

1 2 3 4 5

• 1 Tag Groups menu — under System Configuration.
• 2 Create Tag Group — bundle related tags under one name.
• 3 Tag Groups Name — the group's name (e.g. KWHGROUP).
• 4 Total Tags In Group — how many tags the group contains.
• 5 Edit / Delete — change the group's members or remove it.

Memory Tags Admin

A Memory Tag is a virtual tag not tied to any device — its value is set internally rather than read from a poll. Use them for:

• Setpoints & benchmarks — a target line a chart compares against.
• Computed values — results written by Scripts (e.g. efficiency = output ÷ input).
• Counters & manual entries — shift numbers, batch IDs, operator inputs.
• Testing — drive a widget without real hardware.

Create them under System Configuration → Memory Tags; they then behave like any other tag in widgets, scripts and reports.

1 2 3 4 5 6 7

• 1 Memory Tags menu — under System Configuration.
• 2 Totals — Total / Online / Offline memory-tag counts.
• 3 Search — filter by tag name, or type online / offline.
• 4 Create Tag — add a virtual (device-independent) memory tag.
• 5 Value — the internally-set value (written by scripts, manual entry or calculations).
• 6 Status — the online/offline indicator dot.
• 7 Row actions — delete, edit and duplicate the memory tag.

App Settings Admin

Application-level configuration. The most important item here is the system MQTT broker — MatrixIQ publishes every live tag value to it on a tag_<id> topic, and that is exactly what realtime dashboards subscribe to in order to update instantly. Open System Configuration → App Settings to view or configure the broker and related application tags.

1 2 3 4 5 6 7

• 1 App Settings menu — under System Configuration.
• 2 UserName — the system MQTT broker username.
• 3 Password — the broker password.
• 4 Port — the broker port (live tag values are published here for realtime dashboards).
• 5 Status — Active / inactive.
• 6 Tag Config — configure the application / app tags.
• 7 Edit / Delete — change or remove this configuration.

OPC-UA Server Admin

Besides reading from an OPC-UA server, MatrixIQ can also act as an OPC-UA Server — exposing its own tags so external OPC-UA clients (other SCADA, an MES, a historian) can subscribe to your data. Open System Configuration → OPCUA Server:

1. Create a server endpoint — set its port and security options.
2. Choose which tags it publishes to clients.
3. Save; external clients can then browse and subscribe to those tags.

1 2 3 4 5 6

• 1 OPCUA Server menu — under System Configuration.
• 2 Create Server — opens the server-setting dialog shown here.
• 3 AuthType — Anonymous or User Detail (username/password) for clients connecting in.
• 4 Port — the port the OPC-UA server listens on.
• 5 Active — enable the server.
• 6 Create — save it; then use Tag Config (in the row) to choose which tags it publishes to clients.

Building Dashboards Both

Dashboards (also called Configurable Screens) are the heart of MatrixIQ. A dashboard is a free-form canvas onto which you drop widgets — gauges, charts, tables, buttons, images — and bind each one to your tags. Nothing is hard-coded: you design exactly the screen your operators need.

Creating a dashboard

1. Open Dashboards (or System Configuration → Screen Management) and click Create. Give the dashboard a name. Use Import to load a dashboard that was exported earlier.
2. The new dashboard opens in the builder — an empty grid canvas with a toolbar.

1 2 3 4 5 6

• 1 Dashboard name — the screen you're editing (here IOCL).
• 2 Builder toolbar — Back, Preview (▶), Add Widgets (+) and Save (also Ctrl+S).
• 3 Search — find a widget by name.
• 4 Categories — Trends, Table, Gauge, Tools, Status, Shape, Alarm, Jobs, Analysis.
• 5 Widget thumbnails — click to pick (LineChart, PieChart, DonutChart, HeatMap…).
• 6 OK adds the selected widget to the canvas; Cancel closes the palette.

The builder at a glance

Placing a widget

1. Click Add Widgets to open the palette.
2. Pick a category on the left (Gauge, Trends, Tools…) or type in the palette search box (e.g. “chart”, “gauge”, “realtime”).
3. Click a widget tile — it is added to the canvas.
4. Move it by dragging; resize it from a corner/edge. Right-click a widget for actions such as duplicate and delete.
5. Select the widget and set its Data (which tag) and Style in the properties panel.
6. Click Save.

Widget Library

MatrixIQ ships with 80+ widgets, organized into the categories you see down the left of the Add Widgets palette. The category list is built automatically, so any custom KPI widgets you create also appear here. Below is the full reference.

Gauge visual

Single-value indicators — show one tag as a dial, bar or specialised gauge.

Trends — charts

Time-series and comparison charts (these support both Realtime and Historical data where applicable).

Tools — text, buttons, controls

The largest category — values as text, interactive controls and navigation.

Table

Status & Shapes

Alarm, Jobs, Analysis & AI

Binding & Configuring Widgets Both

Selecting a widget opens its properties, split into Data (what it shows) and Style (how it looks).

1 2 3 4 5 6 7

• 1 DATA / STYLE tabs — DATA binds what to show; STYLE controls appearance (colours, legend, title…).
• 2 tag — bind the tag(s) or parameter the widget displays.
• 3 Tag Alias — show a friendly alias instead of the raw tag name.
• 4 functions — the aggregation for historical data (Average, Sum, Min, Max…).
• 5 timeSpan — the period (Today, Yesterday, Week…).
• 6 type — Realtime (live stream) or Historical (query stored data).
• 7 The widget live-previews on the canvas as you change the settings.

Realtime vs Historical

Most value widgets have a Type switch:

Binding a tag

1. In Data, pick the Tag (on a device dashboard) or Parameter (on a template/screen, so it resolves per device).
2. Optional — enable Tag Alias and type a friendly name to display instead of the raw tag name.
3. For Historical widgets, also set Function, Time Span and Interval (or a From/To range).
4. Set a Benchmark / set-point if the widget supports it — choose a constant value or a tag, and a line colour; a reference line is drawn on charts/gauges.

The configuration controls

The properties panel is generated automatically from each widget's definition, so the same control types appear everywhere:

Templates & Screens Admin

When you have many similar devices, build the dashboard once as a Template and reuse it everywhere. Templates bind to Parameters (logical names) instead of specific tags, so the same screen automatically shows the right values on each device.

Templates

• Create a template (Templates screen → Create), then add one or more Screens to it.
• Design each screen in the builder exactly like a dashboard, but bind widgets to Parameters.
• Import / Export templates as .zip (including images) to move them between systems.

Applying a template

When adding or editing a Device, choose a template; the device instantly gains all of the template's screens, resolved to that device's tags. Update the template once and every device using it follows.

1 2 3 4 5 6

• 1 Templates — under Dashboards → Tools (alongside KPI, Popups, Assets, Predefined Parameters).
• 2 Import — bring in a template as a .zip (incl. images).
• 3 Create — make a new template.
• 4 Template Name — e.g. MFM443, CHILLER, AHU, PUMP.
• 5 Screens — open/manage the template's screens (designed against Parameters).
• 6 Row actions — delete, edit, duplicate and export the template.

Standard Screens Admin

Not every screen needs to be built from scratch. Standard Screens are a fixed catalogue of ready-made screens and reports whose look and functionality are pre-built — you don't drag widgets onto a canvas, you just fill in a short configuration form (a name, the devices/tags/parameters to show, and a heading) and the screen is instantly ready. They're the fastest way to stand up common views.

Adding a Standard Screen

Open Standard Screen Management — it lists every available standard screen with a Configuration (+) action. Click it, fill the short form (typically a Name, the devices / tags / parameters to show, and a Heading / SubHeading) and save. The finished screen is then linked to users just like any dashboard.

1 2 3

• 1 Standard View — under Dashboards (next to Configurable View, Publish, Tools).
• 2 Name — the nine ready-made screens with a fixed look & function (see the table below).
• 3 Configuration (+) — open the short form to set up that screen.

The available standard screens

Dashboards in Action User

These are real examples of finished dashboards — what an operator sees after signing in. Everything here is built from the widgets, templates and standard screens described above; the left menu is the user's runtime menu (Static headings with Dynamic screens beneath, assigned per user).

Energy & electrical monitoring

Industry examples

More example dashboards will be added to this gallery.

Scripts Admin

Scripts let you add custom logic in JavaScript — read tags, do calculations, write results back to tags or memory tags, send emails/notifications, and more. MatrixIQ runs scripts in four different ways, each with its own page under the Scripts menu:

Each type has its own list page (e.g. Interval Script Management). Click Create Script to add one:

1 2 3 4 5 6 7 8

• 1 Script types submenu — Interval, Schedule, Value Change, User Action (and Scheduler below).
• 2 Create Script — add a new script (opens this dialog).
• 3 Script Name.
• 4 Time Interval (m) — for Interval scripts, how often it runs.
• 5 Bind Device — tie the script to device(s) so it can use Parameters / Memory Tags.
• 6 Status — Active / Deactive.
• 7 Create — saves; then open it in the editor.
• 8 JS — open the script's code editor (see below).

Device vs. global scripts

When you create a script you choose whether it is tied to specific devices or runs globally. This changes what you can reference inside it:

• Device script — can insert Parameters and Memory Tags (resolved against the selected devices), so the same script works on any matching device.
• Global script — can insert raw Tags, Tag Groups, Device Names, User Groups and Recipes.

The script editor

Open a script to get a full-screen code editor with four actions along the top:

1 2 3 4 5 6

• 1 Insert Data — drop a tag / parameter / built-in function at the cursor.
• 2 Save Script.
• 3 Test Script — run once; output shows in the log below.
• 4 Back — return to the script list.
• 5 Code editor — write JavaScript (read/write tags, calculations).
• 6 Log panel — print() output appears here for debugging.

Built-in Script Functions

The Insert Data → Function list gives you ready-made async helpers — there are a lot, so they're grouped below by what they do. Each is called with await (e.g. let v = await read('TagName')). The reference categories also appear under Script Functions in the navigation menu (click to expand).

Reading & writing tags

Historical aggregations

Each reduces a tag's stored history over a timeSpan to a single number.

Interval aggregations

The same reductions, but the window is split into interval buckets and a series is returned (one result per bucket) — handy for building report rows or trend arrays.

Alarm set-points

Set a tag's alarm threshold values at run-time (e.g. from a recipe or shift schedule).

Utilities & integration

Email & notifications Licensed

These two appear in the Function list only when enabled in your licence.

Schedulers Admin

A Scheduler automatically drives a Parameter value on chosen days within a daily time window — ideal for "on during working hours" style control (lighting, HVAC, pumps) without writing any code. Open Scheduler Management; each row shows Schedule Name, Parameter, Status, Days, Start Time, Stop Time.

1 2 3 4 5 6 7 8

• 1 Scheduler menu — under Automation & Logic.
• 2 Create Schedule — add a new schedule (opens this dialog).
• 3 Schedule Name.
• 4 Devices — which device(s) to drive.
• 5 Parameters — the parameter value the schedule controls.
• 6 Start Time / Stop Time — the daily on/off window.
• 7 Days — the days of the week it runs (Sun–Sat).
• 8 Status (Active / Deactive), then Create to save.

Creating a schedule

1. Click Create and give the schedule a name (stored UPPERCASE).
2. Pick the Device(s) and the Parameter to drive.
3. Select the Days of the week it should run.
4. Set the Start Time and Stop Time for the daily window.
5. Set Status to Active and save. MatrixIQ warns you if it overlaps an existing schedule on the same parameter/days/time.

Parameters & Recipes Admin

Parameters

A Parameter is a logical measurement name — e.g. VOLTAGE L-N AVG, REAL POWER TOTAL — that you map onto the physical tag carrying that reading on each device. Bind a widget, report column, scheduler or script to the parameter and it automatically follows the correct tag on every device. This is what makes templates and multi-device reports possible.

• Create on the fly — the easiest way: while creating a tag (Tag editor → Select Parameter), pick an existing parameter or type a New Parameter Name to add one right there. The tag is linked to it immediately.
• Predefine Parameter Management — a central screen to view/add parameters up front, if you prefer to define them before tagging.
• System Import — bulk-load the standard energy-meter parameter set (voltages, currents, power, energy, power-factor, THD, demand…) instead of typing them.

Recipes

A Recipe Group is a named set of target/setpoint values for a product or batch. Operators select a recipe on a dashboard and the system applies/compares those targets. Recipes are surfaced through dashboard widgets:

• Recipe Selector widget — lets an operator choose the active recipe group on screen.
• Recipe Settings / Download widget — view and manage the recipe's parameter values.
• Recipes can also be referenced inside global scripts via Insert → Recipe.

Alarms & Rules Both

Alarms watch your tags and raise an event when a value crosses a limit. There are two levels:

• Alarm — a named container (the "what we're watching", e.g. High Temperature). Open Alarm Management to create one; each row has an Add Rule action.
• Alarm Rule — the actual condition(s) under an alarm.

1 2 3 4 5 6 7 8

• 1 Alarms & Notifications menu.
• 2 Create — add a new alarm rule.
• 3 Rule Name.
• 4 Bind to a Tag, or a Device + Parameter (so the rule works across devices).
• 5 Interlock Tag — only alarm while this parent tag is active (suppresses nuisance alarms).
• 6 Hi / HiHi / Low / LowLow — tick the bands you need, set their values and optional aliases.
• 7 Notification / Email (to a User Group) and Timeline — how the trip is announced and logged.
• 8 Create — save the rule.

Creating an alarm rule

1. From an alarm, click Add Rule and give the Rule Name.
2. Bind it to Tag(s), or to a Device + Parameter (so the same rule works across devices).
3. Set the threshold values you need — Hi, HIHI, Low, LOWLOW — each with an optional Alias (a friendly message such as "Warning" / "Critical").
4. Optionally pick an Interlock Tag (parent condition) — the alarm only fires while that tag is in the active state, which suppresses nuisance alarms (e.g. only alarm on temperature while the machine is running).
5. If licensed, choose a User Group to receive an email and/or an app notification when the rule trips.
6. Save. Live alarms appear on the alarm screens/widgets where operators can acknowledge them.

Escalation & Notifications Admin

An Escalation makes sure an unacknowledged alarm reaches the right people in stages. Open Alarm Escalation and create a chain:

1. Give the escalation a name and set Type = ALARM.
2. Pick the Group / Alarm and the specific Rule it applies to.
3. Add escalation levels — each level has a Delay Time (minutes) and a User Group. If the alarm is still unacknowledged after the delay, the next group is notified.

Email & notification setup

For alarm emails, scheduled reports and script emails to work, configure delivery once under Email Settings:

• SMTP — Service Type / Host Name, Port, and Username (from-mail) / password.
• AWS SES — Access Key ID, Secret Access Key, region and apiVersion.

Scheduled emails

The Emails screen (Alarms & Notifications → Emails) sends automated emails on a schedule — for example a Daily Report delivered every morning, or an alarm digest. Click Create Email and configure it:

1 2 3 4 5 6 7 8 9

• 1 Emails menu — under Alarms & Notifications.
• 2 Create Email — schedule a new automated email.
• 3 Email Name (and Email Subject below it).
• 4 Email Schedule Type (Daily…) and Time — how often and when it's sent.
• 5 Select Report — the Reports / alarm bundles to attach (e.g. Daily Report, Voltage Alarms).
• 6 Active / User Group — enable it; tick User Group to send to a group instead of typed addresses.
• 7 Email To — recipient address(es).
• 8 Email CC — cc address(es).
• 9 Message body — then Update / Create to save. The list shows each email's Day & Time and Status (Scheduled).

App/push notifications are sent to User Groups and require the notification feature in your licence.

Reports Both

Reports turn historical tag data into Excel and PDF documents, generated on a schedule and optionally emailed out. Open Reports Management; each row shows the Report Name, its Start Time and a Report Config action.

1 2 3 4 5 6 7 8 9

• 1 Reports menu — under Reporting & Analysis.
• 2 Create Report — add a new report.
• 3 Report Name.
• 4 Start Time — when the report is generated each cycle.
• 5 Default Interval — data resolution (1 min … Month).
• 6 Excel template — the uploaded .xlsx whose blank cells get filled; use Choose File to replace it.
• 7 Download Options — Excel and/or PDF output.
• 8 PDF Report Config — page numbering (Page / Page of / None) + header/footer Labels with $name/$email/$date/$time placeholders at chosen positions.
• 9 Update / Create — save the report.

Creating a report

1. Click Create Report, enter a Report Name and a Start Time (when the report is generated each cycle).
2. Set the Default Interval — the data resolution: 1 / 5 / 10 / 15 / 30 min, Hour, Day, Week or Month.
3. Tick the output format(s): Excel and/or PDF.
4. Upload your Excel template (.xls / .xlsx) — this is the heart of a customised report (see below).
5. If you ticked PDF, set the PDF Report Config (page numbering & header/footer — see below). Click Create.

Customised reports from an uploaded Excel template

Instead of a fixed layout, MatrixIQ builds each report into your own Excel workbook. You design the spreadsheet exactly how you want it — logo, headings, fixed text, formulas, merged cells, formatting — leaving empty cells where live data should land. MatrixIQ then fills those cells from your tags every time the report runs. The result always matches your house style.

Step 1 — Design & upload the template

• In Excel, lay out the workbook (you can use multiple sheets — e.g. Daily, Monthly). Put your static content (titles, units, headings, company logo, calculation formulas) wherever you like.
• Leave the cells that should receive data blank, and note their addresses (e.g. B5, the column under a heading, a row beside a label).
• Save and upload it as the report's template (the file picker accepts .xls/.xlsx).

Step 2 — Open Report Config and pick a sheet

From the report's Report Config action you reach the rule page. First use Select sheet to choose which sheet of your workbook you're mapping; the rule tools only appear once a sheet is selected. Each rule you add is listed with its Rule Name, Rule Type and Location.

Step 3 — Add rules that place data into cells

The Report Config menu offers four rule types — pick the one that matches the shape of the area you're filling:

Here is a Cell Config rule being edited on the COST_ANALYSIS sheet — the rule list shows each rule's Location (the cell it fills):

1 2 3 4 5 6 7 8 9

• 1 Select sheet — which sheet of your workbook you're mapping.
• 2 Rule list — each rule's Name, Rule Type (Cell) and Location (the cell it fills, e.g. C3, B7).
• 3 Rule Name.
• 4 Cell Address — the exact cell the value lands in (e.g. C7).
• 5 Select Tag — the tag / parameter whose data fills the cell.
• 6 Select Rule — the aggregation (Last, Average, Sum, Min, Max…).
• 7 Select TimeSpan — the period (Today, Yesterday…).
• 8 Value / TimeStamp — output the value or its timestamp.
• 9 Condition Color — turn on conditional formatting (setpoint + colour).

Step 4 — Choose what value lands and how it's calculated

For each rule:

• Tag — the tag, memory tag, parameter or system tag whose data fills the cell(s). Bind to a Parameter to make the report reusable across devices.
• TimeSpan — the period each value covers (the same options as elsewhere: 1 min … 24 hour completed, Today, Yesterday, Week, Month, Year).
• Rule (aggregation) — how the period is reduced to a number: Average, Min, Max, Difference, Delta Sum, Last, Sum, Negative Vector.
• TimeInterval — (Row/Column) the bucket size used to step across/down, so a window is broken into a series of cells.
• Write — output the Value or its TimeStamp.

Step 5 — (Optional) conditional formatting

Any rule can colour its cell based on a Setpoint + Condition (< > >= <= == !=): set a Font Color and Background Color that apply when the condition is met — e.g. turn a cell red when a value exceeds its limit. This makes exceptions jump out in the finished sheet.

PDF header/footer & page numbers

When PDF is enabled you can add up to 6 header/footer lines, each with a Label and a position (Top/Bottom × Left/Center/Right). Labels support placeholders that are filled at generation time: $name (user name), $email, $date, $time. Page numbering can be Page, Page of or None, at a chosen position.

Reuse, test & deliver

• Test — use the Test action on the rule page to generate the report now and confirm every cell is filled correctly before relying on the schedule.
• Import / Export — export a sheet's rule set as a .json file and import it into another report to reuse your mapping.
• Delivery — once it tests clean, the report runs automatically from its Start Time at the Default Interval and can be emailed to recipients (configure mail under Email Settings).

Downtime & KPIs Both

The Downtime Reporting System (DTRS) captures why equipment stopped and turns it into KPI reports. Its management screen is organised into tabs:

Operators acknowledge stoppages on the Acknowledge Dashboard, assigning a cause to each event; the reporting dashboard then summarises downtime by cause and period.

1 2 3 4 5 6 7 8

• 1 Downtime Report menu — under Reporting & Analysis.
• 2 Tabs — Cause Lists, Rules, Acknowledge Dashboard, Reporting Dashboard.
• 3 Create Rule — define a new downtime rule.
• 4 Token Name / Description / Select Tag (+ Set Point) — the rule's id and the tag it watches.
• 5 Select Cause List — the causes operators choose from for this rule.
• 6 Ignore Time / Ticket Validity / Ticket Edit Time — debounce and ticket lifetimes.
• 7 Script Execution Time — when the rule runs.
• 8 Update / Create — save the rule.

KPIs

The KPI module builds dashboards that roll your tags up into key performance indicators (availability, consumption per unit, efficiency…), designed in the same builder as normal dashboards.

Ticket Manager Both

The ticketing modules turn problems into trackable maintenance jobs. There are a few co-operating pieces:

Together they cover the life-cycle: a fault is detected (automatically or reported by an operator) → a ticket is created and assigned to a user group for action.

Integrations Admin

MatrixIQ connects outward in three ways:

Node-RED

NodeRed Management lets you build low-code automation flows alongside the platform (transform data, bridge to other systems, custom logic) without changing MatrixIQ itself. Requires the Node-RED feature in your licence.

API access

API Management shows your installation's API token with a one-click copy. Pass that token to external applications so they can read your data over the MatrixIQ API. Treat the token like a password — anyone holding it has API access. Requires the API feature in your licence.

OPC-UA Server

As covered under System Configuration → OPC-UA Server, MatrixIQ can publish its tags to external OPC-UA clients — the standard way to feed another SCADA, MES or historian.

User Management & Licensing Admin

The Admin account owns the system and builds everything; the Users the Admin creates are the people who actually run the plant day-to-day. The two login kinds are chosen on the sign-in page: the single Admin, and the Users.

1 2 3 4 5 6 7 8 9

• 1 User Management menu.
• 2 Add User — create a new login.
• 3 Email / Password — credentials (the eye toggles visibility).
• 4 Name, Mobile, Department, Address — contact details.
• 5 security level — 1–10 privilege rank.
• 6 Activation Type — validity: Unlimited (no expiry) or Limited (+ Activation Days).
• 7 Session — auto-log-out after an idle timeout.
• 8 Link Dashboard — assign which dashboards this user sees (their runtime menu).
• 9 User Groups — create groups (Add User Group); used by alarms, reports and notifications.

Creating a user

Open User Management → Add User and fill in:

Validity (Activation Type)

Each user has a validity set by the Activation Type:

• Unlimited — the account never expires.
• Limited — the account is valid only for a set number of Activation Days; after that it expires and must be renewed. Ideal for contractors or temporary operators.

Session timeout

Turn on Session to auto-log-out a user after an idle period — set the idle Time (min) (e.g. 1, 2, 5, 10, 15, 20, 25, 30). This protects an unattended operator station: after the timeout the runtime locks and the user must sign in again.

Linking dashboards to a user (the runtime menu)

Creating the login is only half the job — you then decide which dashboards that user can open. From a user's row choose Link Dashboard and Assign New Dashboard. This builds the menu the operator sees in their runtime. Each assignment has a Dashboard Type:

Aliasing the menu entry

The Alias Name is the friendly label the user sees in their menu instead of the dashboard's real name. So one master dashboard called FEEDER_TEMPLATE_V2 can appear to operators simply as “Feeder 1”, “Feeder 2”, etc. — each alias pointing at the same template bound to a different device. If you leave the alias blank, the real dashboard name is shown.

1 2 3 4 5 6 7 8

• 1 Set dashboard for — the user whose runtime menu you're building.
• 2 Link Dashboard — open the Assign New Dashboard dialog.
• 3 Save Dashboard — save the menu.
• 4 Dashboard Type — Static (a menu folder/heading) or Dynamic (a real screen).
• 5 Select Dashboard — the dashboard/template to show (for Dynamic).
• 6 Alias Name — the friendly label the user sees instead of the real dashboard name.
• 7 Static entries — section headings (here in red) that group the menu, e.g. Reports, Analysis, HVAC.
• 8 Dynamic entries — the actual dashboards the user opens, nested under a heading with their aliases (e.g. Daily Report).

User Groups

A User Group (give it a Group Name and add members) is how alarms, escalations, reports and script notifications address people — you send to a group, not to individuals, so membership changes don't break your alerts.

Licensing

What your installation can do is controlled by its licence (visible on the Admin profile). The licence defines:

• Active-user limit (userCount) — you can't activate more users than the licence allows; deactivate one to free a slot. Activation/expiry is governed by activation date + activation days.
• Enabled drivers — exactly which protocols appear in the Connections type list.
• Feature flags — each major module is individually licensed: Email, App Notifications, MQTT Server, OPC-UA Server, Downtime, API access, Node-RED, Templates, and the AI features.

Admin & Backups Admin

The Profile Management screen (Admin profile) is the system's control panel — your details, look & feel, backups and software updates.

1 2 3 4 5 6 7

• 1 Auto Backup — schedule automatic database backups (Local / Cloud FTP).
• 2 Select Theme — the application accent colour.
• 3 Actions — software Updates (FDM Auto-Updater) and password change.
• 4 Profile details — email, name, contact, state/country and TimeZone.
• 5 Select Font — the application font family.
• 6 License Details — validity (activation / expiry), enabled drivers, Users Limit, and the per-module feature flags (Email, App Notifications, MQTT / OPCUA Server, Downtime, API, Node-RED, Templates, AI).
• 7 About Us — Company Name, Heading (the brand shown in the sidebar, e.g. CSPL) and the FDM version.

• Profile details — name, mobile, contact and "About Us" information, and password change.
• Select Theme — pick the application's accent colour (the readable font colour is chosen automatically) and a font family.
• Auto Backup — open the backup configuration (below).
• Updates — the FDM Auto-Updater checks for and installs new software versions.

Auto-Backup configuration

Open Profile → Auto Backup to schedule automatic database backups so you never lose configuration or history:

1 2 3 4 5 6 7

• 1 Select Storage Location — Local (a server directory) or Cloud (FTP).
• 2 Backup Frequency — Daily or Monthly.
• 3 Execution Time — when the backup runs each cycle.
• 4 Storage Path / Directory — (Local) where the backup files are written. (For Cloud, FTP Host/Port/User/Password appear here instead.)
• 5 Verify Path — check the path / FTP credentials are valid before saving.
• 6 Retention Files — how many backups to keep (default 3).
• 7 Save Backup Configuration — save it (enabled once the path is verified).

Glossary

Key terms used throughout MatrixIQ and this manual:

Troubleshooting

Common issues and where to look first: