Is ISA 84 the same as IEC 61511? Substantially, yes. ANSI/ISA-84.00.01 is the American National Standard through which the US adopted IEC 61511, and the two carry the same safety lifecycle, the same Safety Integrity Level framework, and largely the same clause structure. It is the same technical content, published by two different standards bodies, under two different names.
That matters past terminology. A project specification calling for design per ISA 84 and one calling for design per IEC 61511 are asking for the same hazard-to-SIF traceability, the same Safety Requirements Specification content, and the same I/O list structure. The one place a real distinction shows up is a transitional provision US practice associates specifically with the ISA 84 designation, covering how an existing SIS designed to earlier practice is treated. The standard's content in full is covered in IEC 61511 for the I&C engineer. What follows is the narrower question of how the two names relate, and what either one demands of the document set.
Key takeaways
- ANSI/ISA-84.00.01 is ISA and ANSI's adoption of IEC 61511 as an American National Standard, with the same safety lifecycle, same SIL framework, and shared clause structure.
- The two names exist because ISA had already developed a US standard for safety instrumented systems before the international work concluded, then aligned it with IEC 61511 rather than maintaining a separate technical position.
- A client specification that cites ISA 84 and one that cites IEC 61511 are asking for the same document set in nearly every practical case.
- The one US-specific provision worth knowing is often called the grandfather clause, which lets an existing SIS designed to earlier practice remain in service where the operating company evaluates it and documents that it is safe as installed.
- Either designation places the same demand on the SRS, the SIF register, and the I/O list, namely safety points demarcated from BPCS points, a SIL field carried per SIF, and a record that survives revisions.
Why two names exist for one body of content
International standards are rarely adopted verbatim everywhere they are used. IEC 61511 is published by the International Electrotechnical Commission. ANSI/ISA-84.00.01 is published by ISA and adopted as an American National Standard through ANSI. ISA had already developed its own standard for safety instrumented systems in the process industries before the IEC effort concluded, and when the international work finished, ISA aligned its standard with it rather than keeping a separate technical position. The result is a national standard that tracks the international one closely enough that engineers on both sides treat the two as interchangeable for design purposes.
The two names persist because many owner-operator engineering standards and project specifications were written when ISA 84 was the term in common use, and revising every document to cite IEC 61511 instead has not been a priority for most operating companies. Both names point at the same body of requirements. Which one a project uses is a matter of house style, not substance.
Where the names line up
| Dimension | ANSI/ISA-84.00.01 | IEC 61511 | IEC 61508 |
|---|---|---|---|
| Publishing body | ISA, adopted as an American National Standard through ANSI | International Electrotechnical Commission | International Electrotechnical Commission |
| Scope | Process industry SIS, US national adoption | Process industry SIS, international | Safety-related electrical, electronic, and programmable electronic systems generally, all sectors |
| Primary audience | Owner-operators, EPCs, and I&C engineers on US process plants | Owner-operators, EPCs, and I&C engineers on process plants worldwide | Device and system manufacturers |
| Safety lifecycle | Hazard analysis through decommissioning, aligned with IEC 61511 | Hazard analysis through decommissioning | The development lifecycle of the safety device or system itself, not a plant lifecycle |
| Typical citation | "Per ISA 84" in US-domestic or older specifications | "Per IEC 61511" in international or newer specifications | Cited for device SIL capability, rarely cited directly by the I&C engineer |
What a client spec means by "per ISA 84"
When a project specification calls for compliance per ISA 84, it is asking for the IEC 61511 safety lifecycle under its US name, not for something in addition to it. The SRS, the LOPA-to-SIF traceability, the SIL verification, and the proof-test program a spec of this kind expects are the same items an IEC 61511-referenced spec expects.
An engineer working from a client specification does not need to resolve which designation governs before starting design. The document set the safety lifecycle demands is the same either way. It is worth flagging, in the design basis, which term the project standard uses, so the terminology stays consistent from the SRS through the closeout package rather than drifting between two names across a project's life.
The grandfather clause, in concept
US practice includes a transitional provision, commonly called the grandfather clause, that is closely associated with the ISA 84 designation. At a conceptual level, a safety instrumented system designed and installed under earlier practice is not automatically required to be redesigned or upgraded to match current requirements. The operating company is expected to evaluate the existing SIS, determine whether it remains safe to operate as installed, and document that determination. Where that judgment cannot be supported, the SIS is brought up to current practice.
The provision assigns a judgment call to the operating company. It is not a blanket exemption, and it does not remove the obligations that apply through the rest of the operating phase. Proof testing, management of change, and periodic reassessment still apply to a grandfathered SIS. An I&C engineer encountering an older SIS on a brownfield project should expect to find, or ask for, the documented basis for treating it as grandfathered rather than assuming it by default.
What either name demands of the document set
The naming question matters less than what happens once the design starts, because both designations place the same requirement on the paperwork. A P&ID can show a safety function correctly and still fail a review if the SIF register, the SIL target, and the safety classification do not carry through to the I/O list in a form a reviewer can trace without opening a second document.
| Document | What it carries | Where it shows up on the I/O list |
|---|---|---|
| Safety Requirements Specification | The safe-state action and integrity requirement for each SIF | Referenced by SIF identifier on each safety-classified row |
| SIF register | Every Safety Instrumented Function, its SIL target, and its safe-state definition | The SIL target and SIF identifier columns |
| Hazard and LOPA record | The scenario and risk reduction factor behind each SIL target | Not a column itself, but the source the SIL target column must trace back to |
| I/O list | The BPCS/SIS classification and the rack or card each point lands on | The classification column and the rack or system column, covered in SIL-rated I/O |
Neither designation changes what an engineer does at the drawing board. What it changes is the standard of evidence a reviewer expects, namely safety points demarcated from BPCS points, a SIL field carried per SIF rather than guessed per instrument, and a record that survives revisions instead of being rebuilt from the drawing each time the set changes. Tracing a SIF from the HAZOP finding through to its I/O list row without a gap is the practical effect either designation is asking for.
Where IEC 61508 fits
IEC 61508 sits above both. It is the umbrella functional safety standard covering the development of safety-related electrical, electronic, and programmable electronic systems generally, across industries, and it governs how a device or logic solver manufacturer demonstrates SIL capability. IEC 61511, and by extension ANSI/ISA-84.00.01, is the process-sector application of that framework. It is the standard an I&C engineer works to on a plant, referencing IEC 61508 for device qualification without repeating its content. For the fuller picture of how the lifecycle divides between hazard study, realisation, and operation, see IEC 61511 for the I&C engineer and the short-form what is SIL.
A starting point
If a project specification names ISA 84, treat it as a request for the IEC 61511 safety lifecycle under its US label, not as a separate set of requirements. Confirm the designation in the design basis, keep the terminology consistent through the SRS and the I/O list, and reserve the grandfather provision for existing SIS with a documented basis, not as a default assumption for anything installed before the current edition. The document set either name demands is unchanged, namely an SRS, a SIF register with traceable SIL targets, and an I/O list that keeps SIS and BPCS points demarcated through every revision. For the BPCS/SIS boundary itself, see BPCS and SIS separation.