Updated: 28 June 2026 Reserve Your Windrose →
← Back to About Us
Type Approval · UN R156

Software Update Management System

Windrose holds UN Regulation No. 156 type approval, confirming that its Software Update Management System (SUMS) meets the requirements of WP.29 for managing vehicle software updates across OTA, diagnostic tool, USB, and EOL delivery methods throughout the vehicle fleet lifecycle.

Certificate No. CYPRUS·CERT·1021·00
Regulation UN R156 (WP.29)
System SUMS — WR-SUM-04
Issue Date 17 April 2025
Document Ref. R156体系证书20250417
Total Pages 36
01 Management System Scope
Governing Documents
  • Vehicle Software Update Management System Manual Tier 1 — overarching policy
  • Project Management / Process Management / Information Management / System Management Control Procedures Tier 2
  • Document & Records / Audit / Management Review / Corrective Improvement / Human Resources / Procurement Control Procedures Tier 2
  • Impact Assessment / Development & Testing / Release & Rollout / User Notification Management Measures Tier 3
  • Monitoring & Emergency Response / Process Safety / Network Security Management Measures Tier 3
  • Configuration Information / Compliance Information / Records Management Measures Tier 3
Key Processes
  • Internal audit cycle
  • Management review
  • Information sharing — shared procedure with CSMS (R155)
02 Software Update Project Management
Governing Documents
  • Vehicle Software Update Project Management Control Procedure
  • Impact Assessment Management Measures
  • Development and Testing Management Measures
  • Release and Rollout Management Measures
  • Monitoring and Emergency Response Management Measures
Key Processes
  • Requirements planning → Impact assessment (EE + After-sales + Technical Management joint review)
  • Development and testing (functional + link + network security)
  • Small-scale pilot rollout
  • Full fleet release
  • After-sales monitoring
  • OTA push process
  • Offline update process (diagnostic tool / USB / EOL)
03 Software Update Process Management
Governing Documents
  • Process Management Control Procedure
  • Process Safety Management Measures
  • Network Security Management Measures
Key Processes
  • Four update delivery modes: OTA / Diagnostic tool / USB / EOL
  • Target vehicle identification and export
  • User notification workflow
  • A/B partition rollback safety mechanism
  • OTA platform infrastructure security (username + password + SMS verification + HTTPS)
04 Software Update Information Management
Governing Documents
  • Configuration Information Management Measures
  • Compliance Information Management Measures
  • Records Management Measures
Key Processes
  • Software and hardware version coding and uniqueness management
  • RXSWIN coding and ledger management
  • Type approval ledger generation and maintenance
RXSWIN Format
WH13-R141-RN000-EXT000
Regulatory extension of software identification number — uniquely identifies each certified software version per type approval record.
05 Supplier Management
Governing Documents
  • Supplier Management Measures
Key Processes
  • Supplier qualification and onboarding — shared process with R155
  • SOR and CIA agreement execution
  • Delivery inspection and quality control
  • Ongoing supplier performance evaluation
  • Software package security coding requirements
  • Code scanning report submission
  • Encrypted transmission requirements
Key Output Forms
F-01Vehicle Software Update Impact Assessment Form
F-02Special Update Application Form
F-03RXSWIN / Software Identification Code Ledger
F-04Vehicle Type Approval Ledger
F-05Vehicle Software and Hardware Version Information Management Form