Systems and methods for equipment services

A piece of equipment that needs services may not have connectivity to a network. In an example method, an event triggers the piece of equipment to generate a barcode or QR code. The event may be installation of equipment, preventive maintenance, update of software, periodic calibration, abnormal operation, change of location, etc. The barcode or QR code contains information of the piece of equipment and the triggering event. The piece of equipment halts upon display of the barcode or QR code. An application installed in a user device scans the barcode or QR code and sends a message to a remote service center. The service center analyzes the message and updates a service database. The service center returns a key in a message back to the user device. When the key is input into the piece of equipment, the operation of the piece of equipment is resumed.

FIELD

This disclosure relates to systems and methods for equipment services.

BACKGROUND

Various types of equipment require services to ensure proper operation. For example, medical systems (e.g., x-ray, CT, MR) used in hospitals or clinics are serviced regularly by personnel who address operating problems, configure and calibrate the systems, and perform periodic checks and software updates. In recent years, computerized service centers have been used to remotely manage equipment services. For example, pieces of equipment are connected to the service center via the network (e.g., intranet, Internet). A variety of data, such as log information, configuration information, location information, operational information, etc., is collected from the pieces of equipment, transmitted to the service center via the network, and stored in a database of the service center. The service center can further analyze the data, evaluate system performance, propose or schedule visits by service personnel, and so on. In addition, the service center can facilitate enforcement of service activities on the pieces of equipment, such as activities prescribed by the facility maintenance institutes, scheduled maintenance, security updates, modifications such as Field Modification Instructions (FMIs) or upgrades, etc.

However, not every piece of equipment has connectivity to the service center—some may not have network interface for connecting to the Internet or other networks. Collecting data from those systems that do not have connectivity and enforcing activities (e.g., cyber security compliance) on the systems may be problematic. Thus, a method of collecting data from and enforcing activities on the systems that do not have connectivity to the network is generally desired.

BRIEF SUMMARY

In one embodiment, the present disclosure provides a piece of equipment comprising a code generator, a display, and an input device. The code generator is configured to generate a barcode or QR code in response to a triggering event. The barcode or QR code contains information of the piece of equipment and the triggering event. The display is configured to display the barcode or QR code. Operation of the piece of equipment halts upon display of the barcode or QR code. The input device is configured to receive an input of a key. Operation of the piece of equipment resumes upon input of the key.

In another embodiment, the present disclosure provides service center comprising a database and a server. The database stores information related to equipment services. The server is communicably connected to the database and configured to receive a message from a user device. The message contains information of a piece of equipment and a triggering event which happened to the piece of equipment. The server is further configured to analyze the message and update the database with the received message, generate a return message, and transmit the return message to the user device. The return message includes a key for putting the piece of equipment back to operation.

In still another embodiment, the present disclosure provides a method for equipment service. The method comprises generating a barcode or QR code in response to a triggering event. The barcode or QR code contains information of a piece of equipment and the triggering event which happened to the piece of equipment. The method further comprises displaying the barcode or QR code and halting operation of the piece of equipment upon display of the barcode or QR code, and receiving an input of a key and resuming operation of the piece of equipment resumes upon input of the key.

In yet another embodiment, the present disclosure provides a method for equipment service. The method comprises receiving a message from a user device. The message contains information of a piece of equipment and a triggering event which happened to the piece of equipment. The method further comprises analyzing the message and updating a database with the received message, generating a return message, and transmitting the return message to the user device. The return message includes a key for putting the piece of equipment back to operation.

The drawings illustrate specific aspects of the described components, systems and methods for equipment services. Together with the following description, the drawings demonstrate and explain the principles of the structures, methods, and principles described herein. In the drawings, the size of components may be exaggerated or otherwise modified for clarity. Well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the described components, systems and methods.

DETAILED DESCRIPTION

One or more specific embodiments of the present disclosure are described below in order to provide a thorough understanding. These described embodiments are only examples of the systems and methods for equipment services. The skilled artisan will understand that specific details described in the embodiments can be modified when being placed into practice without deviating the spirit of the present disclosure.

When introducing elements of various embodiments of the present disclosure, the articles “a,” “an,” and “the” are intended to mean that there are one or more of the elements. The terms “first,” “second,” and the like, do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements. As the terms “connected to,” “coupled to,” etc. are used herein, one object (e.g., a material, element, structure, member, etc.) can be connected to or coupled to another object regardless of whether the one object is directly connected or coupled to the other object or whether there are one or more intervening objects between the one object and the other object.

As used herein, the terms “system,” “device,” “module,” etc., may include a hardware and/or software system that operates to perform one or more functions. For example, a module, device, or system may include a computer processor, controller, and/or other logic-based device that performs operations based on instructions stored on a tangible and non-transitory computer readable storage medium, such as a computer memory. Alternatively, a module, device, or system may include a hard-wired device that performs operations based on hard-wired logic of the device. Various modules, devices, and/or systems shown in the attached figures may represent the hardware that operates based on software or hardwired instructions, the software that directs hardware to perform the operations, or a combination thereof.

In addition, it should be understood that references to “one embodiment” or “an embodiment” of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features.

Referring to the figures generally, the present disclosure is to provide systems and methods for equipment services, such as collecting data from and enforcing activities on pieces of equipment. In some embodiments, the piece of equipment that needs services is not connected to the Internet or a proprietary network of an equipment manufacturer, an equipment seller, or a maintenance service provider. In an example method, an event triggers the piece of equipment to generate a barcode or QR code. The triggering event may include but is not limited to, for example, completion of installation of equipment, performance of preventive maintenance, update of software, periodic calibration and/or configuration of system, abnormal operation, change of location, etc. The barcode or QR code may contain information of the piece of equipment, such as the type and identification (e.g., serial number), location, status of operation (e.g., OK, error, etc.), as well as information of the triggering event, modification and/or updates, log history, etc. The barcode or QR code is presented on, for example, a display of the piece of equipment. The display may also prompt a message asking an operator to enter a key. In some embodiments, the piece of equipment halts before the key is entered.

The operator, upon seeing the barcode or QR code and the prompt message, activates an application installed in a user device (e.g., smart phone, laptop, tablet, etc.) to scan the barcode or QR code on the display. The application then generates a message which contains information derived from the barcode or QR code and sends the message to a server, e.g., a remote server of a service center. The server receives the message and analyzes the information carried by the message. The server may update the database of the service center with the information received. In some embodiments, if the message indicates that services have been properly performed on the piece of equipment, the server may send a key in a return message back to the user device. The operator can input the key to the piece of equipment to resume its operation. In some embodiments, if the message indicates that services have not been properly performed, or further intervention is needed, or the operation status was erroneous, the server may send instructions and/or warnings along with the key in the return message back to the user device. The operator can input the key to resume the operation and perform actions per the instructions/warnings received from the server.

Referring toFIG. 1A, a schematic diagram of an environment100for equipment services is shown, in accordance with an exemplary embodiment. As illustrated inFIG. 1A, various pieces of equipment110require services. In the context of, for example, medical equipment, the pieces of equipment110may include but are not limited to, for example, PET, SPECT nuclear camera, CT, MR, X-ray, etc. The pieces of equipment110may be made by the same or different manufacturers. It should be understood that although medical equipment is used as an example in this disclosure, the methods and systems disclosed herein may apply in any appropriate industries.

An operator team102performs services for the equipment110, such as fixing operating problems, configuring and calibrating the systems, performing periodic checks and software updates, and so on. A service center130includes a database139for storing information of equipment services and a server131for analyzing the information and performing operations (e.g., providing instructions, scheduling service events, etc.) based on the information. In some embodiments, the service center130is located in the cloud, leveraging computing and storing capacities of the cloud. In some embodiments, at least some pieces of equipment110do not have connectivity to the Internet, or a proprietary network of an equipment manufacturer, an equipment seller, or a maintenance service provider. Therefore, these pieces of equipment110are not directly connected to the service center130. A user device120is capable of communicating with the service center130via a network connection104. The user device120may be, for example, a smartphone, a tablet, a laptop, or any other appropriate device used by the operator team102. A same operator may use the same user device120at different pieces of equipment110. The communication capability of the user device120is leveraged to collect data from the unconnected pieces of equipment110to the service center130and to enforce activities on the unconnected pieces of equipment110.

FIG. 1Bshows more details of each component ofFIG. 1Ain a block diagram, in accordance with an exemplary embodiment. As shown inFIG. 1B, in some embodiments, an example piece of equipment110comprises a code generator112, a display114, and an input device116. The code generator112is configured to generate a barcode or QR code in response to an event. The triggering event may include performance of a service event, such as, completion of installation of equipment, performance of preventive maintenance, update of software, periodic calibration and/or configuration of system, change of location, etc. The triggering event may also include an upcoming service event. For example, the code generator112may be configured to generate a barcode or QR code when a periodic calibration is due in a week, three days, or one day. The triggering event may further include abnormal operation of the piece of equipment110, for example, when an error occurs. The triggering events may be predefined and stored in the piece of equipment110.

The generated barcode or QR code may contain information of the piece of equipment110, such as the type and identification (e.g., serial number), location, status of operation (e.g., OK, error, etc.), as well as information of the operator (e.g., identification). The barcode or QR code may further contain information of the triggering event, such as the type of the triggering event (e.g., periodic calibration, updates of software, etc.), details of the triggering event (failure, success, partial failure), timestamp of when the triggering event occurred, etc. The barcode or QR code can be generated by any appropriate method known in the art. In some embodiments, the barcode or QR code includes authentication data for authenticating the piece of equipment110, for example, credentials of the piece of equipment110. In some embodiments, information contained in the barcode or QR code is encrypted. In some embodiments, no privacy related information is included to generate the barcode or QR code, such as patient information, images, clinical information, hospital personnel information and so on.

The display114may be a monitor or screen, which can display the barcode or QR code generated by the code generator112, as well as information/instructions to the operator102. For example, the display114may display the barcode or QR code along with a prompt message, instructing the operator102to input a key which is returned from the service center130. The input device116may be a keyboard, touchpad, mouse, or any other appropriate device that the operator102can use to input data to the device110. In some embodiments, the operator102inputs user name, password, or the like through the input device116for the piece of equipment110to authenticate the operator. In some embodiments, the display114and the input device116are integrated into one component, e.g., a touch screen.

Still referring toFIG. 1B, in some embodiments, the user device120comprises a mobile application122, a user interface124, a camera126, and a communication interface128. The mobile application122, when activated by the operator102, runs on the user device120and facilitates the operations disclosed herein. In some embodiments, the mobile application122is a web-based portal/application. In some embodiments, the mobile application122is downloaded by the operator102onto the user device120from a website such as Google Play, Apple Store, or a website of an equipment manufacturer, an equipment seller, or a maintenance service provider. In some embodiments, the operator102needs to register before activating the mobile application122for the first time, by providing, for example, a user name, password, phone number, email, and so on.

The user interface124may be a hardware device (e.g., touch screen) or a software program (e.g., graphical user interface) or a combination thereof. The user interface124for the mobile application122may be configured to help or guide the operator102in performing the operations described herein. In some embodiments, the user interface124may be configured according to certain rules, preferences, and/or functions. Furthermore, the operator102can customize the user interface124according to his/her desires, preferences, and/or requirements.

The camera126may be any appropriate image capturing device capable of scanning the barcode or QR code displayed on the device110. The communication interface128may be a hardware device, a software program, or a combination thereof to connect the user device120to a wired network and/or a wireless network, such as, Ethernet interface, cellular interface, Wi-Fi interface, Bluetooth interface, or the like.

Still referring toFIG. 1B, in some embodiments, the service center130comprises the server131and the database139. The service center130may be managed by, for example, a medical equipment manufacturer, a medical equipment sales company, or a maintenance service provider. In some embodiments, the service center130is cloud-based, leveraging computing and storing capacities in the cloud. The database139stores equipment service information associated with each piece of equipment110, for example, an identification (e.g., serial number) and type of the piece of equipment110, location, software version, services performed on the piece of equipment110and date/time of performance, services scheduled for the piece of equipment110and date/time, operators who performed and/or will perform the services, and so on.

The server131comprises a registry132, a mobile application host134, a message analyzer136, and a message generator138. The registry132registers various pieces of equipment110and the operator team102with the service center130. Thus, the equipment110and operator team102are added to the service center130and stored, alone and/or as part of a hierarchy or organization structure of organization/sites/devices in the database139. Each piece of equipment110can be associated with a device identifier in the registry132, which can be used with information such as device name, model, type (e.g., MR, CT, X-ray), location, operational status (e.g., OK, error), etc. to create a device profile managed by the service center130. Each operator102can be associated with an operator identifier in the registry132, which can be used with information such as user name, phone number, email address, calendar, etc. to create an operator profile managed by the service center130. In some examples, the registry132includes an authentication module for authenticating equipment110and operator102. The database139may store device/operator credentials to facilitate the authentication.

The mobile application host134supports the mobile application122on the user device120to access the service center130. The service center130can receive messages from and send messages to the user device120through the mobile application host134. In some embodiments, the mobile application host134may authenticate the data from the user device120. For example, the mobile application host134may check the credentials of the equipment110and operator102contained in the message and compare with the corresponding credentials stored in the database139.

The message analyzer136analyzes the message received from the mobile application122. In some embodiments in which the mobile application122does not have the function of extracting information from the barcode or QR code, the message analyzer136extracts information from the barcode or QR code. In some embodiments in which the mobile application122has extracted information from the barcode or QR code, the message analyzer136analyzes the extracted information. The message analyzer122determines what to do based on the information contained in the message. For example, if the received message indicates that the operator102has successfully performed a service event on the piece of equipment110, the message analyzer136updates the database139with the type of service performed, status of performance (e.g., success), date/time of performance, etc. If the received message indicates that the piece of equipment110has been moved to another location, the message analyzer136updates the location in the database139. If the message indicates that a regular service (e.g., calibration) is due, the message analyzer136schedules a service and appoints an operator for the upcoming service. If the message indicates that a service has not been successfully performed (e.g., failed), the message analyzer136may identify the cause of the failure. If the message indicates that the operation of the piece of equipment110is abnormal, the message analyzer136analyzes the error code to identify the cause. It should be noted that the types of messages described herein are for illustration not for limitation, the message can contain any appropriate information.

The message generator138generate a return message to the user device120based on the analysis by the message analyzer136. For example, if the service has been successfully performed and no further action is needed, the message generator138may generate a key for resuming the device110. The key can be, for example, numbers, letters, characters, or any combination thereof. If a service is not successfully completed and/or error code indicates abnormal operational status, the message generator138may generate a return message that contains warnings of the problem, or instructions regarding further personal intervention, etc., along with the key.

FIG. 2illustrates a flow diagram of an equipment service process200performed at the service center130, according to an exemplary embodiment. At operation202, equipment110and operator team102are registered with the registry132of the service center130. For example, various pieces of equipment110and operators102are added to the service center130and stored, alone and/or as part of a hierarchy or organization structure of organization/sites/devices in the database139. Each piece of equipment110can be associated with device identifiers, which can be used with information such as device name, type, model, location, status (e.g., OK, error), and the like to create a device profile. Each operator102can be associated with an operator identifier, which can be used with information such as user name, phone number, email address, calendar, etc. to create an operator profile.

At operation204, the mobile application host204receives a message from the user device120. In some embodiments, the message includes the barcode or QR code generated by the device110in response to a triggering event. In some embodiments, the message includes information extracted from the barcode or QR code. Besides, the message may further contain the type and identification (e.g., serial number) of the piece of equipment110, its location, identification of the operator102, the type of the triggering event, etc. In further embodiments, the mobile application host134may authenticate the message received from the user device120. For example, the mobile application host134may check the credentials of the piece of equipment110and operator102contained in the message and compare with the corresponding credentials stored in the database139.

At operation206, the message analyzer136analyzes the message received from the user device110. If the received message contains the barcode or QR code, the message analyzer136extracts information from the barcode or QR code. If the received message contains the extracted information, the message analyzer136analyzes the extracted information. The message analyzer136determines what to do based on the information contained in the message. For example, if the received message indicates that the operator102has successfully performed a service event on the piece of equipment110, the message analyzer136updates the database139with the performed service. If the received message indicates that the piece of equipment110has been moved to another location, the message analyzer136updates the location in the database139. If the message indicates that a regular service (e.g., calibration) is due, the message analyzer136schedules an upcoming service. If the message indicates that a service has not been successfully performed and/or the operational status is abnormal, the message analyzer136may identify the cause of the failure and/or analyze the error code.

At operation208, the message generator138generates a return message based on the analysis by the message analyzer136. For example, if the service has been successfully performed and no further action is needed, the message generator138may generate a key for resuming the piece of equipment110. If a service is not successfully completed and/or the operation is abnormal, the message generator138may generate a return message that contains warnings of the problem, or instructions regarding further personal intervention, etc., along with the key.

At operation210, the mobile application host134sends the return message generated by the message generator138to the user device110.

It should be understood that the process described with reference toFIG. 2is for purposes of illustration only and not for limitation. Any suitable equipment service process with more, fewer, and/or different operations can be implemented.

FIG. 3illustrates a work flow300of an equipment service process involving the piece of equipment110, the user device120, and the service center130, in accordance with an exemplary embodiment.

At operation302, the code generator112of the piece of equipment110generates a barcode or QR code in response to a triggering event. The triggering event may include performance of a service event, such as, installation of equipment, performance of preventive maintenance, update of software, periodic calibration and/or configuration of system, change of location, etc. The triggering event may also include an upcoming service event, for example, a periodic calibration due in a week, three days, or one day. The triggering event may further include abnormal operation of the piece of equipment110, for example, when an error occurs. The triggering events may be predefined and stored in the piece of equipment110.

The generated barcode or QR code may contain information of the piece of equipment110, such as the type and identification (e.g., serial number), location, status of operation (e.g., OK, error, etc.), as well as information of the operator (e.g., identification). The barcode or QR code may further contain information of the triggering event, such as the type of the triggering event (e.g., periodic calibration, updates of software, etc.), details of the triggering event (failure, success, partial failure), timestamp of when the triggering event occurred, etc. In some embodiments, the barcode or QR code includes authentication data for authenticating the piece of equipment110, for example, credentials of the piece of equipment110. In some embodiments, information contained in the barcode or QR code is encrypted. In some embodiments, the piece of equipment110halts when the barcode or QR code and the prompt message are displayed.

When the operator102sees the displayed barcode or QR code and the prompt message, the operator102activates the mobile application122in the user device120. Once activated, the user interface124prompts the operator102to scan the barcode or QR code. The camera126scans the barcode or QR code displayed on the device110at operation304.

At operation306, the mobile application122of the user device120then generates a message based on the barcode or QR code and sends the message to the service center130via the communication interface128. In some embodiments, the mobile application122includes the function of extracting information from the barcode or QR code. The mobile application122sends the extracted information to the service center130. In some embodiments, the message created by the mobile application102include the barcode or QR code itself. In further embodiments, the mobile application120adds information to the barcode or QR code or information extracted therefrom. The additional information may include, for example, an identification of the operator102, location information determined by a GPS in the mobile device, timestamp of scanning and/or transmission, and the like. In some embodiments, the message is encrypted.

Operations308-314correspond to operations204-210inFIG. 3, separately. In particular, at operation308, the mobile application host204receives a message from the user device120. At operation310, the message analyzer136analyzes the message received from the user device110. At operation312, the message generator138generates a return message based on the analysis by the message analyzer136. At operation314, the mobile application host134sends the return message generated by the message generator138to the user device110.

At operation318, the user device120receives the return message and displays the return message at the user interface124.

At operation320, the operator102inputs the key contained in the return message at the piece of equipment110. Operation of the piece of equipment110resumes. In some embodiments, the return message includes instructions/warnings besides the key, the operator102may follow the instructions to perform further actions.

The process illustrated inFIG. 3can be repeated, per triggering events. It should be understood that the equipment service process described with reference toFIG. 3is for purposes of illustration only and not for limitation. Any suitable equipment service process with more, fewer, and/or different operations can be implemented.