الهيئة السعودية للمواصفات والمقاييس والجودة 
Saudi Standards, Metrology and Quality Org (SASO)  
 
 
  
  
  
  
 
  
  
 
 
  
SASO/FDS / 33192 :2023  
المركبات- أنظمة النقل الذكية (ITS) - متطلبات أجهزة التيلماتيكس   
Motor Vehicles -Intelligent Transportation System  
(ITS)  - Telematics Requirements  
 
 
 
 
 
 
 
 
ICS:  43.020  
 
THIS DOCUMENT IS A DRAFT SASO STANDARD CIRCULATED FOR 
COMMENT. IT IS, THEREFORE SUBJECT TO CHANGE AND MAY 
NOT BE REFERRED TO AS A SASO STANDARD UNTIL APPROVED 
BY THE BOARD OF DIRECTORSASO STANDARD  SASO/FDS /33192: 2023 
 
2   
Motor Vehicles -Intellig ent Transportation System  
(ITS)  - Telematics Requirements  
 
Foreword  
 
Saudi Standards, Metrology and Quality Organization (SASO) has  prepared the 
Saudi Standard SASO /FDS/33192 :2023 Motor "  vehicles - Intelligent 
Transportation Systems (ITS) - Requirements fo r Public Transport Vehicle 
Operation" based on relevant ADMO, International and National  foreign 
Standards and references.  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 SASO STANDARD  SASO/FDS /33192: 2023 
 
3   
CONTENTS  
1.0 SCOPE ………………………………………………………………………… …4 
2.0 REFERENCES …………………… .………… .……… .……………… ………… 4 
3.0 DEFINITIONS  …………………………………… ……….…………………….. 5 
4.0 APPLICATION FOR TYPE APPROVAL OF VEHICLE TELEMATICS 
SYSTEM  …………… ..………………………………………… ...……………… 7 
5.0 ITS FUNCTIONS AND REQUIREMENTS - VEHICLE TELEMATICS 
SYSTEM  ……………………… …………………………… …...……………….. 8 
6.0 VEHICLE TELEMATICS SYSTEM incl. Vehicle Location Tracki ng (VLT), 
Emergency Button, On Board Weighing EQUIPMENT (OBW) and Configuration 
of Device Parameters Over the Air (OTA) ………………… ..…………………… 8 
7.0 COMMUNICATION  PROTOCOL ………………………… ………… ..………. 15 
8.0 CONSTRUCTION AND INSTALLATION ……………… ….………………… 23 
9.0 FUNCTIONAL, PERFORMANCE, D URABILITY, ENVIRONMENTAL AND 
PROTOCOL TESTS  …………………………………………………………….24  
10.0 DEVICE TO BACKEND COMMUNICATION MECHANISM ……… .……… 42 
11.0 CODE OF PRACTICE for Implementation of Vehicle Telematics device and 
Command and Control Centres ……………………… ………………………… 44 
ANNEX -A Informa tion to be Submitted for Type Approval…… ...…………............ 56 
ANNEX -B Criteria for Extension of Type Approval ...………………………… ........ 58 
Table 5 A ……………………………………………………………………………… 8 
Table 6 B………… .…………………………………… .……………………………. 14 
Table 7A …………………………………………………… .….…………………… .16 
Table 7B ……………………………………………………… .…… .……………… .18 
Table 7C ………………………………………………………………… ..…………. 20 
Table 9A …………………………………………………………………… ..………. 25 
Table 9B ………………………………………………………………… .………….  29 
Table 9C ……………………………………………………………… ..……………. 33 
Table 9D ……………………………………………………………………… .……..99 
 
 
 
 
 
 SASO STANDARD  SASO/FDS /33192: 2023 
 
4  1.0 SCOPE  
 
This standard applies to both individual components as well as system environment intended 
to be used in Public transport vehicles, Goods transport vehicles and vehicles used for general 
purpose by the government entities in their fleet.   
 
Functionalities covered under this Intelligent Transportation Systems (ITS) standard, 
necessary for installing the device (standard of the device itself) as standalone device are:  
a. Vehicle Location Tracking  
b. Monitor traffic violations and traffic enforce ment  
c. Emergency Request Button to indicate safety/panic situation caused by human or 
natural disaster or vehicle accident  
d. On board mass monitoring system (motor vehicles in categories M2,  M3 and N2 and 
N3, see chapter 6 .0.3) 
 
Note: The governmental vehicles  used for Members of the Council of Ministers (the Cabinet), Ministry of 
Defense and relating directly to National security and the Saudi Defense Forces, Officers of special ranks and 
Diplomats shall be excluded with the requirement of vehicle location tra cking.  
 
2.0 REFERENCES:  
2.1 Directive 2010/40/EU,  “on the framework for the deployment of Intelligent Transport 
Systems in the field of road transport and for interfaces with other modes of transport” (the 
“ITS Directive”)  
2.2 ISO 11898 -1:2003  Road vehicles -  Controller  area network  (CAN)  
2.3 ISO 26262:2018  Road vehicles - Functional safety  
2.4 ISO/TR 12859:2009 – Intelligent transport systems - System Architecture -Privacy  aspects 
in ITS standards and  systems  
2.5 ISO 17185 -1:2014  - Intelligent transport systems - Public transport user  information  — 
Part 1: Standards  framework  for public  information  systems  
2.6 ISO 15638 -5:2013  Intelligent transport systems – Framework for collaborative 
Telematics Applications for Regulated commercial freight Vehicles (TARV) – Part 5 : Generic 
vehicle information  
2.7 ISO 15638 -15:2014  Intelligent transport systems - Framework for cooperative telematics 
applications for regulated vehicles (TARV) – Part 15: Vehicle location monitoring  
2.8 Trans model Standard (CEN/TC 278 WG3/SG4, Referenc e Entity - Relationship Data 
Model for Public Transport) - European reference data model for Public Transport operations 
developed within several European Projects - EN 12896:2006  
2.9 Specification for Entity -Relationship for describing the main fixed objec ts in Public 
transport CEN/TC 278, 2008 - EN 28701:2012  SASO STANDARD  SASO/FDS /33192: 2023 
 
5  2.10 SAE  J 1939  Recommended  Practice  for a Serial  Control  and Communications  Vehicle  
Network.  
2.11 SAE  USCAR  18 / USCAR 18-3 - FAKRA  SMB  RF CONNECTOR  SUPPLEMENT  
2.12 APTA  TCIP  - American  Public  Transpo rtation  Association  (APTA)  Standard  for 
Transit  Communications  Interface Profiles  (TCIP)  
2.13 EBSF  - European  Bus System  of the Future  
2.14 Bus-FMS -Standard  
2.15 National ITS  Architecture  - U.S. Department  of Transportation  
2.16 RTIG (Real Time Information  Group Ltd) - Digital Air Interface Protocol  
2.17 SIRI (Service Interface for Real Time Information) European Technical Specification 
(TS) - CEN/TS 15531  
2.18 NeTEx -Network Exchange European Technical Specification (TS) CEN/TS 16614  
2.19 NaPTAN (National P ublic Transport Access Node)  
2.20 NMEA -0183 : The NMEA 0183 standard defines an electrical interface and data  protocol  
for communications  between marine  instrumentation.  
 
3.0 DEFINITIONS : 
 
For the purpose  of this standard,  definitions  are given  below:  
3.1 ‘Acqu isition sensitivity ’ refers to the minimum signal level at which the  device is able to 
successfully perform a cold start TTFF. The acquisition  sensitivity  test is a  simulated signal 
test. 
3.2 ‘Assisted GPS (A -GPS) ’ is a system allowing satellite receivers to obtain  information 
from communication network resources to assist in acquiring  satellite location. A -GPS system 
is especially useful when the receiver is in  a location  where it  is difficult  for the satellite 
signals  to penetrate.  In addition to providin g better coverage, A -GPS also improves the start -
up time,  which  is the time required  by the  satellites  and the receivers  to establish  a reliable  
connection.  
3.3 ‘Circular Error Probability (CEP )’ is defined as the radius of a circle  centered  on the 
true value that contains  50% of the actual  GPS measurements. So a receiver with 5 meter CEP 
accuracy will be within 5  meter of the true measurement 50% of the time. The other 50% of 
the time  the measurement will be in  error  by more  than one meter.  
3.4 ‘Dilution o f Precision (DOP) ’ is the degree of proximity of the location  data to  their 
mean  value.  The relative position  of satellites  affects  the accuracy  of location  calculation  by 
the locating  module.  Location  coordinates computed when the satellites are clustered  together 
suffer from  dilution of precision (DOP), a factor that multiplies the associated errors.  The 
DOP for an ideal satellites constellation arrangement equals close to 1,  which does not 
magnify  the underlying  errors.  SASO STANDARD  SASO/FDS /33192: 2023 
 
6   
3.5 ‘Distance  Root  Mean  Square  (DRMS  also called  RMS,  1 Sigma) ’ 
This is computed as square root of the average of the squared horizontal  position  errors  with 
65% probability.  The position  expressed  has the probability of being within a circle with 
radius with 65% probability. A  locating m odule with 6 metre DRMS accuracy would be 
within 6 meters of  its actual position 65%  of the  time.  
3.6 ‘Emergency Button ’ A button provided in vehicle for passengers or crew  members to 
send specialized data packet /SMS to Centralized regulatory  server  to indicate  safety/panic  
situation  caused  by human  or natural  disaster  or vehicle  accident, etc.  
3.7 ‘Global Navigation Satellite System (GNSS) ’ refers to a space -based radio navigation 
system and comprises several networks of satellites that transmit radio sig nals containing time 
and distance data that can be picked up by a receiver, allowing the user to identify the location 
of its receiver anywhere around the globe.  
3.8 ‘Sensitivity ’ refers to the minimum signal strength level at which locating  module can 
successfully perform a location fix. A GNSS locating module  has two different sensitivity 
levels – acquisition sensitivity and tracking  sensitivity.  
3.9 ‘Time to First Fix (TTFF) ’ describes the time required for a tracking  device to acquire 
adequate satellite  signals and related data (almanac and  ephemeris  data) to compute location.  
3.10 ‘Tracking Sensitivity ’ refers to the minimum signal level at which the  device is able to 
successfully maintain the location fix. The acquisition  sensitivity  test is a  simulate d signal 
test. 
3.11 ‘Vehicle Location Tracking (VLT) ’ device uses satellite based location  technology to 
determine and record the precise location of a vehicle at  regular intervals. The location data so 
determined can be stored within the  device, and/or ca n be transmitted to the Backend Control 
Centre using a  wireless  communication  modem built in  the device.  
3.12 ‘Vehicle telematics system ’ includes vehicle telematics devices, which are tracking 
devices installed into vehicles that facilitate the transmissi on and storage of telemetry data via 
wireless networks and the vehicle’s own onboard modem and diagnostics (ODBII). Telematic 
devices are monitoring locations, movements, status and safety behaviour of a vehicle or fleet 
of vehicles such as speeding, drivi ng direction, ignition status, driving violations, past trips, 
and more.  
3.13 ‘SIM/UICC ’ refers to Subscriber Identification Module (SIM)/ Universal integrated 
circuit card (UICC) as per GSMA guidelines / DoT (TEC) Guidelines. Embedded SIM/UICC 
is a PCB so ldered SIM/UICC/eUICC.  
3.14 ‘Cellular Technology ’ such as GPRS/UMTS/HSPA/LTE etc.  
3.15 ‘maximum authorized weight ’ shall mean the maximum weight for use of a laden 
vehicle in traffic  
3.16 ‘on-board weighing equipment ’ (‘OBW ’) means the equipment on -board a vehicle that 
is able to determine the total weight or the axle weight;  SASO STANDARD  SASO/FDS /33192: 2023 
 
7  3.17 ‘total weight ’ means the total weight of a motor vehicle and, in case of a vehicle 
combination, of the vehicle combination as determined by the OBW, in kilogram;  
3.18 ‘axle weig ht’ or ‘axle load ’ means the weight of a laden axle or group of axles as 
determined by the OBW, in kilogram;  
3.19 ‘calculated weight ’ or ‘weight value ’ means either the total weight or the axle weight, 
in kilogram;  
3.20 ‘motor vehicle unit ’ (‘MVU ’) means the part of the OBW placed in the motor vehicle, 
excluding the sensors, able to collect, store, process data and to calculate a weight value 
resulting from those data;  
3.21 ‘trailer unit ’ (‘TU’) means the part of the OBW placed in a trailer or semi -traile r, 
excluding the sensors, able to collect, store, process data from the trailer or semi -trailer 
equipment and to calculate axle weight values resulting from those data;  
3.22 ‘weight data ’ means the raw data transmitted between elements of the OBW that must  
be processed in order to obtain the calculated weight;  
3.23 ‘sensor ’ means the element of the OBW that is able to generate weight data by 
measuring specific physical parameters, being those data used by either the MVU or the TU 
for further processing;  
 
4.0 APPLICATION  FOR  TYPE  APPROVAL OF VEHICLE TELEMATICS SYSTEM  
 
4.1 The application for device level approval shall be accompanied by information on the 
system specification as mentioned in Annexure A.  
4.2 Type approval shall involve following steps:  
4.3 Device Approval: Approval provided at device level for compliance to this standard. 
These approved devices can be fitted / retro -fitted by device or vehicle manufacturer/ dealer/ 
permit holder/system integrator in any vehicle model provided it shall meet installa tion 
requireme nts as mentioned in Clause No. 8  of this standard.  
 
4.4 Modifications and Extension of Approval  
 
4.4.1.1 Every modification pertaining to the information, even if the changes are not technical 
in nature decl ared in accordance with clause 4.2 , shall be intimated by the device 
manufacturer to the approval authority.  
 4.4.1.2 If the changes are in parameters not related to the provisions, no further action need 
be taken.  
4.4.1.3 If the changes are in parameters related to the provisions, the appr oval authority, 
which has issued the certificate of compliance, may then consider, based on the justification 
provided by the device manufacturer and further reviewed by the approval authority, whether,  SASO STANDARD  SASO/FDS /33192: 2023 
 
8  4.4.1.4 The model with the changed specifications sti ll complies with provisions; Or,  
4.4.1.5 Any further verification is required to establish compliance.  
4.4.1.6 In case of 4.4.1.2 , tests for only those parameters which are affected by the 
modifications need be carried out based on criteria for extension o f type approval as per 
Annexure B.  
4.4.1.7 In case of fulfilment of criterion of clause 4.4.1.1 or after results of further verification 
as per clause 4.4.1.2  are satisfactory, the approval of compliance shall be extended for the 
changes carried out.  
5.0 ITS FUNCTIONS AND REQUIREMENTS - VEHICLE TELEMATICS SYSTEM  
 
5.0.1 The list of ITS functions envisaged from this device type is set out below in 
Table 5A.. 
Table 5A. 
Function  Sub Functions  
 
Safety  and Security  Vehicle  Location  Tracking  (VLT)  
Emergency  Buttons 
Traffic enforcement  Over Speeding w.r.t maps data  
On board weighing system (OBW)  
 
5.0.2 The above functions and their requirements shall be met by only single  device  
that can be interfaced  by in-built telematics unit.  The communications to Backend 
Control Server (Government authorized  server) shall be done by device as per the 
protocol and functionalities  defined  below.  
6.0 Vehicle Telematics System incl. Vehicle Location Tracking (VLT), Emergency 
Button, On Board Weighing EQUIPMENT (OBW) and Configurat ion of Device  
Parameters  Over  the Air (OTA)  
 
6.0.1 General Provisions and Functional Requirements -Vehicle telematics system 
Vehicle location tracking (VLT)  
6.0.1.1 Device shall be capable of obtaining position information using Global  Navigation 
Satellite  System (GNSS). GNSS receiver specifications are  as follows:  
a. Device  shall  have  a position  accuracy  of minimum  2.5 m CEP or  6 m 2DRMS.  
b. Device shall have an acquisition sensitivity of minimum ( -) 148  dBm.  
c. Device shall have an acquisition sensitivity of mini mum ( -) 145 dBm with  GNSS  
d. Device  shall  have  an internal  antenna;  however  if in case of aftermarket OEM 
approved kits if  the fitment location prevents the internal antenna from functioning,  
then external antenna  shall be  provided.  SASO STANDARD  SASO/FDS /33192: 2023 
 
9  6.0.1.2 Device shall suppo rt standard minimum I/Os as mentioned: 4 Digital, 2 Analogue 
Input and 1 Serial Communication (e.g. RS232) for interfacing  external systems (E.g. Digital 
input for Emergency request button interfacing).  
6.0.1.3 Device shall be capable of transmitting data  to Backend Control Server (Government 
authorized server) via Wide Area (Mobile) Communications network (Cellular) as per 
Com munication Protocol in Section 7 . 
6.0.1.4 Device shall be capable of transmitting Position, Velocity and Time (PVT data) along 
with heading (direction of travel) and for purpose of other application as mentioned in this 
regulation to a Backend Control Server (Government authorized server) at configurable 
frequency as per Com munication Protocol of Section 7 . 
6.0.1.5 The fixed frequency  shall be user configurable. Highest data transmission rate shall be 
5 sec during vehicle operation and not less than 10 minutes in sleep/IGN OFF) as per the 
protocol defined in Communication Protocol of Section 7. 
6.0.1.6 Device shall be capable of transm itting data to minimum 2 different IP addresses (1 IP 
address for regulatory purpose (PVT data) and 1 IP address for Emergency response system 
other than the IP’s required for Operational purpose.  
6.0.1.7 Device shall have an internal back -up battery to su pport 4 hours of normal operations 
(to be tested for positional record transmission at a frequency of 60 sec).  
6.0.1.8 Device shall be capable of transmitting alerts to the Backend Control Server 
(Government authorized server) directly. The applicable list  of alerts is given in Section 7.2.1 
(Alert ID 3 to 12) of Section 7. 
6.0.1.9 Device shall support over the air software and configuration update.  
6.0.1.10 Device shall support basic standard configuration (Mobile communications network 
settings, Backend C ontrol Server (Government authorized server) details, data frequencies, 
alert thresholds etc.) as per configuration specification defined in Section 7. 
6.0.1.11 Device shall support store and forward mechanism for all type of data (periodic data 
and alerts ) meant for backend transmission. The system shall store data in internal memory 
during communication network un - availability and transmit the data when the connection 
resumes in last in first out (LIFO) manner. The live data shall be given higher priorit y for 
transmission than back log (stored data) at any point in time.  
6.0.1.12 The Device shall have a unique identifier for identifying the VLT device and data. 
The unique ID shall be stored in a read only memory area so that it cannot be altered or 
overwr itten by any person. The unique identifier is IMEI (International Mobile Station 
Equipment Identity) Number.  
6.0.1.13 Device shall store/write the registration number of the vehicle in the internal non - 
volatile memory.  
6.0.1.14 Device shall have an Embedd ed SIM/UICC.  
6.0.1.15 Device shall be designed to operate between 12V DC and 24V DC.  
6.0.1.16 Device shall have a sleep mode current ≤ 50 mA.  SASO STANDARD  SASO/FDS /33192: 2023 
 
10  6.0.1.17 Device shall support any operational GNSS system with 12 (minimum) acquisition 
channels.  
6.0.1.18 The Device shall support:  
 Location  on Cellular GPRS/SMS  
 Non-volatile  memory  to store  min 40,000  positional log  
 Configurable  backup  SMS  facility  in case  of Cellular failure  
 Capability  to send serving  and adjacent  cell ID as well as network  measurement  
report (NMR)  
6.0.1.19 The VLT d evice  shall  have:  
 The capability  of Hot start < 10s  
 The capability  of Warm  start <  60s 
 The capability  of Cold start < 120 s  
6.0.1.20 Device  shall support  Outputs as per  NMEA 0183  
6.0.1.21 The Device Cellular  module  shall  have:  
 Multi  slot Cellular  with In - built Quad -band  Cellular module/Modem  
 Cellular  class  10 or  above  
 Support  Embedded  SIM/UICC  to cater  to the operational  requirement such as 
vibration, temperature and humidity and provide  long life span with at least 10  years 
life and more than 1 million  read/write cycles  
 Cellular  module &  Embedded SIM/UICC shall support  
o SMS,  Data (Cellular,  TCP/IP)  and 
o Support  multiple  network  OTA  switching  (on-demand/automatic)  capabilities.  
6.0.1.22 Device  shall  be dust,  temperature,  vibration,  water  splash  resistant, IP 65 rated  or 
bette r, tamper proof as per Section 9 . 
6.0.1.23 Device shall be manufactured by manufacturer whose quality management system 
has been certified for compliance to ISO / TS 16949 or ISO 9001 or any equivalent 
National or International standard.  
6.0.1.24 Device shall support A -GPS (Assisted GPS).  
6.0.1.25 Device shall  have provision of secured data transmission to the Backend  Control 
Centre from the devices through secured channel (e.g. secured  dedicated  APN).  
6.0.1.26 Device  shall  have  3 axis accelerometer  and 3 axis gyroscope  for getting the  alerts 
on harsh  breaking , harsh acceleration,  and rash turning.  
6.0.2 Functional Requirement for Emergency System  
 
6.0.2.1 Passengers or in -vehicle  crew  present  in the vehicle shall  be able to make an 
emergency  request  by pressing  the emergency  button provided.  
6.0.2.2 The emergenc y request  function  shall  not exist  as standalone.  The function shall be 
part of Vehicle Location Tracking (VLT) system. An  alert shall be sent to the Backend SASO STANDARD  SASO/FDS /33192: 2023 
 
11  Control Server (Government authorized  server) when emergency request is raised. De -
activation shal l always be  from  authorized  government  server  who receives  alert message  i.e. 
NERS  system as mentioned in Sub -section 7.2.2 . 
6.0.2.3 The Emergency Buttons will be such that disconnection between switch and controller 
should be detected through controller l ogic or ‘Normally Closed’ (NC) Type Switch. For 
Emergency button, there shall be indication of its working status visible for passengers in 
Ignition ON Condition. The form factor of Emergency Buttons will be such that the button is 
easy to press in the cas e of an emergency, and simultaneously also minimizes the possibility 
of accidental or unintended press thereby causing a false alert.  
6.0.2.4 On pressing of Emergency button, the system implementing VLT function shall send 
emergency Alert (Alert ID 10 as m entioned in Sub - section 7.2.1 of Communication Protocol 
Section 7) to the Backend Control Server (Government authorized server) as per the 
Communication Protocol mentioned in Section 7. In the absence of Cellular network, the alert 
shall be sent as SMS me ssage along with vehicle location data to configured control center 
number. The SMS shall consist of parameters as given in Sub -section 7.2.2. 
6.0.2.5 In absence of both Cellular and GSM networks and on pressing of Emergency Button, 
the system implementing  VLT function shall store the emergency Alert (Alert ID 10 as 
mentioned in Sub -section 7.2.1 of Communication Protocol Section 7). Once the Cellular or 
GSM is available, this alert information shall be sent on high priority to the configured IP 
addresses a s per the communication protocol mentioned in Section 7 or as SMS message 
along with vehicle location data to configured control center number. The SMS shall consist 
of parameters as given in Sub -section 7.2.2. 
6.0.3 Functional Requirement for On -Board Wei ghing Equipment (‘OBW’)  
6.0.3.1 Following vehicles are in the scope of weight estimation:  
a. rigid lorries with an axle configuration of 4×2 and a technically permissible maximum 
laden mass exceeding 16 tonnes;  
b. rigid lorries with an axle configuration of 6×2;  
c. tractors with an axle configuration of 4x2 and a technically permissible maximum 
laden mass exceeding 16 tonnes; and  
d. tractors with an axle configuration of 6x2  
 
6.0.3.2 In addition, the follow vehicles specifications are exempted:  
a. Vehicles with Sequential  Manual Transmission (SMT)  
b. Vehicles with torque converters automatic transmission  
c. Vehicles approved for gaseous fuels, dual -fuel or with PI -engines  
d. Vehicles with CI -engines approved for B100  
e. Vehicles with leaf suspension on all axels  
f. Electrified vehicles  
6.0.3.3 The on -board weighing equipment shall be accurate and reliable, fully interoperable 
and compatible with all vehicle types.  SASO STANDARD  SASO/FDS /33192: 2023 
 
12  6.0.3.4 In order to ensure compatibility with all vehicle types, on -board systems of motor 
vehicles shall have the capability  to receive and process any data coming from any type of 
trailer or semi -trailer attached to the motor vehicle  
6.0.3.5 Competent authorities may exempt from the obligation requiring the instalment of on -
board weighing equipment in vehicles or vehicle combi nations the design or type of load of 
which makes it impossible to exceed the maximum authorised weight. Those exemptions shall 
not be based on the technically permissible maximum laden mass of a vehicle indicated by the 
manufacturer. The vehicles or vehic le combinations which benefit from an exemption may 
still be subject to control by the competent authorities of the maximum authorised weight.  
6.0.3.6 The following types of OBW systems are included in the scope of this Regulation:  
a. dynamic system: OBW sys tem that determines the weight by collecting and 
processing information from parameters that are captured while the vehicle is in 
motion, such as accelerations, traction or braking forces, and which do not take place 
when the vehicle is standing still;  
b. static system: OBW system that determines the weight with information obtained from 
parameters that are captured while the vehicle is standing still, such as the pressure in 
an air bellow  
6.0.3.7 The OBW shall comprise the following elements:  
a. a motor vehicl e unit (‘MVU’) placed in the motor vehicle;  
b. optionally, a TU in the trailer or semi -trailer;  
c. sensors;  
6.0.3.8 MVU and Trailer Unit may each consist of a single processing unit or be split into 
different units.  
6.0.3.9 The OBW shall calculate the total we ight and, optionally, the axle weight.  
6.0.3.10 Motor vehicle unit (‘MVU’)  
              The MVU shall:  
a. receive the axle load from the TU, if the latter is present;  
b. collect weight data from the sensors in the motor vehicle;  
c. process the available informat ion and calculate the corresponding weight values;  
6.0.3.11 Trailer unit (‘TU’)  
               Where present, the TU shall:  
a. collect weight data from the sensors in the trailer or semi -trailer, process the available 
information and calculate the axle wei ghts resulting from those data;  
b. transfer the axle weight values to the motor vehicle.  
6.0.3.12 Calculation of weight  
a. For dynamic systems, a first weight value shall be calculated at the latest 15 minutes 
after the vehicle starts to move forward and shall  be recalculated, every 10 minutes 
henceforth or faster.  SASO STANDARD  SASO/FDS /33192: 2023 
 
13  b. For static systems, weight values shall be calculated every minute when ignition is on 
and the vehicle is standing still.  
c. The resolution of the calculated weight shall be 100 kg or better.  
6.0.3.13  Accuracy  
a. The accuracy of the calculated weight shall be ± 10 % or better when the vehicle is 
loaded at greater than 90 % of its maximum authorised weight.  
6.0.3.14 The driver shall be informed by a display of, at least, the total weight.  
6.0.3.15 The weight information shall  not exist  as standalone.  The information shall be part of 
the information sent by the Vehicle telematics system to the Backend Control Server 
(Government authorized server) as per the Communication Protocol mentioned in Section 7. 
6.0.3.16 Exchange of information between the motor vehicle and the trailers or semi -
trailers of a vehicle combination  
a. Each trailer or semi -trailer shall make available to the motor vehicle the weight values 
calculated by the former in accordance with below re quirements.  
b. Each trailer or semi -trailer shall be assigned a position within the vehicle combination 
in the frame of a dynamic address assignment as set out in ISO 11992 -2:2014.  
c. After the address assignment phase is carried out, the TU of each trailer or semi -trailer 
shall transfer to the MVU the axle load sum or the axle load in accordance with the 
description provided in points 6.5.4.7 and 6.5.5.42 of ISO 11992 -2:2014.  
d. The messages on axle load sum or axle load shall follow the specifications set out in  
ISO 11992 -2:2014 for the message types EBS22 and RGE22.  
e. The format, routing and general parameter ranges of the messages shall be in 
accordance with points 6.1, 6.3 and 6.4 of ISO 11992 -2:2014.  
 
 Note: Different specifications may be used, provided that the OBW equipment                        
in the motor vehicle and in the trailers or semi -trailers are compatible with them.  
6.0.4 Configuration  of Device  Parameters  Over  the Air (OTA)  
The device shall support at least the below parameters to be configurab le over the air (through 
SMS and Cellular). The updation/configuration shall be allowed  only over an ‘authenticated’  
channel:  
1. Setting/  Change  of the Primary  or Secondary  IP and  port number  
2. Setting/ Change  of the  APN  
3. Set configuration  parameter  like sleep  time, overspeed  limit,  harsh  braking,  harsh  
acceleration,  rash turning  threshold  limits , etc. 
4. Emergency  control  SMS Centre  Number(s)  
5. Configuring  the vehicle  registration  number  
6. Configuring  the frequency  of data transmission  in normal  / Ignition    state  / OFF 
state sleep mode/ Emergency  state, etc.  
7. Configuring  the time duration for Emergency  state 
8. Capability to reset the device  
9. Command to get the IMEI of the device Configurable commands must involve the 
following features:  SASO STANDARD  SASO/FDS /33192: 2023 
 
14  9.1 SET: For setting the parameters.  
9.2 GET: For enquiring regarding the parameters such as mobile number, GSM 
strength, vehicle number and other important parameters.  
9.3 CLR: For clearing certain commands, alarms, alerts etc. except emergency 
alert 
After  each SET,  GET,  CLR  command  the device  should  send alert to Backend Control 
Centre, as mentioned in Section 7 Alert 12, giving the  details  of Mode,  mobile  no/ IP of 
control  center  sending commands.  
6.0.5 Tracking  Device  Health  Monitoring  Parameters  
The device shall send status of health parameters at configurable interval  and this threshold 
value shall also be configurable over the air. It shall be possible for health parameters to be 
fetched on demand via command as  set out below in Table 6B. 
 
Table 6B 
Sl. No. Field  Description  
1 Start  Character  $ 
2 Header  The header of  the packet/ identifier  
3 Vendor  ID Vendor  identification  header  
4 Firmware  Version  Version  details  of the Firmware  used in 
EX.1.0.0  
5 IMEI  Identified  of the sending  unit. 15 digit 
standard unique  IMEI  no. 
6 Battery  percentage  Indicates  the internal  battery  charge  
percentage  
7 Low battery  threshold value  Indicates  value  on which  low 
battery  alert generated  in percentage  
8 Memory  percentage  Indicates  flash  memory  percentage  used 
9 Data  update  rate when  
ignition  ON Indicates  Packet  frequency  on 
ignition  ON 
10 Data  update  rate when  
ignition  OFF Indicates  Packet  frequency  on 
ignition  OFF 
11 Digital  I/o status  Inputs  connected  to the device.  
12 Analog  I/o status  Analog  input  status  
13 End character  * 
 SASO STANDARD  SASO/FDS /33192: 2023 
 
15  6.0.6 SMS  Fall Back  
In case o f emergency state, (i.e. on pressing of Alert button), the device will shift to the SMS 
mode in case Cellular connectivity is not available. In such case, the device will send the 
Alert message and tracking data through SMS mode. Since SMS has the limitati on of sending 
only 160 characters, so the tracking data to be sent in one SMS will have fields - IMEI, 
Latitude, Direction, Longitude, Direction, location fix, speed, Cell ID, LAC (Location Area 
Code), Date and Time as per emergency alert . The details is provided in Sub -section 7.2.2. 
 
7.0 COMMUNICATION  PROTOCOL  
7.1 Data  Frame  Format  
Table below (Table 7A) contains the listing of fields that the vehicle telematics sdevices 
would be required to send to the Backend Control Centre. The first 3 fields (Start chara cter, 
Header for VLT with Emergency Buttons and Vendor ID, who has supplied the device) must 
be fixed in position as well as format (Header part of frame). Rest all other fields are required 
to be present in the location data sent by the devices to the bac kend, but can be in any 
sequence and with any separator between fields. The data value can be either in American 
Standard Code for Information Interchange (ASCII) or in HEX format. Device must transmit 
the Login message whenever it establishes (re -establis hes after disconnection) its connectivity 
with Server with the specified fields. Login Message will carry following information:  
$DeviceName  –Vehicle  number (vehicle registration number)  on which  the device  is 
installed.  
$IMEI  –15 Digit  IMEI  number.  
$Firmw are – Version of  the firmware  used in the  hardware.  
$Protocol  -Version  of the frame  format  protocol.  
$LastValidLocation  – Last location  info saved  at the device.  
 
Table 7A 
Field  Description  Sample  Data  
Start  Character  $ $ 
Header  The header  of the  
packet / identifier   
Vendor  ID Vendor  identification  
header   
Firmware  Version  Version  details  of the 
Firmware  used in 
EX.1.0.0  1.0.0  
Packet  Type  Specify  the packet  type SASO STANDARD  SASO/FDS /33192: 2023 
 
16   NR = Normal  Depending  upon  the 
context,  every  frame  from  
tracking  device  must carry 
a qualification  code. This 
helps  to determine  the 
state in which vehicle is  at 
that time.   EA = Emergency Alert  
 TA =  Tamper Alert   
 HP = Health  Packet  
 IN = Ignition  On 
 IF = Ignition Off  
 BD = Vehicle Battery  
Disconnect  
 BR = Vehicle  Battery  
 Reconnect  
BL = Internal  Battery  
Low  
Packet  Status  L = Live  or H =  History  L 
IMEI  Identified of the sending  
unit. 15 digit standard  
unique  IMEI  no. 123456789012345  
Vehicle  Reg. No Mapped vehicle  
registration  number  3690JBA  
GPS Fix 1 = GPS fix OR 0 = GPS 
Invalid  1 
Date  Date  value  as per GPS 
date time per GPS date 
time (DDMMYYYY)  22072022  
Time  Time value as per GPS  
date time in UTC format  
(hhmmss)  050656  
Latitude  Latitude value in  decimal 
degrees (not  less than 6  
places)  28.758963  
Latitude  Dir Latitud e Direction.  
Example  
N= North,  S= South  N 
Longitude  Longitude value in  
decimal degrees (not  less 
than 6  places)  77.6277844  SASO STANDARD  SASO/FDS /33192: 2023 
 
17  Longitude  Dir Longitude  Direction.  
E= East,  W= West  W 
Speed  Speed of Vehicle as  
calculated by GPS  
module in VLT. (in  
km/hrs.)  (Upto One  
Decimal  Value)  25.1 
Heading  Course over ground in  
degrees  310.56  
Total Weight  Weight in Kg. should 
represent the total weight 
of vehicle + load  6500  
No of Satellites  Number of satellites  
available  for fix 8 
Altitude  Altitude of the device in  
mete rs 183.5  
PDOP  Positional dilution of  
precision   
HDOP  Horizontal dilution of  
precision   
Network  Operator  Name  of Network    
Name  Operator   
Ignition  1= Ignition On , 0 =  
Ignition  Off 1 
Main  Power  Status  0= Vehicle Battery  
disconnected  
1= Vehicle Battery  
reconnected  1 
Main  Input  Voltage  Indicator showing source  
voltage  in Volts. (Upto  
One Decimal  Value)  12.5 
Internal Battery  Voltage  Indicator  for level  of 
battery charge  remaining.  
(Upto  One Decimal  
Value)  4.2 
Emergency  Status  1= On , 0  = Off  0 SASO STANDARD  SASO/FDS /33192: 2023 
 
18  Tamper Alert   C = Cover  Closed,  O = 
Cover  Open  C 
GSM  Signal  Strength  Value  Ranging  from  0 – 
31 25 
MCC  Mobile  Country  Code  404 
MNC  Mobile  Network  Code  10 
LAC  Location  Area  Code  00D6  
Cell ID GSM  Cell ID CFBD  
NMR (Network  
Measurement  Report)  
Neighbouring  Cell ID Neighbouring  4 cell ID 
along with their LAC &  
signal  strength   
Digital  Input  Status  4 external  digital  input  
status (Status of Input 1  
to Input  3 (0=Off;  
1=On))  0001  
Digital  Output  Status  2 external  digital  output  
status (0=Off;  1=On)  01 
Frame  Number  Sequence  Number  of the 
messages (000001  to 
999999)  000005  
Checksum  Ensures No error in 
transmission (optimal)  16 
End Character  Indicated  End of the  
frame  * 
 
7.2 Messages  & Alerts  from  Vehicle Telematics Device  
 
7.2.1 Table below (Table 7B) contains th e listing of alerts that need to come  from  the 
telematics  device.  These  alerts  are applicable  for both live packets  as well as the 
history  packets.  
Table 7B 
Alert  ID Message  & Alerts  Remarks  
1. Location  Update  Default  message  coming  from   each  
device  SASO STANDARD  SASO/FDS /33192: 2023 
 
19  2. Location  Update  (history)  Would be sent, if Cellular is not 
available at the time of sending the 
message in protocol format Zero, 
BLANK, NIL, etc.  
3. Alert –Disconnect from  
main battery  If device  is disconnected  from  vehicle 
battery and running on its  internal 
battery  
4. Alert – Low battery  If device  internal  battery  has fallen  
below  a defined  threshold  
5. Alert – Low battery  removed  Indicates  that device  internal  
battery  is charged again  
6. Alert – Connect  back  to 
main battery  Indicates that device  is connected  back 
to main battery  
7. Alert – Ignition  ON Indicates  that Vehicle’s  Ignition  is 
switched ON  
8. Alert – Ignition  OFF Indicates  that Vehicle’s  Ignition  is 
switched OFF  
9. Alert – GPS box opened   Message  would  be generated  indicating  
GPS box opened  
10. Alert – Emergency state  
ON*  When  any of the emergency button  is 
pressed  
11. Alert – Emergency State  
OFF When  emergency  state of vehicle  is 
removed  
12. Alert  Over  the air 
paramete r change  When any parameter is changed  over 
the air. Shall  include  the name of 
parameter changed and  source  of 
command  
13. Harsh  Braking  Alert indicating for harsh  braking.  
14. Harsh  Acceleration  Alert indicating for harsh  acceleration.  
15. Rash  Turning  Alert  indicating  for Rash turning.  
16. Over speeding  Alert indicati ng exceeding the speed 
limits  
17. Device  Tempered  Alert  Indicating  Emergency  button 
wire disconnect/ wire cut / 
Transmission failure,  etc. 
18. Alert -Tamper Weight  Alert indicating Tamper with weight 
sensors. Applied once there is no signal SASO STANDARD  SASO/FDS /33192: 2023 
 
20  sent by the we ight sensors or the once 
the sensor disconnected from the 
vehicle  
19. Accident  Applied once the device experiences a 
shock that indicated as an accident as 
per the device manufacturer settings  
20. Over Weight  Alert indicating exceed the technically 
permi ssible maximum laden mass of a 
vehicle indicated by the vehicle 
manufacturer  
 
7.2.2 In case of emergency alert, the alert message shall be sent to 2 different IP 
addresses hence the device shall support minimum 2 IP addresses (1 IP address for 
regulatory purpose (PVT data) and 1 IP address for Emergency response system other 
than the IP’s required for Operational purpose. The PVT data will send the emergency 
alert to the system. Only Primary alert data will go to the emergency response 
Backend Control Cent re as may be notified by the Government of Kingdom of Saudi 
Arabia in the schema below:  
 
 
Primary alert will go to the emergency response Backend Control Centre  as notified 
by the Government of Kingdom of Saudi Arabia in the indicative format below  (Table  
7C): 
Table  7C 
Attribute  Value  / Description  Size 
 Start  Character  $  1 Byte  
SASO STANDARD  SASO/FDS /33192: 2023 
 
21  Packet  Header  EPB, The unique identifier  
for all messages  from  
telematics device  Character,  3 bytes  
Packet  Type  Message Types supported.  
Emergency Message  
(EMR) or Stop Message  
(SEM)  Character,  3 bytes  
IMEI  Number  Unique  ID of the Vehicle  
(IMEI  Number)  Character,15  bytes  
Packet  Status  NM – Normal  Packet,  
SP – Stored  Packet  Character,  2 bytes  
Date  Date and time of location  
the location obtained from  
the data in DDMMYYYY  
hhmmss  format  Character,14  bytes  
GPS Validity  A – Valid,  
V – Invalid  Character,  1 byte 
Latitude  Latitude  degrees  format -in 
decimal dd.dddddd  Double,  12 bytes  
Latitude  Direction  N – North,  
S – South  Character,  1 byte 
Longitude  Longitude  degrees  format -
in de cimal dd.dddddd  Double,  12 bytes  
Longitude  Direction  E – East 
W – West  Character,  1 byte 
Altitude  Altitude  in meters  (above  
sea level)  Double,  12 bytes  
Speed  Speed  of Vehicle  as 
Calculated  by GPS module 
in VLT. (in km/hr)  Float,  6 bytes  
Accident  Applie d once the device 
experiences a shock that 
indicated as an accident as 
per the device manufacturer 
settings  Character,  8 byte SASO STANDARD  SASO/FDS /33192: 2023 
 
22  Distance  Distance  calculated  from  
previous  GPS data Float,  6 bytes  
Provider  G - Fine GPS  
N - Coarse GPS or data 
from the network  Character, 1 byte  
Vehicle Registration No  Registration Number of the 
Vehicle  Character, 16 bytes  
Reply Number  The mobile number to 
which Test response needs 
to be sent. (Emergency 
Mobile No. as specified by 
KSA.)  0 
Note: No number needs to 
be sent. This  field will with 
value ‘zero’  
End Character  * 1 byte  
Check sum  Ensure  no error in 
transmission  8 bytes  
*Above format is indicative only. These Format will be notified by the 
Government of Kingdom of Saudi Arabia time to time.  
 
7.3 Testing  of Configurat ion of Device  Parameters Over  the Air (OTA)  
The following  testing  will be done  for 
1. Setting/  Change  of the Primary  or Secondary  IP and  port number  
2. Setting/  Change  of the  APN  
3. Set configuration,  parameter  like sleep  time for speed,  harsh  braking,  rash 
turns,  etc. 
4. Emergency  SMS  Centre  Number  
5. Configuring  the vehicle  registration  number  
6. Configuring  the frequency  of data transmission  in normal  / Ignition  state / 
OFF state sleep mode, Emergency  state, etc.  
7. Configuring  the time duration for Emergency  state 
8. Capabili ty to reset the  device  
9. Command  to get  the IMEI  of the  device  
Configurable  commands  must  involve  the following  features:  
 SET:  For setting  the parameters.  
 GET:  For enquiring  regarding  the parameters  such as mobile  number,  GSM  
strength, vehicle number  and other important parameters.  
 CLR:  For clearing  certain  commands,  alarms,  alerts  etc. except emergency 
alert 
 SASO STANDARD  SASO/FDS /33192: 2023 
 
23   
 
 
8.0 CONSTRUCTION  AND  INSTALLATION  
8.1 Requirements  on vehicle  interface  for vehicle telematics system  
Connector  for Power  
(This requirement  is only a guideline  for fitment  and shall  not be checked  during  
component  approval  or on vehicle)  
Standard connectors conforming to ISO 15170 shall be used at vehicle  side. Connector 
requirements shall be as per Annexure – C, Clause 1.1  (Sl. No 1  - Low power syste ms 
1) 
8.2 Requirement of Emergency System  
(To be verified on component level)  
Emergency button shall be one time press type. Separate release action from 
authorized server shall be required to bring back the emergency button to normal 
mode or clear emergen cy flag.  
8.3 Physical Mounting  
(This requirement is only a guideline for fitment and shall not be checked during 
component approval or on vehicle)  
The Vehicle Telematics System shall be mounted in a suitable location such a way 
that it is not easily access ible /exposed to passengers.  
This requirement shall not be applicable in case of combined systems Vehicle 
Telematics System with HMI (Human Machine Interface) display in front of driver.  
Emergency button(s) shall be fitted in such a way that every passenge r including 
driver shall be able to access the Emergency button(s).  
Passenger Car shall have at least one emergency buttons on each passenger row easily 
accessible by each of the passenger. There shall also be one dedicated emergency 
button for the driver row. 
Passenger Transport bus shall have emergency buttons at locations easily visible & 
accessible to all the passengers such as every 2 meters on both the sides on passenger 
seating area. For seats reserved for ladies there shall be a dedicated panic butt on for 
each row.  
In case of passenger transport bus which has a glass window covered between two 
pillars having pitch 2m or more, the emergency buttons shall be provided on each 
pillar  
Trucks shall have one dedicated emergency button for the driver row.  SASO STANDARD  SASO/FDS /33192: 2023 
 
24  8.4 Power  Supply  
(The requirements related to vehicle are only a guideline for fitment and shall not be 
checked during component approval or on vehicle)  
The Vehicle Telematics System will be installed on vehicles in which the power 
supply voltage from vehicl e battery is widely varying (12V, 24V etc.) and also the 
power supply is not as stable as that in case of fixed locations, especially during 
engine start -up and braking when the voltage can fall to as low as 9V. Typically 
electronic devices are very sensit ive to power surges and spikes, and equipment may 
fail if they do not receive stable power supply. The devices will need to have a 
resilient power supply unit that can withstand such fluctuations and the devices also 
need to have power backup so that they continue to function for some duration when 
the vehicle battery is not functional or is disconnected from the devices.  
Vehicle power interface shall have  
 One common ground linked to vehicle chassis  
 One permanent power Supply (12/24V) connected to the vehic le battery 
(+V bat). 
 One non -permanent power line (12/24V) connect to the battery after ignition 
(IGN).  
8.5 Electrical Wiring  
The wiring harness used in the device shall be tested as per IEC 62368 -1 or ISO 19642 
series where ever applicable.  
The fuse links  and connectors of different voltage class s hall be tested with applicable 
ISO 8820  
9.0 FUNCTIONAL, PERFORMANCE, DURABILITY, ENVIRONMENTAL AND 
PROTOCOL TESTS  
9.1 Component  Level  Functional  Tests  
Following functionalities for each of the systems shall be d emonstrated.  At the choice  
of the manufacturer, these functionalities  can also be alternately demonstrated at the 
vehicle level and shall be deemed to be  complied  with at component level as well.  
9.1.1 Vehicle  Telematics System  
9.1.1.1 Standard  connector  provided  for Power  and other  signals  as per Clause no 8.1. 
9.1.1.2 Configuration  of device  as per the standard  format  mentioned  in  Section  7.Local 
configuration upload shall be verified. Configuration upload from control center shall be 
verified.  
9.1.1.3 Vehicle Location data transmission to Backend Control Center. The system shall 
transmit Emergency request information to one IP and PVT information to other IP of 
backend Control Center at user configurable frequency (minimum 5 seconds) via 
GSM/Cellular  SASO STANDARD  SASO/FDS /33192: 2023 
 
25  9.1.1.4 Backend Control Centre shall be able to check the version of firmware loaded on the 
system.  
9.1.1.5 Update the firmware of the system from Backend Control Centre only.  
9.1.1.6 System shall communicate to control center on the occurrence of the alerts captured in 
Communication Protocol Section 7. 
9.1.1.7 When Emergency Button is pressed, emergency request message shall be sent from 
the system and received at the control center.  
9.2 Device Level Functional, Performance & Durability Tests  
 
The tests to be  performed for device level approvals are as listed below.  These  
functionality  check  will be performed  after each test as acceptance  criteria – 
Tested systems shall satisfy general functional requirements at all the  specified  ranges 
during  the test and aft er the  test. 
Following  to be checked after  testing:  
a. Tracking functionality shall be checked via Backend Control Centre  for the 
Vehicle Telematics System (Functional Test number 1 as per “Table 9A 
Functional  Testing”.  
9.2.1  Functional Testing  
Functional Tes ting as described in the Table 9A below shall be done  with the 
acceptance criteria in Table 9A after completion of all the  Performance &  Durability 
Tests as  listed in Table  9B. 
Table  9A 
Sl. No Test Test Procedure  
1 Tracking 
Functionality  Test  The test shall be conducted  on vehicle 
telematics device to determine the proper 
functioning of VLT  with Emergency  Button  
by testing  its connectivity  to Backend  Control  
Centre  (Government  authorized server).  
 
Procedure:  The vehicle telematics device  
shall  be connecte d to vehicle  battery  to switch 
it on. The vehicle telematics device  shall be 
tested for the connectivity  to server  and its 
capability  to send two location  messages  
2 Location  Accuracy  
Test This test shall be conducted on vehicle 
telematics device . SASO STANDARD  SASO/FDS /33192: 2023 
 
26   
The receiver is placed into a cold start state  
– usually by a command sent to the receiver 
through a test connection – and then a fairly 
strong navigation signal simulating in L 
and/or S band is sent. The time it takes for the 
receiver to determine its first g ood location 
fix is recorded. Test is done many times (>15 
times) over many conditions and the results 
are averaged.  
Acceptance Criteria:  2.5 m CEP or 6 m 
2DRMS.  
3 Acquisition  
Sensitivity  Test This test shall be conducted on vehicle 
telematics device   
 
Procedure:  Set the simulator to output 
navigation signal simulating L and/or S band 
to a particular location with a very level so 
that the tracking is not possible. Gradually 
increase the signal level that allows the 
receiver to successfully perform a cold s tart 
TTFF. The minimum signal level that allows 
acquisition is referred as to the acquisition 
sensitivity.  
 
Acceptance Criteria:  The acquisition 
sensitivity shall be minimum ( -)145 dBm 
with GNSS  
4 Tracking  
Sensitivity  Test This test shall  be conducted  on vehicle 
telematics device.  
Procedure:  The device  under  this test is 
locked on to the simulator's output frequency  
(navigation  signal  simulating  L and/or  S 
band)  and the simulator  power  output  is 
lowered  until the lock is lost. Multiple  
repetition of the t est with different satellite  
geometries ensures that an accurate average  
measure  is recorded.  
SASO STANDARD  SASO/FDS /33192: 2023 
 
27  Acceptance  Criteria:  The tracking  sensitivity 
shall be equal to or better than ( -) 165 dBm.  
5 Cold -Start  Time  to 
First Fix (TTFF)  
Test The vehicle telematics dev ice in this test is 
placed into a cold  start state. The time it takes 
for the device to  determine  its first good  
location  fix is  recorded.  The cold start test is 
performed  several  times  and the results  are 
averaged.  
Acceptance Criteria : The cold start TTF F 
shall be less than 40 seconds at Open Sky  
condition  or (-) 130 dBm.  
6 Warm -Start  Time  
to First Fix Test In this test the vehicle telematics device  is 
started in warm start mode and time taken by 
device to determine   the first valid location 
fix is reco rded. This is done several times and 
results are averaged.  
 
Acceptance Criteria:  The warm start TTFF 
shall be less than 60 seconds at Open Sky 
condition or ( -) 130 dBm  
7 Hot-Start Time  to 
First Fix  Test In this test the vehicle telematics device  is 
starte d in Hot start  mode and time taken by 
device to determine  the first valid location fix 
is recorded. This  test is performed  several  
times  and results  are averaged.  
Acceptance  Criteria:  The hot start TTFF  shall  
be less than 10 seconds.  
8 Embedded SIM / 
UICC  Test This test is to check the suitability of the 
embedded SIM/ UICC and communication 
module. The test shall be conducted to 
determine the effectiveness and operation of 
the Cellular module with OTA network 
switching capabilities on demand as well as 
automatically in real -time. The test consist of 
two type of testing as below:  SASO STANDARD  SASO/FDS /33192: 2023 
 
28   
The device would be tested to perform as per 
the protocol using an embedded SIM/UICC.  
The Cellular module & embedded 
SIM/UICC, shall support:  
SMS, Data (Cellular, TCP/IP) and  
Suppo rt multiple network OTA switching 
capabilities (On Demand as well as 
Automatic Switching on real - time basis)  
 
Acceptance Criteria:  In the testing, vendors 
has to demonstrate the embedded SIM/UICC 
based tracking and multiple network OTA 
switching capabilit ies (On Demand as well as 
Automatic Switching on real -time basis) for 
effective network management and 
transmission.  
9 Functional  
Endurance  Test Vehicle telematics device  shall be operated 
for 96 hours  with external  power  supply  and 
internal  battery  conne cted to device.  PVT  
data monitoring  will be done  for complete  
duration  of test with data frequency defined 
after IGN  switch ON mode. Vehicle 
telematics device  shall function  successfully  
during  and after test. 
10 On Vehicle 
Dynamic Location 
Test Vehicle t elematics device  will be mounted on 
any target vehicle connected with vehicle 
battery. Target vehicle with Vehicle 
telematics device  will be run for 10 km on 
pre-defined track/route to verify dynamic 
location test. Vehicle telematics device  PVT 
data shall be within 12 meter for more than 
90% of the fixed location data (as arrived 
using DGPS device on the same route). 
Vehicle telematics device  PVT data shall be 
super imposed on followed route map to 
check its correctness of followed route.  SASO STANDARD  SASO/FDS /33192: 2023 
 
29  11 On Vehicle 
Dynamic Weight 
Test Vehicle telematics device  will be mounted on 
any target vehicle .  
For dynamic systems, a first weight value 
shall be calculated at the latest 15 minutes 
after the vehicle starts to move forward and 
shall be recalculated, every 10 minutes 
henceforth or faster.  
For static systems, weight values shall be 
calculated every minute when ignition is on 
and the vehicle is standing still.  
The accuracy of the calculated weight shall 
be ± 10 % or better.  
 
 
9.2.2 Performance & Durability Test  
The Performance &  Durability  Test is listed  in Table  9B. 
Table  9B 
Sl. 
No Test Test Procedure  
1 Shock  Test Shock test is performed to provide a degree of 
confidence that the device can physically and 
functionally withstand the relatively infrequent, 
non-repetiti ve shocks encountered in 
transportation environments. This test provides 
an assessment of the effect of the shocks on the 
performance of the device. The test shall be 
performed as per IEC 60068 -2-29 (1986), IEC 
60068 -2-31 (1969), IEC 60068 -2-32 (1975). 
Severity Level = 15g, Impact duration = 11ms, 
Impact Type = Half sine, Total number of 
impact = 9 (3 on each axis)  
Acceptance Criteria: Device after the shock  test 
shall be required to meet the provisions  of 
Functional  Test Number  1 as listed  in Table  
9A. SASO STANDARD  SASO/FDS /33192: 2023 
 
30  2 Vibration  Test This test is performed  to check  that the device  
the device  can physically  and functionally  
withstand  the vibration  exposures  in the life 
cycle  typically  encountered in a vehicular 
environment. The  test shall  be performed  as 
per IEC 60068 -2-6. 
The test specimen  mounted  on a suitable 
support shall be rigidly fixed on a  suitable  
vibrating  machine  constructed  to produce  
simple  harmonic  function  (total  amplitude of 
1.5 mm) and shall be subjected  to vibration 
through a frequency range of 10 - 55-10 Hz in a 
sweep period of 1 min with  continuously  
varying  frequencies.  The vibration  shall  be 
applied  for not less than 1 h in the directions of 
each of the 3 major axes  of the light.  
 
Acceptance Criteria: During and after the test  
the device  shall  be requir ed to meet  the 
provisions  of Functional  Test Number  1 as 
listed  in Table 9A. 
3 Ingress  Protection  (IP) The vehicle tracking devices must be able to  
work in dusty environment that are typically  
encountered  by the public  transport  vehicles  
where these would  be installed. IP rating (IEC 
60529 -2001) is used for specifying the  
environmental protection characteristics of the  
tracking device. The device will be tested for  
dust and water  ingress  according  to IP 65 
rating.  
Acceptance  Criteria:  The device  shall  be 
required to meet the provisions of Functional  
Test Number 1  as listed in  Table 9A. 
4 EMI /EMC  The Electromagnetic Interference (EMI) and  
Electromagnetic  Compatibility (EMC)  tests are 
performed to assess whether the device  
performs  its intended  functions  in the 
electromagnetic  environment  to which  it would 
be exposed. Further, the device shall  not 
generate  electromagnetic  disturbances  that may 
influence  other  equipment  in the vicinity.  SASO STANDARD  SASO/FDS /33192: 2023 
 
31  Acceptance Criteria: The device shall meet  the 
EMI/EMC requirements as pe r UNECE 
Regulation No. 10 / CISPR 25.  
5 Battery  Backup  Test Battery backup is the amount of time that the 
device battery can support sending the data 
without being connected to the power source. 
This test will be performed by disconnecting 
the input charg ing voltage to the device. On 
disconnecting the external supply, battery 
would use its charge capacity to send data 
through Cellular. Time duration between 
external power disconnect to the last data 
packet time d enotes the battery backup time.  
Acceptance C riteria:  Device shall be able to 
work in active mode for a period of 4 hours or 
more at the polling/ transmission rate of 60 sec.  
6 Reverse  Polarity  
Protection  without  Fuse  The device to be tested shall be connected to  a 
reversed voltage of 14 V for 12 V systems  and 
27 V for 24 V systems for 2 min after  
connecting  the system  to the suitable  circuit.  
Acceptance Criteria: After test; the device  shall 
be required to meet the provisions of  
Functional Test Number 1 as listed in Table  
9A. 
7 Wiring  Harness - 
Flammability  Test Flammability  Test:  The wiring  harness  used in 
the device shall be tested for  flammability   
8 Wiring  Harness - 
Electrical  Properties  As per DIN 72551 or ISO 6722  
9 Free Fall IEC 60068 -2-32 (1975) Free  fall at 500 mm. 
Acceptance Criteria: Af ter test the device  shall 
be required to meet the provisions of  
Functional Test Number 1 as listed in Table  A SASO STANDARD  SASO/FDS /33192: 2023 
 
32  10 Performance  Parametric  
Test 
(Nine points,  tri 
temperature/tri  voltage)  During testing, Vehicle telematics device  shall  
be kept  inside test  chamber in  power  ON 
condition.  
(System shall be stabilized for minimum 5  min 
at each condition.  
At each test point the system will be powered  
on and shut down  5 times  with a duration  of 1 
min ON  and 1 min OFF  time)  
Following  are the various  voltages  & 
tempera tures  
Acceptance  Criteria:  The device  shall be 
required to mee t the provisions of Functional 
Test Number 1 as listed in Table A for each  
value  of the temperature  and voltage.  24V System  12V System  
18V,  -25°C  9V, -25°C  
18V,  +80°C  9V, +80°C  
18V, Room  
Temperature  9V, Room  
Temperature  
27V,  -25°C  13.5V,  -25°C  
27V,  +80°C  13.5V,  +80°C  
27V, Room  
Temperature  13.5 V, Room  
Temperature  
32V,  -25°C  16V,  -25°C  
32V,  +80°C  16V,  +80°C 
32V, Room  
Temperature  16V, Room  
Temperature  
 SASO STANDARD  SASO/FDS /33192: 2023 
 
33  11 Insulation  
Resistance Test  Test shall be conducted as per ISO 16750 - 
2:2010 after damp heat test mentioned in  point  
3 of the Section 6.4.  
System/components  shall  remain  0.5 h at RT 
after the damp heat test.  
Test shall be conducted With a voltage of  500 
V DC. Acceptance  Criteria:  Insulat ion 
Resistance  shall  be > 1 MΩ.  
No arcing or puncturing of insulation  allowed  
shall be  observed  
12 Load Dump  Test 
Pulse  5a Vehicle telematics device  shall  be tested  for 
this. 
For 12 V  System:  
A Voltage  spike  of 65V,  4 Ohms  200ms  
pulse -5a as per  standard  ISO 7637 -2: 2004  
For 24 V System:  
A Voltage  spike  of 123V,  8 Ohms  200ms  
pulse -5a as per standard  ISO 7637 -2: 2004.  
Acceptance  Criteria:  Device  shall  meet  
functional class A as per ISO 7637 -2: 2004.  
After  test, the device  shall  be required  to meet  
the provisions  of Functio nal Test Number  1 as 
listed in Table 9A. 
 
 
 
 
 
 
 
 
 
 
 
 
 SASO STANDARD  SASO/FDS /33192: 2023 
 
34  9.2.3 Device  Level  Environmental  Tests  
The environmental  tests to be performed  for device  level  approvals  are as listed  in Table 9C. 
Following  to be checked  after testing:  
i. Tracking  functionality shall  be checked  via Backend  Control  Centre  for the  Vehicle 
telematics device.  
Table  9C: 
 
Sl. No Test Test Procedure  
1 Dry Heat / High  
Temperature  Test The high temperature test is used to evaluate  
effects  of high temperature  conditions  on 
safety,  integrity,  and performance  of the 
device.  The test shall  be carried  out in 
accordance with IEC 60068 -2-2 the  device  
shall  be subjected  to temperature  of 70 ± 2°C 
for 16 h in high temperature.  Test with device  
in working condition.  The recovery  period shall  
be 2 h.  
 
Acceptanc e Criteria: Device during and after  
the high temperature test the device shall be  
required to meet the provisions of Functional  
Test Number 1  as listed  in Table 9A. 
2 Cold  Test The test shall be carried out in accordance with  
IEC 60068 -2-1. The device  under test shall  be 
subjected  to temperature  of 
–10 ± 2°C for 2 h with device  in working  
condition.  The recovery  period shall  be 2 h.  
Acceptance Criteria: Device during and after  
the cold test, the device shall be required to  
meet the provisions of Functional  Test Number 
1 as listed in  Table 9A. SASO STANDARD  SASO/FDS /33192: 2023 
 
35  3 Damp  Heat  Test The device under test shall be tested according  
to IEC  60068 -2-30. The test is  carried out at 
+25° to +55° C, Humidity 95%.  Six cycles 
(each test cycle of 24 h) shall be run  with 
device  in off conditi on. Functional  test shall  be 
carried  out with power  in ‘On condition’  at 
start of 2nd , 4th and 6th cycle.  
Acceptance Criteria: Device during and after  
the test the device shall be required to meet the  
provisions  of Functional  Test Number  1 as 
listed  in Ta ble 9A. 
4 Temperature  Shock  Temperature  shock  test is carried  out to 
determine if the device can withstand sudden  
changes in the temperature of the surrounding  
atmosphere  without  experiencing  physical  
damage or deterioration in performance. The  
device  shall be tested  as per IEC 60068 -2-14. 
Exposure time would be 3  hours/cycle  and 
number  of cycles  would  be two. 
Acceptance Criteria: Device after the test the  
device shall be required to meet the provisions  
of Functional Test Number 1 as listed in Table  
9A. 
5 High Temperature  
Test The high temperature test is used to evaluate  
effects  of high temperature  conditions  on 
safety,  integrity,  and performance  of the 
device.  The test shall  be carried  out in 
accordance with IEC 60068 -2-2 where  the 
device  shall  be subjec ted to temperature  of 70 ± 
2°C for 16 h in high temperature.  Test with 
device  in working  condition.  The recovery  
period shall  be 2 h.  
Acceptance Criteria: Device during and after  
the high temperature test  the device shall be  
required to meet the provisions  of Functional  
Test Number 1  as listed  in Table 9A. SASO STANDARD  SASO/FDS /33192: 2023 
 
36  6 Salt Spray  Test The salt spray  test is conducted  to check  
corrosion  resistance  of device.  The device  shall 
be tested according to IEC 60068 -2-11 for  96 h.  
 
Acceptance  Criteria:  The device  shall  be 
required to meet the provisions of Functional  
Test Number 1 as  listed in Table 9A. 
7 High  Voltage  Test The test is conducted  to ensure  service  life 
requirements & functionality. The device under  
test shall be operated for 60 minutes at 18 V for  
12 V systems &  36 V for 24 V systems. This  
test is  as per ISO  16750 -2:2010  
Acceptance Criteria: Device during and after  
the test the device shall be required to meet the  
provisions  of Functional  Test Number  1 as 
listed  in Table 9A. 
 
9.2.4 Protocol  Testing  
These set of testing needs to be done for all cases namely vehicle level  testing  and 
component  (Device)  level testing . 
Protocol is a set of rules to be followed by the device while sending data  to the Backend 
Control Centre. The protocol comprises data update rate,  number of fields, start character, end 
character, alert type etc. Protocol  testing involves checking the compliance of data sets 
received by the  Backend Control Centre  against the protocol both with respect to the  data 
fields as well the format. It is expecte d that the data coming to a  central server shall be exactly 
as required under the protocol. Table  below  (Table  9D) mentions  the validation  process  for 
the protocol  communication.  
Table  9D 
Field  Description  Validation  Process  
Field  Description  
Start  Chara cter $ 
Header  The header of  the packet/ identifier  
Vendor  ID Vendor  identification  header  
Firmware  Version  Version  details  of the Firmware  used in EX.1.0.0  SASO STANDARD  SASO/FDS /33192: 2023 
 
37  Packet  Type  Specify the packet type – NR = Normal  
EA =  Emergency  Alert  
TA = Tamper  Alert  
HP = Health Packet  IN = Ignition  On 
IF = Ignition  Off 
BD = Vehicle Battery  Disconnect  
BR = Vehicle  Battery  Reconnect  
 BL = Internal  Battery  Low 
HB= Harsh Braking  
HA= Harsh Acceleration  
RT= Rash Turning  
Packet  Status  L=Live  or H=  History  
IMEI  Identified  of the sending  unit. 15 digit standard  
unique IMEI  no. 
Vehicle  Reg. No Mapped  vehicle registration  number  
GPS Fix  1 = GPS fix OR 0 =  GPS invalid  
Date  Date  value  as per GPS date time 
(DDMMYYYY)  
Time  Time  value  as per GPS date time in UTC 
format  (hhmmss)  
Latit ude Latitude  value  in decimal
 degrees  (with  minimum  6 decimal 
places)  
Latitude  Dir. Latitude  Direction.  
Example  N=North,  S= South  
Longitude  Longitude  value  in decimal  degrees  (with  
minimum  6 decimal  places)  
Longitude  Dir. Longitude  Direction.  
Example  E=East,  W= West  
Speed  Speed of Vehicle as Calculated by GPS module  
in VLT.(in km/hr)  
Heading  Course  over ground  in degrees  SASO STANDARD  SASO/FDS /33192: 2023 
 
38  Total Weight  Total weight of vehicle + load in Kg  
No. of Satellites  Number  of satellites available  for fix 
Altitude  Altitude  of the device  in meters  
PDOP  Positional  dilution  of precision  
HDOP  Horizontal  dilution  of precision  
Network  Operator  Name  Name  of Network  Operator.  
Ignition  1= Ign  On , 0 = Ign Off 
Main  Power  Status  0 = Vehicle Battery  Disconnected  
1= Vehicle Battery  Recon nected  
Main  Input  Voltage  Indicator  showing  source voltage  in Volts.  
Internal  Battery  Indicator  for Level  of battery  charge  remaining  
Alert ID  02 Character  
Voltage   
Emergency  Status  1= On , 0  = Off  
Tamper Alert   C = Cover Closed  , O = Cover  Open  
GSM  Signal  Strength  Value  Ranging  from  0 – 31 
MCC  Mobile  Country  Code  
MNC  Mobile  Network  Code  
LAC  Location  Area  Code  
Cell ID GSM  Cell ID 
NMR (neighbouring  Cell 
ID) Neighbouring  4 cell ID along  with their LAC  and 
signal  strength  
Digital  Input  Status  4 external  digital input  status  (Status of  Input 1  
to Input  3 (0=Off; 1=On))  
Digital  Output  Status  2 external  digital  output  status  
(0=Off;  1=On)  
Frame  Number  Sequence  Number  of the messages  (000001  to 
999999)  
Checksum  Insures  No error  in transmission  (opti onal)  
End Character  Indicated  End of the frame  SASO STANDARD  SASO/FDS /33192: 2023 
 
39  The following  test would be  performed  along  with the protocol testing of 
the device:  
 
a. Memory  Storage  
The device shall support 40000 or more positional logs/packets. This is a functional 
test and the device will be simulated to be in non – Cellular coverage area and the logs 
will be maintained. The capacity of logging will be checked by monitoring the logs on 
the device.  
b. Messages  & Alerts  from  Devices  
Table below (Table 9E) contains the listing of alerts that  need to  come from the 
Vehicle telematics devices. These alerts are applicable for both  live packets as well as 
the history  packets.  
Table  9E 
Alert  
ID Message  & Alerts  Remarks  
1. Location  Update  Default  message  coming  from  
each device  
2. Location Update (history)  Would be sent, if Cellular is not 
available at the time of sending 
the message  
3. Alert  – Disconnect  from  main 
battery  If device is disconnected from  
vehicle battery and running on  its 
internal battery  
4. Alert  – Low battery  If device  internal  battery  has 
fallen below a defined  threshold  
5. Alert – Low battery  removed  Indicates  that device  internal  
battery  is charged again  
6. Alert  – Connect  back  to main 
battery  Indicates that device is  
connected  back  to main  battery  
7. Alert  – Ignition  ON Indicates that Vehicle’s  Ignition  
is switched  ON 
8. Alert  – Ignition  OFF Indicates that Vehicle’s  Ignition  
is switched  OFF 
9. Alert – GPS box opened   Message  would  be generated  
indicating  GPS box opened  
10. Alert  – Emergency  state ON*  When  any of the emer gency  
button  is pressed  SASO STANDARD  SASO/FDS /33192: 2023 
 
40  11. Alert  – emergency  State  OFF Emergency  state of switch  will 
be cancelled by backend  server, 
when emergency state  of vehicle  
is removed  
12. Alert  Over  the air parameter  
change  When any parameter is  changed 
over the air. Shall  include the 
name of parameter  changed  and 
source  of command  
13. Harsh  Braking  Alert  indicating  for harsh  
braking.  
14. Harsh  Acceleration  Alert indicating for harsh  
acceleration.  
15. Over Speeding  Alert indicating exceeding of 
speed limits  
16. Rash  Turnin g Alert  indicating  for Rash  turning.  
17. Alert -Tamper Weight  Alert indicating Tamper with 
weight sensors. Applied once 
there is no signal sent by the 
weight sensors or the once the 
sensor disconnected from the 
vehicle  
18. Accident  Applied once the device  
experiences a shock that 
indicated as an accident as per 
the device manufacturer settings  
19. Over Weight  Alert indicating exceed the 
technically permissible 
maximum laden mass of a 
vehicle indicated by the vehicle 
manufacturer  
* In case of Emergency Al ert ON system, the alert message should go in 
the below format as set out in Table 9F. This emergency alert message  
shall be sent to 2 different IPs; i.e. the device shall support minimum 2  IPs 
simultaneously.  
 
 
 
Table  9FSASO STANDARD  SASO/FDS /33192: 2023 
 
41  Start  Character    $ 1 byte 
Packe t Header  EPB, The unique identifier  for all 
messages  from  Vehicle telematics 
device  Character,  3 bytes  
Packet  Type  Message Types supported.  
Emergency  Message  (EMR)  or Stop 
Message (SEM)  Character,  3 bytes  
IMEI  Number  Unique ID of the Vehicle  (IMEI  
Number ) Character,15  bytes  
Packet  Status  NM – Normal Packet,  SP – Stored  
Packet  Character,  2 bytes  
Date  Date  and time of the location  obtained 
from the location  data in 
DDMMYYYY  hhmmss  format  Character,14  bytes  
GPS Validity  A – Valid,  V – Invalid  Character,  1 byte 
Latitude  Latitude  in decimal  degrees  - 
dd.mmmmmm  format  Double,  12 bytes  
Latitude  Direction  N – North,  S – South  Character,  1 byte 
 
Longitude  Longitude  in decimal  degrees  - 
dd.mmmmmm format  Double,  12 bytes  
Longitude  
Direction  E – East W – West  Character,  1 byte 
Altitude  Altitude  in meters  (above  sea level)  Double,  12 bytes  
 
Speed  Speed of Vehicle as Calculated by 
GPS module in Vehicle telematics 
device  (in km/hrs.)  Float,  6 bytes  
Accident  Applied once the device experiences 
a shock that indica ted as an accident 
as per the device manufacturer 
settings  Character,  8 byte 
Distance  Distance  calculated  from  previous  
GPS data  Float,  6 bytes  
 
Provider  G – Fine GPS 
N – Coarse  GPS or data from  the 
network  Character,  1 byte SASO STANDARD  SASO/FDS /33192: 2023 
 
42  Vehicle  Reg. No  Registration  Number  of the Vehicle  Character,  16 bytes  
 
 
Reply  Number  The mobile number to which  Test 
response need to be sent.  (Emergency  
Mobile  No. as specified Government 
of Kingdom of Saudi Arbia)  0 
End Character  * 1 byte 
Check  sum Ensure  no error  in transmissi on. 8 bytes  
 
 
10.0 DEVICE  TO BACKEND  COMMUNICATION  MECHANISM  
 
The Vehicle telematics device would transmit data to the Backend Control Centre using 
Cellular wireless connectivity (with SMS fall back) as per the protocol provided in respective 
sections (Su b-section 6.3.4). The data from the devices would travel over the wireless telecom 
service provider network and finally get delivered at the Backend Control Centre. Since the 
permit holders/Device suppliers would require to have a valid communication plan on 
embedded SIM/UICC cards on the devices and would avail services from multiple telecom 
service providers, the data would be transmitted to the Backend Control Centre using the 
networks of multiple telecom service providers.  
The Communication from Device to backend should happen on a Secure channel  over 
TCPIP protocol preferably on socket based connections where sessions are  managed to 
send commands over the same connection to the device and are  authenticated,  
identifiable,  so as to prevent  spoofing  on IME I/ Unique  ID 
 SASO STANDARD  SASO/FDS /33192: 2023 
 
43   
 
A suitable control mechanism would be established for the data transfer from Vehicle 
telematics device to Backend Control Centre, as only the authorized devices should be able to 
transfer data to the Backend Control Centre and a mechanism for authenticating the devices/ 
embedded SIM/UICC shall also be put into place.  
The following mandatory provisions will have to be made in the Backend  Control Centre:  
1. Registration  and activation  of the device(s)  fitted  on the vehicle,  including the  details  
of vehicle  registration  number,  engine  number,  chassis number, vehicle make and 
model, device make and model, and  telecom  service  provider’s  name.  
2. Re-registration/re -activation of the device(s) fitted on the vehicle in case  of any change  
in device  or telecom service  provider, etc.  
3. Regular health check of the device(s) fitted on the vehicle, as per the  parameters  and 
frequency  defined in Sub -section 6.0.5 . 
4. Administration/configuration  of devices  for any changes  in the parameters  as decided 
by the respective  state from  time to time.  
5. Notification of alerts in case of press of an Alert Button fitted on the  vehicle,  in the  
protocol defined in Section 7. 
6. Notification of alerts in case of defined deviations by vehicle such as  over-speeding, 
deviation from defined route/geographic area, time of  operation,  etc. 
7. Location tracking of the vehicle including real -time as well as history  tracking  for up 
to last  90 days.  
8. Notification to the permit -holder through SMS in case any device(s)  stops  
functioning/sending  data to the Backend Control Centre.  
SASO STANDARD  SASO/FDS /33192: 2023 
 
44  9. Reports of the vehicles with devices not working/sending data beyond  defined  number  
of days (1 day,  3 days, 7  days and 30 days).  
10. Ensure  that the security  and privacy  of the data is maintained  in accordance  with 
applicable  laws/gui delines  of various  government  authorities. Personal data should be 
protected by reasonable security safeguards against such risks as loss or unauthorized 
access, destruction, use, modification or disclosure of data.  
In addition to the above mandatory provi sions, the Backend Control Centre  can provide  any 
other optional features.  
The mechanism  to set up the  Backend Control  Centre  shall be decided  by the respective 
states. The states can chose any of the following options for  setting  up the  Backend Contro l 
Centre: 
1. States can set up their own dedicated Backend Control Centre, meeting  the above 
listed mandatory provisions and any other optional features as  they may decide.  
2. States can allow telecom service providers to offer Backend Control  Centre as a Value 
Adde d Service (VAS) to the permit holders, meeting  the above listed mandatory 
provisions and any other optional features as  they may decide.  In this case,  the 
telecom  service  providers  shall  provide  access  to the Backend  Control  Centre  to 
government  officials,  as decided by  the respective state.  
11.0 CODE OF PRACTICE for Implementation of Vehicle Telematics device and 
Command and Control Centres  
 
This Code of Practice for this standard has been formulated for facilitating smooth  
Implementation of Vehicle Telem atics device including Vehicle Location Tracking (VLT) 
Device, Emergency Button(s), On Board Weighing System (OBW)  and Command  and 
Control  Centres  for the guidance  of the stakeholders  concerned.  
 
11.1 General  
a. The device manufacturers will get their devices  tested and certified from  SASO or 
authorized type approval authority.  
 
b. The Backend System shall mean the backend Command and Control Centre  set up/ 
authorized  by administrative regions (or  states),  providing  interface  to various  
stakeholders/systems  such  as State  emergency  response  centre,  the transport  
department  or Regional  Transport  Offices,  Ministry  of Transport and its 
designated agency, administrative regions (or states)  system used  for registration  
of vehicles  and/or  issuance of  permits), Vehicle Te lematics device manufacturers 
and their authorized dealers, testin g agencies , permit  holders,  etc. In the absence  of 
administrative regions (or states)  State  backend  system,  the registration,  activation,  
health  check  and alert updates  of Vehicle Telematics  device  shall be  through  a 
common  layer  for updation  in central vehicle registration database.  
The details of each device ( Vehicle Telematics device  manufacturer code, device  
serial number, IMEI number, ICCID number and other details as notified by  the SASO STANDARD  SASO/FDS /33192: 2023 
 
45  respective ministry in the Kingdom of Saudi Arabia) shall be uploaded on the vehicle 
registration database directly  or through  backend  system  by the Vehicle Telematics 
device manufacturer  using its secure  authenticated  access.  
The device  manufacturers  or their authorized  dealers  shall  install  the devices  in 
vehicles  and register/activate  the devices  along  with details of vehicle and permit 
holder on the corresponding backend systems in real - time as per the process  set out 
below.  
The backend system/common laye r will update the details of device in the vehicle 
registration system  against  the respective  vehicle  record  at the time of installation  
and registration/activation  of device.  
c. The Vehicle Telematics device manufacturers or their authorized dealers, at the 
time of  installation of device in vehicles, shall configure the IP address and  SMS 
gateway details in the device for sending emergency alerts to the  emergency  
response  system  of the State  concerned.  
 
d. The Vehicle Telematics device manufacturers or their aut horized dealers, at the 
time of installation  of device in vehicles, shall configure the configuration  
parameters mentioned in this standard in the device such as IP address and SMS  
gateway  details  for sending  required  data to the backend  system.  
 
e. The Vehic le Telematics device manufacturers shall ensure that a control 
mechanism is  established for the secure data transfer from device to the backend 
system  and that only the authorized devices transfer data to the backend system.  
The device manufacturers shall also ensure that the mechanism for  authenticating 
the vehicle owner and devices is followed as per the protocol  specified in this 
standard or such additional requirements as specified by the  States. Authentication 
of vehicle shall be done through an OTP se nt on  vehicle  owner’s  mobile  number  
from  the corresponding backend  system.  
 
f. In case of press of an emergency button, the Vehicle Telematics device will send 
data directly to the emergency response system of the respective State. In  addition, 
the backend sy stem will send the alert to the respective permit  holder,  as decided  
by the State.  
 
g. Vehicle Telematics device manufacturers  shall  get their devices  tested  for 
conformity  of production every year from the date of first certification, from 
SASO or authorized  type approval authority.  
 
h. Vehicle Telematics device manufacturers shall get their backend systems certified for 
the States  from  the SASO or authorized type approval authority.  
 
i. The Vehicle Telematics device manufacturers  or their authorized  dealers,  at the 
time of installation  of devices  in vehicles,  shall  configure  the device  to send a 
secure authenticated activation message directly to the State  backend  
system/common  layer  as per the details  provided  in this section  11. SASO STANDARD  SASO/FDS /33192: 2023 
 
46   
j. The Vehicle Telematics device manufacturers  shall  ensure  that the Health  Check  
parameters are configured in the device to send Health Check  messages, on request 
from the State backend system/common layer, to  the respective backend system 
through SMS as per reference protocol  mentioned  in this section   11. 
 
k. Vehicle Telematics device manufacturers  or their  authorized  dealers  shall  provide  
comprehensive warranty/maintenance support for the device and  facilitate  cellular  
connectivity  in accordance  with the guidelines  issued  by Government of Ki ngdom 
of Saudi Arabia via separate order and amended from time to time.  
 
 
l. SASO or authorized type approval authority may  verify  the conformity  of 
production  for the Vehicle Telematics device as prescribed  in section  11.5. 
 
11.2 Installation,  Registration,  Activation  and Service  Process  for Vehicle Telematics 
Device  
 
a. Device manufacturers or their authorized dealers shall install Vehicle Telematics 
device  on permit  holder’s  vehicles  (only  tested  and approved  model).  
b. Device manufacturers shall ensure necessary  uploading/integration of  the 
installation/activation  data to the backend  system/ vehicle registration database.  
c. In case of any problem  in updating  backend  system/ vehicle registration database,  
it will be device  manufacturer’s  responsibility  to resolve  the same.  
d. Device manufacturers or their authorized dealers will also provide  necessary print 
of installation/activation report to permit holder from the  respective  backend  
system.  
e. Regional  Transport  Offices  shall  be able to verify  the 
registration/activation /functional  status  of device  in the vehicle registration 
database /corresponding  backend  system  at the time of fitness  testing.  
f. The permit holder will have option to check the installation and device  working  
status  in the vehicle registration database.  
g. The device  manufacture  may offer  value  added  services,  in addition to  the 
mandatory performance requirements to the permit holders as per the  mutual 
agreement between them. Mandatory performance requirements  shall  mean  the 
following:  
 
i. Uploading  device  data in the backend  system/ vehicle registration database  
ii. Updating  registration  and activation  data of Vehicle Telematics device  
iii. Sending  device  health  status  to the backend  system  
iv. Sending emergency alerts to the corresponding State / central emergency  response  
system  
v. Sending  over speeding  alerts  to the backend  system  
vi. Other performance requirements as this standard and as notified by Government of 
Kingdom of Saudi Arabia via separate order and amended from time to time.  SASO STANDARD  SASO/FDS /33192: 2023 
 
47   
h. Device manufacturers may create their own sy stem to monitor  their  supplied  
devices,  emergency  button/s  & connectivity  working  / non- working  status  for 
managing  warrantee  / AMC  and Cellular  services.  
i. Device manufacturers or their dealers will update the SIM  numbers  and their 
validity/renewal  details  in the backend  system.  
 
11.3 Vehicle telematics device manufacturers  backend  application/system  requirements  
 
In case Vehicle Telematics device manufacturer offers to provide its backend system for 
State,  the same will need to meet the following requireme nts, in addition to those specified  in 
Clause  10 of this standard : 
a) The application  will provide  the ability  to locate  a vehicle  at a given  time.  
b) Facility to track defined vs. actual movement of vehicles, capture deviations  if any 
(For vehicles where schedu led movement can be defined on GIS  map.)  
c) The application should provide ability to track vehicle location on map. The  map 
engine  and data should  comply  with applicable  regulations  including guidelines  as 
set out by Kingdom of Saudi Arabia from  time to time. 
d) Facility for users to access and view position / location information on GIS  maps  near 
real-time through  web interface  with historic  data displayed  on maps.  
e) Facility  for providing  current  information  location  on demand.  
f) Facility for playing back the reco rded details of the vehicle movement along the 
authorized  route  (where  applicable).  
g) Provide  facility  of alert generation  
 
i. Ability  to define  new alerts  on specific  events  
ii. From  the on-board  devices  in case of tampering  
iii. Speed  exceeds  the permissible  limit  
iv. Vehicle moves  out of its designated  route  or area 
v. Vehicle weight exceeding the permissible limits  
vi. Data  feed not received  from  the on-board  device  
 
h) Provide facility to define rules for alerts/ notification and their delivery  mode  like 
SMS,  email,  pop-up etc. 
i) Management of notifications to various stakeholders by way of email or  SMS  e.g. 
permit  holders,  about  device  not working,  over-speed, over -weight,  etc. 
j) Notification to the permit -holder through SMS in case any device stops  
functioning/sending  data to the application.  
k) Capability  to update  the on-board  devices’  firmware  from  the backend.  
 
l) Capability  to configure  on-board  device  parameters  from  the backend.  SASO STANDARD  SASO/FDS /33192: 2023 
 
48  m) The tracking  data will be kept live in the system  for at least 90 days.  Utilities  will be 
provided to sup port archive and restore functions for older data.  Alerts/reporting  
shall  be available  for one year in the backend.  
n) The backend will store VTS time -related data at the same resolution as  received in 
the live application. The archived data after 90 days can  also be  restored  using  
utilities  provided.  
o) From a security perspective, the devices will not communicate to any IP  address  
located  outside  Kingdom of Saudi Arabia  whether  it be the manufacturer’s  
application  or for purposes  of configuration  or firmware  updates.  
p) Firmware of the device needs to be available for auditing to notified testing  agencies. 
Firmware binary should be made available with version matching  one in the device  as 
well as binary  size & modification  timestamp  and/ or checksum should match fo r the 
binary provided and one installed on device.  Backend System should be able to 
remotely read the existing version  number  of the firmware  via an OTA  
configuration  read command.  A new version of the firmware should be pushed 
over the air from the Vehicl e Telematics device  manufacturer’s application. This 
shall be verified by the backend system  remotely reading the new version number of 
the firmware in the device via  and OTA  configuration  read command.  
 
q) The device will communicate only to whitelisted set of IP addresses located  in 
Kingdom of Saudi Arabia  and will receive  communication  and commands  also 
from  whitelisted  set of IP addresses  located  in Kingdom of Saudi Arabia.  
r) The application and all key components like device management, firmware  control,  
GIS map shall  be hosted  at a data centre/  cloud  in Kingdom of Saudi Arabia  and it 
will be available  for auditing  by regulatory  agencies.  
s) The system shall provide > 99% availability and adhere to Infrastructure  Security,  
Vulnerability  Assessment  and Penetrati on Testing  guidelines  as set out by relevant 
ministry of Government of Kingdom of Saudi Arabia.  
t) No data should flow out of the country under any circumstances in  compliance  
with applicable  laws/regulations/guidelines.  
 
u) The common layer shall be tested from  SASO or authorized type approval authority  
for the following  minimum  functionalities:  
i. Registration and activation of the device(s) fitted on the vehicle,  including  the 
details  of vehicle  registration  number,  engine  number,  chassis number, vehicle 
make and  model, device make and model,  and connectivity details (telecom 
service provider’s name, ICCID,  SIM Nos.,  IMSI,  date of validity,  etc.).  
ii. Publish Vehicle Telematics device details in the vehicle registration database/ any 
other State system  used for regist ration  of vehicles  and/or  issuance  of permits  
iii. Re-registration/re -activation  of the device(s)  fitted  on the vehicle  in case of any 
change  in device  or telecom  service  provider,  etc. 
 
iv. Periodic health check of the device(s) fitted on the vehicle through  SMS,  as per 
section  11.4. SASO STANDARD  SASO/FDS /33192: 2023 
 
49  v. Receiving  alerts  from  Vehicle Telematics devices  in case of defined  deviations  by 
vehicle such as over -speeding, etc. Publish alerts and health check received  from  
device  in the vehicle registration database / any other  State  system use d for 
registration  of vehicles  and/or  issuance  of permits.  
vi. Provide interface to vehicle registration database , respective States, RTOs, SASO 
or authorized type approval authority,  Vehicle Telematics device manufacturer’s  
and their  dealers.  
11.4 Activation  message  and Health  Check  Message  Protocol  
 
The protocols for activation message and health check message are given below.  Device  
shall  send  the activation  and health  check  messages  on request  as specified  below directly 
to the backend system (i.e. backend Command and Control Centre set  up/ authorized  by 
States  or a Common  Layer  system  providing  interface  to Vehicle Telematics device 
manufacturers’  backend  applications).  
 
A. Activation  SMS  Format  from  Backend  System  to Device  
 
For completion  of the installation  process,  the Vehicle Telematics device  shall  undergo  
Activation process  as per below:  
 Activation  Message  Request  Format  from  the Backend  System  to the Device  
(Through  SMS):  ACTV,  Random  Code,  Reply  SMS  Gateway  no. 
 
 Activation  Message Reply  Format from Dev ice to the Backend System  (Through  
SMS)  as per Table  1 below:  
 
 
Table -1: 
Activation  & Health  Check Response SMS Format  from  Device  to Backend  
System  
Field  Name  Characters  Activation  
Example  Health  Check  Example  
Header  5 ACTVR  HCHKR  
Separator  1 , , 
Rand om code  6 343434  474747  
Separator  1 , , 
Vendor  ID 4   SASO STANDARD  SASO/FDS /33192: 2023 
 
50  Separator  1 , , 
Firmware  version  6 V1.6.1  V1.6.1  
Separator  1 , , 
IMEI  15 01234567891234
5 012345678912345  
Separator  1 , , 
Alert  ID 2 1 1 
Separator  1 , , 
Latitude  12 14.034533  14.034533  
Separat or 1 , , 
direction  1 N N 
Separator  1 , , 
Longitude  12 24.32045  46.32045  
Separator  1 , , 
Direction  1 E E 
Separator  1 , , 
GPS fix 1 1 1 
Separator  1 , , 
Date  and Time  15 16112018  120317  16112018  120317  
Separator  1 , , 
Heading  6 263.19  263.19  
Separ ator 1 , , 
Speed  4 25.4 25.4 
Separator  1 , , 
GSM  Strength  2 23 23 
Separator  1 , , 
Country  Code  
(MCC)  3 420 420 
Separator  1 , , SASO STANDARD  SASO/FDS /33192: 2023 
 
51  Network  Code  
(MNC)  4 10 10 
Separator  1 , , 
LAC 4 d6d6  d6d6  
Separator  1 , , 
Main  Power  1 1 1 
Separator  1 , , 
IGN Status 1 1 1 
Separator  1 , , 
Battery  Voltage  4 24.6 24.6 
Separator  1 , , 
Frame  Number  6 100000  100000  
Separator  1 , , 
Vehicle  mode  2 ID ID 
Total  Characters  139   
 
B. Health  Check  Random  Messages  from  Backend  System  to Device  
Frequency:  Twice  Daily  (Recomm ended),  
Health  Check  Message  Request  Format  from  the Backend  System  to the Device  
(Through  SMS):  HCHK,  Random  Generated  ID, Reply  SMS  Gateway  no. 
Health  Check  Message  Reply  Format  from  Device  to Backend  System  (Through  
SMS):  As per Table  1 above.  
 
C. Publish  Data  to Common  Layer by Vehicle Telematics device Manufacturers’  
Applications  (Sample)  
 
Requirement  to be complied  with  by Vehicle Telematics device manufacturers’  
applications  
Application  shall  publish  the data to common  layer  in a specified  frequency  and format  
as mentioned  below  
Services  to publish  data  to the common  layer:  
i. Push  Offence  Details  SASO STANDARD  SASO/FDS /33192: 2023 
 
52  Type  REST  web service  
Data  Type  JSON  Array  
Frequency  1 Hour  
A single  request  may contain  JSON  Array  of maximum  500 JSON  Objects  of the 
following  format.  
Sl No Key Value  Length in 
bytes  Description  
In Parameters  
1. oftyp  2 Offence  Type  
OS= Overspeed  
2. vno 16 Vehicle number without any  
delimiter  like hyphen  (-) or space.  
3. imei 15 IMEI  number.  
4. date 8 Date  in format  DDMMYYYY  
5. time 6 UTC  in format  hhmms s 
6. lat 12 Latitude, decimal  not less than 6 
places  
7. latd 1 Latitude  Direction.  N=North,  S= 
South  
8. lon 12 Longitude, decimal  not less than 6 
places  
9. lond 1 Longitude  Direction.  E=East,  W= 
West  
10. spd 6 Speed  in km/hr, u pto One Decimal 
Value . 
11. wei 6 Weight in Kg.  
12. loc  Location  (Reverse  Geo-coded)  
13. rto  Road transport authority code  
14. state   State  Code  
Response  
15. resp  OK/ Error  
 
 SASO STANDARD  SASO/FDS /33192: 2023 
 
53  ii. Push Alert Details  
Type  REST  web service  
Data  Type  JSON  Array  
Frequency  1 Hour  
A single  reque st may contain  JSON  Array  of maximum  500 JSON  Objects  of the 
following  format.  
Sl No Key Value  Length  in 
bytes  Description  
In Parameters  
1. alrtid  2 Alert  ID as per this SASO standard  
2. vno 16 Vehicle number without any  
delimiter  like hyphen  (-) or space. 
3. imei 15 IMEI  number.  
4. date 8 Date  in format  DDMMYYYY  
5. time 6 UTC  in format  hhmmss  
6. lat 12 Latitude, decimal  not less than 6 
places  
7. latd 1 Latitude  Direction.  N=North,  S= 
South  
8. lon 12 Longitude, decimal  not less than 6 
places  
9. lond 1 Longitude  Direction.  E=East,  W= 
West  
10. spd 6 Speed  in km/hrs,  Upto  One Decimal  
Value.  
11. wei 6 Weight in Kg.  
12. loc  Location  (Reverse  Geo-coded)  
13. rto  RTO  Code  
14. state   State  Code  
Response  
15. resp  OK/ Error  
 
 SASO STANDARD  SASO/FDS /33192: 2023 
 
54  11.5 Conformity  of Production  - Testing  Parameters  
 
a. SASO or authorized type approval authority which has granted approval may at 
any time verify the conformity of control methods applicable to each production 
unit. The normal frequency of such inspections shall be once every tw o years or as 
mutually agreed between SASO and the manufacturer. The parameters for testing 
shall be as specified  in Table  1 of this section.  
b. The Vehicle Telematics device manufacturers shall get their backend applications  
audited  from  SASO or authorized t ype approval authority every  year from  the date 
of first certification.  The parameters  for auditing  shall  be as specified  in Table  2 of 
this annexure.  
c. SASO or authorized type approval authority shall provide the details of the 
Vehicle Telematics devices  and backend applications certified by them to the by 
uploading the  same  on the respective  backend  systems  or any other  means to know 
the available approved device manufacturers.  
 
Table  1: 
Test for COP  of Vehicle Telematics device incl. VLT and  Emergency  Buttons 
Sl. No. Test Details  (As per AIS-140)  
1. Emergency  button  functionality  (Clause  No. 6.0.2.4 ) 
2. SMS  fall back  (Clause 6.0.6 ) 
3. Table  9A: Functional  Testing  (Sr. No. 1-9, Clause  6.3.1)  
4. Performance  Parametric  Test of Table  9B (Clause  6.3.2,  Sr. No.10)  
5. Protocol  & alerts  verification  as per 
-Clause  No 7.1 and Table  no 7A, 
-Clause  No 7.2 and Table  no 7B, 7C 
-Clause  No 6.0.5 & Table  no 6B 
-OTA  Commands  verification  
6. Ingress  Protection  (IP) Test as per Sr. No. 3 of Table  9B SASO STANDARD  SASO/FDS /33192: 2023 
 
55  Table  2: 
Test Parameters  for Auditing  of Vehicle Telematics device  Manufacturer’s  
Backend  Application/System  
Sl. No. Test Details  
1. Firmware over the air update. Backend application should be able 
to remotely read the existing version number of the firmware via 
an OTA  configuration read command. A new version of the 
firmware should be  pushed over the air. This should be verified by 
reading the new version  number of the new firmware in the device 
via and OTA configuration read  command.  
2. Application availability test to be conducted over a 7 days’ period 
by periodic check of availability randomly or at specified intervals 
in an  automated  or manual  manner.  
3. Test functionality  of application  to allow  user to map & un-map a 
device  to a vehicle.  
4. Test functionality to t rack a vehicle on a map over a period of 8 
hours  given either a device ID or vehicle registration number. The 
device ID  and vehicle  should  be mapped  beforehand.  
5. Test replay  of a vehicles  location  by specifying  a start and end  date 
and time and device  ID or vehicle  registration  number.  The start and 
end date and time should  be from  within  the last 3 months  at date of 
test. In case 3 months  of historical  data is not available,  the Vehicle 
Telematics  manufacturer  can pre- populate  test data for the 
duratio n. 
6. Firmware  binary  should  be made  available  with version  matching  
one in the device as well as binary size & modification timestamp 
and/ or  checksum should match for the binary provided and one 
installed on  device.  
7. Test to confirm  geographical  location of IP addresses,  the device  
communicates with by IP Geolocation for all IPs configured into 
the device to confirm they are in Kingdom of Saudi Arabia. The 
IPs configured should be read  from the firmware configuration via 
configuration read command and  also separately confirmed against 
a list of IPs provided by the device  manufacturer.  
8. Device manufacturer  to provide  a certificate,  statement  or legal 
affidavit  certifying the location of data centre/ cloud hosting region 
in Kingdom of Saudi Arabia for  user,  device  and vehicle  data.  
9. Device manufacturer  to provide a Vulnerability  Analysis and  
Penetration  Testing  report  from  a 3rd party  test agency  authorized  by 
SASO or authorized type approval authority . SASO STANDARD  SASO/FDS /33192: 2023 
 
56   
ANNEXURE  A: 
INFORMATION  TO BE SUBMITTED  FOR  TYPE  APPROVAL  
 
1.0 VEHICLE TELEMATICS D EVICE  SYSTEM  DETAILS  
a. Make  
b. Type  
c. Model  No. 
d. Part No : 
e. Installation  layout: Attach  drawing  showing  location in  vehicle  
1.1 VEHICLE  LOCATION  TRACKING , EMERGENCY  BUTTONS AND ON -
ABOARD WEIGHING SYSTEM  
a. Make  
b. Model  No. 
c. Part No. 
d. OBW T ype (Dynamic / Static)  
e. Connector  used 
f. Connector  used for antennas  
f.1. Main  GSM antenna  
f.2. GPS antenna  
f.3. WLAN  antenna  
1.2 SYSTEM  SOFTWARE  
a. Make  
b. Version  
c. Operating  System  Details  with Version  
1.3 COMMUNICATION PROTOCOL USED  
a. Vehicle to Center  
b. Device to Control Center  
c. Command Set for Configurations  
1.4 DESCRIPTION  OF DEVICE  
1.5 DRAWINGS  
 
1.6 DEVICE / SYSTEM DRAWINGS  
 
1.7 INSTRUCTIONS  MANUAL  SASO STANDARD  SASO/FDS /33192: 2023 
 
57   
ANNEXURE  B: 
CRITERIA  FOR  EXTENSION  OF TYPE  APPROVAL  
ANNEXURE  B: CRITERIA  FOR  EXTENSION  OF TYPE  APPROVAL  
 
B1.0  In case of following  changes,  Functional,  Performance,  Durability  and 
Environmental Tests which are necessary for establishing compliance  
are listed  below  
 
 Changes  in System  Tests  to be conducted  
B1.1  Change  in Make,  Model,  
Type,  accompanied with or 
without a  Part No of Vehicle 
Telemati cs device incl. 
Vehicle  Location  Tracking  
(VLT)  and Vehicle  Health  
Monitoring.  Applicable tests as per Section 6 
and Functional  verification  at 
system  integration  level  or 
component  level  as applicable  
B1.2  Change System in software  
Of ITS  Functional  verification  at system  
integration  level.  
B1.3  Change  in wiring  harness  Wiring harness requirements  
specified  in this standard