Proposal for a Vehicle Tracking System (VTS)

Proposal for a Vehicle Tracking System (VTS)

2 Executive Summary Intelligent Instructions is an IT product development and consulting company. At Intelligent Instructions, we focus on the needs of the client by applying consulting principles adopted by reputed organizations. Our offerings are end to end solutions for web related applications of all complexities from simple to enterprise levels. For maintaining our focus on core competencies, we function as two entities within the single organization. Our development team is called Accudata group placed in Cochin, India. The sales and consulting function is done under the brand of intelligent Instructions. In Accudata, we have dedicated team of 40 members working on core applications. Through this team we provide services like domain registration, server space and management, website development and maintenance of all levels. You could visit us at accudatagroup.com. The team of Intelligent Instructions is a 3 member consulting and 3 member sales team performing activities from three separate locations. The two sales offices in India is located in New Delhi and Bangalore. The other overseas sales office is at Wyoming State US. The consulting practice for web related application is at Bangalore. We have a 10 member team dedicated to RFID core development and deployment. We have expertise in.net and Java Technologies and have a proven track record. We have also associated with known brand names in the world. Some of our associates for knowledge and technology transfer are bielomatik, Germany ( we represent bielomatik in India), Printronix, Singapore ( we have a strong working relationship for RFID printers) etc. We are grateful for this opportunity to submit a proposal for your RFID based vehicle tracking system solution and maintenance to. 1. The Vehicle Tracking System Business View Tracking many numbers of vehicles over a boundary or premises is possible only when we have uniquely identified vehicles and their verification at a very fast speed. Unique vehicle identification number should be any widely accepted. The solution should be widely accepted, easily trace able, various technological supports should

be there. Vehicle readers can be used at the entry/exit points. Each movement through the should update the Data Base for any future reference in case of theft or any unwanted incident. Any unwanted intrusion should also be tracked. The system should be fast enough to inform any unwanted vehicle. The business logic must produce vehicle reports, their movement through all security checks. All necessary information can also be stored with the vehicle data. So that when requested vehicle owners can be verified with the mapped information. This will help in avoiding vehicles theft etc. Future vehicle movements can also be configured in the system e.g. any event where only few vehicles are authorized to enter only 2 or 3 times. Vehicle authentication can also limit to a specific group of persons only. Any unwanted person can not drive the vehicle. In this case license information can also be stored with vehicle data. Any third party system can be attached to the system so components should be adaptive enough. 3 Based on the brief description of project, we held discussions with our technical team. We decided to present a proposal and rework the functionalities based on your feedback. Based on the discussion we arrived at the following framework 2.1 Purpose of VTS document This document is produced by the Engineering to define the software design for VTS system.vts is a RFID based Vehicle Tracking System, for managing the security of vehicles in a premesis or boundries.on road vehicles can also be tracked through mobile tracking devices. RFID tags are widely acceptable Electronic Product Code based (EPC) based tags which are stickable to any product. Uniquely stored information in tags can be read using RFID tag readers. Static pole readers as well as hand held readers can be used for querying the EPC code of the vehicle.any unwanted vehicle will result in a RFID check fail. That can help security in avoiding any unwanted activity. VTS will contain a web GUI for the reference of senior managers as well as normal users.time wise reports for each vehicles, Employees work scheduling, Instructions and Time alerts etc are few business activites which can be achieved through the GUI. GUI will be exposed to every user of the system. Authorization mechanism will be used for allowing users for all operations.any bulk updation of data in system will be possible through GUI.Relevent informaion of vehicle can also be found using GUI. e.g Owner information, Vehicle registration etc. Individual vehicle owners can also get system access to view their vehicle information. VTS is a distributed system with single data base and multiple clients.various client will update centralised DB. The main solution is to trace vehicles at various check

posts and store the track in DB for future reference and if found any unauthorized vehicle inform the secutiry. Exhibit 1 : Multilevel RFID Based Business Model 4 Audience The audience for this document includes Engineering team and client. Assumptions Serial # Assumption Open Issues Serial # Issue Resolution Status (Owner) 1. Terms and Abbreviations Term Description

3.0 Vehicle Tracking System Architecture There are two possible architectures for the solution of VTS. One is c/c++ runtime based solution, and second is SUN solution based. 3.1 Solution First: C/C++ Runtime based Solution Exhibit 2: Various Module Interaction Diagram 5 3.1.1 The EPC Reader System This module acts as an interface between RFID reader hardware and data base Driver must expose methods (probably combinations of read/ioctl calls) to the driver library. These methods must be called by Application through driver library interface and not directly. This way application is not dependent on driver and the hardware for reading EPC. The system should be flexible enough to scale to any hardware. The Driver Library is responsible for exposing APIs which can be used directly by the application to read EPC. The driver library must take care of platform independent functionality.

Exhibit 3: RFID Reader and middleware Interaction Diagram 3.1.2 The Security Alarms System. Security Alarm systems are required for making check on any unwanted theft. For the provision of this service in memory cache is required for carrying EPC data. Immediate check can be made with the help of In Memory cache. In memory cache is required for prompt response. Security checks are required at various check points as well as with security guards. Every new vehicle movement should update the in memory cache immediately for updating the in memory product inventory. A high level accuracy is required in maintaining this in memory cache. An interface must be exposed which can be used by driver library APIs to raise/stop an ALARM. If supported by the hardware, we should be able to configure the alarm time. An in memory cache is going to be utilized by this part so that a real time check can be made when a vehicle is passing. 3.1.3 Security Center GUI Following are few points to be considered while developing the GUI system, Query/Response System to get status of a product by EPC (High Response System with ideally not more than few milliseconds of delay). GUI must work with EPC reader System for user friendly, RFID centralized management system GUI system can be enhanced to any other systems like interactive response system for the self service. 6 At the hit of final sanction or submit at GUI. Immediate affect should be reflected in memory cache.

Higher level transaction management is required at this level for avoiding any EPC conflict. Solution should be platform independent. Authentication and Authorization is required for managing security. 3.2 Solution Second: SUN RFID Solution SUN is a big player in Enterprise Solutions Industry. SUN provides its solutions for RFID industry, RFID event manager and EPC information servers. JMS based communications is used for integrating business logic with Event managers. This is solution is very helpful for integrating with other preexisting or future components. Enterprise servers like web logic can be used for holding the business logic and SUN event managers communicate as mediator between RFID reader and Application Server. It also provides JAVA library for accommodating any new RFID readers. Following is the System level View of the SUN RFID Solution, Exhibit 4: architecture based on sun technologies (Courtesy sun technologies)

7 3.3 Business Layer This module is responsible for the following Maintaining EPC data over various Security Checks in flexible way. Reporting System for generating the vehicle tracking report. The whole business logic for Vehicle Tracking system. High Level GUI will interact with this business logic for management level view. The initial idea is to keep the business logic separate from access mechanisms. SOAP based Web services would be used for this purpose. Web services can be accessed from any type client. This would help in maintaining in less hardware dependency. The further additions can be made on this section on mutual discussions. 3.4 Distributed web 2.0 GUI GUI will be the common solution for both JAVA based solution and c/c++ based solution. The main task of GUI is to provide Enterprise Level View of the System. Every individual entity of the system should be manageable through the GUI. Either its manpower or raw apparel GUI should show the status of every related data stored in system. GUI is the central port of every system for coordinating between various departments of apparel business. Web 2.0 is a submit less web technology, following are few qualities of web 2.0, The web as a platform Data as the driving force Network effects created by an architecture of participation Innovation in assembly of systems and sites composed by pulling together features from distributed, independent developers (a kind of "open source" development) Lightweight business models enabled by content and service syndication In less it can be said web 2.0 is submit less data centric technology where instead of whole page only data flows in network; comparatively faster to contemporary web 1.0. GUI will help people to manage all high level tasks as well as individual level efforts. Various level activities e.g. Document generation (CSV, XML, DOC, PDF etc). Bulk Vehicle Information Upload. Bulk Vehicle Information download. Role-based information display. Role-based user rights (like editing /deleting /inserting) for providing users centralized view of the whole system.

Vehicle Status (Date wise, Day Wise etc. Manpower Management (Activity, Scheduling etc) 8 EPC Tracking. Event and Performance Alerts to respective users for maintaining schedules. Business Process Management. Rule Based Solutions. 4. The time line of completion and Resource Charts The time line outline the entire SDLC life cycle with the weekly reports send across to the client. Activity / Week 1 2 3 4 5 6 7 8 9 10 11 12 13 15 16 Detailed System Study Preliminary Design Logic Implementation Final Visual design Integration & Testing Role functions Team Size IT Architect 1 Senior Programmers 2 Junior Programmers 2 Visual designers 1 Testing professionals 2 4.0 Professional Fees

The professional fees and the details of the hardware requirements can be discussed based on the level of implementation and its scope. 5. Delivery Lifecycle and schedules The acceptance of the final proposal with the initial advance of 30% of the project value will commence the project. On the week 10, we provide with a pre acceptance run for the client representation in our facility in India. With the successful completion of the pre acceptance test, a 15% of the project value should be advanced and we will be testing the application extensively till the final two weeks. 9 All the modifications if any will be incorporated into the system and will me made ready for deployment. A 15% of the total project value should be provided and we will be deploying our team to the premises of the client for a final test run and implementation. The knowledge transfer will be done with subsequent workshops at your premises for the chosen employees for the project. The remaining payment of 40% should be transferred after the successful knowledge transfer. 6.0 Why Intelligent Instructions We could offer you the complete solution or service related to your requirements. Hence we provide one point solution we could integrate all the functionalities more effectively. We have strong partner networks like bielomatik Germany (RFID conversion machinery) etc. With these associations, we could provide with quality solutions which our partners ensure to the customers across the world.