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.



