Customized instruction flow chart generation and modification system
The system addresses the challenge of varying user experience levels and non-linear task flow by generating customizable flowcharts that adapt detail levels and track progress, improving efficiency and clarity in maintenance tasks.
Patent Information
- Application Number
- JP2022082487
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-07-02
- Filing Date
- 2022-05-19
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2042-05-19
AI Technical Summary
Existing systems for communicating maintenance instructions to technicians face challenges in managing non-linear task flowcharts, difficulty in tracking progress, and providing tailored instructions for technicians with varying experience levels, leading to inefficiencies and confusion during task completion.
A system and method that generates customizable flowcharts or decision trees, adjusting the level of detail based on user experience and device characteristics, allowing both experts and novices to follow the same flowchart while hiding or exposing additional information as needed, and enabling seamless continuation of tasks across shifts.
Enables efficient task completion by providing appropriate levels of detail to users, reducing the need for multiple versions of instructions, and ensuring clear progress tracking, thus enhancing productivity and reducing confusion.
Smart Images

Figure 0007595614000001 
Figure 0007595614000002 
Figure 0007595614000003
Abstract
Description
[Technical field]
[0001] The subject matter described herein relates to systems and methods for generating and communicating instruction flowcharts for performing tasks on an object (eg, equipment). [Background technology]
[0002] Technology Considerations Instructions to correct or diagnose equipment problems are sometimes called "prescriptions" or "Rx." Some of these well-known instructions are created as a list of tasks to be performed in sequence. The prescriptions can be communicated electronically to maintenance technicians and craftsmen as a list of tasks to be performed on the equipment. The prescriptions can be delivered electronically (e.g., email) and delivered as a list of tasks that can be printed at the time of use or displayed on an online portal.
[0003] Often, when a technician or craftsman is fulfilling a prescription, they may need to stop for some reason and resume later. Sometimes, the technician or craftsman fulfilling a prescription is not able to finish before the end of their shift and needs to communicate where they left off to the next technician or craftsman who will take over on the next shift.
[0004] When a prescription is laid out as a list of sequential tasks, a technician or craftsman can easily see how much progress he or she has made in performing the prescription tasks. However, if the tasks in the prescription are not performed (e.g., not executed) in sequence, it may not be easy or clear for the technician or craftsman to determine where he or she left off. This may be especially true for flowchart prescriptions that do not have to follow a linear path to completion. A person taking over a partially completed prescription may not know or be able to determine what tasks have been completed, what the task completion order is (e.g., what path through the flowchart was taken), etc. Additionally, when a prescription is provided digitally, it may be difficult for a person to add notes or annotations to completed tasks.
[0005] A prescription may also include detailed instructions for performing the tasks outlined in the prescription. Personnel performing the tasks may have a variety of different amounts of experience, training, education, etc. More experienced and / or more educated personnel may not need as much detail as less experienced or less educated personnel on how to complete a task. For example, expert technicians and craftsmen want to perform the prescription at a high level. These personnel are usually familiar with the prescription, or the failure modes targeted by the prescription, and do not need a lot of additional detail to complete the tasks within the prescription. These personnel may need simple or minimal instructions, if any, because they know how to address the problem at hand and may not want the structure and content of the prescription to get in their way and slow them down.
[0006] On the other hand, novice technicians and craftsmen (or at least those who are not familiar with the prescription or its targeted failure mode) may want more information available. These personnel may want to have more guidance when working on problems or equipment with which they are less familiar. These personnel may want a more detailed set of instructions for implementing the prescription, with additional documentation available as needed. However, creating multiple versions of a complex prescription, with each version tailored to different technicians and craftsmen with different experience and / or education levels, is an approach that is too timely, labor-intensive, and costly for many prescriptions.
[0007] Short Description In one embodiment, a method (e.g., for tailoring or customizing a single prescription for presentation to different users to complete tasks on a device) is provided. The method includes obtaining a prescription that represents a flow chart or decision tree for performing a main set of tasks on the device. One or more of the tasks include a subset of subtasks. The method also includes determining a person characteristic of a person performing the tasks on the device, a device identification, a device configuration, a first history of use and / or performed past tasks on the device, a second history of use and / or performed past tasks on other devices of the same model as the device, and / or sensor data of the device. The method also includes configuring the prescription based on the person characteristic, the device identification, the device configuration, the first history, the second history, and / or the sensor data. The set of instructions is configured by publishing at least a first subset of the subtasks and / or privately publishing at least a second subset of the subtasks. The method also includes communicating the configured prescription to one or more people for performing the tasks in the prescription on the device.
[0008] Also provided is a system (e.g., for tailoring or customizing a single prescription for presentation to different users to complete tasks on a device). The system includes a controller (e.g., a user controller and / or a system controller) configured to obtain a prescription representing a flow chart or decision tree for performing a main set of tasks on the device. One or more of the tasks include a subset of subtasks. The controller is configured to determine one or more of: a location of the device, a person characteristic of one or more people performing tasks on the device, a device identification, a device configuration, a first history of use and / or performed past tasks on the device, a second history of use and / or performed past tasks on other devices of the same model as the device, and / or sensor data of the device. The controller is also configured to instruct the input and output devices to display the prescription based on one or more of the location, person characteristic, device identification, device configuration, the first history, the second history, and / or the sensor data. The set of instructions is configured by one or more of: publishing at least a first subset of the subtasks and / or hiding at least a second subset of the subtasks.
[0009] Also provided is another method (e.g., for tailoring or customizing a single prescription for presentation to different users to complete tasks on a device). The method includes obtaining a prescription that represents a flow chart or decision tree for performing a main set of tasks on the device, determining one or more characteristics of a user of the device or prescription, and tailoring (e.g., customizing) the content of the prescription displayed to the user while performing at least some of the tasks on the device based on the one or more characteristics. The content of the prescription is adjusted by hiding one or more of the tasks that are not applicable to the device from display to the user. This can be done without removing or adding any data or information to the prescription. In other words, the content of the prescription can be adjusted without changing the information contained in the prescription. Instead, the prescription can be adjusted by changing what information is automatically and / or initially displayed to the user. The method also includes communicating the adjusted prescription to the user for performing the tasks in the prescription on the device. [Brief description of the drawings]
[0010] The subject matter of the invention can be understood from reading the following description of non-limiting embodiments with reference to the accompanying drawings, in which:
[0011] [Figure 1] 1 illustrates one embodiment of a customized instruction flowchart generation and modification system. [Figure 2A] FIG. 1 illustrates one example of a graphical user interface (GUI) that may be presented on a user I / O device for viewing, expanding or collapsing, editing, or annotating one or more of the prescriptions. [Figure 2B] FIG. 1 illustrates one example of a graphical user interface (GUI) that may be presented on a user I / O device for viewing, expanding or collapsing, editing, or annotating one or more of the prescriptions. [Diagram 3] 2C shows another embodiment of the prescription shown in FIG. 2A and FIG. 2B with the nodes deployed. [Figure 4] 4 illustrates an alternative embodiment of the portion of the GUI shown in FIG. 3. [Diagram 5] 2C illustrates another embodiment of a portion of the GUI shown in FIGS. 2A and 2B. [Figure 6] 1 illustrates a flowchart of one embodiment of a method for creating, submitting, and / or using a prescription to perform an operation on a device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] Embodiments of the subject matter described herein relate to systems and methods for customizing, generating, and / or modifying instruction flowcharts or process maps. These systems and methods can be used to generate flowcharts and communicate the flowcharts to personnel to complete tasks in the flowcharts. The personnel can be humans performing the tasks in the flowcharts, but can optionally include automated equipment (such as robots) performing the tasks in the flowcharts. At least one technical effect of the subject matter described herein is the diagnosis or repair of equipment using flowcharts generated and / or customized by the systems and methods. For example, the at least one technical effect can involve changing the state of equipment (e.g., engines, brakes, turbines, electrical systems, etc.) from a non-functional state (or a state in which the equipment is operating but with reduced functionality) to a functional state (or an improved state in which the equipment is operating with increased functionality).
[0013] As one example, the system and method can create prescriptions that include flowcharts and / or decision trees that include information targeted to experts and novices alike within the same prescription. The prescription can be displayed by the system and method to allow both experts and novices to view and implement the same prescription. An expert technician / craftsman can view tasks with instructions written at a high level, and a novice can choose to view more information, e.g., tasks written for a lower level of understanding. Only a single version of the prescription can be created and maintained, thereby reducing or avoiding the effort, cost, and time involved in creating different prescriptions for different experience and / or education levels. Only a single set of tasks can be created within a prescription. Tasks within a prescription can have both simple and detailed task content. A person can choose to view the simplified content, but can also view the detailed content if desired. Additional documentation (e.g., images, text, videos, etc.) can be attached to the task by the system and method. A person can choose to review or not review the additional documentation based on their personal need for additional information.
[0014] The system and method can create a prescription by defining a set of subtasks for a complex task. The subtasks can be organized as smaller flowcharts or decision trees nested within a larger flowchart or decision tree of the overall prescription. The subtask flows can be used to break down the task into more detail. The beginning and end of the subtask flows can be marked with explicit "start" and "end" subtask nodes to clearly define where the subtask begins to be performed and where the subtask flow ends. Each subtask can provide more information to a novice or less experienced user, or to an experienced user who requires additional information, detail, or depth.
[0015] When displayed, the subtask flow of a task can be hidden until requested by the user. Within a flowchart or decision tree view, a higher level task can be clicked to expand the task and display the subtasks of the higher level task (organized as a decision tree). In one embodiment, subtasks within a higher level task are not visible unless or until a node representing the higher level task is selected (e.g., by a user selecting the node using a user I / O device). Once expanded, the subtask view can be collapsed again to hide the subtasks and display only the higher level task. Once a higher level task is expanded and the subtasks are displayed, personnel can be automatically taken to a node in the subtask flow that is marked as start. At the subtask level, technicians and craftsmen can perform the subtask just as they would perform a task (e.g., personnel can view explanatory content and attached images, view additional documentation if provided, etc.). If the task is a decision point, personnel can answer questions (i.e., choose a path forward) and mark the task complete.
[0016] The practitioner is then automatically taken to the appropriate next task in the subtask flow (e.g., by the system or method changing the display of the prescription). Once the end of the subtask flow is reached (e.g., upon reaching a node that marks the end of the subtask flow), the system and method can automatically collapse the higher level task, hide the subtask flow, and return to displaying the top level task to the user. The user can then answer the prescription's questions (e.g., was the task completed?, what were the sensor readings or measurements?, etc.), complete the higher level task, and proceed to the appropriate next task in the prescription's flowchart or decision tree. The collapsed higher level task can be displayed as a node in the flowchart or decision tree, with a summary of the contents of the higher level task displayed within the node.
[0017] An expert user can choose to view and perform a higher level task (given less instruction detail), while a novice user can choose to work at a subtask level where more detailed instructions can be given and more supporting documentation can be made available. The end user can choose for themselves whether or not to see more detail. This helps to keep the details hidden and out of the way for the expert user, but leaves the details available if the user decides to get more information to perform the task at hand. Both expert and novice users follow the same basic flowchart or decision tree flow through the prescription. The user can choose to perform several more subtask steps, but ultimately the same task is performed.
[0018] The system may know the user with whom it is interacting, based on user input or selection, based on user identification, based on a user tag or identification device, or the system may automatically determine. In one embodiment, the inventive system automatically determines the skill or experience level of the user. This may be done, for example, by checking a table or equivalent database with information about the user, or by checking the history of user activity with the system. For example, if the user has executed the prescription before, the system may assign the user a respective skill level. If the user has executed the prescription at hand many times before, the system may determine that the user is a skilled and experienced user. If there is no history or user skill table available, the system may assume that the user has a basic set of skills or is unskilled. Other factors may be considered for the automatic assignment of skill levels (which may be overridden by the user, as disclosed herein). If the user has executed the prescription many times, but the equipment has been upgraded to a new model, or a warning has been attached to the part or component affected by the prescription, the system may do one or more of flagging the change, alerting the user, or reverting to a basic set of skill levels. In one instance, the portion of the prescription affected by the flagged change is set to a larger and more expansive instruction set, while the remaining portion of the prescription that is not unchanged remains in a condensed state (for experienced users). The system may further consider the user's success rate in completing the prescription, the time it takes the user to complete the prescription, the user's performance on related but different prescriptions, the user's performance relative to other users' performance on the same or similar repairs, or the performance after repair of the device relative to past prescription maintenance by the user.
[0019] Another feature is that once a user is identified and their skill level determined, the system can reconstruct the prescription in the user's preferred language. Not only can text be translated, but video and audio files can be selected that match the user profile. Disability accessories can be associated with user preferences, so that, for example, larger print can be used. And the device from which the user accesses the system can affect the presentation, so that a user with a tablet receives a different user interface than one on a smaller smartphone or smart glasses.
[0020] FIG. 1 illustrates one embodiment of a customized instruction flow chart generation and modification system 100. The system can be used to create, modify, and present prescriptions for inspecting, repairing, maintaining, etc., equipment 102. The equipment can represent one or more motorized systems, such as a vehicle, an engine, a battery system, an electric circuit, a turbine, a motor, or one or more non-motorized systems, such as a resistive brake grid, a wheel, etc. The system 100 includes a system controller 104 having and / or representing hardware circuitry connected with one or more processors (e.g., field programmable gate arrays, integrated circuits, microprocessors, etc.) that perform the operations described herein in association with the system controller. The system also includes one or more input and / or output devices 106 ("I / O devices" in FIG. 1) that receive inputs and / or provide outputs. The I / O devices can represent touch screens, other electronic displays, keyboards, microphones, styluses, etc. The I / O devices can be used to create and / or review prescriptions described herein.
[0021] The system also includes one or more computer-readable storage devices or memories 108. The memory shown in FIG. 1 may represent one or more databases, hard drives, servers, etc. that may store different prescriptions 110 for different types of equipment (e.g., different makes and / or models). The memory may be permanent data storage in one embodiment. Instead of having multiple different prescriptions for the same equipment or equipment part (different prescriptions containing different amounts of information for personnel performing tasks in the prescription), the system may store a single prescription for each different type of equipment, piece of equipment, etc.
[0022] The system controller can communicate prescriptions for equipment inspection, repair, and / or maintenance to the user controller 112 via one or more computer networks 114. The network can represent all or a portion of the Internet, one or more local area networks, one or more wide area networks, and / or the like. The user controller can represent a hardware circuit having and / or connected with one or more processors (e.g., field programmable gate arrays, integrated circuits, microprocessors, etc.) that perform the operations described herein in association with the user controller. One or more additional I / O devices 116 can be operatively coupled to the user controller to enable a representative to provide input and / or receive output via the user I / O devices 116. For example, a representative can provide input to select a prescription, view details of a prescription (and optionally expand or collapse the prescription for more or less information as described herein), add a note to the prescription, etc. The user controller can communicate with the system controller to retrieve a prescription, expand or collapse a prescription, etc. based on input received from the representative. Optionally, one or more of the user I / O devices may be an output device.
[0023] The system may include one or more automated devices 118. An automated device may represent an apparatus or system that automatically performs some or all of the actions in a prescription at an appliance. For example, a suitable automated device may represent one or more robots or robotic systems that perform the actions in a prescription.
[0024] The system may optionally include one or more sensors 120 capable of measuring characteristics of the device. The sensors may measure the temperature of the device, measure current, take pictures or videos, etc., before, during, and / or after executing the prescription on the device. These measured characteristics may be used to make decisions within a flow chart or decision tree within the prescription, to verify that a task was completed correctly, etc. The sensors may communicate the measured characteristics to a user controller, which may use the received measured characteristics to determine whether a prescription task is or has been completed. The system may record the time of each step of the repair or maintenance process and may compare one user's efficiency with other users performing the same task or with a baseline established by the user's past efforts. This comparison may be used to automatically show or hide certain tasks during the execution of tasks within the same prescription or during the execution of tasks within subsequent prescriptions executed by the same user. For example, when a user takes less time to complete certain tasks, the user becomes more efficient at those tasks. As the user becomes more efficient at completing tasks, less detail of those tasks may be displayed to the user (or some tasks may be hidden from view) on the same or subsequent prescriptions.
[0025] The user controller can control the user I / O device 116 to display the contents of the prescription, such as images, graphics, videos, text, and user interface controls (menus, buttons, scroll bars, check boxes, text entry fields, etc.). The user I / O device can include a pointing device (e.g., a stylus, electronic mouse, touch screen, etc.) that allows the user to select entities displayed on the user I / O device, as well as to select and drag entities to reposition entities on the display of the user I / O device. The user I / O device can display a single or multiple prescriptions as one or more flowcharts or decision trees. The flowcharts or decision trees can include summaries of information for each task in the prescription. These summaries can be represented by nodes in the flowchart or decision tree, and can include information such as (but not limited to) a sequence number used as a shorthand to identify the task, the title of the prescription, a short description of the prescription, questions for the user to provide a response, and so forth.
[0026] 2A and 2B show one example of a GUI 200 that may be presented on a user I / O device to view, expand or collapse, edit, or annotate one or more of a prescription. The GUI 200 shown in FIG. 2 shows a portion of a flowchart or decision tree 202 that represents tasks to be performed within a prescription. The flowchart or decision tree includes nodes 204 (e.g., nodes 204A-C) that are coupled to one another by links 206. The location and orientation of the nodes and links visually indicate to the person fulfilling the prescription the order or sequence of tasks to be performed. Some nodes 204A may indicate the start or end of an entire prescription or a nested flowchart within a larger flowchart. Other nodes 204B, 204C may include text, images, graphics, etc. to indicate what actions should be performed before the prescription progresses past or beyond the corresponding node. The prescription may display different nodes in different ways to indicate whether a task associated with the node (or a nested flowchart contained within the node) has been completed, is not yet completed, was skipped, could not be completed, has been selected to reveal more detail, etc. For example, nodes may be presented in different colors, with different borders, with different types of text, etc.
[0027] In the illustrated example of FIG. 2A, the first node below or after the start node is selected by the practitioner using a user I / O device to select the node. The user controller can detect the user selection of this node and direct the display of the user I / O device to present additional details 208 of the task in the prescription at the selected node. The additional details can include images, videos, text, drawings, etc. to assist or guide the practitioner through the steps required to complete the associated task. In one embodiment, the additional details can include a document or a link to a document that can be downloaded and viewed. Selecting another node in the prescription will cause the user controller to direct the user I / O device to display other details of another task. As the user progresses through the prescription, selecting different nodes will cause different details to be displayed.
[0028] The prescription may cause the user controller to instruct the user I / O device to display navigation icons 210. These navigation icons may be selected to zoom in or out of the flowchart, return to the start of the flowchart or to a previous node, collapse the portion of the flowchart that includes the prescription subtask, expand the prescription subtask, etc. One or more of the nodes may include an expand icon 212 that may be selected to expand a nested flowchart contained within the corresponding node, as described herein.
[0029] The system controller and / or user controller can modify the prescription or how the prescription is displayed based on the output from the sensor. For example, the system controller and / or user controller can receive the output from the sensor and determine that the sensor output is abnormal or outside of a specified range. If the sensor output is abnormal or outside of a specified range, the system controller and / or user controller can automatically expand the node to expose one or more subtasks that need to be completed, change a task associated with the node from an optional task to a required task (that must be completed before progress on the prescription can proceed or that must be completed before the prescription is completed), etc.
[0030] The prescription flow chart may include one or more decision nodes 204C. At a decision node, the progression or advancement of the prescription to a subsequent node depends on the outcome of a task performed at the decision node. For example, a decision node may require input from a user or a sensor. Based on the input, the progression of the flow chart may proceed to a different node 204B.
[0031] Also, as shown in FIG. 2B, user selection of a node can reveal additional information on the right side of the GUI. This additional information can include images and / or videos 214 to guide the practitioner through the tasks associated with the selected node. The user can add notes to the prescription (as shown on the right side of FIG. 2B) using the user I / O device. These notes can indicate problems encountered, anomalies the practitioner noticed, sensor outputs, test results, etc.
[0032] As discussed above, an expand icon may be selected to expand a node into a larger single node, two or more nodes that do not include a decision node, and / or two or more nodes that include a decision node. FIG. 3 illustrates another example of the prescription shown in FIGS. 2A and 2B with node 300 expanded. Node 300 may be referred to as a higher level node. A user I / O device may be used to select a node (resolve "4 intermittent wires..." in FIG. 2B). As shown in FIG. 3, when this selected node is expanded, it contains three nested nodes 302. These nested nodes may represent additional tasks, instructions, images, videos, etc. that may be presented to a user on a user I / O device and require completion before proceeding through the nested nodes. The nested nodes may be referred to as subnodes, and the tasks within the nested nodes may be subtasks. In the illustrated embodiment, the three nested nodes represent a subset of the tasks within the prescription.
[0033] A prescription may be created by the system controller with all of the nested tasks or nodes, text, images, videos, etc. However, before sending the prescription to the user controller, the system controller may modify which nodes to expand (to display nested tasks or nodes), how much information (text, images, videos, etc.) to present when one or more of the nodes are selected, etc., based on one or more characteristics of the personnel performing the tasks in the prescription. For example, a user performing a task in the prescription may provide identification information, such as a login and password combination, an identification number or an alphanumeric string, to the system controller via a user I / O device and the user controller. The system controller may store (e.g., in memory) different experience levels, education levels, etc., along with different identities of users. Depending on the identification information provided, the system controller may determine how experienced and / or educated the personnel attempting to perform some or all of the prescription is.
[0034] The system controller may then modify the prescription by collapsing some expandable nodes for more experienced and / or more educated personnel, by expanding some expandable nodes for other less experienced and / or less educated personnel, by expanding the amount of text, images, videos, etc. that is presented when one or more nodes are selected for less experienced and / or less educated personnel, by collapsing or reducing the amount of text, images, videos, etc. that is presented when one or more nodes are selected for more experienced and / or more educated personnel, etc. The system controller may make these changes without deleting data from the prescription, but instead by collapsing or otherwise obscuring from view details that are not necessary for some personnel, or expanding or otherwise displaying details that may be required by other personnel.
[0035] The system controller can make these changes without altering the contents of the prescription. For example, the size of the electronic software data file or files containing the prescription may remain the same when the prescription is provided to the user controller and displayed on the user I / O device, regardless of which nodes are collapsed or expanded, what information is or is not displayed in additional detail, etc. This may eliminate the need to create many different prescriptions with different amounts or levels of detail for representatives with different experience and / or education levels. Optionally, the user controller can change which nodes and / or additional detail are expanded or collapsed based on the representative's experience and / or education.
[0036] As one example, different personnel may have previously completed the same prescription or node task several times. The number of completions of the prescription and / or task may be stored in memory and associated with the personnel's identifier. Once a personnel has completed the same prescription or node task at least a threshold number of times, the system controller and / or user controller may change how the prescription is displayed. Personnel who have completed the prescription or task more than the threshold number of times may see fewer nodes in expanded mode and / or less information in the additional information section of the GUI, while other personnel who have not completed the prescription or task more than the threshold number of times may see more nodes in expanded mode and / or more information in the additional information section of the GUI.
[0037] As another example, different people may have different quantified ratings stored in memory (described below). These ratings may be set or established manually and / or may change based on or based on how many times a user completes a prescription. A user who completes the same prescription more times may be associated with a higher rating, while a user who completes the same prescription less times may be associated with a lower rating (relative to users with higher ratings). A controller (e.g., a system controller or a user controller described below) may display more details of the prescription based on the rating (more instructions are displayed for lower ratings and fewer instructions are displayed for higher ratings) and, optionally, may request a consent signature or approval from a user based on the rating. For example, a user with a rating below a threshold rating may not be able to proceed or pass through one or more tasks or decisions in the prescription unless or until another user with a higher rating (e.g., higher than the threshold rating) reviews and approves the work completed by the user with the lower rating. Users with ratings higher than the threshold rating may not have this required consent signature or approval, but instead, these users may be able to proceed with the prescription without pausing or waiting for the consent signature or approval.
[0038] The display of the prescription can be altered based on the characteristics of the device performing the tasks in the prescription. The user controller can communicate the device's identification (e.g., serial number or other unique number, make and model identification, etc.) to the system controller. The system controller (or user controller) can reference a memory that can store the level or amount of information to be displayed based on the device identification.
[0039] The system controller or user controller may tailor the contents of the prescription based on, for example, the characteristics of the device. That is, the system controller or user controller can hide (e.g., from display) tasks that are not applicable to the device (e.g., tasks that cannot be performed on the device, tasks that should not be performed on the device, etc.). The system controller or user controller can determine which tasks of the prescription to hide from the display based on the identity of the owner of the device, the identity of the device fleet in which the device is included, the type of device (e.g., engine vs. alternator, hybrid vs. liquid fuel vehicle, etc.), the model of the device (e.g., model number), the configuration of the device (e.g., whether the device is configured to operate as a traction motor to propel a vehicle or as a motor to perform tasks other than propulsion, etc.).
[0040] The identification or information provided to the controller about the equipment can optionally indicate what tasks or prescriptions have been previously performed on the equipment. For example, if the equipment has been recently tested, inspected, or maintained, one or more operations performed during the recent test, inspection, or maintenance may not need to be performed again, or less detail may need to be provided to the personnel. The system controller or user controller can then collapse the amount of information presented in the prescription (e.g., by collapsing a node, displaying less information in the additional details section, etc.). As another example, if it has been a significant amount of time since the equipment was tested, inspected, or maintained, more information may need to be presented to the personnel to ensure that no steps are missed. The system controller or user controller can then expand the amount of information presented in the prescription (e.g., by expanding a node, displaying more information in the additional details section, etc.).
[0041] As another example, the identification may indicate what tasks or prescriptions have been previously performed on another piece of equipment of the same make and / or model of equipment. For example, if the same user has performed the same task or prescription on the same make or model of equipment, less detail of the nodes and tasks may need to be displayed to the user. However, if the same user has not performed the same task or prescription on the same make or model of equipment, more detail of the nodes and tasks may need to be displayed to the user.
[0042] The system controller or user controller may skip nodes that do not apply to the equipment on which the prescription is being used. For example, the same prescription may be used to inspect the same equipment used in different power systems (e.g., different vehicles). Some tasks may not need to be performed or may be inappropriate for some uses of the equipment. Based on the characteristics of the equipment, the system controller and / or user controller may determine which tasks, if any, do not need to be performed. Nodes representing these tasks may be presented differently (e.g., grayed out), hidden from view, or otherwise indicated as not necessary for completion of the prescription.
[0043] The display of the prescription may be altered based on an identification of the user, an identification of the device, an identification of an entity (e.g., a company, a business, a government agency, etc.), etc. The user controller may communicate the identification to the system controller. The system controller may reference a memory in which preferences associated with the provided identification may be stored. For example, some customers may prefer that metric units be used on their prescriptions instead of imperial units, some users may prefer that more or less detail be displayed, etc. The system controller may alter how the prescription is displayed or instruct the user controller to alter how the prescription is displayed based on the preferences associated with the identification, as described herein.
[0044] The display of the prescription can optionally be changed based on the location of the device. The user controller can communicate the location of the device to the system controller, or the location of the device can be known to the system controller, such as from output from a sensor (e.g., a global navigation satellite system receiver). The system controller and / or user controller can change how the prescription is displayed based on the location of the device. For example, the units of measurement displayed can be changed from English to metric (or vice versa) based on the country in which the device is located. Alternatively, units of measurement less commonly used in the country can be dimmed from view, while units of measurement more frequently used are displayed.
[0045] FIG. 4 illustrates another embodiment of a portion of the GUI 200 shown in FIG. 3. An input 400 can be provided to a user controller from a user I / O device or an automated device. The input can indicate that a task has been completed, what repairs have been made, etc. The input can be provided to the additional details section of the GUI by a user using a user I / O device, by a user controller receiving output from a sensor, and / or by a user controller receiving output from an automated device. The input can be stored in memory with the prescription, or can be stored separately from but associated with the prescription (e.g., in memory, such as by using a file pointer, library call, or other data file association). The user controller can then advance the prescription's progress to the next node along the flowchart, such as by automatically changing the color of the next node and displaying details of that node in the additional details area of the GUI.
[0046] For example, the user controller and / or system controller can optionally change how different nodes, links, etc. in a prescription are displayed in response to tasks being completed, decisions at decision nodes being made, personnel adding notes or information to the prescription, etc. This can aid in communication between different personnel working on the prescription at the same or different times, and can reduce or eliminate confusion as to what tasks have been completed, what decisions have been made in the prescription, where other personnel stopped or stopped working in the prescription, etc.
[0047] The controller may display the current completion state of the prescription by visually distinguishing task nodes of completed tasks from other task nodes that are not completed. As one example, this may be accomplished by changing the color of the task nodes relative to the color used for nodes whose tasks are not marked as completed, changing the thickness of the border, etc. As another example, the controller may visually distinguish the path taken as the technician or craftsman answers questions and moves from task to task within the flowchart or decision tree of the prescription. For example, links connecting completed nodes may be displayed in different ways (different colors, different thicknesses, static vs. dynamically changing or flashing, etc.). As another example, the controller may visually mark the current task being viewed or worked on relative to other nodes by highlighting it, changing the color in which the corresponding task node is displayed, changing the thickness of the border of the node, etc.
[0048] Upon completing a task or subtask, the user controller can automatically change the display of the prescription flowchart or decision tree. For example, the display of the flowchart or decision tree can automatically pan and / or zoom to the next node (e.g., a task) along one or more links from the previous node. This can avoid confusion that would otherwise occur to personnel who would become lost in the flowchart or decision tree by having to go back to changing the display of the flowchart or decision tree every time a task or node is completed.
[0049] Providing input to a prescription can aid in the completion of a prescription when the prescription is performed by several different personnel and / or over an extended period of time (e.g., several work shifts, days, etc.). The user controller can change the color or other appearance of a node to indicate that the node is completed (e.g., by displaying the node in green), that a task within the node has been started to be completed but not yet completed (e.g., by displaying the node in yellow), that a task has been skipped (e.g., by displaying the node in blue), or that a task has not yet been started (e.g., by displaying the node in gray). This can aid the personnel in determining which nodes and tasks within the node still need to be completed. Upon resuming work on the prescription after a stop, the user controller can automatically pan and / or zoom the display of the flowchart or decision tree to the last node that was completed, the last node that is being worked on but not yet completed, or the next node following the last completed node. This can reduce delays in the personnel finding where to resume work on the prescription.
[0050] FIG. 5 illustrates another embodiment of a portion of the GUI 200 shown in FIG. 2A and FIG. 2B. As shown in FIG. 5, a user I / O device can be used to select a bookmark icon 500 and / or add other inputs 400 to the prescription. The bookmark icon can be selected and saved with the prescription (or in a data file associated with the prescription but not included in the prescription) to indicate where the practitioner stopped working on the prescription. For example, a node 204B that the practitioner has started working on but not completed and has one or more tasks associated with a bookmark can be displayed in a different color, with a different sized border, with different font text, with different sized text, etc., relative to the other nodes to indicate which node 204B was last worked on (as shown in FIG. 5).
[0051] The representative can use the sensors to add input such as photos, videos, drawings, typed text, etc. to inform other representatives or remind the same representative where the prescription's progress stopped (e.g., at the end of a shift or when a problem was encountered). The next representative who resumes work on the prescription can then easily find out which node was being worked on when work on the prescription stopped, and may optionally be able to read or otherwise obtain additional information from the representative who previously worked on the prescription.
[0052] The input provided by the practitioner to the prescription can be a variety of different types of input. For example, the practitioner can add one or more photos or videos as input using a sensor (e.g., a camera), a recording (of the device operating or the practitioner speaking) as input using a sensor (e.g., a microphone), a sensor output as input to the prescription, a document (the document itself or a link to the document) as input, etc.
[0053] The user controller can accept input from a user who is executing at least a portion of the prescription to mark or otherwise highlight a task or node in the prescription. This can be an aid to bring the task or node to the attention of the same or other personnel. The user controller can change how the node is displayed in response to that note being selected by the user for marking or highlighting. Different users can be associated with different colors or other methods to change how the node is displayed. The user controller can change the display of the marked node to call attention to the node. The user controller can optionally receive additional input from the user who marks the node or task. This input can be a note of an observation made by the user, a warning from the user, other items to investigate or inspect, etc., to remind the same user or to inform other users who are also working on the prescription. This can be an aid to prevent loss of information when the prescription is handed over between different personnel who are working on the prescription at different times. The user controller can receive input from the same or a different user that can stop highlighting or marking a node and can also delete any notes or other input provided by the user.
[0054] The system controller can record which personnel have completed different tasks, when the different tasks were completed, sensor readings associated with the different tasks, etc. This completion information can be saved upon completion of the prescription and later viewed for auditing or otherwise review, to determine which personnel to contact for a particular task, etc. For example, the user controller and / or the system controller can save data indicative of the current state of the prescription and the tasks within the prescription to be a permanent or persistent data store. This data can indicate which tasks have been completed, answers provided or obtained (e.g., from sensors) for decision nodes, which links extending from the decision nodes have been taken in the progress of completing the prescription, which tasks were being worked on when the most recent personnel stopped working on the prescription, etc. This data can be sent by the system controller and / or retrieved by the user controller to modify the display of the prescription to indicate what tasks have been completed, paths taken through the prescription, answers, etc. This can help the same or different personnel quickly and easily recognize where to resume working on the prescription.
[0055] Although one or more embodiments describe different people working on different parts of the same recipe at different times, optionally, two or more different people can work on the same recipe in unison or simultaneously. For example, one part of the recipe can be performed by a first person working on a first piece of equipment (e.g., the engine of a vehicle), while another different part of the recipe can be performed by a second person working on a second piece of equipment (e.g., the cooling system of the same vehicle), etc. The user controller and / or system controller can record the progress and inputs of the different people so that all people working on the same recipe, at the same time or at different times, are aware of the tasks completed by others and the results from those tasks.
[0056] In one embodiment, the automation device can execute one or more of the tasks in the node automatically and without operator intervention. For example, after a practitioner starts to execute a prescription, the automation device can execute one or more of the tasks automatically without the practitioner having to manually control the device to execute the tasks. This can result in some or all of the nodes in the prescription being completed automatically.
[0057] The system controller and system I / O devices can optionally be used by one or more persons to draft or create a prescription. The drafter can use the I / O devices to associate images and / or documents with tasks, upload external documents to be added as attachments to one or more of the tasks, and / or select one or more tasks and create a higher level task that encompasses the selected tasks as a subtaskflow or subset of the tasks. The system I / O devices can also be used to select tasks and draw links between tasks to indicate the flow and / or outcome of decisions within the prescription. The system I / O devices can enable a person to select one or more tasks (represented by one or more nodes) and drag them onto or into another node, thereby creating a subtaskflow or subset of the task. The system I / O devices can be used to add text, images, videos, or other information to the nodes for later viewing by the practitioner.
[0058] FIG. 6 illustrates a flow chart of one embodiment of a method 600 for creating, presenting, and / or using a prescription for performing operations on an equipment. The method may represent operations performed by one or more of the controllers described herein. In step 602, a prescription is obtained that includes tasks to be performed on the equipment. The prescription may be obtained from a computer memory through or via one or more networks. The prescription may be a single prescription for repairing, inspecting, or maintaining the equipment that includes information necessary for both novice and expert users in performing tasks on the equipment. In step 604, the level of experience and / or education of a person performing the tasks in the prescription is determined. The experience and / or education may be determined from identifying information about the person or based on other input provided by the person.
[0059] In step 606, the display of tasks in the prescription is modified or controlled based on the level of experience and / or education. As described above, for a person with a high level of experience and / or education, two or more nodes or tasks can be collapsed into fewer or a single node or task, while for a person with a lower level of experience and / or education, fewer or no nodes or tasks can be collapsed into fewer or a single node. The collapsed nodes can be expanded by user input to ensure that many different levels of experience and education can obtain more information about completing the prescription, as needed. In this way, a single prescription can be generated for the device, but the display of the prescription can be altered so that a more experienced and / or more educated user is not burdened with the details of the tasks that the user has knowledge and experience in completing, while a less experienced and / or less educated user is provided with more details of the tasks.
[0060] In step 608, the display of the tasks in the prescription is changed based on the progress of the prescription. As described above, when a task is completed, the color, border, text, or other appearance of the node representing the task may be changed. This may help to easily and quickly inform the user which nodes or tasks are being performed, which nodes or tasks are completed, and which nodes or tasks need to be completed. In step 610, a determination is made as to whether input from a person or a sensor has been received. A user performing a task in the prescription may provide input such as notes on observations, problems encountered, additional steps or actions performed, etc. Data output by a sensor may be provided before, during, and / or after the execution of one or more tasks to check the validity of the task, the success of the task, or other impact of the task. If user input and / or sensor output is obtained, the flow of the method may proceed to step 610, where the input and / or sensor output may be stored or saved with the node or task associated with the input and / or sensor output for later retrieval and review. If user input and / or sensor output has not been obtained, method flow may proceed to step 612.
[0061] In step 612, a determination is made as to whether there is a turnover or cessation of work being performed on or with the prescription. For example, a user may not be able to complete all of the tasks in the prescription. The user may stop working on the prescription (e.g., stop) and / or hand over work on the prescription to another use (e.g., turnover). If a stop or turnover occurs, the method flow may proceed towards step 614. Otherwise, work on the prescription may continue and the method flow may return to another operation, such as step 606. Alternatively, the method flow may end upon completion of the prescription.
[0062] At step 614, the user's progress through the prescription may be stored. For example, data may be stored in memory indicating tasks or nodes completed, decisions made at decision nodes, user inputs, sensor outputs, etc. This data may be retrieved later when work on the prescription is resumed by the same or another user. The display of the prescription may be altered to visually indicate where the previous user stopped working. A user resuming work on the prescription may see where to start working and may also review the previous user's notes, sensor outputs, etc., which may aid in further progress toward completion of the prescription. The method flow may return to another operation (e.g., step 606) or may end upon completion of the prescription.
[0063] In one embodiment, a method (e.g., for tailoring or customizing a single prescription for presentation to different users to complete tasks on a device) is provided. The method includes obtaining a prescription that represents a flow chart or decision tree for performing a main set of tasks on the device. One or more of the tasks include a subset of subtasks. The method also includes determining a person characteristic of a person performing the tasks on the device, a device identification, a device configuration, a first history of use and / or performed past tasks on the device, a second history of use and / or performed past tasks on other devices of the same model as the device, and / or sensor data of the device. The method also includes configuring the prescription based on the person characteristic, the device identification, the device configuration, the first history, the second history, and / or the sensor data. The set of instructions is configured by publishing at least a first subset of the subtasks and / or privately publishing at least a second subset of the subtasks. The method also includes communicating the configured prescription to one or more people for performing the tasks in the prescription on the device.
[0064] Optionally, configuring the prescription may include, in response to determining that one or more persons performing the tasks in the prescription have at least a threshold level of experience or education, making private at least a second subset of the subtasks by collapsing a display of at least a second subset of the subtasks into a single node in a flowchart or decision tree. Configuring the prescription may include, in response to determining that one or more persons performing the tasks in the prescription do not have at least a threshold level of experience or education, making public at least a first subset of the subtasks by expanding the at least a first subset of the subtasks into multiple nested nodes within a single node in a flowchart or decision tree. Configuring the prescription may include modifying a display of the prescription without deleting or adding data to the prescription.
[0065] The method may also optionally include receiving input from the person during performance of the tasks in the prescription to (a) expand a subset of the subtasks that are collapsed in the flowchart or decision tree display, and / or (b) collapse a subset of the subtasks that are expanded in the flowchart or decision tree display. At least one of the tasks may include a decision, and the method may also include modifying the flowchart or decision tree display to move to a subsequent one of the tasks that follows the decision based on an outcome of the decision.
[0066] The method may also include modifying the presentation of one or more of the nodes or links in the main set of tasks in the flowchart or decision tree in response to completion of at least one of the tasks, starting but not completing work on at least one of the tasks, data entry by the one or more persons while working on at least one of the tasks, and / or bookmarks added by the one or more persons in response to stopping work on the prescription. Configuring the presentation may include modifying units of measurement used in the tasks based on one or more of a user's identity or device location.
[0067] The method may also include storing data indicative of (a) completion of one or more of the tasks, (b) input provided by one or more persons, and / or (c) decisions made within a flowchart or decision tree in response to or in association with ceasing activity on the prescription, and in response to resuming activity on the prescription, retrieving the stored data and displaying the flowchart or decision tree based on the retrieved data.
[0068] Also provided is a system (e.g., for tailoring or customizing a single prescription for presentation to different users to complete tasks on a device). The system includes a controller (e.g., a user controller and / or a system controller) configured to obtain a prescription representing a flowchart or decision tree for performing a main set of tasks on the device. One or more of the tasks include a subset of subtasks. The controller is configured to determine one or more of: a location of the device, a person characteristic of one or more people performing tasks on the device, a device identification, a device configuration, a first history of use and / or performed past tasks on the device, a second history of use and / or performed past tasks on other devices of the same model as the device, and / or sensor data of the device. The controller is also configured to direct the input and output devices to display the prescription based on one or more of the location, person characteristic, device identification, device configuration, the first history, the second history, and / or the sensor data. The set of instructions is configured by one or more of: publishing at least a first subset of the subtasks and / or hiding at least a second subset of the subtasks.
[0069] Optionally, the controller may be configured to instruct the input and output devices to display the prescription by concealing at least a second subset of the subtasks by collapsing display of at least a second subset of the subtasks into a single node in a flowchart or decision tree in response to determining that one or more persons performing the tasks in the prescription have at least a threshold level of experience or education. The controller may be configured to instruct the input and output devices to display the prescription by disclosing at least a first subset of the subtasks by expanding at least a first subset of the subtasks into multiple nested nodes in a single node in a flowchart or decision tree in response to determining that one or more persons performing the tasks in the prescription do not have at least a threshold level of experience or education.
[0070] The controller can be configured to direct the input and output devices to modify the display of the prescription without removing or adding data to the prescription. The controller can be configured to receive input from one or more persons during performance of the tasks in the prescription to do one or more of: (a) expand a subset of the subtasks that are collapsed in the flowchart or decision tree display; or (b) collapse a subset of the subtasks that are expanded in the flowchart or decision tree display.
[0071] At least one of the tasks can include a decision, and the controller can be configured to change the display of the flowchart or decision tree to move to a subsequent one of the tasks following the decision based on an outcome of the decision. The controller can be configured to change the presentation of a node in the main set of tasks in the flowchart or decision tree in response to one or more of: completion of at least one of the tasks, starting but not completing work on at least one of the tasks, data entry by one or more persons while working on at least one of the tasks, or a bookmark added by one or more persons in response to ceasing work on the prescription.
[0072] The controller can be configured to modify the presentation of links between nodes in the main set of tasks in the flowchart or decision tree in response to completion of at least one of the tasks. The controller can store data indicative of one or more of (a) the completion of one or more of the tasks, (b) input provided by one or more persons, or (c) decisions made in the flowchart or decision tree in response to or in association with cessation of work on the prescription, and the controller is configured to direct the input and output devices to retrieve the stored data and to display the flowchart or decision tree based on the retrieved data in response to resuming work on the prescription.
[0073] Another method (e.g., for tailoring or customizing a single prescription for presentation to different users to complete tasks on a device) is also provided. The method includes obtaining a prescription that represents a flow chart or decision tree for performing a main set of tasks on the device, determining one or more characteristics of a user of the device or prescription, and tailoring (e.g., customizing) the content of the prescription displayed to the user while performing at least some of the tasks on the device based on the one or more characteristics of the device. The content of the prescription is adjusted by hiding one or more of the tasks that are not applicable to the device from display to the user. This can be done without any data or information being removed from or added to the prescription. In other words, the content of the prescription can be adjusted without changing the information contained in the prescription. Instead, the prescription can be adjusted by changing what information is automatically and / or initially displayed to the user. The method also includes communicating the adjusted prescription to the user for performing the tasks in the prescription on the device. Optionally, the prescription may be adjusted by hiding at least some of the tasks based on one or more of the equipment owner, the equipment fleet in which the equipment is included, the equipment type, the equipment model, or the equipment configuration.
[0074] As used herein, the terms "processor" and "computer" and related terms, such as "processing device", "computing device", and "controller", may not be limited to only those integrated circuits referred to in the art as computers, but may refer to microcontrollers, microcomputers, programmable logic controllers (PLCs), field programmable gate arrays, and application specific integrated circuits, as well as other programmable circuits. Suitable memory may include, for example, computer-readable media. Computer-readable media may be, for example, computer-readable non-volatile media such as random access memory (RAM), flash memory, and the like. The term "non-transitory computer-readable media" refers to tangible computer-based devices implemented for short-term and long-term storage of information, such as computer-readable instructions, data structures, program modules and sub-modules, or other data, within any device. Thus, the methods described herein may be coded as executable instructions embodied in tangible non-transitory computer-readable media, including, but not limited to, storage devices and / or memory devices. Such instructions, when executed by a processor, cause the processor to perform at least a portion of the methods described herein. As such, the term includes non-transitory computer storage devices, including but not limited to volatile and non-volatile media, tangible computer readable media, including but not limited to firmware, physical and virtual storage devices, removable and non-removable media such as CD-ROMs, DVDs, and other digital sources such as a network or the Internet.
[0075] The singular forms "a," "an," and "the" include plural references unless the context clearly indicates otherwise. "Optional" or "optionally" means that the subsequently described event or circumstance may or may not occur, and the description may include cases where the event occurs and does not occur. Approximation language used herein throughout this specification and claims may be applied to modify any quantitative expression that may be permissibly varied without causing a change in the basic function involved. Thus, values modified by terms such as "about," "substantially," and "approximately" or terms may not be limited to the exact value specified. In at least some cases, approximation language may correspond to the precision of an instrument for measuring the value. Throughout this specification and claims, unless the context or language indicates otherwise, range limitations may be combined and / or interchanged, and such ranges are specified and may include all subranges contained therein.
[0076] This written description uses examples to disclose embodiments, including the best mode, and to enable one of ordinary skill in the art to practice the embodiments, including making and using any device or system and performing any incorporated methods. The claims define the patentable scope of the disclosure, and include other examples that occur to those of ordinary skill in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that are substantially different from the literal language of the claims.
Claims
1. 1. A method comprising: obtaining a prescription representing a flow chart or decision tree for performing a main set of tasks on a device, one or more of the tasks including a subset of subtasks; determining an experience or education level of one or more individuals performing the task on the device using a controller that stores a history of the one or more individuals; automatically altering a display of the prescription in a graphical user interface (GUI) by at least one of exposing at least a first subset of the sub-tasks in response to the level of experience or education being below a threshold level and exposing at least a second subset of the sub-tasks in response to the level of experience or education being above the threshold level; automatically performing one or more of the tasks on the equipment using an automation device in response to the level of experience or education being below the threshold level; automatically displaying the prescription in the GUI to the one or more persons performing the task at the device; A method comprising:
2. 2. The method of claim 1, wherein automatically modifying the display of the prescription includes making the at least the second subset of the subtasks private by collapsing the display of the at least the second subset of the subtasks into a single node within the flowchart or the decision tree.
3. 2. The method of claim 1, wherein automatically modifying the display of the prescription comprises exposing the at least the first subset of the subtasks by expanding the at least the first subset of the subtasks into multiple nested nodes within a single node in the flowchart or decision tree.
4. 10. The method of claim 1, wherein automatically modifying the prescription display does not remove or add data to the prescription.
5. 2. The method of claim 1, further comprising receiving input from the one or more persons during performance of the tasks in the prescription to do one or more of: (a) expand the subset of the subtasks that are collapsed in the flowchart or decision tree representation; or (b) collapse the subset of the subtasks that are expanded in the flowchart or decision tree representation.
6. At least one of the tasks includes a decision; The method comprises: The method of claim 1 , further comprising modifying the display of the flowchart or decision tree to move to a subsequent one of the tasks following the decision based on an outcome of the decision. (a) completion of at least one of the tasks; (b) work on the at least one of the tasks has begun but not been completed; (c) data entry by the one or more persons while working on the at least one of the tasks; or (d) bookmarks added by the one or more persons in response to cessation of activity on the prescription; 2. The method of claim 1, further comprising modifying a presentation of one or more of the nodes or links in the main set of tasks in the flowchart or decision tree in response to one or more of the following:
8. The method of claim 1, further comprising the step of altering the display of the prescription by changing the units of measurement used in the task in response to the location of the device.
9. storing data indicative of one or more of: (a) completion of one or more of the tasks; (b) input provided by the one or more persons; or (c) decisions made within the flowchart or decision tree in response to or in connection with the cessation of activity on the prescription; retrieving the stored data in response to resuming activity on the prescription; The method of claim 1 , further comprising: displaying the flowchart or the decision tree based on the retrieved data.
10. 1. A system comprising: a controller configured to obtain a prescription representing a flowchart or a decision tree for performing a main set of tasks in the device, one or more of the tasks includes a subset of subtasks; the controller is configured to determine an experience or education level of one or more individuals performing the tasks on the equipment by storing a history of the one or more individuals; the controller is configured to automatically modify a display of the prescription in a graphical user interface (GUI) by at least one of exposing at least a first subset of the sub-tasks in response to the level of experience or education being below a threshold level and exposing at least a second subset of the sub-tasks in response to the level of experience or education being above the threshold level; the controller is configured to instruct an automation device to automatically perform one or more of the tasks on the equipment in response to the level of experience or education being below the threshold level; The system, wherein the controller is configured to automatically display the prescription in the GUI to the one or more persons performing the task at the device.
11. 11. The system of claim 10, wherein the controller is configured to automatically modify the display of the prescription by collapsing the display of at least the second subset of the subtasks into a single node within the flowchart or the decision tree, thereby hiding at least the second subset of the subtasks.
12. 11. The system of claim 10, wherein the controller is configured to automatically modify the display of the prescription by exposing the at least the first subset of the subtasks by expanding the at least the first subset of the subtasks into multiple nested nodes within a single node in the flowchart or decision tree.
13. 11. The system of claim 10, wherein the controller is configured to automatically modify the display of the prescription without removing or adding data to the prescription.
14. 11. The system of claim 10, wherein the controller is configured to receive input from the one or more persons during performance of the tasks in the prescription to do one or more of: (a) expand the subset of the subtasks that are collapsed in the representation of the prescription; or (b) collapse the subset of the subtasks that are expanded in the representation of the prescription.
15. At least one of the tasks includes a decision; 11. The system of claim 10, wherein the controller is configured to modify the display of the prescription to move to a subsequent one of the tasks following the decision based on an outcome of the decision.
16. The controller: (a) completion of at least one of said tasks; (b) work on the at least one of the tasks has begun but not been completed; (c) data entry by the one or more persons while working on the at least one of the tasks; or (d) bookmarks added by the one or more persons in response to cessation of activity on the prescription; The system of claim 10 , configured to modify a presentation of nodes in the main set of tasks in the flowchart or decision tree in response to one or more of:
17. The system of claim 10 , wherein the controller is configured to modify a presentation of links between nodes in the main set of tasks in the flowchart or decision tree in response to completion of at least one of the tasks.
18. the controller is configured to store data indicative of one or more of: (a) completion of one or more of the tasks; (b) input provided by the one or more persons; or (c) decisions made within the flowchart or decision tree in response to or in connection with a cessation of activity on the prescription; The controller: retrieving the stored data in response to resuming activity on the prescription; and displaying the flowchart or the decision tree based on the retrieved data; The system of claim 10 .
19. 1. A method comprising: obtaining, via a controller, a prescription representing a flow chart or decision tree for executing a main set of tasks in the device, one or more of the tasks including a subset of subtasks; determining, via the controller, one or more characteristics of the device based on output from one or more sensors; automatically modifying a display of the prescription by exposing at least a first subset of the subtasks in response to the one or more characteristics being outside a specified range; automatically performing one or more of the tasks on the equipment using an automation device in response to a level of experience or education being outside of the specified range; and automatically displaying the prescription to one or more persons performing the task.
20. 20. The method of claim 19, wherein modifying the prescription representation does not remove or add data to the prescription.
Citation Information
Patent Citations
Work procedure management system, work procedure management method and work procedure management program
JP2014089586A
Scheduling support method, information processor, and scheduling support program
JP2017033457A
Building incident management system with user interface for creating and editing standard operating procedures
US20200074832A1
