EPMS / SCADA Integration Engineer

Ziggurat Automation Inc.; Sacramento (CA); Hybrid; USD 100,000 - 130,000; Full time

Benefits offered by this job

Travel 20-40% for site integration.

Standard office hours for development.

Job summary

Ziggurat Automation Inc. is hiring a Senior Engineer in Sacramento, CA (Hybrid) to support EPMS/SCADA integrations. You will develop and maintain critical control systems, bridging multiple protocols like DNP3 and Modbus.

The role demands strong technical skills in HMI development and alarm rationalization, with a focus on delivering operational impact through robust data path management. Your expertise will be crucial in shaping user interfaces that operators rely on during critical events.

Qualifications

• Experience with SCADA/HMI integration in critical control systems.
• Proficient in HMI development on major platforms.
• Skilled in multi-protocol integration including DNP3 and Modbus.

Responsibilities

• Design EPMS/SCADA architecture including data concentrators and protocol gateways.
• Develop HMI/SCADA interfaces using FactoryTalk, Wonderware, or Ignition.
• Perform alarm rationalization and historian integration.

Skills

SCADA/HMI Integration

Multi-protocol knowledge

HMI Development

Alarm Rationalization

Education

7+ years in SCADA/HMI or EPMS integration

Tools

FactoryTalk View

Wonderware

Ignition

Job description

Hiring Senior Engineer – Sacramento, CA (Hybrid) – Role Code: ZA-31012

This role supports our EPMS/SCADA and end‑to‑end service scopes.

Why This Role Exists

Protection relays and controllers generate data — status, alarms, metering, SOE — that has to reach operators through HMI/SCADA and reach historians for trending and analysis. This role exists because EPMS/SCADA integration bridges the gap between the protection layer and the monitoring layer, spanning multiple protocols (DNP3, Modbus TCP/RTU, BACnet/IP, SNMP) and HMI platforms (FactoryTalk, Wonderware, Ignition). You own the monitoring and control layer: point lists, HMI screen development, alarm rationalization, historian integration, and the BMS‑to‑power system boundary. When an operator sees a trip alarm or a historian trends power quality, your integration made that data path work.

What You Own

• EPMS/SCADA architecture design: data concentrator topology, protocol gateways, redundancy schemes
• HMI/SCADA development on FactoryTalk View, Wonderware, or Ignition platforms — operator graphics, navigation, alarm annunciation
• Point list engineering: RTAC‑to‑HMI point maps, Modbus/DNP3 register assignments, SOE tagging schemas
• Alarm rationalization: alarm matrices, priority assignments, flood prevention, operator notification logic
• Historian integration: meter‑to‑historian tag configurations, data collection automation, trending/reporting templates
• BMS‑to‑power system integration boundary: BACnet/IP segmentation, BBMD broadcast management, cross‑system monitoring
• Platform refresh/upgrade: FactoryTalk View server/client upgrades, cutover procedures maintaining operational continuity

Systems You’ll Touch

Software Tools

• Wonderware InTouch / System Platform
• Ignition
• FactoryTalk View Studio
• ALC WebCTRL
• AcSELerator
• RTAC

Vendor Platforms

• SEL
• Electro Industries (EIG)

Protocols

• DNP3
• Modbus TCP
• Modbus RTU
• BACnet/IP
• BACnet MS/TP
• SNMP

What Success Looks Like

First 90 Days

• Reviewed existing SCADA/HMI configuration on an active project — point lists, alarm setup, operator graphics
• Developed or modified HMI screens for an integration scope (FactoryTalk View, Wonderware, or Ignition)
• Produced a point list or alarm matrix for an RTAC‑to‑HMI data path

First 180 Days

• Owning EPMS/SCADA integration scope on at least one project — architecture through functional testing
• Historian integration delivered: meter data flowing through RTACs to dual historian servers with SOE tagging
• Alarm rationalization completed and validated through alarm flood testing

Required Background

• 7+ years SCADA/HMI or EPMS integration for critical power or industrial control systems
• HMI development on at least one major platform: FactoryTalk View, Wonderware InTouch/System Platform, or Ignition
• Multi‑protocol integration: DNP3, Modbus TCP/RTU, and at least one of BACnet/IP or SNMP
• Point list engineering: protocol‑to‑HMI data mapping, SOE tagging, alarm configuration
• Alarm rationalization experience: alarm matrices, priority tiers, flood prevention strategies
• Understanding of power system SCADA architecture: data concentrators, protocol gateways, redundancy

Preferred Background

• SEL RTAC‑3530 as SCADA data concentrator / protocol gateway
• BMS/BACnet integration experience (ALC WebCTRL or equivalent)
• Power quality metering integration (EIG Shark‑250 or equivalent)
• Historian platform experience (OSIsoft PI, Wonderware Historian, or FactoryTalk Historian)
• IT/OT boundary management: network segmentation between BMS and power system OT networks

What to Expect in the Field

• Travel 20–40% for site integration, functional testing, and cutover support
• Site hours: standard office hours for development; site hours during integration testing and SCADA cutover windows
• Customer‑Facing Interface with prime contractor controls engineers, BMS integrators, and facility operations for HMI requirements and alarm philosophy
• Documentation Heavy — point lists, alarm matrices, HMI screen specifications, historian tag configurations, integration test procedures
• Field Safety Minimal direct electrical exposure; NFPA 70E awareness for switchgear‑adjacent controls equipment

Why Ziggurat

• Full‑stack integration: from relay terminals through RTACs through HMI to historian — you see the complete data path
• Multi‑protocol environment: DNP3, Modbus, BACnet, SNMP — not a single‑protocol shop
• Your HMI screens and alarm logic are what operators rely on during real events — direct operational impact
• BMS‑to‑power integration boundary is a specialization few firms own — high‑value, low‑competition skill set

Hiring Process

1. Screen – background review against role requirements, vendor platform experience, relevant certifications, project types, and standards familiarity.
2. Technical Review – deeper evaluation of technical depth, review of sample work (relay settings files, protection study reports, commissioning test procedures, or SCADA configuration packages), or discussion of specific project scenarios.
3. Interview – scenario‑based conversation with the principal engineer about coordination studies, commissioning plans, and troubleshooting during site acceptance testing.
4. Exercise / Artifact Review – take‑home exercise or artifact walkthrough to demonstrate engineering methodology and decision making.
5. Final Conversation – role scope, current project pipeline, working arrangements, and compensation.