Protection & Relay Engineering – Hiring ENG III – Sacramento, CA (Hybrid)Why This Role ExistsOur protection architecture uses IEC 61850 GOOSE for peer‑to‑peer trip signals, PRP dual‑star networks for zero‑SPOF communication, and RTAC‑3530 controllers for protocol gatewaying and sequence logic. This role exists because that stack requires an engineer who can work at the protocol level — SCL files, GOOSE datasets, PRP multicast groups, and RTAC logic programs — not just relay settings. You own the automation layer between the protection relays and the SCADA/HMI system: IEC 61850 configuration, protocol conversion (GOOSE DNP3 Modbus), and the deterministic logic that manages mode transitions, load shedding, and black‑start sequencing.What You OwnIEC 61850 GOOSE dataset configuration: publish/subscribe mappings, multicast group assignments, SCL/CID/SCD filesPRP dual‑star network architecture: VLAN/VRF design, QoS for GOOSE traffic prioritization, dual‑plane separationSEL RTAC‑3530 logic programs (IEC 61131‑3 Structured Text): sequence control, mode management, load shed/add, SOE concentrationProtocol gateway configurations: GOOSE DNP3 Modbus point maps, alarm/state model definitionsConfiguration management: versioned CID/SCD baselines, change control documentation across 134‑IED designsIRIG‑B time synchronization design and SOE timestamp correlationSystems You'll TouchVendor PlatformsSEL CiscoSoftware ToolsSEL Architect AcSELeratorRTAC AcSELeratorQuickSetWiresharkProtocolsIEC 61850 GOOSEDNP3Modbus TCPIRIG‑BSNMPStandardsIEC 61850IEC 62439‑3 (PRP/HSR)Site ActivitiesAutomatic mode transitionsAutomatic black‑start sequencingPriority‑based load sheddingSequenced load restorationWhat Success Looks LikeFirst 90 DaysReviewed existing IEC 61850 configurations (SCL/CID files) and RTAC logic programs on a current projectDelivered a GOOSE dataset configuration or RTAC logic modification through internal reviewCaptured GOOSE messages with Wireshark and validated publish/subscribe behavior on a PRP networkFirst 180 DaysOwning IEC 61850 configuration scope on at least one project — SCL engineering, GOOSE datasets, PRP multicastDelivering RTAC logic programs for mode management or sequence controlParticipating in PRP network commissioning — failover testing, GOOSE continuity verificationRequired Background5+ years protection or automation engineering with IEC 61850 implementation experienceGOOSE configuration: SCL file engineering (CID/SCD), publish/subscribe mappings, dataset designPRP or HSR network experience per IEC 62439‑3 — dual‑plane architecture, DANP endpointsSEL RTAC‑3530 or equivalent automation controller programming (IEC 61131‑3)Protocol gatewaying experience: IEC 61850 GOOSE, DNP3, Modbus TCP/RTUNetwork protocol analysis with Wireshark — GOOSE message capture and troubleshootingPreferred BackgroundSEL Architect SCL engineering tool experienceIndustrial Ethernet network design: VLAN segmentation, QoS, Cisco IE switch configurationIEC 62443 zone/conduit model awareness for OT network securityIRIG‑B time synchronization design and SOE correlationConfiguration management for large IED deployments (100+ devices)What to Expect in the FieldTravel 20–40% during commissioning and network integration phasesSite Hours: Standard office hours for configuration engineering; site hours during PRP network commissioning and GOOSE verificationCustomer‑Facing Interface with prime contractor network and controls engineers; vendor technical support for multi‑vendor interoperabilityDocumentation Heavy — SCL/CID/SCD files, network architecture diagrams, RTAC logic documentation, GOOSE dataset specifications, protocol point mapsField Safety NFPA 70E awareness required for switchgear‑adjacent network equipment installation and testingWhy ZigguratIEC 61850 GOOSE in production — not a pilot or proof‑of‑concept, but the operating protection communication layer on live critical systems134‑IED designs with formal configuration management — work at a scale where protocol engineering mattersFull‑stack automation: you touch the protocol layer, the logic layer, and the network layer, not just one sliceDirect access to the principal engineer who architected the DSN protection network — learn from the design authority#J-18808-Ljbffr