vdms - mtsfb · 2020. 6. 22. · figure 5.1: vdms hardware system in figure 5.1 above shows the...
Post on 27-Jan-2021
1 Views
Preview:
TRANSCRIPT
-
Page 1 of 49
VDMS VEHICLE DIAGNOSTIC MONITORING SYSTEM
DATE:
10th July 2017
PREPARED BY:
Adila Alias
Imran Khairuddin
Techcapital Resources Sdn. Bhd.
-
Page 2 of 49
On Behalf of MALAYSIAN TECHNICAL STANDARDS FORUM BHD
TABLE OF CONTENTS
1.0 Target Groups And Benefits 3
2.0 Introduction/Background 4
3.0 Objectives 6
4.0 Scope Of Works 7
5.0 Methodology/ Approach 8
5.1 SYSTEM HARDWARE COMPONENTS 9 5.1.1 SCANIA’S CAN BUS 11 5.1.2 MCP2515 CONTROLLER 13 5.1.3 ARM BASED NANOPC 14 5.1.4 SMART POWER SUPPLY 16 5.1.5 3G COMMUNICATION 17 5.2 SYSTEM SOFTWARE COMPONENTS 18 5.3 WEBSITE DEVELOPMENT 19
6.0 Progress 21
7.0 Result Analysis 23
8.0 Total Cost Project 26
9.0 Overall Project Schedule/ Actions 29
10.0 Conclusion 40
11.0 References 41
12.0 Appendix 42
-
Page 3 of 49
1.0 Target Groups and Benefits
The main target group of this technology is the public transportation provider such
as buses and taxis whereby close tracking and monitoring of their vehicles are
vital for observing service performances and efficiencies.
The major benefits of adopting this technology include:
• Improving service performances and efficiencies by closely monitoring the
vehicles activities
• Improving safety of the service by monitoring drivers’ driving practice while
at the same time ensuring the drivers’ good work disciplines
• Helping the transportation service provider to examine daily fuel
consumption of the vehicle thus improvise the necessaries to reduce the cost
and fuel consumption
• Supporting “green technology” by monitoring carbon emission of the vehicle;
the vehicle to be ensured to be under carbon emission limit for the respective
cities it travels.
• Helping the transportation service provider to obtain health status of the
vehicle at any given time and to alert them if there is any case of vehicle
emergencies.
-
Page 4 of 49
2.0 Introduction/Background
The current rapid development in the urban cities calls for more people moving
from places to places for work, school and simply making a living. And more
people are using public transportations today than before as their daily commute
primarily because it is easy, cheap, and fast. Therefore, public transportation
providers such as bus and taxi providers have to step up their games by making
their services more favourable by the customers and more efficient to compete
with other public transportation providers. This is where our technology comes in to
help these providers advance in their games.
Our Vehicle Diagnostic & Monitoring System (VDMS) provides a connected,
data-rich travel environment. Our device helps capture real-time data from the
vehicles (buses, taxis and trucks) to give information on the vehicle status to the
public transportation providers. This way, the service providers can monitor their
vehicles location and activity, the health status of the vehicles, the fuel
consumption and carbon emission of their vehicles among other features.
-
Page 5 of 49
Figure 2.1: VDMS system overall structure
Our device works by installing the VDMS hardware system equipped
MCP2515 controller, ARM Based NanoPC, ECU Communication Interface, Smart
Power Supply, GPS Module and 3G communication to the vehicle’s Engine Control
Unit (ECU) thus giving instant access to the vehicle status. This hardware system
is then connected to a cloud data hub through the wireless connection. The user
can then access this vehicle status information through a specially created website
portal. The visual interpretation of the overall architecture of VDMS system can be
seen in Figure 2.1 above.
-
Page 6 of 49
3.0 Objectives
The main objectives of this technology implementation are:
• To monitor the speed, location and route of the bus via GPS module
• To improve service performance and efficiency by monitoring bus activity
(location and time of start and stop)
• To observe for environmental friendliness by monitoring fuel consumption,
𝐶𝑂2 emission of the bus among others
• To provide accurate and reliable real-time information on bus activity to
traffic management officer and bus service provider through website portal.
-
Page 7 of 49
4.0 Scope of work
The scope of work for this project is as the following:
Phase 1:
1. Project Planning
Phase 2:
1. Hardware Implementation on sample bus: connecting the hardware to the
vehicle’s ECU, collecting sample data from the VDMS device
2. Submission of purchase orders to DTS
3. VDMS device installation and data integrity acceptance by DTS
Phase 3:
1. Data collection study: to ensure values obtained from the VDMS device
are correct and are in designated range.
2. Submission of final project report and data sample for approval to DTS
-
Page 8 of 49
5.0 Methodology/Approach
There are four major steps for which VDMS works. Firstly, the VDMS hardware is
developed installed into the vehicle. It comprises of MCP2515 controller, ARM
Based NanoPC, ECU Communication Interface, Smart Power Supply, GPS
Module and 3G communication. The VDMS hardware is directly connected to the
vehicle’s Engine Control Unit (ECU) thus giving instant access to the vehicle
status.
The second step is to connect the vehicle data to the VDMS device to be
collected, interpreted into user readable information.
The third step, the processed information is then channeled to the cloud
data hub by using 3G wireless connection. Through this cloud data hub, the user
can access the status of the vehicle from any location and time with the simple
help of internet connection.
The fourth step is to visualize the data. The previously analyzed data is
presented in a user-friendly dashboard.
The few following pages presented more detailed technical descriptions on
how all the above four major steps in creating VDMS are performed.
-
Page 9 of 49
5.1 System Hardware Components
Figure 5.1: VDMS hardware system
In Figure 5.1 above shows the VDMS hardware system. The VDMS system
is enclosed in a black box of size 13.3 cm (length) by 10.6cm (width) and
7.0 cm (height). The VDMS is connected to the ECU of the bus through the
C471 Connector in Figure 5.2 which is located under the central electric
unit in the instrument panel of the bus via a via a round 2 position socket, of
part No. 1-1719434-1 from TE connectivity in Figure 5.3. The main
components inside the VDMS are the ARM Based NanoPC, ECU
Communication Interface, Smart Power Supply, 3G communication and
MCP2515 controller. The functions and descriptions of these items will be
individually explained later in the next paragraphs.
-
Page 10 of 49
Figure 5.2: The connection point to the ECU of the bus at C471 Connector.
Figure 5.3: The connection to C471 Connector by using1-1719434-1 Socket.
-
Page 11 of 49
Once the VDMS is connected to the ECU, the VDMS system has to extract
data from the ECU to obtain information about the bus status. The SCANIA
bus (the bus model that we used for this project) like every other modern
vehicle has a form of communication system to connect and communicate
the different components of the vehicle. The communication system used by
SCANIA Bus is called CAN Bus. Then, another standard system exists to
manage the CAN Bus for its data management and monitoring called Fleet
Management System (FMS). We collect vehicle data from the CAN Bus,
interpret and analyzing them into human readable information and display
this information on the dashboard.
5.1.1 SCANIA’S CAN Bus
Controller Area Network (CAN) bus is a rigid digital bus (communication
system) which is designed to communicate many computers/micro-
controllers together without the need of host computer. It is hardware and
software (protocol) designed to connect many controlling units together
such as engine control unit, auto transmission, airbags, ABS, power
steering, advance audio systems and air conditioner. For example, if the
driver changes the gear to a reverse gear position, the CAN Bus will send
signals to the rear camera, brake light and rear sensor to be activated to aid
in the car reversing process. Certainly, all these items cannot communicate
among themselves directly without a central communicator other than hard
wired method which takes a lot of effort and energies.
-
Page 12 of 49
Figure 5.4: An example of how CAN bus connection work as a communicator between multiplex wiring system of different components in a vehicle.
Since the data collected by the CAN Bus comprises of many parameters for
example the total fuel used, engine coolant temperature and engine speed,
all these parameters are identified through their unique identifiers and
filtered to what required for VDMS. The unique identifiers are standardized
across CAN Buses using FMS. Below is the sample of SCANIA CAN Bus
parameters and their respective identifiers:
Table 5.1: Sample of CAN Bus parameters and Their Respective Identifiers
-
Page 13 of 49
5.1.2 MCP2515 Controller
Figure 5.5: MCP2515 Controller
Figure 5.6: MCP2515 Controller to ARM Block Diagram
The CAN Bus data collected by SCANIA bus is not readily understandable
by our ARM Based NanoPC. MCP 2515 controller is used to convert the
CAN Bus Scania (SAE J1939) Protocol to the standard SPI protocol. This
way, the CAN Bus data can then be processed by our ARM Based NanoPC
processor into a user readable data.
However, the data for 𝐶𝑂2 emission is not displayed in the CAN Bus data.
The 𝐶𝑂2 emission of the vehicle is calculated based on GHG Protocol-
Mobile Guide (03/21/05)v1.3 by using the preferred fuel-based approach
(1).
-
Page 14 of 49
The 𝐶𝑂2 emission is calculated by using the following Equation 1:
𝐶𝑂2(𝑘𝑔) = 𝑓𝑢𝑒𝑙 𝑢𝑠𝑒𝑑(𝑙𝑖𝑡𝑟𝑒) 𝑥 ℎ𝑒𝑎𝑡𝑖𝑛𝑔 𝑣𝑎𝑙𝑢𝑒 (𝐺𝐽
𝑙𝑖𝑡𝑟𝑒) 𝑥 𝑒𝑚𝑖𝑠𝑠𝑖𝑜𝑛 𝑓𝑎𝑐𝑡𝑜𝑟 (
kg CO2GJ
)
Fuel used = readily obtained from CAN bus data (litre)
Heating value = 0.0371 GJ/litre
Emission factor= 74.01 kg 𝑪𝑶𝟐/GJ
5.1.3 ARM Based NanoPC
Figure 5.7: ARM Based NanoPC
The ARM based NanoPC is where the data processing from the CAN bus or
the vehicle actually takes place. The java program written to extract and
calculate the CAN bus data is embedded in the Samsung Cortex-A9 Quad-
core Exynos4412, 1.5GHz. The detailed description of the ARM based
NanoPC is as below:
-
Page 15 of 49
Figure 5.8: ARM Based NanoPC with labeling
Specifications:
• Samsung Cortex-A9 Quad-core Exynos4412, 1.5GHz
• RAM: 1GB DDR3 RAM, 32bit data bus
• Flash: 8GB eMMC Flash
• HDMI output resolution: 1080P (1920x1080)
• LCD: TFT LCD interface
• USB OTG: One MicroUSB interface
• USB Host: two USB Host 2.0 interface
• Ethernet: 100Mhz Ethernet, RJ45
• SD Card slot
• Audio In: One MIC in box
• One Audio Out in jack
• IR: one Infrared Receiver
• Two USER KEY
• Two User LED
• Six Digital sensor I/O
• CMOS CAMERA Interface
• MIPI interface: Support HD Camera
• GPIO1-34Pin: UARTx2, SPIx1, I2Cx1
• GPIOx13GPIO2-16Pin: UARTx1, GPIOx2, SDIOx1, USB Host2.0x1
• Android 4.2.2 & 5.0
60 mm
100 mm
-
Page 16 of 49
5.1. 4 Smart Power Supply
Figure 5.9: Smart Power Supply
Another essential part of the device is a power regulator called Smart Power
Supply. This component not only helps to protect the device from over
voltage and short circuit, but also supervise the status of the hardware and
the program in order to reset the system in case of crash or connectivity
lost. Below is the description of this integrated board:
▪ Wide range voltage input
▪ Reverse polarity protection
▪ Over voltage protection
▪ Short circuit protection
▪ Independent watchdog timer to detect the software is not running to
recycle the power to restart the unit and remove fault.
▪ ECU communication interface
▪ RS232 interface
▪ Surge protection
▪ Status indicators
▪ Power on
▪ ECU connection
▪ GPS status
▪ 3G status
-
Page 17 of 49
▪ Software status
▪ LCD connector (debugging purpose)
▪ Capacitive touch screen
5.1.5 3G Communication
Figure 5.10: 3G Communication Module
The data connection from the VDMS to the virtual dashboard/website portal
is done through a 3G connection. Celcom telecommunication simcard is
used to allow for this communication through GSM based connection.
-
Page 18 of 49
5.2.1 System Software Components
A java program is written to extract the information from the CAN bus
through the MCP2515 controller, to do data conversions and calculations,
and to channel the processed information to our cloud data hub. The java
program is written in Android Studio by using Android Open Source
Project (AOSP) as its operating system. Below is the screen shot of the
java program written:
Figure 5.11: A screenshot of the java program for ARM Based NanoPC
-
Page 19 of 49
5.3.1 Website Development
The information is displayed to the user through a specially designed dashboard or
website portal. This website is designed in html environment. To use this portal, the user
will log into the website on the top left side of the portal and select their desired bus. The
portal will then load the status of the vehicle containing the vehicle RPM meter, speed
meter, engine temperature and fuel used among others.
Below is the screenshot of the html codes written:
Figure 5.12: A screenshot of the html codes
-
Page 20 of 49
Below is the login interface of the dashboard:
Figure 5.13: Dashboard login interface
Below is the design of the VDMS dashboard:
Figure 5.14: Display dashboard
-
Page 21 of 49
6.0 Progress Status
As of July 9 ,2017, we managed to install one VDMS system onto one double-
decker SCANIA bus as provided by DTS.
STEP 1
The sample bus used to
install and test VDMS device
STEP 2
Cable connection to the bus
ECU is made for power
source and CAN Bus.
STEP 3
Cable is made to pass under
the bus and then into the
compartment beside the first
floor’s dashboard.
Figure 6.1: DTS Bus Figure 6.2: ECU Bus Figure 6.3: Cables installation
Figure 6.4: Bus dashboard
-
Page 22 of 49
STEP 4
Wiring works in progress to
connect the cable from the
bus ECU to the second floor
of the bus
STEP 5
The VDMS is installed into
this front compartment on
the second floor of the bus
STEP 7
VDMS completes with wiring to
the ECU installed.
Figure 11.0: Sequence of VMDS system installation onto SCANIA Bus.
Figure 6.4: Drilling holes Figure 6.4: VDMS Compartment Figure 6.4: VDMS Installation
-
Page 23 of 49
7.0 Result Analysis
In Table 7.1 shows the data collected from VDMS for Period July 01,2017 – July 09,
2017. The data is extracted from the VDMS dashboard at the end of the day for
every date displayed here. The location column displayed the last GPS location of
the bus BLG7808 at time 23:59:59 with the first number showing the longitude and
the second number showing the latitude position of the bus.
The tachometer reading columns shows the total distance traveled by the bus since
its first day of operation where the reading added up for every traveled day. The
remaining columns of travel(km), max speed (km/hr), max temperature (°C), fuel
consumption for the day(liter), fuel counter (liter),and 𝐶𝑂2 emission (kg) describe the
bus’ engine activity for the day. For instance, On July 2,2017, the bus traveled a
distance of 108 km with max speed of 108 km/hr and max. engine temperature of
104 °C. For that day, the bus used up 370 litre of diesel fuel to give total fuel counter
of 268987 litre of diesel fuel used. Also, for that amount of diesel fuel and engine
activity, the bus had emitted 1014.56 kg of 𝐶𝑂2 emission.
-
Page 24 of 49
Table 7.1: Table of Data Collected from VDMS for Period July 01, 2017 – July 09, 2017
No Date Time location Tachometer
(Km)
Travel
(km)
Max
Speed
(Km/hr)
Max Temp.
(°C)
Fuel
Consumptio
n for the day
(litre)
Fuel
Counter
(litre)
Emission
(Kg)
1 Saturday,
July 01, 2017
23:59:59 2.856931686401367,
101.75530242919922
668135.9375 0.5 0 54 0.5 268617.5 1.37
2 Sunday,
July 02, 2017
23:59:59 4.829001426696777,
103.41488647460938
669012.8125 876.88 108 104 369.5 268987 1014.56
3 Monday,
July 03, 2017
23:59:59 2.920471668243408,
101.65157318115234
669540.1875 527.38 108 104 225 269212 617.80
4 Tuesday,
July 04, 2017
23:59:59 2.970950126647949,
101.5840072631836
669820.8125 280.63 108 104 139 269351 381.66
5 Wednesday,
July 05, 2017
23:59:59 2.920754909515381,
101.65181732177734
669820.8125 0 108 104 1 269352 2.75
6 Thursday, July
6, 2017
23:59:59 2.9204182624816895,
101.65215301513672
670126.75 306 108 104 158 269510 433.84
7 Friday, July 7,
2017
23:59:59 2.920330047607422,
101.65203857421875
670299.5 173 108 104 92 269602 252.61
8 Saturday, July
8, 2017
23:59:59 2.9204649925231934,
101.65204620361328
670310.8125 11 108 104 9 269611 24.71
9 Sunday, July
9, 2017
23:59:59 2.920316696166992,
101.65206146240234
670578.25 268 108 104 143.5 269754.5 394.02
2CO
-
Page 25 of 49
Figure 7.1:User’s VDMS Dashboard Interface .
Figure 7.1 above shows the snapshot of the VDMS dashboard in use. Through this
dashboard, the user can access the current information of the bus by logging in into the
website and entering the bus plate number in the top row. The portal will then load the
status of the vehicle containing the vehicle RPM meter, speed meter, engine temperature
and fuel used among others. For example, the user can see that the speed of the bus
BLG7808 at 23:59:59 is at 88 km/hr and that the engine temperature at that time is 85°
-
Page 26 of 49
8.0 TOTAL COST
The purchase invoices for the system are attached in the Appendix.
Table 8.1: Table of Purchases for VDMS system with grand total of RM 7286.43
Date of purchase Supplier Items Detail Unit Total Price
12/9/2016
Guangzhou FriendlyElec Technology Co., Limited
NanoPi S2+7" capcacitive LCD Combo 5 RM 1,215.50
1/21/2015
Guangzhou FriendlyARM Computer Technology Co., Limited
GStar GPS with the antenna and flat cable 1 RM 162.45
10/27/2015 Mouser Electronics, Inc.
Schurter Surface Mount Fuses, MFG Part No:3402.0014.11 2 RM 5.94
10/27/2015 Mouser Electronics, Inc.
Schurter Surface Mount Fuses, MFG Part No:3402.0016.11 2 RM 5.94
10/27/2015 Mouser Electronics, Inc.
TE Connectivity Headers & Wire Hou, MFG Part No:640445-2 2 RM 1.58
10/27/2015 Mouser Electronics, Inc.
TE Connectivity Headers & Wire Hou, MFG Part No:3-643817-2 2 RM 3.56
10/27/2015 Mouser Electronics, Inc.
Molex Headers & Wire Housings, MFG Part No:46992-0610 10 RM 29.00
10/27/2015 Mouser Electronics, Inc.
Molex Headers & Wire Housings, MFG Part No:39-00-0039 60 RM 24.06
10/27/2015 Mouser Electronics, Inc.
TE Connectivity Headers & Wire Hou, MFG Part No:640456-9 2 RM 5.34
10/27/2015 Mouser Electronics, Inc.
TE Connectivity Headers & Wire Hou, MFG Part No:3-643813-9 2 RM 14.76
10/27/2015 Mouser Electronics, Inc.
FCI Headers & Wire Housings, MFG Part No:89361-130LF 2 RM 13.86
10/27/2015 Mouser Electronics, Inc.
TE Connectivity Headers & Wire Hou, MFG Part No:3-643813-6 2 RM 11.98
10/27/2015 Mouser Electronics, Inc.
Harwin Headers & Wire Housings, MFG Part No:M22-3070200 3 RM 1.49
10/27/2015 Mouser Electronics, Inc.
Harwin Headers & Wire Housings, MFG Part No:M22-2200246 3 RM 3.12
10/27/2015 Mouser Electronics, Inc.
Harwin Standoffs & Spacers, MFG Part No:R30-3000402 10 RM 20.10
10/27/2015 Mouser Electronics, Inc.
Harwin Standoffs & Spacers, MFG Part No:R30-1011302 2 RM 5.54
10/27/2015 Mouser Electronics, Inc.
RAF Electronic Hardware Screws & F, MFG Part No:M3473-SS 2 RM 20.70
10/27/2015 Mouser Electronics, Inc.
TE Connectivity Automotive Connect, MFG Part No:8-968971-1 12 RM 77.28
10/27/2015 Mouser Electronics, Inc.
TE Connectivity Automotive Connect, MFG Part No:1-968851-1 (Cut Strip) 100 RM 91.10
10/27/2015 Mouser Electronics, Inc.
Wurth Ferrite Clamp On Cores, MFG Part No:74271142S 4 RM 88.32
10/12/2016
Lian Hup Electronics Cable and connectors RM 256.00
-
Page 27 of 49
Date of purchase Supplier Items Detail Unit Total Price
10/13/2016
Lian Hup Electronics Wire RM 39.00
10/12/2016 Perniagaan Elektrik WinKong Sdn. Bhd. 12" black cable 1 RM 10.00
10/12/2016 Perniagaan Elektrik WinKong Sdn. Bhd. 6" black cable 1 RM 4.00
10/12/2016 Perniagaan Elektrik WinKong Sdn. Bhd. 8mm black flexible conduct 1 RM 190.00
10/12/2016
Lian Hup Electronics And Electric Sdn Bhd. 4 Core Scrren Cable 1 RM 195.00
10/12/2016
Lian Hup Electronics And Electric Sdn Bhd. Stereo Cable 5 RM 29.00
10/12/2016
Lian Hup Electronics And Electric Sdn Bhd. 18650 battery Charger 1 RM 32.00
10/12/2016
Lian Hup Electronics And Electric Sdn Bhd. 2Core Wire 1 RM 52.00
10/12/2016
Lian Hup Electronics And Electric Sdn Bhd. Stereo jack 2 RM 56.00
10/13/2016
Lian Hup Electronics And Electric Sdn Bhd.
Car Fuse Holder 10 RM 30.00
10/13/2016
Lian Hup Electronics And Electric Sdn Bhd. Cable Lug 30 RM 9.00
10/27/2015 Silvtronics Sdn Bhd PCB Size : 3.94" x 2.09" 13 RM 595.00
10/6/2015
Lian Hup Electronics And Electric Sdn Bhd.
5 Way Connector (Black) 10 RM 10.00
10/6/2015
Lian Hup Electronics And Electric Sdn Bhd.
D89PIN Female (T) 10 RM 13.00
10/6/2015
Lian Hup Electronics And Electric Sdn Bhd.
D89PIN Cover(Metal)(T) 10 RM 65.00
10/6/2015
Lian Hup Electronics And Electric Sdn Bhd.
PCB Stand SS10X3 210 RM 147.00
10/6/2015
Lian Hup Electronics And Electric Sdn Bhd.
Screen Cable 40 RM 100.00
10/6/2015
Lian Hup Electronics And Electric Sdn Bhd.
MK-4-2370 Cable 10 RM 15.00
10/6/2015
Lincoln Communication Sdn Bhd
GSM Antenna 10 RM 750.00
10/6/2015 Sigma Components Sdn Bhd SH Header 10 RM 20.00
10/6/2015 Sigma Components Sdn Bhd JD 2x17 20 RM 36.00
10/6/2015 Sigma Components Sdn Bhd LED (Blue & Orange) 230 RM 230.00
10/6/2015 Sigma Components Sdn Bhd LP-IR-02 10 RM 18.00
-
Page 28 of 49
10/6/2015 Sigma Components Sdn Bhd SA Object 10 RM 2.00
10/6/2015 Sigma Components Sdn Bhd 525/6 Holder 10 RM 10.00
10/6/2015 Sigma Components Sdn Bhd LED Holder 40 RM 12.00
10/6/2015 Sigma Components Sdn Bhd USB Cable 10 RM 8.00
10/6/2015 Sigma Components Sdn Bhd 2P Housing 10 RM 2.00
10/6/2015 Sigma Components Sdn Bhd 3P Housing 10 RM 2.50
10/6/2015 Perniagaan Elektrik WinKong Sdn. Bhd.
Conduct PVC RM 95.00
14.02.2017 Element14 Can bus analyzer tool 1 RM 533.06
11.04.2017 Mouser Automotive Connectors 10 RM 45.80
11.04.2017 Mouser RS-232 Interface IC 10 RM 50.73
14.04.2017 Mouser Connectors 4 POS DIA 2.5 SOCKET 5 RM 64.89
04.05.2017 Mouser VERT Holder (coin cell battery holder) 5 RM 21.51
24.05.2017 Friendlyarm 3G PCB Module 1 RM 455.82
09.05.2017 Digi Simcard 1 RM 53.00
22.05.2017 Celcom Celcom Simcard Billing (2016) 1 RM 804.50
2015 Teakway Industrial Sdn Bhd Enclosure 5 RM 315
GRAND TOTAL RM 7286.43
-
Page 29 of 49
9.0 Overall Project Schedule
Year Date Item Discussion/Action
Apr-15
21st April 2015
IOT Meeting on
demonstrator
1. First Meeting TCS with MCMC to introduce
TCS project "VDMS"
2. Explained the benefits and objectives of
VDMS
27th April 2015
Joint robotics
project
TCS to submit a proposal paper to MCMC on
the potential collaboration by 30th April 2015:
VDMS POC on Pos Malaysia
30th April 2015
First VDMS
proposal
Submitted the first proposal to MCMC
May-15
19th May 2015
Updated
VDMS
Proposal
TCS resubmitted updated VDMS proposal
Jun-15
8th June 2015
Breakfast
Meeting:
MCMC-TCS
POC
To discuss and formalise the MCMC-TCS POC
on:
1. VDMS on Pos Malaysia
9th June 2015
Guidelines for
VDMS POC
The POC proposal should cover the following
details:
Executive summary (key components of entire
project, brief of problem solved, cost, schedule)
- Project proposal (as detailed as possible)
- Objective
- Benefits (to MCMC, industry, community, etc)
- Impact to the environment
- Project costing and CAPEX estimation
- Total cost of ownership (TCO)
- Origin of materials and services
- Implementation schedule
Key focus area for the connected vehicles
proposal shall be on the Green ICT assessment,
measurements and related study.
-
Page 30 of 49
18th June 2015
Discussion on
RoadMe with
MCMC and
Cyberview
Agenda:
1. Presentation by TCS Sdn Bhd on RoadMe
Solution
2. Discussion on potential collaboration – POC
with Cyberview’s fleet management and
MCMC’s vehicles.
Conclusion:
Cyberview is insterested and recommend to do
the pilot project with DTS
24th June 2015
VDMS
discussion on
Installation of
pilot on DTS
buses
Presented to DTS on VDMS
DTS Technical team showed to TCS the ECU
29th June 2015
VDMS
Timeline
TCS submitted latest milestone to MCMC
Jul-15
30th July 2015
VDMS Slide
TCS submitted VDMS presentation slide to
Cyberview
Aug-15
6th August 2015
VDMS
Proposal
TCS submitted VDMS proposal to Cyberview
7th August 2015
VDMSProgress
update
1. On 3rd August 2015, TCS had a meeting with
Ms Athirah, Cyberview and few from DTS at
DTS office, Cyberjaya.
2. We have agreed on one(1)-year pilot program
with selected of 10 buses;
-9 Bus (Engine- Scania K380)
-1 Bus (Engine- Hino)
3. TCS have emailed VDMS proposal as
requested by Ms Athirah, Cyberview with a
proposed implementation schedule which will be
started on the 10th September 2015.
Sep-15
8th September 2015
MCMC request
TCS to submit
proposal to
MTSFB
MCMC has asked TCS to submit VDMS
proposal to MTSFB, In the proposal, TCS has
reached an agreement with MCMC, Cyberview
and DTS to implement "Connected Vehicle" Pilot
Project in DTS fleet of buses.
-
Page 31 of 49
Oct-15
15th October 2015
VDMS meeting
with MTSFB
Agenda
a) Introduction
b) Project briefing
c) Discussion
d) Way forward
23rd October 2015
VDMS
proposal to
MTSFB
TCS submitted to new updated proposal based
on MTSFB template
Nov-15
18th November 2015
GICT WG
Meeting
New project proposal for roadme and presented
to working group under MTSFB and MCMC
27th November 2015
VDMS
proposal to
MTSFB
TCS revised proposal and request to have
another presentation on 2nd or 4th Dec
Dec-15
4th December 2015
GICT WG
Meeting
MTSFB
Standard form
1. Meeting Postponed
2. MTSFB send a standard proposal form to
TCS and to be presented for the next meeting
7th December 2015
GICT WG
Meeting
Revised presentation by TCS on VDMS
proposal
10th December 2015
VDMS
proposal to
MTSFB
TCS submitted revised proposal based on GICT
WG requirements
22nd December 2015
GICT WG
Meeting
Meeting postponed
29th December 2015
GICT WG
Meeting
Discuss on VDMS proposal, to be added on
guidelines of the data extracted
TCS resubmitted to MTSFB:
1. Inclusion of maintenance data to keep track of
proper vehicle maintenance.
2. Carbon footprint data
3. Estimated saving of emission through good
driving behavior/pattern
4. Gamification in methodology.
5. Collaboration with MIROS
6. Comparison between VDMS and OBD2
7. Revised costing based on latest requirement
for software visualization and gamification
platform.
-
Page 32 of 49
Jan-16
4th January 2016
VDMS
proposal to
MTSFB
TCS to adjust 4th revised proposal based on
GICT WG requirements & format (Milestone &
Gantt chart)
13th January 2016
GICT WG
Meeting
Revised presentation by TCS on VDMS
proposal and update on:
1. How the data is being transmitted to the
device (for the gamification)? The revised
proposal didn’t mention about such transmission
process. Need your team to elaborate it.
2. What are the analytics formula that are
going to be used?
3. What will be the proposed suggestions on
how MTSFB (GICT WG in this case) to promote
this idea and etc.
4. In the timeline and milestone segment,
there is no information in regard to Alpha stage,
Beta stage and trial stage. Please include this as
well.
5. Revised on the project cost as initially cost
cannot be exceeding more than RM 50K
Feb-16
1st February 2016
VDMS
proposal to
MTSFB
1. TCS resubmitted updated final VDMS
proposal submission
2. MTSFB will prepare the LoA for the Special
Committee's endorsement and MCMC's
approval
-
Page 33 of 49
23rd February 2016
Discussion
TCS with
Cyberview on
VDMS
1. Please resend me the latest VDMS
Proposal together with the WIP schedule and
Reporting attachment
2. TCS to sort out and seek clarity on who
would sign of for the accountability of vehicle
damage risks in association to the pilot project
3. TCS to send CSB questionnaire to
ascertain user requirement for dashboard
4. The RoadMe project will contain 2 parts,
which is the installation of the roadme units and
dashboard
5. Process for sign off and execution of pilot
to include the following documentation :
a. Letter of Undertaking
b. Letter of Collaboration
c. Copy of LOA from MCMC
d. Project Brief
e. VDMS Proposal
6. We target to meet again on 1st week of
March for signing off on the execution of this
project.
TCS submitted latest VDMS Proposal and
Milestones
WIP to be postponed to 3rd March 2016
-
Page 34 of 49
Mar-16
3rd March 2016
TechCapital
WIP with
Cyberview
Discuss on work progress:
a. Proposal
b. Milestones
c. User Requirements
1. VDMS Scope > to add scoping info into
column that matches scope as mechanics
required for fulfilment of objective and targeted
benefits
2. Requirements for Dashboard > Requirements
to be fulfilling of data required for meeting
objective targets, as per discussion, dashboard
requirement needs to be enhanced to show
historical comparison, line graph charts, area
hotspot when doing data analysis
3. ATA to look into acquiring assistance of data
scientists to compare data
4. ATA & Eugene to further elaborate roles of
each partner in collaboration, including 2
professors from UPM > on safety and UM > on
green calculations
5. Excel of ROADME SCOPE to be uploaded
online on google sheet for collaborative updating
TCS submitted the User Requirements for the
Dashboard which Cyberview to fill
Cyberview sent an email for TCS; Proposal info
to be formated into project brief
WIP to be postponed to 10th March 2016
7th March 2016
Acceptance of
LOA from
MCMC
10th March 2016
TechCapital
WIP with
Cyberview
WIP postponed
22nd March 2016
VDMS Project
Brief
TCS submitted Project Brief to Cyberview as
requested
25th March 2016
VDMS Data
and Report
TCS Submitted VDMS Data and Monthly
Performance Report to Cyberview
28th March 2016
VDMS Project
Brief
TCS resubmitted Project Brief to Cyberview
-
Page 35 of 49
31st March 2016
Project Charter
Project Chartered
1. Include kick-off meeting include Cyberview
2. Project Planning- Team Members (Fairuze-
Dashboard developer and Dr Wong from
MIMOS)
3. Data Scientist from Cyberview
Include Meeting dates for Milestones
4. Reporting- forth meeting and report targeted
dates to meet up and report
5. Requirements from TCS
6. Business impact (Green City showcase and
mobility)
7. Charter to include progress meeting and
milestones meeting sync with reporting and
papers to derive from there
8. Complete all blank form
Separate Project Brief for Phase 2 (Web Portal)
1. Process impacted: DTS-from MCMC side on
long term plan
2. LCCF and MSC Status
Conclusion
1. TCS has completed fill up all the blank form
for project chartered 1 including the milestones
date, goal and business impact
2. TCS has separate 2 project chartered
3. TCS has emailed Cyberview updated project
brief (Scope and requirements included)
4. Still couldn’t get Dr Wong from MIMOS
5. Still waiting for En Badz from MCMC to give
details on long-term plan for this project
TCS submitted Project Charter as requested by
Cyberview
Apr-16
6th April 2016
TechCapital
WIP with
Cyberview
Postponed to 8th April
8th April 2016
TechCapital
WIP with
Cyberview
TCS submitted
a. Benchmark
b. Dashboard Requirements
c. Milestone VDMS
d. VDMS Project Brief
e. VDMS Dashboard Fleet
f. VDMS Dashboard Table
g. VDMS Dashboard Vehicle
-
Page 36 of 49
19th April 2016
Project Brief -
LivingLab Pilot
By signing the pilot project brief is a commitment
by Tech Capital for pilot requirements agreed by
all parties including Cyberview and DiSitu
RoadMe Pilot project is park under LivingLab
Pilot project
TCS to sign the project agreement
May-16
12th May 2016
LivingLab Pilot
project
TCS has been awarded for Cyberview LivingLab
Pilot project collaboration of RoadMe Vehicle
Diagnostics & Monitoring System (VDMS) on
Dedicated Transport System (DTS) programme
with Disitu Hodlings Sdn Bhd for 1-year project
30th May 2016
TCS Indemnity
Letter
TCS has been requested by Cyberview to email
Company letter head for the indemnity letter get
TCS managing Director to sign
Jun-16
8th June 2016
Meeting with
TechCapital,
Cyberview,
GICT WG &
MTSFB on
VDMS project
clarifications
The main agenda of this meeting to allow all
parties (MTFSB, GICT WG, TechCapital,
Cyberview along with MCMC) is to seek some
clarifications on the project updates from
TechCapital on their VDMS project.
TCS presented latest update and clarifcation on
the project delay together with Cyberview
16th June 2016
Technical
Meeting with
Scania Team,
DTS Team &
VDMS Team
Due to SCANIA protocol, TCS is not allowed to
tape VDMS directly to the ECU, thus some
changes need to be done:
a. TCS has to install CAN bus system inside
VDMS
b. SCANIA to give TCS the protocol and the
communication
c. TCS to submit SCANIA VDMS architecture
system drawing
-
Page 37 of 49
17th June 2016
Update MTSFB
on VDMS
project
MTSFB request TCS to:
a. referring to the slide (presented during
meeting at Cyberview), TCS has come out with
a new milestone for this project.
b. transfer it into the gantt chart and send it to us
together with the updates
TCS update MTSFB, TCS together with DTS
and Cyberview had a technical meeting with
SCANIA yesterday (16/06/16) to discuss on:
1. Technical details of the ECU
2. Communication and Installation protocol
3. Installation guidance
28th June 2016
Project Brief
Cyberview requested TCS to look at the project
Brief and ensure all outputs as agreed are
transferred to the deliverables of this project and
reflected in the gantt chart as well.
29th June 2016
VDMS Report
template
TCS submitted cyberview:
1. updated report template
2. Dashboard
30th June 2016
TechCapital
WIP with
Cyberview
Agenda of the meeting:
1. Run through updated Gantt chart
2. Agree on reporting format and requirements
for reporting
Jul-16
1st July 2016
WIP for VDMS
With the official handover of the Project Brief
document and Scania meeting, 16/6/2016 as
project plan sign off or completion of user
requirement. This of course sets the basis for
user requirement of the dashboard but does not
denote the complete description for user
requirement of dashboard. This is because we
need to meet with listed stakeholders to get their
consent and agreement on the credibility and
feasibility of the user requirement to ensure
value of reporting from the dashboard.
14th July 2016
WIP for VDMS
TCS submitted to Cyberview updated milestones
19th July 2016
Technical
Meeting with
SCANIA
Technical Meeting with SCANIA postponed
-
Page 38 of 49
Aug-16
3rd August 2016
Technical
Meeting with
SCANIA
1. TCS requested SCANIA to send the protocol,
after waiting for months,
2. TCS submitted the VDMS Architecture
16th August 2016
Technical
Meeting with
SCANIA
SCANIA emailed the name of protocol however
its not as TCS requested. Requested SCANIA to
resend the right protocol and communication
18th August 2016
WIP for VDMS
TCS submitted to Cyberview the WIP draft as
requested
Oct - 16
13th October 2016
VDMS
installation
-We have managed to complete the wiring for all
3 buses (BLG7801, BLG7802, BLG7805) with
the help from DTS's Technician.
-The route for the wire is passing from the ECU
Box > under the bass > compartment beside the
dashboard > 1st floor bus chassis (wall) > 2nd
floor front compartment –> VDMS Device
-Bus BLG7801 and BLG7802, the wiring is made
fully by DTS's technician without any drilling on
the bus wall.
-Bus BLG7805 requires some drilling for our
cable to pass through as that bus is the old
model and the wiring route is inside the chassis
itself. We made the drilling after we have obtain
permission from DTS's technician.
-We did not manage to finish install VDMS fully
because we did find some more items that need
to have before fully install.
-We can proceed with the installation of VDMS
once we have all our items ready as we already
have all the information provided by DTS's
technician on the ECU and power connection.
-
Page 39 of 49
27th October 2017
Cable
installation
The installation process was done on
bus BLG7801, BLG7802 and BLG7805. The
installation includes:
1. Installing the socket for power and ECU at
VDMS device (2nd floor)
2. Installing the Power Connector at the Battery
board (1st floor)
3. VDMS devices and ECU are complete
synchronized
Nov-17
15th November 2017
Cable
installation
-We have completed the wiring process for the
bus with license plate number BLG7808 with the
help from DTS bus technicians.
-The wiring and cabling process of the bus which
requires drilling on the bus wall is made fully by
DTS bus technicians.
Apr-17
11th April 2017
Socket
Inspection
-Socket inspection on bus BLG 7808 on the bus
ECU’s.
June-17
20th June 2017
Replace VDMS
-Replace old socket and VDMS (Updated
version) on bus BLG 7808.
21th June 2017
VDMS
meeeting
-Meeting progress at MCMC.
-VDMS dashboard presentation.
-
Page 40 of 49
10.0 Conclusion In summary, we managed to achieve the main objectives of this project. The first
objective is to build the technology implementation that is able to monitor the
speed, location and route of the bus via GPS module. VDMS system designed is
able to provide and allow for monitoring of these information with the installation of
3G communication module. Second, to improve service performance and
efficiency by monitoring the bus activity (location and time of start and stop). The
real-time monitoring environment of VDMS system allows for this functionality to be
met where the user can check the activity of the bus at any time through the
website portal created. Third, to observe for environmental friendliness by
monitoring fuel consumption and emission of the bus among others. The
VDMS system designed is able to provide and allow for monitoring of these
information via the website portal. With the collected information on fuel
consumption and emission rate, the service providers are able to come out
with better approaches such as route revision to further reduce the fuel
consumption. With the reduced fuel consumption, this can then reduce the
emission rate to the environment and therefore supporting for “green technology”
for the environment. Finally, to provide accurate and reliable real-time information
on bus activity to traffic management officer and bus service provider through
website portal. As mentioned, the VMDS system designed is able to fulfill this need
with its robust engineering make.
2CO
2CO
2CO
-
Page 41 of 49
11.0 References
1. Calculating 2CO Emission from Mobile Sources. GHG Protocol - Mobile Guide
(03/21/05) v1.3. Retrieved from http://www.ghgprotocol.org/guidance-0
-
Page 42 of 49
12.0 Appendix A
-
Page 43 of 49
Appendix B
-
Page 44 of 49
Appendix C
-
Page 45 of 49
Appendix D
-
Page 46 of 49
Appendix E
-
Page 47 of 49
Appendix F
-
Page 48 of 49
Appendix G
-
Page 49 of 49
THE MALAYSIAN TECHNICAL STANDARDS FORUM BHD
Malaysian Communications & Multimedia Commission (MCMC Old Building)
Off Persiaran Multimedia, Jalan Impact 63000 Cyberjaya,
Selangor Darul Ehsan Tel: (+603) 8320 0300 Fax: (+603) 8322 0115
Website: www.mtsfb.org.my
http://www.mtsfb.org.my/
top related