January 2027 is closer than it looks
UNECE WP.29's R185 will require a documented safety case, audited for coverage of the conditions a vehicle is reasonably expected to face. That evidence has to come from your data pipeline. If the pipeline wasn't built to produce it, that becomes an expensive problem very quickly.
In his new blog, our CEO Ziv Binyamini explains why the leading programs are already treating the safety case as an engineering output of development and validation, not something assembled at the end for the regulator.
The key is a unified data flywheel: one foundation of prepared, labeled, continuously evolving real-world data, extended with synthetic data where more coverage is needed, serving development, validation, and safety alike.
OEMs are making this decision right now as they build their pipelines. Here's how to get it right: https://lnkd.in/dJvhQPcx
Why this matters for talent
Foretellix is arguing that a coming UNECE requirement makes the safety case an engineering output, not paperwork assembled at the end. If that view holds, safety engineers, data pipeline engineers and validation leads get pulled closer to the core of development programs. It is a vendor making its own case, so weigh it that way, but regulatory deadlines do tend to move hiring budgets. Engineers who can connect safety evidence to data systems should pay attention.
Read the original LinkedIn post. Curated by Larry Sherwood Jr. from company announcements; analysis above is my own.