The difference between a set of screens and a coherent HMI is a style guide. Without one, every engineer draws a pump, colors an alarm, and lays out navigation their own way, and the result is a display estate the operator has to relearn screen by screen. This guide explains what an HMI style guide is - both the document and the object library - what it standardizes, and why that consistency directly reduces operator error when a plant is in trouble.
HMI Style Guide in one line: An HMI style guide is the project document and accompanying object library that fixes the visual and behavioral conventions for every operator screen: the fonts, colors, indicator shapes, faceplate templates, symbols, and navigation patterns that all displays must use. It is the deliverable that turns a design philosophy into concrete, reusable rules, so every screen looks and behaves the same way. Under ISA-101, the style guide is the artifact that makes consistency enforceable rather than aspirational.
An HMI style guide has two complementary parts. The first is a written document that specifies the conventions in detail: the exact color palette and what each color means, the fonts and text sizes, how a value should be displayed, how alarm states are indicated, the layout grid, the navigation scheme, and the rules for when and how color and animation may be used. It is the rulebook that any designer building a screen must follow, and the reference against which finished screens are reviewed.
The second part is a library of standardized display objects - the reusable building blocks that put the rules into practice. Rather than redraw a pump, a valve, a moving analog indicator, or a control-loop faceplate from scratch each time, designers assemble screens from library objects that already embody the conventions. A separator symbol, a pump status graphic, a standard faceplate template: each is built once, to the style guide, and reused everywhere. The library is what makes consistency the path of least resistance, because using the approved object is easier than building a nonconforming one. Together the document and the library turn the style guide from a set of good intentions into a working toolkit.
Consistency is not an aesthetic nicety - it is a safety mechanism. When every faceplate of a given type is laid out identically, every alarm color means the same thing on every screen, and navigation works the same way everywhere, the operator builds reliable muscle memory. Under normal conditions this saves time; under upset conditions, when the operator is stressed, moving fast, and cognitively loaded, it prevents errors. A start button always in the same place, a red that always means the same priority - these let the operator act on instinct without having to re-read and re-interpret each screen.
Inconsistency does the opposite. If a pump is green-means-running on one screen and green-means-stopped on another, or if the acknowledge button moves around, the operator has to consciously check the meaning every time, which is slow and error-prone precisely when there is no time to spare. A style guide eliminates that variability at the source by ensuring every screen is built from the same conventions and objects. This is why standards like ISA-101 make the style guide central: it is the mechanism by which the human factors principles of high-performance HMI actually reach the operator's eyes, uniformly, across the whole system.
A browser-delivered SCADA is a natural home for a style guide because screens are built centrally and served from one place, which makes both the object library and enforcement easier. A shared library of display objects can be maintained once and used across every screen, and an update to a standard object propagates everywhere rather than having to be reapplied on each workstation. That central control is exactly what keeps a growing display estate from drifting away from its conventions over time.
For an oil and gas operator running a cloud SCADA such as Merobix, a style guide is what makes many similar sites feel like one system: every well-pad, separator, tank-battery, and pipeline screen assembled from the same object library reads identically to an operator in the control room or a technician on a tablet in the field. As Merobix renders tags read over Modbus, DNP3, OPC UA, and MQTT into browser graphics, building those graphics from a consistent object library - conforming to a documented style guide under ISA-101 principles - is what turns a large, expanding field of screens into a single coherent HMI rather than a patchwork that operators must relearn site by site.
It contains both a written specification and an object library. The document fixes the color palette and their meanings, fonts, value-display rules, alarm indication, layout grid, and navigation scheme. The library provides reusable standardized objects - equipment symbols, indicators, faceplate templates - that embody those rules, so designers assemble conforming screens from approved building blocks rather than drawing everything from scratch.
Consistency lets operators build reliable muscle memory, which matters most during upsets when they are stressed and acting fast. When every faceplate is laid out the same, every color means the same thing, and navigation works identically everywhere, operators can act on instinct without re-interpreting each screen. Inconsistency forces conscious rechecking exactly when there is no time for it, which invites error.
ISA-101 defines the HMI lifecycle and requires an organization to establish and apply its own display conventions, and the style guide is the concrete artifact that captures those conventions. In ISA-101 terms, the style guide sits between the high-level philosophy and the design and implementation of individual screens - it is the document that makes the standard's requirement for consistency enforceable rather than just aspirational.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.