 |
eTechSchoolBus is complete school bus security solution. According to a survey, it has been found that parents are extremely worried about their children when they are on the way to school in school bus. The key reason of worrying is increase in crime; rush driving of school bus driver etc. Hence the tracking of school bus is ultimate solution. eTechSchool Bus provides RFID based location updates of your children whether your child has reached school or not. GPS device installed in vehicle gives current location of school bus. eTechSchool Bus product is designed specifically for the real time movement tracking, knowing when students got picked or dropped from the bus. Android Notifications or SMS alerts are sent to parents on the arrival of the bus as well as when a student is picked or dropped.
Now, AIS 140 compliant GPS devices are available !!!
In order to increase and ensure the efficiency of the transport system the government of India as designed an Intelligent Transport System (ITS) under the Automotive Industry Standard -140. The ITS is globally proven to optimize the utilization of existing transport infrastructure to the best of its capacity. This helps in improving the transportation system in terms of efficiency, quality, comfort and safety. AIS 140 is not being implemented across the country. There are various parts of the AIS 140 which encompasses the various aspects of vehicle regulation and maintenance of safety standards. Since the primary aim of designing the system is to increase the vehicle safety there are many subsections to the ITS and these include AIS-140 is the intelligent transport system that is a new addition for automotive industry standards. The intelligent transport system (ITS) is a much needed requirement of the world of vehicles. The vehicles on the road are increasing daily and therefore there is a need of a government guidelines which specify the emergency and safety standards that need to be implied in all kind of public transport systems. These include all kinds of rail, road, air and water transportation modules to be fitted with AIS-140 GPS devices. There are two kinds of AIS-140 requirements in a GPS device – emergency button and vehicle location tracking.
ARAI Certified GPS Tracker Features
ACC detection for ignition status
Be aware of the ignition status whenever you need
Multiple alarms
Instant alert for overspeed, power off, geo-fence
Configure alerts for over-speeding
Send instant email/SMSto notify vehicle`s speeding
Offline data
Offline data stored for 2 days at a frequency of 30 sec
ARAI Certified AIS 140 GPS Tracker - Transync Gps Trackers
DOWNLOAD BROCHURE
GPS+AGPS+LBS positioning
Allow the location to be pinpointed accurately and rapidly
Configurable tracking modes
Location uploded following fixed distance, time interval.
Tracked by: SMS, APP, Web
Reports iocation in real time through different interfaces
Easy installation
Plug-and-track, easy to swap between vehicles
Who needs AIS 140 ?
State Transport Undertakings – Inter-city & Intra city
Private Bus Operators – Inter & Intra city
AIS 140 device for busses
Taxies
Car and Bus Taxi fleet owners or operators (incl. corporate fleets)
Rental taxis operators
Taxi hailing service providers
Self-driven car rental operators
AIS 140 device for school busses
Institutional
Schools, Colleges and institutional (incl. corporate) bus operators
This standard has been prepared by considering inputs received from all stake holders on ITS, mainly –
a. Directions of CMVR-TSC
b. Detailed Specification Document on Vehicle Tracking Devices (dated 4th March 2015, published by MoRTH)
c. Report of Department of Telecom (Telecom Engineering Centre) Automotive
Working Group on M2M enablement in Intelligent Transport System (ITS) This AIS on ITS, has been provisioned for device level approval; including construction and target vehicle level approval. Device level approval is needed to enable retro-fitment of ITS systems on in-use vehicles. This will ensure ITS Backend Control Centre infrastructure already presents with the STUs can be more fully utilized and make the investment in the Backend Control Centre infrastructure more viable.
As per the direction of CMVR-TSC which needed the Communication Protocol and Backend Control Centre requirement for tracking and handling the alerts to be detailed, the same has been addressed in Section 6 & 7, as detailed below.
The devices would transmit data to the Backend Control Centre using 2G/3G/4G wireless connectivity (with SMS fall back) as per the protocol provided in respective sections (Section 6). The data from the devices would travel over the wireless telecom service provider network and finally get delivered at the Backend Control Centre. The detail about Device to Backend Communication Mechanism is mentioned in Section 7. BIS and AIS both have panels which are formulating standards on ITS. It is our belief that taking the AIS route for the 1st implementation would give the faster time for adoption. Experts in the BIS panel and in DIMTS who are working on these subjects have been co-opted and invited to work in the AIS panel to make the AIS as robust as possible. Once implemented and all implementation problems in this emerging technology have been eliminated, BIS standard can be made with further inclusions if any resulting from consultations with the wider stakeholder community. Because of these reasons, we recommend the AIS route for regulation creation and first implementation.
One of the major concerns which has been raised during the panel meetings is on the issue of privacy encroachments by ITS systems. Some overseas member countries of the 1958 agreement have been continuously emphasizing in WP29 forums that the regulated ITS system must not encroach on privacy. Towards this, the panel has submitted a document titled ‘Data Privacy in Transportation ITS’ To help the system developers deal with these issues. Further, system developer can also take guidance
from ‘IS/ISO/TR 12859: 2009 – Intelligent Transport Systems — System Architecture — Privacy Aspects in ITS Standards and Systems’ while developing their systems to meet the requirements of this standard. The Panel and the Automotive Industry
Standards Committee (AISC) responsible for preparation of this standard are given in Annexure-D and Annexure -E respectively.
3.1.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 be capable for operating in L and/or S band and include support for NAVIC/IRNSS (Indian Regional Navigation Satellite System) for devices installed on or after 1st April, 2018.
b. The Device shall support GAGAN, the Indian SBAS (Satellite Based Augmentation System)
c. Device shall have a position accuracy of minimum 2.5 m CEP or 6 m2DRMS
d. Device shall have an acquisition sensitivity of minimum (-) 148 dBm
e. Device shall have an tracking sensitivity of minimum (-) 165 dBm
f. Device shall have an internal antenna; however if in case of Integrated systems with vehicle / aftermarket OEM approved kits if the fitment location prevents the internal antenna from functioning, then external antenna shall be provided.
3.1.1.2 Device shall support standard minimum I/Os as mentioned: 4 Digital, 2 Analogue and 1 Serial Communication (e.g. RS232) for interfacing external systems (E.g. Digital input for Emergency request button interfacing).
3.1.1.3 Device shall be capable of transmitting data to Backend Control Server (Government authorized server) via Wide Area (Mobile) Communications network (GSM/GPRS) as per Communication Protocol in Section 4.
3.1.1.4 Device shall be capable of transmitting Position, Velocity and Time (PVT data) along with heading (direction of travel) to a Backend Control Server (Government authorized server) at configurable frequency as per Communication Protocol of Section 4. The fixed frequency shall be user configurable, minimum frequency 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 4.
3.1.1.5 Device shall be capable of transmitting 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.
3.1.1.6 On pressing of Emergency button, the system implementing VLT function shall send emergency Alert (Alert ID 10 as mentioned in Subsection
4.2.1 of Communication Protocol Section 4) to the configured IP address(s) as per the Communication Protocol mentioned in Section 4. In the absence of GPRS network, the emergency alert shall be sent as SMS message along with vehicle location data to configured control center number(s). The SMS shall consist parameters as given in Sub-section
3.1.1.7 Device shall have an internal back-up battery to support 4 hours of normal operations (to be tested for positional record transmission at a frequency of 60 sec)
3.1.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 4.2 (Alert ID 3 to 12) of Section 4.
3.1.1.9 Device shall support over the air software and configuration update.
3.1.1.10 Device shall support basic standard configuration (Mobile communications network settings, Backend Control Server (Government authorized server) details, data frequencies, alert thresholds etc.) as per configuration specification defined in Section 4.
3.1.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 unavailability and transmit the data when the connection resumes in last in first out (LIFO) manner. The live data shall be given higher priority for
transmission than back log (stored data) at any point in time.
3.1.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 overwritten by any person. The unique identifier may be Vehicle Identification number or IMEI (International Mobile Station Equipment Identity) Number.
3.1.1.13 Device shall store/write the registration number of the vehicle in the internal nonvolatile memory.
3.1.1.14 Device shall have an Embedded SIM.
3.1.1.15 Device shall be designed to operate between 8VDC and 32VDC using vehicle battery input voltage range 12 /24Volts.
3.1.1.16 Device shall have a sleep mode current ≤ 20 mA (If the function is implemented in a dedicated system/device).
3.1.1.17 Device shall support any operational GNSS system with 12 (minimum)acquisition channels.
3.1.1.18 The Device shall support:
• Location on GPRS/SMS
• Non-volatile memory to store min 40,000 positional log
• Configurable backup SMS facility in case of GPRS failure
• Capability to send serving and adjacent cell ID as well as network measurement report (NMR)
Visitors reached here while searching for AIS 140, arai approved gps tracker, gps tracker india, gps tracking system
How eTechSchoolBus works?
Download GPS + RFID Presentation
Download Brochure
A smart card (nametag) is provided to each student. Smart Card contains student information. At the entrance of the bus, RFID card reader will be provided (Internally its connected with GPS Device). Students need to flash the smart card (nametag),
An android notification and/or sms will be sent in each of the above cases. Parents can check exact location of bus on online software of eTechSchool Bus or via eTechTracker/eTechSchool Android App. Individual UserID and password will be provided to parents. Parents will be able to check the bus location of their child only. User Id and password will also be provided to school administrators, so that they will be able to check location of all buses.
Features:
Live tracking ie. the system provides real-time location data that displays the movement of the bus along with the date and time stamp, direction, speed and number of students in the bus on a map.
For Parents: Track the child getting in/out of the bus and entering or leaving the School.
Many more alerts can be configured with the system in cases such as:
