What Is an ISA-20 Instrument Datasheet?
Before an instrument can be bought, installed, or calibrated, someone has to write down exactly what it must do, and ISA-20 is the standard that structures how. This page explains what an ISA-20 instrument datasheet is, what it captures, and where it sits in the life of an instrument. It is written for the engineer or technician who has seen these spec sheets and wants to understand why they are laid out the way they are and how to use them.
ISA-20 datasheet in one line: An ISA-20 instrument datasheet is a standardized specification form that captures every parameter needed to purchase, install, and calibrate a specific instrument. It records the process conditions the instrument must handle, the required range and output, the materials, the connection details, and the tag, in a consistent layout so a manufacturer, buyer, and technician all read the same fields the same way. It is the single-page contract of what an instrument must be.
How the Datasheet Works
An ISA-20 datasheet is organized so that the information flows from the process to the device. It starts with the service and tag, states the process conditions the instrument will see, such as the fluid, the operating and design pressures and temperatures, and the range to be measured, then specifies the instrument's required response: its calibrated range, its output, and its accuracy class. Because the layout is standardized, anyone reading it knows where to find each parameter without hunting, which is the entire point of using a standard form rather than a free-form specification.
The form separates what the process demands from what the instrument provides, and that separation is what makes it useful. The process side is fixed by physics and the plant design; the instrument side is chosen to satisfy it. A well-filled datasheet lets a reviewer check, field by field, that the selected device actually covers the stated conditions, for example that a pressure transmitter range comfortably spans the operating pressure with margin at both ends.
Where It Fits in the Instrument's Life
The datasheet is the hub that other documents point to across the whole life of the instrument. During design it is the basis for selection and purchase; during procurement it is what the manufacturer quotes against; during installation it tells the technician the connection sizes, materials, and mounting; and during commissioning it gives the calibration range and output the technician uses to verify the device. One consistent form threads through every stage, which is why keeping it current matters.
It also connects to the other core engineering deliverables. The instrument's tag on the datasheet is the same tag that appears on the P&ID and in the loop diagram, so the datasheet, the drawing, and the instrument loop diagram together describe one device from three angles: what it must do, where it sits in the process, and how it is wired. The instrument index lists them all and cross-references the datasheets.
Design and Commissioning Considerations
The parameter that causes the most downstream trouble if it is wrong is the calibrated range. Set it too wide and the instrument wastes resolution on span it will never use; set it too narrow and normal operation drives it off scale. The datasheet forces the range to be stated explicitly, which is a chance to get it right, so treat the range field as a design decision and not a copy-paste. The same discipline applies to the output and accuracy class, which the datasheet states so the calibration technician has a target.
At commissioning, the datasheet becomes the reference for calibration, and the values on it should match what the instrument is actually trimmed to. When the recorded range and output on the datasheet agree with the field calibration and with the scaling configured in the controller, the whole chain from process to SCADA tag is consistent. A mismatch between the datasheet range and the controller scaling is a classic source of a reading that is off by a fixed factor.
Failure Modes and Misuse
The most common failure is the stale datasheet: the field device was replaced or re-ranged during operations, but the datasheet was never updated, so it no longer describes what is installed. A stale datasheet is worse than none, because it invites a technician to calibrate to a range that no longer matches the process. Treating the datasheet as a living document, updated whenever the instrument changes, is what keeps it trustworthy.
The other misuse is under-specifying the process conditions, leaving the manufacturer to guess at the fluid, the design pressure, or the ambient conditions. A datasheet that states the tag and range but omits the process context can still yield a device that survives the average case and fails at the extremes. The value of the ISA-20 form is that it prompts for every field that matters; skipping fields quietly reintroduces the risk the standard exists to remove.
Frequently Asked Questions
What information goes on an ISA-20 datasheet?
The service and tag, the process conditions the instrument will see (fluid, operating and design pressures and temperatures, the range to be measured), the instrument's required calibrated range, output, and accuracy class, and the physical details such as materials, connection sizes, and mounting. The standard layout puts each parameter in a known place so buyers, manufacturers, and technicians all read the same fields.
How is a datasheet different from a P&ID?
A P&ID shows where an instrument sits in the process and how it connects, using symbols and tags. A datasheet specifies what that one instrument must be: its range, output, materials, and process conditions in detail. They share the tag and describe the same device from different angles, the drawing for context and the datasheet for the full specification.
Why does the calibrated range on the datasheet matter so much?
Because it flows into procurement, calibration, and the controller scaling. Too wide and the instrument wastes resolution; too narrow and normal operation runs off scale. When the datasheet range matches the field calibration and the controller scaling, the reading is consistent all the way to SCADA. A mismatch between them is a classic cause of a value that is off by a fixed factor.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.