Roadmap

The fence around the agent, the code policy, the audit trail, the formula language; MQTT, HTTP, the OPC UA server, OpenID Connect, licences that bind, instrument templates, the verified-hardware record; versions with rollback, a project that lives in a repository, the designer in German, French, Spanish and Chinese, the embed; the 21 CFR Part 11 validation pack, electronic signatures on writes, the long-term support procedure and its backport check, the integrator programme.

The beta paths - USB and GPIB instruments through the VISA library, DAQ devices, serial instruments on a physical port - run on the design partners' benches and recorded on the hardware page; the SCPI templates confirmed on the instruments they name; Mosquitto and EMQX for MQTT; a PLC's OPC UA server.

Alarms as a table the station evaluates and keeps across a restart, the station's users managed from the designer, recipes and scheduled jobs, the historian, Siemens S7 and EtherNet/IP, shapes and process symbols, and templates to start from.

Subflows and a library of your own nodes; SAML without an OIDC bridge; Sparkplug B on the MQTT source; a designer for the agent's whole configuration in the browser (today: the instruments).

A cloud, an account or a phone-home of any kind; a PLC programming environment; SCADA depth - redundancy, a historian of years, an alarm journal across sites - where a SCADA belongs and this agent's OPC UA server plugs into it; a per-client or per-tag price.

A path you need first, an instrument you have on the bench, a standard you must meet: write to support@jqwidgets.com. A bench record moves a path up the hardware page; a partner's instrument gets its template.