Skip to content

Life Sciences

Five fields every point on an I/O list needs

  • Life Sciences
  • 1 min read

An I/O list that gives each point a tag and a signal type leaves every other decision to whoever programs the controller.

The programmer will make them. Ranges default to 0–100%, alarms sit at the ends of the instrument range, and outputs do whatever the card does on a fault.

A complete line for a point has:

  1. A tag, and a description a night-shift operator would recognise, with the drawing it appears on.
  2. Signal type, range and engineering unit together: "4–20 mA = 0 to 50 °C", and never just "AI".
  3. Alarm limits, delay and priority. Where there is no alarm, the word "none", so that a blank cannot be read as forgotten.
  4. Fail state: what an output does on loss of power or signal, and what the controller does with an input whose wire has broken.
  5. A GMP-critical flag, and for flagged points the calibration interval and tolerance.

The alarm list, the calibration schedule, the loop check sheets for IQ and the test scripts for OQ can all be drawn from it, and they agree because they share one source.

The columns cost a process engineer some days at design stage. Left blank, the same decisions are made at two in the morning during commissioning, by someone with no reason to write them down.

Which of these columns does your programmer fill in for you today?

Industries

Related

More on this subject

Fixed-speed FFUs slow down as their HEPA loads

A fixed-speed fan filter unit loses airflow as its HEPA filter loads. Set at 0.45 m/s, it has 20% to lose before the 0.36 m/s bottom of the Annex 1 guidance range. Constant-airflow EC units hold velocity if they are selected at the final pressure drop, and their speed trend doubles as a filter-loading record.

InsightRead