Can Geo SCADA and Ignition share the same OPC server?

Geo SCADA includes a built-in OPC UA server that Ignition can connect to as a client. They don't share a single OPC server — rather, Ignition subscribes to Geo SCADA's OPC UA server to access field data. If both platforms need to read from the same PLC, each can have its own OPC connection, though consolidating through one platform is preferred to avoid polling conflicts.

Which is better for remote telemetry, Geo SCADA or Ignition?

For wide-area remote telemetry across hundreds of sites using DNP3 or Modbus over cellular, radio, or satellite links, Geo SCADA is purpose-built and excels. Ignition is stronger for local plant-floor HMI, high-tag-count installations, and enterprise integration. The best architecture often uses both platforms for their respective strengths.

How do you manage alarms across two SCADA platforms?

The recommended approach is to designate one platform as the alarm authority. In most hybrid deployments, Geo SCADA serves as the alarm source because it has protocol-level context for field alarms. Critical alarms are forwarded to Ignition via OPC UA for display on control room dashboards. This prevents duplicate alarming and maintains a single alarm history.

Integrating Geo SCADA with Ignition: When and Why a Hybrid Architecture Makes Sense

Quick Answer

A hybrid Geo SCADA and Ignition architecture leverages each platform's strengths — Geo SCADA for wide-area telemetry and DNP3 polling across remote sites, Ignition for HMI dashboards, MES integration, and control room visualization. Integration patterns include OPC UA bridging, shared database access, and API federation.

Where Geo SCADA Excels

Schneider Electric Geo SCADA (ClearSCADA) was designed from the ground up for geographically distributed infrastructure. Its strengths include:

Wide-area telemetry: Efficient polling of hundreds or thousands of remote sites across large geographic areas — entire pipeline networks, regional water distribution systems, or scattered wellsite installations.
DNP3 protocol mastery: Deep DNP3 implementation including unsolicited responses, event-driven reporting, multi-drop serial networks, and DNP3 Secure Authentication. Geo SCADA handles DNP3 edge cases that other platforms struggle with.
Communication management: Sophisticated communication channel management across diverse media — cellular, radio, satellite, serial, TCP/IP — with automatic failover, bandwidth optimization, and store-and-forward for intermittent connections.
Built-in redundancy: Native server mirroring with automatic failover, designed for critical infrastructure availability requirements.

Where Ignition Excels

Inductive Automation's Ignition platform has different strengths that complement Geo SCADA:

HMI and dashboards: Ignition's Perspective module provides modern, responsive web-based HMI development with a rich component library and strong data visualization capabilities.
Developer ecosystem: Python (Jython) scripting, module SDK, and a large community of third-party modules give Ignition flexibility for custom applications.
MES and enterprise integration: Ignition's MES module and database connectivity make it well-suited for bridging the gap between OT and IT systems — connecting SCADA data to ERP, CMMS, and business intelligence platforms.
Unlimited licensing: Ignition's licensing model allows unlimited tags, clients, and connections per server — making it cost-effective for high-tag-count local installations.

Integration Patterns

OPC UA Bridging

The most common integration pattern connects Geo SCADA's OPC UA server to Ignition's OPC UA client. Geo SCADA collects field data via DNP3/Modbus from remote sites and exposes it through its OPC UA interface. Ignition subscribes to the data points it needs for HMI displays, dashboards, and enterprise integration. This pattern keeps Geo SCADA as the single source of truth for field data while allowing Ignition to present that data in its visualization framework.

Database Sharing

Both platforms can read from and write to SQL databases. A shared database architecture allows Ignition to query Geo SCADA's historian data for trend displays and reporting, while Geo SCADA can access setpoints or configuration data stored in Ignition-managed databases. Database sharing requires careful access control and query optimization to prevent cross-platform performance impacts.

API Federation

For more complex integrations, REST APIs can bridge the two platforms. Ignition's scripting environment can make HTTP requests to Geo SCADA's web API, and vice versa. API federation is useful for triggering actions across platforms — for example, an Ignition dashboard action that initiates a Geo SCADA report or a Geo SCADA alarm that triggers an Ignition notification workflow.

Use Case: Utility with Geo SCADA Field + Ignition Control Room

A common deployment pattern for water and gas utilities:

Geo SCADA handles all field communication — polling 200+ remote sites via DNP3 over cellular, managing communication failover, and maintaining the telemetry historian.
Ignition runs the control room dashboards — providing operators with modern, responsive HMI screens, interactive maps, and drill-down trend displays using data sourced from Geo SCADA via OPC UA.
Alarm management flows through Geo SCADA — which has the protocol-level context to distinguish between communication alarms and process alarms — with critical alarm notifications displayed on Ignition dashboards.

This architecture gives operators the best of both platforms: Geo SCADA's unmatched wide-area telemetry capabilities and Ignition's modern visualization and integration features.

Managed Services for Hybrid Environments

Hybrid SCADA environments require managed support that spans both platforms. A managed service provider that only knows one platform will miss integration-layer issues — a communication failure in Geo SCADA that manifests as stale data in Ignition, or an OPC UA subscription problem that creates intermittent data gaps in dashboards.

NFM Consulting provides managed Geo SCADA services with the integration expertise to support hybrid environments. Our team understands both platforms and the integration layers between them, ensuring reliable data flow from field devices through Geo SCADA to Ignition and beyond.