Saudi SASO Mandates ISO 22513-2 RDI for Heavy Trucks from Aug 2026

Saudi Arabia’s Standards, Metrology and Quality Organization (SASO) issued a technical notice on May 22, 2026, introducing a mandatory remote diagnostic interface (RDI) requirement for imported heavy-duty trucks. Effective August 1, 2026, all new heavy truck imports must be equipped with an RDI compliant with ISO 22513-2:2025 — enabling real-time transmission of engine, ABS, ADAS, and battery health data to Saudi Arabia’s national transport regulatory platform. This marks a significant regulatory shift in the Gulf region’s vehicle type-approval framework, directly impacting China-based heavy truck OEMs, Tier 1 suppliers, and intelligent driving system developers engaged in Middle East exports.

Event Overview

On May 22, 2026, SASO published a formal technical notice stipulating that, starting August 1, 2026, every newly imported heavy-duty truck entering Saudi Arabia must feature a pre-installed remote diagnostic data interface conforming to ISO 22513-2:2025. The interface must support authenticated, secure, and standardized data streaming of critical vehicle subsystems — specifically engine control unit (ECU), anti-lock braking system (ABS), advanced driver assistance systems (ADAS), and high-voltage battery health metrics — to the Saudi Transport Regulatory Platform. Non-compliant vehicles will be ineligible for SASO Certificate of Conformity (CoC), thereby blocking market access.

Industries Affected

Direct Trading Enterprises: Exporters and distributors of Chinese heavy trucks face immediate certification delays and potential shipment rejections if their current model portfolios lack RDI hardware and software integration. Compliance verification now requires not only physical interface installation but also backend data routing, encryption, and protocol alignment with Saudi authorities’ API specifications — extending lead time for CoC issuance by 4–8 weeks per model variant.

Raw Material Procurement Enterprises: Suppliers sourcing electronic components — particularly automotive-grade microcontrollers, CAN FD transceivers, secure boot modules, and cellular communication chips (e.g., LTE Cat-M1/NB-IoT) — are seeing revised bill-of-materials (BOM) requests from OEMs. Demand is shifting toward components certified for ISO 22513-2 message framing and TLS 1.3–based secure channel support, prompting procurement teams to reassess vendor qualification and lead-time buffers.

Manufacturing Enterprises: Heavy truck assemblers and chassis-integrated system integrators must redesign or retrofit vehicle electronic architectures to embed RDI functionality at the gateway or telematics control unit (TCU) level. This includes firmware updates for ECU-level data extraction, implementation of ISO 22513-2 message sets (e.g., Diagnostic Data Stream 0x01–0x0F), and integration testing with SASO’s reference validation platform — a process requiring cross-functional engineering coordination across powertrain, chassis, and infotainment domains.

Supply Chain Service Providers: Certification consultants, homologation labs, and logistics firms specializing in GCC vehicle compliance now need updated test protocols, SASO-recognized RDI validation tools, and trained personnel fluent in ISO 22513-2 conformance testing. Third-party test reports must include evidence of successful data handshake, payload integrity, and timestamp synchronization — adding complexity beyond traditional EMC or safety testing scopes.

Key Focus Areas and Recommended Actions

Verify Model-Level RDI Readiness Before Q3 2026

OEMs should conduct internal gap assessments against ISO 22513-2:2025 Annex A (mandatory data elements) and Annex B (communication requirements) before July 2026. Prioritize models with scheduled Saudi deliveries between August and December 2026; retrofitting post-shipment is not permitted under the new CoC rules.

Engage Early with SASO-Accredited Validation Labs

Only laboratories listed in SASO’s updated ‘Approved Testing Facilities’ directory (updated April 2026) may issue RDI conformance reports acceptable for CoC applications. Pre-submission validation — including simulated data upload to the sandbox environment of the Saudi Transport Regulatory Platform — is strongly advised to avoid iterative rejection cycles.

Update Export Documentation and Firmware Version Control

Technical files submitted for CoC must include RDI firmware version logs, cryptographic key management documentation, and a signed declaration of data scope coverage (e.g., which ADAS features are actively streamed). Any firmware update deployed post-certification triggers revalidation — meaning version control and traceability must be embedded into production quality systems.

Editorial Perspective / Industry Observation

Observably, this mandate signals Saudi Arabia’s strategic pivot from passive vehicle regulation to active, data-driven fleet governance — aligning with Vision 2030’s smart mobility objectives. Unlike EU’s UNECE R155/R156 cybersecurity management system (CSMS) framework, SASO’s approach focuses narrowly on diagnostic data accessibility rather than full SDV lifecycle security. Analysis shows this lowers the entry barrier for mid-tier suppliers but raises interoperability pressure: ISO 22513-2 remains a relatively new standard (published March 2025), with limited global adoption outside GCC markets. From an industry perspective, it is more accurate to view this not as a standalone compliance hurdle, but as the first visible layer of a broader regional telematics regulatory architecture likely to expand to light commercial vehicles by 2027.

Conclusion

This requirement represents a material inflection point for export-oriented heavy vehicle stakeholders — less about incremental certification adjustment and more about foundational readiness for connected vehicle data governance. For Chinese manufacturers, timely adaptation offers competitive differentiation in a consolidating GCC market; delay risks marginalization in favor of EU- or Korea-based OEMs already embedding similar interfaces. A rational interpretation is that SASO is using heavy trucks as a controlled pilot for scalable telematics oversight — making responsiveness here a leading indicator of future regulatory exposure across adjacent vehicle segments.

Source Attribution

Official source: SASO Technical Notice No. TN-TRK-2026-004, published May 22, 2026, accessible via SASO’s Technical Notices Portal. Note: SASO has indicated that detailed implementation guidelines, including API endpoints and certificate enrollment procedures, will be released in Q3 2026 — content currently pending and subject to ongoing monitoring.