Abstract: The present disclosure relates to field of optimization of transport, and envisages a system and method for transportation optimization. The system (100) comprises a database (102), an input means (104), a request processing unit (106), a transport optimisation unit (108), and a billing unit (112). The input means (104) is configured to receive request for articles to be transported from user to supplier. The transport optimisation unit (108) evaluates the request based on the pre-determined evaluating rules, decides a route based on the pre-determined routing rules and the evaluated data, and allocates a vehicle based on the routes, the pre-determined vehicle allocation rules and the tracking rules. The billing unit (112) generates a bill for the request, based on the pre-determined billing rules, and sends notifications to the user and supplier. The present disclosure provides optimum utilization of transportation cost, average loading efficiency of vehicles, and improves traceability of vehicles.
Claims:WE CLAIM :
1. A system (100) for transportation optimization comprising:
• an input means (104) configured to receive a request for articles to be transported from a user to a supplier;
• a database (102) configured to store a list of locations of a plurality of pre-determined suppliers, a list of plurality of pre-determined articles, a list of pre-determined weightage associated with each of said articles, a list of a plurality of pre-determined vehicles with type, load capacity and charge of said vehicles, a pre-determined set of billing rules, a pre-determined set of transport receipt (TR) modifying rules, a pre-determined set of TR validating rules, a pre-determined set of vehicle allocation rules, a pre-determined set of routing rules, a pre-determined set of evaluating rules, a pre-determined set of tracking rules and a list of pre-determined templates for said digital tickets;
• a request processing unit (106) configured to cooperate with said input means (104), to generate digital tickets associated with said request;
• a transport optimisation unit (108) configured to cooperate with said request processing unit (106) and said database (102), further configured to evaluate said request based on said pre-determined evaluating rules, decide a route based on said pre-determined routing rules and said evaluated data, and allocate a vehicle based on said routes, said pre-determined vehicle allocation rules and said tracking rules; and
• a billing unit (112) configured to cooperate with said database (102) and said transport optimisation unit (108), further configured to generate a bill for said request, based on said pre-determined billing rules, further configured to send notifications to said user and said supplier,
wherein said request processing unit (106), said transport optimisation unit (108), and said billing unit (112), are implemented using one or more processor(s).
2. The system (100) as claimed in claim 1, wherein said request includes location of said supplier, quantity of said articles, weightage of said articles, and date for transportation.
3. The system (100) as claimed in claim 1, wherein said request processing unit (106) includes:
• a ticket generator (114) configured to cooperate with said database (102), said transport optimisation unit (108), and said billing unit (112) to generate digital tickets associated with said requests.
4. The system (100) as claimed in claim 1, wherein said transport optimisation unit (108) includes:
• a request evaluator (116) configured to cooperate with said database (102) and said request processing unit (106), further configured to evaluate said request based on said pre-determined evaluating rules;
• a route planner (118) configured to cooperate with said database (102) and request evaluator (116), further configured to decide said route based on said pre-determined routing rules and said evaluation data;
• a vehicle tracker (120) configured to cooperate with said database (102) and said route planner (118), further configured to track all vehicles on said planned route, based on said tracking rules and said planned route;
• a vehicle allocator (122) configured to cooperate with said database (102) and said vehicle tracker (120), further configured to allocate said vehicle, based on said planned route and said pre-determined vehicle allocation rules;
• a trip generation unit (124) configured to cooperate with said database (102) and said vehicle allocator (122), further configured to generate a new trip or modify an existing trip based on said request.
5. The system (100) as claimed in claim 4, wherein said allocated vehicle is fitted with a GPS, at least one image capturing unit and a load sensor.
6. The system (100) as claimed in claim 5, wherein said vehicle tracker (120) employs geo-fencing.
7. The system (100) as claimed in claim 1, wherein said allocated vehicle can be fitted with a plurality of pallets, to optimise utilisation of said vehicle space.
8. The system (100) as claimed in claim 1, wherein said billing unit (112) includes:
• a bill estimation unit (126) configured to cooperate with said database (102) and said transport optimisation unit (108), further configured to generate a bill of said request, based on said pre-determined billing rules, and a transport receipt;
• a dispatch unit (128) configured to cooperate with said database (102) and said bill estimation unit (122) to dispatch said requested articles, based on said transport receipt;
• a modify transport receipt unit (130) configured to cooperate with said transport optimisation unit (108) and said input means (104), further configured to modify said transport receipt generated, based on said pre-determined TR modifying rules and inputs provided through said input means (104); and
• a validate transport receipt unit (132) configured to cooperate with said transport optimisation unit (108), to validate said modified transport receipt and said pre-determined TR validating rules.
9. The system (100) as claimed in claim 1, wherein a notification generation unit (110) is configured to cooperate with said database (102) and said billing unit (112) to send notifications to said user, said supplier and driver on respective notification devices.
10. The system (100) as claimed in claim 9, wherein said notification generation unit (110) includes:
• an order delay notification unit (134) configured to cooperate with said database (102) and said billing unit (112), to initiate a timer when said requested articles are dispatched and further configured to send notifications after said timer times off after a pre-determined time period, before receiving an acknowledgement through said input means (104).
11. The system (100) as claimed in claim 9, wherein said notification devices are selected from the group, not limited to, consisting of handheld device, smart phone, laptop, desktop, palmtop, iPad, and tablet.
12. The system (100) as claimed in claim 1, wherein said user can be a selected from the group, not limited to, purchaser, buyer, and seller.
13. The system (100) as claimed in claim 1, wherein said input means (104) is selected from the group, not limited to, consisting of a third party application, an ERP system or any device.
14. The system (100) as claimed in claim 1, wherein said request can be pick articles request or/and drop articles request, and said trip planned can be from said supplier to said user, or said user to said supplier.
15. A method for transportation optimization, said method comprising the following steps:
• receiving, by an input means (104), a request for articles to be transported from a user to a supplier;
• storing, by a database (102), a list of names and locations of a plurality of pre-determined suppliers, a list of plurality of pre-determined articles, a list of pre-determined weightage associated with each of said articles, a list of a plurality of pre-determined vehicles with type, load capacity and charge of said vehicles, a pre-determined set of billing rules, a pre-determined set of transport receipt (TR) modifying rules, a pre-determined set of transport receipt (TR) validating rules, a pre-determined set of vehicle allocation rules, a pre-determined set of routing rules, a pre-determined set of evaluating rules, a pre-determined set of tracking rules and a list of pre-determined templates for said digital tickets;
• generating, by a request processing unit (106), digital tickets associated with said request;
• evaluating, by a transport optimisation unit (108), said request based on said pre-determined evaluating rules;
• deciding, by said transport optimisation unit (108), a route based on said pre-determined routing rules and said evaluated data;
• allocating, by said transport optimisation unit (108), a vehicle based on said routes, said pre-determined vehicle allocation rules and said tracking rules;
• generating, by a billing unit (112), a bill for said request, based on said pre-determined billing rules; and
• sending, by said billing unit (112), notifications to said user and said supplier.
, Description:
FIELD
The present disclosure is related to optimization of transport.
BACKGROUND
In conventional systems, the process of transporting a material from one place to another is managed manually and the material is typically delivered as per the convenience of vendors. There is a greater dependency on manpower, since no time frame exists for issue and receipt of material from a supplier. Additionally, there is a lack of a single window for material receipt from different suppliers. The lack of control on delivery of material from one supplier to another supplier causes an unnecessary movement of man, material and the handling equipment. Further, conventional systems fail to make the optimum utilization of the vehicles which increases the cost of transporting the material. The overall low utilisation of vehicles and lack of optimum utilisation of each trip of the vehicle adds to an increased level of the carbon footprint. Moreover, the traceability of the vehicles is missing in the conventional systems.
Therefore, there is a need to provide a system and a method for transportation optimization that alleviates the above mentioned drawbacks of the conventional systems.
OBJECTS
Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows:
It is an object of the present disclosure to ameliorate one or more problems of the prior art or to at least provide a useful alternative.
An object of the present disclosure is to provide a system for transportation optimization and a method thereof.
Another object of the present disclosure is to provide the system and method for improving the traceability of vehicles.
Yet another object of the present disclosure is to provide the system and method that automatically manages and optimizes routes for pickup and delivery.
Still another object of the present disclosure is to provide the system and method that provides the optimum utilization of transportation cost and average loading efficiency of vehicles.
Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
SUMMARY
The present disclosure envisages a system and method for transportation optimization. The system for transportation optimization comprises an input means, a database, a request processing unit, a transport optimisation unit and a billing unit.
The input means is configured to receive a request for articles to be transported from a user to a supplier.
The database is configured to store a list of locations of a plurality of pre-determined suppliers, a list of plurality of pre-determined articles, a list of pre-determined weightage associated with each of the articles, a list of a plurality of pre-determined vehicles with type, load capacity and charge of the vehicles, a pre-determined set of billing rules, a pre-determined set of transport receipt (TR) modifying rules, a pre-determined set of transport receipt (TR) validating rules, a pre-determined set of vehicle allocation rules, a pre-determined set of routing rules, a pre-determined set of evaluating rules, a pre-determined set of tracking rules and a list of pre-determined templates for the digital tickets.
The request processing unit is configured to cooperate with the input means, to generate digital tickets associated with the request.
The transport optimisation unit is configured to cooperate with the request processing unit and the database, to evaluate the request based on the pre-determined evaluating rules, decide a route based on the pre-determined routing rules and the evaluated data, and allocate a vehicle based on the routes, the pre-determined vehicle allocation rules and the tracking rules.
The billing unit is configured to cooperate with the database and the transport optimisation unit to generate a bill for the request, based on the pre-determined billing rules, and further configured to send notifications to the user and the supplier.
The request processing unit, the transport optimisation unit, and the billing unit, are implemented using one or more processor(s).
In an embodiment, the request includes location of the supplier, quantity of the articles, weightage of the articles, and date for transportation.
In another embodiment, the request processing unit includes a ticket generator configured to cooperate with the database, the transport optimisation unit, and the billing unit to generate digital tickets associated with the requests.
In yet another embodiment, the transport optimisation unit includes a request evaluator, a route planner, a vehicle tracker, a vehicle allocator, and a trip generation unit.
The request evaluator is configured to cooperate with the database and the request processing unit to evaluate the request based on the pre-determined evaluating rules.
The route planner is configured to cooperate with the database and request evaluator to decide the route based on the pre-determined routing rules and the evaluation data.
The vehicle tracker is configured to cooperate with the database and the route planner to track all vehicles on the planned route, based on the tracking rules and the planned route.
The vehicle allocator is configured to cooperate with the database and the vehicle tracker to allocate the vehicle, based on the planned route and the pre-determined vehicle allocation rules.
The trip generation unit configured to cooperate with the database and the vehicle allocator to generate a new trip or modify an existing trip based on the request.
In yet another embodiment, the allocated vehicle is fitted with a GPS, at least one image capturing unit and a load sensor.
In still another embodiment, the vehicle tracker employs geo-fencing.
In an embodiment, the allocated vehicle can be fitted with a plurality of pallets, to optimise utilisation of the vehicle space.
The billing unit includes a bill estimation unit, a dispatch unit, a modify transport receipt unit, and a validate transport receipt unit.
The bill estimation unit is configured to cooperate with the database and the transport optimisation unit, and further configured to generate a bill of the request, based on the pre-determined billing rules, and a transport receipt.
The dispatch unit is configured to cooperate with the database and the bill estimation unit to dispatch the requested articles, based on the transport receipt.
The modify transport receipt unit is configured to cooperate with the transport optimisation unit and the input means, to modify the transport receipt generated, based on the pre-determined TR modifying rules and inputs provided through the input means.
The validate transport receipt unit is configured to cooperate with the transport optimisation unit, to validate the modified transport receipt and the pre-determined TR validating rules.
In another embodiment, the notification generation unit is configured to cooperate with the database and the billing unit to send notifications to the user, the supplier and driver on respective notification devices. The notification generation unit includes an order delay notification unit configured to cooperate with the database and the billing unit, to initiate a timer when the requested articles are dispatched and further configured to send notifications after the timer times off after a pre-determined time period, before receiving an acknowledgement through the input means.
In yet another embodiment, the notification devices are selected from the group, not limited to, consisting of handheld device, smart phone, laptop, desktop, palmtop, iPad, and tablet.
In still another embodiment, the user can be a selected from the group, not limited to, purchaser, buyer, and seller.
In an embodiment, the input means is selected from the group, not limited to, consisting of a third party application, an ERP system or any device.
In another embodiment, the request can be pick articles request or/and drop articles request, and the trip planned can be from the supplier to the user, or the user to the supplier.
The present disclosure envisages a method for transportation optimization.
BRIEF DESCRIPTION OF ACCOMPANYING DRAWING
A system for transportation optimization and a method thereof of the present disclosure will now be described with the help of the accompanying drawing, in which:
Figure 1 illustrates a block diagram of a system for transportation optimization; and
Figures 2a and 2b illustrate a flow chart of a method for transportation optimization.
LIST OF REFERENCE NUMERALS USED IN THE DESCRIPTION AND DRAWING
Reference Numeral Reference
100 System
102 Database
104 Input means
106 Request processing unit
108 Transport optimisation unit
110 Notification generation unit
112 Billing unit
114 Ticket generator
116 Request evaluator
118 Route planner
120 Vehicle tracker
122 Vehicle allocator
124 Trip generation unit
126 Bill estimation unit
128 Dispatch unit
130 Modify transport receipt unit
132 Validate transport receipt unit
134 Order delay notification unit
DETAILED DESCRIPTION
Embodiments, of the present disclosure, will now be described with reference to the accompanying drawing.
Embodiments are provided so as to thoroughly and fully convey the scope of the present disclosure to the person skilled in the art. Numerous details are set forth, relating to specific components, and methods, to provide a complete understanding of embodiments of the present disclosure. It will be apparent to the person skilled in the art that the details provided in the embodiments should not be construed to limit the scope of the present disclosure. In some embodiments, well-known processes, well-known apparatus structures, and well-known techniques are not described in detail.
The terminology used, in the present disclosure, is only for the purpose of explaining a particular embodiment and such terminology shall not be considered to limit the scope of the present disclosure. As used in the present disclosure, the forms "a,” "an," and "the" may be intended to include the plural forms as well, unless the context clearly suggests otherwise. The terms "comprises," "comprising," “including,” and “having,” are open ended transitional phrases and therefore specify the presence of stated features, integers, steps, operations, elements, modules, units and/or components, but do not forbid the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The particular order of steps disclosed in the method and process of the present disclosure is not to be construed as necessarily requiring their performance as described or illustrated. It is also to be understood that additional or alternative steps may be employed.
When an element is referred to as being "mounted on," “engaged to,” "connected to," or "coupled to" another element, it may be directly on, engaged, connected or coupled to the other element. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed elements.
The terms first, second, third, etc., should not be construed to limit the scope of the present disclosure as the aforementioned terms may be only used to distinguish one element, component, region, layer or section from another component, region, layer or section. Terms such as first, second, third etc., when used herein do not imply a specific sequence or order unless clearly suggested by the present disclosure.
Terms such as “inner,” “outer,” "beneath," "below," "lower," "above," "upper," and the like, may be used in the present disclosure to describe relationships between different elements as depicted from the figures.
A system for transportation optimization of the present disclosure is described with reference to Figure 1 of the accompanying drawing.
The system (100) for transportation optimization (hereinafter referred as “system”) (100) comprises a database (102), input means (104), a request processing unit (106), a transport optimisation unit (108), and a billing unit (112).
The input means (104) is configured to receive a request for articles to be transported from a user to a supplier. In an embodiment, the input means (104) is selected from the group, not limited to, consisting of a third party application, an ERP system or any device.
The request can be pick articles request or/and drop articles request, and the trip planned can be from the supplier to the user, or the user to the supplier.
The request placed includes the location of the supplier, quantity of the articles, weightage of the articles, and date for transportation. The user can be selected from the group, not limited to, purchaser, buyer, and seller.
The database (102) is configured to store a list of locations of a plurality of pre-determined suppliers, a list of plurality of pre-determined articles, a list of pre-determined weightage associated with each of the articles, a list of a plurality of pre-determined vehicles with type, load capacity and charge of the vehicles, a pre-determined set of billing rules, a pre-determined set of transport receipt (TR) modifying rules, a pre-determined set of transport receipt (TR) validating rules, a pre-determined set of vehicle allocation rules, a pre-determined set of routing rules, a pre-determined set of evaluating rules, a pre-determined set of tracking rules and a list of pre-determined templates for the digital tickets.
In an embodiment, the database (102) is configured to receive new lists of suppliers, vehicles and articles, in addition to the existing lists.
The request processing unit (106) is configured to cooperate with the input means (104), to generate digital tickets associated with the request. The ticket generator (114) is configured to cooperate with the database (102), the transport optimisation unit (108), and the billing unit (112) to generate digital tickets associated with the requests.
In an embodiment, the digital tickets generated is selected from the group, not limited to, consisting of 57F4 challan, gate entry, Advance shipping notice (ASN), purchase order, and manual challan. The digital tickets are generated by filling pre-determined templates stored in the database (102) with the required values for digital tickets
The transport optimisation unit (108) is configured to cooperate with the request processing unit (106) and the database (102). The transport optimisation unit (108) is further configured to evaluate the request based on the pre-determined evaluating rules, decide a route based on the pre-determined routing rules and the evaluated data, and allocate a vehicle based on the routes, the pre-determined vehicle allocation rules and the tracking rules.
The transport optimisation unit (108) includes a request evaluator (116), a route planner (118), a vehicle tracker (120), a vehicle allocator (122), and a trip generation unit (124).
The request evaluator (116) is configured to cooperate with the database (102) and the request processing unit (106), to evaluate the request based on the pre-determined evaluating rules. The evaluation of the request is on the basis of the quantity of the articles, the total weight to be transported, and the location of the supplier.
The route planner (118) is configured to cooperate with the database (102) and request evaluator (116), to decide the route based on the pre-determined routing rules and the evaluation data. The route is decided based on parameters like weight to be carried, available vehicles, and supplier location, accessed through the database (102). The route is planned and ranked based on the parameters and the pre-determined routing rules, and the highest ranking route is selected for the articles to be transported.
The vehicle tracker (120) tracks all the vehicles as the vehicles are fitted with a GPS, at least one image capturing unit and a load sensor. The vehicle tracker (120) tracks the vehicles on the planned route and the best available vehicle based on the planned route and the pre-determined vehicle allocation rules, is allocated by the vehicle allocator (122). The pre-determined vehicle allocation rules includes the vehicle load, fuel consumption of the vehicle, distance to be covered till the supplier, pick/drop load, charge of the vehicle, per km charge of the vehicle, and the vehicle load must be greater than the articles load.
The trip generation unit (124) is configured to cooperate with the database (102) and the vehicle allocator (122), to generate a new trip or modify an existing trip based on the request. A new trip can be planned if the request is an urgent request. An ongoing trip can be modified if the allocated vehicle is completing a trip.
The billing unit (112) is configured to cooperate with the database (102) and the transport optimisation unit (108) to generate a bill for the request, based on the pre-determined billing rules, and sends notifications to the user, the supplier and driver.
The billing unit (112) includes a bill estimation unit (126), a dispatch unit (128), a modify transport receipt unit (130), and a validate transport receipt unit (132).
The bill estimation unit (126) is configured to cooperate with the database (102) and the transport optimisation unit (108), to generate a bill of the request, based on the pre-determined billing rules, and a transport receipt. The bill estimation unit (126) generates a transport receipt signal, once the trip is generated or altered. The ticket generator (114) is configured to generate a transport receipt for the request.
The dispatch unit (128) is configured to cooperate with the database (102) and the bill estimation unit (126) to dispatch the requested articles, based on the transport receipt. The driver receives the transport receipt and a manual challan is generated, to release the articles for transportation.
A notification generation unit (110) is configured to cooperate with the database (102) and the billing unit (112) to send notifications to the user, the supplier and driver on respective notification devices.
The notification generation unit (110) includes an order delay notification unit (134) configured to cooperate with the database (102) and the billing unit (112), to initiate a timer when the requested articles are dispatched and further configured to send notifications after the timer times off after a pre-determined time period, before receiving an acknowledgement through the input means (104).
In an embodiment, the notification devices are selected from the group, not limited to, consisting of handheld device, smart phone, laptop, desktop, palmtop, iPad, and tablet.
When the trip is over, the transport receipt can be modified either in the case when the vehicle did not reach the supplier location, or when the supplies were not received. The reason is entered through the input means (104). The modify transport receipt unit (130) is configured to cooperate with the transport optimisation unit (108) and the input means (104), to modify the transport receipt generated, based on the pre-determined TR modifying rules and inputs provided through the input means (104). The existing TR is modified and a bill modified signal is generated. The bill estimation unit (126) is configured to alter the bill and generate a re-schedule signal. The transport optimisation unit (108) is configured to re-schedule a trip to the supplier.
The validate transport receipt unit (132) is configured to cooperate with the transport optimisation unit (108), to validate the modified transport receipt and the pre-determined TR validating rules. The transport receipt or the modified transport receipt is validated against an acknowledgement from the supplier through the input means (104).
In an embodiment, the vehicle tracker (120) employs geo-fencing. The vehicle tracker (120) generates a route deviation signal in an event if the current location of the vehicle is deviated from the planned path, for the pre-determined amount of time. The notification generation unit (110) is configured to receive the signal, and send notifications to the supplier, and the user. The notification generation unit (110) is configured to provide the driver details to the supplier and the user, in order to communicate with the driver.
The request processing unit (106), transport optimisation unit (108), and billing unit (112) are implemented using one or more processor(s).
The processor is configured to cooperate with the memory to receive and process the pre-determined rules to obtain a set of system operating commands. The processor may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any device that manipulates signals based on operational instructions. Among other capabilities, the processor is configured to fetch and execute the set of predetermined rules stored in the memory to control modules of the system (100).
In another embodiment, the allocated vehicle can be fitted with a plurality of pallets, to optimise utilisation of the vehicle space.
In yet another embodiment, the system (100) communicates through a wired or wireless network.
In still another embodiment, the system (100) reduces the level of carbon footprint, as the vehicles are optimally utilised, and the vehicle picks and drops in the same trip, instead of scheduling a new trip.
Figures 2a and 2b illustrate a flowchart of a method for transportation optimization.
• Step 202: Receiving, by an input means (104), a request for articles to be transported from a user to a supplier.
• Step 204: Storing, by a database (102), a list of names and locations of a plurality of pre-determined suppliers, a list of plurality of pre-determined articles, a list of pre-determined weightage associated with each of the articles, a list of a plurality of pre-determined vehicles with type, load capacity and charge of the vehicles, a pre-determined set of billing rules, a pre-determined set of transport receipt (TR) modifying rules, a pre-determined set of transport receipt (TR) validating rules, a pre-determined set of vehicle allocation rules, a pre-determined set of routing rules, a pre-determined set of evaluating rules, a pre-determined set of tracking rules and a list of pre-determined templates for the digital tickets.
• Step 206: Generating, by a request processing unit (106), digital tickets associated with the request.
• Step 208: Evaluating, by a transport optimisation unit (108), the request based on the pre-determined evaluating rules.
• Step 210: Deciding, by the transport optimisation unit (108), a route based on the pre-determined routing rules and the evaluated data.
• Step 212: Allocating, by the transport optimisation unit (108), a vehicle based on the routes, the pre-determined vehicle allocation rules and the tracking rules.
• Step 214: Generating, by a billing unit (112), a bill for the request, based on the pre-determined billing rules.
• Step 216: Sending, by the billing unit (112), notifications to the user and the supplier.
TECHNICAL ADVANCEMENTS
The present disclosure described herein above has several technical advantages including, but not limited to, the realization of a system for transportation optimization and a method thereof, that:
• improves the traceability of vehicles;
• automatically manages and optimizes routes for pickup and delivery; and
• provides optimum utilization of transportation cost and average loading efficiency of vehicles.
The embodiments herein and the various features and advantageous details thereof are explained with reference to the non-limiting embodiments in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
The foregoing description of the specific embodiments so fully revealed the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
The use of the expression “at least” or “at least one” suggests the use of one or more elements or ingredients or quantities, as the use may be in the embodiment of the disclosure to achieve one or more of the desired objects or results.
Any discussion of documents, acts, materials, devices, articles or the like that has been included in this specification is solely for the purpose of providing a context for the disclosure. It is not to be taken as an admission that any or all of these matters form a part of the prior art base or were common general knowledge in the field relevant to the disclosure as it existed anywhere before the priority date of this application.
The numerical values mentioned for the various physical parameters, dimensions or quantities are only approximations and it is envisaged that the values higher/lower than the numerical values assigned to the parameters, dimensions or quantities fall within the scope of the disclosure, unless there is a statement in the specification specific to the contrary.
While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
| # | Name | Date |
|---|---|---|
| 1 | 201921003011-STATEMENT OF UNDERTAKING (FORM 3) [24-01-2019(online)].pdf | 2019-01-24 |
| 2 | 201921003011-PROOF OF RIGHT [24-01-2019(online)].pdf | 2019-01-24 |
| 3 | 201921003011-FORM 1 [24-01-2019(online)].pdf | 2019-01-24 |
| 4 | 201921003011-DRAWINGS [24-01-2019(online)].pdf | 2019-01-24 |
| 5 | 201921003011-DECLARATION OF INVENTORSHIP (FORM 5) [24-01-2019(online)].pdf | 2019-01-24 |
| 6 | 201921003011-COMPLETE SPECIFICATION [24-01-2019(online)].pdf | 2019-01-24 |
| 7 | 201921003011-Proof of Right (MANDATORY) [25-03-2019(online)].pdf | 2019-03-25 |
| 8 | Abstract1.jpg | 2019-04-22 |
| 9 | 201921003011-ORIGINAL UR 6(1A) FORM 1-250319.pdf | 2020-01-07 |
| 10 | 201921003011-FORM-26 [08-02-2021(online)].pdf | 2021-02-08 |
| 11 | 201921003011-FORM 18 [09-06-2022(online)].pdf | 2022-06-09 |
| 12 | 201921003011-FER.pdf | 2022-10-11 |
| 13 | 201921003011-FORM 3 [19-11-2022(online)].pdf | 2022-11-19 |
| 14 | 201921003011-OTHERS [07-12-2022(online)].pdf | 2022-12-07 |
| 15 | 201921003011-FER_SER_REPLY [07-12-2022(online)].pdf | 2022-12-07 |
| 16 | 201921003011-COMPLETE SPECIFICATION [07-12-2022(online)].pdf | 2022-12-07 |
| 17 | 201921003011-CLAIMS [07-12-2022(online)].pdf | 2022-12-07 |
| 18 | 201921003011-US(14)-HearingNotice-(HearingDate-15-05-2024).pdf | 2024-04-30 |
| 19 | 201921003011-FORM-26 [02-05-2024(online)].pdf | 2024-05-02 |
| 20 | 201921003011-Correspondence to notify the Controller [02-05-2024(online)].pdf | 2024-05-02 |
| 21 | 201921003011-Written submissions and relevant documents [30-05-2024(online)].pdf | 2024-05-30 |
| 22 | 201921003011-MARKED COPIES OF AMENDEMENTS [30-05-2024(online)].pdf | 2024-05-30 |
| 23 | 201921003011-FORM 13 [30-05-2024(online)].pdf | 2024-05-30 |
| 24 | 201921003011-AMMENDED DOCUMENTS [30-05-2024(online)].pdf | 2024-05-30 |
| 25 | 201921003011-PatentCertificate19-09-2024.pdf | 2024-09-19 |
| 26 | 201921003011-IntimationOfGrant19-09-2024.pdf | 2024-09-19 |
| 1 | searchE_11-10-2022.pdf |