SCADA that survives your next expansion.
The screens are the visible part. The tag structure and historian configuration underneath decide whether the system still works after you add another line.
Most Utah facilities that call us about SCADA already have something. It might be an Ignition project that grew across three phases with three different naming conventions, or a legacy Wonderware system nobody wants to touch. Either way the first job is understanding what is there.
We work primarily in Ignition, which suits Utah plants well: it is licensed per gateway rather than per client, so putting a screen in the maintenance office, the plant manager's phone and the control room does not multiply the cost.
Where a migration is genuinely warranted we will say so, and where an existing system is adequate we will say that too. Rebuilding a working SCADA system is a large expense and it is not always the right call.
What we deliver
- Ignition Perspective and Vision projects
- Gateway architecture and redundancy configuration
- Tag structure and UDTs that survive plant expansion
- Historian sizing, retention policy and trend screens
- Alarm rationalisation with documented responses
- Full project backup and unlocked source at handover
What this involves.
Ignition development
Perspective and Vision projects, gateway architecture, tag structure and UDTs designed to scale.
Historian & trends
Retention and resolution set per tag group, sized against real storage rather than a guess.
Alarming & remote access
Rationalised alarms with meaningful priorities, and secure remote access for people who are not on site.
Let us look at your tag structure.
It is the fastest way to tell whether a SCADA system will age well or become a rebuild.
Or call (801) 946-2710, Monday, Friday, 8:00am, 4:30pm MT