WO2017132120A1 - Systèmes et procédés pour analyser des opérations d'équipement mobile - Google Patents

Systèmes et procédés pour analyser des opérations d'équipement mobile Download PDF

Info

Publication number
WO2017132120A1
WO2017132120A1 PCT/US2017/014684 US2017014684W WO2017132120A1 WO 2017132120 A1 WO2017132120 A1 WO 2017132120A1 US 2017014684 W US2017014684 W US 2017014684W WO 2017132120 A1 WO2017132120 A1 WO 2017132120A1
Authority
WO
WIPO (PCT)
Prior art keywords
fuel consumption
data
service vehicle
consumption data
processor
Prior art date
Application number
PCT/US2017/014684
Other languages
English (en)
Inventor
Philip Rodoni
Original Assignee
Rubicon Global Holdings, Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Rubicon Global Holdings, Llc filed Critical Rubicon Global Holdings, Llc
Publication of WO2017132120A1 publication Critical patent/WO2017132120A1/fr

Links

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096708—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control
    • G08G1/096716—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control where the received information does not generate an automatic action on the vehicle control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0816—Indicating performance data, e.g. occurrence of a malfunction
    • G07C5/0825—Indicating performance data, e.g. occurrence of a malfunction using optical means
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096733—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place
    • G08G1/096741—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place where the source of the transmitted information selects which information to transmit to each vehicle
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096766—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission
    • G08G1/096775—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission where the origin of the information is a central station
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/20—Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C2205/00—Indexing scheme relating to group G07C5/00
    • G07C2205/02—Indexing scheme relating to group G07C5/00 using a vehicle scan tool
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station

Definitions

  • This disclosure generally relate to a tool that assists operation analysis, and more particularly, relates to a tool provided via a mobile device that provides an operation analysis of mobile equipment.
  • Existing technologies allow a user to monitor the operation of mobile equipment (e.g., a service vehicle) as well as behavior of the driver of the service vehicle.
  • the monitoring can be performed for various purposes, such as promoting safe driving habits, improving security, tracking and reducing fuel consumption of the service vehicle.
  • the monitoring system can monitor and log the locations of the service vehicle, and/or the distances travelled by the service vehicle within a pre-determined period. Such a period can be, for example, classified by the driver of the service vehicle as a time during which the service vehicle is being operated for a specific purpose (e.g., for a business use versus for a personal use).
  • the driver when classifying a certain operation of the service vehicle as for a business use (or for a personal use) can introduce errors in the logging, especially when that operation does not fall within the normal course of operation of the service vehicle.
  • the error can be further exacerbated when the monitoring system does not take into consideration the type of the service vehicle (e.g., whether the service vehicle is a piece of mobile equipment specially designed for non-transportation functions), the type of road the service vehicle operates in, and the action taken during the operation of the service vehicle.
  • the logged data may not be useful for tracking and analyzing the normal operation of the service vehicle.
  • the disclosure is directed toward a system for analyzing operation of a service vehicle.
  • the system may include a server, a data collection device, a memory for storing a set of instructions, and a processor in communication with the server, the data collection device, and the memory.
  • the processor may be configured to execute the set of instructions to receive, from the data collection device, fuel consumption data associated with the service vehicle, and to determine time and location information associated with the service vehicle.
  • the processor may also be configured to execute the set of instructions to determine an operation being performed by the service vehicle, and to selectively transmit the fuel consumption data to the server based on the operation being performed and the time and location information.
  • the disclosure is directed toward a method for analyzing a service vehicle.
  • the method may include collecting fuel consumption data associated with the service vehicle, and generating time and location information associated with the service vehicle.
  • the method may also include determining an operation being performed by the service vehicle and selectively transmitting the fuel consumption data to a server based on the operation being performed and the time and location information.
  • the disclosure is directed toward a mobile device for analyzing a service vehicle.
  • the mobile device may include a memory for storing a set of instructions, and a processor in communication with the server, the data collection device, and the memory.
  • the processor may be configured to execute the set of instructions to receive, from an onboard data collection device, fuel consumption data associated with the service vehicle, and to determine time and location information associated with the service vehicle.
  • the processor may also be configured to execute the set of instructions to determine an operation being performed by the service vehicle and to selectively transmit the fuel consumption data to a remote server based on the operation being performed and the time and location information.
  • FIG. 1 is a block diagram of an exemplary system for analyzing an operation of mobile equipment, consistent with disclosed embodiments
  • FIG. 2 is a block diagram of an exemplary server for analyzing an operation of mobile equipment, consistent with disclosed embodiments;
  • FIG. 3 is a block diagram of an exemplary system for analyzing an operation of mobile equipment consistent with disclosed embodiments
  • FIG. 4 is a block diagram of an exemplary mobile application device for analyzing an operation of mobile equipment, consistent with disclosed embodiments
  • FIG. 5 is a flowchart of an exemplary method for analyzing an operation of mobile equipment, consistent with disclosed embodiments
  • FIG. 6 is a flowchart of an exemplary method for analyzing an operation of mobile equipment, consistent with disclosed embodiments
  • FIGs. 7A and 7B are illustrations of an exemplary user interface for monitoring an operation of mobile equipment, consistent with disclosed
  • FIGs. 8A and 8B are illustrations of an exemplary user interface for displaying an analysis of an operation of mobile equipment, consistent with disclosed embodiments.
  • a mobile device for analyzing an operation of mobile equipment may include a memory device for storing a set of instructions, and one or more hardware processors configured to execute the set of instructions to receive, from one or more data collection devices, fuel consumption data associated with the mobile equipment, and to determine time and location information associated with the mobile equipment.
  • the one or more hardware processors of the mobile device can also be configured to determine, based on the time and location information, an operation by the mobile equipment; to transmit data representing the operation to a server; and to receive, from the server, data representing an analysis of the data representing the operation.
  • the exemplary disclosed embodiments allow the analysis of an operation of mobile equipment based on a type of the mobile equipment, as well as the location and time associated with the operation. As a result, the analysis can be more specific, efficient, and accurate. A result of the analysis can be provided to a user, through a mobile application on a mobile device. The mobile application also allows the user to configure the logging of the operation, to further improve the specificity and efficiency of the analysis.
  • Fig. 1 is a diagram illustrating an exemplary system 100 for analyzing an operation of mobile equipment, consistent with the disclosed embodiments.
  • the mobile equipment can include, for example, a service vehicle that is designed for transportation (e.g., a trash-hauler), equipment designed for non-transportation function (e.g., a mobile office trailer, a mobile crane, etc.), etc.
  • system 100 may include a mobile equipment operation analyzing device 110, one or more data collection devices 120, client device 130, and a network 140.
  • the components and arrangement of the components included in the system 100 may vary.
  • the system 100 may further include other components that perform or assist in the performance of one or more processes consistent with the disclosed embodiments.
  • Mobile equipment operation analyzing device 110 may include one or more computing systems that are configured to execute software instructions stored on one or more memory devices to perform one or more operations consistent with the disclosed embodiments.
  • Mobile equipment operation analyzing device 110 may include one or more of a server, a computer, an embedded system, or a dedicated hardware device.
  • mobile equipment operation analyzing device 110 may be configured as a particular apparatus, system, and the like based on the storage, execution, and/or implementation of the software instructions that perform one or more operations consistent with the disclosed embodiments.
  • mobile equipment operation analyzing device 110 may include hardware and/or software components configured to determine an operation performed by the mobile equipment based on at least one of: one or more locations of the mobile equipment, time and date information associated with the one or more locations, and attribute information associated with the mobile equipment. Mobile equipment operation analyzing device 110 can then determine whether to log the operation data based on the determined operation.
  • mobile equipment operation analyzing device 110 can determine that the trash-hauler is dumping trash at a landfill site and is not travelling on a public road. Based on this determination, mobile equipment operation analyzing device 110 can then determine to log operation data (e.g., fuel consumption, distance travelled, etc.) associated with the trash-dumping operation during that certain time and on that certain date. As another illustrative example, mobile equipment operation analyzing device 110 can also determine not to log the operation data of that service vehicle, when mobile equipment operation analyzing device 110 determines that the service vehicle is travelling on a public road outside the boundary of the landfill site.
  • operation data e.g., fuel consumption, distance travelled, etc.
  • mobile equipment operation analyzing device 110 can perform the determination of analyzing (or not analyzing) operation data based on data provided by data collection devices 120 (e.g., via client device 130), and based on information from a configuration database and a location database (not shown in Fig. 1). Mobile equipment operation analyzing device 110 can also provide a result of the analysis to, for example, client device 130, or other devices for displaying and/or further analysis.
  • Data collection devices 120 can include hardware and software systems configured to obtain operation data of mobile equipment.
  • the operation data can include, for example, location information of the mobile equipment, fuel consumption information of the mobile equipment, timing information associated with the location and fuel consumption information, and attribute information of the mobile equipment.
  • Figs. 1 and 3 illustrate data collection devices 120 and client device 130 are separate devices, it is understood that in some embodiments, at least a part of data collection devices 120 can also be included in client device 130.
  • the location information can include but not limited to: longitude and latitude of the mobile equipment, direction and speed of movement of the mobile equipment, etc.
  • data collection devices 120 can include a global positioning satellite (GPS) receiver, an accelerometer, a gyroscope, an electronic compass, etc., to provide the aforementioned location information.
  • GPS global positioning satellite
  • the fuel consumption information can be obtained from, for example, an onboard diagnostic (OBD) port that conforms to OBD-II standard, and data collection devices 120 can include hardware and software interfaces to an OBD port to acquire the fuel consumption information.
  • OBD onboard diagnostic
  • Data indicative of fuel consumption e.g., distance travelled, odometer reading, engine fuel settings, engine speed and load, etc.
  • OBD port can also be acquired from the OBD port.
  • Timing information can include times and dates associated with the location and fuel consumption information, and data collection devices 120 can include hardware and software (e.g., a timer) to determine the times and dates.
  • the timing information can also be obtained by a GPS receiver included in data collection devices 120.
  • Attribute information can include information that can be used to identify and/or to classify the mobile equipment.
  • the information can include, for example, a service vehicle identification number (VI N), a serial number, a model number, or any information that can be used to determine a type of the mobile equipment (e.g., whether it is a trash-hauler, a mobile office trailer, a mobile crane, etc.).
  • data collection devices 120 can acquire at least some of the information (e.g., a VIN number) from the OBD port.
  • Data collection devices 120 can also be configured (e.g., by client device 130) to collect the operation data at a pre-determined rate (e.g., once every minute), and to transmit the operation data (e.g., wirelessly or using any suitable means) to client device 130 and/or mobile equipment operation analyzing device 110.
  • a pre-determined rate e.g., once every minute
  • the operation data e.g., wirelessly or using any suitable means
  • Client device 130 may be one or more computing systems that are configured to execute software instructions for performing one or more operations consistent with the disclosed embodiments.
  • client device 130 may be a mobile device (e.g., a tablet, smartphone, etc.), a laptop, a desktop computer, a server, an embedded system, a dedicated hardware device, etc.
  • Client device 130 may include one or more processors configured to execute software instructions stored in memory.
  • Client device 130 may also include software that, when executed by a processor, performs known network-related communication and content display processes.
  • client device 130 may execute browser software that generates and displays interface screens including content on interface hardware (e.g., a display device) included in, or connected to, client device 130.
  • interface hardware e.g., a display device
  • Client device 130 may also execute software that packetizes operation data received from one or more data collection devices 120 according to any suitable protocol (e.g., Transmission Control Protocol/Internet Protocol (TCP/IP)), and transmits the packetized operation data to mobile equipment operation analyzing device 110 via network 140.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • client device 130 may be a mobile device configured to execute one or more mobile applications ("apps").
  • the app can be mobile equipment monitoring app that provides an interface to receive and display configuration information from a user.
  • Client device 130 can then configure the one or more data collection devices 120 based on the received configuration information.
  • client device 130 can configure data collection devices 120 to collect specific categories of operation data (e.g., fuel consumption) at a particular location and at a particular time and date.
  • the app can also cause client device 130 to perform some of the functionalities of mobile equipment operation analyzing device 110. For example, it may also determine an operation performed by the mobile equipment based on at least one of: one or more locations of the mobile equipment, time and date information associated with the one or more locations, and attribute information associated with the mobile equipment. The app can then determine whether to transmit the operation data to mobile equipment operation analyzing device 110 based on the determined operation.
  • the app can determine that the trash-hauler is dumping trash at a landfill site and is not travelling on a public road. Based on this determination, the app can determine to cause client device 130 to transmit operation data (e.g., fuel consumption, distance travelled, etc.) associated with that trash-dumping operation during that certain time and on that certain date to mobile equipment operation analyzing device 110, which can then log the data and provide the data for displaying and/or further analysis.
  • operation data e.g., fuel consumption, distance travelled, etc.
  • the app can also determine to instruct client device 130 not to transmit the operation data of that service vehicle, after determining that the service vehicle is travelling on a public road outside the boundary of the landfill site.
  • the app can determine the operation based on operation data received from data collection devices 120, and based on information from a configuration database and a location database (not shown in Fig. 1).
  • client device 130 can reduce wireless transmissions to mobile equipment operation analyzing device 110 to reduce power consumption.
  • Network 140 may be any type of network configured to provide communications between components of system 100.
  • network 140 may be any type of network (including infrastructure) that provides communications, exchanges information, and/or facilitates the exchange of information, such as the Internet, a Local Area Network, Near Field Communication (NFC), WIFI, Bluetooth ®, or other suitable connection(s) that enables the sending and receiving of information between the components of system 100.
  • NFC Near Field Communication
  • WIFI Wireless Fidelity
  • Bluetooth ® or other suitable connection(s) that enables the sending and receiving of information between the components of system 100.
  • one or more components of system 100 may communicate directly through a dedicated communication link(s) (not shown), such as a link between mobile equipment operation analyzing device 110 and client device 130.
  • Fig. 2 shows an exemplary server 200 for analyzing an operation of mobile equipment, consistent with the present disclosure.
  • server 200 may correspond to mobile equipment operation analyzing device 110. It should be understood, however, that variations of server 200 may correspond to client device 130, and/or components thereof.
  • server 200 may include one or more
  • server 200 may be an embedded system or similar computing device(s) that generate, maintain, and provide web site(s) and/or mobile applications consistent with disclosed embodiments.
  • Server 200 may be standalone, or it may be part of a subsystem, which may be part of a larger system.
  • server 200 may represent distributed servers that are remotely located and communicate over a network (e.g., network 140) or a dedicated network, such as a LAN.
  • Processor 210 may include one or more known processing devices, such as a microprocessor from the PentiumTM or XeonTM family manufactured by IntelTM, the TurionTM family manufactured by AMDTM, or any of various processors manufactured by Sun Microsystems. The disclosed embodiments are not limited to any type of processor(s) configured in server 200.
  • Memory 220 may include one or more storage devices configured to store instructions used by processor 210 to perform functions related to disclosed embodiments.
  • memory 220 may be configured with one or more software instructions, such as prograrh(s) 222 that may perform one or more operations when executed by processor 210.
  • the disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks.
  • memory 220 may include a single program 221 that performs the functions of the server 200, or program 222 could comprise multiple programs.
  • processor 210 may execute one or more programs located remotely from server 200.
  • mobile equipment operation analyzing device 110 and client device 130 may, via server 200, access one or more remote programs that, when executed, perform functions related to certain disclosed embodiments.
  • Memory 220 may also store data 224 that may reflect any type of information in any format that the system may use to perform operations consistent with the disclosed embodiments.
  • I/O devices 230 may be one or more devices configured to allow data to be received and/or transmitted by server 200.
  • I/O devices 230 may include one or more digital and/or analog communication devices that allow server 200 to communicate with other machines and devices, such as other components of system 100.
  • Server 200 may also be communicatively connected to one or more database(s) 240.
  • Server 200 may be communicatively connected to database(s) 240 through network 140.
  • Database 240 may include one or more memory devices that store information and are accessed and/or managed through server 200.
  • database(s) 240 may include MS SQL, OracleTM databases, SybaseTM databases, or other relational databases or non-relational databases, such as Hadoop sequence files, HBase, or Cassandra.
  • the databases or other files may include, for example, data and information related to the source and destination of a network request, the data contained in the request, etc. Systems and methods of disclosed embodiments, however, are not limited to separate databases.
  • system 100 may include database 240.
  • database 240 may be located remotely from the system 100.
  • Database 240 may include computing components (e.g., database management system, database server, etc.) configured to receive and process requests for data stored in memory devices of database(s) 240 and to provide data from database 240.
  • computing components e.g., database management system, database server, etc.
  • Fig. 3 is a diagram illustrating an exemplary configuration of the components of system 100, including various additional components and features thereof. It should be understood that the configuration of system 100 depicted in Fig. 3 is exemplary, and that other configurations, including additional and/or alternative components and features are possible.
  • mobile equipment operation analyzing device 110 may include features configured to monitor an operation of mobile equipment, and to provide a result of the monitoring (e.g., a log) to client device 130.
  • mobile equipment operation analyzing device 110 may include an equipment operation determination module 302, a fuel consumption determination module 304, and a log generation module 306.
  • “modules” also known as “engines” may be implemented in software, hardware, firmware, a mix of any of those, or the like.
  • the disclosed "modules" are implemented in software, they may be stored in a memory associated with mobile equipment operation analyzing device 110. Processors, I/O devices, and memory devices may be used to perform processes to implement and facilitate operations of the modules.
  • the modules may include code instructions executable by one or more processors, alone or in various combinations with other modules disclosed in this or other embodiments.
  • equipment operation determination module 302, fuel consumption determination module 304, and log generation module 306 may be configured to interact with each other, and/or with other modules of mobile equipment operation analyzing device 110, shown or not shown in Fig. 3, to perform functions consistent with disclosed embodiments.
  • the disclosed "modules" are implemented in hardware, they may comprise an embedded system or other dedicated hardware configured by machine code, assembly code, or the like to interact with other modules of mobile equipment operation analyzing device 110 to perform functions consistent with disclosed embodiments.
  • equipment operation determination module 302 can determine an operation performed by the mobile equipment.
  • equipment operation determination module 302 may be configured to execute software instructions to determine the operation based on at least one of: one or more locations of the mobile equipment, time and date information associated with the one or more locations, and attribute information associated with the mobile equipment. Using the illustrative example discussed above, based on a
  • mobile equipment operation analyzing device 110 can determine that the trash-hauler is dumping trash at a landfill site and is not travelling on a public road.
  • Equipment operation determination module 302 can interact with other components of system 100 to collect data for the determination.
  • system 100 can also include configuration database 310 and location database 320.
  • Configuration database 310 can store configuration information related to the mobile equipment.
  • configuration database 310 can store a mapping between a VIN number and a type of a service vehicle (e.g., a trash-hauler), or a mapping between any kind of identifier (e.g., a serial number) and any attribute of the mobile equipment (e.g., a mobile crane).
  • equipment operation determination module 302 can determine a type of the service vehicle (or mobile equipment) for a set of operation data received from data collection devices 120 (via client device 130). For example, equipment operation determination module 302 can match the VIN number included in the operation data (received from OBD of the service vehicle by data collection devices 120) with the data stored in configuration database 310 to determine that operation data is associated with a trash-hauler.
  • Location database 320 can store information related to different sites where the mobile equipment may be located. For example, location database 320 can store the coordinates (e.g., latitude, longitude, etc.) of various sites (e.g., a landfill site), the operating hours of these sites, etc.
  • mobile equipment operation analyzing device 110 can obtain, as part of operation data, location information and time information from data collection devices 120 (via client device 130).
  • Equipment operation determination module 302 can then compare the location information and time information against the data stored in location database 320, to determine that a service vehicle is operating at a landfill site. Based also on a determination that the service vehicle is trash-hauler, equipment operation determination module 302 can then determine that a set of operation data is associated with a trash-dumping operation at landfill site.
  • fuel consumption determination module 304 can determine an amount of fuel consumption during an operation (e.g., determined by equipment operation determination module 302) by the mobile equipment, based on the operation data received from data collection devices 120 and information from configuration database 310. For example, in a case where fuel consumption data is not available from the operation data received from data collection devices 120, fuel consumption determination module 304 can estimate fuel consumption based on at least one of these data: the duration of the operation, the distance travelled by the equipment within the duration, the speed of movement of the equipment, gas mileage (e.g., of a service vehicle), etc.
  • configuration database 310 can store historical data of fuel consumption of the equipment.
  • the historical data can be associated with a certain speed of movement of the equipment, or with a certain location that indicates a certain operation being performed by the equipment. Based on the operating data (e.g., speed, location, etc.) of tine equipment and the historical data stored at configuration database 310, fuel consumption determination module 304 can then determine an amount of fuel consumption during an operation determined by equipment operation determination module 302.
  • fuel consumption determination module 304 can estimate an amount of fuel consumption by the trash-hauler within the duration when the trash-hauler operates at a landfill site, based on the speed of movement of the trash- hauler, historical data that reflects a rate of fuel consumption by the trash-hauler when operating at a landfill site, and the amount of time spent by the trash-hauler at the landfill site.
  • log generation module 306 can generate data that represent a result of analyzing an operation of the mobile equipment. For example, log generation module 306 can provide a log of fuel consumption by the mobile equipment, as determined by fuel consumption determination module 304, for a specific operation identified by equipment operation determination module 302. For example, based on a determination that a trash-hauler performs trash-dumping at a landfill site during a specific time and on a specific date, by equipment operation determination module 302, log generation module 306 can determine to provide a log of fuel consumption by the trash-hauler when performing the trash-dumping during that specific time and on that specific date.
  • log generation module 306 can also determine to provide a log of speed of movement of the trash-hauler in the landfill site. Further, log generation module 306 can also determine to omit some of the operation data from logging. For example, log generation module 306 can determine to omit the fuel consumption data of the trash-hauler during the time when it is determined to be travelling on a public road. Log generation module 306 can also determine to omit the fuel consumption data of the trash-hauler at a landfill site, if equipment operation determination module 302 determines, based on information stored in location database 320, that the landfill site was not open for business at the time when the trash-hauler is at the landfill site.
  • configuration database 310 can store a set of rules governing analysis of operation data, log generation, and/or operation data transmission, and log generation module 306 can determine the scope of data to be analyzed and included in a logging result, based on the rules stored at configuration database 310.
  • the rules can define that operation data generated when the mobile equipment is at a certain location is to be logged.
  • the rules can also define that operation data generated when the mobile equipment is travelling on a public road is not to be logged.
  • the rules can also define the operation data to be logged (e.g., fuel consumption, duration, distance travelled, etc.).
  • the rules can also be associated with a particular type of mobile equipment, and can have different definitions for different types of mobile equipment (e.g., a trash-hauler versus an a mobile crane).
  • client device 130 can provide an interface to receive and display configuration information from a user. After receiving configuration information from the user, client device 130 can also store the received configuration information at configuration database 310.
  • mobile equipment operation analyzing device 110 can then transmit the logging result to a client device (e.g., client device 130) for displaying and/or further analysis.
  • a client device e.g., client device 130
  • Mobile equipment operation analyzing device 110 can also store the logging result in a database for future analysis.
  • device 130 may be a mobile device configured to execute mobile application 332.
  • Mobile application 332 can provide an interface to receive and display configuration information from a user. Client device 130 can then configure the one or more data collection devices 120 based on the received configuration information.
  • Mobile application 332 can also cause client device 130 to perform some of the functionalities of mobile equipment operation analyzing device 110.
  • mobile application 332 can provide at least some of the functionalities of equipment operation determination module 302 and fuel consumption determination module 304, and can cause client device 130 to interact with configuration database 310 and location database 320, to determine an operation of the mobile equipment and the fuel consumption during that operation. Based on the rules governing analysis and log generation stored at configuration database 310, mobile application 332 can cause client device 130 to selectively transmit operation data to log generation module 306 of mobile equipment operation analyzing device 110, which can cause some of the operation data (generated by data collection devices 120) to be omitted from analysis and log generation. With such an arrangement, power consumption of client device 130 can be reduced.
  • Fig. 4 depicts an exemplary client device 130 in more detail, consistent with disclosed embodiments.
  • Client device 130 may include memory hardware 410, processing hardware 420, and interface hardware 430.
  • Other features of client device 130 may include a location device (e.g., a GPS device) configured to determine a location of client device 130, and may also include a connection device configured to wirelessly connect to network 140 (e.g., a cellular communication device, Wi-Fi Device, etc.).
  • a location device e.g., a GPS device
  • connection device configured to wirelessly connect to network 140 (e.g., a cellular communication device, Wi-Fi Device, etc.).
  • Client device 130 may be configured to execute a mobile application 450 stored in memory hardware 410.
  • client device 130 may be a smartphone, tablet, or watch configured to run a mobile operating system (e.g., iOS, Android, etc.) which may be compatible with a variety of mobile applications provided by third-party providers.
  • mobile application 450 provides at least some of the functionalities of mobile application 332 of Fig. 3, which enables client device 130 to provide monitoring of an operation of mobile equipment to a user of client device 130 via mobile application 450.
  • Client device 130 may operate in conjunction with other devices in order to provide monitoring of an operation of mobile equipment. For example, client device 130 may communicate with mobile equipment operation analyzing device 110, configuration database 310 and location database 320 via network 140, and with data collection devices 120.
  • Fig. 5 is a flowchart of an exemplary method 500 for analyzing an operation of mobile equipment, consistent with the present disclosure.
  • Method 500 can be performed by client device 130 when executing instructions (e.g., mobile application 332) via processing hardware 420.
  • Client device 130 can be
  • a remote server communicatively coupled (e.g., via network 140) with a remote server that performs at least some of the functionalities (e.g., logging a monitoring result) of mobile equipment operation analyzing device 110, and with data collection devices 120 configured to provide operation data of the mobile equipment.
  • client device 130 may receive operation data of mobile equipment.
  • the operation data can include, for example, location information of the mobile equipment, fuel consumption information of the mobile equipment, timing information associated with the location and fuel consumption information, and attribute information of the mobile equipment.
  • Client device 130 may receive the operation data from data collection devices 120, which can include, for example, a GPS receiver, an interface to OBD ports, a timer, etc.
  • client device 130 may determine configuration information for analyzing the received data.
  • the configuration information may include, for example, a set of rules governing analysis of operation data, log generation and/or transmission of operation data.
  • the rules can define that operation data generated when the mobile equipment is travelling on a public road is not to be logged. As an extension of such a rule, operation data generated when the mobile equipment is travelling on a public road are is not to be transmitted to the server for logging.
  • the rules can also define that operation data generated when the mobile equipment is at a certain location is to be logged, and such operation data is to be transmitted to the server for analysis and logging.
  • Client device 130 can determine the configuration information based on, for example, data stored in configuration database 310, and information provided by a user via an interface provided by the execution of mobile application 332 by client device 130.
  • client device 130 can determine whether to transmit the received operation data to the server, based on the configuration information determined in step 504. For example, based on the configuration information and the operation data (e.g., a VIN number, location and time information, etc.), client device 130 can determine that the operation data is associated with a certain type of service vehicle (e.g., a trash-hauler), and that the operation data is generated when the trash-hauler is operating at a certain landfill rather than travelling on a public road. If the rules in the configuration information define that operation data generated when a trash-hauler is operating at that landfill is to be logged, client device 130 can then determine to transmit the received operation data to the server. On the other hand, if the operation data indicates that the trash-hauler is travelling on a public road, client device 130 can determine not to transmit the received operation data to the server.
  • a certain type of service vehicle e.g., a trash-hauler
  • client device 130 can then transmit the received operation data to the server, in step 510.
  • client device 130 can also perform additional analysis on the received operation data, and transmit a result of the additional analysis to the server, in step 510. For example, in a case where fuel consumption data is not available from the operation data received from data collection devices 120, client device 130 can estimate fuel consumption based on at least one of these data: the duration of the operation, the distance travelled by the equipment within the duration, the speed of movement of the equipment, gas mileage (e.g., of a service vehicle), etc.
  • configuration database 310 can store historical data of fuel consumption of the equipment.
  • the historical data can be associated with a certain speed of movement of the equipment, or with a certain location that indicates a certain operation being performed by the equipment.
  • client device 130 can then determine an amount of fuel consumption, and transmit data that reflects the amount of fuel consumption (as well as other information such as a location and a time/date associated with tine fuel consumption) to the server, in step 510.
  • Client device 130 can packetize the operation data into data packets according to any suitable protocol (e.g., TCP/IP), and then transmit the packets to the server via network 140.
  • any suitable protocol e.g., TCP/IP
  • Fig. 6 is a flowchart of an exemplary method 600 for analyzing an operation of mobile equipment, consistent with the present disclosure.
  • Method 600 can be performed by a server (e.g., server 200 of Fig. 2) when executing instructions (e.g., programs 222) via processors 210 to perform at least some of the instructions (e.g., programs 222) via processors 210 to perform at least some of the instructions (e.g., programs 222) via processors 210 to perform at least some of the
  • Server 200 can be communicatively coupled with a client device (e.g., client device 130) configured to transmit operation data of the mobile equipment.
  • client device 130 e.g., client device 130
  • server 200 may receive operation data of mobile equipment, in step 602.
  • the operation data can include, for example, location information of the mobile equipment, fuel consumption information of the mobile equipment, timing information associated with the location and fuel consumption information, and attribute information of the mobile equipment.
  • Server 200 may receive the operation data from client device 130 via network 140.
  • server 200 may determine configuration information for analyzing the received data.
  • the configuration information may include, for example, a set of rules governing log generation.
  • Server 200 can determine the configuration information based on, for example, data stored in configuration database 310, and information provided by a user via an interface provided by the execution of mobile application 332 by client device 130.
  • server 200 can determine whether to generate a logging report for the received operation data, based on the configuration information determined in step 604. For example, based on the configuration information and the operation data (e.g., a VIN number, location and time information, etc.), server 200 can determine that the operation data is associated with a certain type of service vehicle (e.g., a trash-hauler), and that the operation data is generated when the trash-hauler is operating at a certain landfill rather than travelling on a public road. If the rules in the configuration information define that operation data generated when a trash-hauler is operating at that landfill is to be logged, server 200 can then determine to log the received operation data.
  • a certain type of service vehicle e.g., a trash-hauler
  • server 200 can determine to omit the received operation data from logging. In some embodiments, at least part of step 606 can be performed by equipment operation determination module 302 of Fig. 3. [064] If server 200 determines to generate a logging report for the received operation data, in step 608, server 200 can then generate a logging report in step 610. In some embodiments, server 200 can also perform additional analysis on the received operation data before generating the logging report in step 610.
  • server 200 can estimate fuel consumption based on at least one of these data: the duration of the operation, the distance travelled by the equipment within the duration, the speed of movement of the equipment, gas mileage (e.g., of a service vehicle), as well as historical data of fuel consumption of the equipment Based on the operating data (e.g., speed, location, etc.) of the equipment and the historical data stored at configuration database 310, server 200 can then determine an amount of fuel consumption, and associate the amount with other information, such as a location and a time/date, in step 610.
  • these data the duration of the operation
  • the distance travelled by the equipment within the duration the speed of movement of the equipment
  • gas mileage e.g., of a service vehicle
  • server 200 can then determine an amount of fuel consumption, and associate the amount with other information, such as a location and a time/date, in step 610.
  • Server 200 can then include the fuel consumption and location and time/date information in the log. Server 200 can also include other operation information, such as a moving speed of the mobile equipment, in the logging report as well. In some embodiments, at least a part of step 610 can be performed by fuel consumption determination module 304 and log generation module 306 of Fig. 3.
  • Server 200 can provide the logging report in various ways.
  • server 200 can host a web site that includes the logging report.
  • the client device 130 (or any other devices) can then access the web site and display the logging report in a browser.
  • Server 200 can also generate a file (e.g., a spreadsheet, a document file, etc.) that includes data of the logging report, and transmit the file to client device 130 or to any other devices that have suitable software to open and render the file for displaying.
  • a file e.g., a spreadsheet, a document file, etc.
  • the logging of an operation of mobile equipment can be performed based on a type of the mobile equipment, as well as the location and time associated with the operation. As a result, the logging can be more specific and efficient, which allows more accurate analysis of the operation of the mobile equipment.
  • FIGs. 7A and 7B are illustrations of an exemplary user interface 700 for an monitoring operation of mobile equipment, consistent with the present disclosure.
  • interface 700 can be provided by client device 130 when executing mobile application 332.
  • interface 700 includes a map 702, an equipment attribute field 712, and options 722, 724, and 726.
  • map 702 provides a graphical representation of an area within which the mobile equipment is located.
  • Map 702 includes
  • Map 702 can also include an indication of the location of the mobile equipment (e.g., as denoted by symbol 704).
  • the display of map 702 can be generated and updated based on location information of the mobile equipment (e.g., based on location information provided by data collection devices 120).
  • interface 700 can also provide other options (not shown in Figs. 7A-C) for manipulating the display of map 702, such as zooming in and out of a particular area in the map.
  • equipment attribute field 712 can provide an indication about a type of the mobile equipment of which an operation is being monitored. For example, as shown in Fig. 7 A, an operation of a trash-hauler is being monitored.
  • the type of mobile equipment can be determined based on, for example, VI N number received as part of the operation data provided by data collection devices 120.
  • options 722, 724, and 726 may allow a user to select locations and data to be monitored.
  • option 722 allows a user to select one or more locations from recycle centers A and B, landfill site C, and construction site D, for logging operation data.
  • client device 130 detects a selection of recycle center B from option 722
  • client device 130 can start logging operation data of the mobile equipment when the mobile equipment is detected to be within boundary 703 (for example, based on the location information from data collection devices 120).
  • Option 724 allows a user to select logging operation data when the mobile equipment is on a public road (e.g., public roads X and Y).
  • client device 130 can start logging operation data of the mobile equipment when the mobile equipment is detected to be on public road Y.
  • Option 726 allows a user to select a certain type of operation data to be logged. For example, as shown in Fig. 7A, option 726 allows a user to select one or more data type to be logged from distance travelled, fuel consumption, or duration. [071]
  • available options 722, 724, and 726 can be updated based on a type of the mobile equipment.
  • option 724 for logging of operation on a public road
  • the unavailability can be indicated by, for example, graying-out of the option.
  • option 724 is available for a mobile crane.
  • fuel consumption data logging option is provided in option 726, while for a mobile crane, fuel consumption data logging option is not available, and has been grayed-out.
  • options 722 for selecting a location for logging
  • FIGs. 8A and 8B are illustrations of an exemplary user interface 800 for displaying operation logs of mobile equipment, consistent with disclosed
  • interface 800 can include a browser interface configured to display a webpage that includes operation log data hosted by server 200, or any suitable interface configured to display the content of a file transmitted by server 200 that includes the log data.
  • interface 800 can be provided by client device 130 when executing mobile application 332. As shown in Figs. 8A-B, interface 800 includes an equipment identification field 802, an equipment type field 804, a monitoring period field 806, and a table 808. Table 808 can further include columns 810, 812, 814, 816, and 818.
  • equipment Identification field 802 is configured to display identification information of the mobile equipment.
  • the identification information can include, for example, a service vehicle VI N number (as shown in Fig. 8A), an equipment serial number (as shown in Fig. 8B), or any other kinds of information that can be used to identify the equipment.
  • the identification can be part of operation data received by data collection devices 120 (e.g., a VIN number), or determined by client device 130 (e.g., input by a user).
  • Equipment type field 804 is configured to display information that indicates a type of the mobile equipment (e.g., a trash-hauler, a mobile crane, etc.).
  • the type information can be generated by server 200 based on the equipment identification information and configuration data stored in configuration database 310.
  • Monitoring period field 806 is configured to display time and date information of a period within which the monitoring was performed. For example, in this illustrative example, interface 800 displays a result of monitoring within a period between January 1 , 2015 to January 7, 2015. [074]
  • table 808 is configured to display operation log data generated based on the rules governing log generation stored in configuration database 310. In the illustrative example discussed above, the rules can define that the fuel consumption of a trash-hauler when operating away from a public road is to be logged, as reflected in the data displayed in table 808 of Fig. 8A.
  • column 810 shows the locations of the trash-hauler where operation data was logged, including recycle centers A and B.
  • Columns 812 and 814 shows the date and time of the operations, while column 816 shows an amount of fuel consumed (in gallons) during the operations.
  • the rules can also define that the fuel consumption of a mobile crane can be logged regardless of whether the mobile crane is traveling on a public road or being operated on a site.
  • column 810 shows that the fuel consumption of the mobile crane is logged when the mobile crane is within construction site D, and when the mobile crane is travelling on public road Y. Additional information can also be shown in table 808.
  • fuel consumption data is not available in the operation data provided by data collection devices 120, but data representing the distances travelled is available. Therefore, in Fig. 8B, an additional column 818 is provided to display information about distance travelled.
  • column 816 of Fig. 8B also includes an indication that the fuel consumption figure is an estimate, while in Fig. 8A, column 816 includes an indication that the figure represents actual fuel consumption.
  • the exemplary disclosed embodiments allow the analysis of an operation of mobile equipment based on a type of the mobile equipment, as well as the location and time associated with the operation. As a result, the analysis can be more specific, efficient, and accurate. A result of the analysis can be provided to a user, through a mobile application on a mobile device. The mobile application also allows the user to configure the logging of the operation, to further improve the specificity and efficiency of the analysis.
  • Computer programs created on the basis of the written description and methods of this specification are within the skill of a software developer.
  • the various programs or program modules can be created using a variety of programming techniques.
  • program sections or program modules can be designed in or by means of Java, C, C++, assembly language, or any such programming languages.
  • One or more of such software sections or modules can be integrated into a computer system, computer-readable media, or existing communications software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Atmospheric Sciences (AREA)
  • Traffic Control Systems (AREA)

Abstract

La présente invention concerne un système pour analyser le fonctionnement d'un véhicule de service. Le système peut comporter un serveur, un dispositif de collecte de données, une mémoire pour stocker un ensemble d'instructions, et un processeur en communication avec le serveur, le dispositif de collecte de données et la mémoire. Le processeur peut être configuré pour exécuter l'ensemble d'instructions pour recevoir, depuis le dispositif de collecte de données, des données de consommation de carburant associées au véhicule de service, et pour déterminer des informations de temps et d'emplacement associées au véhicule de service. Le processeur peut en outre être configuré pour exécuter l'ensemble d'instructions pour déterminer une opération étant effectué par le véhicule de service, et pour transmettre sélectivement les données de consommation de carburant au serveur sur la base de l'opération étant effectuée et des informations de temps et d'emplacement.
PCT/US2017/014684 2016-01-25 2017-01-24 Systèmes et procédés pour analyser des opérations d'équipement mobile WO2017132120A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662286880P 2016-01-25 2016-01-25
US62/286,880 2016-01-25

Publications (1)

Publication Number Publication Date
WO2017132120A1 true WO2017132120A1 (fr) 2017-08-03

Family

ID=59398889

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/014684 WO2017132120A1 (fr) 2016-01-25 2017-01-24 Systèmes et procédés pour analyser des opérations d'équipement mobile

Country Status (1)

Country Link
WO (1) WO2017132120A1 (fr)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6141609A (en) * 1993-11-08 2000-10-31 Mannesmann Aktiengesellschaft Device for recording information on a vehicle's itinerary
EP2239710A1 (fr) * 2009-04-08 2010-10-13 Lagarde Spedition spol. s.r.o. Procédé de détermination de la consommation en carburant de véhicules poids-lourd
US20100280734A1 (en) * 2006-06-20 2010-11-04 Zonar Systems, Inc. Method and apparatus to encode fuel use data with gps data and to analyze such data
US20110166773A1 (en) * 2009-10-29 2011-07-07 Greenroad Driving Technologies Ltd. Method and device for evaluating vehicle's fuel consumption efficiency
WO2012012655A2 (fr) * 2010-07-21 2012-01-26 Eaton Corporation Système et procédé pour optimiser l'économie en carburant au moyen d'informations prédictives relatives à l'environnement et au comportement du conducteur
US20150004572A1 (en) * 2013-06-26 2015-01-01 Caterpillar Inc. Real-Time Operation-Based Onboard Coaching System
US20150052987A1 (en) * 2013-08-21 2015-02-26 Hyundai Motor Company Method and system for informing fuel efficient driving
US20150177001A1 (en) * 2013-12-20 2015-06-25 Verizon Patent And Licensing Inc. System and method for providing a dynamic telematics dashboard
US20150310674A1 (en) * 2014-04-29 2015-10-29 Caterpillar Inc. System for providing on-site service for industrial equipment
US20160377445A1 (en) * 2015-06-23 2016-12-29 Rubicon Global Holdings, Inc. System, method, and app for managing waste services

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6141609A (en) * 1993-11-08 2000-10-31 Mannesmann Aktiengesellschaft Device for recording information on a vehicle's itinerary
US20100280734A1 (en) * 2006-06-20 2010-11-04 Zonar Systems, Inc. Method and apparatus to encode fuel use data with gps data and to analyze such data
EP2239710A1 (fr) * 2009-04-08 2010-10-13 Lagarde Spedition spol. s.r.o. Procédé de détermination de la consommation en carburant de véhicules poids-lourd
US20110166773A1 (en) * 2009-10-29 2011-07-07 Greenroad Driving Technologies Ltd. Method and device for evaluating vehicle's fuel consumption efficiency
WO2012012655A2 (fr) * 2010-07-21 2012-01-26 Eaton Corporation Système et procédé pour optimiser l'économie en carburant au moyen d'informations prédictives relatives à l'environnement et au comportement du conducteur
US20150004572A1 (en) * 2013-06-26 2015-01-01 Caterpillar Inc. Real-Time Operation-Based Onboard Coaching System
US20150052987A1 (en) * 2013-08-21 2015-02-26 Hyundai Motor Company Method and system for informing fuel efficient driving
US20150177001A1 (en) * 2013-12-20 2015-06-25 Verizon Patent And Licensing Inc. System and method for providing a dynamic telematics dashboard
US20150310674A1 (en) * 2014-04-29 2015-10-29 Caterpillar Inc. System for providing on-site service for industrial equipment
US20160377445A1 (en) * 2015-06-23 2016-12-29 Rubicon Global Holdings, Inc. System, method, and app for managing waste services

Similar Documents

Publication Publication Date Title
US11870704B2 (en) Instant notification of load balance and resource scheduling based on resource capacities and event recognition
CA2985509C (fr) Determination de types de segment de rue
US11170589B2 (en) Emergency event based vehicle data logging
US10061854B2 (en) Trusted maps: updating map locations using trust-based social graphs
US9576407B1 (en) Systems and methods for mobile mileage tracking
US9275010B2 (en) Method for improving fuel economy of an operated vehicle
US9217656B2 (en) Internet telematics service providing system and internet telematics service providing method for providing mileage-related driving information
US20110184784A1 (en) Tracking Carbon Footprints
CN103890816A (zh) 用于事故重建的系统和方法
CN102801803B (zh) 基于b/s架构的车辆监控系统
US9785897B2 (en) Methods and systems for optimizing efficiency of a workforce management system
US20140195453A1 (en) System, method, and apparatus for managing fluid transportation
US20170229016A1 (en) Mobile automobile parking application
US20190108756A1 (en) System and method for tracking and logging asset activity
US8744410B2 (en) Communication of position data via text message
DK178501B1 (en) Construction site image management system and method
US20160267423A1 (en) Systems and methods for mobile workforce management system trusted agent work order processing
WO2014089163A2 (fr) Système, procédé et appareil de gestion de transport de fluide
US20170221284A1 (en) Vehicle fluid replacement monitoring system and method
WO2017132120A1 (fr) Systèmes et procédés pour analyser des opérations d'équipement mobile
CN102831653B (zh) 一种出租车计价信息无线修改方法
CN113282638B (zh) 一种城建用车识别方法和装置
JP5256222B2 (ja) 行動状況を判定するための方法、装置及びプログラム
CN106875044B (zh) 提供预设服务建议的系统及其方法
WO2014155110A1 (fr) Procédé et appareil de mesure de distance

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17744751

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 04.12.2018)

122 Ep: pct application non-entry in european phase

Ref document number: 17744751

Country of ref document: EP

Kind code of ref document: A1