Skip to content

News

UTC underneath, local time on screen

  • News
  • 1 min read

On the first Sunday of November, US clocks run from 1:00 to 1:59 a.m. twice.

An audit trail that stores local time will record two different events in that hour with the same time stamp. 21 CFR 11.10(e) asks for computer-generated, time-stamped audit trails that record the date and time of operator entries and actions. A stamp that can mean two moments is a weak record, and it only takes one deviation investigation in that hour to find out.

Viet Nam runs on UTC+7 all year, with no daylight saving. A system that only ever serves one site here can live with local time. Trouble starts when the same SCADA, historian or LIMS also serves a US site, or when data is pulled together for a US parent company or a US inspection. Now one database holds a zone that never moves and one that moves twice a year, in March and November.

Storing local time keeps the raw data easy to read, and leaves the autumn hour ambiguous and the spring hour missing. Storing UTC gives every event one unambiguous place on the timeline; screens and reports convert to local time for the operator, with the offset shown.

The UTC route costs some work. Every interface, export and report has to convert the same way, and the validation needs test cases for both clock changes. It is still the design we recommend for any system that may one day cross a border.

Related

More on this subject

Annex 11 supplier assessment belongs in the validation plan

EU GMP Annex 11 clause 3.2 makes supplier competence and reliability part of computerized system validation, with the need for an audit set by risk. For SCADA, BMS and EMS, supplier records can reduce the testing the user repeats; the URS, risk assessment and configuration tests such as alarm limits and user roles stay with the user.

InsightRead

Infrastructure qualification under a GMP SCADA

Servers, network, virtualisation, backup and time sync under a GMP system are qualified as a controlled platform; the application on top is validated for its intended use. With the platform qualified, a routine OS patch needs an impact assessment and a targeted check, not a new OQ of the SCADA.

InsightRead

21 CFR Part 11 and EU GMP Annex 11 overlap on validation, access control and audit trails but differ in emphasis: Part 11 on electronic signatures, Annex 11 on a risk-based system lifecycle. Fixing the destination market in the design basis means the URS and validation plan for BMS, EMS and SCADA are written once.

Read