Field Device

What is a field device?

A field device is a physical device in the field, meaning on the shop floor or in the process plant, that measures a process variable or acts directly on the process and is connected for that purpose to a control system such as a PLC, DCS or SCADA system. Think of a sensor, a transmitter, a control valve with its positioner, an actuator or a motor with a variable frequency drive. Field devices form the bottom layer of every installation: in the Purdue Model they sit at level 0, the physical process, and in the automation pyramid at the field level. Everything a control system knows about the process ultimately comes from a field device.

🧠 What types of field devices are there?

Field devices can broadly be grouped by their role in the control loop: sensing, measuring and transmitting, or acting on the process.

Between the field and the controller there is often infrastructure that is not itself a field device but belongs with it: Remote IO that collects signals close to the process, fieldbus couplers, Ex barriers and field cabinets. In the P&ID every field device gets a unique tag number according to ANSI/ISA-5.1, for example PT-101 for a pressure transmitter. That tag number is the key for engineering, calibration and maintenance.

📡 How does a field device communicate with the controller?

Field devices use a wide range of signals, from a simple contact to full Ethernet. In existing plants all generations often coexist.

A 4-20 mA loop has a live zero: 4 mA is the start of the measuring range, so a broken wire (0 mA) can be detected. The NAMUR recommendation NE 43 specifies that 3.8 to 20.5 mA is a valid measured value and that 3.6 mA or lower, or 21 mA or higher, signals a fault. A 0-10 V signal has no live zero and is more sensitive to voltage drop over long cables; it is mostly found in building automation. Older devices such as flow meters and energy meters sometimes communicate via Modbus, usually as Modbus RTU over RS-485. For the different measuring principles of flow instruments, see flow measurement.

🔧 What makes a field device “smart”?

A smart field device has a microprocessor and firmware. It supplies not only a measured value but also parameters, identification and diagnostics. To configure all these devices in a uniform way, engineering and asset management software uses device descriptions:

• EDDL (IEC 61804-3) - text-based device descriptions (DD files) for HART, PROFIBUS and Foundation Fieldbus
• FDT/DTM (IEC 62453) - a software component per device type that runs inside an FDT frame application
• FDI (IEC 62769) - the successor that combines EDDL and FDT in a single FDI package

Since NAMUR NE 107, diagnostics are reported in a standardised way using four status signals: Failure, Function check, Out of specification and Maintenance required. This lets a maintenance department apply condition monitoring and predictive maintenance. In practice this information often goes unused, because the control system only reads the process variable. Yet for Smart Industry applications this device data is exactly what is valuable. The NAMUR Open Architecture was designed to make these diagnostics available through a second channel.

🏭 Where are field devices used?

• Industrial automation - manufacturing, chemicals, food and pharma; from batch and continuous processes to machine building
• Building automation - HVAC, lighting and access control, with temperature sensors, damper actuators and occupancy sensors
• Energy - energy management and metering, substations and solar parks
• Water - pumping stations, sewage pumping stations and flow measurement at water boards and drinking water companies

✅ What requirements must a field device meet?

Field devices operate in harsh conditions: moisture, dust, vibration, temperature changes and sometimes an explosive atmosphere.

• Enclosure - the IP Code according to IEC 60529 indicates the degree of protection. IP65 withstands water jets, IP67 temporary immersion up to 1 metre for 30 minutes, IP68 continuous immersion under conditions specified by the manufacturer. IP69K (originally DIN 40050-9, now ISO 20653) is used for high-pressure washdown in the food industry.
• Explosion protection - in an Ex zone equipment must comply with the ATEX Directive 2014/34/EU. Common protection types are the flameproof enclosure (Ex d) and intrinsic safety (Ex i), where the energy in the circuit is too low to cause ignition.
• Functional safety - sensors and valves in an SIS receive a SIL rating and must be proof tested periodically.
• Calibration and maintenance - instruments drift and must be calibrated periodically; every device belongs in the asset register alongside your other assets.
• Long service life - field devices often stay in service for fifteen years or more, far longer than IT equipment.

🔐 How vulnerable are field devices?

Classic field communication such as 4-20 mA, HART and PROFIBUS PA has no authentication: anyone with physical access, or access via the systems above, can change settings. For a long time this was acceptable because the field was isolated. Three developments are changing that picture:

• Ethernet into the field - with Ethernet-APL and IO-Link masters with web interfaces, the field gets IP addresses and therefore a network attack surface.
• Access via asset management - HART multiplexers and engineering stations can change the parameters of hundreds of instruments from one place.
• Firmware - smart devices run software with potential vulnerabilities that must be patched.

IEC 62443-4-2 therefore sets security requirements for components, with a separate category for embedded devices (EDR). Many transmitters also have write protection via a jumper or DIP switch; enable it after commissioning. Smart field devices with a data connection fall under the Cyber Resilience Act as products with digital elements: manufacturers must report actively exploited vulnerabilities from 11 September 2026, and the full requirements apply from 11 December 2027. Organisations within scope of the Dutch Cybersecurity Act must take appropriate measures for their network and information systems; it makes sense to give field devices and their engineering access a place in the zones and conduits model as part of that.

🧭 How do you manage field devices in practice?

1. Take inventory - record manufacturer, type, firmware version, protocol, Ex and SIL status per tag number. Combine the P&ID with asset discovery for the digital devices.
2. Choose standards - limit the number of manufacturers and protocols; that saves on spare parts, device descriptions and training.
3. Set calibration intervals - based on criticality, for example annually for custody transfer or safety-related measurements.
4. Use the diagnostics - route NE 107 status signals to the asset management system instead of leaving them on the local display.
5. Secure access - write protection on, HART multiplexers and engineering stations in a separate zone, changes logged.
6. Plan the lifecycle - track in lifecycle management when types are being phased out, and choose deliberately between 4-20 mA with HART, fieldbus or Ethernet-APL when replacing.

❓ Frequently asked questions

What is the difference between a field device and a sensor?

A sensor is one kind of field device: the element that detects a physical quantity. The term field device is broader and also covers transmitters, analysers, actuators, positioners and drives. Anything in the field that measures or acts on the process and is connected to the control system is a field device.

At which Purdue level are field devices?

Field devices sit at level 0 of the Purdue Model, the level of the physical process. The PLCs and DCS controllers that read and control them sit at level 1. Smart field devices with an Ethernet connection make that boundary less sharp in practice.

Is Remote IO a field device?

Strictly speaking, Remote IO is not a field device but an I/O station that collects the signals of field devices close to the process and passes them to the PLC or DCS over a network. It is installed in the field and is therefore often mentioned together with field devices. It does not itself measure or act on the process.

What does a 4-20 mA signal mean for a field device?

A 4-20 mA signal is the classic analogue output of a field device, where 4 mA represents the start and 20 mA the end of the measuring range. Because the range does not start at 0 mA, the controller can detect a broken wire. According to NAMUR NE 43, a current of 3.6 mA or lower, or 21 mA or higher, indicates a fault.

What is Ethernet-APL for field devices?

Ethernet-APL is a physical layer that brings 10 Mbit/s Ethernet over two wires right into the field device, including power and intrinsic safety. A spur to the device may be 200 metres long and a trunk up to 1,000 metres. Over time, Ethernet-APL can replace 4-20 mA and classic fieldbuses in the process industry.

Do field devices need to be secured?

Field devices need to be secured because changing a measuring range or valve setting has a direct effect on the process and on safety. Classic field protocols have no authentication, so protection comes mainly from write protection, network segmentation and restricted access to engineering tools. New smart field devices must also comply with the Cyber Resilience Act.

📌 In summary

Field devices are the sensors, transmitters, actuators, positioners and drives at level 0 that form the physical link between the digital control system and the real process. They communicate via 4-20 mA, HART, fieldbuses, IO-Link or Ethernet-APL, must withstand harsh and sometimes explosive conditions, and often stay in service for fifteen years or more. With smart diagnostics and Ethernet reaching into the field, they become more valuable for maintenance, but also part of the cybersecurity of the plant.