Eli Svetanic Control Systems Designer
Share this article

When most people hear about the Year 2038 problem, they dismiss it as an issue for another generation of engineers.  

The issue stems from a limitation in some systems that use 32-bit timestamps to track time. On January 19, 2038, those systems may no longer be able to correctly process dates and times, potentially leading to software errors, incorrect timestamps, communication failures, or unexpected system behavior.

After all, January 19, 2038 is still more than a decade away.

For the nuclear industry, however, the challenge isn't a future date on the calendar. It's the reality that many of the systems being purchased, deployed, and modernized today are expected to remain in service well beyond that date.

That long-term risk was the focus of a presentation I gave at the CNS DIET 2026 Conference in Niagara Falls in October 2026. My message to the audience was simple:

The Year 2038 problem may be years away, but the time to address it is now.

Why Accurate Time Matters

When people think about a date-related software issue, they often picture an incorrect timestamp on a screen.

In reality, time is a critical dependency across industrial control systems, operational technology environments, and the digital infrastructure that supports modern nuclear operations.

Control logic, schedulers, historian databases, operator interfaces, authentication services, certificates, alarms, and communications protocols all rely on accurate and synchronized time. When systems lose that synchronization, organizations can experience communication failures, authentication issues, data integrity concerns, and operational disruptions.

In highly regulated environments such as nuclear power, those consequences can quickly extend beyond technology and into operational reliability, compliance, and cybersecurity.

This Isn't Just a Legacy System Issue

More surprising was the discovery that some equipment purchased as recently as 2024 exhibited date-related limitations well before 2038. Testing identified firmware, networking, and certificate-management constraints that could impact functionality as early as 2035 or 2036 without updates or patches.

The takeaway is clear: organizations cannot assume that recently purchased equipment is automatically future-ready.

Why Nuclear Is Different

Nuclear facilities are designed for longevity. Critical systems often remain operational for decades, and replacing them requires significant engineering effort, regulatory oversight, and investment. As a result, many plant systems currently in operation are expected to remain in service beyond 2038.

At the same time, technology lifecycles continue to shrink. Software, operating systems, and hardware platforms evolve rapidly, creating a growing gap between the lifespan of infrastructure and the lifespan of the technology supporting it.

The Year 2038 problem is ultimately an asset lifecycle management issue. It highlights the challenge of ensuring today's technology decisions remain viable decades into the future while supporting ongoing nuclear modernization initiatives.

Solving the Problem Starts Today

The organizations best positioned for 2038 won't be the ones rushing to fix systems in 2037. They'll be the ones assessing and addressing risk now.

A structured approach begins with understanding where date and time dependencies exist across operational technology environments, legacy infrastructure, and industrial control systems. This includes identifying software, firmware, operating systems, communications infrastructure, authentication services, and connected devices that may be affected.

For many nuclear operators, this assessment can provide valuable insight beyond the Year 2038 problem itself. It helps identify aging technologies, unsupported software, cybersecurity vulnerabilities, and modernization priorities that may impact the reliability and resilience of critical infrastructure over the coming decades.

From there, organizations can:

  • Inventory and prioritize systems based on criticality and lifecycle requirements.
  • Assess vendor guidance and software supportability.
  • Perform controlled rollover testing to understand real-world impacts.
  • Identify vulnerable components and develop mitigation or upgrade strategies.
  • Incorporate Year 2038 requirements into future procurement and modernization initiatives.

Most importantly, organizations should treat the Year 2038 problem as part of a broader asset lifecycle and resiliency strategy rather than a standalone technology issue.

How Alithya Can Help

The Year 2038 problem isn't simply about updating software. It's about understanding how operational technology, industrial control systems, cybersecurity, engineering, and asset lifecycle management intersect across critical infrastructure environments.

Alithya helps utilities and nuclear operators:

  • Assess legacy systems and legacy infrastructure for long-term operational, cybersecurity, and lifecycle risks.
  • Assess operational technology and industrial control system environments for long-term lifecycle risks.
  • Identify vulnerable software, firmware, operating systems, and infrastructure dependencies.
  • Validate system readiness through testing and risk-based assessments.
  • Develop modernization roadmaps that balance reliability, cybersecurity, compliance, and cost.
  • Incorporate long-term resiliency requirements into engineering, procurement, and digital transformation programs.

The Year 2038 problem may seem distant, but the decisions that determine whether systems will be ready are being made today. Organizations that take a proactive approach now will be better positioned to reduce risk, improve resilience, and ensure their critical systems remain secure and supportable for decades to come.