Screens ✦ Alarms ✦ Logic ✦ Station
A builder for operator screens that runs in a browser and ships its own station. Draw the screens from the components, write the alarms as a table the station raises day and night, add the logic as a block diagram, and let the station run it all on the plant network - Modbus TCP and RTU, Siemens S7, EtherNet/IP for Allen-Bradley, OPC UA client and server, MQTT, HTTP. Operators open a URL: no client to install, and no licence per screen.
designerComponents on a grid, bound to tags by drag: faceplates, seven-segment readouts, strip charts, alarm banners, stack lights, every component of the library. A request from an operator - a setpoint, a command - goes to the plant and comes back confirmed. Pages, templates, the Bench theme, two ISA-101 themes and the default.
ISA-18.2A table, one condition on one tag per row: above or below a limit, on, off, or not delivering, with a deadband, a delay, a priority and the words the operator reads. The station raises them whether or not a screen is open, an operator acknowledges or shelves them on any screen, and each raise, clear and acknowledgement is kept with who did it. A spreadsheet of them comes in as CSV.
dataflowThe program behind the panel: nodes with typed terminals, one value per wire, run by data. While and For loops as frames with feedback between iterations, a Case frame, subdiagrams called as nodes, records, front-panel terminals. Message flows for what reacts to events. It runs where you put it: with the page, or on the agent.
Node.jsA small server for the station PC, no dependencies: OPC UA client and server, Modbus TCP and RTU, Siemens S7, EtherNet/IP for Allen-Bradley Logix, MQTT, HTTP; for a bench, SCPI over TCP and serial and VISA (VXI-11, socket, serial, USB and GPIB through the library), in beta until a path has met a device; a simulator. One WebSocket for the tags, the published apps, the diagrams marked for it, CSV logs, users and roles managed from the designer, TLS, running at boot.
It runs from this site, or from the station's own address. It opens on a plant overview whose five alarms are evaluated live, beside a gallery of templates to start from instead: alarm management, line operations, an andon board, a KPI wall, safety interlocks, a meter logger, a signal generator.
Add a source - a simulator, a WebSocket, an HTTP endpoint, or the station with its PLCs - and its tags appear in the bar. Drag them onto components, and onto the Alarms table for the alarms. What needs logic goes on a diagram: the screen's terminals, a Tag, a Multiply, a loop, wired by their colours.
The designer runs the screens and evaluates the alarms as you build them. Publish sends the project to the station, which serves the app, raises its alarms and runs its diagrams around the clock - or download it as a zip for any web server.
No cloud, no account, no database. A project is one JSON file, readable and diffable. The designer is static files; the agent is Node.js 18 or later.
Scada Studio builds the screens and the logic around them and talks to the equipment through the agent. It is not a PLC programming environment and not a historian, and it does not read other tools' file formats.
Evaluation runs with a watermark; a licence token from Smart UI removes it. What the agent stores, what leaves the station, and how the roles work are written down.
next releaseOne zip with the designer, the runtime, the samples, the documentation, the agent and the component package - nothing to install beyond Node.js 18 for the agent. Published with the next release.
SHA-256 · signatureNext to the zip: its SHA-256, its signature and the public key - how to check them. The bill of materials is sbom.cdx.json (CycloneDX).
evaluationWithout a licence everything works and says so. The editions: a developer seat and a station licence, perpetual, or Enterprise for a site; a 30-day trial token for all of it. Your first bench in fifteen minutes.
IEC 62443-4-1 · CRAThe fence around the agent's port, the code policy, the hash-chained audit trail, how the product is developed, the disclosure policy with response times, supported versions - on one page: security. Users from your identity provider through OpenID Connect.
path by pathWhich instrument and PLC paths met a device on a bench, which the emulator, which neither - said plainly, with the device records: verified hardware. A beta path is called beta.
performanceHow many samples a second the agent delivers to how many clients over how many tags, what a write costs, what it takes of the machine - measured by a script anyone can run, with the machine named: performance.
WCAG 2.2 AA · measuredWhat the designer, a published app and the documentation support of WCAG 2.2 level AA, measured by a script rather than claimed, with the figures and what is not supported: accessibility.
roadmapWhat is planned and what is not, by release line, so a buyer knows what the maintenance year brings: the roadmap. Every release is a dated entry in the release notes.