Abstract: A system for monitoring RMC (Ready Mix Concrete) quality control is provided. The system includes a first (Internet of Things) device installed in a concrete batching plant and configured for operating one or more sensing devices; processing the sensed data and communicating the processed data to a central server. The system also includes a panel board data recording device comprising a second IoT device, installed in a panel board of the concrete batching plant and configured for recording and tracking the entire batch data, at least a minuscule manipulation to calibration in the concrete batching plant and the panel board and communicating the recorded data by the second Iot device to the central server. Moreover, the system also includes a computing device comprising a processor, a memory coupled to the processor, and a third IoT device installed in a batching plant operating system of the computing device. The memory stores a plurality of modules to be executed by the processor, wherein the plurality of modules are configured for recording and tracking the entire batch data, detecting and recording at least a minuscule manipulation to calibration in the concrete batching plant and the panel board and communicating the processed data to the central server. The third IoT device is configured to receive, store and send the processed data from the processor, to the central server.
SYSTEM AND METHOD FOR RMC (READY MIX CONCRETE) QUALITY
CONTROL
FIELD OF TECHNOLOGY
[001] The present invention generally relates to a system and a method for a RMC (Ready Mix Concrete) quality control and more particularly to the system and the method for a real-time evaluation and monitoring of the RMC quality control during manufacturing and delivery to a consumer.
BACKGROUND
[002] Over the last few decades, a major portion of mixing of concrete for construction of a building is usually done at a construction site. The construction site situation is always a complex, resulting into an inconvenience at the construction site. The inconvenience at the construction site have an impact on the mixing of different raw materials for the preparation of concrete in calculated mix-proportions, thus affecting the quality of the concrete production. Hence, the idea of RMC (Ready Mix Concrete) product thus evolves.
[003] Particularly, RMC is a product which is produced after carefully mixing of about 5-7 different raw materials in calculated mix-proportions. However, RMC has a shelf life of about only 3 to 4 hours. After the expiration of the said period, the concrete loses most of the strength gaining phenomenon and thus prove to be useless. The demand of the RMC product is getting popularity day by day. However, the majority of builders and developers are facing problems while buying the RMC product from the manufacturer/supplier. The problems of the builders and the developers are not only limited to the quality of the standard concrete of the RMC product, but also to the quantity, prevention of a pilferage of the concrete during transit of the RMC product and while breakdown of a plant during the procurement of the concrete.
[004] However, to check the exact quantity or the mix proportions of the RMC product after production is an impossible task. Buyers generally rely on a batch-slip to know the exact quantity or the mix proportions of RMC product produced after production. The batch-slip is accompanied by every vehicle and is produced by a supplier. The batch-slip can be easily forged by the supplier in a one or more way. The one or more way includes manufacturing of sub-standard quality concrete and sending lesser quantities of concrete in each transit mixer vehicle. In addition, the suppliers can also edit or delete the detail of the actual mix-proportions
recorded in the local database. Moreover, there is also a probability of material pilferage of the RMC product during transit by the supplier between a manufacturing plant and a project site.
[005] Several methods are currently being practiced at a project site level to verify the quality and quantity of the RMC. In the context of the measurement of the quantity of concrete, the exact dimensions of the area in which concrete is being poured into before and after placing concrete are recorded and verified, but this method cannot be used in the measurement of all the structural elements. Another way is to install weigh bridges in project locations and take the weight details of every RMC vehicle before and after concreting, however this method takes a lot of space in project sites and is very costly. However, these methods only verify the quantity but does not give the exact quantity of the raw materials used in the production of the RMC product.
[006] Furthermore, in case of the plant breakdown for one or more reasons, the buyer
cannot procure the concrete from different suppliers, during the procurement of the concrete, because of the change in the material properties (for example, chemical structure, sources, quality and the like). In addition, the buyer cannot wait for a time gap, the time gap between the breakdown and the repair of the plant. The time gap and the change in the supplier affect the homogeneity of the concrete and may result in a substandard quality work and structural deformities of the concrete.
[007] To overcome at least some of the above mentioned problems, there exists a need for a system and a method for online evaluation and monitoring of the RMC quality control. Moreover, the system and the method is needed that provides the real-time evaluation and monitoring of the RMC quality control during manufacturing and delivery of the RMC product to the consumer.
SUMMARY
[008] This summary is provided to introduce a selection of concepts in simple manners that are further described in the detailed description of the disclosure. This summary is not intended to identify key or essential inventive concepts of the subject matter nor is it intended to determine the scope of the disclosure.
[009] Briefly, according to an exemplary embodiment, a system for Ready Mix Concrete (RMC) quality control is provided. The system includes a first (Internet of Things) device
installed in a concrete batching plant and configured for operating one or more sensing devices; processing the sensed data and communicating the processed data to a central server. The system also includes a panel board data recording device comprising a second IoT device, installed in a panel board of the concrete batching plant and configured for recording and tracking the entire batch data, at least a minuscule manipulation to calibration in the concrete batching plant and the panel board and communicating the recorded data by the second Iot device to the central server. Moreover, the system also includes a computing device comprising a processor, a memory coupled to the processor, and a third IoT device installed in a batching plant operating system of the computing device. The memory stores a plurality of modules to be executed by the processor, wherein the plurality of modules are configured for recording and tracking the entire batch data, detecting and recording at least a minuscule manipulation to calibration in the concrete batching plant and the panel board and communicating the processed data to the central server. The third IoT device is configured to receive, store and send the processed data from the processor, to the central server.
[0010] Briefly, according to an exemplary embodiment, a method for monitoring RMC (Ready Mix Concrete) quality control is provided. The method includes installing a first IoT (Internet of Things) device, in a concrete batching plant for operating one or more sensing devices; processing the sensed data and communicating the processed data to a central server. The method also includes installing a panel board data recording device comprising a second IoT device, in a panel board of the concrete batching plant for recording and tracking the entire batch data, at least a minuscule manipulation to calibration in the concrete batching plant and the panel board, and communicating the recorded data by the second IoT device, to the central server. Furthermore, the method includes executing a set of instructions in a batching plant operating system of a computing device, for recording and tracking the entire batch data, detecting and recording at least a minuscule manipulation to calibration in the concrete batching plant and the panel board and communicating the said recorded data to the central server. In addition, the method includes installing a third IoT device in the batching plant operating system of the computing device for receiving and storing the said recorded data, and communicating the said recorded data to the central server.
[0011] The summary above is illustrative only and is not intended to be in any way limiting. Further aspects, exemplary embodiments, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DESCRIPTION OF THE FIGURES
[0012] These and other features, aspects, and advantages of the exemplary embodiments can be better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
[0013] FIG. 1 illustrates a system showing the implementation of a central server interconnected with one or more parts of a batching plant premise and configured to administer quality control for a ready mix concrete (RMC), according to an embodiment of the present disclosure;
[0014] FIG. 2 illustrates a generic system view of a RMC plant premise and a GPS system along with a system of geo-fences configured for delivering a quality controlled RMC to a consumer, according to an embodiment of the present disclosure;
[0015] FIG. 3 is a flow chart illustrating a method for monitoring a RMC (Ready Mix Concrete) quality control, according to an embodiment of the present disclosure;
[0016] FIG. 4 illustrates a system for verifying and linking the results of a concrete cube testing, to a specific order according to an embodiment of the present disclosure; and
[0017] FIG. 5 is a flow chart illustrating a method for verifying and linking the results of a concrete cube testing, to a specific order according to an embodiment of the present disclosure.
[0018] Further, skilled artisans 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 invention so as not to obscure the figures with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
DETAILED DESCRIPTION
[0019] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiments illustrated in the figures and specific language
will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.
[0020] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the invention and are not intended to be restrictive thereof.
[0021] 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 comprise only those steps but may comprise other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by "comprises... a" does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components. Appearances of the phrase “in an embodiment”, “in another embodiment” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
[0022] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The system, methods, and examples provided herein are illustrative only and not intended to be limiting.
[0023] In addition to the illustrative aspects, exemplary embodiments, and features described above, further aspects, exemplary embodiments of the present disclosure will become apparent by reference to the drawings and the following detailed description.
[0024] FIG. 1 illustrates a system 100 showing the implementation of a central server interconnected with one or more parts of a batching plant premise and configured to administer quality control for a RMC, according to an embodiment of the present disclosure. In particular, the system 100 illustrates a plant premise 102. The plant premise 102 further includes a concrete batching plant 104, a panel board 108, a computing device 116 comprising a processor and a memory (118). A first IoT (Internet of Things) device 106-A is installed in the batching
plant 104. a second IoT device 106-B also called as panel board data recording device is installed in the panel board 108. A third IoT device 106-C is installed in a batching plant operating system of the computing device 116. The components of the plant premises 102 are connected to a central server 112 and a consumer 114 via a communications means or a network. It may be noted that the system 100 is shown to have the IoT (Internet of Things) devices 106-A through 106-D; however, those skilled in the art would appreciate that the system 100 can include plurality of IoT (Internet of Things) devices 106-A through 106-N.
[0025] For conciseness, the first IoT device 106-A is a hardware device installed in the concrete batching plant 104, the second IoT device 106-B is a hardware device installed in panel board (PLC device) 108, the third IoT device 106-C (smart Iot device) is a hardware device installed in computing device 116 and the IoT device 106-D is a cycle data software installed in the batching plant operating system of the computing device 116.
[0026] Typically, the concrete batching plant 104 includes a production counter in the plant premise 102 and is a counter where the records of a one or more production units are maintained. The concrete batching plant 104 further includes a batch set which includes a batch start auto, a batch start semi auto, a batch start manual, a batch report view, and the like. The concrete batching plant 104 further includes a one or more silos and is used to store the raw materials used for the preparation of the RMC product. The raw materials used for the preparation of the RMC product further, is comprised of cement, sand, stone, admixture, water-cement ratio, sand ratio, the ratio of bone and bone, and the like. The concrete batching plant (RMC batching plant) 104 is generally divided into various components as described above. All these above components are connected to an electronic panel board 108 known as panel board through various sensors.
[0027] The IoT (Internet of Things) device 106-A is installed in the concrete batching plant 104. It may be noted that, although only IoT device 106-A is shown in FIG. 1, one or more IoT (Internet of Things) devices may be installed in the concrete batching plant 104. The one or more IoT (Internet of Things) devices (106-A) are configured for operating one or more sensing devices, processing the sensed data and communicating the processed data to the central server 112. The one or more sensing devices are weight capturing sensors installed in the concrete batching plant 104. The weight capturing sensors are configured for capturing at least a miniscule alteration made in the course of preparation of RMC in the concrete batching plant 104 and further configured for processing the captured miniscule alteration by comparing with
an actual sensed data obtained by a one or more batching plant sensors to detect any tampering in the course of preparation of RMC in the concrete batching plant 104. Here, one or more batching plant sensors are the sensors installed by a manufacturer of RMC and the IoT device (106-A) includes the sensing devices installed by the system 100.
[0028] In addition, the weight capturing sensors are further configured for communicating the processed data by sending an alert notification to the central server 112. For example, the weight capturing sensors installed in the concrete batching plant 104 sends a notification to the central server 112 when they are tampered. In one example, the weight capturing sensors and batching plant sensors may be calibrated to the exact weights with the help of government or third party or authorised agency. Whenever there is a difference in captured values between batching plant sensors (installed by the manufacturer) and weight capturing sensors (IoT devices 106-A), an alert is generated to notify the change. The alerts are generated via the central server 112 to notify the one or more changes. Hence the plant calibration is tracked from sensors level, and the correct weight of the materials is recorded.
[0029] The panel board 108 is an electronic board and also known as a PLC board. In one embodiment, the panel board data recording device 110 is installed in the panel board 108 and is configured for recording the entire batch data, any manipulation in the concrete batching plant 104 and any changes in the calibration at the panel board level. For example, the panel board data recording device 110 (PLC device) installed in the panel board 108 of the concrete batching plant 104 will record any changes in the plant calibration at the panel board level. Here, the word panel board, electronic panel board and the PLC board refer the same and are used interchangeably in the description.
[0030] The panel board data recording device 110 (IoT device 106-B) installed in the panel board 108 of the batching plant 104 performs one or more functions. The panel board data recording device 110 is configured to record all the production details of the batching plant PLC board itself. Hence, the data is recorded in the panel board data recording device 110 before entering into the database of the plant premise 102. The panel board data recording device 110 also has internal memory storage, thus storing all the real-time data recorded in the panel board data recording device. In addition, the panel board data recording device 110 has an internal internet connected to the central server 112, transmitting real-time data to the central server 112 at every instant. Further, the PLC data recording device 110 has a program. The program notifies or alerts the central server 112 regarding the connectivity with the PLC device
or with the internet. Furthermore, the panel board data recording device 110 also has its own internal battery with the help of which the panel board data recording device 110 can sustain for one or more hours without power supply and can still record all the production data if any through manual batching. In addition, the panel board data recording device 110 comprises a program which notifies/alerts the central server 112 even if it is either not connected to the internet.
[0031] In one embodiment, the plant premises 102 includes the computing device 116 interconnected with the concrete batching plant 104 and the panel board 108. The computing device 116 is connected to the IoT device 106-C and IoT device 106-D. The computing device 116 includes a processor and a memory (116). The memory stores a plurality of modules to be executed by the processor. Further, the plurality of the modules are configured for recording and tracking the entire batch data, detecting and recording at least a minuscule manipulation to calibration in the concrete batching plant 104 and the panel board 108 and communicating the processed data to the central server 112.
[0032] Further, the third IoT device 106-C is a hardware installed in a concrete batching plant operating system of the computing device 116 and configured to store the data received from IoT device 106-D (Cycle data software) and transmit to central server 112. The IoT device 106-C has an inbuilt memory, internet and battery.
[0033] The third IoT device 106-C is connected through a port to the batching plant operating system of the computing device 116. The third IoT device 106-C is configured to perform one or more functions. The IoT device 106-C has its own internal internet connection through which the IoT device 106-C is connected to the central server 112. The IoT device 106-C also has own an internal memory storage. The internal memory storage stores all the real-time data received from a software installed in the computing device 116 (cycle data software). Moreover, the IoT device (106-C) has a program, for notifying or alerting the central server 112 in case, it is not connected to the cycle data software (installed by the system 100) or to the internet. In addition, the IoT device 106-C has its own internal battery with the help of which the device sustains for one or more hours without a power supply.
[0034] The IoT device 106-D includes a software (a batching tracking module) installed in a concrete batching plant operating system of the computing device 116 to record and transmit data to the central server 112. The installed batching tracking module in the concrete batching
plant operating system of the computing device 116 is a customized software (Cycle data software) and configured to execute a computer-readable instructions for detecting and recording at least a minuscule manipulation to calibration in the concrete batching plant 104 and the panel board 108 and communicating the processed data to the central server 112.
[0035] In one embodiment, the customized software (Cycle data software) is installed in the batching plant operating system of the computing device 116. This software when installed is directly connected to plant’s local database and central server 112, constantly sending ping to the central server 112. As soon as any batch data is recorded in the database it is captured in real-time by cycle data software and is sent to third IoT device 106-C and to the central server 112 if internet is available with the concrete batching plant operating system. Apart from real¬time, cycle data software also captures the data after a fixed interval of time which helps in recording the changes in database if any during that period of time. Also the cycle data software tracks any changes that are done in the database (created by the manufacturer) and records the same for further use. All this data is transmitted to the central server 112 and the third IoT device (106-C).
[0036] In one embodiment, the manufacturers of the RMC product use a batching software to give a one or more commands to the panel board 108 and the data is stored in the local database. The batching software is installed in the batching plant operating system. To verify the data in the local database recorded by the sensors and stored in the local database, installed by the manufacturer, the system 100 is also configured to implement a customized software (Cycle data software), which can record the exact mix-proportions and quantities of different raw materials in the concrete batching plant 104. This software records the data with the help of sensors and load-cells (IoT devices 106-A-D) which are pre-installed in the manufacturing plant.The word batching software refer to the software installed by the manufacturer and the word customized software, cycle data software, cycle data middleware refer the same and are used interchangeably in the description and is the software installed by the central server 112 of system 100.
[0037] In one embodiment, the cycle data software records the data in real-time. With the help of the IoT device 106-C-D which is installed in the concrete batching plant operating system of the computing device 116, information is recorded and sent to the central server 112 directly without depending on local internet facility. Once the central server 112 receives data, this is verified and compared with the actual mix-design which the builder or the consumer 114
10
requires and a report is sent to the builder instantly online. Thus the builder receives this data of concrete before receiving concrete at his site. Hence builders or the consumers 114 can be assured regarding the total quantity and mix-proportions of the concrete procured.
[0038] The central server 112 is configured for receiving processed data from the first IoT device 106-A, recorded data from the second IoT device 106-B, processed data from the processor and third IoT device 106-C. After, receiving the data from the first, second and third IoT hardware devices (IoT device 106-A-C) and the IoT device 106-D (cycle data software), the central server 112 is configured for performing comparison and combinations of received data to generate a report and publishing the generated report real-time to a consumer 114 and supplier. For example, in central server 112, data pertaining to consumer’s project details and supplier manufacturing plant details are recorded. As soon as a new Project or manufacturing plant is created, geo-fences pertaining to them are established by the central server 112. When a new order is created in between a supplier and consumer 114, its order details are recorded along with target mix-design. The central server 112 records data from the first, second and third IoT hardware devices (IoT device 106-A-C) and the IoT device 106-D (cycle data software). Through various comparisons and combinations of the data, the central server 112 generates reports for buyer and supplier.
[0039] The functions which are performed by the central server 112 is to capture actual mix proportions obtained through IoT devices 106-A-C and to compare with target mix-design which the respective consumer and supplier agreed upon (This target mix-design is recorded from order details). The central server 112 generates deviations per each material. The central server 112 now compares these deviations with the permissible deviation limits per each material. (Permissible deviation limits are set by the central server 112 in general, these can also be changed to more specific ranges with respect to each consumer). The central server 112 records production time and other time stamps with the help of location tracking devices and geo-fences. Therefore the buyer can know the updates and live location of the vehicle and prosecute for any doubtful delays and instances.
[0040] All these data is aggregated and a report is generated which is shown to respective consumer 114 and supplier real-time. Thus consumer 114 receives actual and genuine data of concrete before they actually utilize the concrete.
[0041] Thus the system 100 of the present disclosure with the help of the first, second and third IoT hardware devices (IoT device 106-A-C) and the IoT device 106-D (cycle data software) provide a fool-proof solution for a real-time evaluation and monitoring of the RMC quality control during manufacturing and delivery to the consumer 114. These IoT devices (106-A-C) with the help of cycle data software is configured to record data real-time and at multiple instances later on to track any changes which takes place in the database (created by the manufacturer).
[0042] In addition, apart from the quality control performed by the IoT device 106-D (cycle data software installed in computing device), smart Iot device 106-C (hardware installed in computing device), the panel board data recording device 110 (IoT device 106-B), and the IoT device 106-A installed in the concrete batching plant 104, the system 100 also procures data from OEM (Original Equipment Manufacturer) to perform another quality control. Moreover, the system 100 provides a Fool-proof solution in the market right now, reducing the financial damage to the consumer 114.
[0043] FIG. 2 illustrates a generic system view 200 of a RMC plant premise and a GPS system along with a system of geo-fences configured for delivering a quality controlled RMC to a consumer, according to an embodiment of the present disclosure. In particular, the generic system 200 of the RMC plant premise include the plant premise 102, the central server 112, a GPS system 202, an order creation module 204 and the consumer (site) 114. In one embodiment, the generic system 200 of the RMC include the plant premise 102 (as shown in FIG. 1). The plant premise 102 further includes the batching plant 104, the one or more IoT (Internet of Things) devices 106A-106D, the panel board 108, the panel data recording device 110, the central server 112 and the consumer 114 (as explained above and shown in FIG. 1).
[0044] In particular, the GPS system 202 of FIG. 2 is interconnected with one or more outputs of the components of the plant premise 102 and the central server 112. Here, the word GPS system and the GPS hardware refer the same and are used interchangeably in the description. The GPS system 202 is a system connected to a specific vehicle. The specific vehicle connected with the GPS system 202 is a vehicle carrying or delivering the RMC product to the consumer 114 or the consumer site. Further, the specific vehicle connected with the GPS system 202 carrying or delivering the RMC product to the consumer site 114 is connected through the central server 112. Here, the GPS system 202 or the GPS hardware is a location tracking device. The location tracking device may be a fixed or a portable device connected to
the specific vehicle, the vehicle carrying or delivering the RMC product to the consumer site 114. In addition, the GPS connected vehicle is connected through the central server 112 and continuously configured to send location pings of the specific vehicle carrying or delivering the RMC product to the consumer site 114.
[0045] In the same embodiment, the GPS system 202 includes an assigned vehicle configured to include a GPS hardware in combination with a marking geo-fences in the plant premise 102 and the delivery site or the consumer site 114. The GPS hardware in combination with the marking geo-fences the plant premise 102 and the delivery site or the consumer site 114 is further configured to exhibit a live location and a geo-fence data of the assigned vehicle. The live location and the geo-fenced data of the assigned vehicle pertains to a creation of a new project or to a creation of a new manufacturing plant. With the help of GPS devices, geo-fencing and monitoring system, the consumer 114 can make sure that there is no pilferage during transit of RMC. The creation of the new project or the creation of the new manufacturing plant refers the creation of the same in between a supplier and the consumer 114. When a new order is created between the supplier and the consumer, the order details of the supplier and the consumer are recorded along with a target mix-design. The target mix-design is the actual mix proportions of the one or the more raw materials used for the preparation of the RMC product, on which a respective consumer and a supplier agreed upon. The central server 112 captures the actual mix proportions of the one or the more raw materials used for the preparation of the RMC product through the cycle data software installed in the concrete batching plant operating system of the computing device 116 on the plant premises 102, IoT devices 106A-106D and the panel data recording device 110 installed on the panel board 108 on the plant premises 102.
[0046] In one embodiment, the order creation module 204 creates an order in a one or more designs such as the target mix-design, project design and the plant details. In addition, the order creation module 204 includes a buyer on-boarding and a supplier on-boarding. Further, the buyer on-boarding and the supplier on-boarding creates an agreement sign-offs and an account creation. The agreement sign-offs and the account creation is configured to define a project and a mix-design details of the buyer on-boarding and the supplier on-boarding. The project and the mix-design details of the buyer on-boarding and the supplier on-boarding creates the buyer and the supplier details of the mix-proportions of the raw materials used for the preparation of the RMC product. Henceforth, an order defining by the buyer and the supplier acceptance
creates an order between the buyer and the supplier details for the mix-proportions of the raw materials used for the preparation of the RMC product. Hence, the order creation module 204 creates an overall order in designs containing the target mix-design, project design and the plant details. The central server 112 records data from the one or more devices of the plant premise 102 (for example, the concrete batching plant 104, IoT devices 106A-106D, the panel board 108 , the panel board data recording device 110 and the cycle data software installed on the batching plant operating system ), the GPS system 202 and the order creation module 204. Through a plurality of comparisons and combinations of the data of the one or more devices of the plant premise 102, the GPS system 202 and the order creation module 204; the central server 112 generates a report for the buyer (consumer 114) and the supplier (manufacturer). The generation of the report is based on the order details, actual production, GPS data and deviations per each material. The central server 112 compares the one or more deviations with a permissible deviation limit per each material. The permissible deviation limits are set by the central server 112 and more particularly may also be changed to a more specific range with respect to each consumer. Furthermore, the report is generated based on the aggregation of the data and sending the report to a respective buyer (consumer 114) and a supplier (manufacturer). in real time. Hence, the consumer 114 receives an actual and genuine data of the concrete before the consumer 114 actually utilize the concrete at the site.
[0047] The central server 112 records production time and a one or more other time stamps and the like with the help of the location tracking devices and the Geo-fences of the GPS system 202. Hence, the consumer 114 may get to know in advance the updates and the live location of a vehicle, the vehicle carrying the RMC product to the consumer 114 site. In addition, the consumer 114 may also prosecute for any doubtful delays, for example, a time frame for a vehicle to reach at the consumer site 114, the vehicle carrying the RMC product, and the like instances.
[0048] FIG. 3 is a flow chart 300 illustrating a method for monitoring a RMC (Ready Mix Concrete) quality control, according to an embodiment of the present disclosure. In particular, the steps as described in FIG. 3 may be executed for monitoring the RMC (Ready Mix Concrete) quality control.
[0049] At step 302, a first IoT (Internet of Thing) device is installed in a concrete batching plant. It may be noted that, although first IoT device is refereed in method 300, one or more IoT (Internet of Things) devices may be installed in the concrete batching plant. The one or
14
more IoT (Internet of Things) devices are installed for operating one or more sensing devices, processing the sensed data and communicating the processed data to a central server in the concrete batching plant. The one or more sensing devices are weight capturing sensors installed in the concrete batching plant. The weight capturing sensors installed in the concrete batching plant are configured for capturing at least a miniscule alteration made in the course of preparation of RMC (Ready Mix Concrete), in the concrete batching plant 104. Moreover, the captured miniscule alteration is processed by comparing with an actual sensed data. The actual sensed data are obtained by a one or more batching plant sensor to detect a one or more tampering in the course of preparation of the RMC (Ready Mix Concrete) in the concrete batching plant. The one or more batching plant sensors are the sensors installed by a manufacturer of RMC (Ready Mix Concrete). However, the IoT (Internet of Things) devices 106A-106B (as shown in FIG. 1) and the batching plant sensors are calibrated to the exact weights in association with a government agency or a third party or an authorized agency. Furthermore, whenever there is a difference in values between the batching plant sensors and the IoT device sensors, an alert will be generated to notify one or more changes. The alerts are generated through the central server 112 to notify the one or more changes. The batching plant calibration is tracked from the sensors level and the correct weight of the raw materials used in the RMC product is recorded. In addition, the processed data is communicated by sending an alert notification to the central server 112.
[0050] At step 304, a panel board data recording device comprising a second IoT device is installed in a panel board of the concrete batching plant for recording and tracking the entire batch data, at least a minuscule manipulation to calibration in the concrete batching plant and the panel board, and communicating the recorded data by the second IoT device, to the central server. The panel board data recording device apart from recording changes in calibration, also records all the batch data done automatically or manually. The panel board 108 is connected with the one or more components of the batching plant 104 through a one or more sensors. The one or more sensors refers to the sensors of the batching plant 104 of the plant premise 102.
[0051] At step 306, a set of instructions are executed in a batching plant operating system of a computing device, for recording and tracking the entire batch data, detecting and recording at least a minuscule manipulation to calibration in the concrete batching plant and the panel board and communicating the said recorded data to the central server. Further, a third IoT device is installed in the batching plant operating system of the computing device for receiving
and storing the said recorded data, and communicating the said recorded data to the central server. The computing device is interconnected with the batching plant and the panel board of the plant premise comprises a processor and a memory coupled to the processor. The memory stores a plurality of modules to be executed by the processor. Further, the plurality of the modules is configured for recording and tracking the entire batch data, detecting and recording at least a minuscule manipulation to calibration in the concrete batching plant and the panel board and communicating the processed data to the central server. In the same embodiment, the processor comprises a batching tracking module. The batching tracking module is installed in the concrete batching plant 104. The installed batching tracking module is customized software (Cycle data software) in the concrete batching plant 104 and is configured to execute a computer-readable instructions for detecting and recording the one or more manipulation in the concrete batching plant 104 at batching plant system level.
[0052] Hence, the method steps of the flow chart 300 provides alerts in case any data manipulation is done in the concrete batching plant (step 302), at the panel board level (step 304). In addition, the cycle data software installed at step 306) in the plant system records any changes in the plant calibration in the batching plant system level.
[0053] FIG. 4 illustrates a system 400 for verifying the result of a concrete cube testing, according to an embodiment of the present disclosure. The system 400 for verifying the result of a concrete cube testing includes a mould 402, an unique identifier (ID code for example, RFID or a QR code or a bar code) 404, a concrete block 406, an IoT device 106, a cube testing apparatus 408, a camera 410, and a cube based on ID code 406.
[0054] In particulars, the mould 402 is a hollowed-out block. The hollowed-out block may be of one or more shapes and sizes. The one or more shapes, for example, may include a rectangle, a triangle, a round, a square shape and the like. The hollowed-out block is filled with one or more liquids or pliable materials. The one or more liquids or the pliable materials, for example, plastic, metal, glass or ceramic raw material. With the existing disclosure, the raw materials used for filling the hollowed-out block are mixtures of sand, water, cement, admixtures, crushed stones and the like. The mixtures of the raw materials hardens or sets inside the hollowed-out block adopting a shape, the shape of the hollowed-out block. However, a complete mould is formed by combining a plurality of multiple pieces and further disassemble to release the finished casting.
16
[0055] In the same embodiment, an ID code 404 is assigned as a unique identifier for every single cube during the process of casting. The ID code, may be, for example, an RFID code or a QR code or a bar code. The ID number 404 of the code of the cube is provided to a supplier and to a buyer both. The ID code 404 is used to automatically identify an object and track the object with the help of a tag attached to the objects.
[0056] In the same embodiment, an IoT device is implemented in cube testing apparatus 408. The IoT device implemented in the cube testing apparatus 408 is configured to detect the presence of a cube based on ID code 406 or the unique identifier. With the help of the unique identifier, the cube testing results are automatically linked to the specific order in the central server. The cube testing apparatus 408 is a machine meant for testing a concrete cube based on the compressive strength of the concrete. In addition, the cube testing apparatus 408 is also used for quality assurance of the concrete to make sure the concrete is suitable for a defined purpose. The cube testing apparatus 408 further also records the final compression strength value of the concrete after the testing and further send the recorded information to the central server 112 of FIG. 1. Moreover, the camera 410 is placed in front of the cube testing apparatus 408. The camera 410 placed in front of the cube testing apparatus 408 is configured to record the footage of the testing of the cube based on the ID code 406 and sending the recorded information to the central server 112. Further, the recorded information is compared with the stored information to verify the results of the concrete cube testing. The verified result is linked to the respective order of respective buyer. Furthermore, based on the ID code 404, the verified result is linked to a respective order of the respective buyer. In addition, the camera 410 also detects the QR code or the bar code as a secondary measure.
[0057] FIG. 5 is a flow chart 500 illustrating a method for verifying the results of a concrete cube testing, according to an embodiment of the present disclosure. In particular, the steps as described in FIG. 5 may be executed for verifying the results of the concrete cube testing.
[0058] At step 502, a unique identifier is assigned for every single cube during the process of casting. The unique identifier may be an ID code or an RFID code or a QR code or a bar code. The ID code 404 of the cube is provided to a supplier and to a buyer both. The ID code 404 is used to automatically identify an object and track the object with the help of a tag attached to the objects.
[0059] At step 504, an IoT (Internet of Things) device is implemented in a cube testing apparatus. The IoT device 106 implemented in the cube testing apparatus 408 is configured to detect the presence of a cube based on ID code 406 or the unique identifier. The cube testing apparatus 408 further also records the final compression strength value of the concrete after the testing and further sent the recorded information to the central server 112.
[0060] At step 506, a camera was placed in front of the cube testing apparatus. The camera 410 placed in front of the cube testing apparatus 408 is configured to record the footage of the testing of the cube based on the ID code 406 and sent the recorded information to the central server 112.
[0061] At step 510, the recorded information is compared with the stored information to verify the results of the concrete cube testing. The verified result of the concrete cube testing is linked to a respective order of a respective buyer. Furthermore, based on the ID code 404, the verified result is linked to the respective order of the respective buyer.
[0062] The existing disclosure also recommends an optimum ready mix concrete design to a one or more consumers of the concrete. This optimum design mix is calculated with the help of the data from IoT devices 106-A-D of FIG 1 and the cube testing results as described in FIG. 3. The recommended optimum ready mix concrete design is of optimum strength with reduced cost or with other properties as requested by the one or more consumer. Henceforth, helps a one or more users to buy or sell better quality concrete at a lesser price. With the help of these two data sources an optimum mix design with reduced cost and without compromising on the quality parameters is calculated and recommended to the end consumer.
[0063] The present disclosure also recommends in suggesting a different supplier in the times of a plant breakdown during the procurement of concrete for one or more reasons for a one or more buyers. The buyer cannot procure the concrete from different suppliers, because of the change in the material properties (for example, chemical structure, sources, quality and the like). In addition, the buyer cannot wait for a time gap, the time gap between the breakdown and the repair of the plant. The time gap and the change in the supplier affect the homogeneity of the concrete and may result in a substandard quality work and structural deformities of the concrete. The present disclosure provides a solution by dealing with a plurality of concrete manufacturers with clear information about the plant locations and material properties. The
system finds the supplier with similar material properties and provide a safe delivery distance so that the structure retains the homogeneity and the buyer can avoid any losses.
[0064] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person skilled in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.
[0065] 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, orders 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 necessarily need to be performed. Also, those acts that are not dependent 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. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.
WE CLAIM:
1. A system for Ready Mix Concrete (RMC) quality control, the system comprising:
a first (Internet of Things) device installed in a concrete batching plant and configured for operating one or more sensing devices; processing the sensed data and communicating the processed data to a central server; a panel board data recording device comprising a second IoT device, installed in a panel board of the concrete batching plant and configured for: and
recording and tracking the entire batch data, at least a minuscule manipulation to calibration in the concrete batching plant and the panel board; and communicating the recorded data by the second Iot device to the central server; a computing device comprising a processor, a memory coupled to the processor, and a third IoT device installed in a batching plant operating system of the computing device; wherein the memory stores a plurality of modules to be executed by the processor, wherein the plurality of modules are configured for recording and tracking the entire batch data, detecting and recording at least a minuscule manipulation to calibration in the concrete batching plant and the panel board; and communicating the processed data to the central server; and wherein the third IoT device is configured to receive, store and send the processed data from the processor, to the central server.
2. The system of claim 1, wherein the central server is configured for receiving:
processed data from the first IoT device, recorded data from the second IoT device; processed
data from the processor and third IoT device; performing comparison and combinations of received data to generate a report; and publishing the generated report real-time to a consumer and supplier.
3. The system of claim 1, wherein the one or more sensing devices are weight capturing sensors
installed in the concrete batching plant and configured for:
capturing at least a miniscule alteration made in the course of preparation of (RMC) Ready Mix Concrete in the concrete batching plant;
processing the captured miniscule alteration by comparing with an actual sensed data obtained by a one or more batching plant sensor to detect any tampering in the course of preparation of (RMC) Ready Mix Concrete in the concrete batching plant; and
communicating the processed data by sending an alert notification to the central server.
4. The system of claim 3, wherein the one or more batching plant sensors are the sensors installed by a manufacturer of (RMC) Ready Mix Concrete.
5. The system of claim 1 and 4, wherein the sensing devices and the batching plant sensors are calibrated to the exact weights in association with a government agency or a third party or an authorized agency.
6. The system of claim 1, wherein the processor comprises a batching tracking module installed in the batching plant operating system of the computing device and configured to execute the computer-readable instructions for recording and tracking the entire batch data, detecting and recording at least a minuscule manipulation to calibration in the concrete batching plant and the panel board.
7. A method for monitoring (RMC) Ready Mix Concrete quality control, the method comprising:
installing a first IoT (Internet of Things) device, in a concrete batching plant for operating one or more sensing devices; processing the sensed data and communicating the processed data to a central server;
installing a panel board data recording device comprising a second IoT device, in a panel board of the concrete batching plant for recording and tracking the entire batch data, at least a minuscule manipulation to calibration in the concrete batching plant and the panel board, and communicating the recorded data by the second IoT device, to the central server;
executing a set of instructions in a batching plant operating system of a computing device, for recording and tracking the entire batch data, detecting and recording at least a minuscule manipulation to calibration in the concrete batching plant and the panel board and communicating the said recorded data to the central server; and
installing a third IoT device in the batching plant operating system of the computing device for receiving and storing the said recorded data, and communicating the said recorded data to the central server.
8. The method of claim 7, further comprising receiving by the central server the processed data from the first IoT device, recorded data from the second IoT device; processed data from the processor and third IoT device.
9. The method of claim 8, further comprising:
performing, by the central sever comparison and combinations of received data to generate a
report; and publishing the generated report real-time to a consumer and supplier.
10. The method of claim 7, wherein the one or more sensing devices are weight capturing sensors
installed in the concrete batching plant configured for:
capturing at least a miniscule alteration made in the course of preparation of (RMC) Ready Mix Concrete in the concrete batching plant;
processing the captured miniscule alteration by comparing with an actual sensed data obtained by a one or more batching plant sensor to detect any tampering in the course of preparation of (RMC) Ready Mix Concrete in the concrete batching plant; and
communicating the processed data by sending an alert notification to the central server.
11. A method for verifying the results of concrete cube testing, the method comprising:
assigning an unique identifier for every single cube during the process of casting;
implementing an IoT (Internet of Things) device in a cube testing apparatus for: detecting the
presence of the cube based on the unique identifier; recording a final compression strength value of the concrete after the testing; and
sending the recorded information to a central server; placing a camera in front of the cube testing apparatus for: and recording the footage of the testing; and sending the recorded information to the central server; verifying the results of the concrete cube testing by comparing the recorded information with
the stored information; wherein the verified result is linked to the respective order of
respective buyer.
12. The method of claim 9, further comprising recommending an optimum ready mix concrete design to a one or more consumers of the concrete; wherein the recommended optimum ready mix concrete design is of optimum strength with reduced cost or with other properties as requested by the one or more consumer.
| # | Name | Date |
|---|---|---|
| 1 | 201841005413-STATEMENT OF UNDERTAKING (FORM 3) [13-02-2018(online)].pdf | 2018-02-13 |
| 2 | 201841005413-FORM FOR SMALL ENTITY(FORM-28) [13-02-2018(online)].pdf | 2018-02-13 |
| 3 | 201841005413-FORM FOR SMALL ENTITY [13-02-2018(online)].pdf | 2018-02-13 |
| 4 | 201841005413-FORM 1 [13-02-2018(online)].pdf | 2018-02-13 |
| 5 | 201841005413-EVIDENCE FOR REGISTRATION UNDER SSI(FORM-28) [13-02-2018(online)].pdf | 2018-02-13 |
| 6 | 201841005413-DRAWINGS [13-02-2018(online)].pdf | 2018-02-13 |
| 7 | 201841005413-DECLARATION OF INVENTORSHIP (FORM 5) [13-02-2018(online)].pdf | 2018-02-13 |
| 8 | 201841005413-COMPLETE SPECIFICATION [13-02-2018(online)].pdf | 2018-02-13 |
| 9 | 201841005413-FORM-9 [14-02-2018(online)].pdf | 2018-02-14 |
| 10 | 201841005413-FORM 18A [14-02-2018(online)].pdf | 2018-02-14 |
| 11 | 201841005413-Proof of Right (MANDATORY) [15-03-2018(online)].pdf | 2018-03-15 |
| 12 | 201841005413-FORM-26 [15-03-2018(online)].pdf | 2018-03-15 |
| 13 | Correspondence by Agent_Form1, GPA_21-03-2018.pdf | 2018-03-21 |
| 14 | 201841005413-FER.pdf | 2018-06-01 |
| 15 | Correspondence by Agent_Submission Document_04-06-2018.pdf | 2018-06-04 |
| 16 | 201841005413-OTHERS [14-11-2018(online)].pdf | 2018-11-14 |
| 17 | 201841005413-FORM FOR STARTUP [14-11-2018(online)].pdf | 2018-11-14 |
| 18 | 201841005413-FER_SER_REPLY [14-11-2018(online)].pdf | 2018-11-14 |
| 19 | 201841005413-EVIDENCE FOR REGISTRATION UNDER SSI [14-11-2018(online)].pdf | 2018-11-14 |
| 20 | 201841005413-CLAIMS [14-11-2018(online)].pdf | 2018-11-14 |
| 21 | 201841005413-HearingNoticeLetter.pdf | 2019-01-21 |
| 22 | 201841005413-FORM-26 [27-02-2019(online)].pdf | 2019-02-27 |
| 23 | Correspondence By Agent_Power of Attorney_07-03-2019.pdf | 2019-03-07 |
| 24 | 201841005413-Written submissions and relevant documents (MANDATORY) [07-03-2019(online)].pdf | 2019-03-07 |
| 25 | Marked Up Claims_Granted 310373_29-03-2019.pdf | 2019-03-29 |
| 26 | Drawings_Granted 310373_29-03-2019.pdf | 2019-03-29 |
| 27 | Description_Granted 310373_29-03-2019.pdf | 2019-03-29 |
| 28 | Claims_Granted 310373_29-03-2019.pdf | 2019-03-29 |
| 29 | Abstract_Granted 310373_29-03-2019.pdf | 2019-03-29 |
| 30 | 201841005413-PatentCertificate29-03-2019.pdf | 2019-03-29 |
| 31 | 201841005413-IntimationOfGrant29-03-2019.pdf | 2019-03-29 |
| 32 | 201841005413-REQUEST FOR CERTIFIED COPY [03-05-2019(online)].pdf | 2019-05-03 |
| 33 | 201841005413-FORM28 [03-05-2019(online)].pdf | 2019-05-03 |
| 34 | 201841005413-RELEVANT DOCUMENTS [15-05-2020(online)].pdf | 2020-05-15 |
| 35 | 201841005413-FORM-26 [10-02-2021(online)].pdf | 2021-02-10 |
| 36 | 201841005413-Correspondence, POA_01-03-2021.pdf | 2021-03-01 |
| 37 | 201841005413-RELEVANT DOCUMENTS [15-09-2021(online)].pdf | 2021-09-15 |
| 38 | 201841005413-RELEVANT DOCUMENTS [10-08-2022(online)].pdf | 2022-08-10 |
| 1 | search12345_28-05-2018.pdf |