System and method for remote machine data transfer

TECHNICAL FIELD

0001The present disclosure relates generally to data transfer between remote assets and, more particularly, to systems and methods for transferring large volumes of raw machine data between geographically dispersed computer systems and/or servers.

BACKGROUND

0002Many of today's commercial and industrial work environments involve machines or other equipment systems that operate in geographical areas that are located remotely from one another and from a job-site command center. In order to monitor the health, productivity, and status of these machines, each machine may be equipped with on-board data collection devices for monitoring various aspects associated with operations of the machine. The machines may also include communication equipment for facilitating data communication between the on-board data collection devices and an off-board system, such as a computer system associated with the job-site command center. The collected data may be analyzed to diagnose health or productivity problems associated with one or more of the equipment systems.

0003In some work environments, particularly those that employ large numbers of machines, the volume of data received by the job-site may quickly become too cumbersome for the job-site computer system to handle. Many project managers and job-site personnel simply do not have the appropriate training to monitor and analyze the large volume of data received by the job-site computer system. To address these problems, some equipment manufacturers and dealers offer subscriber-based services that receive machine data from a plurality of job-sites in a centralized data monitoring server. The centralized data monitoring server may analyze the data received from computer systems associated with one or more job-sites. The data monitoring server may also provide diagnostic and prognostic reports summarizing the health, status, and productivity of the equipment systems to one or more project managers or business entities associated with the job-site.

0004Although subscriber-based diagnostic services may provide a cost-effective and reliable solution to job-site data management and reporting, the transfer of large amounts of machine data securely, reliably, and in a timely fashion can be problematic. For example, should one or more communication channels between the job-site computer system and the data monitoring server become interrupted or disabled, the data monitoring server may not receive machine data in time to diagnose and/or resolve problems associated with one or more machines. This may potentially lead to unnecessary equipment downtime and/or losses in job-site productivity. Thus, in order to enhance reliability of data transfer in machine work environments, an integrated machine data file transfer system that monitors file transfers between a sender and intended recipient, identifies potential data transfer problems, and promptly notifies the sender and recipient of any communication problems may be advantageous.

0005At least one data transfer system has been developed that notifies the sender and recipient of a successful data transfer procedure. For example, U.S. Patent Publication No. 2003/0177422 (“the '422 publication”) to Tararoukhine et al. describes a file transfer and data management system that tracks the status of a document or file to be uploaded to a file transfer server. The system of the '422 publication may detect when the file has been uploaded to the file server and automatically provide an email notification of the uploaded file to the intended recipient and the sender of the file. Additionally, the system may provide an e-mail notification to the sender of the file when the intended recipient has downloaded the file from the file server.

0006Although conventional systems exist that provide e-mail notifications when files have been successfully transferred, they may still be insufficient. For example, conventional systems may not be equipped to monitor data transfer based on user-defined file transfer specifications, detect exceptions to data transfer specifications, and provide exception notifications if the file transfer session was not in conformance with the specifications. Thus, in order to ensure the reliable, efficient, and timely transfer of machine data between a remote job-site and a data monitoring server, an integrated, “real-time” file transfer protocol that provides an exception-based notification system may be required.

0007The presently disclosed system and method for remote machine data transfer is directed toward overcoming one or more of the problems set forth above.

SUMMARY OF THE INVENTION

0008In accordance with one aspect, the present disclosure is directed toward a method for data transfer between a client system and a server. The method may include receiving one or more user-defined file transfer specifications and establishing a communication channel between a client system and a server system based on the file transfer specifications. The method may also include initializing transfer of operation data between the client system and the server system via the communication channel. The method may also include providing an exception notification to one or more user-designated recipients if the transfer of the operation data between the client system and the server system is inconsistent with the file transfer specifications.

0009According to another aspect, the present disclosure is directed toward a system for remote machine data transfer. The system may include a client system associated with one or more machines operating in a work environment, a server system communicatively coupled to the client system and configured to receive operation data associated with the one or more machines from the client system, and a data transfer application for facilitating communication between the client system and the server system. The data transfer application may be configured to receive one or more user-defined file transfer specifications, establish a communication channel between the client system and the server system based on the file transfer specifications, and initialize transfer of operation data between the client system and the server system via the communication channel. The data transfer application may also be configured to provide a notification to one or more user-designated recipients if the transfer of machine data between the client system and the server system is unsuccessful.

0010In accordance with yet another aspect, the present disclosure is directed toward a work environment comprising a machine including at least one monitoring device communicatively coupled to at least one component of the machine, the monitoring device configured to monitor operation data associated with the machine. The work environment may also include a client system in data communication with the machine and configured to collect operation data from the at least one monitoring device, a server system communicatively coupled to the client system and configured to receive operation data associated with the one or more machines from the client system, and a data transfer application for facilitating communication between the client system and the server system. The data transfer application may be configured to receive one or more user-defined file transfer specifications, establish a communication channel between the client system and the server system based on the file transfer specifications, initialize transfer of operation data between the client system and the server system via the communication channel, and provide a notification to one or more user-designated recipients if the transfer of machine data between the client system and the server system is unsuccessful.

BRIEF DESCRIPTION OF THE DRAWINGS

0011<figref idref="DRAWINGS">FIG. 1A</figref> illustrates an exemplary work environment consistent with certain disclosed embodiments;

0012<figref idref="DRAWINGS">FIG. 1B</figref> provides a block diagram illustrating an exemplary network for facilitating remote machine data transfer in accordance with the disclosed embodiments;

0013<figref idref="DRAWINGS">FIG. 2</figref> provides a schematic illustrating an exemplary computer system, one which processes and methods consistent with the disclosed embodiments may be implemented;

0014<figref idref="DRAWINGS">FIG. 3</figref> provides a flowchart depicting an exemplary method for transferring data between a client system and a server; and

0015<figref idref="DRAWINGS">FIG. 4</figref> provides a flowchart depicting an exemplary data transfer process that includes data management and filtering features consistent with the disclosed embodiments.

DETAILED DESCRIPTION

0016<figref idref="DRAWINGS">FIG. 1A</figref> illustrates an exemplary work environment <b>100</b> in which processes and systems consistent with the disclosed embodiments may be implemented. Work environment <b>100</b> may include one or more components that that cooperate to perform a machine environment task associated with an industry such as mining, construction, transportation, agriculture, manufacturing, or any other type of industry. Work environment <b>100</b> may include one or more machines <b>120</b> coupled to a client system <b>140</b> and/or a data monitoring server <b>150</b> via one or more communication networks <b>130</b>. Work environment <b>100</b> may be configured to monitor, collect, control, filter, and/or manage information associated with an operation of one or more machines <b>120</b> and distribute the information to one or more back-end systems, such as data monitoring server <b>150</b>. It is contemplated that additional and/or different components than those listed above may be included in work environment <b>100</b>.

0017Machines <b>120</b> may each be a fixed or mobile machine configured to perform an operation associated with work environment <b>100</b>. Thus, machine, as the term is used herein, refers to a fixed or mobile machine that performs some type of operation associated with a particular industry, such as mining, construction, farming, etc. and operates between or within project environments (e.g., construction site, mine site, power plants, etc.) Furthermore, machine <b>120</b> may be used to refer to any remote asset operating within or associated with work environment <b>100</b>. A non-limiting example of a fixed machine includes an engine system operating in a plant, a material conveyer, or off-shore environment (e.g., off-shore drilling platform). Non-limiting examples of mobile machines include commercial machines, such as trucks, cranes, earth moving vehicles, mining vehicles, backhoes, material handling equipment, farming equipment, marine vessels, aircraft, and any type of movable machine that operates in a work environment. A machine may be driven by a combustion engine or an electric motor. The types of machines listed above are exemplary and not intended to be limiting. It is contemplated that work environment <b>100</b> may implement any type of machine. Accordingly, although <figref idref="DRAWINGS">FIG. 1A</figref> illustrates machines <b>120</b> as mobile earth-moving machines, each machine <b>120</b> may be any type of machine operable to perform a particular function within work environment <b>100</b>. Furthermore, it is contemplated that machines <b>120</b> may include a first set of machines <b>110</b> and a second set of machines <b>112</b> for associating the operations of particular machines to groups of machines. Furthermore, it is also contemplated that first and second sets of machines may be located in separate work sites located remotely from each other, and with client system <b>140</b>.

0018According to one embodiment, first set of machines <b>110</b> and second set of machines <b>120</b> may operate in separate job-site environments within work environment <b>100</b>. In order to facilitate data communication between or among separate job-sites and a centralized back-end system, work environment <b>100</b> may employ a plurality of client systems <b>140</b>, each client system acting as a data collection hub for a respective job site. Each client system may collect operation data from one or more machines operating within the designated geographical confines of the corresponding job-site. The operation data may be transferred to data monitoring server <b>150</b> using software and/or hardware devices that establish a direct and secure communication link between client systems <b>140</b> and data monitoring server <b>150</b>.

0019Work environment <b>100</b> may embody a connected worksite that may integrate data collection capabilities of machines <b>120</b> with “real-time” or “near real-time” file transfer capabilities to distribute the collected data to one or more client systems <b>140</b> and/or data monitoring server <b>150</b>. Furthermore, work environment <b>100</b> may employ a customizable file transfer platform that facilitates secure and direct data communication between machine <b>120</b>, a client data collection system (e.g., client system <b>140</b>), and third-party data monitoring servers <b>150</b>. <figref idref="DRAWINGS">FIG. 1B</figref> illustrates a schematic diagram detailing certain component and features corresponding to work environment <b>100</b> of <figref idref="DRAWINGS">FIG. 1A</figref>. As illustrated in <figref idref="DRAWINGS">FIG. 1B</figref>, each machine <b>120</b> may include on-board data collection and communication equipment to monitor, collect, and/or transmit information associated with an operation of one or more components of machine <b>120</b>. For example, machine <b>120</b> may include, among other things, one or more monitoring devices <b>121</b> (e.g., sensors, electronic control modules, etc.) coupled to one or more data collection devices <b>125</b> via communication lines <b>122</b>. Each machine <b>120</b> may also be configured to receive information from off-board systems, such as a client system <b>140</b>. The components described above are exemplary and not intended to be limiting. Accordingly, the disclosed embodiments contemplate each machine <b>120</b> including additional and/or different components than those listed above.

0020Data collector <b>125</b> may be operable to receive, collect, and/or package operation data associated with machine <b>120</b>. Operation data, as the term is used herein, refers to any type of data indicative of at least one operational aspect associated with one or more machines <b>120</b> or any of its constituent components or subsystems. Non-limiting examples of operation data may include, for example, health information such as fuel level, oil pressure, engine temperate, coolant flow rate, coolant temperature, tire pressure, or any other data indicative of the health of one or more components or subsystems of machine <b>120</b>. Alternatively and/or additionally, operation data may include status information such as engine power status (e.g., engine running, idle, off), engine hours, engine speed, machine speed, location, or any other data indicative of a status of machine <b>120</b>. Optionally, operation data may also include certain productivity information such as, task progress information, load vs. capacity ratio, shift duration, haul statistics (weight, payload, etc.), fuel efficiency, or any other data indicative of a productivity of machine <b>120</b>. Alternatively and/or additionally, operation data may include control signals for controlling one or more aspects or components of machine <b>120</b>. Data collector <b>125</b> may receive/collect operational information associated with an operation of machine <b>120</b> from one or more monitoring devices <b>121</b> during the execution of an assigned task.

0021Data collector <b>125</b> may be configured to coordinate the transmission of operation data from the machine to one or more off-board systems, such as client system <b>140</b> or data monitoring server <b>150</b>. To facilitate data communication, data collector <b>125</b> may include one or more communication modules. For example, data collector <b>125</b> may include a satellite communication module that may be adapted to facilitate communication between machine <b>120</b> and an off-board system (such as a client system <b>140</b> and/or data monitoring server <b>150</b>) via a satellite communication network. The satellite communication module may be configured to operate using one or more satellite subscriber networks such as LEO or GeoSat services. Alternatively, the satellite communication module(s) may be configured to communicate with one or more public or governmental satellite services, such as GPS or Glonass. Alternatively and/or additionally, data collector <b>125</b> may include cellular communication modules that may be configured to facilitate wireless communication between machine <b>120</b> and an off-board system via one or more available cellular subscriber network(s). Data collector <b>125</b> may include a WiFi or WiMax communication module(s) that communicates data via a wireless local area network device. Alternately and/or additionally, data collector <b>125</b> may also include a point-to-point wireless communication module that communicates with other point-to-point equipped systems. Furthermore, satellite, cellular, WiFi, point-to-point, and/or other communication methods may all be supported by a single communication module, thereby limiting the amount of equipment required to support multiple communication methods. Data collector <b>125</b> may be adapted to support multiple communication methods or services such as satellite, cellular, short message service (SMS), text messaging, paging, or any other type of communication services suitable for remote communication of data in asset management environments.

0022Communication link <b>130</b> may include any network that provides two-way communication between machines <b>120</b> and an off-board system (e.g., client system <b>140</b>, data monitoring server <b>150</b>, etc.) For example, communication link <b>130</b> may communicatively couple machines <b>120</b> to client system <b>140</b> across a wireless networking platform such as, for example, a satellite communication system, a cellular communication system, or any other platform for communicating data with one or more geographically dispersed assets (e.g., Bluetooth, microwave, point-to-point wireless, point-to-multipoint wireless, multipoint-to-multipoint wireless.) Although communication link <b>130</b> is illustrated as satellite- and/or cellular-based wireless communication networks it is contemplated that communication link <b>130</b> may also include or embody wireline networks such as, for example, Ethernet, fiber optic, waveguide, or any other type of wired communication network. It is also contemplated that communication network may support additional communication media or communication methods such as smartcard technology, manual data transport methods, or any suitable means for transporting data between machine <b>120</b> and off-board systems.

0023Communication link <b>130</b> may also include any necessary infrastructure to support message routing and network operations. For example, communication link <b>130</b> may include various hardware and software support systems and equipment that facilitate operations of one or more communication services, such as subscriber-based satellite and cellular services.

0024Client system <b>140</b> may be configured to receive operation data associated with one or more machines <b>120</b>. According to one embodiment, client system <b>140</b> may be a centralized computer system associated with a job-site of work environment <b>100</b> that may communicatively coupled to one or more data collectors <b>125</b> associated with one or more machines <b>120</b> operating within the job-site. Client system <b>140</b> may be adapted to detect one or more machines <b>120</b> operating within a particular job-site, establish a communication channel with machines <b>120</b>, and offload operation data from one or more machines <b>120</b>. Client system <b>140</b> may be configured to maintain a continuous communication channel with one or more machines <b>120</b>. Alternatively, client system <b>140</b> may be adapted to periodically connect and download the operation data from one or more machines <b>120</b>.

0025Client system <b>140</b> may be configured to distribute the operation data to data monitoring server <b>150</b>, for further analysis. As illustrated in <figref idref="DRAWINGS">FIG. 1B</figref>, client system <b>140</b> may be communicatively coupled to data monitoring server <b>150</b> via communication network <b>145</b>. Communication network <b>145</b> may include any type of network over which data may be communicated between client system <b>140</b> and data monitoring server <b>150</b>. For example, communication network <b>145</b> may communicatively couple client system <b>140</b> to data monitoring server <b>150</b> across a wireless networking platform such as, for example, a satellite communication system. Alternatively and/or additionally, communication network <b>145</b> may include one or more other broadband communication platforms appropriate for communicatively coupling one or more client system <b>140</b> to data monitoring server <b>150</b> such as, for example, cellular, Bluetooth, microwave, point-to-point wireless, point-to-multipoint wireless, multipoint-to-multipoint wireless, or any other appropriate communication platform for networking a number of components. It is also contemplated that communication network <b>145</b> may include wireline networks such as, for example, Ethernet, fiber optic, waveguide, or any other type of wired communication network. According to one embodiment, communication network <b>145</b> may include any type of communication medium that allows client system <b>140</b> to communicate with data monitoring server <b>150</b> via a communication network, such as the Internet.

0026Data monitoring server <b>150</b> may embody a computer server adapted to receive, collect, filter, route, and/or manage data collected by one or more client systems <b>140</b>. According to one embodiment, data monitoring server <b>150</b> may establish a secure, direct communication channel with one or more client systems <b>140</b> via the Internet of other available communication platform. As such, data monitoring server <b>150</b> may receive machine operation data files directly from client systems <b>140</b>, without requiring the use of an intermediate file depository.

0027Condition monitoring system <b>160</b> may include any device or system configured to analyze operation data associated with machines <b>120</b> and/or one or more groups of machines <b>110</b>, <b>112</b>. For example, condition monitoring system <b>160</b> may embody a computer system including diagnostic software for analyzing the operation data associated with one or more machines <b>120</b> based on threshold levels (that may be factory set, manufacturer recommended, and/or user configured) associated with a respective machine.

0028Condition monitoring system <b>160</b> may generate customized data analysis reports <b>162</b> summarizing results of analysis performed on operation data. These reports may be provided to a client via a web interface <b>165</b> that allows a client to view current and past analysis reports associated with machines <b>120</b>, set of machines <b>120</b>, one or more job-sites, and/or work environment <b>100</b>. These reports may embody interactive web pages that allow users to select, view, and customize the format of the reported data. For example, a repair technician assigned to maintain a particular type of machine may modify the report display format to include only those types of machines to which he is assigned.

0029Client system <b>140</b>, data monitoring server <b>150</b>, and condition monitoring system <b>160</b> may each embody processor-based computer systems, such as system <b>200</b> illustrated in <figref idref="DRAWINGS">FIG. 2</figref>. System <b>200</b> may include any type of processor-based system on which processes and methods consistent with the disclosed embodiments may be implemented. As illustrated in <figref idref="DRAWINGS">FIG. 2</figref>, system <b>200</b> may include one or more hardware and/or software components configured to execute software programs, such as software for collecting, distributing, and analyzing data collected from machines operating in work environment <b>100</b>. For example, system <b>200</b> may include one or more hardware components such as, for example, a central processing unit (CPU) <b>201</b>, a random access memory (RAM) module <b>202</b>, a read-only memory (ROM) module <b>203</b>, a storage <b>204</b>, a database <b>205</b>, an interface <b>206</b>, and one or more input/output (I/O) devices <b>207</b>. Alternatively and/or additionally, system <b>200</b> may include one or more software components such as, for example, a computer-readable medium including computer-executable instructions for performing methods consistent with certain disclosed embodiments. It is contemplated that one or more of the hardware components listed above may be implemented using software. For example, storage <b>204</b> may include a software partition associated with one or more other hardware components of system <b>200</b>. System <b>200</b> may include additional, fewer, and/or different components than those listed above. It is understood that the components listed above are exemplary only and not intended to be limiting.

0030CPU <b>201</b> may include one or more processors, each configured to execute instructions and process data to perform one or more functions associated with system <b>200</b>. As illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, CPU <b>201</b> may be communicatively coupled to RAM <b>202</b>, ROM <b>203</b>, storage <b>204</b>, database <b>205</b>, interface <b>206</b>, and I/O devices <b>207</b>. CPU <b>201</b> may be configured to execute sequences of computer program instructions to perform various processes, which will be described in detail below. The computer program instructions may be loaded into RAM for execution by CPU <b>201</b>.

0031RAM <b>202</b> and ROM <b>203</b> may each include one or more devices for storing information associated with an operation of system <b>200</b> and/or CPU <b>201</b>. For example, ROM <b>203</b> may include a memory device configured to access and store information associated with system <b>200</b>, including information for identifying, initializing, and monitoring the operation of one or more components and subsystems of system <b>200</b>. RAM <b>202</b> may include a memory device for storing data associated with one or more operations of CPU <b>201</b>. For example, ROM <b>203</b> may load instructions into RAM <b>202</b> for execution by CPU <b>201</b>.

0032Storage <b>204</b> may include any type of mass storage device configured to store information that CPU <b>201</b> may need to perform processes consistent with the disclosed embodiments. For example, storage <b>204</b> may include one or more magnetic and/or optical disk devices, such as hard drives, CD-ROMs, DVD-ROMs, or any other type of mass media device.

0033Database <b>205</b> may include one or more software and/or hardware components that cooperate to store, organize, sort, filter, and/or arrange data used by system <b>200</b> and/or CPU <b>201</b>. For example, database <b>205</b> associated with client system <b>140</b> and/or data monitoring server <b>150</b> may store historical operation data associated with a machine <b>120</b>. This data may be accessible by CPU <b>201</b> associated with the condition monitoring system should, for example, a user request a historical report associated with operation data for a particular aspect of one or more machines. It is contemplated that database <b>205</b> may store additional and/or different information than that listed above.

0034Interface <b>206</b> may include one or more components configured to transmit and receive data via a communication network, such as the Internet, a local area network, a workstation peer-to-peer network, a direct link network, a wireless network, or any other suitable communication platform. For example, interface <b>206</b> may include one or more modulators, demodulators, multiplexers, demultiplexers, network communication devices, wireless devices, antennas, modems, and any other type of device configured to enable data communication via a communication network.

0035I/O devices <b>207</b> may include one or more components configured to communicate information with users associated with system <b>200</b>. For example, I/O devices <b>207</b> may include a console with an integrated keyboard and mouse to allow users to input parameters associated with system <b>200</b>. I/O devices <b>207</b> may also include a display including a graphical user interface (GUI) for outputting information on a monitor. I/O devices <b>207</b> may also include peripheral devices such as, for example, a printer for printing information associated with system <b>200</b>, a user-accessible disk drive (e.g., a USB port, a floppy, CD-ROM, or DVD-ROM drive, etc.) that allows users to input data stored on a portable media device, a microphone, a speaker system, or any other suitable type of interface device.

0036File transfer application <b>208</b> may include software instructions for facilitating the transfer of data files between a remote system, such as client system <b>140</b>, and a centralized back end-system, such as data monitoring server <b>150</b> and/or condition monitoring system <b>160</b>. File transfer application <b>208</b> may include a client application (not shown). The client application may be loaded onto one or more client systems <b>140</b>. The client application provides users with an interactive interface for defining file transfer specifications and data management settings of data monitoring server <b>150</b> associated with the respective client system <b>140</b>.

0037Similarly, file transfer application <b>208</b> may include a server application (not shown). The server application may be loaded onto data monitoring server <b>150</b> and may be configured to collect file transfer specifications and data management settings from one or more client systems <b>140</b> and establish individual file transfer and data management settings for each client system in accordance with the collected specifications and settings. Accordingly, operations of data monitoring server <b>150</b> may be individually defined by users of a plurality of client systems <b>140</b>. Operations of file transfer application <b>208</b>, client system <b>140</b>, and data monitoring server <b>150</b> will be described in detail below.

0038According to one embodiment, file transfer application <b>208</b> may be built upon a message oriented middleware communication protocol, such as IBM WebSphere® MQ software, that provides fast, efficient communication of messages from one message queue server to another (or between a message queue server and a message queue client). File transfer application <b>208</b> may provide a data communication system that capitalizes on the advantages of message oriented middleware (e.g., the “real-time” and “near real-time” data transfer capabilities associated with asynchronous systems) while neutralizing some of the deficiencies associated with message oriented middleware (e.g., incomplete or interrupted data transmissions).

0039Processes and methods consistent with the disclosed embodiments may facilitate secure and efficient transfer of data between remote systems and a back-end server by providing an automated method for monitoring and logging data transfer operations and notifying one or more designated recipients if the data transfer is inconsistent with user-defined file transfer specifications. Additionally, features and methods associated with the disclosed embodiments may be included as part of a condition monitoring system that monitors operation data associated with a plurality of remote assets operating in a work environment. As such, methods consistent with the disclosed embodiments may provide organizations that rely on “real-time” or “near real-time” data analysis and reporting with a system that monitors the transfer of data between remote data collection systems and back-end servers, detects exceptions to successful data transfer operations (i.e., data transfer failures, delays, etc.), and notifies designated personnel of the exceptions so that appropriate corrective measures can be taken. <figref idref="DRAWINGS">FIG. 3</figref> provides a flowchart <b>300</b> depicting an exemplary method for transferring data between a client system <b>140</b> and a server <b>150</b> consistent with the disclosed embodiments.

0040As illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, one or more file transfer specifications may be received from a user associated with one or more client systems <b>140</b> (Step <b>310</b>). According to one embodiment, file transfer specifications may be defined by a user using a graphical interface associated with file transfer application <b>208</b> associated with client system <b>140</b>. File transfer specifications may include customized instructions and/or definitions that, when uploaded into a data monitoring server <b>150</b>, defines the manner in which file transfer is to be carried out with respect to a particular client system <b>140</b>. File transfer specifications may include, for example, a file transfer source address, a network address of the server system, a file transfer destination server, a file transfer communication port, a file transfer destination folder address, a time limit that data can remain in a communication queue, a data storage time limit, one or more alert email recipient addresses, and/or a data communication schedule. The file transfer specifications noted above are exemplary only and not intended to be limiting. Accordingly, additional, fewer, and/or different file transfer specifications may be used to define file transfer capabilities between client system <b>140</b> and data monitoring server <b>150</b>.

0041Once file transfer specifications have been received, a communication channel may be established between client system <b>140</b> and data monitoring server <b>150</b> (Step <b>320</b>). According to one embodiment, file transfer application <b>208</b> may provide instructions for a client system <b>140</b> to establish a communication channel with data monitoring device <b>150</b> using a message queue service associated with the file transfer application <b>208</b>. As such, client system <b>140</b> may locate data monitoring server <b>150</b> using a network address of the server specified in the file transfer specifications provided by the user. Accordingly, a communication channel may be established between a message queue of client system <b>140</b> and, a message queue of the server system <b>150</b>, for transferring data between the client and server systems.

0042According to one embodiment, a data transfer schedule may be established that defines a data transfer schedule between client system <b>140</b> and data monitoring server <b>150</b>. Accordingly, client system <b>140</b> may establish a communication channel in accordance with the data transfer schedule. The data transfer schedule may be defined by a user as part of the file transfer specifications. By establishing a data transfer schedule, organization with limited access to bandwidth in remote areas may conserve network bandwidth by ensuring that client systems sharing the same network are not communicating data simultaneously.

0043Once the communication channel has been established between client system <b>140</b> and data monitoring server <b>150</b>, client system <b>140</b> may initialize data transfer with data monitoring system <b>150</b> (Step <b>330</b>). For example, client system <b>140</b> may identify operation data stored at a file transfer source address specified by the file transfer specifications. Client system <b>140</b> may load the data into the client message queue. The client message queue may begin transferring the data to the server message queue via the communication channel.

0044According to one embodiment, operation data may be received from one or more machines and stored in a file transfer source location by client system <b>140</b>. Subsequently, a client message queue may locate the operation data in a file source location associated with the file transfer specifications defined by the user. Alternatively and/or additionally, file transfer application <b>208</b> may search client system and identify any “new” operation data that has been received since the last data transfer session. The client message queue may schedule the operation data for communication to the server message queue via the communication channel.

0045File transfer application <b>208</b> may monitor data transfer between client system <b>140</b> and data monitoring server <b>150</b> (Step <b>340</b>) to determine whether each data file transfer is complete and in conformance with the file transfer specifications (Step <b>350</b>). If the data transfer is successful (Step <b>350</b>: Yes), file transfer application <b>208</b> may queue subsequent data files for transfer (Step <b>355</b>). If, however, the data transfer is unsuccessful (Step <b>350</b>: No), file transfer application may provide an exception notification to one or more designated recipients specified by the file transfer specifications.

0046According to one embodiment, file transfer application <b>208</b> may provide instructions that enable client system <b>140</b> to determine if the data file is successfully transmitted from the client system to the message queue of the server in conformance with the file transfer specifications. If the data is not transferred by client system <b>140</b>, file transfer application <b>208</b> may provide an exception notification message to one or more designated recipients indicating a problem with the client communication capabilities. Exception notification message may include any type of electronic message such as, for example, an electronic message to a cellular or wireless device, an electronic mail message, a prerecorded voicemail message, a pop-up window associated with a desktop portion of file transfer application <b>208</b>, or any other type of electronic message.

0047Similarly, file transfer application <b>208</b> may provide instructions that enable data monitoring server <b>150</b> to determine if the data file is successfully received from the client system. For example, data monitoring system <b>150</b> may analyze a received file, compare the received file to the file transmitted by client system <b>140</b>, and determine if the received data is consistent with the transmitted data. If, for example, the data includes missing or incomplete information, file transfer application <b>208</b> may generate an exception notification message to the designated recipients indicating a problem with the server communication capabilities.

0048The file transfer processes described herein may be implemented in virtually any environment where “real-time” or “near real-time” analysis of data may be advantageous. According to one exemplary embodiment, the file transfer processes described herein may be implemented as part of a connected worksite environment that collects operation data associated with one or more machines, groups of machines, or work environment in a remote client systems; queues the operation data for transfer to one or more back-end systems, such as data monitoring server <b>150</b>; monitors the transfer of data between the remote client system and the back-end system based on one or more file transfer specifications; and provides an exception notification to one or more designated users if the transfer of data is inconsistent with the file transfer specifications.

0049In addition to monitoring the transfer of data between one or more client systems <b>140</b> and data monitoring server <b>150</b>, processes and methods described herein may provide a solution that allows users to define data management and handling capabilities associated with the file transfer process. For instance, the file transfer process described herein may be enhanced by allowing users to designate a priority level associated with one or more operational aspects. As such, file transfer application <b>208</b> may queue operation data for data transfer and analysis according to the designated priority of the operation data. Accordingly, data identified as high-priority may be queued for data transmission and analysis before data that is not designated as high-priority. <figref idref="DRAWINGS">FIG. 4</figref> provides a flowchart <b>400</b> that illustrates an exemplary data transfer process that includes data management and filtering features consistent with the disclosed embodiments.

0050As illustrated in <figref idref="DRAWINGS">FIG. 4</figref>, the file transfer process may begin with the receipt/collection of operation data associated with one or more machines operating in a remote work environment (Step <b>410</b>). For example, file transfer application <b>208</b> may be configured to receive operation data from one or more machines and/or groups of machines. According to one embodiment, operation data may be collected by one or more data monitoring devices <b>122</b> associated with each machine and loaded into the machine's data collector <b>125</b>. Each data collector <b>125</b> may stream the operation data to a nearby client system <b>140</b>, which is adapted to collect operation data from one or more machines operating in an associated geographical area.

0051Alternatively and/or additionally, operation data collected by one or more monitoring devices <b>121</b> may be temporarily stored in data collector <b>125</b> associated with each machine. Periodically, client system <b>140</b> may transmit a data request signal to each of data collectors <b>125</b> and receive the operation data stored in data collector <b>125</b>, in response to the data request signal.

0052Once operation data has been received/collected by client system <b>140</b>, the operation data may be filtered in accordance with a predefined priority (Step <b>420</b>). According to one embodiment, the data management interface may allow users to establish a priority associated with one or more operational aspects. For instance, users may designate certain health information associated with machine (e.g., engine temperature, engine oil pressure, vital fluid levels, machine location, etc.) as high-priority data. Similarly, users may designate certain non-vital health data (e.g., productivity data such as machine load statistics, etc.) as low priority data.

0053Users may further specify certain data management and filtering actions to be taken by client system <b>140</b> and/or data monitoring server <b>150</b>. For example, file transfer application may include a data management interface, whereby users may designate the manner in which the operation data is handled by client system <b>140</b> and/or data monitoring server <b>150</b>. According to one embodiment, users may designate different file storage locations for high-priority data and low-priority data. Accordingly, users may define separate file transfer specifications for each file storage location such that the high-priority operation data is transferred prior to and/or with greater frequency than low-priority data. Similarly, data monitoring server <b>150</b> may identify and filter high-priority data from among other operation data and queue the high-priority data for condition monitoring analysis and reporting with greater urgency than low-priority data.

0054Once data management specifications have been established, operation data files may be transferred between client system <b>140</b> and data monitoring server <b>150</b> according to the user-defined priority (Step <b>430</b>), in accordance with the file transfer methods described herein. Data monitoring server <b>150</b> may manage the received operation data in accordance with the data management settings defined by the user. For instance, data monitoring system may immediately queue high-priority operation data for analysis by condition monitoring system <b>160</b> (Step <b>440</b>), while storing low-priority operation data in a destination file specified by the user for future analysis (e.g., after high-priority operation data has been analysis and/or according to a user-defined schedule.)

0055Condition monitoring system <b>160</b> may generate a report that summarizes the operation data analysis (Step <b>450</b>). For high-priority data, these reports may be automatically generated as soon as the analysis is complete. In contrast, low-priority data reporting may be performed at scheduled intervals according to the data management specifications provided by the user. Once complete, the analysis report may be posted and/or uploaded to a web-interface (Step <b>460</b>) that allows user to access, customize, download, and/or print the analysis reports.

0056By implementing the file transfer processes illustrated in <figref idref="DRAWINGS">FIG. 3</figref> in the connected work environment of <figref idref="DRAWINGS">FIG. 1A</figref>, organizations that rely on fast, efficient, and reliable transfer of large amounts of raw data may become more efficient. Specifically, the file transfer processes no longer require sender and recipients to continuously monitor file transfers to confirm that data has been sent and received successfully. Furthermore, by implementing the file transfer method of <figref idref="DRAWINGS">FIG. 4</figref>, which allows users to customize the data management and data handling features of a condition monitoring system, organizations may further customize file transfer and condition monitoring processes to optimize the use of communication resources available to one or more client systems <b>140</b>. Accordingly, should one client system be located in an area where communication service is significantly limited, the file transfer process may be adapted to dedicate file transfer resources to communicating only operation data designated as high-priority.

INDUSTRIAL APPLICABILITY

0057Methods and systems consistent with the disclosed embodiments may provide a file transfer process that facilitates the direct transfer of data between a remote client system and a back-end server, while identifying any exceptions to the successful transfer of machine data in accordance with user-defined file transfer specifications. Work environments that employ processes and features consistent with the disclosed embodiments provide an automated system for monitoring file transfer sessions and automatically notifying user-designated personnel of problems with the file transfer, thereby limiting the amount of oversight required to ensure that data files are sent successfully and in a timely manner.

0058Although the disclosed embodiments are described in connection with a file transfer process associated with machine work environments, they may be applicable to any environment where it may be advantageous to monitor file transfer processes and notify support personnel of potential problems with file transfer capabilities. According to one embodiment, the presently disclosed file transfer process may be included as part of a remote asset monitoring system to ensure the timely transfer of data from a remote work-site to a condition monitoring system that analyzes the health, status, and/or productivity of the remote assets.

0059The presently disclosed file transfer process may have several advantages. For example, because the file transfer process described herein provides a solution that automatically notifies designated personnel upon detection of a problem with a data transfer session, support personnel may be able to identify and resolve data transfer problems soon after detection. Furthermore, these automated processes may limit the need for senders and intended recipients to manually monitor whether a file transfer was successful. As a result, organizations that rely on “real-time” or “near real-time” collection and analysis or work environment data may become more efficient.

0060In addition, the presently disclosed file transfer process may have certain cost advantages, when employed in conjunction with a machine condition monitoring systems. For instance, by providing a file transfer process that facilitates and maintains “real-time” and “near real-time” data acquisition, potential health problems associated with one or more machines may be identified, analyzed, and resolved soon after detection, thereby preventing more costly and serious damage if the problem were allowed to persist.

0061It will be apparent to those skilled in the art that various modifications and variations can be made to the disclosed system and method for remote machine data transfer without departing from the scope of the invention. Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the present disclosure. It is intended that the specification and examples be considered as exemplary only, with a true scope of the present disclosure being indicated by the following claims and their equivalents.