Once you have chosen a barrier and a field device, how do you actually prove the intrinsically safe loop between them is safe? You do not send it to a lab - you check it on paper, using a small set of certified numbers called entity parameters. The entity concept lets anyone verify an IS loop by comparing what the barrier can deliver against what the field device can safely accept, with the cable's own storage taken into account. This guide explains the parameters, the matching inequalities, and why the entity concept is the practical answer to how you verify intrinsic safety.
Entity Parameters in one line: Entity parameters are the certified numbers used to verify that a barrier and a field device form a safe intrinsically safe loop. The barrier is rated by what it can deliver into a fault - its output voltage (Voc or Uo), current (Isc or Io), and the maximum cable capacitance (Ca or Co) and inductance (La or Lo) it can tolerate. The field device is rated by what it can safely accept - Vmax (Ui), Imax (Ii), and its own internal capacitance (Ci) and inductance (Li). If the barrier's outputs stay within the device's limits and the cable fits within the allowances, the loop is certified safe on paper.
The entity concept splits an intrinsically safe loop into two rated ends and a cable between them, each described by a handful of parameters. The barrier, or associated apparatus, is characterized by the most it could ever push into a fault: its open-circuit output voltage, written Voc or Uo; its short-circuit output current, written Isc or Io; and the maximum external capacitance and inductance it can safely drive, written Ca and La, or Co and Lo. These last two are the barrier's budget for energy storage in whatever is connected to it - primarily the cable.
The field device, the apparatus in the hazardous area, is characterized by the most it can safely take: its maximum input voltage, Vmax or Ui; its maximum input current, Imax or Ii; and, crucially, the energy-storing elements inside the device itself - its internal capacitance, Ci, and internal inductance, Li. A field device is not just a passive load; it contains capacitors and inductance that can store energy and release it as a spark, so those internal values have to be counted against the barrier's allowance. The device's datasheet or certificate lists all four.
Between the two ends sits the cable, which is the third party in every entity calculation. Cable is not merely a connection; it has capacitance and inductance per unit length, and over a long run those add up to a meaningful store of energy that could feed a spark. The entity method treats the cable's total capacitance and inductance as things that must fit inside the barrier's Ca and La budget alongside the field device's own Ci and Li. This is why a loop that is safe over a short cable can become unsafe over a long one, purely because the cable's stored energy grows with length.
Verifying the loop is a matter of checking a small set of inequalities, and every one of them has to pass. First, the barrier must not be able to over-voltage or over-current the device: the barrier's Voc must be less than or equal to the device's Vmax, and the barrier's Isc must be less than or equal to the device's Imax. In plain terms, the most the barrier can ever push must be no more than the most the device can safely accept. If either of these fails, the barrier can drive the field device beyond its safe rating under fault, and the loop is not intrinsically safe.
The second pair of checks governs stored energy. The barrier's allowed external capacitance, Ca, must be greater than or equal to the sum of the device's internal capacitance, Ci, plus the total cable capacitance. Likewise the barrier's allowed external inductance, La, must be greater than or equal to the device's internal inductance, Li, plus the total cable inductance. The barrier can only tolerate so much stored capacitance and inductance hanging off it before a fault could release enough energy to ignite; the device's own internals and the cable both eat into that allowance, so both must be subtracted from the budget.
The practical workflow is to take the barrier's four numbers and the device's four numbers from their certificates, compute the cable's total capacitance and inductance from its per-length figures and the run length, and run through the checks. If Voc is within Vmax, Isc is within Imax, and Ca and La each cover the device internals plus the cable, the loop passes. The elegance of the method is that it needs no test lab and no special equipment - just the certified parameters and the cable length - which is exactly what makes it usable by an engineer verifying a design or a technician checking an installation in the field.
The reason the entity concept matters is that it turns intrinsic-safety verification from a laboratory exercise into a paperwork one that anyone competent can perform. Before the entity approach, proving a particular barrier-and-device combination was safe could mean testing that exact combination. The entity concept decouples the two ends: certify the barrier by its output parameters and the device by its input parameters once, publish those numbers, and then any pairing can be checked by comparing numbers rather than by testing hardware. This is what lets a designer mix a barrier from one maker with an instrument from another and still prove the loop is safe.
It also makes the cable a first-class part of the safety case rather than an afterthought. Because the method forces you to add the cable's capacitance and inductance to the device's internals and check the total against the barrier's allowance, it captures the real-world fact that a long run stores more energy. That is why an IS loop sheet records the cable type and maximum length - those figures are part of the verification, and extending a cable beyond the length the entity calculation allowed can invalidate the safety of a loop that was previously fine. The entity concept keeps that constraint explicit and checkable.
For field operations and SCADA work, the entity calculation is the artifact that lets a loop be commissioned, modified, and audited with confidence over its whole life. When an instrument in a hazardous area is replaced, its entity parameters are checked against the existing barrier and cable before it goes in; when a cable is rerouted or lengthened, the capacitance and inductance are rechecked. A cloud SCADA platform such as Merobix reads the safe 4-20 mA value the loop produces and never sees the entity numbers directly, but the documentation that the platform's tag points back to - the loop sheet with its Voc, Isc, Ca, La and the device's Vmax, Imax, Ci, Li - is what proves that particular hazardous-area measurement was gathered without ever carrying ignition-capable energy into the field. Keeping that entity verification current is part of keeping the whole monitored system both safe and auditable.
They describe what a barrier or associated apparatus can deliver into a fault. Voc (also written Uo) is the maximum open-circuit output voltage, Isc (Io) is the maximum short-circuit output current, Ca (Co) is the maximum external capacitance the barrier can safely tolerate, and La (Lo) is the maximum external inductance. The field device's own internal capacitance and inductance plus the cable's must both fit within the barrier's Ca and La allowances.
You compare the barrier's output parameters against the field device's input parameters and the cable. The checks are: the barrier's Voc must not exceed the device's Vmax, its Isc must not exceed the device's Imax, its allowed capacitance Ca must be at least the device's Ci plus the cable capacitance, and its allowed inductance La must be at least the device's Li plus the cable inductance. If all four pass, the loop is certified safe without any lab testing.
Because cable has capacitance and inductance per unit length, and over a long run those add up to a meaningful store of energy that could feed an igniting spark. The entity method adds the cable's total capacitance and inductance to the field device's internal values and checks the sum against the barrier's allowances. A loop that is safe over a short cable can fail the check over a long one, which is why the maximum cable length is part of the IS verification and recorded on the loop sheet.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.