METHOD OF MANAGING A PROJECT INVOLVING TRANSPORT OF A MATERIAL VIA A MATERIAL CARRYING VEHICLE
FIELD OF THE INVENTION
The present disclosure relates to project management in construction and mining industries. Specifically, the present invention relates to a method and system of managing a project activity involving transport of a material via a material carrying vehicle.
BACKGROUND
Construction and mining projects are difficult to manage due to fragmentation and inaccessibility of relevant data related to work being done and equipment, plants, and machinery being used. Thus, an owner/operator of a site does not have access to concise, accurate, and meaningful data on either performance of the plants, machinery and equipment, or on the work being done. Lack of such data increases time to take necessary action during critical issues such as stoppage of work, breakdown of equipment etc. Also, significant time, money and resources are consumed to routinely survey the work being performed by heavy civil construction equipment.
The conventional approach to manage such projects is to manually capture and consolidate data from a variety of sources either in the form of physical paper-work or isolated spreadsheets. In the case of 'project work-done data', daily progress reports are collected orally, on paper or on spreadsheets. In the case of 'equipment, plant and machinery data', usage and production logs are manually collected from the existing instruments available on the equipment. All these isolated fragments of data are to either be manually reconciled or entered into a traditional ERP system. Due to the human intervention required to capture and process this plethora of data, the conventional approach is liable to inaccuracy, irregularity and even deliberate mismanagement. While the existing plants, machinery and equipment generate data logs using OEM-specific data protocols, such data is fragmented and does not follow any set standard. As such, it is difficult for the operator of the site to process and use this information. Considering the fact that materials constitute more than 60% of a project cost, managing such an abuse becomes extremely crucial as costs of a project are an essential parameter of assessment of feasibility of a particular civil project.

The problem thus being addressed is the collection, processing, and monitoring/tracking of data from various machines operating at a site. .
SUMMARY
This summary is provided to introduce a selection of concepts in a simplified format that are further described in the detailed description of the invention. This summary is neither intended to identify key or essential inventive concepts of the invention, nor is it intended for determining the scope of the invention.
In an embodiment, the present subject matter refers to a method of managing a project activity involving transport of an amount of material (X) via a material carrying vehicle (MCV) from a source location (SL) to a destination location (DL). The method comprises of receiving transport request information (TRI), retrieving, based on TRI, handling information (HI), the HI at least comprising information pertaining to the material carrying vehicle and creating an intelligent data packet (TDU) comprising TRI and HI. Further, the method comprises of providing the IDU to an electronic controller at SL and/or person in-charge at SL and an electronic controller at DL and/or person in-charge at DL. Additionally, the method comprises of receiving source location transaction information (SLTI) from the electronic controller at SL or source location manifest information (SLAI) from an electronic device associated with the person in-charge at SL, and receiving destination location transaction information (DLTI) from the electronic controller at DL or destination location acknowledgement information (DLAI) from an electronic device associated with the person in-charge at DL. Further, the method comprises of generating "transaction information" based on at least one of SLTI and SLAI, and at least one of DLTI and DLAI, and indicating completion of the activity if the "transaction information" satisfies at least one predetermined criterion.
In accordance with another embodiment of the present invention, a central server is provided to manage a project activity involving transport of an amount (X) of material (M) from a source location (SL) to a destination location (DL) via a material carrying vehicle (MCV) is disclosed. The system comprises of a receiver to receive transport request information (TRI), source location transaction information (SLTI) from an electronic controller at SL or source location manifest information (SLAI) from an electronic device associated with the person in-charge at SL, and destination location transaction information (DLTI) from an electronic controller at DL

or destination location acknowledgement information (DLAI) from an electronic device associated with the person in-charge at DL. Further, the system comprises of a processor to (a) retrieve, based on TRI, handling information (HI), the HI at least comprising information pertaining to the material carrying vehicle, (b) create an intelligent data packet (IDU) comprising TRI and HI, (c) generate "transaction information" based on at least one of SLTI and SLAI, and at least one of DLTI and DLAI, and (d) indicate completion of the activity if the "transaction information" satisfies at least one predetermined criterion. The system further comprises of a transmitter to provide the IDU to the electronic controller at SL and/or person in-charge at SL, and the electronic controller at DL and/or person in-charge at DL.
In accordance with another embodiment of the present invention, a system is provided to manage a project activity involving transport of an amount (X) of material (M) from a source location (SL) to a destination location (DL) via a material carrying vehicle (MCV) is disclosed. The system comprises of a (l)a first electronic controller including a first receiver and a first transmitter, the first electronic controller situated at the SL; the first receiver and the first transmitter configured to receive and transmit information respectively, (2) a first electronic device including a second receiver and a second transmitter, the first electronic device associated with a person-in charge at the SL; the second receiver and the second transmitter configured to receive and transmit information respectively, (3) a second electronic controller including a third receiver and a third transmitter, the second electronic device situated at the DL; the third receiver and the third transmitter configured to receive and transmit information respectively, (4) a second electronic device including a fourth receiver and a fourth transmitter, the second electronic device associated with a person in charge at the DL; the fourth receiver and the fourth transmitter configured to receive and transmit information respectively, (5) a processing unit including a fifth receiver and a fifth transmitter, the processing unit provided on the MCV; and (6) a central server including a receiver, a processor and a transmitter. The receiver at the central server is configured to receive a transport request information (TRI), source location transaction information (SLTI) from the first electronic controller at SL or source location manifest information (SLAI) from the first electronic device associated with the person in-charge at SL. Further, the receiver is configured to receive destination location transaction information (DLTI) from the second electronic controller at DL or destination location acknowledgement information (DLAI) from the second electronic device associated with the person in-charge at DL. Further, the receiver is also configured to receive tracking information from the processing

unit (PU) provided on the material carrying vehicle. The processor at the central server is configured to (a) retrieve, based on TRI, handling information (HI), the HI at least comprising information pertaining to the material carrying vehicle, (b) create an intelligent data packet (IDU) comprising TRI and HI, (c) generate "transaction information" based on at least one of SLTI and SLAI, at least one of DLTI and DLAI and the tracking information, and (d) indicate completion of the activity if the "transaction information" satisfies at least one predetermined criterion. Further, the transmitter at the central server is configured to provide the IDU to the first electronic controller at SL and/or the first electronic device associated with the person in-charge at SL, and to the second electronic controller at DL and/or the second electronic device associated with person in-charge at DL.
Overall, the present subject matter enables collection, processing, and monitoring/tracking of data from various machines operating at sites by providing a real time flow of information from sites, including one or more other locations allocated to monitor the MCV carrying the desired material (M) in the desired amount (X), to a project operator's management office. Further, the embodiments of the application provide an end to end system for information capture and flow which ensures that available data is not fragmented in any form. Embodiments of the present invention employ hardware enabled with technology to physically track materials and machinery, which help avoid any abuse of exiting system and resources. Further, mis-identification and mis-quantification of materials; and fraud or misappropriation of material being transported to and from construction and mining sites via trucks can be easily and quickly identified. This enables quick action by operator in case of any issue, thereby reducing financial losses to the operator considerably.
To further clarify advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS
These and other features, aspects, and advantages of the present invention will become 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:
Figure 1 illustrates a method in accordance with an embodiment of the present invention.
Figure 2 illustrates a system implementing a method in accordance with an embodiment of the
present disclosure.
Figure 3 represents a diagrammatic representation of an example in accordance with an
embodiment of the present invention.
Figure 4 illustrates illustrates a typical hardware configuration of a system implementing a
method in accordance with the present invention.
Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have been necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.
DETAILED DESCRIPTION OF FIGURES
For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings 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.

It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the invention and are not intended to be restrictive thereof.
Reference throughout this specification to "an aspect", "another aspect" or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, 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.
The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such 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.
Unless otherwise defined, all technical and scientific terms used herein have the lqsame 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.
Embodiments of the present invention will be described below in detail with reference to the accompanying drawings.
Figure 1 illustrates a method 100 to manage a project activity involving transport of an amount (X) of material (M) from a source location (SL) to a destination location (DL) via a material carrying vehicle (MCV), in accordance with an embodiment of the present invention. Figure 2 illustrates a system 200 for implementing the method 100 in accordance with the present invention. Figure 1 shall be explained with reference to Figure 2 wherever appropriate.

Unless otherwise specified, the terms, which are used in the specification and claims, have the
meanings commonly used in the field of construction and/mining and machines involved therein.
Specifically, the following terms have the meanings indicated below.
The project can be civil constructions projects, mining projects and other industrial projects that
involve a project activity including transport of materials and surveillance of the quantities of
materials being transferred from one source location (SL) to another destination location (DL).
The destination location (DL) can include one or more sites and can also include mid-way
locations allocated to monitor the transportation.
The material (M) can include both fuel and other raw substances such as cement, concrete, sand,
stones, asphalt, crushers etc.
The amount (X) refers to a measured quantitative value of the material (M).
The material carrying vehicle (MCV) includes a variety of transportation vehicles that can be
used to carry the material (M), such transportation vehicles including heavy machinery trucks,
fuel tanks equipped trucks, fully loaded trucks, tempos, cranes, mining vehicles and many more.
As illustrated in Figure 1, the method 100 includes at step 102 receiving transport request information (TRI). In one implementation, the transport request information (TRI) can be received at a central server 200C as illustrated in Figure 2. In one implementation, the central server 200C can be located at a remote location. In another implementation, the central server 200C can be located at the source location (SL). The central server 200C can be accessed by one or more project operators who can monitor and survey the material (M) being transported in a desired material carrying vehicle (MCV) implementing the method 100 of the present invention.
The transport request information (TRI) comprises of an information about the material (M), information about the amount (X) of material, information about the source location (SL), and information about the destination location (DL). The information about the material (M) refers to the material (M) actually being transferred, such as cement, rocks, asphalt etc., and the amount (X) refers to the actual quantitative value of that material (M) being measured at the source location (SL). Further, information about the source location (SL) and the destination location (DL) refers to details identifying the location such as Global Positioning (GPS) data. However, GPS data should not be construed as limiting to the present invention and other technology used to identify a location can be used as well. In one implementation, the TRI can be received from SL. In another implementation the TRI can be received from DL. In yet another implementation,

the TRI can be received from a third party. In yet another implementation, the TRI can be received from the project operator though user selections communicated over one or other input devices explained in detail below.
Further, the method 100 includes at step 104 retrieving, based on TRI, handling information (HI). The handling information (HI) comprises of information pertaining to the MCV. The HI enables identifying a type of MCV suitable to carry the material (M). For example, M being a fuel will require a MCV equipped with a fuel tank, or M being heavy stones may require suitable heavy trucks as the MCV. Further, the HI may comprise information pertaining to a person-in-charge at the SL and/or a person-in-charge at the DL.
Further, the method 100 includes at step 106 creating an intelligent data packet (IDU) comprising TRI and HI. Depending upon the IDU, the project managers can supervise the transportation of materials and acknowledge accurate and precise data related to such transportation of the materials. The method 100 is described in more detail below to explain handling of the IDU in the entire process of transportation from SL to DL, in accordance with the present invention.
Further, the method 100 includes at step 108 providing the IDU to one or more electronic devices located at SL and DL. The step 108 of providing the IDU shall be explained with reference to Figure 2. Figure 2 illustrates the system 200 comprising a first electronic controller 201A located at the SL and a first electronic device 201B associated with a person-in-charge present at the SL. Further, the system 200 comprises a second electronic controller 201C located at the DL and a second electronic device 20ID associated with a person-in-charge present at the DL. In one implementation, the IDU is provided to the first electronic controller 201A at the SL and the second electronic controller 201C at the DL. In another implementation, the IDU can be provided to the first electronic device 201C at the SL and the second electronic device 20ID at the DL. The IDU can be provided to the person-in charge at the SL and DL respectively, in any other form also, such as a manual sheet or communicated using other communication methods known in the art as well.
As describe above, the IDU includes the TRI and the HI, which is used to implement a relevant part of the project activity, i.e., the material (M) being loaded in the amount(X) in the suitable

(MCV). In one implementation, the IDU can be received in the form of an electronic data on the first electronic controller 201A or the first electronic device 201B at the SL. This ensures no discrepancy in X as desired by the project manager. Even, in the other implementations, the IDU as received by the person-in-charge at the SL, the IDU shall always include accurate data from the available information and cannot be hampered by any person at the SL or DL or any other person not authorized to modify the IDU. Similarly, the IDU is also communicated to a person-in charge at the DL over the second electronic controller 201C and/or the second electronic device 20ID. Therefore, an end-to-end transparency of data (IDU) being shared is maintained in the implementation of the present invention.
Further, the method 100 includes at step 110 receiving (a) source location transaction information (SLTI) or source location manifest information (SLMI) from SL, and (b) destination location transaction information (DLTI) or destination location acknowledgement information (DLAI) at DL. In one implementation, the SLTI is received from the first electronic controller 201A at the SL. The SLTI can include information such as: (1) information about M provided to the MCV; (2) information about the X provided to the MCV; (3) information about the SL; and (4) a time stamp. In an implementation, the first electronic controller 201A gathers SLTI information on the basis of sensor data generated at the SL. As illustrated in Figure 2, the SL includes sensor(s) 218 to capture sensor data. The sensor(s) 218 can include a weight sensor, an image sensor, a plant telemetry sensor-complex and many other forms of other sensor(s) that are enabled to capture (1) information about M and (2) information about the X, as described above. Such sensor(s) enable capturing accurate data in relation to the X and M which is further carried out to ensure transparency during the entire implementation of the project activity. Sensor(s) 218 may also include devices and/or technology to provide accurate location data of the SL and the time stamp. The time stamp may include multiple time stamps, wherein each corresponds to loading of M into the MCV, dispatch of MCV and other relevant events required to be captured by the project operator.
In another implementation, the SLMI is received from the first electronic device 20IB at the SL, where SLMI includes information relevant to the project as provided by the person-in-charge at the SL. This information can be the same as SLTI associated with M, X, MCV, time stamp etc., but are provided by the person-in-charge. The person -in charge can communicate SLMI using the electronic device 201B. It should be understood, that the second electronic device 201B

associated with the person-in-charge can also be configured to receive sensor data from sensor(s) 218 and the SLMI can be sent by the person-in-charge at the SL on the basis of the sensor data. In a further implementation, both the SLTI and SLMI can be received to ensure no discrepancy in the data received at CS.
Similarly, in one implementation, the DLTI is received from the second electronic controller 201C at the DL. The DLTI can include information such as: (1) information about M received from the MCV; (2) information about the X received from the MCV; (3) information about the DL; and (4) a time stamp. In an implementation, the second electronic controller 201C gathers DLTI information on the basis of sensor data generated by sensor(s) at various intermediate pre-specified locations where the MCV stops by or waits to be checked and monitored. For example, weight sensors, image sensors, RFID transponders (contactless card), unmanned aerial vehicles (UAV) etc. can be used as sensor(s) at such one or more intermediate locations. In another implementation, the second electronic controller 201C gathers DLTI information on the basis of sensor data generated at the DL. As illustrated in Figure 2, the DL includes sensor(s) 228 to capture sensor data. Also, the DL can either implement sensor(s) 228 or any other known technology or device to capture data regarding the location of the DL and time stamps, the time stamps being associated with one or more relevant events at the DL during receiving the MCV at the DL and unloading the transported M from the MCV.
In another implementation, the DLAI is received from the second electronic device 20ID at the DL, where DLAI includes acknowledgement information relevant to the project as provided by the person-in-charge at the DL. This information can be the same as DLTI associated with M, X, MCV, time stamp etc., but are provided by the person-in-charge. The person-in-charge employs the second electronic device 20ID to communicate the DLAI. It should be understood, that the electronic device 20ID associated with the person-in-charge can also be configured to receive sensor data from sensor(s) 228 and the person-in-charge at the DL can rely on such sensor data to provide the DLAI on the electronic device 20ID.
Further, the method 100 includes at step 112 generating "transaction information" based on: (a) at least one of SLTI and SLMI; and (b) at least one of DLTI and DLAI. Further, the method 100 includes at step 114 indicating completion of the activity if the "transaction information"

satisfies at least one predetermined criterion. Herein the activity relates to completion of the
transportation activity of a civil project such as construction project, mining project etc.
In one implementation, the SLTI received from the SL can be compared quantitatively with the
DLTI to assess if the M has been transported as desired in quantity X to the DL using the MCV
allocated to the transportation.
In another implementation, the SLMI received from the SL can be compared quantitatively with
data received from DL.
In one another implementation, the DLAI received from the DL can be compared quantitatively
with data received from SL.
Such comparisons are used to generate transaction information. Accordingly, if the "transaction
information" satisfies at least one predetermined criterion, the completion of the activity is
indicated. The one or more predetermined criterion can be set by the project manager for
validating the transaction information. In one example, the predetermined criterion can be
measuring exactly X amount at DL on receiving the MCV at the DL. In another example, the
predetermined criterion may be measuring exactly X amount at DL on receiving the MCV at the
DL but allowing a certain variation in the measured amount. However, these examples should
not be construed as limiting and other criterions as suitable to the industrial project can be
implemented.
In one implementation, the method 100 may further comprise providing and storing the IDU on a portable carrying device 230, shown in Figure 2B. The portable carrying device 230 can be utilized by a user in the construction and mining domains to manage projects efficiently. The portable carrying device 230 provides real time visibility of project activity and prevents pilferage and misuse of materials and machinery.
In one implementation, the method 100 may further comprise receiving tracking information from a processing unit (PU) 232 provided on the MCV, shown in Figure 2B and described in more detail below.
In one implementation, the tracking information can comprise one or more of a location related data, a time stamp data, a vehicle condition related data, a vehicle fuel-level data, a vehicle driver-ID data, and a vehicle driving-quality data (based on in-built inertial sensors). The PU 232 enables tracking of the MCV when on road. Further, the condition of the MCV can also be

assessed from the above information such as vehicle fuel level data which can enable the project operator to further assess the progress of the project depending on factors related to the MCV. The MCV may have one or more sensors on the MCV that are enabled to monitor the tracking information listed above. In one implementation, the MCV may operate in accordance with the project requirement on road such as in the case of heavy machineries in road constructions, mining industries etc. The PU 232 can also be used to gather data from MCV operations on road and provide such data to CS to enable mentoring of the MCV during operation. In a further implementation, the tracking information gathered from the MCV is used to generate transaction information to be communicated to the CS.
In one implementation, the MCV is further adapted to receive and store upon thereupon information gathered at the SL and DL using the in-built inertial sensors or a device capable of receiving information from sensor(s) 218 located at the SL and the sensor(s) 228 located at the DL respectively. Such information gathered and stored can include source location transaction information (SLTI), destination location transaction information (DLTI), source location manifest information (SLMI), and destination location, acknowledgment information (DLAI).
In a further implementation, the PU 232 provided on the MCV is adapted to receive the source location transaction information (SLTI) from the electronic controller 201A at the SL during a handshake process there between and store the same, receive the source location acknowledgement information (SLAI) from the electronic device 201B associated with the person in-charge at SL during a handshake process there between and store the same. Similarly, the PU 232 is adapted to receive the destination location transaction information (DLTI) from the electronic controller 201C at DL during a handshake process there between and store the same, and receive the destination location acknowledgement information (DLAI) from the electronic device 20ID associated with the person in-charge at DL during a handshake process there between and store the same.
Figure 2 shall be now explained in detail. Figure 2A illustrates the system 200 including the central server (CS) in communication with the source location SL and in communication with the destination location DL. As detailed above, the CS can also reside either at the SL, DL or a remote location where the CS can be accessed by the project operator. Further, the CS includes a memory 202, a processor 204, a receiver 206 and a transmitter 208. The memory 202 includes

lists of materials M to be transported with corresponding amounts, lists of different MCVs appropriate for transportation of M in X amounts, and lists of locations acting as SL and/or DL. The receiver 206 is adapted to receive information from one or more devices located at the SL, DL, and MCV as described above. The transmitter 208 is adapted to transmit information to one or more devices located the SL, DL, and MCV, as described above. The processor 204 is adapted to perform various steps of the method 100 as described above, some of them which are to retrieve, based on TRI, the handling information (HI) pertaining to the MCV, to create the intelligent data packet (IDU) comprising TRI and HI, to generate the "transaction information" based on at least one of SLTI and SLAI, and at least one of DLTI and DLAI, and to indicate completion of the activity if the "transaction information" satisfies at least one predetermined criterion.
Further as shown in Figure 2A, the first electronic controller 201 A, located at the SL, includes a first receiver 210 and a first transmitter 212, which enable communications (i.e., reception and transmission of information) with the CS, device(s) located at the DL, and the PU 232 at the MCV. Similarly, the first electronic device 20IB, corresponding to the person-in-charge at the SL, includes a second receiver 214 and as second transmitter 216, which enable communications with the CS, device(s) located at the DL, and MCV. Similarly, the second electronic controller 201C, located at the SL, includes a third receiver 220 and a third transmitter 222, which enable communications with the CS, device(s) located at the SL and the PU 232 at the MCV. Similarly, the second electronic device 20ID corresponding to the person-in-charge at the DL, includes a fourth receiver 224 and a fourth transmitter 226, which enable communications with the CS, device(s) located at the SL, and MCV. As discussed above, the sensor(s) 218 and sensor(s) 228 are also located the SL and the DL, respectively, that transmit sensor data as described earlier.
Figure 2B illustrates the system 200 including the central server (CS) in communication with the MCV, wherein the processing unit 232 is provided on the MCV. The processing unit 232 can include a fifth receiver (not shown) and a fifth transmitter (not shown). Further, the CS is in communication with the portable data carrying unit 230 including the display 2301, memory 2302, receiver 2303 and processor 2301. The IDU a received from the CS is stored upon the memory 2302.

In accordance with a further implementation, the PU 232 provided on the MCV is adapted to receive the source location transaction information (SLTI) from the first electronic controller 201A located at the SL during a handshake process there between and store the same, receive the source location acknowledgement information (SLAI) from the first electronic device 20IB associated with the person in-charge at SL during a handshake process there between and store the same.
Similarly, the PU 232 is adapted to receive the destination location transaction information (DLTI) from the second electronic controller 201C at DL during a handshake process there between and store the same, and receive the destination location acknowledgement information (DLAI) from the second electronic device 20ID associated with the person in-charge at DL during a handshake process there between and store the same.
Figure 3 illustrates an example of reception of data, as described above, by the CS from site(s) or plant(s), equipment(s) located at the sites(s) such as heavy machinery and crusher, sensor(s) such as weighing bridge located at DL and various intermediate location, and MCV(s) such as dump trucks.
Figure 4 illustrates a typical hardware configuration of the CS wherein the CS is in the form of a computer system 2100 implementing the method 100 of the present invention. The computer system 2100 can include a set of instructions that can be executed to cause the computer system 2100 to perform any one or more of the methods disclosed. The computer system 2100 may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices such as the electronic controller 201A and the electronic device 20IB, the electronic controller 201C and the electronic device 20ID, and the processing unit PU 232 located at the SL, DL and the MCV respectively.
In a networked deployment, the computer system 2100 may operate in the capacity of a server or as a client user computer in a server-client user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system 2100 can also be implemented as or incorporated across various devices, such as a personal computer (PC), a tablet PC, a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone having a touch-screen user interface, or any other machine capable of executing a set

of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while a single computer system 2100 is illustrated, the term "system" shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple-sets, of instructions to perform one or more computer functions.
The computer system 2100 may include the processor 204 e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both. The processor 204 may be a component in a variety of systems. For example, the processor 204 may be part of a standard personal computer or a workstation. The processor 204 may be one or more general processors, digital signal processors, application specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analysing and processing data The processor 204 may implement a software program, such as code generated manually (i.e., programmed).
The computer system 2100 may include the memory 202, such as a memory 202 that can communicate via a bus 2101. The memory 202 may include, but is not limited to computer readable storage media such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read¬only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like. In one example, the memory 202 includes a cache or random access memory for the processor 204. In alternative examples, the memory 202 is separate from the processor 208, such as a cache memory of a processor, the system memory, or other memory. The memory 202 may be an external storage device or database for storing data. The memory 202 is operable to store instructions 2102 executable by the processor 208. The functions, acts or tasks illustrated in the figures or described may be performed by the programmed processor 208 executing the instructions stored in the memory 202. The functions, acts or tasks are independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firm-ware, micro-code and the like, operating alone or in combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel processing and the like.
As shown, the computer system 2100 may or may not further include a touch-sensitive display unit 2103, for outputting determined information as well as receiving a user's touch-gesture

based inputs, such as drag and drop, single tap, multiple-taps, etc. The display 2103 may act as an interface for the user to see the functioning of the processor 208, or specifically as an interface with the software stored in the memory 201 or in a drive unit 2104.
Additionally, the computer system 2100 may include an input device 2105 configured to allow a user to interact with any of the components of system 2100. The computer system 2100 may also include a disk or optical drive unit 2104. The disk drive unit 2104 may include a computer-readable medium 2105 in which one or more sets of instructions 2102, e.g. software, can be embedded. Further, the instructions 2104 may embody one or more of the methods or logic as described. In a particular example, the instructions 2102 may reside completely, or at least partially, within the memory 202 or within the processor 204 during execution by the computer system 2100.
The present invention contemplates a computer-readable medium that includes instructions 2102 or receives and executes instructions 2102 responsive to a propagated signal so that a device connected to a network 2107, such as electronic controllers 201A and 201C and electronic devices 20IB and 20ID, can communicate voice, video, audio, images or any other data over the network 2107. Further, the instructions 2102 may be transmitted or received over the network 2107 via the transmitter 208 and the receiver 206 respectively using the bus 2101. It should be understood that the processor 204, the receiver 206 and the transmitter 208 may be incorporated as a single unit or as one or more separate units. These units may be created in software or may be a physical connection in hardware and are configured to connect with the network 2107, external media, the display 2103, or any other components in system 2100, or combinations thereof. The connection with the network 2107 may be established wirelessly as discussed later. Likewise, the additional connections with other components of the system 2100 may be established wirelessly. The network 2106 may alternatively be directly connected to the bus 2101.
The network 2107 may include wireless networks, Ethernet AVB networks, or combinations thereof. The wireless network may be a cellular telephone network, an 802.11, 802.16, 802.20, 802.1Q or WiMax network. Further, the network 2106 may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols. The system is not limited to operation with any particular

standards and protocols. For example, standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) may be used.
Embodiments of the present application provide option of physically tracking materials and machinery, which help avoid abuse of existing system and resources. The present application provides methods for capturing real time locational and transactional data from equipment, vehicles, machinery, plants and weigh stations and provides all the information at one central server which could be at the project management office. This enables real time monitoring and management of site related activity, material movement, stock maintaining and verifying all the information using technology disclosed above.
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 in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein. The drawings and the forgoing 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.
Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

We claim:
1. A method to manage a project activity involving transport of an amount (X) of material
(M) from a source location (SL) to a destination location (DL) via a material carrying
vehicle (MCV), the method comprising:
(a) receiving transport request information (TRI) comprising at least one of:
• information about the material (M);
• information about the amount (X) of material;
• information about the source location (SL); and
• information about the destination location (DL);

(b) retrieving, based on TRI, handling information (HI), the HI at least comprising information pertaining to the material carrying vehicle;
(c) creating an intelligent data packet (IDU) comprising TRI and HI;
(d) providing the IDU to:

• an electronic controller at SL and/or person in-charge at SL; and
• an electronic controller at DL and/or person in-charge at DL;
(e) receiving:
• source location transaction information (SLTI) from the electronic controller at SL or source location manifest information (SLMI) from an electronic device associated with the person in-charge at SL; and
• destination location transaction information (DLTI) from the electronic controller at DL or destination location acknowledgement information (DLAI) from an electronic device associated with the person in-charge at DL;
(f) generating "transaction information" based on:
a. at least one of SLTI and SLMI; and
b. at least one of DLTI and DLAI; and
(g) indicating completion of the project activity if the "transaction information"
satisfies at least one predetermined criterion.
2. The method as claimed in claim 1, wherein source location transaction information
(SLTI) includes at least one of:
• information about the material (M) provided to the material carrying vehicle;

• information about the amount (X) of material provided to the material carrying vehicle;
• information about the source location (SL); and
• a time stamp.
3. The method as claimed in claim 1, wherein destination location transaction information
(DLTI) includes at least one of:
• information about the material (M) received from the material carrying vehicle;
• information about the amount (X) of material received from the material carrying vehicle;
• information about the destination location (DL); and
• a time stamp.
4. The method as claimed in claim 1, wherein handling information (HI) further comprises:
a. information pertaining to person-in-charge at the source location; and/or
b. information pertaining to person in-charge at the destination location.
5. The method as claimed in any of the preceding claims, further comprising providing a portable data carrying device, and storing the IDU on the portable data carrying device.
6. The method as claimed in any of the preceding claims, wherein the portable data carrying device is further adapted to store thereupon at least one of:

• source location transaction information (SLTI);
• destination location transaction information (DLTI);
• source location manifest information (SLMI); and
• destination location acknowledgement information (DLAI).
7. The method as claimed in any of the preceding claims, wherein source location
transaction information is generated by the electronic controller at the source location
based on source sensor information, the source sensor information being generated by at
least one sensor provided at the source location.

8. The method as claimed in any of the preceding claims, wherein destination location transaction information is generated by the electronic controller at the destination location based on destination sensor information, the destination sensor information being generated by at least one sensor provided at the destination location.
9. The method as claimed in claim 7, wherein the at least one sensor at the source location includes:

• a weight sensor;
• an image sensor;
• a plant telemetry sensor-complex.
10. The method as claimed in claim 8, wherein the at least one sensor at the destination
location includes:
• a weight sensor;
• an image sensor;
• RFID transponder (contactless card).

11. The method as claimed in any of the preceding claims, further comprising receiving tracking information from a processing unit (PU) provided on the material carrying vehicle.
12. The method as claimed in claim 13, wherein the tracking information comprises at least one of:

• a location related data;
• a time stamp data;
• a vehicle condition related data;
• vehicle fuel-level data;
• vehicle driver-ID data;
• vehicle driving-quality data (based on in-built inertial sensors).

13. The method as claimed in any of the preceding claims, wherein generating "transaction information" is further based on the tracking information.
14. The method as claimed in claim 11, wherein the processing unit (PU) provided on the material carrying vehicle is further adapted to receive and store thereupon at least one of:

• source location transaction information (SLTI);
• destination location transaction information (DLTI);
• source location manifest information (SLMI); and
• destination location, acknowledgment information (DLAI).
15. The method as claimed in claim 11, wherein the processing unit (PU) provided on the
material carrying vehicle is adapted to:
• receive the source location transaction information (SLTI) from the electronic controller at SL during a handshake process there between and store the same;
• receive the source location manifest information (SLMI) from an electronic device associated with the person in-charge at SL during a handshake process there between and store the same;
• receive the destination location transaction information (DLTI) from the electronic controller at DL during a handshake process there between and store the same;
• receive the destination location acknowledgement information (DLAI) from an electronic device associated with the person in-charge at DL during a handshake process there between and store the same.
16. A central server to manage a project activity involving transport of an amount (X) of
material (M) from a source location (SL) to a destination location (DL) via a material
carrying vehicle (MCV), the system comprising:
(a) a receiver to receive:
- transport request information (TRI) comprising at least one of:
o information about the material (M);
o information about the amount (X) of material;
o information about the source location (SL); and

o information about the destination location (DL); source location transaction information (SLTI) from an electronic controller at SL or source location manifest information (SLMI) from an electronic device associated with the person in-charge at SL; and
destination location transaction information (DLTI) from an electronic controller at DL or destination location acknowledgement information (DLAI) from an electronic device associated with the person in-charge at DL;
(b) a processor to:
retrieve, based on TRI, handling information (HI), the HI at least comprising information pertaining to the material carrying vehicle; create an intelligent data packet (IDU) comprising TRI and HI; generate "transaction information" based on:
o at least one of SLTI and SLMI; and
o at least one of DLTI and DLAI; indicate completion of the project activity if the "transaction information" satisfies at least one predetermined criterion and
(c) a transmitter to provide the IDU to:
- the electronic controller at SL and/or person in-charge at SL; and
- the electronic controller at DL and/or person in-charge at DL;
17. A system to manage a project activity involving transport of an amount (X) of material (M) from a source location (SL) to a destination location (DL) via a material carrying vehicle (MCV), the system comprising:
(a) a first electronic controller including a first receiver and a first transmitter, the first electronic controller situated at the DL; the first receiver and the first transmitter configured to receive and transmit information respectively;
(b) a first electronic device including a second receiver and a second transmitter, the first electronic device associated with a person-in charge at the SL; the second receiver and the second transmitter configured to receive and transmit information respectively
(c) a second electronic controller including a third receiver and a third transmitter, the second electronic device situated at the DL; the third receiver

and the third transmitter configured to receive and transmit information respectively
(d) a second electronic device including a fourth receiver and a fourth
transmitter, the second electronic device associated with a person in charge at
the DL; the fourth receiver and the fourth transmitter configured to receive
and transmit information respectively;
(e) a processing unit including a fifth receiver and a fifth transmitter, the processing unit provided on the MCV; and
(f) a central device including a receiver, a processor and a transmitter; wherein:
- the receiver is configured to receive:
> a transport request information (TRI) comprising at least one of:
o information about the material (M);
o information about the amount (X) of material; o information about the source location (SL); and o information about the destination location (DL);
> source location transaction information (SLTI) from the first electronic controller at SL or source location manifest information (SLMI) from the first electronic device associated with the person in-charge at SL; and
> destination location transaction information (DLTI) from the second electronic controller at DL or destination location acknowledgement information (DLAI) from the second electronic device associated with the person in-charge at DL;
> tracking information from the processing unit (PU) provided on the material carrying vehicle
- the processor is configured to:
> retrieve, based on TRI, handling information (HI), the HI at least comprising information pertaining to the material carrying vehicle;
> create an intelligent data packet (IDU) comprising TRI and HI;
> generate "transaction information" based on:
o at least one of SLTI and SLAI;
o at least one of DLTI and DLAI; and o the tracking information

> indicate completion of the project activity if the "transaction
information" satisfies at least one predetermined criterion and
a transmitter to provide the IDU to:
> the first electronic controller at SL and/or the first electronic device associated with the person in-charge at SL; and
> the second electronic controller at DL and/or the second electronic device associated with person in-charge at DL.