Bristol FB300 SCADA Integration with Modern Platforms

Quick Answer

The Bristol FB300 integrates with modern SCADA systems via DNP3 Level 2 outstation. Most SCADA platforms — Ignition, GE Cimplicity, OSIsoft PI, ClearSCADA, and VTScada — include native DNP3 drivers that connect to the FB300 over serial or TCP with minimal configuration.

Integration Architecture

A typical FB300-to-SCADA integration follows this architecture:

flowchart LR
  subgraph Field["Field Sites"]
    FB1["FB300 #1 Tank Battery"]
    FB2["FB300 #2 Wellsite"]
    FB3["FB300 #3 Meter Station"]
  end

  subgraph Comms["Communication"]
    R1["Radio / Cellular / Satellite"]
  end

  subgraph SCADA["SCADA Center"]
    M["SCADA Master (DNP3 Driver)"]
    H["Historian"]
    HMI["Operator HMI"]
  end

  FB1 --> R1
  FB2 --> R1
  FB3 --> R1
  R1 --> M
  M --> H
  M --> HMI

Ignition by Inductive Automation

Ignition's DNP3 driver module connects directly to FB300 outstations:

1. Install the DNP3 Driver Module from the Ignition Gateway.
2. Create a new DNP3 device connection:
   • Transport: TCP or Serial
   • Remote address: The FB300's DNP3 outstation address
   • Local address: The master's DNP3 address
   • IP/Port or COM port: Network path to the FB300
3. Ignition will automatically discover available data objects via an integrity poll. Map discovered objects to Ignition tags.
4. Configure poll rates per class: Class 1 every 1–5 seconds, Class 2 every 5–30 seconds, Class 3 every 60+ seconds.

GE Cimplicity / iFIX

1. Configure a DNP3 communication port in the Cimplicity Device Communication Manager.
2. Add the FB300 as a DNP3 outstation device with the correct address and communication parameters.
3. Import or manually create point definitions matching the FB300's DNP3 point map.
4. Verify data quality indicators — Cimplicity will flag stale or suspect data if communication is intermittent.

OSIsoft PI (AVEVA PI)

1. Install a PI Interface for DNP3 node on a server with network access to the FB300 (directly or via communication infrastructure).
2. Configure the interface with the FB300's DNP3 address and transport parameters.
3. Create PI tags corresponding to each DNP3 data object. Set appropriate exception deviation and compression deviation for historian efficiency.
4. The PI interface will collect both polled data and DNP3 unsolicited events, preserving field timestamps for accurate historical analysis.

Schneider Electric ClearSCADA (Geo SCADA)

1. Create a DNP3 outstation object in the ClearSCADA database, specifying the FB300's address and communication channel.
2. Define DNP3 point objects under the outstation, matching the FB300's DNP3 index map.
3. ClearSCADA supports both polled and unsolicited DNP3 communication — enable unsolicited responses for faster alarm reporting.
4. Configure historic data collection and alarm management per your operational requirements.

VTScada

1. Add a DNP3 driver instance and configure the FB300 as a remote outstation.
2. VTScada's DNP3 implementation supports automatic point discovery — run a discovery scan to populate the tag database from the FB300's reported data objects.
3. Configure alarm limits and historical logging within VTScada's tag properties.

Migrating from Legacy BSAP Networks

Many existing FB300 installations still communicate using BSAP (Bristol Synchronous/Asynchronous Protocol), the legacy Bristol proprietary protocol. Migration to DNP3 can be done incrementally:

1. Phase 1 — Dual-protocol operation: Configure the FB300 to run both BSAP and DNP3 simultaneously on separate serial ports or TCP sockets. The legacy BSAP master continues operating while the new DNP3 master is configured and tested.
2. Phase 2 — Parallel validation: Run both SCADA systems simultaneously and compare data between the legacy BSAP display and the new DNP3 display. Resolve any discrepancies before cutover.
3. Phase 3 — Cutover: Switch operational reliance to the DNP3 SCADA master. Disable BSAP polling but keep the configuration available for rollback if needed.
4. Phase 4 — Decommission BSAP: After a stable period (typically 30–90 days), remove the BSAP configuration from the FB300 to free serial port resources.

Protocol Gateway Option

If the FB300 firmware doesn't support simultaneous BSAP and DNP3, or if the FB300 has limited serial ports, a protocol gateway (e.g., a Bristol ControlWave Micro or a third-party serial-to-IP converter with protocol translation) can bridge BSAP-to-DNP3 without modifying the FB300 configuration at all.