System and method for guiding operations on workpiece

Abstract

According to at least one aspect of the present disclosure, there is provided a method of managing a workflow for an industrial application. The method includes providing a guide device configured to communicatively connect to a tool configured to be used on a workpiece; obtaining identification data relating to the workpiece used in the industrial application; obtaining industrial application state data relating to at least one state of the industrial application; obtaining workpiece state data; operating the tool on the workpiece; obtaining tool operation data; uploading, via the boot device, at least one of the identification data, the industrial application state data, and the tool operation data to a service system; and verifying the industrial application state data.

Description

Technical Field

[0001] At least one example in accordance with the present disclosure generally relates to workflow management and control in industrial applications. Background Art

[0002] In large-scale industrial applications, such as building complex chemical production and refining facilities, it is often necessary that the individual components of the facility are correctly installed within predetermined tolerances so that the facility can operate efficiently and correctly. It may also be necessary to monitor the individual components in the facility to ensure that they remain suitable for their intended purpose. Inadequate quality and engineering controls can result in significant losses and huge repair costs. Summary of the invention

[0003] According to at least one aspect of the present disclosure, a method for managing workflows for industrial applications is provided. The method includes providing a guide device configured to be communicatively connected to a tool configured to be used on a workpiece; obtaining identification data related to the workpiece used in the industrial application; obtaining industrial application status data related to at least one state of the industrial application; obtaining workpiece status data; operating the tool on the workpiece; obtaining tool operation data; uploading at least one of the identification data, the industrial application status data, and the tool operation data to a service system via the guide device; and verifying the industrial application status data.

[0004] In some examples, obtaining industrial application status data related to at least one state of the industrial application includes: obtaining first industrial application status data related to the state of the industrial application before the tool is operated; obtaining second industrial application status data related to the state of the industrial application after the tool is operated; and uploading at least one of the first industrial application status data and the second industrial application status data to a service system. In various examples, the second industrial application status data is based at least in part on the tool operation data. In many examples, the method includes obtaining first workpiece status data corresponding to the state of the workpiece before the tool is operated; obtaining second workpiece status data corresponding to the state of the workpiece after the tool is operated; and uploading at least one of the first workpiece status data and the second workpiece status data to the service system.

[0005] In some examples, the second workpiece state data is based at least in part on the tool operation data. In various examples, the industrial application state data is obtained through a set of requirements that are verified by an end user. In many examples, the tool operation data is obtained from a sensor configured to monitor the operation of the tool on the workpiece. In some examples, verifying the industrial application state data includes: marking a workpiece for inspection in response to determining that an error may have occurred in the operation of the tool; performing a quality inspection on the workpiece; and releasing the inspection of the workpiece.

[0006] In some examples, the service system analyzes the data it receives and provides analysis information to a user, the analysis information including a data model of the artifact based at least on the industrial application status data. In various examples, verifying the industrial application status data includes checking the analysis information. In many examples, uploading to the service system via the boot device also includes: transmitting the industrial application status data from a client installed on the boot device to a local client communicatively connected to the client; transmitting the industrial application status data from the local client to a server communicatively connected to the local client, the server hosting a database configured to store the industrial application status information; and transmitting the industrial application status data from the server to the service system, the service system configured to perform operations on the industrial application status data.

[0007] In some examples, the service system is configured to perform operations on the industrial application status data including data analysis and constructing a data model of the industrial application associated with the industrial application status data. In various examples, the guidance device is further configured to provide workflow instructions to the end user, the instructions instructing the end user at least one of the following: on which workpiece to operate the tool; when to collect the industrial application status data; and when to collect the tool operation data. In many examples, providing the workflow instructions to the end user causes the guidance device to update the information displayed to the end user.

[0008] According to at least one aspect of the present disclosure, a non-transitory computer-readable medium having embodied thereon a sequence of computer-executable instructions for managing a workflow of an industrial application is provided.

[0009] In some examples, the computer-readable instruction sequence includes instructions instructing at least one processor to perform the following operations: provide workflow instructions to a first user; associate identification data with an artifact used in the industrial application; associate industrial application status data with one of a first industrial application status and a second industrial application status, wherein the first industrial application status corresponds to a status of the industrial application before a tool operates on the workpiece, and the second industrial application status corresponds to a status of the industrial application after the tool operates on the workpiece; associate workpiece status data related to the workpiece with the identification data; update at least the second industrial application status data based on tool operation data related to the operation of the tool on the workpiece; and upload at least one of the identification data, the first industrial application status data, the second industrial application status data, and the workpiece status data to a service system.

[0010] In some examples, the workflow instructions also include one or more of the following: selecting an appropriate tool to be used on the workpiece; recording the identification data associated with the workpiece; recording the industrial application status data; recording the workpiece status data; and stopping work on the workpiece while waiting for the release of a holder associated with the workpiece. In various examples, the instructions also instruct the processor to record the completion of the specified workflow instruction in response to the first user displaying the completion of the specified workflow instruction. In many examples, the instructions also instruct the at least one processor to instruct the service system to provide the data to the second user; perform data analysis on the data, the data analysis including building a data model of the workpiece; placing the holder on the workpiece in response to receiving an instruction to place the holder on the workpiece; and releasing the holder on the workpiece in response to receiving an instruction to release the holder on the workpiece.

[0011] In some examples, the data includes at least one of the industrial application state data, the workpiece state data, and the tool operation data. In various examples, the second user provides instructions to place the holder on the workpiece and release the holder on the workpiece. In many examples, the instructions also instruct the at least one processor to instruct the service system to provide the data analysis to the second user. In some examples, the instructions also instruct the at least one processor to change the workflow instructions in response to input from the second user.

[0012] According to at least one aspect of the present disclosure, a system for managing the workflow of industrial applications is provided. The system may include: at least one sensor; a guiding device configured to provide instructions to a user indicating an action to be performed by the user, receiving at least one of tool operation data, industrial application status data, and workpiece status data obtained in response to the operation of a tool from the at least one sensor, and providing the tool operation data, the industrial application status data, and the workpiece status data to a service system; and a service system configured to receive at least one of the tool operation data, the industrial application status data, and the workpiece status data, perform data analysis on the received data (including generating a data model associated with the workpiece), place a holder on the workpiece, release the holder from the workpiece, and review the received data.

[0013] In some examples, the tool operation data is associated with the operation of the tool and is received by the guidance device from the at least one sensor in communication with the guidance device, the at least one sensor being configured to monitor the operation of the tool to generate the tool operation data. In various examples, there is a local client configured to communicate with the guidance device and the service system, the guidance device providing the tool operation data, at least one of the industrial application status data, and the workpiece status data to the local client, and the local client providing the tool operation data, at least one of the industrial application status data, and the workpiece status data to the service system.

[0014] In some examples, the local client is further configured to provide updated data to the guidance device in response to receiving at least one of the following data: the industrial application status data, the workpiece status data, the tool operation data, data indicating placement of the retainer on the workpiece, and data indicating release of the retainer from the workpiece. In many examples, the industrial application status data includes first industrial application status data and second industrial application status data, the first industrial application status data corresponding to a status of the industrial application before the tool operates on the workpiece, and the second industrial application status data corresponding to a status of the industrial application after the tool operates on the workpiece. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Various aspects of at least one embodiment are discussed below with reference to the accompanying drawings, which are not drawn to scale. These drawings are included to provide illustration and further understanding of the various aspects and embodiments, and are incorporated into and constitute a part of this specification, but are not intended as a definition of limitations on any particular embodiment. The drawings, together with the rest of the specification, are used to illustrate the principles and operation of the described and claimed aspects and embodiments. In the drawings, each identical or nearly identical part shown in various figures is represented by a similar number. For clarity, not every component will be labeled in every figure. In the drawings:

[0016] Figure 1 shows a block diagram of an industrial application management system;

[0017] Figure 2A A block diagram of a workflow process for managing industrial applications is shown;

[0018] Figure 2B A block diagram showing a process for collecting status data prior to tool operation;

[0019] Figure 2C A block diagram illustrating a process for collecting tool operation data;

[0020] Figure 2D A block diagram showing a process for collecting status data after tool operation;

[0021] Figure 2E A block diagram of a remediation process for repairing errors in industrial applications is shown;

[0022] Figure 3 A block diagram of a workflow process is shown;

[0023] Figure 4A The workflow of the bolt connection assembly is shown;

[0024] Figure 4B shows the stress testing workflow;

[0025] Figure 5A The workflow builder interface is shown;

[0026] Figure 5B The control center interface is shown;

[0027] Figure 5C The workpiece interface is shown;

[0028] Fig. 6A The bolt tightening interface is shown;

[0029] Figure 6B The photo interface is shown; and

[0030] Figure 6C The checklist interface is shown. DETAILED DESCRIPTION

[0031] The application of the examples of the methods and systems discussed herein is not limited to the construction details and component arrangements set forth in the following description or shown in the accompanying drawings. These methods and systems can be implemented in other embodiments and can be implemented or executed in various ways. The examples of specific implementations provided herein are for illustrative purposes only and are not intended to be limiting. In particular, the actions, components, elements, and features discussed in conjunction with any one or more examples are not intended to exclude similar roles in any other examples.

[0032] In addition, the wording and terminology used herein are for illustration and should not be considered as limiting. Any reference to the examples, embodiments, parts, elements or actions of the system and method mentioned in the singular herein may also include embodiments comprising multiple, and any embodiments, parts, elements or actions quoted in the plural herein may also include embodiments comprising only the singular. Reference in the singular or plural form is not intended to limit the system or method, its parts, actions or elements of the present disclosure. "Including," "comprising," "having," "containing," "involving," and variations thereof used herein are intended to include the items listed thereafter and their equivalents and additional items.

[0033] References to "or" are understood to be inclusive, so any term described using "or" can mean singular, plural, and any of the described terms. In addition, if there is an inconsistency in the usage of a term between this document and a document incorporated herein by reference, the usage of the term in the incorporated feature is supplemental to this document; for irreconcilable differences, the usage of the term in this document controls.

[0034] Industrial applications include a wide variety of facilities, systems, and equipment used in a variety of industries. For example, industrial applications include large-scale facilities such as offshore refineries, chemical processing plants, oil pipelines, etc. Industrial applications can also include smaller-scale equipment and devices such as pressure chambers, distillers, etc.

[0035] Current industrial application management systems are inefficient and costly. Existing industrial application management systems result in poor record keeping, for example due to conflicts between individual contractors and the systems used by contractors to record industrial application data. Similarly, poor or ineffective training courses prevent workers from performing their tasks correctly, resulting in difficult to find and costly errors. Unqualified inspectors may not properly review industrial application sites and thus fail to identify worker errors. Inadequate and fragmented recordkeeping practices make it difficult to properly monitor errors when they occur, or to identify error patterns (for example, workers always apply insufficient or excessive torque to the bolts on the flange).

[0036] For example, in refineries and chemical plants (two industrial applications), ineffective joint management procedures can be costly. Industry data shows that up to 19% of first-level containment failure (LOPC) events, such as leaks, are caused by leaking bolted joints and flanges. These leaks can cost a facility $3 million or more per year, not including production and disaster losses, and can release hundreds of millions of metric tons of greenhouse gases into the atmosphere or leak chemicals into groundwater reservoirs and aquifers, among other things.

[0037] Therefore, there is a need for improved systems and techniques for industrial application management. The systems and techniques disclosed herein can reduce the likelihood of adverse and expensive events (such as LOPC events, etc.), improve the ability of owners and operators of industrial applications to identify and predict where failures may occur, reduce overhead and paperwork, etc.

[0038] Figure 1 A block diagram of an industrial application management system (IAMS) 100 according to an example is shown. The IAMS 100 includes one or more data sources 102, one or more boot devices 104, an optional local client 106, and a service system 108. A top user 110 is also shown, although it should be understood that the IAMS 100 can support multiple top users. Data sources include tools 102a, smart tools 102b, sensors 102c, and / or manual input devices 102d.

[0039] One or more data sources 102 are communicatively connected to a guiding device 104. The guiding device 104 is communicatively connected to a local client 106. The local client 106 is communicatively connected to a service system 108. The service system 108 can provide information related to industrial applications to a top-level user 110 via any suitable interface. It should be understood that if the optional local client 106 is not present, the guiding device 104 can be communicatively connected to the service system 108.

[0040] One or more data sources 102 provide data to the guidance device 104. One or more data sources 102 can provide any type of data to the guidance device 104, however, in some examples, one or more data sources 102 can provide data including industrial application status data, workpiece identification data, tool operation data, and other forms of data discussed in more detail below. In some examples, one or more data sources 102 can also receive instructions from the guidance device 104, such as a request to provide data.

[0041] The guiding device 104 performs a variety of functions. As described above, the guiding device 104 can receive data from one or more data sources 102 and can send instructions to one or more data sources 102. In addition, the guiding device 104 can provide instructions to be executed to the end user (e.g., a worker, supervisor and / or field engineer using and / or equipped with the guiding device 104). For example, the guiding device 104 can instruct the end user to collect a specific type of data, or to inspect a specific workpiece, or to perform a specific task. For example, due to the placement of a hold on the workpiece or due to some potential errors or problems that have been identified (which requires the end user to stop working on the industrial application), the guiding device 104 can also notify the end user of a stop work command. The guiding device 104 can also provide data to the local client 106 and / or the service system 108, for example, the guiding device can provide industrial application status data, workpiece identification data, tool operation data and any other type of data. The guiding device 104 will be discussed in more detail herein.

[0042] When the service system 108 is not accessible, and / or when it is necessary to perform data processing functions on a local network (e.g., a secure local network that is not connected to the Internet), an optional local client 106 can be used. The local client 106 can receive data from the boot device 104 and provide data and / or instructions to the boot device 104. For example, when more than one boot device 104 is used, the local client 106 can aggregate data received from each boot device 104 and then propagate updated data to each boot device 104. The local client 106 can also be configured to perform any functions that the service system 108 can perform.

[0043] The service system 108 can aggregate data collected by one or more data sources 102, and can perform data analysis on the data. For example, the service system 108 can build a data model for industrial applications and / or artifacts used in industrial applications. The data model can predict when maintenance should be performed, which artifacts or components of industrial applications may fail, and so on. The service system 108 can also provide data to the top user 110 for display through an interface. Possible interfaces and display modes will be discussed in more detail below. The service system 108 can also receive input including instructions from the top user 110. For example, in response to receiving data related to the artifact, the top user 110 can place a retainer on the artifact, requiring at least some work to be stopped. The service system 108 can then send a stop work command to the local client 106 and / or the guide device 104, which will then notify the end user to stop working. The service system 108 can also automatically classify the received data, maintain a database of data, and so on. The service system 108 can be implemented on a server, a distributed cloud-based architecture, a computer, and the like. The service system will be discussed in more detail below.

[0044] In the above examples, it should be understood that the one or more data sources 102 may include data sources other than tools 102a, smart tools 102b, sensors 102c, and manual inputters 102d. For example, any device or system capable of collecting the necessary data may be used.

[0045] It will also be understood that more than one guiding device 104 may be used at any time, and each guiding device 104 may be communicatively connected to the guiding device 104. Information may flow in an upstream and / or downstream direction. For example, when flowing in an upstream direction, information may flow from a data source 102 to a guiding device 104. The guiding device 104 may continue to transmit information in an upstream direction, such as to a local client 106 and / or a service system 108, etc. When flowing in a downstream direction, information may flow from a service system 108 to a local client 106 and / or guiding device 104, or in another example of downstream data flow, from a guiding device 104 to one or more data sources 102. Information may also flow in both directions, such that downstream and upstream data communications occur substantially simultaneously. Likewise, one or more local clients 106 or service systems 108 may also be used, and one or more top-level users 110 may access or receive data.

[0046] Figure 2A-2E A block diagram of methods and techniques related to industrial application management systems according to examples is shown.

[0047] Figure 2A A block diagram of a workflow process 200 for managing industrial applications is shown according to an example.

[0048] At a first action 202, an end user identifies a workpiece to be worked on. The end user may receive instructions through a guidance device (e.g., guidance device 104) that instruct the end user to find a specific workpiece or a known workpiece. The end user may find the workpiece and identify it, in particular, for example, by recording workpiece identification data. In some examples, the workpiece identification data will correspond to a unique workpiece (i.e., the workpiece identification data will correspond to and only correspond to one workpiece). In other cases, the workpiece identification data may correspond to multiple workpieces, for example, multiple related workpieces. In some examples, the end user may record one or more of the location of the workpiece, a serial number corresponding to the workpiece, one or more photographs of the workpiece, workpiece status data corresponding to the state of the workpiece at a specified time and / or before or after a specified event, etc. Any data that may be used to identify the workpiece may be recorded. The workpiece status data may also include data indicating that the workpiece is damaged, defective, or may not be suitable for industrial applications. This "mark" may be forwarded to a top-level user or a service system (e.g., service system 108), and a retainer may be placed on the workpiece to prevent the workpiece from being used before the workpiece is evaluated. The artifact identification data and the artifact status data may be recorded on the boot device and may be transmitted via the boot device to a data source, another boot device, a local client, a service system, a top-level user, or another person.

[0049] It should be understood that a workpiece can be any object that can be operated by a tool as part of an industrial application. For example, a workpiece can be a nut, bolt, fitting, fastener, wiring, pipe, gauge, valve, beam, filter, or any other such device.

[0050] At action 204, the end user collects state data corresponding to one or more of the industrial application and / or workpiece. Other data may also be collected. The industrial application state data collected at action 204 may correspond to the state of the industrial application before the operation of the tool (e.g., the operation of the tool on the workpiece identified in action 202). The collected workpiece state data may correspond to the state of the workpiece before the operation of the tool (e.g., the operation of the tool on the workpiece identified in action 202). It will be understood that the workpiece state data may be collected during this action, action 202, or other actions. However, whenever any type of state data is collected, this may also correspond to updating the previously collected state data or to providing additional or new state data associated with the previously collected state data. In some examples, the industrial application state data will be primarily related to the state of the industrial application adjacent to the workpiece. In these examples, the term "close" may mean physically close or functionally close, i.e., the workpiece and the industrial application state data are closely related in the functions they perform (e.g., a conveyor belt that transports waste to a shredder may need to store the waste in the shredder, so the components are functionally close because the operations of the components are related). In some cases, the state data collected at act 204 may be transmitted via the boot device to a data source, a local client, another boot device, and / or a service system, etc.

[0051] At action 206, the end user operates a tool on the workpiece. The tool can be any type of tool. For example, the tool can be a smart tool with built-in sensors, a regular tool without "smart" features, and the like. Those skilled in the art will recognize that certain tools are suitable for certain tasks, such as tightening a bolt with a wrench, or measuring a voltage difference with a voltmeter. Although in some examples, the end user receives instructions to use a specific tool on the workpiece, any suitable tool can be used on the workpiece. The end user can also receive tool operation instructions on how to use the tool on the workpiece, such as tool operation instructions that instruct the end user when to use the tool, what actions to use to operate the tool (e.g., how many times to turn the tool), etc. The tool operation instructions can be displayed and / or received via a guidance device.

[0052] At act 208, the end user collects tool operation data. The tool operation data corresponds to the use of the tool on the workpiece. For example, the tool operation data may include how many turns of the wrench were made on the workpiece, and / or an indication of how much resistance the workpiece presented to further operation. In general, the tool operation data may be obtained from any data source, such as Figure 1Any data source 102 in. It should be understood that the tool operation data does not need to be directly obtained by the tool. In some examples, the smart tool can directly provide the tool operation data to the guiding device. In other examples, a separate sensor (e.g., a torque sensor, a pressure gauge, a thermometer, etc.) can be used to obtain the tool operation data. In other examples, the end user can determine the tool operation data by himself (i.e., manually). It should be understood that the collection of tool operation data can be a continuous process. For example, when the tool is operating on the workpiece, the tool operation data can be continuously collected and / or updated. In some examples, the data source provides the tool operation data to the end user in real time so that the end user can adjust the operation of the tool according to the tool operation data. The tool operation data can be provided to the guiding device by the tool, sensor or other data source, and the guiding device can display the tool operation data to the end user, or transmit the tool operation data to the local client, service system, other guiding devices, etc.

[0053] At act 210, it is determined whether the operation of the tool is complete, or whether further operation of the tool is required. Determining whether the operation of the tool is complete can be a manual process, in which an end user evaluates the tool operation data to determine whether further operation of the tool is required, or can be an automated process. For example, in an automated process, the tool operation data can be provided to a guidance device, and the guidance device can determine when a threshold of tool operation is reached and further operation of the tool is not required. For example, the guidance device can receive tool operation instructions that instruct it to recognize when the tool has been fully operated and further operation is not required and / or desired. If further operation is not required, the process 200 continues to act 212. If further operation of the tool is required, the process 200 returns to act 206, and steps 206 to 210 can be repeated until the operation of the tool is completed or an error is detected and a retainer is placed on the workpiece.

[0054] At act 212, state data is collected. The state data may be substantially similar to the state data collected during act 202 and / or act 204. For example, the state data may include workpiece identification data, industrial application state data, workpiece state data, etc. In some examples, the collected state data may be modified, for example, based on tool operation data to reflect changes in the workpiece and / or industrial application caused by the operation of the tool. Figure 2A As shown, action 212 occurs after the tool is operated. Therefore, the collected state data will correspond to the state of the industrial application and / or workpiece after the tool is operated.

[0055] At action 216, any data collected during process 200 may be reviewed to detect errors and verify the correctness of the data. For example, photographs of workpieces and industrial applications near the workpieces may be reviewed to ensure that the correct workpieces were operated, or that the tools indicated by the data source were operated correctly, etc. The service system and / or local client may also evaluate the collected data to build data models and perform data analysis to assist in evaluating the collected data. The service system and / or local client and / or boot device may make the collected data, data analysis, data models, and / or other data available to end users, top users, or others.

[0056] At action 218, it is determined whether an error has occurred. The determination of whether an error has occurred can be made automatically, such as by a service system that analyzes the data set and flags the problem, or manually, such as by an inspector, engineer, auditor, etc. If it is determined that an error has occurred, the process 200 proceeds to remediation (200 yes). If no error has occurred, the process 200 proceeds to data verification (200 no).

[0057] At act 220, it is determined that an error has occurred, and process 200 proceeds to remediation steps to correct the error. Figure 2E An example of remediation is discussed in more detail.

[0058] At act 222, the data is validated. Refining operations may be performed on the data, and the service system may continue to use the collected data to build data models and monitor the performance or state of the industrial application or workpiece. Once the collected data is validated at act 222, the collected data is considered to be canonical (i.e., authentic and / or representative of the actual state of the industrial application and / or workpiece).

[0059] Figure 2B A block diagram of a process 300 for collecting status data prior to tool operation according to an example is shown. In some examples, the process 300 may be suitable for replacing Figure 2A Actions 202 and 204 of process 200.

[0060] At act 302, an end user identifies an artifact. The end user may Figure 2AThe workpiece may be identified in a substantially similar manner as described in act 202 of , such as by collecting workpiece identification data that may uniquely identify the workpiece. At act 304, the end user records the workpiece identification data according to a checklist, prompt, or other set of requirements for the workpiece identification data. For example, the end user may be prompted to enter and / or verify the type of workpiece, the serial number of the workpiece, the size of the workpiece, the material of the workpiece, etc. In some examples, the end user need not verify every requirement, but may only verify a subset of the requirements. In some examples, the end user may completely ignore certain requirements. Once the end user completes verification of the requirements, the verified requirement data may be stored and recorded, such as by a boot device.

[0061] At act 306, the end user collects industrial application status data. The industrial application status data can be Figure 2A The industrial application status data collected at action 204 of process 200 is substantially similar. At action 308, the end user records the industrial application status data based on a checklist, prompt, or other set of requirements for the industrial application status data. For example, the end user can be prompted to enter and / or verify the status data. In some examples, the end user does not need to verify each requirement, but can only verify a subset of the requirements. In some examples, the end user can completely ignore certain requirements. Once the end user completes verification of the requirements, the verified requirement data can be stored and recorded, for example, by a boot device.

[0062] At act 310, the end user collects artifact state data. The artifact state data may be associated with Figure 2A The artifact state data collected at act 202 of process 200 is substantially similar. At act 312, the end user records the artifact state data according to a checklist, prompt, or other set of requirements for the artifact state data. For example, the end user can be prompted to enter and / or verify the state data. In some examples, the end user need not verify every requirement, but can only verify a subset of the requirements. In some examples, the end user can completely ignore certain requirements. Once the end user completes verification of the requirements, the verified requirement data can be stored and recorded, for example, by a boot device.

[0063] At optional action 314, a quality check may be performed by an end user, a top user, or automatically by a service system, a boot device, and / or a local client. The quality check may include a review of the data collected so far. Errors may be identified and flagged for correction. For example, if a necessary or important requirement was not verified during actions 304, 308, or 312, the service system may issue a flag indicating that the top user or end user needs to review the requirement. In some examples, the top user reviewing the requirement may determine that the requirement warrants placing a retainer on the workpiece and perform remediation, such as Figure 2E Likewise, in some examples, a service system, local client, or boot device may automatically determine that a retainer should be placed on a workpiece and that remediation is required before further work is completed.

[0064] Figure 2C A block diagram of a process 400 for collecting tool operation data according to an example is shown. The process 400 may replace or supplement Figure 2A Actions 206 to 210 of process 200.

[0065] At act 402, an end user operates a tool on a workpiece. The end user may Figure 2A The tool is operated in a substantially similar manner as described in act 206 of process 200. At act 404, tool operation data is collected. The tool operation data may be in the form of Figure 2A The tool operation data may be collected in a substantially similar manner as described in act 208 of process 200. In act 406, the end user records the tool operation data according to a checklist, prompt, or other set of requirements for the tool operation data. For example, the end user may be prompted to enter and / or verify the tool operation data. In some examples, the end user need not verify every requirement, but may only verify a subset of the requirements. In some examples, the end user may completely ignore certain requirements. Once the end user completes verification of the requirements, the verified requirement data may be stored and recorded, for example, by a boot device.

[0066] In optional act 408, a quality check may be performed by an end user, a top user, or automatically by a service system, a boot device, and / or a local client. The quality check may include a review of the data collected so far. Errors may be identified and flagged for correction. For example, if a necessary or important requirement was not verified during act 406, the service system may issue a flag indicating that the top user or end user needs to review the requirement. In some examples, the top user reviewing the requirement may determine that the requirement warrants placing a retainer on the workpiece and perform remediation, such as Figure 2E Likewise, in some examples, a service system, local client, or boot device may automatically determine that a retainer should be placed on a workpiece and that remediation is required before further work is completed.

[0067] Figure 2D A block diagram of a state data collection process 500 according to an example is shown. The process 500 may be adapted to supplement and / or replace Figure 2A Action 212 of process 200 .

[0068] At action 502, an end user collects industrial application status data. The end user can Figure 2AIndustrial application status data is collected in a manner substantially similar to that described in acts 212 and / or 204 of process 200. At act 504, the end user records the industrial application status data based on a checklist, prompt, or other set of requirements for tool operation data. For example, the end user may be prompted to enter and / or verify the collected data. In some examples, the end user need not verify each requirement, but may only verify a subset of the requirements. In some examples, the end user may completely ignore certain requirements. Once the end user completes verification of the requirements, the verified requirement data may be stored and recorded, for example, by a boot device.

[0069] At optional act 506, a quality check may be performed by an end user, a top user, or automatically by a service system, a boot device, and / or a local client. The quality check may include a review of the data collected so far. Errors may be identified and flagged for correction. For example, if a necessary or important requirement was not verified during act 506, the service system may issue a flag indicating that the top user or end user needs to review the requirement. In some examples, the top user reviewing the requirement may determine that the requirement warrants placing a retainer on the workpiece and perform remediation, such as Figure 2E Likewise, in some examples, a service system, local client, or boot device may automatically determine that a retainer should be placed on a workpiece and that remediation is required before further work is completed.

[0070] Figure 2E A block diagram of a remediation process 600 according to an example is shown. The remediation process 600 may supplement or replace Figure 2A The remediation process 600 is also suitable for following the steps in the process 200. Figure 2B-Figure 2D Examples of any quality checks described, or remediation processes in any other situations where errors may have occurred.

[0071] At action 602, the collected data is analyzed for errors. The collected data may include any one or all of tool operation data, industrial application status data, workpiece status data, workpiece identification data, etc. In some examples, data models generated by data analysis, such as data analysis provided by a service system, may also be used to determine and / or predict whether an error may exist or has occurred. In some examples, if an error is detected, a mark is raised (or set). The mark may be raised, for example, manually by an end user or a top user, or automatically generated, for example, by a service system, a local client, or a guide device. The mark may be associated with the workpiece and may indicate that a retainer should be placed on the workpiece. The mark does not necessarily indicate that an error has occurred, but instead may indicate that an additional quality check or inspection of the workpiece is required to verify whether an error has occurred. However, in some examples, the mark may indicate that an error has occurred. It will be understood that, although the term "mark" is used, a mark does not necessarily refer to a physical mark. A mark may refer to a software mark, such as when a variable or value is set, so that a service system, a local client, or a guide device responds by marking the workpiece associated with the mark as requiring review and / or remediation. In this way, tags can be passed through the entire workflow system (e.g. Figure 1 The system) propagates a potentially erroneous state.

[0072] If no error is detected (602 No), process 600 may proceed to act 610. If an error is detected (602 Yes), process 600 proceeds to act 604.

[0073] At action 604, a retainer is placed on the workpiece. The retainer placed on the workpiece ensures that no tool will operate on the workpiece until the workpiece assessment is completed and remediation is performed if necessary. The retainer can be placed on the workpiece manually, for example, by an end user or a top user, or automatically placed, for example, by a service system, a local client, or a guide device. When there is a retainer on the workpiece, other workpieces will also be affected. For example, it may not be suitable to work on the second workpiece until the marked workpiece is reviewed and remedied. In this case, a temporary mark can be set on the second workpiece so that the retainer is placed on the second workpiece before the problem of placing the retainer on the marked workpiece is solved. In some examples, as described below in actions 604, 606, and 608, when the marked workpiece is checked and released, the temporary mark will be automatically removed. However, based on the assessment of the second workpiece, the end user, the top user, or the service system, the guide device, or the local client can manually or automatically delete the temporary mark. For critical workpieces, retainers can be set regardless of any errors detected. For example, if an artifact serves some critical function or purpose such that an industrial application cannot function if the artifact has an error, a hold may be placed on the critical artifact to ensure that the artifact is inspected before processing other artifacts. This behavior can be beneficial in ensuring that time and resources are not wasted due to unnoticed or undetected errors in critical artifacts. In some examples, automatic holds may be placed on any artifact for any reason based on end-user or top-level user input or project requirements.

[0074] At action 604, a determination is made as to whether remediation is required. The determination as to whether remediation is required may be performed automatically by a service system, a boot device, or a local client, or may be performed manually by an end user or a top-level user. In some examples, the service system, the local client, or the boot device may provide relevant data and analysis to the top-level user so that the top-level user may examine the reasons for the hold based on the data that has been collected, and then determine whether remediation is required without having to physically inspect the workpiece in person. In some examples, an end user, a supervisor, a field engineer, an inspector, or other personnel may be dispatched to the workpiece to physically inspect the workpiece. In examples where someone physically inspects the workpiece to determine whether remediation is required, the boot device may collect data related to the remediation process (including industrial application status data, workpiece identification data, workpiece status data, tool operation data, etc.). The boot device may collect data from data sources such as Figure 1Some or all of the data may be collected from a data source 102, etc.). In some examples, collecting remedial data may include asking the inspector to check various requirements, such as those in a checklist or based on other instructions, and verifying that those requirements are met. In this way, the system can ensure that even inspectors who are not fully trained can get precise instructions on what to do and what data to collect for real-time and artifact-based review. It should be understood that the requirements and instructions described herein may be based on the needs of industrial applications. Once the remedial data is collected and / or the artifact is inspected, the remedial data may be automatically or manually analyzed to determine whether remediation is required, for example by a service system and / or a top-level user. In some examples, remediation is required if the artifact does not meet certain minimum requirements related to its state, condition, operation, etc.

[0075] If it is determined that remediation is required (606 Yes), process 600 proceeds to act 606. If it is determined that remediation is not required (606 No), process 600 proceeds to act 608.

[0076] At action 606, remedial action is taken. In some examples, the remedial action includes operating a tool on the workpiece to correct the incorrect earlier operation of the tool on the workpiece. In some examples, the remedial action includes replacing the workpiece. In some examples, the remedial action may include more substantial actions, such as marking the workpiece for a peripheral design (design-around), in which engineers may need to design new elements for the industrial application to solve the irreparable defects in the workpiece. It should be understood that the remedial actions can be different and vary greatly, and can be creative in themselves or previously known in the art. Once the remedial action is completed, the process 600 returns to action 604, and the action 604 can be repeated to determine whether additional remedial actions are needed. For example, further analysis as discussed with respect to actions 602 and / or 604 may be required because the remedial action may have changed the state of the industrial application and / or the workpiece so that the conditions previously guaranteed to be maintained are no longer applicable, but it is not known whether there is an error in the new state of the industrial application and / or the workpiece. If no new remedial action is required (604 No), the process 600 proceeds to action 608.

[0077] At action 608, the holder on the workpiece is released. Any temporary holders on other workpieces may also be released. The holder may be released manually or automatically, such as by a top-level user and / or a service system. Then, process 600 proceeds to action 610.

[0078] At act 610, process 600 is complete and the data may be verified, e.g., as Figure 2A As described in action 222 of process 200.

[0079] exist Figure 2A-2E In the above examples, when the terminal user receives instructions, prompts or other communications and / or data, the terminal user may receive the instructions, prompts, communications and / or data via the guiding device.

[0080] Figure 3 A block diagram of a workflow process 700 according to an example is shown. It should be understood that the process 700 may be performed instead of or in addition to Figure 2A The elements and actions of process 700 are not necessarily exclusive of process 200 .

[0081] At action 702, the end user receives (or is provided with) a boot device. The boot device can be any type of device capable of receiving and transmitting data by any method, although in some embodiments, the preferred method may be a wireless data transmission method (e.g., Bluetooth). The boot device may include boot device client software ("Client Software"). Client software may be software that communicates with local clients, service systems, and data sources, and may be updated remotely or manually. The Client Software may provide an interface that allows the end user to access functionality corresponding to other processes and systems described herein. For example, the boot device may enable the end user to obtain data from a data source or, for example, Figure 1 and Figure 2A-2E The client software may also provide other functions that are not directly related to the end user. For example, the client software may include code (such as a driver, etc.) that allows the boot device to automatically identify and interact with sensors, smart tools, manual forms (e.g., through an OCR process), and other data sources. Similarly, the client software may include code that allows the boot device to automatically identify and interact (communicatively couple) with other boot devices, local clients, and / or service systems.

[0082] Once the end user receives the boot device, the end user may activate the boot device. For example, the end user may be required to log into the boot device and / or client software using credentials (e.g., a username and password that may be unique to a particular end user, contractor, organization, etc.). Once the end user activates the boot device, process 700 proceeds to act 704.

[0083] At action 704, the end user receives workflow instructions from the guide device. The workflow instructions may be provided by a software interface displayed on the screen of the guide device, or may be provided in other ways. The form of the workflow instructions may vary for specific industrial applications, workpieces, or projects. The workflow instructions instruct the end user what to do. The workflow instructions may include information such as the workpieces that the end user must process, when the end user must perform processing on the workpiece, how and when to collect status data and other data from the data source, how to record and verify the collected data, what to do when errors are identified, how to operate any tools required to complete the work (e.g., process the workpiece, etc.). The workflow instructions may be automatically generated by the local client and / or the service system, or may be determined by the top user and transmitted to the guide device via, for example, the service system and / or the local client. The workflow instructions may be updated at set time intervals, in real time, etc. Once the workflow instructions are received, the process 700 proceeds to action 706.

[0084] At action 706, the end user determines whether the guidance device indicates whether there is any work to be performed. For example, if the end user completes all assigned work within a given time frame, the guidance device may indicate that there is no more work to be done. If the end user determines that the work is completed (706 Yes), the process 700 continues to action 707. If the end user determines that there is still work to be completed (706 No), the process 700 continues to action 708.

[0085] At action 707, process 700 enters a pause until additional work is to be performed. For example, work may be paused until a time frame is reached in which the additional work is to be performed. Likewise, work may be paused until further workflow instructions are received instructing the end user to perform a task. If further work is to be performed, process 700 may proceed to a different action, such as action 704 or action 702.

[0086] At act 708, the end user obtains artifact identification data. In some examples, the end user may have received workflow instructions instructing the end user to perform work on a particular artifact or group of artifacts. The end user may then find the relevant artifact and record the artifact identification data associated with the artifact. In some examples, the artifact identification data obtained may be substantially similar to the artifact identification data obtained at act 202 of process 200. The artifact identification data may be obtained from any data source (e.g., Figure 1 Once the artifact identification data required for the workflow instruction is obtained and recorded on the boot device, process 700 proceeds to action 710.

[0087] At act 710, potential errors are identified. For example, a set of requirements regarding artifact identification data may be presented to an end user, and verification of these requirements may be required. In some examples, the end user may mark specific errors or potential errors. In some examples, the boot device, client software, local client, and / or service system may automatically identify errors and potential errors and take appropriate action. For example, if the error requires a hold (710 is yes), process 700 may proceed to act 711 and a hold may be placed on the artifact identified by the end user. The hold may include marking the artifact, and remedial action may be required, such as Figure 2E In some examples, after setting the retainer on the workpiece, process 700 can return to an earlier action. In some examples, process 700 can return to action 704, and the guide device can receive new instructions to provide to the end user, such as performing remedial measures on the workpiece, or performing work on a different workpiece. Process 700 can then continue from the earlier action as described above.

[0088] If no error is detected (710 No), process 700 continues to act 712. At act 712, the end user receives instructions from the guide device to obtain status data. The status data may include industrial application status data, workpiece status data, etc. Once the status data is obtained, process 700 proceeds to act 714.

[0089] At action 714, the end user receives workflow instructions instructing the end user to operate a tool on a workpiece. The guidance device may provide instructions instructing the end user how to use the tool, in what order to use the tool, when to monitor the use of the tool, and / or receive data from a data source indicating the state of the workpiece or the operation of the tool on the workpiece. As with other examples provided herein, the data described herein may be retrieved at discrete time points or continuously and may be provided to the user by the guidance device at intervals or continuously.

[0090] At act 716, the guide device may indicate that the tool operation is complete (716 Yes). Alternatively, the guide device may indicate that the tool operation is not complete and further tool operation is required (716 No). If further tool operation is required, the process may return to act 714. If no further tool operation is required, the process 700 may proceed to act 718.

[0091] At action 718, the guide device receives tool operation data from, for example, a data source. The guide device may provide workflow instructions to the end user, telling the end user what type of tool operation data to record and how to process the data. Then, process 700 proceeds to action 720.

[0092] At action 720, the guidance device obtains state data. The obtained state data may be similar to the state data obtained at action 712, but now the state changes of the industrial application and / or workpiece corresponding to the tool operation are combined with the tool operation data. The guidance device may provide workflow instructions to tell the end user what type of state data to record, in what form, sequence, how to process the state data, etc. Then, process 700 proceeds to action 722.

[0093] At action 722, the guiding device uploads the collected data to a local client, other guiding devices, and / or a service system. The guiding device may provide workflow instructions instructing the end user to authorize the upload or may automatically upload. Process 700 then continues to action 704, where the guiding device provides new workflow instructions to the end user, and process 700 may then repeat from action 704.

[0094] It should be understood that act 710 may occur after or concurrently with any other act of process 700. For example, after obtaining status data at act 712, a similar evaluation may be performed on the received status data to determine whether an error has occurred or may exist. Thus, process 700 may proceed to act 711 at any time after identifying an error at act 710. In other words, at any time in process 700, an evaluation for and / or errors may occur, and a retainer may be set on the workpiece in response to identifying an error or potential error.

[0095] It will also be understood that the end user can provide a suitable device on which the client software will be installed. Installing the client software on a suitable device can configure the suitable device to be used as a boot device. In some examples, the boot device and / or the suitable device can be a mobile phone or tablet computer, or other types of computers or smart devices.

[0096] Figure 4A and Figure 4B An industrial application workflow according to an example is shown.

[0097] Figure 4A A bolt connection assembly workflow 800 according to an example is shown. The workflow 800 includes a labeling action 802, a disassembly action 804, an assembly action 806, a holding point 808, a tightening action 810, and a quality control action 812.

[0098] In labeling action 802, the guide prompts the end user to provide a photo of the location where the workpiece is (or will be) located in the industrial application. The checklist may also prompt the end user to provide other information, such as a unique location identifier or any retailer's mark. The assembly workflow 800 then proceeds to action 804.

[0099] Decomposition action 804 includes the guidance device prompting the end user to take a photo of the workpiece and complete a required checklist related to the photo. For example, the guidance device may prompt the end user to take photos of the left and right surfaces of the workpiece. In some examples, the checklist may include taking photos of certain angles of the workpiece (here, the bolt joint), recording the serial number, recording any worker marks at the location, etc. The guidance device can present the checklist to the end user, and the end user can fill out the checklist. Alternatively, the end user can be prompted to upload data through the checklist. For example, the checklist may require a front photo of the workpiece, and may not proceed to the next item until the photo is provided. Then, process 800 can proceed to action 806.

[0100] The assembly action 806 includes the guidance device prompting the end user to assemble the necessary tools and parts. For example, the guidance device can provide workflow instructions to instruct the end user to assemble the bolts and washers required for the task, take photos of the bolts and washers, and fill out a checklist or otherwise verify the requirements related to the tools and parts. Once the end user completes the assigned tasks, the process 800 can proceed to action 808.

[0101] At action 808, a retainer is placed on the workpiece and any previously completed tasks or work can be checked. For example, an end user, supervisor, lead, local client, service system, and / or top-level user can review the data collected so far, such as photos of the workpiece, bolts, and washers, and perform a quality check to ensure that no remedial action is required. Action 808 can be optional. In addition, the quality check can occur at any point in the assembly workflow 800 and need not occur only after assembly action 806. Once the quality check is completed, the workpiece can be released and the assembly workflow 800 can proceed to action 810.

[0102] At tightening action 810, the guidance device provides workflow instructions to the end user, instructing the end user to tighten the workpiece by, for example, tightening a bolt or a washer. The workflow instructions may instruct the end user to select a specific tool or tool type, perform 4 passes of tightening (the end user tightens the workpiece four times in a specific manner), take a photo of the work performed (e.g., bolting), and then fill out a checklist or verify a set of requirements. Once tightening action 810 is completed, process 800 proceeds to action 812.

[0103] At quality check action 812, data collected during any other actions may be provided to a local client, service system, or other guidance device. The collected data may be analyzed by the guidance device, local client, service system, top user, other end user, etc., and potential errors and actual errors may be evaluated. The guidance device may provide the end user with a checklist of requirements to be verified before the quality check is completed, as well as instructions on how to verify each requirement. If further evaluation or data is required, the guidance device may provide workflow instructions instructing the end user to collect additional data, such as photos of the bolted joint, etc. The collected data may be further reviewed and used to verify the work performed by the end user, or to analyze errors.

[0104] Figure 4B A pressure test workflow 900 according to an example is shown. The pressure test workflow 900 includes an inspection action 902, a pre-test process action 904, a static pressure test action 906, a post-test process action 908, a quality control action 910, and two hold point actions 905,909.

[0105] At inspection action 902, the guidance device may provide workflow instructions to the end user to inspect an artifact, such as a valve, pipe, or other device under pressure. The guidance device may provide a checklist of requirements to be verified and may request a photo of the artifact location from the end user. The guidance device may also request any additional artifact identification data. Once the guidance device receives the requested data, process 900 may proceed to action 904.

[0106] At action 904, the guidance device can provide workflow instructions to the end user, prompting the end user to prepare the test artifact. For example, the guidance device can prompt the end user to verify that the necessary tools are present, the correct artifact and (if necessary) replacement parts are present, the correct data source is present, etc. The workflow instructions can also instruct the end user to calibrate the data source or perform other preparatory tasks. The stress test workflow process 900 can then proceed to action 905.

[0107] At act 905, a holder may be placed on the workpiece under quality inspection. Quality inspection may be performed with Figure 4A The quality check performed in action 808 of process 800 is substantially similar. The quality check can verify whether the pre-test process and inspection actions 904, 902 are correctly performed before the holder is lifted on the workpiece. Once the holder on the workpiece is lifted, process 900 can proceed to action 906.

[0108] At action 906, the guidance device provides workflow instructions instructing the end user to perform a hydrostatic test to verify that the workpiece is under the correct amount of pressure, or in some examples, to properly maintain or handle a given pressure. The workflow instructions may include instructions instructing the end user to select a specific measuring instrument (e.g., a pressure sensor) for measuring pressure. The workflow instructions may also instruct the end user to verify that the measuring instrument is communicating correctly with the guidance device, and / or may prompt the end user to record the measuring instrument output when the measuring instrument is used to sense pressure associated with the workpiece. The workflow instructions may also instruct the end user to collect additional data, such as industrial application status data, tool operation data, and / or workpiece status data corresponding to the pre-pressure test and / or post-pressure test state of the workpiece and / or industrial application. For example, the guidance device may instruct the end user to take a photo of the pressure test setup before performing the pressure test. The workflow 900 may then proceed to action 908.

[0109] At action 908 , the guidance device provides workflow instructions, prompting the end user to collect industrial application status data, workpiece status data, tool operation data, etc. For example, the guidance device may prompt the end user to take a photo of the workpiece after the pressure test is completed.

[0110] At act 909, a retainer may be placed on the workpiece prior to quality inspection. Quality inspection may be performed with Figure 4A The quality check performed in action 808 of process 800 is substantially similar. The quality check can verify that the above actions 906 and 908 are correctly performed before the holder is lifted on the workpiece. Once the holder on the workpiece is lifted, process 900 can proceed to action 910.

[0111] At action 910, the data collected during any other actions may be provided to a local client, service system, or other lead device. The collected data may be analyzed by the lead device, local client, service system, top user, other end user, etc., and potential errors and actual errors may be evaluated. The lead device may provide the end user with a checklist of requirements to be verified before the quality check is completed, as well as instructions to the end user on how to verify each requirement. If further evaluation or data is required, the lead device may provide workflow instructions instructing the end user to collect additional data, such as photos of the bolted connection, etc. The collected data may be further reviewed and used to verify the work performed by the end user, or to analyze errors.

[0112] It should be appreciated that once the quality control actions 812, 910 are completed and the data is validated, the collected data may be considered canonical data regarding the associated artifact.

[0113] Figure 5A-Figure 5CA top-level user interface according to an example is shown.

[0114] Figure 5A A workflow builder interface 1000 according to an example is shown. The workflows described herein, such as processes 800 and 900, can be created or generated by a user (e.g., a top-level user) and / or a service system configured to integrate and communicate with client software. These service systems can provide a workflow builder interface 1000 to the top-level user to facilitate the design and creation of workflows according to the needs of a specific industrial application or the requirements of the top-level user.

[0115] The top user can design any desired workflow process and can set hold points, quality control checks, and work as needed. The top user can define sub-actions and merge them into the workflow. The top user can specify the order of actions to perform the workflow and can update the workflow in real time or in response to receiving data collected by the guide device. As shown in the figure, the workflow includes a decomposition action 1002, an assembly action 1004, an intermediate action 1006, a field completion action 1008, and a quality control action 1010. Each action contains many sub-actions. The decomposition action 1002 includes four sub-actions: a first decomposition sub-action 1002a including a record connection label action and a confirmation action, a second decomposition sub-action 1002b including a checklist action and a confirmation action, a cut connection sub-action 1002c including a photo action and a confirmation action, and a blast / sand action 1002d including multiple actions (e.g., a checklist, a photo, a check photo, and a confirmation action). Other actions 1004, 1006, 1008 also include sub-actions (not marked) with one or more actions. It will be understood that a workflow created by the workflow builder interface 1000 can have any number of actions, each action having any number of sub-actions, and each sub-action having any number of actions associated therewith.

[0116] The workflow created by the top-level user can be automatically compiled and converted into workflow instructions provided to the end-user by the bootstrap device.

[0117] Figure 5BAn example of a control center interface 1100 according to an example is shown. These service systems can generate a control center interface 1100 and fill it with relevant data to provide to top users. The control center interface 1100 provides access to data analysis and other information related to industrial applications. For example, as shown in the figure, the control center interface 1100 provides a timeline of a completion level diagram 1102 of an industrial application to the top user. The line on the completion level diagram 1102 represents the completion percentage of the work performed on the industrial application. The subsystem distribution diagram 1104 is shown by category, and how many workpieces remain unchanged in each category compared to the workpieces that have been identified, operated with tools, passed and / or failed quality inspections, etc. The top bar 1106 provides at-a-glance information about the overall status of the work performed on the industrial application. It will be understood that other data, such as work completed by day, exceptions, errors, and any other information required, can also be included.

[0118] Figure 5C An artifact interface 1200 according to an example is shown. The artifact interface 1200 provides top-level users with data related to a particular artifact. The top-level user can view at a glance the status of various types of actions, such as tagging (identifying) an artifact, etc. The artifact interface 1200 allows the top-level user to quickly view the data collected about any artifact, as well as view a summary that highlights important data related to the artifact.

[0119] Figure 6A-6C Various boot device interfaces according to examples are shown.

[0120] Fig. 6A A bolt tightening interface 1300 according to an example is shown. The interface features four hexagons labeled 1, 2, 3, and 4. Each hexagon is associated with a workpiece (e.g., a bolt on a piece of equipment). Each hexagon may have a color assigned to it indicating an error state of the workpiece. Each hexagon may also have a number on it indicating the order in which the end user operates the tool on the workpiece.

[0121] Figure 6B A photo interface 1400 according to an example is shown. The guide provides instructions for taking a photo of a workpiece (e.g., a flange face), and the end user then takes the photo. Once the end user has taken a photo of the workpiece, the guide displays the taken photo and gives the end user an opportunity to submit or retake the photo.

[0122] Figure 6CA checklist interface 1500 according to an example is shown. During a quality inspection, when a retainer is placed on a workpiece, or when a workflow includes a required step for the end user to verify certain requirements, the guide device can present the checklist interface 1500 to the end user. The checklist can be designed by the top-level user to include any options. As shown, the checklist interface 1500 includes five yes / no questions for the end user to select answers, including "yes", "no" and "N / A" (not applicable). Once the end user answers the questions, the end user can submit the answers. When submitting the answers, the guide device can upload the answers to other guide devices, local clients, and / or service systems. The answers can be analyzed by the service system, and the data contained in the answers can be made available via the top-level user interface (such as information about Figure 5A-Figure 5C Discussion interface) is available to top-level users.

[0123] Now will provide the operation example of the aspects and elements of the present disclosure. In the example, the industrial application needs to perform work, such as building a facility or repairing a facility or a piece of equipment within the facility. The industrial application workflow may be needed to improve efficiency, maintain records and monitor the working status in real time.

[0124] A service system can be set up to manage workflows. A top-level user can design a workflow, creating instructions for each step of the workflow. Local clients can also be set up to provide any functionality provided by the service system if the service system is temporarily or permanently unavailable. As part of implementing a workflow, a top-level user can create various steps or actions, and populate each action with sub-actions. Each sub-action can be populated with various actions or requirements. In this example operation, the work to be performed includes pressure testing of valves that need to be installed.

[0125] Thus, the top-level user defines the artifact—the valve to be installed—and the data source—the pressure sensor. The top-level user may also define the various tools to be used, such as a wrench to adjust the valve and tighten it into place. The top-level user may also determine the location or part of the industrial application where the valve is to be installed. In this example, the top-level user defines the following actions as part of the workflow instructions: (1) identify the artifact and collect the necessary tools and sensors, (2) identify the parts of the industrial application and take photos of the parts before operating the tools, (3) perform quality checks on the artifact (valve) and tool to ensure they are in a ready-to-use condition, (4) pair the pressure sensor with the guide, (5) operate the tool on the artifact and take pressure readings from the valve, (6) take photos of the artifact and industrial application parts after completing the tool operation and upload data from the pressure sensor, (7) perform data analysis on the data and issue a hold if necessary, and (8) if a hold is issued, prompt the top-level user to prepare remedial instructions.

[0126] The top-level user submits the workflow instructions to the service system, which forwards the workflow instructions to the guidance device. At the work site (i.e., at the industrial application), the end user (worker) receives the guidance device, for example, from the manager, and the guidance device displays the workflow instructions. More specifically, the guidance device displays and identifies the workpiece actions (such as Figure 2A The guide device may automatically pair with the pressure sensor, or the end user may manually pair the guide device with the pressure sensor. For each action taken, the end user indicates through input to the guide device that they have retrieved the workpiece, sensor, and tool, and paired the sensor with the guide device. The guide device confirms that each action has been completed and then displays the next set of workflow instructions.

[0127] The next workflow instruction instructs the end user to collect application and artifact state data, e.g., corresponding to Figure 2A Action 204 of . For example, the instructions instruct the end user to identify a part of the industrial application in which the valve is to be installed, and to take a photo of the part. In response to receiving these instructions, the end user proceeds to the specified part of the industrial application—in this example, the pipe in which the valve is required—and takes a photo of the pipe. The end user may also optionally identify the pipe by any markings on the pipe or on the surrounding environment, or by the geographic location of the pipe (e.g., by a set of coordinates). The end user inputs the photo and other status information to the guidance device. The guidance device then provides workflow instructions to the end user, instructing the end user to verify the condition of the valve, wrench, and sensor. The end user can manually check the parts for errors, take photos of each part, and so on. The collected data is submitted to the guidance device, which proceeds to the next set of workflow instructions.

[0128] The workflow instructions now instruct the end user to operate the tool and collect, e.g., Figure 2A The guidance device instructs the end user to pair the sensor with the guidance device (if not already paired). Once the sensor is ready, the guidance device instructs the end user to operate the tool and may provide detailed instructions. For example, the guidance device may instruct the end user to tighten the valve using a wrench by turning the wrench a certain number of times in a particular direction and then testing the pressure in the valve using a pressure sensor. If the pressure is insufficient, the guidance device may instruct the end user to continue tightening the valve by turning the wrench an additional number of times and then checking the pressure sensor again. Once the pressure sensor returns an acceptable value, data related to the tool operation (e.g., the number and direction of rotations) and the pressure level is uploaded to the local client and / or service system via the guidance device.

[0129] The boot device then provides the next set of workflow instructions, such as corresponding to Figure 2A Action 212. The workflow instructions may instruct the end user to take additional photos of the valve and pipe (i.e., workpiece and industrial application) after the tool operation. The end user verifies the completion of these operations, and the data is recorded by the guide device and / or uploaded to the local client / service system. Once the end user has collected all the required data, the end user receives instructions on the completion of the work on the workpiece. The data is then reviewed.

[0130] For example, the guiding device uploads all collected data to the service system, which may correspond to Figure 2A Action 216. The service system analyzes the data and builds a data model of the artifact and industrial application. Any potential errors are flagged. For example, it may be expected that a valve only requires ten turns to tighten, but the end user requires twenty turns. Excessive turns may indicate a problem with the valve or the pipe. Therefore, the service system may automatically flag the valve for inspection, or may submit the error to the top user, who then determines whether to flag the valve for inspection.

[0131] If an error is detected, such as corresponding to Figure 2A Action 218 (Yes) may require remediation, such as corresponding to Figure 2A Action 220. If remediation is required, the top-level user can create additional remediation instructions in a manner substantially similar to creating workflow instructions, and then provide the remediation instructions to the guidance device via the service system. The end user can receive the guidance device and take action based on the remediation instructions.

[0132] If no error is detected, such as corresponding to Figure 2A Action 218 (No), then the data may be verified, for example corresponding to Figure 2A Action 222. When the data is validated, all data is aggregated and recorded and is considered canonical data (i.e., true data). The data can then be accessed by top users and others for inspection, auditing, or any other purpose.

[0133] It will be understood that the term tool does not necessarily refer to a single tool of a single type. The term tool may refer to one or more tools of one or more different types. For example, a tool may be a screwdriver, or it may be two or more tools such as a screwdriver and a wrench. It will be understood by those skilled in the art that some workpieces require multiple tools of multiple types to operate properly on the workpiece for a desired effect or purpose.

[0134] It will also be understood that any actions described herein with respect to any process or workflow may be performed in any order, and not necessarily only in the order described.

[0135] Various devices can be used to perform the various operations described above. The tools, including smart tools, can be any type of tool (wrench, hammer, drill, screwdriver, drain snake, etc.) and should not be considered to be limited to any particular category or group of tools. The guiding device can be any type of computing device that can be configured to communicate with the sensor (mobile phone, personal digital assistant, tablet computer, laptop computer, ASIC, FPGA, any device with a processor or microprocessor, etc.). The sensor can be any type of sensor (analog or digital) and can communicate with the guiding device directly or indirectly. Examples of direct communication include: communication protocols designed to transmit data from the sensor to the guiding device without a medium (Bluetooth, wifi, optical communication protocols, etc.), and examples of indirect communication include: manual input, relaying data through an intermediary system (such as a server or USB flash drive), etc. The local client and service system can be any type of discrete or distributed computer system (mobile phone, PDA, tablet computer, laptop computer, desktop computer, ASIC, FPGA, any device with a process or microprocessor, server, cloud-based server or server infrastructure, etc.). As shown in these examples, many specific combinations of hardware and software may be used according to examples of the present disclosure to perform the operations described herein, and the present disclosure is not limited to any specific combination of hardware and software components. Examples of the present disclosure may include a computer program product configured to perform the above methods, processes, and / or operations. The computer program product may be or include one or more controllers and / or processors configured to execute instructions to perform the above methods, processes, and / or operations.

[0136] Having thus described several aspects of at least one embodiment, various modifications, variations and improvements will readily occur to those skilled in the art. These modifications, variations and improvements are intended to be a part of this disclosure and are within the spirit and scope of this disclosure. Therefore, the above description and accompanying drawings are intended only as examples.

Claims

1. A method for managing a workflow for an industrial application, comprising: providing a guide device configured to be communicatively coupled to a tool configured to be used on a workpiece; obtaining identification data associated with the workpiece used in the industrial application; obtaining industrial application status data related to at least one status of the industrial application; Obtain workpiece status data; operating the tool on the workpiece; Obtain tool operation data; uploading at least one of the identification data, the industrial application status data, and the tool operation data to a service system via the guiding device; as well as The industrial application status data is verified.

2. The method according to claim 1, wherein: Obtaining industrial application status data related to at least one status of the industrial application includes: obtaining first industrial application status data related to the status of the industrial application prior to operation of the tool; obtaining second industrial application status data related to the status of the industrial application after operation of the tool; and At least one of the first industrial application status data and the second industrial application status data is uploaded to the service system.

3. The method according to claim 2, wherein: The second industrial application status data is based at least in part on the tool operation data.

4. The method according to claim 1, further comprising: obtaining first workpiece state data corresponding to a state of the workpiece before the tool operates; obtaining second workpiece state data corresponding to a state of the workpiece after the tool is operated; and At least one of the first workpiece status data and the second workpiece status data is uploaded to the service system.

5. The method according to claim 4, wherein: The second workpiece state data is based at least in part on the tool operation data.

6. The method according to claim 1, wherein: The industrial application status data is obtained through a set of requirements verified by an end user.

7. The method according to claim 1, wherein: The tool operation data is obtained from sensors configured to monitor operation of the tool on the workpiece.

8. The method according to claim 1, wherein: Verifying the industrial application status data includes: marking the workpiece for inspection in response to determining that an error may have occurred in operation of the tool; performing a quality inspection on the workpiece; and The workpiece is released from inspection.

9. The method according to claim 1, wherein: The service system analyzes the data it receives and provides analysis information to a user, the analysis information including a data model of the artifact based at least on the industrial application status data.

10. The method according to claim 9, wherein: Verifying the industrial application status data includes examining the analytical information.

11. The method according to claim 1, wherein: Uploading to the service system via the guiding device also includes: transmitting the industrial application status data from a client installed on the guiding device to a local client communicatively connected to the client; transmitting the industrial application status data from the local client to a server communicatively connected to the local client, the server hosting a database configured to store the industrial application status information; and The industrial application status data is transmitted from the server to the service system, and the service system is configured to perform an operation on the industrial application status data.

12. The method according to claim 11, wherein: The service system is configured to perform operations on the industrial application status data including: Data analysis; and A data model of the industrial application associated with the industrial application status data is constructed.

13. The method according to claim 1, wherein: The guiding device is further configured to provide a workflow instruction to the end user, wherein the instruction indicates to the end user at least one of the following: the workpiece on which the tool is operated; when to collect the industrial application status data; and When to collect said tool operation data.

14. The method according to claim 13, wherein: Providing workflow instructions to the end user causes the directing device to update information displayed to the end user.

15. A non-transitory computer readable medium having embodied thereon a sequence of computer executable instructions for managing a workflow of an industrial application, the sequence of computer readable instructions comprising instructions for instructing at least one processor to: providing workflow instructions to a first user; associating identification data with an artifact used in said industrial application; associating the industrial application state data with one of a first industrial application state corresponding to a state of the industrial application before a tool is operated on the workpiece and a second industrial application state corresponding to a state of the industrial application after the tool is operated on the workpiece; associating workpiece status data related to the workpiece with the identification data; updating at least the second industrial application status data based on tool operation data associated with operation of the tool on the workpiece; as well as At least one of the identification data, the first industrial application status data, the second industrial application status data, and the workpiece status data is uploaded to a service system.

16. The non-transitory computer readable medium of claim 15, wherein the workflow instructions further comprise one or more of: selecting the appropriate tool to be used on the workpiece; recording the identification data associated with the workpiece; Recording the industrial application status data; Recording the workpiece status data; as well as Working on the workpiece is stopped prior to releasing a retainer associated with the workpiece.

17. The non-transitory computer-readable medium of claim 16, wherein the instructions further direct the processor to record completion of the specified workflow instruction in response to the first user indicating completion of the specified workflow instruction.

18. The non-transitory computer readable medium of claim 15, the instructions further instructing the at least one processor to instruct the service system to: providing the data to a second user; Performing data analysis on the data, wherein the data analysis includes constructing a data model of the artifact; placing the retainer on the workpiece in response to receiving an instruction to place the retainer on the workpiece; and The retainer is released on the workpiece in response to receiving an instruction to release the retainer on the workpiece.

19. The non-transitory computer readable medium of claim 18, wherein: The data includes at least one of the industrial application status data, the workpiece status data, and the tool operation data.

20. The non-transitory computer readable medium of claim 18, wherein: The second user provides instructions to place the retainer on the workpiece and to release the retainer on the workpiece.

21. The non-transitory computer-readable medium of claim 18, the instructions further instructing the at least one processor to instruct the service system to provide the data analysis to the second user.

22. The non-transitory computer readable medium of claim 18, the instructions further instructing the at least one processor to change the workflow instructions in response to input from the second user.

23. A system for managing a workflow of an industrial application, the system comprising: at least one sensor; The guiding device is constructed as follows: providing instructions to a user, the instructions indicating an action to be performed by the user; receiving from the at least one sensor at least one of tool operation data, industrial application status data, and workpiece status data obtained in response to operation of the tool; and providing at least one of the tool operation data, the industrial application status data, and the workpiece status data to a service system; as well as The service system is constructed as follows: receiving at least one of the tool operation data, the industrial application status data, and the workpiece status data; performing data analysis on the received data, including generating a data model associated with the artifact; placing a retaining member on the workpiece; releasing the retaining member from the workpiece; as well as Review the data received.

24. The system of claim 23, wherein: The tool operation data is associated with the operation of the tool and is received by the guidance device from the at least one sensor in communication with the guidance device, the at least one sensor being configured to monitor the operation of the tool to generate the tool operation data.

25. The system according to claim 22 further includes a local client, which is constructed to communicate with the guidance device and the service system, the guidance device provides at least one of the tool operation data, the industrial application status data and the workpiece status data to the local client, and the local client provides at least one of the tool operation data, the industrial application status data and the workpiece status data to the service system.

26. The system of claim 24, wherein: The local client is further configured to provide updated data to the boot device in response to receiving at least one of the following data: The industrial application status data, the workpiece status data, said tool operation data, data instructing placement of the holder on the workpiece, and Data indicative of releasing the holder from the workpiece.

27. The system of claim 22, wherein: The industrial application status data includes first industrial application status data and second industrial application status data, the first industrial application status data corresponding to the status of the industrial application before the tool operates on the workpiece, and the second industrial application status data corresponding to the status of the industrial application after the tool operates on the workpiece.

Images