A display naming and numbering convention is the systematic scheme a control system uses to assign every operator display a unique, meaningful identifier. Instead of arbitrary file names, screens get names or numbers that encode where they sit - which area, unit, or level they belong to - so both operators and engineers can locate any of hundreds of graphics quickly. It is one of the least glamorous but most practical parts of an HMI style guide.
Display Naming/Numbering Convention in one line: A display naming and numbering convention is a defined scheme for assigning consistent identifiers to HMI screens, usually encoding attributes such as area, unit, and display level. It lets operators call up a screen directly by its number and lets engineers manage a large display set without duplicates or confusion. Consistency, not the exact code, is what makes it work.
The core idea is that a display identifier should carry information rather than being an accident of whoever created the file. A common approach encodes structure into the identifier: a code for the plant area, another for the unit or system, and often a component that reflects the display level or the specific view. Read left to right, such an identifier tells you where the screen belongs before you even open it, and it sorts naturally so related screens group together in any listing.
Numbering and naming often work together. A human-readable name gives context - it says in words what the screen shows - while a number gives a short, unambiguous handle that can be typed or dialed directly. In many systems an operator can call up a display by entering its number, which is far faster than hunting through menus, so the numbering scheme is not just for cataloging but for day-to-day navigation.
Whatever the exact scheme, the convention has to be defined once and applied everywhere. The value comes from every screen following the same rules, so that the identifier of a display an operator has never seen still tells them roughly what and where it is. A scheme that is documented in the style guide and enforced as new graphics are built is what prevents the identifiers from drifting into inconsistency as the system grows.
For operators, the payoff is speed and confidence under pressure. Direct call-up by number means reaching the exact screen for a given area or piece of equipment without navigating a tree of menus, which matters when seconds count during an upset. Predictable naming also means an operator moving between areas, or a relief operator covering an unfamiliar unit, can infer where a screen lives instead of memorizing an arbitrary map.
For engineers, the convention is what keeps a large display set maintainable. Hundreds of graphics with ad-hoc names quickly become impossible to manage - duplicates appear, links break, and nobody can be sure which screen is authoritative. A systematic scheme guarantees uniqueness, makes it obvious where a new display should slot in, and lets the whole set be reasoned about as a structured catalog rather than a pile of files. Cross-references between displays, and links from alarms to the relevant screen, all rely on stable, predictable identifiers.
The convention also underpins a display register, the master list of every screen with its identifier, purpose, and level. That register is the backbone of managing the display lifecycle: it shows what exists, reveals gaps, and provides the map used during reviews and upgrades. Without a naming and numbering convention the register is just a list; with one, it is an index that anyone can navigate.
In a cloud SCADA covering many sites, a naming and numbering convention scales the same discipline from one plant to a whole fleet. When every site follows the same scheme, a display identifier can encode the site along with the area, unit, and level, so an operator responsible for dozens of remote locations can reach the exact screen for a specific well or skid at a specific site without wandering through per-site menus that each look different.
Consistency across sites is what makes fleet operation practical. If each location named its screens its own way, an operator covering multiple sites would face a different navigation logic at every one. A shared convention means the mental model transfers: knowing how identifiers are built at one site is enough to find your way around another, which is exactly what a single operator monitoring a large remote fleet needs.
A convention also pairs naturally with the tag namespace a cloud platform already uses to keep field data organized. When display identifiers and tag names follow parallel, predictable structures, linking a tag to the display that shows it, or jumping from an alarm on a tag straight to the right screen, becomes reliable across the whole fleet. The naming and numbering convention is the quiet infrastructure that lets a large, multi-site display set stay navigable from a single browser.
Ad-hoc names work for a handful of screens but break down at scale, producing duplicates, broken links, and confusion about which display is authoritative. A systematic convention guarantees uniqueness, encodes where each screen belongs, and lets operators call up displays directly and engineers manage hundreds of graphics as a structured catalog rather than a pile of files.
It commonly encodes structural attributes such as the plant area, the unit or system, and often the display level or specific view. Read in order, the identifier indicates where the screen belongs before you open it, and related screens sort together. The exact scheme varies by system; what matters is that it is defined once and applied consistently everywhere.
A display register is the master list of every screen in the system, each with its identifier, purpose, and level. Built on the naming and numbering convention, it serves as the index for managing the display lifecycle: it shows what exists, reveals gaps, and guides reviews and upgrades. Without a convention it is just a list; with one it becomes a navigable map.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.