Calgary Ignition SCADA Integrator Guide (2026)

Start With the Tag Model

A weak tag model makes every future screen, report, alarm, and historian query harder to maintain. Before building Perspective or Vision screens, the integrator should define naming patterns, UDT usage, asset hierarchy, and where calculations belong.

• Use reusable UDTs for equipment classes instead of one-off tags for every asset.
• Separate raw device data from contextualized production, quality, and downtime signals.
• Document owner, source, engineering unit, and intended use for critical tags.

Alarm Philosophy Has to Be Part of Scope

Ignition makes it easy to create alarms, which means discipline matters. A Calgary plant should expect clear priority rules, suppression logic, shelving expectations, and weekly alarm-performance review points.

• Tie priority to consequence and required response time, not personal preference.
• Review alarm floods, standing alarms, and nuisance alarms before go-live.
• Keep operator action guidance visible where it is needed, not buried in a separate document.

Deployment Discipline Protects Production

Good Ignition delivery includes staging, backup, version control, rollback thinking, and a commissioning checklist. These controls matter most when a site is modernizing a live system or standardizing across multiple facilities.

Evaluation Checklist

• Ask for examples of project standards, tag conventions, and deployment checklists before awarding work.
• Confirm whether the team can support Perspective, Vision, databases, historians, and alarming as one operating system.
• Require handover documentation that maintenance and operations can use without the original developer present.
• Prefer phased modernization when legacy screens and production workflows cannot tolerate a large cutover.

Related Service Paths