Terms | Description |
Original equipment manufacturers (OEMs) | OEMs are companies that manufacture or build components and vehicles, such as Mercedes Benz, Tatas, and BMW. They decide the vehicle type based on the use case, for example, a waste collection vehicle or a reefer truck, and thereby identify the required systems and ECUs. Subsequently, they outsource the production of components to tier 1 suppliers. OEMs are the ultimate authority for the fulfillment of requirements at the vehicle level. They must comply with R156 stipulated by the government. They collect the individual components, systems and sub-systems, ECUs, solenoid valves, and complete documentation related to compliance from the tier 1 supplier. The OEM integrates the systems and ECUs before performing an integration test at the vehicle level. |
Electronic Control Unit (ECU) | An ECU is an embedded device in which you can write software codes to control the mechanical and electrical functions of a vehicle. Each ECU can implement thousands of instructions to regulate the functions of a vehicle and therefore define the functionalities of the vehicle while ensuring that they are compliant with government regulations. One ECU can support single or multiple systems. |
Systems | Systems are physical units in a vehicle. A vehicle comprises a combination of systems that can achieve the mechanical functions required of a vehicle. The systems in a vehicle are coupled with ECUs which contain definitions of the functions. Therefore, systems and the linked ECUs can fulfill applicable regulatory requirements for systems, such as braking systems, fuel and ignition systems, and cooling systems. |
R156 | Rules stipulated by the government and configured in the backend in the SUMS tool to comply with R156 (Software Update Management System). These regulations are established by the United Nations Economic Commission of Europe (UNECE) and apply to the specified classes of vehicles: M: passenger vehiclesN: goods carrying vehiclesO: trailersR: motorcyclesS: specific purpose vehiclesT: agricultural and forestry tractors All the applicable regulations must be complied with for mechanical and pneumatic systems that are physically tested and approved by regulatory authorities. For each regulation, there is a grouping of software and multiple ECUs. |
Software Update Management System (SUMS) | A SaaS application that provides a comprehensive solution to document and maintain the results of R156 conformity tests. The SUMS tool enables authorities to periodically audit records and verify compliance with regulations. |
Tier 1 supplier | The immediate suppliers of OEMs in the automotive supply chain industry that manufacture major components used in vehicle production, such as engines, transmission systems, chassis, electronics, and other key components. They have the expertise and core competency in their field and enter into contractual agreements with the OEMs. Tier 1 suppliers are responsible for ensuring the correct functionality of the systems. They thus support the OEMs by fulfilling the regulations at the system level by coordinating with the Technical Service to facilitate testing of the components. Along with the components, they submit the compliance certificates and test documents to the OEMs. |
Technical service (TS) | An engineering expert test agency appointed and authorized by the government regulatory body to evaluate individual systems and vehicles for compliance. They audit the vehicle, test results, and supporting documentation before approving the vehicle type in compliance with the R156. They issue the compliance certificate to the tier 1 suppliers for system-level testing and the OEMs for vehicle-level testing. The TS thereby ensures optimal functionality, safety, and performance of a vehicle. |
R156 | The government stipulated regulations related to SUMS that extend to aspects such as safety, emissions, fuel efficiency, and manufacturing standards. The following are the R156 requirements for a given vehicle type that the OEM must submit to the regulatory authorities to obtain the compliance certificate: Information about all the systems Information about the ECU hardware and software version numbers Unique RXSWINLatest IVD (Integrity Validation Data) to validate ECUs in the system System parameter files The vehicle type defined must be modeled in the SaaS solution. Detailed documentation of the use case of the vehicle, the systems, and the ECUs required must be identified and documented in the SUMS tool. The Technical Service audit team must obtain access to the vehicle types and vehicle information database to view the details. |
Pre-homologation test/integrated test | Marks the preparation stage during which the OEM performs integration testing on the vehicle to ensure compliance with R156. |
Homologation test | Process of obtaining the compliance certificate from the type approval authority for a vehicle type before initiating mass production for systems and vehicles. The type approval authority performs detailed audits and tests before providing a compliance certificate to the OEM: a type approval number is assigned at this stage. |
RXSWIN | Unique identifier defined by the OEM to denote information about the type approval relevant software. The acronym can be expanded as follows: R: regulationX: regulation number, such as UNECE 48, UNECE 77, and EU 540 SWIN: software identification number, for example, R48-001 is the version for which type approval is required. |
Integrity validation data (IVD) | A 256-byte data that is autogenerated and pertains to information or metadata in the form of checksums to verify the integrity of the ECU. The IVD data plays a vital role in maintaining the reliability of systems as a new IVD is generated with each software update, especially in sensitive and safety-critical environments, such as automotive systems. |
System parameters | Configuration files within the vehicle systems in which settings or functions can be finetuned, enabled, or disabled, such as emission control, climate control, and electrical system parameters. |
Vehicle type | Vehicles can be categorized based on various characteristics, such as size, purpose, design, and intended use. They are designed to cater to specific needs and preferences of consumers. Some common vehicle types in the automotive industry include sedan, SUV, hatchback, coupe, convertible, truck, and van. The OEM decides the vehicle type to manufacture based on the use case. In the Software Update Management System (SUMS) tool, the vehicle type name, variant, and version constitute a vehicle type. |
End-of-line (EOL) | The final stage of the vehicle production process during which the EOL technician performs integration testing, inspection, and validation before they are released for shipment. |
Vehicle identification number (VIN) | A number assigned to uniquely identify each vehicle manufactured. To explain, for 1000 vehicles manufactured, 1000 VINs will be generated. All these VINs must be documented in the SUMS tool. Detailed vehicle information such as specifications, manufacturing location, and year of production can be referenced through the VIN. The VIN enables authorities, technicians, and consumers to identify and track vehicles throughout their lifecycle. |
Software update | Refers to the process of updating the software with the help of diagnostic tools during service, repair, or maintenance. |
Version | Vehicle type version number assigned after a software update is run on a vehicle type. A version can be created by tweaking a few parameters, for example, for minute-level controls, mileage parameters can be finetuned. A version within a variant will group the vehicles that have the following features in common: The technically permissible maximum laden massThe engine capacity in the case of an internal combustion engineThe maximum engine power output or the maximum continuous rated power (electric motor)The nature of the fuel (petrol, gas oil, LPG, bi-fuel or other)The maximum number of seating positionsDrive-by sound levelExhaust emission level (for example Euro 5, Euro 6 or other)Combined or weighted, combined CO2 emissionsElectric energy consumption (weighted, combined)Combined or weighted, combined fuel consumption |
Variant | One form of a specific base model manufactured according to the customer’s requirements by changing a specific component, system, or ECU of a vehicle type. A ‘variant’ within a type of vehicle will group the vehicles that have the following construction features in common: The number of lateral doors or the type of bodywork as defined The power plant has the following construction features:The type of energy supply (internal combustion engine, electric motor, or other)The working principle (positive ignition, compression ignition, or other)The number and arrangement of cylinders in the case of an internal combustion engine (L4, V6, or other)The number of axlesThe number and interconnection of powered axlesThe number of steered axlesThe stage of completion (for example, complete/incomplete)In the case of multi-stage built vehicles, the manufacturer and the type of the previous stage vehicle |
Identification process | The process of identifying the targets (vehicle types) and contents of the software update package—the purpose, ECUs, and regulations that are affected and must be included. |
Verification and validation | Verification and validation are keys to ensuring correct functionality, performance, safety standards of a vehicle, and compliance with applicable regulations. For more information, see Software Package Management > Verify and Validate Software Package. |
Release | Status of a software package that is uploaded in the SUMS app by the technician after verification and is ready for download |
Ready for release | After a software package for the selected vehicle type is validated and verified, it is ready for release for end-of-line production and by the workshop or service center. |
Type approval relevance | For a given release, if a regulation is selected for an ECU for which there is a software update, and if this software update contains a code that can cause an impact on the relevant software functionality, it becomes a regulation-relevant or type approval-relevant change. For more information, see Software Package Management. |
Version control | The changes made to software must be tracked, documented, and implemented to ensure reliability in the safety-critical automotive industry. Version control is a system devised to manage revisions or updates made to a software package (ECUs) over time. |
EOL technician | An End-of-Line technician works in the vehicle production process (for mass production) to build vehicles and ensures that the vehicle is fully assembled, tested, and ready for shipment. They validate the software packages, access, and assemble the approved software packages from the SUMS tool, and perform an integration test. |
Garage technician | A garage technician carries out software updates to a vehicle and plays a pivotal role to ensure that the process is undertaken safely and efficiently. Broadly, their role encompasses the following: Understanding the nature of the software update (bug fixing, new features, or improve performance)Vehicle inspectionDownloading and installing the software updateTesting and troubleshooting in case any issues ariseDocumenting detailed accounts of the software update for future referenceCommunicating with the customer |
JSON file | Represents metadata information about the latest software package installed on a vehicle. The JSON file provides basic information such as the vehicle type, variant, version numbers for each ECU, details about the latest software package installed, and components. |
Electronic control module (ECM) | Consists of information about the ECU, such as hardware and software numbers, version numbers, bootloader software numbers, and ECU IVD data. |
Installed package | The latest version of the software package installed within the vehicle’s system, which comprises the set of relevant ECUs. |
Latest package | The most recent software package available for download on the vehicle’s system. This could include updates made to the ECUs that control the mechanical functions of the vehicle, which could be related to bug fixing, new feature enhancements, or improved performance. |
Final packages | Final software packages are uploaded to the SUMS tool after verification and validation, which are subsequently downloaded by the EOL or garage technician while updating the software package residing in the ECU of a vehicle. |
OBD | Refers to On-Board Diagnostics, an automotive electronic system integrated with a vehicle that tracks vehicle and driver activities and provides diagnostic reports for servicing and repair. With the help of an OBD, a technician can access the sub-system information to monitor performance and analyze issues for repair. |
OBD dongle | A device that can be plugged into the OBD port, used by a garage technician to read the VIN and system information before updating the software residing in the ECU of a vehicle. |
OBD port | Port in which the OBD dongle is inserted by a garage technician to read the VIN and view and download data in real time. |
Diagnostic tools | Tools used by an EOL technician to validate the software packages and JSON files. |
Vehicle type model | As stipulated by R156, detailed documentation of the vehicle type, associated systems, ECUs, and regulations must be identified and documented in the SUMS tool. For example, a waste collection vehicle includes a transmission system, a braking system (pneumatic or hydraulic), and a garbage collection system. This information must be mapped in the SUMS tool: to attain certain functionalities for a vehicle type, identify the required systems and the embedded ECUs. Further, for each ECU, specify the software package version number. This process can be defined as vehicle type modeling and provides a completely linked solution to the use case in the SUMS tool. |
Software packages | A software package comprises a set of ECUs to support the mechanical functions of a vehicle. The software package post verification and validation must be uniquely identifiable and version-controlled before submitting it to the type approval authority. |
Software assembly | Involves integrating and configuring diverse software components (ECUs) to create a software package that supports the automotive systems and functions for a vehicle type. |
Software distribution | Distributing the released software package to the EOL production team for the production of vehicles and to the service centers or workshops (garage) after the vehicle is sold and on the road to facilitate software updates. |
Type approval number | A unique identifiable number assigned to a component or vehicle by the type approval authority after rigorous testing and evaluation that certifies that the component, system, or vehicle complies with the stipulated regulations. |