Support and Evolution

On Sunday, 1 a.m. happens twice

In this article

Nori.mx7 min read

NOVEMBERSunday12:00 → 1:00Juárez and El PasoScans1:40Pallet A1st pass1:10Pallet B2nd passDowntime−45 min1:50 → 1:05actual: 15 minBy time: B before ANight shift23:00 → 7:00Clock says8 hWorked9 h

This Sunday, November 1, at two in the morning, the clocks in Ciudad Juárez go back to one, just like the ones in El Paso. For most people it is an extra hour of sleep. For the night shift it is an extra hour of work. And for any system that stores the time exactly as the wall clock shows it, it is an hour that happens twice.

Almost nothing crashes that night. What happens is quieter: records that end up out of order, an hour of payroll that never shows up, and a server that runs an hour ahead from Sunday on without anybody noticing until someone disputes a late arrival.

What changes on Sunday, and what does not

Mexico’s 2022 Time Zones Law did away with daylight saving time in almost the whole country, but kept it for the northern border. Juárez, Janos, Ascensión, Praxedis G. Guerrero and Guadalupe follow the US calendar: daylight time starts at 2 a.m. on the second Sunday of March and ends at 2 a.m. on the first Sunday of November. The next change is March 14, 2027, and that day the hour is skipped instead of repeated.

The rest of Chihuahua and Mexico City do not change at all. They stay on the same time all year. That has a consequence worth understanding:

  • From March to November, Juárez and Mexico City share the same time.
  • From November to March, Juárez is one hour behind Mexico City and Chihuahua City, and still matches El Paso.

That is why a misconfigured machine can go all summer without anyone noticing. If it was left on Mexico City time, it was right from March on, and from Sunday it will be an hour ahead for four and a half months.

Four things that break that night

1. The night shift works nine hours in an eight-hour shift. If someone clocks in at 11 p.m. and out at 7 a.m., the clock says eight hours and the person was there for nine. A payroll system that subtracts clock-in from clock-out never sees that hour. How it gets paid is for your payroll team and their advisor to decide; what the system has to do is show it, because it was worked. In March it goes the other way: the same shift lasts seven hours and the math says eight.

It matters more this year than most. Starting January 1, 2027, Mexican law requires the record of working hours to be electronic, and that record is the one you will show if the authorities ask for it. It should show the hours that were actually worked.

2. The 1 a.m. records get mixed up. At 1:40 a pallet is scanned. Half an hour later the clock has already gone back and reads 1:10, and another one is scanned. If the system stores only local time, the second one is recorded before the first. When you sort by time to trace a lot or check what came in first, the order is backwards.

Durations are worse. A stop that starts at 1:50 on the first pass and ends at 1:05 on the second lasted fifteen minutes. Subtracting the clock times, it lasted minus forty-five. Some reports leave it like that, others drop it without saying so, and neither one is the stop that happened.

3. The hourly board shows one hour with twice the parts. If production is grouped by clock hour, the 1 a.m. slot adds up two hours of work and shows up at double the target. That is a number somebody will copy into the weekly report, on top of the numbers that already inflate OEE without anybody lying.

4. The server that lives on Mexico City time runs an hour ahead. This is the most common mistake and the one that lasts longest. A server, an ERP or a cloud service set to “Guadalajara, Mexico City, Monterrey”, or to the America/Mexico_City zone, was right all summer. From Sunday on, it puts everything an hour later:

  • The 6:55 clock-in shows up at 7:55, and on a shift that starts at 7:00 that is a late arrival.
  • The inventory cutoff scheduled for midnight runs at 11 p.m. in Juárez, and the last hour of second shift lands on the next day.
  • The ship notice goes out with a time that does not match your customer’s in El Paso, whose clocks did change.

The America/Chihuahua zone has the same problem, because Chihuahua City does not change its clocks either. And the other way around: a machine on “La Paz, Mazatlan”, which is always seven hours behind universal time, becomes correct on Sunday, which means it has been an hour off since March.

What to check before Sunday

Almost all of this can be checked in a morning, and none of it requires buying anything.

  1. The time zone of every server. On Linux, the right zone is America/Ciudad_Juarez; timedatectl tells you which one it has. That zone has existed since November 2022, so if the server does not recognize it, its time zone table has not been updated since then, and probably other things have not either. On Windows, tzutil /g gives you the zone; for Juárez it is Mountain Standard Time, the same as El Paso. It is not “Mountain Standard Time (Mexico)”, which never changes, and it is not Mexico City’s.
  2. The clocks in time clocks and terminals. Many have their own daylight saving setting, separate from the server. Check that they are set to change on the first Sunday of November. If one of them went back on its own last Sunday, it carries the rule the rest of Mexico used before 2022, and it will be wrong again in March.
  3. Jobs scheduled between 1 and 2 a.m. A backup, a transmission or a cutoff scheduled for 1:30 may run twice on Sunday, depending on the tool, and may not run at all in March. Move them out of that hour.
  4. Who works that night. Give payroll the list of the shift that crosses 2 a.m., with clock-in and clock-out times, so the numbers can be compared on Monday against what the system calculated.
  5. On Monday, the 1 a.m. records. Pull everything recorded between 1 and 2 a.m.: clock-ins, scans, downtime and production. If you see negative durations, hours with twice the parts or events out of order, you now know which system stores time without its zone.

The real fix

Changing the server’s time twice a year is not a fix: it is repeating the same mistake on a different date. The fix is for the system to store every event with its time zone, or directly in universal time, and convert it to Juárez time only to display it. That way, the 1 a.m. on the first pass and the 1 a.m. on the second are two different moments, and totals, ordering and durations come out right on their own.

Databases almost always have a data type for this. What takes work is everything written on top of it over the years on the assumption that local time was enough: reports, payroll exports, interfaces with the ERP. It is a contained change, but you have to find every place where one time is subtracted from another.

Where we come in

That work is exactly what we do in support and evolution: go into a system that already works, find where it stores time without its zone, and fix it without shutting anything down. If on Monday you find odd 1 a.m. records, send us the sample and we will tell you where they come from. And if you want to know what else is worth checking in your systems, Chira asks you the questions in five minutes and leaves you a document with what to fix first.

References

Related service

Support and Evolution

Launching the software is the beginning. Keeping it alive is the work.

See the service

Articles on this service

Copy 1Office serverCopy 2External driveCopy 3OffsiteRestore testFile: invoices-2026.xlsxCopy used: 3, offsiteOn another machineIt opened in full

Support and Evolution

A backup is worthless until you restore it

Almost every company backs up and almost none tests a restore. What to copy, where to keep it, how to test it and who has to own it.

7 min read

Plant serverYour applicationSQL Server 2016Windows Server 2016Last patchJanuary 12, 20271Upgrade2022 or 2025, app on top2Extended updatesThrough 2030, via Azure Arc3IsolateOff the general network

Support and Evolution

Windows Server 2016 runs out of patches in January

Windows Server 2016 gets its last patch on January 12, 2027. What end of support really means, the three ways out, and why the hard part is the app that runs on it.

8 min read

final_v3system.execonfig.inidata.mdb12 years on the floorThe two-hour testIs the source code there?Is it in version control?Does it build today?Does it run on a copy of the DB?If #1 fails, it is an installation

Support and Evolution

You inherited software nobody documented

It works, nobody knows how, and the person who wrote it is gone. How to tell whether it can be rescued or has to be replaced, and what to do in week one.

7 min read