Abstract: A system and method for storing and processing information related to one or more vehicles is described. The system and method may enable to overcome inefficient tracking of vehicle history and further determining the definite resale value of a vehicle. The system and method may further disclose portal which stores history of a vehicle which may be entered by a plurality of diversified users. Such portal may be implemented on a server based system which may enable to process the stored history of the user. The system may store a historical data associated to one or more vehicles comprising vehicle profile data, service & maintenance related data and accident related data. The system may receive a plurality of service job cards and estimates from one or more service provider. The system may analyse the historical data to compute a score and a resale value for the one or more vehicles.
DESC:FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See Section 10 and Rule 13)
Title of invention:
SYSTEM AND METHOD FOR STORING AND PROCESSING INFORMATION RELATED TO VEHICLES AND ITS MAINTENANCE
APPLICANT:
BD INDUSTRIES
a Partnership Firm registered under The Indian Partnership Act, 1932
having its registered office at
5, Raj Rajeshwari Road, LBS Marg,
Opp. Naval Stores main road, Narayan Nagar, Ghatkopar West,
Mumbai 400086, INDIA
The following specification describes the invention and the manner in which it is to be performed.
CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY
The present application claims priority from Indian Provisional Patent Application No. 3522/MUM/2015 filed on 14th January, 2016.
TECHNICAL FIELD
The present invention relates to a system and method adapted for administrative, commercial, managerial, supervisory or forecasting purposes for tracking a life history of a vehicle. More particularly, this invention relates to a single universal Internet based portal/website/platform/application which collects, manages and supervises the data relevant to the vehicle history.
BACKGROUND
Vehicles are widely used in the world as various transportation means. They may be either used to transport passengers or cargo. Vehicles are an important companion of an individual or a group of individuals. They may be used to make a successful journey for people to go to a destination or in transportation of goods with least effort.
In order to make the vehicle free from problems which may occur during any journey they are serviced for their maintenance from time to time. They may be serviced for changing engine oil, replacing oil filter, replacing fuel filter, replacing sparkplug, tune engine, replacing any equipment which may be damaged, replacing tyres and the like.
An acknowledgement receipt is given to the owner of the vehicle for services and replacement of spare parts. This receipt may be later docketed or turned into scrap as it delivers only data and amount for the services and replacements of equipment. The owner of the vehicle may be interested in only verifying the replacement of the equipment. This information later lapses and may not be referred in future because of information getting misplaced.
Further, the Original Equipment Manufacturer (OEM) may not get to know the data and whereabouts pertaining to each manufactured product once it is sold. A product once installed is usually not tracked or there may not be any source of tracking the products inside a vehicle. The OEM may not get an alert of the replacement of an equipment to a specified vehicle. They also do not get a proper turnaround time for servicing taken by the dealer and majority of the data that the OEM receives pertaining to the market is through the feedback which dealer shares with the OEM. This portal/website/platform/application will link the consumer to the OEM directly. Also, currently, the OEM may not be able to track the vehicle after it has passed out of the warranty period. This portal/website/platform/application will help to overcome this shortcoming as OEM will be able to track the vehicle for its life.
A pre-owned vehicle buyer always refers to the history of the vehicle to take decision for owning the vehicle as the estimation of the life of the vehicle may be prepared based on the data which holds the history of the vehicle. Further, this history may also allow Original Equipment Manufacturing (OEM) to have real time data about any vehicle and the OEM does not have to rely on data provided by dealer which is a problem faced by OEMs currently.
A history of a vehicle including details of its servicing and replaced components may not be maintained by the owner, user, consumer, dealer or OEM. A history of vehicle is very important for its data entry and evaluation.
History of the vehicle comprising past ownership, accidents, replacement of OEM equipment, loans, title of ownership, travelling logs and the like is desired to be maintained. Such history should be readily accessible in the form of a portal or a gateway. The vehicle user, owner, consumer or the portal may also track the vehicle through a chip which shall be installed on the vehicle.
The present invention may solve the long-lasting problems including but not limited to the ones listed above. The biggest problem being tracking of the history of a vehicle efficiently and trying to overcome the lack of trust in the mind of a prospective second hand car or vehicle buyer.
SUMMARY
Before the system and method of the current invention is described, it is to be understood that this application is not limited to the particular methodologies described, as there can be multiple possible embodiments which are not expressly illustrated in the present disclosure. It is also to be understood that the terminology used in the description is for the purpose of describing the particular versions or embodiments only, and is not intended to limit the scope of this invention. This summary is provided to introduce concepts for facilitating a simple yet secure application for system and method adapted for administrative, commercial, managerial, supervisory or forecasting purposes for tracking a life history of a vehicle and the concepts are further described below in the detailed description. This summary is not intended to identify essential features of the disclosure nor is it intended for use in determining or limiting the scope of the disclosure.
In one embodiment, a method for storing and processing information related to one or more vehicles is described. The method may further comprise receiving, via an input/output interface, a historical data associated to one or more vehicles, wherein the historical data comprises vehicle profile data, service & maintenance related data and accident related data associated to the one or more vehicles, and wherein the historical data is updated at a time interval. The method may further comprise analyzing, via a processor, the historical data associated to the one or more vehicles in order to compute a score and a resale value for the one or more vehicles, wherein the score indicates a qualitative assessment of the one or more vehicles, and wherein the resale value indicates an estimated selling price of the one or more vehicles, and wherein the processor is capable of updating the score and the resale value, in real time, based upon the recently updated historical data. The method may further comprise generating, via the processor, a report depicting the historical data, the score and the resale value for the one or more vehicles.
In another embodiment, a system for storing and processing information related to one or more vehicles is described. The system comprising a server further comprising a processor further comprising an input/output interface and a memory coupled with the processor, wherein the processor executes a plurality of modules stored in the memory. The plurality of modules may further comprise a vehicle profiling module, wherein a historical data associated to one or more vehicles is received by the server via the input/output interface, wherein the historical data comprises vehicle profile data, service & maintenance related data and accident related data associated to the one or more vehicles, and wherein the historical data is updated at a predefined time interval. The plurality of modules 204 may further comprise a servicing module enabled to receive a plurality of service job cards and estimates from one or more service provider wherein such job cards and estimates are based on the particular services requirement broadcasted by the user on the input/output interface. The plurality of modules may further comprise an analysing module wherein the historical data associated to the one or more vehicles is analysed in order to compute a score and a resale value for the one or more vehicles, wherein the score indicates a qualitative assessment of the one or more vehicles, and wherein the resale value indicates an estimated selling price of the one or more vehicles, and wherein the processor is capable of updating the score and the resale value, in real time, based upon the recently updated historical data. The plurality of modules may further comprise a report generating module enabled for depicting the historical data, the score and the resale value for the one or more vehicles.
BRIEF DESCRIPTION OF THE DRAWINGS
The detailed description is described with reference to the accompanying figure. In the figure, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to refer like features and components.
Figure 1 illustrates a network implementation of the system 100 for storing and processing information related to vehicles and its maintenance, in accordance with an embodiment of the present subject matter.
Figure 2 illustrates a server 101 implemented as a portal is illustrated in accordance with an embodiment of the present subject matter.
Figure 3 illustrates a method 300 for storing and processing information related to vehicles and its maintenance is illustrated, in accordance with an embodiment of the present subject matter.
The figures depict embodiments of the present disclosure for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the steps illustrated herein may be employed without departing from the principles of the disclosure described herein.
DETAILED DESCRIPTION
The invention relates to system and method of creating a portal which stores history of a vehicle which may be referred or entered by, but not limited to, an owner, user, consumer, dealer, authorised/unauthorised service stations or Original Equipment Manufacturer (OEM) of the vehicle. Such portal may be implemented on a server based system which may enable to process the stored history of the user.
For the purpose of this invention the term “vehicle” refers to mobile machines to transport passengers or cargo. Vehicle in the present specification comprises wagons, bicycles, motorcycles, cars, trucks, buses, railed vehicles, watercrafts, aircrafts, spacecraft and the like.
For the purpose of this invention, “History of the vehicle” may refer to all the events and operations made in the vehicle. History may refer to services comprising service logs, replacement of OEM equipment, replacing engine, brake, gearbox, clutch oils and the like, due to functional requirements or as preventive maintenance. History may further refer to accidents and damages incurred to the vehicle. Loans and insurance policy data may also be a part of the history including, but not limited to, its title history etc. This history may further be transferable to the new owner of the vehicle. This may happen at a cost or for free.
In one embodiment, the invention may have a payment gateway linked with different parties comprising a dealer, an OEM, one or more consumer(s) and the like. In another embodiment, based on the history of the vehicle, the present disclosure may be enabled with computer programmed product which will automatically perform evaluation of the vehicle with no human intervention. Furthermore, if there is an occurrence of any evaluation which is not comprehensible by the system or which require new commands not present in that current system, then in such exemplary cases the commands for or the problem associated with the evaluation may be solved with human intervention.
For the purpose of this invention “Consumer” may be one or more individual(s) who purchase the vehicle from the dealer or a car owner in case of second hand car sale. The “dealer” may be an individual or a party who may be a stakeholder who is authorized or not authorized by an OEM to sell, service and maintain one or more vehicles or the equipment made by the Original Equipment Manufacturers (OEMs). “OEMs” may be a party authorised to engage in production of an equipment or part of an equipment.
Referring to Figure 1, a network implementation of the system 100 for storing and processing information related to vehicles and its maintenance is illustrated, in accordance with an embodiment of the present subject matter. In one embodiment, the system may comprise a server 101 which is the point for storing and processing the information. The server 101 may be accessed via a network through the user device 103. The user device 103 may be connected to the communication network 107 via a radio access network 102. The server 101 may be accessed via a portal 102 which may enable the user to sign in an account to produce a vehicle profile and a user profile. In an embodiment, the system may comprise profiles further comprising the vehicle profile, dealer profile, user profile and OEM profile corresponding to one or more vehicle and further to log in for updating the information relating to the vehicle from time to time. The server 101 is further capable of generating reports of vehicle comprising information relating to the vehicle of the user wherein such report may be further referred by the server 101 itself to rate and calculate the resale price value of the vehicle.
Although the present subject matter is explained considering that the system is implemented on a server, it may be understood that the system may also be implemented in a variety of computing systems, such as a distributed system, a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, a server, a network server, a handheld device and using a variety of database software like- RDBMS (example- Oracle, Postgres), distributed file systems (example- MapR). Examples of the user devices 101 may include, but are not limited to, a portable computer, a personal digital assistant, a handheld device, and a workstation.
In one implementation, the network may be a wireless network, a wired network or a combination thereof. The network can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further the network may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.
In an embodiment, the system as covered by the present disclosure may comprises a Portal which is connected to a content server over a network. This portal is further connectively coupled to one or more User devices. The one or more user device may further comprise one or more user devices belonging to a user, one or more Dealer devices and one or more OEM devices for the exchange of data and payments and other user devices that may form a part of the portal at a later stage.
In another embodiment, the system is configured such that the server and user device are connected to a chip or device in the vehicle which will transmit the real time vehicle information to the system.
Referring Figure 2, the server 101 implemented as a portal is illustrated in accordance with an embodiment of the present subject matter. In one embodiment, the server may include at least one processor 201, an input/output (I/O) interface 202, and a memory 203. The at least one processor 201 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one processor 201 is configured to fetch and execute computer-readable instructions stored in the memory 203.
The I/O interface 202 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 202 may allow the server to interact with a network administrator using one or more devices such as a laptop computer, personal computer, smartphone, and the like. Further, the I/O interface 202 may enable the server 101 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface 202 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 202 may include one or more ports for connecting several devices to one another or to another server.
The memory 203 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The memory 203 may include modules 204 and data 205.
The modules 204 include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. In one implementation, the modules 204 may include and other modules. The other modules may include programs or coded instructions that supplement applications and functions of the server 101.
The data 205, amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the modules 204. The data 205 may include data repository 210 and other data 211. The data repository 210 may include data records captured from multiple data sources for each session in a communication network. The other data 211 may include data generated as a result of the execution of one or more modules in the other modules. The detailed functionality of the modules 204 are further described.
VEHICLE PROFILING MODULE 206
The vehicle profiling module 205 may enable the user to create a complete profile of the vehicle wherein information comprising the model number, the identification number provided by the traffic authority, the purchase date, insurance issued and loan data associated with the vehicle. Such data may be provided by the user via the network through user device. The vehicle profiling module 205 may further comprise a data not limited to ownership data.
In an embodiment, when a vehicle is purchased by a consumer from a dealer, a vehicle profile may be created in the portal automatically or manually by the consumer, user, owner or dealer with data specific to the vehicle and data of the consumer and dealer embedded in it. The data comprise date, amount of transaction, vehicle title or model number, vehicle registration number, chassis no., engine no., consumer contact details, dealer contact details and the like. This data after being updated may automatically be pitched to one or more OEMs. The OEM refers to the data and checks for the equipment incorporated with the vehicle and an update is made in the data which may enlist the equipment assembled in the vehicle.
In an implementation, the vehicle profile may be made before the purchase of the vehicle while booking with the available data. This pre-set data may be used by the OEM to fix their turnaround time to deliver the equipment and monitor the time dealer takes to deliver the vehicle after it has dispatched from the OEM location.
In an embodiment, the vehicle profiling module 205 may enable the user to update the relevant history of the vehicle further comprising service logs, replacement of OEM equipment, replacing engine, brake, gearbox, clutch oils and the like, due to functional requirements or as preventive maintenance. History may further refer to accidents and damages incurred to the vehicle. Loans and insurance policy data may also be a part of the history including, but not limited to, its title history etc. This history may further be transferable to the new owner of the vehicle.
In an embodiment, an update to the data may be performed for servicing of the vehicle. Any replacement of the equipment within the vehicle is recorded and the same may be updated on the portal. Any accidents and damages incurred with the vehicle may also be updated in the data of the vehicle profile. All the data uploaded on the portal may be accompanied by scans of documents or images.
SERVICING MODULE 207
The servicing module 206 may enable the user and service provider to interact and further conclude to the event of servicing of the vehicle. In an implementation, the user of the vehicle may broadcast service requirement of the vehicle on the portal. The service requirement may comprise at least one of the complete servicing, vehicle washing, vehicle spare part replacement and other miscellaneous works related to the vehicle. A plurality of service providers may review the service requirement shared by the user and further choose to respond by providing a preliminary job card and an estimate associated with the service requirement. For example, a user who has enquired for wheel replacement may receive one or more quotations or estimate from a vehicle wheel dealer, authorised OEM dealer, an authorised service station dealer and the like. The user may optionally select the estimate feasible for him/her and may further fix the deal with the dealer or service provider for servicing the vehicle with the particular service of wheel replacement. Such data log of service may be further updated via the vehicle profiling module 205. The job card may be recorded in the system and vehicle history will be updated automatically.
ANALYSING MODULE 208
The analysing module 208 may enable the server to
• Rate the vehicle within a prescribed range
• Compute the resale value of the vehicle
• Remind the users of insurance renewals, service schedules and other time bound activities related to vehicles.
Such rating is determined by the present condition of the vehicle and the available generated and updated data. In an embodiment, based on the service logs, the analysing module 207 may enable the server to check whether the service have been made time to time and within standard stipulated time. If the service logs synchronises with standardised service logs, then the vehicle may be rated with a rating closer to the upper limit. For example, 8 points out of 10.
Furthermore, the resale value of the vehicle may be computed by the server by considering the information and data available in the updated data. The analysing module 207 may further access the data which is relevant to the vehicle’s monetary value. The resale value may be computed based on a prescribed depreciation algorithm. The depreciation algorithm may consider all parameters directly associated and further affecting the price value of the vehicle in whole.
REPORT GENERATING MODULE 209
The report generating module 209 may enable the server to generate report on the user command or on time to time basis. Such generated report may further comprise a detailed and comprehensible data of the vehicle along with the vehicle history. The comprehensible data may further comprise not limited to the following:
• Date of purchase
• Distance indicated on the Odometer
• Service logs along with details
• Replacement history of one or more spare parts
• Insurance coverage
• Ownership title
• Computed value of vehicle
• Document log
• Odometer log
• Accident log
• Timeline of the vehicle
• Miscellaneous data
Referring Figure 3, a method 300 for storing and processing information related to vehicles and its maintenance is illustrated, in accordance with an embodiment of the present subject matter.
At block 301, the user after purchasing the vehicle may create the vehicle profile with details further comprising the model number, the identification number provided by the traffic authority, the purchase date, insurance issued and loan data and other miscellaneous data associated with the vehicle.
In an embodiment, the vehicle profile may be made before the purchase of the vehicle while booking with the available data which may be provided by OEM with data such as VIN No and the like. This pre-set data may be used by the OEM to fix their turnaround time to deliver the equipment and monitor the time dealer takes to deliver the vehicle after it has dispatched from the OEM location. Such pre-set profile may be further handled by the owner of the vehicle.
At block 302, the user may update relevant information for the upkeep of the vehicle. The relevant information may further comprise service logs, replacement of OEM equipment, replacing engine, brake, gearbox, clutch oils and the like, due to functional requirements or as preventive maintenance. History may further refer to accidents and damages incurred to the vehicle. Loans and insurance policy data may also be a part of the history including, but not limited to, its title history etc.
In another embodiment, the invention also provides a payment gateway between the consumer, dealer or OEM or any other remitter/beneficiary for online transaction. The transaction details may also be added in the data of the vehicle profile. The transaction details may be used to decide the actual value of the vehicle.
At block 303, the user may broadcast a service requirement of the vehicle on the portal which is received by one or more service provider or dealer. Based on the service a plurality of service providers may review the service requirement shared by the user and further choose to respond by providing a preliminary job card and an estimate associated with the service requirement.
At block 304, the user may enable the server to generate reports after providing the required command for the generation of report. Such generated report may further comprise a detailed and comprehensible data of the vehicle along with the vehicle history.
At block 305, the user while selling the vehicle may initiate rating and resale value computation process. The resale value may be computed based on a prescribed depreciation algorithm. The depreciation algorithm may consider all parameters directly associated and further affecting the price value of the vehicle in whole.
In another implementation, the portal will also have an insurance section where consumers can renew their vehicle insurance online and compare insurance suiting best to individual vehicle from different companies.
In yet another implementation, vehicles may be listed on the second-hand market as soon as a consumer ticks the option to list his or her vehicle on the market. General visitors to the site can look and compare vehicles listed on the market and may download history reports.
In yet another implementation, there may be a spare parts area on the portal where in general visitors and site consumer’s users can buy spare parts as it generally happens on an e-commerce platform.
In yet another implementation, in a separate feature on the portal’s website there may be a list of stolen cars available for the general public to view. If a consumer’s car is stolen the same can be reported on the website for the general public to see. Stolen vehicles’ data may also be collected from government and law enforcement agencies and presented on the portal. Consumers may have direct access to OEM should they want to raise any query to them. The portal may also have integration with Regional Transport Office (RTO) system at various levels.
In yet another embodiment, a method of performing the car score with a plurality of factors is illustrated in accordance with the Table 1, Table 2, Table 3 and Table 4.
Table 1 illustrates the rating of the vehicles by considering the plurality of parameters associated with the vehicle. Referring Table 1 below, year wise rating is implied on the vehicle against a plurality of parameters. The values may have either a positive impact or a negative impact based on the nature of parameter. For example, Parameter No. 10 Services not done time may carry a negative value as it represents parameters which may depreciate the value of the vehicle. There may be more parameters added/deleted from time-to-time to meet with current market trend/demand, so as to derive a car score which is highly accurate to possible extent.
Table 1
1st year 2nd year 3rd year 4th year
Sr.No. Parameter Average Average Average Average
1 User Profile Completion 4.17% 4.17% 4.17% 4.17%
2 Car Profile Completion 9.00% 9.00% 12.00% 9.00%
3 Services done 20.00% 13.33% 16.00% 13.33%
4 Percentage of service at authorised centres 10.00% 6.67% 6.00% 3.33%
5 No. of intermediate servicing 10.00% 10.00% 10.00% 10.00%
6 Major Accident Report 25.00% 25.00% 25.00% 25.00%
7 No. of recalls 0.00% 0.00% 0.00% 0.00%
8 No. of owners 5.00% 5.00% 5.00% 5.00%
9 Insurance 10.00% 10.00% 10.00% 5.00%
10 Services not done timely 0.00% -2.50% -2.50% -3.75%
FINAL RATING 93.2% 80.7% 85.7% 71.1%
Table 2 and Table 3 illustrates the depreciation of the vehicle. Referring both the tables below, the depreciation of a vehicle is illustrated year wise. The depreciate may further change brand wise and segment wise. Segment wise is further derived from the purchase value of the car. In an embodiment, segments may vary along a range where each segment is derived with a further range of price/purchase value of the vehicle. For example, table 2 illustrates a vehicle belonging to a Maruti brand with a price value more than 2 lacs. Similar, depreciation is provided in table 3 based on the running of the vehicle wherein the running is compared with standard values of running in the database of the server further resulting in the depreciation of the vehicle.
Table 2
Depreciation
Segment
BRAND Year E > 2L
Maruti 1 17%
2 22%
3 30%
4 42%
5 52%
Table 3
Kilometers driven
Year Kilometers
E > 2L
1 100%
2 100%
3 100%
4 100%
5 100%
Table 4 illustrates the year wise depreciated value of the vehicle by consideration of depreciation. Referring table 4, the algorithm is {Depreciated Car Value x Car Score/Rating}. For a well kept car, the car score/rating will be higher than average. For a poorly maintained car, the car score/rating will be lower than average. For this embodiment of wagon R, the car value is derived each year using the algorithm of {Depreciated Car Value x Car Score/Rating}. Each vehicle valuation is dependent on one more factor which is a levelling score which is further described as a point at which the algorithm decides whether to add or subtract a component from the depreciated car value. This value may vary/further differ as per the brand and the model of the vehicle. For the particular case illustrated in the table 4, the levelling score is 0.8.
Table 4
Algorithm based on fixed value increase based on band
Maruti Wagon R Lxi
$$$ 1st Year 2nd Year 3rd Year 4th Year
Current new car price 4,82,469 4,82,469 4,82,469 4,82,469
Depreciated car value (new price x depreciation) 4,00,449 3,80,427 3,49,993 3,07,994
Car score 0.93 0.81 0.86 0.71
CarLog Value (effective +/- something) 409766 388493 358559 272452
Although implementations for method and system for detecting anomalies in recorded consumption of data in a communication network have been described in language specific to structural features and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations for detecting anomalies in recorded consumption of data in a communication network.
,CLAIMS:1. A method 300 for storing and processing information related to one or more vehicles, the method comprising:
receiving, via an input/output interface 202, a historical data associated to one or more vehicles, wherein the historical data comprises vehicle profile data, service & maintenance related data and accident related data associated to the one or more vehicles, and wherein the historical data is updated at a predefined time interval;
analyzing, via a processor 201, the historical data associated to the one or more vehicles in order to compute a score and a resale value for the one or more vehicles, wherein the score indicates a qualitative assessment of the one or more vehicles, and wherein the resale value indicates an estimated selling price of the one or more vehicles, and wherein the processor is capable of updating the score and the resale value, in real time, based upon the recently updated historical data; and
generating, via the processor 201, a report depicting the historical data, the score and the resale value for the one or more vehicles.
2. The method 300 of claim 1, wherein the vehicle profile data comprises at least a vehicle number, manufacturing year, distances driven, insurance details, chassis number provided by the vehicle manufacturer, purchase date, vehicle model number and transfer of vehicle to different owners.
3. The method 300 of claim 1, wherein the service & maintenance related data comprises not limited to data relating to memorandum of servicing schedule of a vehicle, replacement of spare parts and running of the vehicle with date stamp.
4. The method 300 of claim 1, wherein the report is accessible to one or more users comprising an Original Equipment manufacturer (OEM), a dealer and an authorised person.
5. The method 300 of claim 1, wherein the user device 103 via the server 101 receives a plurality of service job cards and estimates from one or more service provider wherein such job cards and estimates are based on the particular services requirement broadcasted by the user on the input/output interface 202.
6. The method 300 of claim 1, wherein the resale value is computed based upon a plurality of parameters derived from the historical data associated to the one or more vehicles.
7. The method 300 of claim 1, wherein the services comprise one or more of complete servicing, spare part replacement, vehicle wash, other aesthetical services and other services relating to a vehicle.
8. A system 100 storing and processing information related to one or more vehicles, the system comprising:
a server 101 further comprising
a processor 201;
an input/output interface 202; and
a memory 203 coupled with the processor 201, wherein the processor 201 executes a plurality of modules 204 stored in the memory 203, the plurality of modules 204 comprising:
a vehicle profiling module 206, wherein a historical data associated to one or more vehicles is received by the server via the input/output interface, wherein the historical data comprises vehicle profile data, service & maintenance related data and accident related data associated to the one or more vehicles, and wherein the historical data is updated at a predefined time interval;
a servicing module 207 enabled to receive a plurality of service job cards and estimates from one or more service provider wherein such job cards and estimates are based on the particular services requirement broadcasted by the user on the input/output interface.
an analysing module 208 wherein the historical data associated to the one or more vehicles is analysed in order to compute a score and a resale value for the one or more vehicles, wherein the score indicates a qualitative assessment of the one or more vehicles, and wherein the resale value indicates an estimated selling price of the one or more vehicles, and wherein the processor is capable of updating the score and the resale value, in real time, based upon the recently updated historical data; and
a report generating module 209 enabled for depicting the historical data, the score and the resale value for the one or more vehicles.
9. A system of claim 8, wherein the server 101 is accessed by the user via a user device 103 configured to connectively couple with the server 101 through a network.
| # | Name | Date |
|---|---|---|
| 1 | 3522-MUM-2015-FER.pdf | 2020-07-21 |
| 1 | FORM28 [14-09-2015(online)].pdf_29.pdf | 2015-09-14 |
| 2 | 3522-MUM-2015-Correspondence-110316.pdf | 2018-08-11 |
| 2 | FORM28 [14-09-2015(online)].pdf | 2015-09-14 |
| 3 | EVIDENCE FOR SSI [14-09-2015(online)].pdf_28.pdf | 2015-09-14 |
| 3 | 3522-MUM-2015-Form 1-110316.pdf | 2018-08-11 |
| 4 | EVIDENCE FOR SSI [14-09-2015(online)].pdf | 2015-09-14 |
| 4 | 3522-MUM-2015-Power of Attorney-110316.pdf | 2018-08-11 |
| 5 | Drawing [14-09-2015(online)].pdf | 2015-09-14 |
| 5 | ABSTRACT1.jpg | 2018-08-11 |
| 6 | OnlinePostDating(1).pdf | 2018-08-11 |
| 6 | Description(Provisional) [14-09-2015(online)].pdf | 2015-09-14 |
| 7 | OnlinePostDating.pdf | 2018-08-11 |
| 7 | Form 3 [02-12-2016(online)].pdf | 2016-12-02 |
| 8 | OTHERS [14-01-2017(online)].pdf | 2017-01-14 |
| 8 | 3522-MUM-2015-FORM 18 [30-11-2017(online)].pdf | 2017-11-30 |
| 9 | 3522-MUM-2015-ORIGINAL UNDER RULE 6 (1A)FORM 5-15-02-2017.pdf | 2017-02-15 |
| 9 | Drawing [14-01-2017(online)].pdf | 2017-01-14 |
| 10 | Assignment [14-01-2017(online)].pdf | 2017-01-14 |
| 10 | Description(Complete) [14-01-2017(online)].pdf_408.pdf | 2017-01-14 |
| 11 | Description(Complete) [14-01-2017(online)].pdf | 2017-01-14 |
| 12 | Assignment [14-01-2017(online)].pdf | 2017-01-14 |
| 12 | Description(Complete) [14-01-2017(online)].pdf_408.pdf | 2017-01-14 |
| 13 | 3522-MUM-2015-ORIGINAL UNDER RULE 6 (1A)FORM 5-15-02-2017.pdf | 2017-02-15 |
| 13 | Drawing [14-01-2017(online)].pdf | 2017-01-14 |
| 14 | 3522-MUM-2015-FORM 18 [30-11-2017(online)].pdf | 2017-11-30 |
| 14 | OTHERS [14-01-2017(online)].pdf | 2017-01-14 |
| 15 | Form 3 [02-12-2016(online)].pdf | 2016-12-02 |
| 15 | OnlinePostDating.pdf | 2018-08-11 |
| 16 | Description(Provisional) [14-09-2015(online)].pdf | 2015-09-14 |
| 16 | OnlinePostDating(1).pdf | 2018-08-11 |
| 17 | ABSTRACT1.jpg | 2018-08-11 |
| 17 | Drawing [14-09-2015(online)].pdf | 2015-09-14 |
| 18 | 3522-MUM-2015-Power of Attorney-110316.pdf | 2018-08-11 |
| 18 | EVIDENCE FOR SSI [14-09-2015(online)].pdf | 2015-09-14 |
| 19 | EVIDENCE FOR SSI [14-09-2015(online)].pdf_28.pdf | 2015-09-14 |
| 19 | 3522-MUM-2015-Form 1-110316.pdf | 2018-08-11 |
| 20 | FORM28 [14-09-2015(online)].pdf | 2015-09-14 |
| 20 | 3522-MUM-2015-Correspondence-110316.pdf | 2018-08-11 |
| 21 | FORM28 [14-09-2015(online)].pdf_29.pdf | 2015-09-14 |
| 21 | 3522-MUM-2015-FER.pdf | 2020-07-21 |
| 1 | 2020-07-2014-59-55E_20-07-2020.pdf |