Description: FIELD OF INVENTION
[0001] Embodiments of the present disclosure relates to rental management systems, and more particularly to a system and a method for fleet management to facilitate renting of vehicles.
BACKGROUND
[0002] Recent years have witnessed increasing interest and development in the field of vehicle sharing. Riders may individually book one vehicle for a trip and then release the vehicle on usage. Commercial car rental companies typically provide a web site that allows customers to reserve a car for rental for a specified date and time.
[0003] There are several travel agencies and individual cab drivers who find it difficult to connect with online customers. Such drivers don’t have proper webpages or team to manage their webpages to market their services on online platforms. Moreover, this creation and maintenance of webpages adds additional overhead to expenditure.
[0004] Conventionally, most of fleet operators struggle to offer services on a marketplace for customers where the customers can search and browse through various options provided by the fleet operators. Furthermore, the conventional systems lack any effective mechanisms to manage booking transfer in real time to avoid the issue of unavailability of drivers or cab.
[0005] Hence, there is a need for an improved system for fleet management and a method to operate the same and therefore address the aforementioned issues.
BRIEF DESCRIPTION
[0006] In accordance with one embodiment of the disclosure, a system for fleet management is disclosed. The system includes a hardware processor. The system also includes a memory coupled to the hardware processor. The memory comprises a set of program instructions in the form of a plurality of subsystems and configured to be executed by the hardware processor.
[0007] The plurality of subsystems includes a request handler subsystem. The request handler subsystem configured to receive a request for booking a trip from one or more users. The plurality of subsystems also includes a vehicle booking subsystem. The vehicle booking subsystem is configured to identify one or more available vehicles based on the received request using an artificial intelligence-based vehicle management model. The vehicle booking subsystem is also configured to assign the identified one or more available vehicles to the one or more users for completing the requested trip.
[0008] The vehicle booking subsystem is also configured to track real time location of the assigned one or more vehicles upon starting the trip based on real time location information associated with the assigned one or more vehicles.
[0009] The plurality of subsystems also includes a trip management subsystem. The trip management subsystem is configured to determine whether the trip has been terminated based on tracking information associated with the assigned one or more vehicles and user feedback. The trip management subsystem is configured to identify available one or more vehicles in proximity to current location of the one or more users based on the artificial intelligence-based vehicle management model if the trip has been terminated. The trip management subsystem is also configured to transfer the received request for the trip to the identified available one or more vehicles in proximity to the current location of the one or more users.
[0010] The trip management subsystem is also configured to assign the identified available one or more vehicles in proximity to the registered one or more users. The trip management subsystem is also configured to resuming the trip with the assigned available one or more vehicles in proximity. The trip management subsystem is also configured to complete the transferred request for the trip by reaching the target location of the trip.
[0011] In accordance with one embodiment of the disclosure, a method for fleet management is disclosed. The method includes receiving a request for booking a trip from one or more users. The method also includes identifying one or more available vehicles based on the received request using an artificial intelligence-based vehicle management model. The method also includes assigning the identified one or more available vehicles to the one or more users for completing the requested trip.
[0012] The method also includes tracking real time location of the assigned one or more vehicles upon starting the trip based on real time location information associated with the assigned one or more vehicles. The method also includes determining whether the trip has been terminated based on tracking information associated with the assigned one or more vehicles and user feedback. The method also includes identifying available one or more vehicles in proximity to current location of the one or more users based on the artificial intelligence-based vehicle management model if the trip has been terminated.
[0013] The method also includes transfer the received request for the trip to the identified available one or more vehicles in proximity to the current location of the one or more users. The method also includes assigning the identified available one or more vehicles in proximity to the registered one or more users. The method also includes resuming the trip with the assigned available one or more vehicles in proximity. The method also includes completing the transferred request for the trip by reaching the target location of the trip.
[0014] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will follow by reference to specific embodiments thereof, which are illustrated in the appended figures. It is to be appreciated that these figures depict only typical embodiments of the disclosure and are therefore not to be considered limiting in scope. The disclosure will be described and explained with additional specificity and detail with the appended figures.
BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The disclosure will be described and explained with additional specificity and detail with the accompanying figures in which:
[0016] FIG. 1 is a block diagram illustrating an exemplary computing system for fleet management in accordance with an embodiment of the present disclosure;
[0017] FIG. 2 is a flowchart illustrating an exemplary process of assigning the one or more vehicles for a trip in accordance with an embodiment of the present disclosure;
[0018] FIG. 3A-C is an exemplary flowchart for managing a vehicle assignment in accordance with an embodiment of the present disclosure;
[0019] FIG. 4 is a block diagram illustrating interaction of different entities for fleet management in accordance with an embodiment of the present disclosure;
[0020] FIG. 5 is a block diagram illustrating signup process of different entities for fleet management in accordance with an embodiment of the present disclosure;
[0021] FIG. 6 A-B is a block diagram illustrating a client and a vendor relationship for fleet management in accordance with an embodiment of the present disclosure;
[0022] FIG. 7 A-B is a block diagram illustrating the request trip model as designed for fleet management in accordance with an embodiment of the present disclosure;
[0023] FIG. 8 A-B is a block diagram illustrating the interaction mechanism of different entities corresponding to fleet management in accordance with an embodiment of the present disclosure;
[0024] FIG. 9 A-B is a flowchart illustrating a trip lifecycle corresponding to fleet management in accordance with an embodiment of the present disclosure;
[0025] FIG. 10 A-B is a flowchart process illustrating a request lifecycle corresponding to fleet management in accordance with an embodiment of the present disclosure;
[0026] FIG. 11 A-B are snapshots of the dashboard of the computing system for fleet management in accordance with an embodiment of the present disclosure; and
[0027] FIG. 12 is a process flowchart illustrating an exemplary method for fleet management in accordance with an embodiment of the present disclosure.
[0028] Further, those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.
DETAILED DESCRIPTION
[0029] For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiment illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated online platform, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.
[0030] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or subsystems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures or additional components. Appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but not necessarily do, all refer to the same embodiment.
[0031] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.
[0032] In the following specification and the claims, reference will be made to a number of terms, which shall be defined to have the following meanings. The singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise.
[0033] A computer system (standalone, client or server computer system) configured by an application may constitute a “subsystem” that is configured and operated to perform certain operations. In one embodiment, the “subsystem” may be implemented mechanically or electronically, so a subsystem may comprise dedicated circuitry or logic that is permanently configured (within a special-purpose processor) to perform certain operations. In another embodiment, a “subsystem” may also comprise programmable logic or circuitry (as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations.
[0034] Accordingly, the term “subsystem” should be understood to encompass a tangible entity, be that an entity that is physically constructed permanently configured (hardwired) or temporarily configured (programmed) to operate in a certain manner and/or to perform certain operations described herein.
[0035] FIG. 1 is a block diagram illustrating an exemplary computing system 100 for fleet management in accordance with an embodiment of the present disclosure. The computing system 100 provides an easy interaction platform of one or more users availing for vehicles and one or more fleet operators renting the vehicles. In such embodiment, the computing system 100 act as a marketplace for unorganized vehicle, whereby one or more fleet operators compete with other similar vendors by defining their own rate cards.
[0036] The computing system 100 includes a hardware processor 108. The computing system 100 also includes a memory 102 coupled to the hardware processor 108. The memory 102 comprises a set of program instructions in the form of a plurality of subsystems and configured to be executed by the hardware processor 108. Input/output (I/O) devices 110 (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.
[0037] The hardware processors 108, as used herein, means any type of computational circuit, such as, but not limited to, a microprocessor, a microcontroller, a complex instruction set computing microprocessor, a reduced instruction set computing microprocessor, a very long instruction word microprocessor, an explicitly parallel instruction computing microprocessor, a digital signal processor, or any other type of processing circuit, or a combination thereof.
[0038] The memory 102 includes a plurality of subsystems stored in the form of executable program which instructs the hardware processor 108 via bus 104 to perform the method steps. The plurality of subsystems has following subsystems: a request handler subsystem 112, a vehicle booking subsystem 114, and a trip management subsystem 116.
[0039] Computer memory elements may include any suitable memory device(s) for storing data and executable program, such as read only memory, random access memory, erasable programmable read only memory, electrically erasable programmable read only memory, hard drive, removable media drive for handling memory cards and the like. Embodiments of the present subject matter may be implemented in conjunction with program modules, including functions, procedures, data structures, and application programs, for performing tasks, or defining abstract data types or low-level hardware contexts. Executable program stored on any of the above-mentioned storage media may be executable by the hardware processors 108.
[0040] The plurality of subsystems includes a registration subsystem. The registration subsystem is configured to register one or more fleet operators using respective operator data. In one embodiment, the operator data includes personal details of the one or more fleet operators, driver personal details, one or more vehicle details, one or more garage details, rate cards, documents and billing details.
[0041] The registration subsystem is also configured to register one or more users using user data. In one embodiment, the user data includes user personal details and one or more vehicle requirement parameters. In one exemplary embodiment, the one or more users and the one or more fleet operators before using the computing system 100 platform, first registers in the computing system 100 with all such registration data. The one or more users and the one or more fleet operators may avail help only with complete registration. In such embodiment, the one or more users may include corporate users or an individual user.
[0042] Furthermore, by the help of the user data and the operator data, the computing system 100 may also create individual profile for each of the one or more users and each of the one or more fleet operators. Such profiles are created by a profile generation subsystem.
[0043] The profile generation subsystem is configured to generate a fleet operator profile for one or more fleet operator. The fleet operator profile is segmented into first set of categories. In one such embodiment, each of the first set of categories includes fleet operator information, driver information, one or more vehicle information, garage information, rate card information and bill invoice information. In another such embodiment, any particular fleet operator may access any category data though the created profile.
[0044] The profile generation subsystem is configured to create a customer profile for one or more customers. The customer profile is segmented into second set of categories. In such embodiment, each of the second set of categories includes customer information and one or more vehicle requirement parameters. The profile generation subsystem is configured to create a corporate client profile. The corporate client profile is segmented into third set of categories. In such embodiment, each of the third set of categories includes corporate information and one or more vehicle requirement parameters. In one specific embodiment, the corporate information includes Goods and Services Tax Identification Number (GSTIN), corporate personal information and the like.
[0045] The plurality of subsystems includes a request handler subsystem 112. The request handler subsystem 112 is configured to receive a request for booking a trip from one or more users. In one specific embodiment, a user provides the request for a vehicle through the profile booking space. During booking the one or more users specifically provides one or more vehicle requirement parameters.
[0046] The plurality of subsystems also includes a vehicle booking subsystem 114. The vehicle booking subsystem 114 is configured to identify one or more available vehicles based on the received request using an artificial intelligence-based vehicle management model. In such embodiment, to identify one or more available vehicles based on the received request using an artificial intelligence-based vehicle management model, the vehicle booking subsystem 114 in first step maps the vehicle requirement parameters with the prestored operator data and customer data using artificial intelligence-based vehicle management model.
[0047] The vehicle booking subsystem 114 in second step identifies availability of at least one among the one or more vehicles based on the mapping, real time status of the one or more vehicles, real time location of the one or more vehicles and driver availability details.
[0048] In such embodiment, the computing system 100 detects real time location of the one or more vehicles through location capturing devices associated with the vehicle. The location capturing devices associated with the vehicle may include Global Positioning System (GPS) system associated with the vehicle.
[0049] The vehicle booking subsystem 114 is also configured to assign the identified one or more available vehicles to the one or more users for completing the requested trip. In one specific embodiment, a bidding system may be used for assigning one or more available vehicles to the one or more users. For example, one or more available vehicles with minimum renting charge as described in the billing details during registration is identified first for assigning.
[0050] The vehicle booking subsystem 114 assigns electric vehicles for trip based on multiple factors such as current charge, the pickup or drop points, electric vehicle charging stations and the like. The vehicle booking subsystem 114 monitors through one or more sensors all the real time status of the vehicle to monitor stated multiple factors.
[0051] The vehicle booking subsystem114 is also configured to track real time location of the assigned one or more vehicles upon starting the trip based on real time location information associated with the assigned one or more vehicles. Such tracking is important to understand the real time condition of the trip as assigned. The bidding process help in selecting a vendor or a driver for subcontracting a trip.
[0052] The plurality of subsystems also includes a trip management subsystem 116. The trip management subsystem 116 is configured to determine whether the trip has been terminated based on tracking information associated with the assigned one or more vehicles and user feedback. In such embodiment, from the tracked information of the assigned one or more vehicles, the computing system 100 may understand the condition of the on-going trip.
[0053] In one specific embodiment, the trip is determined to be terminated based on one or more termination factors. The one or more termination factors includes break down of the assigned one or more vehicles, driver related issues and non-acceptance of the request for the trip by one or more registered fleet operators. In such embodiment, the tracking information associated with the assigned one or more vehicles is shown to be same. In another embodiment, the user may also provide written feedback regarding the termination of the trip.
[0054] In one embodiment, the driver related issues may include issues particular related to driver such as driver emergency, driver health and the like. In another embodiment, break down of the assigned one or more vehicles include vehicle operation problem, vehicle fuel issue and the like.
[0055] The trip management subsystem 116 is configured to identify available one or more vehicles in proximity to current location of the one or more users based on the artificial intelligence-based vehicle management model if the trip has been terminated. In such embodiment, the to identify available one or more vehicles in proximity, the trip management subsystem 116 maps the vehicle requirement parameters with the prestored operator data and user data using artificial intelligence-based vehicle management model.
[0056] Further, the trip management subsystem 116 identifies availability of at least one among the one or more vehicles on proximity based on the mapping, real time status of the one or more vehicles, real time location of the one or more vehicles and driver availability details. In such embodiment, the real time status of the one or more vehicles includes the geographic location of the one or more vehicle that is mapped by the trip management subsystem 116.
[0057] The trip management subsystem 116 is also configured to automatically transfers the received request for the trip to the identified available one or more vehicles in proximity to the current location of the one or more users. In such embodiment, as the trip received request is transferred to the identified available one or more vehicles in proximity, the one or more users may finish the on-going trip without any mush hassle.
[0058] The trip management subsystem 116 is also configured to assign the identified available one or more vehicles in proximity to the registered one or more users. The trip management subsystem 116 is also configured to resuming the trip with the assigned available one or more vehicles in proximity. The trip management subsystem 116 is also configured to complete the transferred request for the trip by reaching the target location of the trip.
[0059] The plurality of subsystems also includes a billing subsystem. The billing subsystem is configured to generate a billing invoice for the completed trip. The billing invoice is generated for the one or more registered fleet operators associated with the current trip or new fleet operator.
[0060] The plurality of subsystems also includes a payment subsystem. The payment subsystem is configured to receive a bill amount from the one or more customers corresponding to the generated billing invoice. In such embodiment, the bill amount from the one or more customers may be cleared via one or more third-party payment preferences.
[0061] FIG. 2 is a flowchart illustrating an exemplary process 200 of assigning the one or more vehicles for a trip in accordance with an embodiment of the present disclosure. At step 202, the computing system 100 first loads the trip request data. At step 204, the computing system 100 loads preset vehicles. At step 206, preset vehicle list is displayed. At step 208, all vehicle lists are loaded. In such embodiment, the computing system 100 also loads the list of all vehicles. At step 212, list of all vehicles is displayed for choosing along with preset vehicle list 204.
[0062] A step 210, from the provided list, the computing system 100 selects a vehicle. In one particular embodiment, for the selected vehicle, the computing system 100 may assign at step 216, change driver at step 218, or de-select the vehicle at step 220. At step 222, the computing system 100 may get the vehicle assigned to a user. In one embodiment, the computing system 100 may also help in real time adding of a vehicle 214 in the vehicle list.
[0063] FIG. 3A-C is an exemplary flowchart for managing a vehicle assignment 300, 302 and 304 in accordance with an embodiment of the present disclosure. At step 302, a corporate provides details for special requirements for vehicles. At step 304, the computing system 100 determines whether any approvable process for such trip is required of not. At step 306, the computing system 100 determines whether the trip is approved or not based on the provided special requirement details. At step 308, the trip creation may be rejected. At step 310, the trip may be created, whereby the trip may be created by combining multiple trip request or selected billing details.
[0064] At step 312, a vehicle is deployed according to trip created at step 310. Multiple supervisor (Fleet operator, and other vendors) may provide vehicle from step 316 and 318. At step 314, the trip Details are pushed through SMS/Email/Driver App./Employee App. At step 320, a driver determines whether to accept the trip or not. Upon accepting, at step 324, driver may track the trip through driver application. At step 322, the employees may track through web application. At step 326, the fleet operator may track the trip through web application.
[0065] At step 328, invoice is generated after trip completion. At step 330, the invoice is notified to employees. At step 332, the invoice is notified to transport admin. At step 334, the invoice is notified to the fleet operator or sub admins. At 336, reports of the trip may be exported. At step 338, a payment gateway is provided for payment. At step 340, the fleet operator or the sub vendor receives payment.
[0066] FIG. 4 is a block diagram illustrating interaction of different entities for fleet management 400 in accordance with an embodiment of the present disclosure. In one embodiment, the major entities involved in the computing system interactions are corporate 402, fleet operator 408, and driver 414. In corporate entity, major participants may be transport admin 404 of a corporate or a simple passenger 406. Transport admin 404 of a corporate may represent people from the corporate 418. Passenger 406 may represent individuals who are not corporate 420.
[0067] In fleet operator 408 entity, major participants may be owner 410 or a delegated employee 412. Owner 410 may be a driver who are fleet owners themselves 422. Delegated employees 412 are workers of the fleet owners 424. In such embodiment, the driver entity 414 may also be represented by a single driver 416.
[0068] FIG. 5 is a block diagram illustrating signup process of different entities 500 for fleet management in accordance with an embodiment of the present disclosure. At step 502, the fleet operator starts the signup process. At step 504, fleet operator do-self signup. At step 506, the fleet operator invites a driver. At step 508, the fleet operator invites a corporate customer. At step 506, the fleet operator invites a passenger.
[0069] At step 512, a driver is connected for providing service. At step 514, the driver uploads driving licence. At step 516, the driver accepts the fleet operator invitation and signs up. At step 518, a corporate is connected to provide service. At step 520, payment terms are reviewed. At step 522, GSTIN pin is added to the computing system 100. At step 526, a passenger is invited within a corporate. At step 528, a passenger is invited. At step 530, a passenger accepts the fleet operator invitation and signs up.
[0070] FIG. 6 A-B is a block diagram illustrating a client and a vendor relationship 600, 602 for fleet management in accordance with an embodiment of the present disclosure. FIG 6 A showcase the employee registration process with respect to creation of request, and employee registration with name, phone ID, email ID and the like.
[0071] FIG. 7 A-B is a block diagram illustrating the request trip model 700, 702 as designed for fleet management in accordance with an embodiment of the present disclosure.
[0072] FIG. 8 A-B is a block diagram illustrating the interaction mechanism of different entities 800, 802 corresponding to fleet management in accordance with an embodiment of the present disclosure.
[0073] FIG. 9 A-B is a flowchart illustrating a trip lifecycle 900, 902 and 904 corresponding to fleet management in accordance with an embodiment of the present disclosure.
[0074] FIG. 10 A-B is a flowchart process illustrating a request lifecycle 1000, 1002 corresponding to fleet management in accordance with an embodiment of the present disclosure.
[0075] FIG. 11 A-B are snapshots of the dashboard 1100, 1102 of the computing system 100 for fleet management in accordance with an embodiment of the present disclosure. FIG 11A showcase the different categories for a profile that may be created. The dashboard shows categories such as organizations, drivers, garages, vehicles, billing invoices and the like.
[0076] FIG. 12 is a process flowchart illustrating an exemplary method 1200 for fleet management in accordance with an embodiment of the present disclosure.
[0077] At step 1202, a request is received for booking a trip from one or more users. In one aspect of the present embodiment, the request is received for booking the trip from the one or more users by a request handler subsystem. The request comprises vehicle requirement parameters, a source location and a target location.
[0078] At step 1204, one or more available vehicles is identified based on the received request using an artificial intelligence-based vehicle management model. In one aspect of the present embodiment, the one or more available vehicles is identified by a vehicle booking subsystem.
[0079] Furthermore, the method includes mapping the vehicle requirement parameters with the prestored operator data and user data using artificial intelligence-based vehicle management model. The method also includes identifying availability of at least one among the one or more vehicles based on the mapping, real time status of the one or more vehicles, real time location of the one or more vehicles and driver availability details.
[0080] At step 1206, the identified one or more available vehicles is assigned to the one or more users for completing the requested trip. In one aspect of the present embodiment, the identified one or more available vehicles is assigned by the vehicle booking subsystem.
[0081] At step 1208, real time location of the assigned one or more vehicles is tracked upon starting the trip based on real time location information associated with the assigned one or more vehicles. In one aspect of the present embodiment, the real time location of the assigned one or more vehicles is tracked by the vehicle booking subsystem.
[0082] At step 1210, whether the trip has been terminated is determined based on tracking information associated with the assigned one or more vehicles and user feedback. In one aspect of the present embodiment, whether the trip has been terminated is determined by a trip management subsystem.
[0083] The on-going trip is terminated based on one or more termination factors. The one or more termination factors comprises break down of the assigned one or more vehicles, break down of the assigned one or more proximity vehicles, driver related issues and non-acceptance of the request for the trip by one or more registered fleet operators.
[0084] At step 1212, available one or more vehicles in proximity to current location of the one or more users is identified based on the artificial intelligence-based vehicle management model if the trip has been terminated. In one aspect of the present embodiment, available one or more vehicles in proximity to current location of the one or more users is identified by the trip management subsystem.
[0085] At step 1214, the received request for the trip is transferred to the identified available one or more vehicles in proximity to the current location of the one or more users. In one aspect of the present embodiment, the received request for the trip is transferred by the trip management subsystem.
[0086] At step 1216, the identified available one or more vehicles in proximity is assigned to the registered one or more users. In one aspect of the present embodiment, the identified available one or more vehicles in proximity is assigned by the trip management subsystem.
[0087] At step 1218, the trip with the assigned available one or more vehicles is resumed in proximity. In one aspect of the present embodiment, the trip with the assigned available one or more vehicles is resumed by the trip management subsystem.
[0088] At step 1220, the transferred request for the trip is completed by reaching the target location of the trip. In one aspect of the present embodiment, the transferred request for the trip is completed by the trip management subsystem.
[0089] The method 1200 includes registering one or more fleet operators using respective operator data. The operator data comprises personal details of the one or more fleet operators, driver personal details, one or more vehicle details, one or more garage details, rate cards, documents and billing details.
[0090] The method 1200 also includes registering one or more users using user data. The user data comprises user personal details and one or more vehicle requirement parameters.
[0091] The method 1200 also includes generating a fleet operator profile for one or more fleet operators. The fleet operator profile is segmented into first set of categories. Each of the first set of categories comprises fleet operator information, driver information, one or more vehicle information, garage information, rate card information and bill invoice information.
[0092] The method 1200 also includes generating a customer profile for one or more customers. The customer profile is segmented into second set of categories. Each of the second set of categories comprises customer information and one or more vehicle requirement parameters.
[0093] The method 1200 also includes generating a corporate profile for one or more corporate. The corporate profile is segmented into third set of categories. Each of the third set of categories comprises corporate organization information and one or more vehicle requirement parameters.
[0094] The method 1200 includes generating a billing invoice for the completed trip, wherein the billing invoice is generated for the one or more registered fleet operators associated with the current trip or new fleet operator.
[0095] The method also includes receiving a bill amount from the one or more customers corresponding to the generated billing invoice.
[0096] Various embodiments of the present disclosure provide a platform for fleet management. Fleet operators provide easily transport through multi-level networks. The computing system 100 helps the fleet operators create their own website profile and offer transport services by managing their vehicles and rate card packages. Multi-Level Network with visibility for the nodes to information only with upstream and downstream nodes in the network. The fleet operators on particular network interact with their corresponding networks through offline modes. When the vehicles are idle, it is better for the fleet operators to run trips at least to cover the fixed expenses
[0097] The computing system 100 offer services on a marketplace for users to search and browse through various options provided by the fleet operators. In such embodiment, the user can place a trip request and Fleet operators can compete by bidding for the trip. The computing system 100 uses artificial intelligence-based vehicle management model to assign electric vehicles for any trips based on the current charge, the pickup/drop points and electric vehicle charging stations.
[0098] The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, order of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts need to be necessarily performed. Also, those acts that are not dependant on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples.
[0099] The written description describes the subject matter herein to enable any person skilled in the art to make and use the embodiments. The scope of the subject matter embodiments is defined by the claims and may include other modifications that occur to those skilled in the art. Such other modifications are intended to be within the scope of the claims if they have similar elements that do not differ from the literal language of the claims or if they include equivalent elements with insubstantial differences from the literal language of the claims.
[0100] The embodiments herein can comprise hardware and software elements. The embodiments that are implemented in software include but are not limited to, firmware, resident software, microcode, etc. The functions performed by various modules described herein may be implemented in other modules or combinations of other modules. For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can comprise, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
[0101] The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid-state memory, magnetic tape, a removable computer diskette, a random-access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.
[0102] Input/output (I/O) devices (as shown in FIG. 1) (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters.
[0103] A representative hardware environment for practicing the embodiments may include a hardware configuration of an information handling/computer system in accordance with the embodiments herein. The system herein comprises at least one processor or central processing unit (CPU). The CPUs are interconnected via system bus to various devices such as a random-access memory (RAM), read-only memory (ROM), and an input/output (I/O) adapter. The I/O adapter can connect to peripheral devices, such as disk units and tape drives, or other program storage devices that are readable by the system. The system can read the inventive instructions on the program storage devices and follow these instructions to execute the methodology of the embodiments herein.
[0104] The system further includes a user interface adapter that connects a keyboard, mouse, speaker, microphone, and/or other user interface devices such as a touch screen device (not shown) to the bus to gather user input. Additionally, a communication adapter connects the bus to a data processing network, and a display adapter connects the bus to a display device which may be embodied as an output device such as a monitor, printer, or transmitter, for example.
[0105] A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention. When a single device or article is described herein, it will be apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be apparent that a single device/article may be used in place of the more than one device or article, or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the invention need not include the device itself.
[0106] The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed.
[0107] The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, order of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts need to be necessarily performed. Also, those acts that are not dependant on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples.

 
, Claims: WE CLAIM:
1. A system (100) for fleet management, the system (100) comprising:
a hardware processor (108); and
a memory (102) coupled to the hardware processor (108), wherein the memory (102) comprises a set of program instructions in the form of a plurality of subsystems, configured to be executed by the hardware processor (108), wherein the plurality of subsystems comprises:
a request handler subsystem (112) configured to receive a request for booking a trip from one or more users, wherein the request comprises vehicle requirement parameters, a source location and a target location;
a vehicle booking subsystem (114) configured to:
identify one or more available vehicles based on the received request using an artificial intelligence-based vehicle management model;
assign the identified one or more available vehicles to the one or more users for completing the requested trip, wherein the trip is accepted by one or more registered fleet operators; and
track real time location of the assigned one or more vehicles upon starting the trip based on real time location information associated with the assigned one or more vehicles;
a trip management subsystem (116) configured to:
determine whether the trip has been terminated based on tracking information associated with the assigned one or more vehicles and user feedback;
identify available one or more vehicles in proximity to current location of the one or more users based on the artificial intelligence-based vehicle management model if the trip has been terminated, wherein the one or more vehicles in proximity are associated with at least one of: current fleet operator associated with the current trip or new fleet operator;
transfer the received request for the trip to the identified available one or more vehicles in proximity to the current location of the one or more users;
assign the identified available one or more vehicles in proximity to the registered one or more users;
resuming the trip with the assigned available one or more vehicles in proximity; and
complete the transferred request for the trip by reaching the target location of the trip.
2. The system (100) as claimed in claim 1, further comprising a registration subsystem configured to:
register one or more fleet operators using respective operator data, wherein the operator data comprises personal details of the one or more fleet operators, driver personal details, one or more vehicle details, one or more garage details, rate cards, documents and billing details; and
register one or more users using user data, wherein the user data comprises user personal details and one or more vehicle requirement parameters.
3. The system (100) as claimed in claim 1, wherein to identify one or more available vehicles based on the received request using an artificial intelligence-based vehicle management model, the vehicle booking subsystem (114) is configured to:
map the vehicle requirement parameters with the prestored operator data and user data using artificial intelligence-based vehicle management model; and
identify availability of at least one among the one or more vehicles based on the mapping, real time status of the one or more vehicles, real time location of the one or more vehicles and driver availability details.
4. The system (100) as claimed in claim 1, further comprises a profile generation subsystem, wherein the profile generation subsystem is configured to generate:
a fleet operator profile for one or more fleet operators, wherein the fleet operator profile is segmented into first set of categories, wherein each of the first set of categories comprises fleet operator information, driver information, one or more vehicle information, garage information, rate card information and bill invoice information;
a customer profile for one or more customers, wherein the customer profile is segmented into second set of categories, wherein each of the second set of categories comprises customer information and one or more vehicle requirement parameters; and
a corporate profile for one or more corporate, wherein the corporate profile is segmented into third set of categories, wherein each of the third set of categories comprises corporate organization information and one or more vehicle requirement parameters.
5. The system (100) as claimed in claim 1, further comprises a billing subsystem configured to generate a billing invoice for the completed trip, wherein the billing invoice is generated for the one or more registered fleet operators associated with the current trip or new fleet operator.
6. The system (100) as claimed in claim 1, further comprises a payment subsystem is configured to receive a bill amount from the one or more customers corresponding to the generated billing invoice.
7. The system (100) as claimed in claim 1, wherein the trip is determined to be terminated based on one or more termination factors, wherein the one or more termination factors comprises break down of the assigned one or more vehicles, break down of the assigned one or more proximity vehicles, driver related issues and non-acceptance of the request for the trip by one or more registered fleet operators.
8. A method (1200) for fleet management, the method (1200) comprising:
receiving, by a processor, a request for booking a trip from one or more users (1202), wherein the request comprises vehicle requirement parameters, a source location and a target location;
identifying, by the processor, one or more available vehicles based on the received request using an artificial intelligence-based vehicle management model (1204);
assigning, by the processor, the identified one or more available vehicles to the one or more users for completing the requested trip (1206), wherein the trip is accepted by one or more registered fleet operators;
tracking, by the processor, real time location of the assigned one or more vehicles upon starting the trip based on real time location information associated with the assigned one or more vehicles (1208);
determining, by the processor, whether the trip has been terminated based on tracking information associated with the assigned one or more vehicles and user feedback (1210);
identifying, by the processor, available one or more vehicles in proximity to current location of the one or more users based on the artificial intelligence-based vehicle management model if the trip has been terminated (1212), wherein the one or more vehicles in proximity are associated with at least one of: current fleet operator associated with the current trip or new fleet operator
transferring, by the processor, the received request for the trip to the identified available one or more vehicles in proximity to the current location of the one or more users (1214);
assigning, by the processor, the identified available one or more vehicles in proximity to the registered one or more users (1216);
resuming, by the processor, the trip with the assigned available one or more vehicles in proximity (1218); and
completing, by the processor, the transferred request for the trip by reaching the target location of the trip (1220).
9. The method (1200) as claimed in claim 8, further comprising registering, by the processor, one or more fleet operators using respective operator data, wherein the operator data comprises personal details of the one or more fleet operators, driver personal details, one or more vehicle details, one or more garage details, rate cards, documents and billing details.
10. The method (1200) as claimed in claim 8, further comprising registering, by the processor, one or more users using user data, wherein the user data comprises user personal details and one or more vehicle requirement parameters.
11. The method (1200) as claimed in claim 8, wherein identify one or more available vehicles based on the received request using an artificial intelligence-based vehicle management model, the method (1200) comprises:
mapping the vehicle requirement parameters with the prestored operator data and user data using artificial intelligence-based vehicle management model; and
identifying availability of at least one among the one or more vehicles based on the mapping, real time status of the one or more vehicles, real time location of the one or more vehicles and driver availability details.
12. The method (1200) as claimed in claim 8, further comprising generating a fleet operator profile for one or more fleet operators, wherein the fleet operator profile is segmented into first set of categories, wherein each of the first set of categories comprises fleet operator information, driver information, one or more vehicle information, garage information, rate card information and bill invoice information.
13. The method (1200) as claimed in claim 8, further comprising generating a customer profile for one or more customers, wherein the customer profile is segmented into second set of categories, wherein each of the second set of categories comprises customer information and one or more vehicle requirement parameters.
14. The method (1200) as claimed in claim 8, further comprising generating a corporate profile for one or more corporate, wherein the corporate profile is segmented into third set of categories, wherein each of the third set of categories comprises corporate organization information and one or more vehicle requirement parameters.
15. The method (1200) as claimed in claim 8, further comprises generating a billing invoice for the completed trip, wherein the billing invoice is generated for the one or more registered fleet operators associated with the current trip or new fleet operator.
16. The method (1200) as claimed in claim 8, further comprises receiving a bill amount from the one or more customers corresponding to the generated billing invoice.
17. The method (1200) as claimed in claim 8, wherein the on-going trip is terminated based on one or more termination factors, wherein the one or more termination factors comprises break down of the assigned one or more vehicles, break down of the assigned one or more proximity vehicles, driver related issues and non-acceptance of the request for the trip by one or more registered fleet operators.
Dated this 29th day of April 2022

Vidya Bhaskar Singh Nandiyal
Patent Agent (IN/PA-2912)
Agent for applicant