Foundation Fieldbus
Foundation Fieldbus, FF, sometimes written as FOUNDATION fieldbus is a digital all-or-nothing communications standard for process instrumentation. Unlike HART, it replaces the 4-20 mA loop entirely with a digital bus. Multiple field devices share a single twisted pair, instruments execute control logic distributed in the field, and the plant control system supervises rather than computing every PID locally.
Read one of your own drawings.
Drop a P&ID, instrument index, or schedule. Tagsight reads it to the tag and opens a workspace you keep when you sign in.
PDF · DWG · DXF · TIFF · PNG · XLSX
Foundation Fieldbus was developed in the early 1990s by the ISP, Interoperable Systems Project and WorldFIP organizations, which merged to form the Fieldbus Foundation in 1994. The goal was to provide a fully interoperable digital bus for process instrumentation that would reduce wiring, enable distributed control execution, and carry richer device diagnostics than HART could support. Two segments were defined. H1, 31.25 kbps for field-level intrinsically safe instrument connection, and HSE, High Speed Ethernet, 100 Mbps for the controller-to-controller and device-to-DCS backbone. H1 segments power the field devices from the bus. An H1 segment can carry up to 32 devices on one twisted pair, though practical segment loading is typically 8-16 devices due to power budget and cable-length constraints. The function-block model is the defining capability that distinguishes FF from HART. A field transmitter can host the AI function block that delivers its measurement, the PID function block that computes the control output, and the AO function block that sends the output to a control valve, all executing within the transmitter itself. The DCS supervises, monitors, and can override, but does not need to process the PID calculation at all. This distributed architecture reduces DCS loading and provides loop control even during a communication interruption between the field segment and the DCS host, since the field device continues executing the PID independently. The FieldComm Group now maintains the FF standard alongside HART.
What FF actually changes.
Wiring drops to roughly a quarter of conventional 4-20 mA on a project sized to take advantage. Each field segment carries 8-16 devices on a single pair, with the device delivering its primary variable plus diagnostics, secondary variables, and the function-block execution path. PID control can run in the field device, for example, the FT executing the FIC and driving the FCV directly with the DCS supervising. The economics depend heavily on having a project of sufficient scope to amortize the engineering and segment design overhead.
Where FF deployed and where it stalled.
Petrochemicals and offshore oil & gas saw the heaviest FF deployment in the 2000s, particularly Shell, BP, Petrobras, and Saudi Aramco greenfield projects. North American refining largely stayed on HART-over-4-20 mA. The reasons FF didn't displace 4-20 mA universally are non-technical. A smaller pool of integrators trained on FF, longer commissioning curves, and a perception, rightly or wrongly of supply-chain concentration. New projects in 2024 split between FF, Profibus PA, and HART-over-4-20 mA depending on operator standards.
H1 segment design and the I/O list impact.
H1 segment design is engineering work in its own right. Each segment has a power budget, the segment power supply must deliver enough current to all devices on that segment at worst-case operating conditions, a cable-length budget, maximum 1900 m total cable length including spurs, reduced in intrinsically-safe applications, and a time-slot budget, the deterministic bus schedule must fit all device communications within the required loop-update period. The segment design document is a new engineering output that does not exist in a 4-20 mA project. The I/O list for an FF project replaces the terminal-block and cable-pair columns with segment identifier, device address, and block tag columns. Two instruments on the same H1 segment share the same segment reference in the I/O list.
Function-block control architecture.
In a conventional DCS, the PID control algorithm runs on the DCS controller. In FF, the PID function block can run in the field transmitter or valve positioner. Consider a flow control loop. FT-102 reads flow and its AI function block publishes the measurement on the H1 segment. The PID function block in FT-102 receives the measurement, computes the output, and publishes it to FCV-302's AO function block, which strokes the valve. The DCS only monitors and sets the setpoint. It does not compute the PID. This distributed execution model is the engineering motivation for FF. The control loop continues executing even during a DCS communication fault. DCS configuration tools, Emerson DeltaV Control Studio, Honeywell Experion FCE provide drag-and-drop function-block wiring tools that configure these distributed-execution loops.
FF and HART compared.
HART overlays a 1200-baud digital channel on the 4-20 mA wiring without replacing it. Foundation Fieldbus replaces the 4-20 mA entirely with a 31.25 kbps digital bus. HART requires one pair per device. FF puts multiple devices on one pair. HART can only run control logic in the DCS, the 4-20 mA signal updates at the analog scan rate, not at 1200 baud. FF runs PID in the field device. HART's installed base is vastly larger and HART expertise is universal. FF expertise is concentrated at integrators who specialize in FF-platform DCS projects. Both protocols are managed by FieldComm Group and are tested for interoperability through the HART and FF conformance test programs.
Frequently asked.
How does Foundation Fieldbus relate to Profibus PA.
Both run digital communications at 31.25 kbit, s on twisted pair and both serve process instrumentation. The protocols are not interoperable. FF is administered by FieldComm Group. Profibus PA by Profibus & Profinet International. Operating-company selection between them is mostly a function of which DCS vendor the project standardized on.
Does the I/O list look different for an FF project.
Yes. Each segment is engineered for power budget, total cable length, and number of devices. The I/O list grows columns for segment, segment power supply, terminator location, and device address. The project scope expands to include the segment design documents.
What is the H1 segment in Foundation Fieldbus.
H1 is the field-level segment that runs at 31.25 kbit, s on a single twisted pair in an intrinsically safe area. It powers and communicates with up to 32 devices per segment, fewer in practice due to power budgets and cable-length limits. H1 segments connect to a High Speed Ethernet backbone via linking devices or HSE fieldbus interface cards in the DCS.
Can Foundation Fieldbus devices be used in SIS applications.
FF does not have a native safety profile equivalent to PROFIsafe for Profinet. SIS-classified instruments in FF plants are typically wired on conventional 4-20 mA or HART pairs that terminate directly on the SIS logic-solver I/O, separate from the H1 segment infrastructure used for BPCS instruments. FF's lack of a certified safety communication profile is one reason some operators run hybrid projects. FF for BPCS process instrumentation, hardwired 4-20 mA for SIS-classified devices.
Is HSE fieldbus the same as standard Ethernet.
HSE, High Speed Ethernet runs on standard 100 Mbit, s Ethernet physical layer and uses standard TCP/IP and UDP, IP at the transport layer. Above that it carries FF application-layer protocols for the publisher-subscriber model between linking devices, DCS controllers, and HSE-native devices. An HSE segment is not a standard OPC UA or Modbus TCP network. It requires FF-aware DCS components on both ends. HSE is primarily used for H1-to-DCS linking device connections and for high-channel-count HSE field devices such as multi-variable analytical instruments.