The ISA S20 Instrument Datasheet. Field by Field

An ISA S20 instrument datasheet is the standard per-tag specification form for a field instrument: one document that records everything needed to select, purchase, install, and calibrate a single tagged device. The forms were published by ISA as the S20 series and are maintained today as technical report ISA-TR20.00.01, Specification Forms for Process Measurement and Control Instruments, with a separate form for each device category, from pressure transmitters to control valves to analyzers. Whatever the device, the fields fall into the same groups: general and service identification, process conditions, element and body selection, materials of construction, performance and calibration, connections and installation, options and accessories, and a revision and approval block. Three parties fill it in sequence. The process engineer supplies the process data, the instrument engineer makes the selection, and the vendor confirms what will actually be supplied. This is a field-by-field walk through those groups.

From S20 to TR20.00.01

ISA published the specification forms as the S20 series decades ago and has carried them forward as a technical report, ISA-TR20.00.01, extended several times with new forms as device categories multiplied. The current editions split each instrument's specification across linked pages: operating parameters, device specification, and general requirements. In practice almost nobody outside a standards library fills in the ISA sheet verbatim. Operators and engineering contractors maintain house templates, built in a spreadsheet or a database tool, that reproduce the S20 field structure with company formatting and numbering on top.

That is why the field semantics matter more than the form itself. The forms are purchasable documents and the layouts belong to ISA, but the meaning of the fields is common engineering knowledge, and it is the part that transfers between every template you will ever be handed. Learn what each group is for and who owns it, and the specific form is just typography.

The field groups at a glance

General and service fields

The top of the form identifies the device and anchors it to the rest of the document set. The tag number must match the P&ID and the instrument index character for character; a datasheet for FT-4711 that the index carries as FT-4711A is two records for one device, and someone will purchase against the wrong one. The service description states what the instrument measures in plain words, the same wording that will appear on the index and the loop drawing. The P&ID number and revision record where the tag lives and which version of the drawing the data was read from. The line or equipment number places the device on a specific pipe or vessel, which is what makes the process data on the next block checkable. Quantity matters on datasheets that cover several identical tags: a voted transmitter set can share one sheet with three tags listed, provided the service is genuinely identical.

Area classification appears here too, usually as a reference to the hazardous area drawing plus the zone or division, gas group, and temperature class. This single field drives the certification requirements on every electrical device on the sheet.

Process conditions

This is the block that sizes the instrument, and it is the one the instrument engineer cannot invent. The fluid name and phase come first, with composition where it affects the measurement. Then the operating cases: flow, pressure, and temperature each stated at minimum, normal, and maximum, because an instrument selected on the normal case alone will misbehave at the edges. Density and viscosity follow, stated at operating conditions rather than at the laboratory reference, since both change with temperature and both matter to flow and level measurement. Design pressure and design temperature close the block; they set the mechanical rating the body and connections must survive, independent of what the process normally does.

Two conventions cause most of the grief in this block. First, units. A form that mixes barg from the process simulation with psig from a licensed unit package, or kg/h with normal cubic meters per hour, will pass a casual review and fail at the vendor. Pick the project unit set and convert everything before the sheet leaves the originator. Second, the basis of gas flow: normal, standard, and actual volumetric flow are three different numbers for the same stream, and the reference conditions belong on the sheet next to the value.

Element, body, and transmitter fields

Here the instrument engineer records the selection: the measurement principle and the hardware family that implements it. For a flow transmitter this is where orifice, Coriolis, magnetic, vortex, or ultrasonic is declared, along with meter size, which is a sizing outcome rather than a pipe-size copy. For a pressure transmitter the fields cover gauge, absolute, or differential reference, and whether a diaphragm seal system is fitted. For a control valve the equivalent block carries body style, port size, characteristic, and actuator type. The fields differ by device category, which is exactly why S20 publishes a different form per category, but the intent is constant: state the hardware unambiguously enough that two vendors quote the same thing.

Materials

The materials block lists every surface the process touches, and then the pressure envelope around it. Wetted parts govern corrosion: element, diaphragm, sensor tube, or trim, each with a named grade rather than a family. Writing stainless steel where the service needs 316L invites a 304 substitution that is technically responsive to the sheet. Body and flange material follow, then seals, gaskets, and O-rings, which fail before metal does in most services. Diaphragm-seal fill fluid gets its own line where fitted, because fill fluid choice is a temperature and compatibility decision, and on some services a food-grade or oxygen-clean fill is mandatory. Where the process is sour, the block references the applicable material standard for sulfide stress cracking resistance, and that reference flows into the purchase order as a hard requirement.

Performance and calibration

The calibrated range and its units are the most consequential fields on the whole form, because they leave the datasheet and propagate: the range on the sheet becomes the range column on the I/O list, which becomes the scaling in the control system. A transmitter can often be re-ranged in the field, but every document downstream was built on the number written here. The output signal field states 4-20 mA, a fieldbus protocol, or a discrete output, and it must agree with the signal class the I/O list carries for the tag. The accuracy statement records the required performance as a fraction of span or of reading, at stated conditions; the vendor's confirmed figure lands next to it at quotation. Damping, turndown, and response time appear where the measurement needs them, and for control valves this group carries the calculated flow coefficient at each process case along with the predicted noise and cavitation checks.

Connections, installation, options

The connections block ties the instrument to the plant physically: process connection type, size, and rating on one side, electrical entry thread and cable specification on the other. Mounting and orientation fields record whether the device hangs on the pipe, a bracket, or a stand, and any orientation the measuring principle requires. The options block sweeps up everything else that must arrive in the box or the quote: a three- or five-valve manifold, a local indicator, mounting hardware, calibration certificates, material traceability, and the hazardous-area certificate matching the classification declared at the top of the sheet. Anything not written here is not in the purchase order, and site-sourced accessories bought at commissioning cost multiples of what they cost at requisition.

Worked example. FT-4711, reactor feed flow

One invented instrument, populated to the level a sheet should reach before it goes to the vendor:

Note the shape of the collaboration. Every process row exists before the selection rows can be trusted, the meter size differs from the line size because sizing said so, and the vendor's rows are honestly blank until the quote lands rather than padded with catalogue guesses.

Common mistakes

Blank process data sent to vendors. The most common failure. The requisition deadline arrives, the process cases are still provisional, and the sheet ships with the conditions block half empty. The vendor sizes on assumptions, the assumptions become the quote, and the mismatch is discovered when the meter meets the real startup case. A provisional value marked as provisional is workable; a blank is not.

Units mixed across sources. Process data pasted from a simulation in one unit set, design limits copied from a mechanical datasheet in another. The sheet reads fine until someone converts.

The normal case standing in for all three. Minimum and maximum copied equal to normal, because the extremes were never asked for. Turndown problems are invisible on such a sheet.

Range drift against the I/O list. The transmitter is re-ranged during detailed design, the datasheet revises, and the I/O list does not. The control system is then scaled to a number no instrument in the field carries.

Revision control by memory. The sheet does not state which P&ID revision fed it, so when PID-047 moves from C to D nobody can say whether FT-4711's data is current. Tie every datasheet revision to a drawing revision explicitly, and on operating plants route changes through management of change.

Tag and service inconsistency across documents. The datasheet, the instrument index, and the loop drawing each describing the same device slightly differently. Every discrepancy costs a commissioning engineer a lookup, and some cost a wrong termination.

Where the datasheet sits in the document set

The instrument datasheet is the deep record for one tag; the instrument index is the wide record for all of them. The index lists every tagged device with its service, P&ID, and document references, and each index row points at exactly one datasheet. The I/O list is narrower again: only the wired tags, with the signal-facing fields the control system needs, several of which, range, units, output, originate on the datasheet. The three documents answer different questions, and the boundaries between them are covered in instrument index vs I/O list vs line list. All three trace back to the same source: the tags on the P&ID set, read per ISA 5.1 or the project's tagging standard.

That lineage is the practical reason datasheet quality starts before the datasheet. If the tag list pulled from the P&IDs is incomplete or inconsistent, every sheet built on it inherits the defect. Tagsight gives your engineers an instrument index and I/O list built from the P&ID set, ready for their review, so the datasheet register starts from a checked tag list (P&ID to instrument index).

A datasheet is finished when all three authors have signed their blocks, the revision states its P&ID basis, and the range on the sheet matches the range on the list. Anything less is a draft, whatever the title block says.