System, method and apparatus for enhancing process control using a virtual assistant
Through the virtual assistant system, user requests are parsed and execution commands are generated, which solves the problem that operators cannot fully access field equipment data in the prior art, and improves the operation efficiency and convenience of the process control system.
Patent Information
- Application Number
- CN201911286072.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-12-13
- Filing Date
- 2019-12-13
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2039-12-13
AI Technical Summary
In existing process control systems, operators cannot fully access the associated data and information when interacting with field devices, resulting in inefficient operation and requiring additional technical knowledge and assistance to complete tasks.
The virtual assistant system is adopted to improve the user's operation convenience of the process control system by interacting with the user, parsing the action information in the request, mapping it to specific actions, and generating commands to execute or display information associated with the field device.
It enhances the operator's operational convenience of process control systems, reduces dependence on technical knowledge, improves operation efficiency, and allows users to complete complex process control tasks through simple commands.
Smart Images

Figure CN111324093B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to process control systems and, more particularly, to systems, methods, and apparatus for enhancing process control using a virtual assistant. Background Art
[0002] In recent years, process control systems (such as those used in chemical, petroleum and / or other processes) have become increasingly complex with the proliferation of field devices with enhanced processing capabilities to perform new and / or improved process control functions. The current generation of process control systems includes a large number and variety of field devices or field instruments for measuring and / or controlling different aspects of the process control environment. The increase in automation in the process control environment provides operators with more opportunities for interaction through different media to facilitate the operation of the process control system. Summary of the invention
[0003] An exemplary apparatus disclosed herein for enhancing process control using a virtual assistant includes a memory storing instructions and at least one processor for executing the instructions so that the at least one processor determines a process control context based on a request for information associated with a field device of a process control system, the process control context being based on a configuration of the process control system, identifies a subject included in the request, the subject corresponding to the field device based on the process control context, maps the subject to an action to be performed by the field device, generates a command based on the mapping to instruct the field device to perform the action, and sends the command to the field device to perform the action.
[0004] An exemplary method disclosed herein for enhancing process control using a virtual assistant includes determining a process control context based on a request for information associated with a field device of a process control system, the process control context being based on a configuration of the process control system, identifying a subject included in the request, the subject corresponding to the field device based on the process control context, mapping the subject to an action to be performed by the field device, generating a command based on the mapping to instruct the field device to perform the action, and sending the command to the field device to perform the action.
[0005] An exemplary non-transitory computer-readable storage medium includes instructions that, when executed, cause a machine to at least perform the following operations: determine a process control context based on a request for information associated with a field device of a process control system, the process control context being based on a configuration of the process control system, identify a subject included in the request, the subject corresponding to the field device based on the process control context, map the subject to an action to be performed by the field device, generate a command based on the mapping to instruct the field device to perform the action, and send the command to the field device to perform the action. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Figure 1Ais a schematic diagram of an example virtual assistant that facilitates operation of an example process control system.
[0007] Figure 1B is included in the promotion Figure 1A Example Process Control System Operation of an Example Wearable Device Figure 1A Schematic diagram of an exemplary virtual assistant.
[0008] Figure 2 yes Figure 1A Schematic diagram of an exemplary virtual assistant.
[0009] Figure 3 Shows the corresponding Figure 1A An example table of example profiles for an example process tank of an example process control system.
[0010] Figure 4 is with Figure 3 Schematic diagram of a first exemplary visualization corresponding to an exemplary profile.
[0011] Figure 5 is with Figure 3 Schematic diagram of a second exemplary visualization corresponding to an exemplary profile.
[0012] Figure 6 is a flowchart representing machine readable instructions that may be executed to implement Figure 1A-2 An exemplary virtual assistant is provided to generate and execute scripts based on requests.
[0013] Figure 7 is a flowchart representing machine readable instructions that may be executed to implement Figure 1A-2 An exemplary virtual assistant to generate and display visualizations based on requests.
[0014] Figure 8 is constructed to execute Figure 6-7 Instructions to achieve Figure 1A-2 Block diagram of an exemplary processing platform for an exemplary virtual assistant.
[0015] The drawings are not drawn to scale. Alternatively, the thickness of a layer or region may be exaggerated in the drawings. Generally, the same reference numerals will be used throughout the drawings and the accompanying written description to refer to the same or similar parts. DETAILED DESCRIPTION
[0016] Process control systems such as distributed control systems have become increasingly complex with the development of various components with increased data acquisition resolution, processing power, and signal conditioning. Distributed control systems (DCS) are used to monitor and / or control various aspects of operations to be performed in a process control environment, such as, for example, manufacturing components, processing chemical feedstocks, etc. A DCS typically includes a plurality of controllers (e.g., electronic controllers, programmable controllers, etc.) and accompanying input / output (I / O) modules that allow the controllers to acquire signals from various input field devices and / or instruments and control various output field devices and / or instruments. An I / O module may include inputs, outputs, and / or combinations thereof.
[0017] As used herein, the terms "field device," "field instrument," or "instrument" refer to a control device, such as, for example, an actuator, an actuator assembly, an actuator controller, an actuator positioner, a sensor, a transmitter, a valve assembly, etc., which can be used throughout a process control system to measure and / or control different aspects of the process control system (e.g., other process control devices, etc.).
[0018] A typical DCS includes controllers, programmable processors, and / or logic circuits distributed throughout a process control environment to improve reliability and reduce installation costs by localizing control functions near the process control environment, but enabling remote monitoring and supervisory control of the process control environment. In some cases, operators, including engineers, maintenance technicians, or other field personnel, can monitor the DCS remotely through a process control network, or locally through physical interaction with controllers, field devices, etc. For example, an operator can connect to a field device through a wired connection or a wireless connection to view process control data associated with the field device and / or a component or device communicatively connected to the field device.
[0019] In some known DCS implementations, when interacting locally with a field device, the operator has limited visibility of the field device and / or the components or devices that are communicatively coupled to the field device. For example, when an operator is connected to a valve controller associated with a valve via a computer-based software application, the operator may only have access to limited data associated with the valve. In such examples, the operator may only be able to view limited data, such as actuator pressure or valve position. For example, when in a process control room, the operator may only be able to view limited data via a human-machine interface that is displaying limited data. In other examples, the operator may only be able to view limited data via a device (e.g., a laptop, a smart phone, a tablet, etc.) that is communicatively coupled to the valve, which may require additional technical knowledge (e.g., establishing a communication connection, troubleshooting an unresponsive communication connection, etc.) to communicate with the valve through the device. In such examples, when the first operator is performing maintenance or troubleshooting tasks on the valve, the first operator may need the assistance of a second operator to view limited data. For example, the first operator may not have a free hand to operate the device when trying to perform one or more tasks associated with the valve.
[0020] In some known DCS implementations, operators are unable to view associated data and / or supplemental data associated with valves, components or devices coupled to valves, and / or components associated with control loops including valves. Supplemental data may include alarm data, action or task data (e.g., one or more actions or routines that a field device is performing or capable of performing), historical data, etc. In addition, operators are unable to obtain supplemental information from field devices, including process control diagrams, maintenance instructions, wiring diagrams, etc., when performing maintenance on field devices and / or otherwise interacting with field devices. In such examples, operators may have to leave the process control area to obtain supplemental information and then return to the process control area to complete tasks based on the supplemental information, which in turn leads to inefficient operations.
[0021] Examples disclosed herein include systems, methods, and apparatus that enable a user and / or a computer-based software application (e.g., a user interacting with a computer-based software application) to initiate a session with a virtual assistant or robot (e.g., a process control robot) to assist the operator or user in completing tasks related to process control. Examples disclosed herein facilitate user requests for information associated with a field device or process unit by returning corresponding process control values and interacting with the user in a supporting or supplemental role.
[0022] In some disclosed examples, when the virtual assistant is installed on an exemplary computing device such as a laptop, a smart phone, a tablet computer, etc., the user interacts with the virtual assistant. In some disclosed examples, when the virtual assistant is installed on other exemplary computing devices including wearable devices, such as headphones, wristbands or glasses (which include one or more processors, one or more logic circuits, etc. to implement the virtual assistant), the user interacts with the virtual assistant. In such disclosed examples, the virtual assistant can interact with field devices within the range of wireless beacons (e.g., Bluetooth beacons, Wi-Fi beacons, etc.). For example, a Wi-Fi beacon can be communicatively coupled to one or more servers that facilitate requests from the virtual assistant. In such examples, when the virtual assistant is within the range of a Wi-Fi beacon, information associated with field devices within the range of the Wi-Fi beacon can be requested by querying one or more servers via the Wi-Fi beacon. In some examples, in response to entering the coverage area of the Wi-Fi beacon, the virtual assistant downloads information associated with the field device to increase the speed of processing user requests associated with the field device and sending them to the user.
[0023] In some disclosed examples, the virtual assistant obtains a request from a user, parses the request for actionable information, and supports a set of actions or levels of information based on the actionable information. In some disclosed examples, the action includes providing a parameter value associated with a field device or a component or device coupled to the field device by communication. In other disclosed examples, the action includes providing supplemental information, such as a current process or task implemented and / or otherwise performed by the field device, a step-by-step description of performing a task (e.g., a maintenance task, a task associated with a test plan, etc.) on or using the field device, the status of a process control task associated with the field device, etc. In some examples, the action includes a process control workflow, which includes one or more process control operations, and the user can use a corresponding command (e.g., a command via a computer-based application, a voice-based command, etc.) to start, stop, or pause the process control operation.
[0024] Figure 1A is a schematic diagram of an example virtual assistant (VA) 100 that facilitates operation of an example process control system 102. Figure 1A1, VA 100 is a process control virtual assistant. For example, VA 100 can be a computer-based or software agent that performs tasks or services for an example user (e.g., an operator, a maintenance technician, a process control operator, etc.) 104. In some examples, VA 100 interacts with multiple users 104. In some examples, VA 100 is a robot, a chatbot, etc., which can be accessed, initialized, and / or otherwise interacted with via a computer-based or software application, voice commands, text-based commands, etc.
[0025] exist Figure 1A In the illustrated example of , the VA 100 obtains and / or otherwise acquires the request from the exemplary host application 106 running and / or otherwise executing on devices (e.g., processor-based devices) including the first exemplary device 108, the second exemplary device 110, the third exemplary device 112, and the fourth exemplary device 114. Figure 1A In the present invention, the host application 106 includes one or more routines (e.g., software routines) or programs (e.g., software programs) executed by machine-readable instructions. For example, the host application 106 can be a standard operating system (e.g., Windows-based TM Operating systems, Apple Operating system, Apple Operating system, Android TM operating system, The host application 106 is a process control-related software application running on a host computer (such as an operating system). The host application 106 is executed by the devices 108, 110, 112, 114 to enable the user 104 to obtain data or information associated with one or more field devices or corresponding operations contained in the process control system 102 via the VA 100.
[0026] In some examples, the host application 106 enables the user 104, via the VA 100, to perform desired functions or tasks with respect to a process being controlled and / or otherwise monitored by the process control system 102, such as viewing the current state of the process (e.g., via a graphical user interface), evaluating the process, modifying the operation of the process (e.g., via a visual object diagram), etc. In some examples, the host application 106 performs the desired functions by interacting with field devices included in the process control system 102, via the VA 100, based on one or more available commands retrieved from the VA 100, selecting one of the retrieved commands, and sending the command to the field device via the VA 100. For example, the user 104 may request the VA 100 to perform a task, the VA 100 may process the request, the VA 100 may generate an audible message describing and / or otherwise including one or more available commands based on the processed request, the user 104 may select one of the commands via a verbal confirmation or command, and the VA 100 may send the command to one or more corresponding field devices.
[0027] exist Figure 1A In the example shown in FIG. 1 , the first device 108 is a device such as Emerson TM AMS TREX TM , which is capable of facilitating interaction with the process control system 102 via the host application 106 (e.g., via an integrated display, microphone, and / or speaker). Alternatively, the first device 108 may be any other type of process control handheld or mobile device. Figure 1A In the example, the second device 110 is an Internet-enabled tablet computer (e.g., iPad TM , Surface, etc.), which can facilitate interaction with the process control system 102 via the host application 106 (e.g., via an integrated display, microphone, and / or speaker). Figure 1A In , the third device 112 is an Internet-enabled mobile handheld device (e.g., a smart phone), and thus can facilitate interaction with the process control system 102 via the host application 106 (e.g., via an integrated display, microphone, and / or speaker). Figure 1A In the embodiment of the present invention, the fourth device 114 is an Internet-enabled laptop computer that is capable of facilitating interaction with the process control system 102 via the host application 106 (e.g., via an integrated display, microphone, and / or speaker). Alternatively, the VA 100 may facilitate interaction with a computer such as a laptop computer. Figure 1AIn some embodiments, host application 106 can be used to interact with less or more devices than the number and / or type of devices shown in . Although host application 106 is depicted as being the same on each of devices 108, 110, 112, 114, alternatively, host application 106 can be customized based on platform and / or customized in other ways. For example, the host application 106 executed on the first device 108 can be different from the host application 106 executed on the second device 110. In such examples, host application 106 can have different user interfaces, different communication drivers (for example, the first device 108 can have Bluetooth 5.0, and the second device 110 has Bluetooth 4.0, etc.), to be consistent with the corresponding platform. In some examples, host application 106 has no other interface except voice user interface (VUI). For example, the VUI of host application 106 can be used to completely replace the keyboard, gestures from user 104, etc.
[0028] exist Figure 1A In the illustrated example of , the user 104 and / or the host application 106 can interact with the VA 100 via commands including auditory, audible, computer-based, gestures, or verbal commands. Alternatively, any other type of command can be used. In some examples, the user 104 can make verbal requests and / or otherwise request data associated with field devices included in the process control system 102 including a first exemplary field device (field valve (FV) FV-105) 116 and a second exemplary field device (field instrument (FI) FI-205) 118 from the VA 100. Figure 1A The first field device 116 is a fluid flow control component. For example, the first field device 116 can be an electrically, hydraulically, and / or pneumatically actuated valve component. For example, the first field device 116 can include at least an actuator, a valve (e.g., a butterfly valve, a stop valve, etc.), a valve controller (e.g., a local single-loop process controller), etc. For example, the user 104 can issue a verbal command to the VA 100 to request and / or otherwise obtain data associated with the first field device 116, including actuator pressure, valve position, etc. Additionally or alternatively, the VA 100 can trigger corresponding to and / or otherwise facilitate in addition to the combination Figure 1A In addition or alternatively, the VA 100 may request and / or otherwise obtain any other data associated with the first field device 116 (e.g., including a wiring diagram of the first field device 116, a software or communication protocol identifier of the first field device 116, a firmware version associated with a controller included in the first field device 116, etc.).
[0029] Figure 1AThe second field device 118 of the illustrated example is a sensor. For example, the second field device 118 can be a pressure transmitter, a temperature transmitter, etc. In other examples, the second field device 118 can be a level transmitter, a pH transmitter, a valve positioner, etc. For example, the user 104 can issue a verbal command to the VA 100 (e.g., "Virtual Assistant, tell me about FI-205.") to request data associated with the second field device 118, including sensor measurements (e.g., pressure measurements, flow measurements, temperature measurements, etc.) in engineering units (e.g., pounds per square inch (PSI), degrees Celsius, etc.), in non-engineering units (e.g., voltage measurements, current measurements, etc.), in crude oil units, in fluidized catalytic cracking (FCC) units, etc., and / or combinations thereof. In other examples, the verbal command can be a request for calibration information (e.g., the date of the last calibration, the date of the next calibration, the user who calibrated the sensor, etc.), configuration (e.g., communication protocol output address, electrical output range, etc.), manufacturer information (e.g., model number, serial number, etc.), version information (e.g., the firmware version associated with the second field device 118), etc.
[0030] In some examples, the user 104 and / or the host application 106 queries the VA 100 for information associated with the example control loop 120. Figure 1A In FIG. 1 , control loop 120 is a field instrument control (FIC) loop specified by FIC-205. Figure 1A The control loop 120 includes a first field device 116 and a second field device 118 . Figure 1A The control loop 120 corresponds to a controller (e.g., a PLC, a processor-based controller, etc.) that obtains input from the second field device 118 and / or generates output signals to the first field device 116. Alternatively, the control loop 120 may include fewer or more field devices. Figure 1A In , the control loop 120 can operate the first field device 116 (eg, open a valve, close a valve, move a valve to a specific position, etc.). Figure 1A In the embodiment of the present invention, the control loop 120 can acquire and / or otherwise obtain sensor data associated with the first field device 116 from the second field device 118. For example, the control loop 120 can command the first field device 116 to open and cause fluid to flow through the first field device 116, and can measure a parameter of the flow (e.g., temperature, flow rate, pressure, etc.) based on the data obtained from the second field device 118.
[0031] In some examples, the VA 100 returns information associated with the control loop 120, including a mode (MODE) parameter (e.g., automatic mode, manual mode, cascade mode, etc.), a set point (SP) parameter, a process variable (PV) parameter or a measured value (MV) parameter, an output (OUT) parameter, a status parameter, and / or one or more alarms associated with a component or field device included in the control loop 120. For example, the SP parameter may correspond to an expected value, a desired value, etc. of an MV or PV. In such examples, the SP may be input and / or otherwise sent by the user 104 via the VA 100. For example, the user 104 may instruct the VA 100 to assign a value of 100% open to the SP parameter for the valve position parameter of the first field device 116. The MV or PV parameter may correspond to a measured value of a process output (e.g., a flow rate, a pressure, a temperature, etc. of a fluid flowing through the first field device 116). The OUT parameter may correspond to an output of the control loop 120 (e.g., an output from a controller). The OUT parameter may correspond to an output signal generated by the control loop 120 and sent to an actuator (eg, an actuator included in the first field device 116 ) to regulate the actuator.
[0032] In some examples, in response to a MODE parameter corresponding to the automatic mode, the control loop 120 receives the SP and the PV, calculates the OUT parameter, and sends an output signal corresponding to the OUT parameter to the first field device 116. In some examples, in response to a MODE parameter corresponding to the manual mode, the control loop 120 is overridden, thereby allowing the user 104 to send the output signal corresponding to the OUT parameter directly to the actuator. For example, the user 104 can instruct the VA 100 to adjust the valve position of the first field device 116 by overriding the SP stored in the control loop 120.
[0033] In some examples, in response to a mode (MODE) parameter corresponding to the cascade mode, the control loop receives an SP from an external source, such as, but not limited to, another controller associated with another control loop (e.g., FIC-201, FIC-204, etc.). For example, control loop FIC-201 may receive a first SP associated with field device FV-101 from control loop FIC-204. In such an example, user 104 may instruct VA 100 to generate a flow rate of 2 barrels per minute (bpm) for the fluid flowing through FV-101. VA 100 may process the request from user 104, generate a command, and send the command to FIC-204 to assign the flow rate of 2 bpm to the flow rate SP. FIC-204 may obtain a level measurement of the exemplary process tank 122 from FI-204 and convert the change in the level into a flow rate (e.g., a flow rate based on the fill rate of the process tank 122). In turn, the FIC-204 may generate a command based on the flow rate SP and send it to the FIC-201 corresponding to the valve position SP of the FV-101. In response to the FIC-201 receiving the command, the FIC-201 opens the FV-101 to achieve and / or otherwise satisfy the valve position SP that may satisfy the flow rate SP of 2 bpm through the FV-101. In response to satisfying the valve position SP, the FIC-204 may determine whether the flow rate SP of 2 bpm through the FV-101 has been satisfied. In some examples, the VA 100 generates an audible message to the user 104 indicating that the flow rate through the FV-101 associated with the request from the user has been satisfied. Additionally or alternatively, the VA 100 may include information such as the fill rate of the process tank 122, the value of the valve position SP, the valve position associated with the FV-101, and / or a combination thereof in the audible message.
[0034] In some examples, the user 104 and / or the host application 106 issues commands to the VA 100 for execution by one or more components of the process control system 102. For example, the user 104 may issue a verbal command to the VA 100 to turn the first field device 116 on or off, to instruct the second field device 118 to output data using different units of measurement or using a different communication protocol, etc. In other examples, the host application 106 may generate and send commands to the VA 100 to execute a workflow including one or more operations of one or more components of the process control system 102. For example, the host application 106 may generate and send commands to the VA 100 to fill the process tank 122. In such examples, the VA 100 may operate one or more field devices (e.g., FV-101, FV-102, etc.) to fill the process tank 122, by opening the exhaust gas output of the first field device 116, and provide feedback to the user 104 and / or the host application 106 including the operating status, etc. For example, the status may be an audible and / or visual based message indicating that the process tank 122 is 40% full. In other examples, the message may include an estimated duration of operation remaining, an amount of time that has elapsed since the start of the operation, etc. In some examples, the VA 100 generates a notification to the user 104, the host application 106, etc., including safety information. For example, the notification may correspond to a gas leak in the FCC, a liquid leak in the process tank 122, etc. Additionally or alternatively, although in Figure 1A A process tank 122 is shown, but VA 100 may trigger a session with user 104 and / or host application 106 corresponding to functions and / or operations that facilitate utilization of one or more heat exchangers, one or more distillation columns, one or more combustion heaters, etc. and / or combinations thereof.
[0035] exist Figure 1AIn the illustrated example of , the VA 100 queries and / or obtains information from the exemplary database 124 via the exemplary network 126. In some examples, the database 124 includes a configuration of the process control system 102, which may include one or more profiles, each of which corresponds to a component included in the process control system 102 (e.g., a first profile corresponding to the first field device 116, a second profile corresponding to the process tank 122, etc.). In some examples, a profile may correspond to two or more components. For example, a profile may include information associated with the control loop 120, which may include information corresponding to the first field device 116, the second field device 118, the controller, etc. included in the control loop 120. In some examples, the database 124 includes actions (e.g., basic actions, complex actions, etc.) that can be performed by components of the process control system 102. In some examples, the database 124 includes scripts that can be executed by the VA 100 to instruct one or more components of the process control system 102 to perform one or more actions.
[0036] Figure 1A The database 124 may be implemented by a volatile memory (e.g., synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS dynamic random access memory (RDRAM), etc.) and / or a non-volatile memory (e.g., flash memory). The database 124 may additionally or alternatively be implemented by one or more double data rate (DDR) memories, such as DDR, DDR2, DDR3, DDR4, mobile DDR (mDDR), etc. The database 124 may additionally or alternatively be implemented by one or more mass storage devices, such as one or more hard disk drives, one or more optical disk drives, one or more digital versatile disk drives, one or more solid state disk drives, etc. Although in the illustrated example, the database 124 is shown as a single database, the database 124 may be implemented by any number and / or one or more types of databases. In addition, the data stored in the database 124 may be in any data format, such as, for example, binary data, comma-delimited data, tab-delimited data, structured query language (SQL) structures, etc.
[0037] Figure 1AThe network 126 is a bus and / or computer network. For example, the network 126 may be a process control network. In some examples, the network 126 is a network with the ability to be communicatively coupled to the Internet. However, the network 126 may be implemented using any suitable one or more wired and / or wireless networks, including, for example, one or more data buses, one or more local area networks (LANs), one or more wireless LANs, one or more cellular networks, one or more fiber optic networks, one or more satellite networks, one or more private networks, one or more public networks, etc. The network 126 may enable the example VA 100 to communicate with the database 124.
[0038] Figure 1B is included in and / or otherwise executed on the exemplary wearable devices 128, 130, 132 to facilitate Figure 1A Operation of an exemplary process control system 120 Figure 1A A schematic diagram of an exemplary VA 100 is shown. Figure 1B , the wearable devices 128 , 130 , 132 include a first exemplary wearable device 128 , a second exemplary wearable device 130 , and a third exemplary wearable device 132 . Figure 1B The first wearable device 128 is a headset. Additionally or alternatively, the VA 100 can be mounted and / or otherwise configured on any other computing device or wearable device, such as a smart watch, smart glasses, etc.
[0039] Figure 1B The first wearable device 128 of the illustrated example may be a headset that includes a processor-based computer platform including one or more processors, one or more storage devices and / or one or more mass storage devices for storing machine-readable instructions, one or more interface circuits for facilitating Bluetooth and / or Wi-Fi communications, one or more input devices (e.g., buttons and / or microphones), one or more output devices (e.g., speakers, etc.), and / or any other hardware components that may implement the VA 100. In such examples, the user 104 may invoke the VA 100 on the first wearable device 128 by pressing a button or by speaking a particular phrase (e.g., “Hello, virtual assistant”).
[0040] Figure 1BThe second wearable device 130 of the illustrated example is a wristband. For example, the second wearable device 130 may be a wristband including a processor-based computer platform including one or more processors, one or more storage devices and / or one or more mass storage devices for storing machine-readable instructions, one or more interface circuits for facilitating Bluetooth and / or Wi-Fi communications, one or more input devices (such as buttons and / or microphones), one or more output devices (such as speakers, etc.), and / or any other hardware components that may implement the VA 100. In such examples, the user 104 may invoke the VA 100 on the second wearable device 130 by pressing a button or by speaking a specific phrase (e.g., “Hello, virtual assistant”).
[0041] Figure 1B The third wearable device 132 of the illustrated example corresponds to glasses including two lenses. For example, the third wearable device 132 can be glasses including a processor-based computer platform, which includes one or more processors, one or more storage devices and / or one or more mass storage devices for storing machine-readable instructions, one or more interface circuits for facilitating Bluetooth and / or Wi-Fi communications, one or more input devices (such as buttons and / or microphones), one or more output devices (such as displays, speakers, etc.) and / or any other hardware components that can implement VA 100. In such examples, the user 104 can invoke VA 100 on the third wearable device 132 by pressing a button, saying a specific phrase (such as "Hello, virtual assistant"), making a gesture in front of the glasses (such as blinking or waving), etc. In some examples, the third wearable device 132 includes two displays, including a first display integrated into the first of the lenses and a second display integrated into the second of the lenses. In other examples, the third wearable device 132 includes a display in either the first or second lenses of the glasses.
[0042] exist Figure 1B In the illustrated example of , the wearable devices 128, 130, 132 are communicatively coupled to the network 126 via a wireless connection such as Bluetooth or Wi-Fi. In some examples, one or more of the wearable devices 128, 130, 132 can be communicatively coupled to the network 126 via a direct wireless connection without an intervening (intermediate) device such as an access point, beacon, gateway, etc. In other examples, one or more of the wearable devices 128, 130, 132 can be communicatively coupled to the network 126 via an intervening device such as an access point, beacon, gateway, etc.
[0043] exist Figure 1BIn the illustrated example of , one or more of the wearable devices 128, 130, 132 can be communicatively coupled to the network 126 via one or more of the exemplary beacons 134a-g. Figure 1B , beacons 134a-g are Wi-Fi beacons (e.g., Wi-Fi Beacons). For example, beacons 134a-g are devices that include one or more processors that can facilitate wireless communications between computing devices (e.g., between a server and a client device, between an access point and a client device, etc.). Alternatively, one or more of beacons 134a-g can be Bluetooth beacons or dual Bluetooth / Wi-Fi beacons. Additionally or alternatively, one or more of beacons 134a-g can support different wireless communication protocols. Although in Figure 1B Seven beacons 134a-g are depicted in FIG. 1 , but fewer or more beacons 134a-g than shown may be used.
[0044] exist Figure 1B In the illustrated example of FIG. 1 , beacons 134a-g are positioned at various locations throughout the process control system 102. Figure 1B In one embodiment, each beacon 134a-g is set at a location that generates a coverage area that includes one or more field devices. The coverage area may correspond to a geographic area in which a device can be communicatively coupled to a beacon associated with the coverage area. For example, the first of the beacons 134a-g may have a first coverage area that includes FI-205 118 and FIC-207. In some examples, one or more coverage areas of the beacons 134a-g may overlap with each other. In other examples, the coverage areas of the beacons 134a-b may not overlap with each other.
[0045] In some examples, the wearable devices 128, 130, 132 dynamically connect to the beacons 134a-g when within the coverage area generated by and / or otherwise associated with the beacons 134a-g. For example, when entering the range of the associated coverage area of the first beacon 134a, the wearable devices 128, 130, 132 can be communicatively coupled to the network 126 via the first beacon 134a-g. When the wearable devices 128, 130, 132 are communicatively coupled with the first beacon 134a, the user 104 can trigger a session with the VA 100 corresponding to the field device within the range of the first beacon 134a. For example, the user 104 can initiate a session with the VA 100 on the first wearable device 128 corresponding to the FI-205 118. In such an example, the user 104 can invoke the VA 100 by saying "Hello, virtual assistant, give me information about FI-205." In response to the call, the VA 100 may generate a request to a database 124 communicatively coupled to the network 126 via the first beacon 134a. The VA 100 may generate an audible response to the user 104 that includes information corresponding to the FI-205 118.
[0046] In some examples, the VA 100 may download information to the wearable devices 128, 130, 132 associated with the field devices within the coverage area of the beacons 134a-g upon entering the coverage area. For example, when the user 104 wearing the third wearable device 132 enters the first coverage area of the first beacon 134a, the VA 100 may query the first beacon 134a for the field devices in the first coverage area. The first beacon 134a may return a list of field devices including FI-205 118 and FIC-207. The VA 100 may compare the returned list of field devices with the information stored in the third wearable device 132. The VA 100 may download information that is not yet stored in the third wearable device 132. For example, the third wearable device 132 may have stored the first information associated with the FI-205 118, but has not yet stored the second information associated with the FIC-207. In such an example, the VA 100 may query the first beacon 134a for the second information. In some examples, when the third information is different from the first information, the VA 100 queries the first beacon 134a for the third information associated with the FI-205 118. In other examples, the VA 100 may replace the first information with the third information.
[0047] In some examples, upon leaving the coverage area, the VA 100 removes information associated with field devices within the coverage area of the beacons 134a-g. For example, when the user 104 wearing the second wearable device 130 leaves the first coverage area associated with the first beacon 134a, the VA 100 can instruct the second wearable device 130 to delete information associated with the FI-205 118, the FIC-207, etc. In other examples, upon entering a second coverage area different from the first coverage area, the VA 100 can instruct the second wearable device 130 to delete information. For example, the VA 100 can instruct the second wearable device 130 to replace previously stored information associated with the first coverage area with second information associated with the second field device in the second coverage area.
[0048] Advantageously, the VA 100 can reduce the speed of processing requests from the user 104 by storing information associated with field devices in the beacon coverage area locally on the wearable devices 128, 130, 132 rather than obtaining the information from the database via the network 126. For example, when the user 104 wearing the third wearable device 132 enters the first coverage area associated with the first beacon 134a, the VA 100 can download the wiring schematic associated with the FIC-205 120. In such an example, when the user 104 requests the VA 100 to display the wiring schematic, the VA 100 can instruct the third wearable device 132 to display the wiring schematic on one or both glasses (e.g., on one or both displays integrated into the glasses). By storing the wiring schematic locally when entering the first coverage area, the VA 100 can increase the speed of processing the user 104's request.
[0049] Similarly, the VA 100 can reduce the amount of computing resources associated with maintaining the network 126 by obtaining data from information stored on the beacons 134a-g rather than querying the database 124. In some examples, the beacons 134a-g can reduce the networking resources associated with the network 126 by forming a mesh network. For example, the beacons 134a-g can be arranged in the process control system 102 so that each beacon 134a-g is communicatively coupled to at least one of the other beacons 134a-g. In such an example, the first beacon 134a can process requests from the second through seventh beacons 134b-g and send the requests to the network 126, rather than the network 126 processing requests from each beacon 134a-g.
[0050] Figure 2 yes Figure 1A-1B Schematic diagram of the VA 100. Figure 2, the VA 100 operates in an exemplary process control environment 200 and / or otherwise enhances process control (e.g., process control operations). For example, the process control environment 200 may correspond to a process industry environment or system including a chemical plant, a manufacturing facility, an oilfield environment, a factory, etc. For example, the process control environment 200 may correspond to Figure 1A-1B The process control system 102. Figure 2 In the example shown, VA 100 facilitates Figure 1A-1B 104, the host application 106, etc. (e.g., receiving commands, sending responses, etc.). In some examples, the user 104 and / or the host application 106 query the VA 100 for data or information of interest via exemplary requests 201a-b including a first exemplary request 201a and a second exemplary request 201b. One or both requests 201a-b may correspond to a verbal request, a command (e.g., a verbal command), a selection and / or input to the host application 106, etc. For example, the user 104 may ask with the first request 201a, "What is the status of FIC-205?" In such an example, the VA 100 may return one or more parameters, including the following: Figure 1A-1B MODE, SP, PV, OUT, status, alarm, etc., and / or combinations thereof, associated with the control loop 120 of the VA 100. In other examples, the user 104 can interact with the host application 106 by selecting a second request 201b from a pre-filled list displayed on the user interface, or by generating input by typing a text-based command or request that is not included in the pre-filled list (e.g., "find me FI*"), where a wildcard character shown as an asterisk (*) can instruct the VA 100 to return a list of components or field devices associated with the FI, or to include the FI in the description of the component or field device. For example, the VA 100 can generate a list to include the names, descriptions, and / or corresponding path information of one or more field devices, control loops, etc. that are assigned indicators including the FI (e.g., FI-201, FIC-201, FI-202, FIC-202, etc.).
[0051] exist Figure 2 In the example, the host application 106 may be an exemplary mobile application 202. For example, Figure 1A-1B The first device 108, the second device 110, and / or the third device 112 may be used to execute and / or otherwise operate the mobile application 202. For example, the mobile application 202 may be iOS mobile app, Android TM Mobile applications, etc. For example, the mobile application 202 may be a process control-based mobile application, such as Emerson TM DeltaV TMMobile.
[0052] exist Figure 2 In the illustrated example of FIG. 1 , the host application 106 may be an exemplary browser application 204. For example, the browser application 204 may implement a web browser and / or web server in which information sent to, received from, and / or otherwise exchanged with the VA 100 is formatted as HTTP messages. However, any other message formats and / or (communication) protocols may additionally or alternatively be used, such as, for example, the File Transfer Protocol (FTP), the Real-time Transport Protocol (RTP), the Simple Message Transfer Protocol (SMTP), the HTTP Secure (HTTPS) protocol, etc. For example, the browser application 204 may be an example of a web browser that uses the Emerson TM DeltaV TM A browser-based process control application built and / or otherwise generated live.
[0053] Figure 2 The host application 106 may be an exemplary desktop application 206. For example, the desktop application 206 may be Computers (e.g. computer, The desktop application 206 may be operated and / or otherwise run on a Windows-based desktop and / or laptop computer, a Linux-based desktop and / or laptop computer, etc. For example, the desktop application 206 may be operated and / or otherwise run as a standalone application that does not require a web browser and / or an Internet connection to run or operate. In other examples, the desktop application 206 may be operated and / or otherwise run as a computer application that may be run or operated using a web browser and / or an Internet connection.
[0054] exist Figure 2In the illustrated example of , the host application 106 running and / or otherwise executing on the mobile application 202, the browser application 204, and the desktop application 206 includes a user interface for accepting and / or otherwise obtaining the request 201a-b from the user 104. For example, the VA 100 can send a response to the request 201a-b to the host application 106. In such examples, the host application 106 can display the response via the user interface (e.g., display a graphic including the parameter value, display a visualization, display a text-based message including the response, etc.). In some examples, the host application 106 can transmit the response from the VA 100 via one or more speakers communicatively coupled to the host application 106. For example, the host application 106 can generate a verbal message representing the response from the VA 100, and transmit the verbal message via one or more speakers coupled to the computing device executing the host application 106.
[0055] exist Figure 2 In the illustrated example of , the host application 106 includes one or more application programming interfaces (APIs), extensions, plug-ins, etc., and / or combinations thereof, which can be used to facilitate communication with the VA 100 via the exemplary host application robot framework 208. Alternatively, the host application 106 can communicate and / or otherwise exchange data with the VA 100 without the host application robot framework 208. Figure 2 In the embodiment of the present invention, the host application robot framework 208 is included in the host application 106 to queue requests and arrange requests and responses. For example, the host application robot framework 208 can process and / or otherwise manage requests to the VA 100 (e.g., buffering requests, prioritizing requests, classifying requests, comparing requests with responses stored in a cache, etc.) and responses from the VA 100.
[0056] exist Figure 2 In the illustrated example of , the user 104 and / or the host application 106 communicate and / or otherwise interact with the VA 100 via an exemplary server robot framework 210. The VA 100 includes a server robot framework 210 to facilitate communication by receiving and processing commands and / or requests. For example, the server robot framework 210 can process or manage queries from the host application 106 based on request / response, publish / subscribe, or event registration with a callback architecture or pattern. In some examples, the server robot framework 210 is implemented by one or more processor-based servers.
[0057] In some examples, the server robot framework 210 returns the response to the user 104, the host application 106, etc. synchronously, while in other examples, the server robot framework 210 returns the response asynchronously. For example, the asynchronous response can be returned as an alert, notification, etc. In such examples, the user 104 can request a long-running workflow, such as filling Figure 1A-1B The server robot framework 210 can asynchronously generate and send a response to the user 104 (e.g., via an audible alarm or notification), the host application 106 (e.g., via an audible alarm and / or visual notification on a user interface of the host application 106), and / or one of the wearable devices 128, 130, 132 after completing filling the processing tank 122 and / or at various milestones in filling the processing tank 122 (e.g., when the processing tank 122 is 25% filled, 50% filled, 75% filled, etc.). In some examples, the server robot framework 210 can generate and send a response that includes information associated with the long-running workflow, such as the fill rate of the processing tank 122, the number of times the processing tank 122 is filled, and / or the number of times the processing tank 122 is filled. Figure 1A-1B the flow rate of the first field device 116, Figure 1A-1B The sensor measurement results of the second field device 118, etc., as well as the alarm or notification and / or the above information contained in the alarm or notification.
[0058] exist Figure 2 In the illustrated example of FIG. 2 , the server robot framework 210 includes an exemplary framework controller 212, an exemplary parser 214, an exemplary analyzer 216, an exemplary generator 218, and an exemplary executor 220 to process and / or otherwise manage interactions with the host application 106. Alternatively, the server robot framework 210 may include more Figure 2 Fewer or more components are shown. Alternatively, including Figure 2 The components in the server robot framework 210 shown in FIG. 2 may be combined, divided, rearranged, omitted, eliminated, and / or implemented in any other manner.
[0059] exist Figure 2 In the illustrated example of FIG. 1 , the server robot framework 210 includes a framework controller 212 to facilitate interaction between (1) a user 104, a host application 106, one of the wearable devices 128, 130, 132, etc. and (2) the server robot framework 210. In some examples, the framework controller 212 determines the configuration and / or type of request management system to use when managing requests. For example, the framework controller 212 can determine to facilitate communication or data transfer with the user 104, the host application 106, the wearable device 128, 130, 132, etc. based on request / response, publish / subscribe, or event registration with callback, and / or any other message processing mode.
[0060] In some examples, the framework controller 212 determines a response management system to manage responses to requests 201a-b received and / or otherwise obtained from the user 104, the host application 106, and / or the wearable devices 128, 130, 132. For example, the framework controller 212 can determine to send and / or otherwise return responses to the user 104, the host application 106, and / or the wearable devices 128, 130, 132 asynchronously or synchronously ... Figure 1A-1B The framework controller 212 may determine to asynchronously return a response as a notification to the user 104 based on determining that the initial request from the host application 106 is a request for information (e.g., a request for information related to the Figure 1A-1B The request for the firmware version associated with the first field device 116 is used to determine to synchronously return a response to the host application 106.
[0061] exist Figure 2 In the illustrated example, the server robot framework 210 includes a parser 214 to determine and / or otherwise identify elements (e.g., distinguishable elements, different components, etc.) contained in the requests 201a-b from the user 104, the host application 106, and / or the wearable devices 128, 130, 132. In some examples, the parser 214 includes a tokenizer for performing word segmentation (tokenization), or a process or method for dividing and / or classifying parts of an input string. For example, the parser 214 can decompose or segment the word stream included in the first request 201a of the user 104 into lexical units (tokens), which are obtained by the analyzer 216 for further processing. Additionally or alternatively, the parser 214 can determine the elements of the first request 201a in any other manner.
[0062] In some examples, the parser 214 performs dimensionality reduction to reduce and / or otherwise eliminate elements in the first request 201a that do not add substantial recognition value by the server robot framework 210. For example, the parser 214 can filter and / or otherwise eliminate irrelevant or unrecognizable audible noise in the first request 201a from the user 104 to reduce the amount or duration of processing power required by the server robot framework 210 to process the first request 201a. In other examples, the parser 214 can reduce the number of vocabulary units sent to the analyzer 216 for processing. For example, the parser 214 can eliminate tokens associated with non-actionable, filler, or irrelevant words such as "um," "the," etc. from the first request 201a from the user 104 before sending the determined vocabulary units to the analyzer 216.
[0063] In some examples, the parser 214 identifies and / or otherwise determines expressions (e.g., regular expressions, typical expressions, etc.) based on requests from the user 104, the host application 106, and / or the wearable devices 128, 130, 132. For example, the parser 214 can determine that the request 201a-b is based on a generic question such as "What is the status of FIC-201?", "Where is FV-106 located?", etc. In such examples, the parser 214 can determine typical phrases, such as "What is the status", "Where is", etc., and determine a response based on the requested component (e.g., FIC-201, FV-106, etc.) following the typical phrase. In some examples, the parser 214 includes image recognition hardware (e.g., one or more hardware accelerators) and / or software to recognize elements of gesture-based requests (e.g., waving a hand, a thumbs-up gesture to confirm a response from the VA 100, etc.).
[0064] In some examples, the parser 214 performs information extraction based on the requests 201a-b. For example, the parser 214 can identify the field device, control loop, etc. associated with the request 201a-b based on extracting the name and / or type of the requested field device. In other examples, the parser 214 can identify the type of the request 201a-b (e.g., command, location request, maintenance procedure request, etc.) based on extracting information from the request 201a-b.
[0065] exist Figure 2In the illustrated example of , the server robot framework 210 includes an analyzer 216 to validate requests 201a-b from users 104, host applications 106, wearable devices 128, 130, 132, etc. In some examples, the analyzer 216 performs one or more validation or verification checks including grammar checks, spelling checks, semantic checks, etc. to determine whether the expression tokenized by the parser 214 is a valid expression. For example, the analyzer 216 can determine whether the parser 214 has generated one or more vocabulary units that, when assembled to form an expression, can be returned by the VA 100 as a valid response.
[0066] exist Figure 2 In the illustrated example of FIG. 2 , the server robot framework 210 includes a generator 218 to compile, generate, and / or otherwise produce a set of actions including one or more searches, responses, scripts, and / or templates. In some examples, the generator 218 performs a search based on the request 201 a-b. For example, the generator 218 may perform a search based on a query of “What is the status of FIC-201?” For this query, the generator 218 may search for Figure 2 One of the exemplary systems 222 obtains the status, formulates an exemplary response "The status of FIC-201 is closing FV-101" based on the search, and sends the exemplary response to the user 104, the host application 106, the wearable device 128, 130, 132, etc.
[0067] In some examples, the generator 218 may generate at least one of a script or a template based on the request 201a-b. In such examples, the generator 218 may send the script or template to the executor 220. For example, the request 201a-b from the user 104 may correspond to a long-running workflow, or a workflow including multiple steps or completion points. For example, the long-running workflow requested by the user 104 may be "What are the steps for replacing a seal in FV-105?" In such examples, the generator 218 may create a template based on at least one of the field device type corresponding to the FV-105, the component of the field device type being queried, or the identification of the user 104. For example, the template may include a set of steps organized into individual steps, wherein each step in the set includes one or more instructions for executing the step, one or more tools for executing the step, and / or one or more verification steps to ensure that one or more instructions are correctly executed. In such examples, the template may include a response for each step, which may be sent to the user 104 when the user 104 confirms that the step has been completed or if the user 104 requests additional information. For example, the response may be information associated with a next step, or may be a response to a query (eg, request 201a-b) from user 104 associated with a current step being performed, a tool corresponding to the current step, etc.
[0068] In some examples, the generator 218 formulates a response to request additional information from the source of the request. For example, when the user 104 requests information about a field device that is not included in the process control system 102, requests to perform an action on a field device that is not supported by the field device, etc., the generator 218 can generate a response to the user 104 requesting clarification or additional information. In such examples, the generator 218 can request additional information from the user 104 to verify the accuracy of the request processed by the server robot framework 210. In some examples, the generator 218 determines that the request is an erroneous request (e.g., a frequently received erroneous request) and generates a response that includes a suggested alternative to the request 201a-b and / or corresponding information describing why the original request 201a-b is incorrect and / or why the suggested alternative can be performed in place of the original request 201a-b.
[0069] exist Figure 2In the illustrated example, the server robot framework 210 includes an actuator 220 to facilitate actions or commands based on requests from the user 104, the host application 106, and / or the wearable devices 128, 130, 132. For example, the actuator 220 can receive a script, template, etc. from the generator 218. In some examples, the actuator 220 triggers and / or otherwise initiates the script, template, and / or action based on the request 201a-b. For example, the actuator 220 can send a command structure based on the JavaScript Object Notation (JSON) format to the exemplary session context engine 224. In response to the sending, the session context engine 224 can generate a command for opening the first field device 116 in response to the user 104 requesting to open the first field device 116. Figure 1A In other examples, the actuator 220 may trigger the template to fill in the command of the first field device 116. Figure 1A-1B The executor 220 may send a script, template, etc. to the session context engine 224 to trigger the filling of the process tank 122. In other examples, the executor 220 may trigger a script in response to the user 104 requesting information associated with the first field device 116, the second field device 118, etc.
[0070] In some examples, executor 220 updates an example model 243 included in and / or otherwise stored in an example session context database 244. In some examples, session context database 244 includes more than one model 243. For example, model 243 may correspond to one or more machine learning models, one or more neural networks (e.g., artificial neural networks), etc. For example, executor 220 may update model 243 used to process a request from one or more of user 104, host application 106, wearable devices 128, 130, 132, etc. In such examples, executor 220 may trigger example session context engine 224 to update model 243 included in session context database 244 associated with VA 100. In some examples, based on Figure 1A-1B The model 243 may be reconfigured, updated, etc., based on a new configuration of the process control system 102. For example, the process control system 102 may be modified by removing and / or adding one or more field devices, modifying one or more control loops, etc., which may affect responses generated by the server robot framework 210 and / or more generally the VA 100.
[0071] The (one or more) models 243 stored in the session context database 244 may correspond to an artificial neural network. An artificial neural network is a computer system architecture model that learns to perform tasks and / or provide responses based on evaluation or "learning" of examples with known inputs and known outputs. A neural network such as the (one or more) models 243 stored in the session context database 244 may be characterized by a series of interconnected nodes called "neurons" or nodes. Input nodes are activated from external sources / stimuli, such as inputs from actuators 220 (e.g., requests 201a-b from users 104, responses generated by generators 218, etc.). Input nodes activate other internal network nodes based on the connections between nodes (e.g., controlled by machine parameters, prior relationships, etc.). The connections are dynamic and can be changed based on feedback, training, etc. By changing the connections, the output of the artificial neural network can be improved or optimized to produce more / most accurate results. For example, information from one or more sources may be used to train model(s) 243 stored in session context database 244 to map inputs to responses, etc., to improve the accuracy of responses, to reduce the time required to generate responses, etc., and / or combinations thereof.
[0072] Machine learning techniques, whether neural networks, deep learning networks, support vector machines, and / or other (one or more) experiential / observational learning systems, can be used, for example, to generate optimal results, locate objects in images, understand speech and convert speech to text, and improve the relevance of search engine results. Deep learning is a subset of machine learning that uses sets of algorithms to model high-level abstractions in data using deep graphs with multiple processing layers, including linear and non-linear transformations. While many machine learning systems are seeded with initial features and / or network weights that will be modified through learning and updating of the machine learning network, deep learning networks train themselves to identify "good" features for analysis. Using a multi-layer architecture, machines using deep learning techniques can process raw data better than machines using traditional machine learning techniques. Using different evaluation or abstraction layers helps to examine data for groups of highly related values or unique themes.
[0073] For example, deep learning using convolutional neural networks (CNNs) segments data using convolutional filters to locate and identify learned, observable features in the data. Each filter or layer of the CNN architecture transforms the input data to increase the selectivity and invariance of the data. This abstraction of the data allows the machine to focus on the features in the data it is trying to classify and ignore irrelevant background information.
[0074] Deep learning works with the understanding that many data sets consist of high-level features that consist of lower-level features. For example, when examining an image (e.g., an image based on a gesture request), rather than looking for objects, it is more efficient to look for edges that form patterns that form part of the object being looked for. These hierarchies of features can be found in many different forms of data.
[0075] The observable features learned include objects and quantifiable regularities learned by the machine during supervised learning. A machine provided with a large number of well-classified data sets can better distinguish and extract features related to successfully classifying new data. A deep learning machine using transfer learning can appropriately connect data features to certain classifications confirmed by human experts. Conversely, the same machine can update classification parameters when informed of classification errors by human experts. Settings and / or other configuration information can be guided, for example, by the use of learned settings and / or other configuration information, and as the system is used more (e.g., repeatedly and / or by multiple users), the number of variations and / or other possibilities of settings and / or other configuration information can be reduced for a given situation.
[0076] For example, an exemplary deep learning neural network can be trained on an expert-classified data set. The data set constructs the first parameters of the neural network, which will be the stage of supervised learning. During the supervised learning stage, the neural network can be tested to see if it achieves the desired behavior. Once the desired neural network behavior is achieved (e.g., the machine has been trained to operate according to a specified threshold, etc.), the machine can be deployed for use (e.g., the machine is tested using "real" data, etc.). During operation, the neural network classification can be confirmed or rejected (e.g., by an expert user, an expert system, a reference database, etc.) to continue to improve the neural network behavior. The (one or more) models 243 included in the session context database 244 are then in a transfer learning state because the parameters for determining the classification of the neural network behavior are updated based on the ongoing interaction. In some examples, an artificial neural network such as the (one or more) models 243 stored in the session context database 244 can provide direct feedback to another process, such as elements parsed by the parser 214, responses generated by the generator 218, etc. In some examples, the (one or more) model 243 outputs data that is buffered (e.g., via the cloud, etc.) and verified before being provided to another process.
[0077] In some examples, the actuator 220 updates the target based on the request 201a-b from the user 104, the host application 106, the wearable device 128, 130, 132, etc. For example, the actuator 220 can update the target of the template, script, etc. based on a request from the user 104 to cancel the action, process, operation, etc. associated with the previous request. For example, the user 104 can request in a first request that the VA 100 fill in Figure 1A-1B 122, and in a second request, the VA 100 is requested to cancel filling the process tank 122, wherein the first request is made before the second request. In such examples, the executor 220 may generate a command to stop filling the process tank 122 by canceling and / or otherwise stopping a script, template, etc. generated in response to the first request. In some examples, the executor 220 generates an action in response to updating the target. For example, the executor 220 may generate a command to purge the process tank 122 in response to the user 104 requesting to stop filling the process tank 122. In such examples, the executor 220 may send information associated with the command to the user 104 to ensure that the user 104 approves the command before the executor 220 facilitates execution of the command.
[0078] In some examples, the actuator 220 updates the session or response plan. For example, the actuator 220 can generate a script or template based on the request 201a-b from the user 104, the host application 106, the wearable device 128, 130, 132, etc. For example, the actuator 220 can generate a script based on the user 104 asking "What is the status of FV-105?" The actuator 220 can generate a script to include responses or levels of responses to potential problems associated with FV-105, a device coupled to FV-105, or a control loop including FV-105 that the user 104 can ask. In such examples, when the user 104 asks a follow-up question to the response generated and sent by the generator 218, the actuator 220, etc., the actuator 220 can update the session associated with the script. For example, the actuator 220 can determine that the user 104 has transitioned from a first-level question and corresponding response to a second-level question and corresponding response based on the user 104 asking for more specific information in a subsequent request.
[0079] exist Figure 2 In the illustrated example of FIG. 1 , the user 104 may interact with the VA 100 via an exemplary DCS controller component 226. For example, the DCS controller component 226 may be an Emerson TM DeltaV TMS series DCS system. For example, the DCS controller component 226 can be one or more programmable logic controllers (PLC) or any other process controller used for industrial or process automation. Alternatively, the DCS controller component 226 can be any other type of DCS system. Figure 2 The DCS controller assembly 226 includes a first controller 228 and a second controller 230. Figure 2 In the embodiment, the first controller 228 and the second controller 230 are characterization module (CHARM) I / O cards (CIOC). Alternatively, any other number or type of electronic controllers may be used. The first controller 228 and the second controller 230 perform data acquisition and control operations, such as obtaining and processing sensor measurements, sending sensor measurements to an external controller and / or DCS, etc. For example, the first controller 228 and the second controller 230 may include Figure 1A The process control system 102 is used to control and / or monitor the first field device 116, the second field device 118, etc.
[0080] Figure 2 The first controller 228 and the second controller 230 are electrically coupled to the I / O module 232 via the terminal block 234. The I / O module 232 is removably coupled to the terminal block 234. Figure 2 The I / O modules 232 are CHARMs. Alternatively, any other type of input and / or output modules for data acquisition and control may be used. Each CHARM is a separate input and / or output channel for the first controller 228 and the second controller 230. For example, each I / O module 232 may be an analog input or output channel, a digital input or output channel, a relay channel, etc. Each I / O module 232 may include an analog-to-digital (A / D) conversion circuit, a signal isolation circuit, etc.
[0081] exist Figure 2 In the illustrated example, the first of the I / O modules 236 is a VA module. In some examples, the VA module 236 can facilitate the DCS controller component 226 to communicate (1) with the VA 100 via the network 126, (2) with one or more of the beacons 134a-g, and / or (3) with the VA 100. Figure 1B For example, the first wearable device 128 may send a first request 201a to the first beacon 134a, which in turn may send a query to the VA module 236, which in turn may query the VA 100 via the network 126 for the interaction with one or more of the wearable devices 128, 130, 132. Figure 1A-1B104. The VA module 236 may be associated with the field device 118 of the DCS controller component 226. In such examples, the VA module 236 may store information in a mass storage disk or storage device included in the DCS controller component 226 and / or send information to the user 104. For example, the VA module 236 may facilitate the user 104's interaction with the VA 100 (e.g., send information to the user 104 and / or obtain the first request 201a from the user 104). For example, the VA module 236 may include one or more speakers and / or one or more microphones. In such examples, the VA module 236 may use one or more microphones to listen to and / or otherwise obtain the first request 201a from the user 104. The VA module 236 may use one or more speakers to transmit and / or otherwise send a response to the first request 201a to the user 104.
[0082] In some examples, the VA module 236 converts the first request 201a into one or more digital signals, which can be transmitted via Figure 1A-1B The server robot framework 210 may transmit the one or more digital signals to the server robot framework 210 via the network 126 of the DCS controller component 226. In response to the server robot framework 210 receiving the one or more digital signals, the server robot framework 210 may convert and / or otherwise transform the one or more digital signals into vocabulary units via the parser 214. The server robot framework 210 may analyze the vocabulary units, determine a response based on the vocabulary units, and convert the response into one or more digital signals to be sent to the VA module 236 via the network 126, the DCS controller component 226, etc. In response to the VA module 236 receiving the one or more digital signals, the VA module 236 transforms the one or more digital signals into sound via one or more speakers included in the VA module 236 to transmit the response to the user 104.
[0083] Alternatively, the functionality of the VA module 236 may be included and / or otherwise integrated into at least one of the first controller 228 or the second controller 230. For example, one or more microphones and / or one or more speakers may be integrated into the DCS controller component 226, the first controller 228, and / or the second controller 230. In some examples, the VA module 236 is a standalone device that may be communicatively coupled to the DCS controller component 226 (e.g., via a wired connection, a wireless connection, etc.), one or more of the beacons 134a-g, and / or at least one of the VAs 100.
[0084] exist Figure 2In the illustrated example of , the VA 100 includes a session context engine 224 to manage and / or otherwise process requests from the user 104, the host application 106, the wearable devices 128, 130, 132, the DCS controller component 226, etc. based on the session context. For example, the user 104 can ask the VA 100 for information and / or status associated with the first controller 228, the second controller 230, etc. of the DCS controller component 226. In such examples, the status can correspond to the health of the first controller 228, the firmware version of the second controller 230, the health of one or more I / O modules 236, etc. In some examples, the session corresponds to an interaction with the VA 100. For example, the session can correspond to the user 104 verbally communicating with the VA 100 and / or receiving information from the VA 100 via the beacons 134a-g, the wearable devices 128, 130, 132, the VA module 236, etc. In other examples, a session may correspond to a host application 106 sending a request to the VA 100 and / or receiving a response from the VA 100. In some examples, the session context engine 224 is implemented by one or more processor-based servers. In some examples, the server robot framework 210 and the session context engine 224 are implemented by the same one or more processor-based servers. In other examples, the server robot framework 210 is implemented by one or more processor-based servers separate from the one or more processor-based servers that implement the session context engine 224.
[0085] In some examples, the session context corresponds to requests, responses, etc. associated with process industries including chemical plants, manufacturing facilities, oil field environments, etc. In some examples, the session context engine 224 and / or more generally the VA 100 may generate a session context based on the session context. Figure 1A-1B The session context engine 224 may generate responses based on the system configuration associated with the process control system 102. For example, the session context engine 224 may generate responses to requests from users 104, host applications 106, wearable devices 128, 130, 132, etc. based on process control device configurations (e.g., DeltaV database configurations), asset management software (AMS) databases, recipes, and / or other process-related information.
[0086] Figure 2The session context engine 224 includes an example session processor 238, an example action processor 240, and an example session state handler 242 to process and / or otherwise manage requests processed by the server robot framework 210. For example, the session context engine 224 can establish a context based on the configuration of the process control system 102, identify a subject associated with the context (e.g., a request associated with the first field device 116, the second field device 118, etc.), and determine one or more actions associated with the subject. For example, the session context engine 224 can determine that the context of the request 201a-b from the user 104, the host application 106, the wearable device 128, 130, 132, etc. is Figure 1A-1B The session context engine 224 may customize and / or otherwise generate a process-centric response based on determining that the context of the request is the process control system 102. ... Figure 1A-1B Database 124, Figure 2 The configuration loaded in the session context database 244, etc., determines that the context of the request is the process control system 102. In such examples, the session context engine 224 can execute one or more scripts to perform one or more actions, return information associated with the subject, etc., and / or a combination thereof.
[0087] exist Figure 2 In the illustrated example of , the session context engine 224 includes a session processor 238 to assemble, compile, and / or otherwise aggregate scripts or other lists of automated tasks, each of which includes one or more actions. For example, the session processor 238 can obtain the request 201a-b from the user 104 via the server robot framework 210. The session processor 238 can identify one or more actions, one or more parameters to be returned (e.g., one or more values of the parameters to be returned), etc., and / or a combination thereof based on the request. For example, the user 104 can issue a request such as "show me FV-105". The server robot framework 210 can process the request and send the processed request to the session processor 238. The session processor 238 can identify the request as a request for information associated with a field device assigned with an identifier FV-105. In such an example, the session processor 238 obtains parameters associated with the field device including MODE, OUT, STATUS, etc., aggregates the obtained parameters into a response, and sends the response to the user 104 via the server robot framework 210. In an example, the response is transmitted to the user 104 via verbal communication. In some examples, the response is transmitted to the user 104 via the host application 106 (eg, displaying the response on a display, transmitting the response with a speaker coupled to the computing device, etc.).
[0088] Figure 2 The session processor 238 aggregates scripts based on information retrieved and / or otherwise obtained from the exemplary session context database 244. In some examples, the session processor 238 queries the session context database 244 for information based on the exemplary topics 246. For example, the session processor 238 may map topics 246 based on field device names or descriptions, field device types, etc. to information included in the session context database 244. In such examples, the session processor 238 may map topics 246 including names or descriptions of field devices (e.g., FV-105, FIC-205, etc.) to exemplary configurations 248a, exemplary scripts 248b, etc. associated with the topics 246. For example, the session processor 238 may obtain, in response to mapping the topic 246 for FV-105 associated with the first field device 116 to the session context database 244 for FV-105. Figure 1A-1B MODE, OUT, and STATUS parameters of the first field device 116.
[0089] In some examples, the session processor 238 maps a topic 246 including a type of field device (e.g., valve, pressure transmitter, process tank, etc.) to a configuration, script, etc. associated with the topic 246. For example, the session processor 238 can obtain a list of field devices that match and / or are otherwise associated with the topic 246. In such an example, the session processor 238 can obtain a list of field devices that match and / or are otherwise associated with the topic 246 by mapping the topic 246 of "valve" (e.g., a request by the user 104 such as "What valve is running?") to the session context database 244 based on the identified context of the process control system 102. Figure 1A List of valves such as FV-101, FV-102, FV-103, etc.
[0090] In some examples, the session processor 238 aggregates and / or otherwise generates a script, template, etc. by obtaining one or more exemplary actions 250 from the session context database 244 based on the subject 246. For example, the session processor 238 can map the subject 246 (e.g., name, device type, etc.) to the session context database 244. Based on the mapping, the session processor 238 can obtain one or more actions 250 from the session context database 244 and generate a script, template, etc. based on the obtained actions 250. In some examples, the action 250 is a basic action. For example, the basic action can correspond to a one-to-one request for a command-type action, such as a request to open a valve and a corresponding command to open the valve. In other examples, the basic action can correspond to a request for information (e.g., parameter values, security information, etc.). For example, the basic action can correspond to a one-to-one request for information, such as a request for current security alarms and a corresponding request including one or more security alarms or a confirmation that there are no security alarms to report.
[0091] In some examples, action 250 is a complex action. For example, a complex action may correspond to a workflow that includes two or more actions, such as filling Figure 1A-1B In such an example, the complex action includes opening Figure 1A-1B The session processor 238 may obtain a complex action associated with a request to fill the process tank 122 and generate a script to perform the complex action based on the obtained complex action including the associated action 250. In some examples, the action 250 includes a script to perform a basic action, a complex action, etc.
[0092] exist Figure 2 In the illustrated example of , the session context engine 224 includes an action processor 240 to execute and / or otherwise facilitate the script generated by the session processor 238. In some examples, the action processor 240 performs the action by communicating with Figure 2 One or more of the systems 222 interact to execute a script or a set of commands, instructions, etc. Figure 2 The system 222 includes an exemplary process control system 252 and an exemplary process control network system 254. Alternatively, the system 222 may include Figure 2 Fewer or more systems than those shown in .
[0093] Figure 2The process control system 252 is a system that monitors and / or controls various aspects of operations to be performed in a processing environment such as, for example, manufacturing parts, processing chemical feedstocks, etc. For example, Figure 2 The process control system 252 may correspond to Figure 1A-1B The process control system 102 is provided. Figure 2 The process control system 252 may include at least one controller (e.g., a first controller 228, a second controller 230, etc.) and accompanying inputs and outputs, thereby allowing the (one or more) controllers to obtain signals from various input field devices and / or instruments and control various output field devices and / or instruments. For example, Figure 2 The process control system 252 may correspond to at least one Emerson TM DeltaV TM Emerson Controller TM DeltaV TM Distributed control system (DCS).
[0094] In some examples, the action processor 240 generates commands and / or sends commands to Figure 2 The process control system 252 facilitates the execution of the script. For example, the action processor 240 may generate an open Figure 1A-1B The action processor 240 may generate a command to be sent to the controller of the first field device 116 of the management control loop 120 to turn on the first field device 116. Figure 2 A set of commands to be executed simultaneously or sequentially by the process control system 252 of the process control system 252. For example, the action processor 240 can generate a set of commands to open FV-101, FV-102, and FV-103 and disable, for example, Figure 1A-1B The FP-101 fluid pump (FP) shown is used to fill Figure 1A-1B The processing tank 122.
[0095] In some examples, the action processor 240 facilitates execution of the script by requesting information from the process control system 252. For example, the action processor 240 can obtain information associated with the first field device 116, including one or more parameter values. For example, the action processor 240 can query the control loop 120 (e.g., query the controller that controls the control loop 120) for parameters such as MODE, OUT, and STATUS associated with the first field device 116, the second field device 118, etc. In response to the query, the action processor 240 can obtain the one or more parameter values and send the one or more parameter values to the session processor 238 to be packaged into a response.
[0096] Figure 2 The process control network system 254 is a system that is communicatively coupled to at least one of the process control systems 252 or the VA 100. In some examples, the process control network system 254 is a cloud-based network that monitors and / or controls multiple process control systems. For example, the process control network system 254 can correspond to one or more open platform communications (OPC) servers that convert hardware communication protocols from multiple controllers included in multiple process control systems into OPC protocols and / or any other communication protocols. In some examples, the process control network system 254 can perform cloud-based data storage, analysis, big data analysis, deep machine learning, etc. to provide a unified control environment based on multiple process control systems (e.g., Figure 1A-1B The information obtained and / or processed by the process control system 102) can realize multi-process control environment scale modeling, digital process control efficient operation and automation, prognostic health monitoring, component reliability analysis, process control management and / or optimization.
[0097] In some examples, the action processor 240 facilitates execution of the script by generating and / or sending commands to the process control network system 254. For example, the action processor 240 may generate commands to perform an emergency shutdown of two or more process control systems included in and / or otherwise monitored by the process control network system 254. For example, the action processor 240 may generate and send a set of actions that the process control network system 254 may implement to perform the emergency shutdown.
[0098] In some examples, the action processor 240 facilitates execution of the script by requesting information from the process control network system 254. For example, the action processor 240 may query the process control network system 254 to determine prognostic health monitoring information associated with the first field device 116. For example, the user 104 may request the VA 100 to estimate the number of life cycles remaining for the first field device 116. In such examples, the action processor 240 may send information including a serial number, a manufacturer part number, a device type, a number of cycles performed (e.g., a number of valve opening and closing operations), a duration since the last maintenance event, etc. associated with the first field device 116 to the process control network system 254. In response to receiving the information, the process control network system 254 may map the information to previously analyzed field devices having substantially similar information (e.g., the same manufacturer part number, a number of cycles within a tolerance of 100 cycles, a duration within 5 days, etc.), and determine a failure rate (e.g., an average failure rate, a range of failure rates, etc.) based on the data associated with the previously analyzed field devices. In response to at least the mapping and the determining, the process control network system 254 can send the failure rate and / or other prognostic health monitoring information to the action processor 240, which can send the failure rate and / or other prognostic health monitoring information to the session processor 238 for inclusion in a response to the server robot framework 210. For example, the action processor 240 can send the failure rate, including the duration until expected failure, the number of cycles until expected failure, etc., to the user 104, the host application 106, the wearable device 128, 130, 132, etc. In such examples, the action processor 240 can send a safety alert based on the failure rate, the impending failure, etc.
[0099] exist Figure 2In the illustrated example of , the session context engine 224 includes a session state handler 242 to store and / or otherwise maintain the state of a session initiated by a user 104, a host application 106, a wearable device 128, 130, 132, etc. In some examples, the session state corresponds to a subject identified based on the request. For example, the session state handler 242 can assign and / or otherwise associate a subject such as FV-105 to a session state. In such examples, the session state handler 242 can enable the user 104, the host application 106, the wearable device 128, 130, 132, etc. to request additional details or information levels about the subject of FV-105, thereby delving deeper into the subject, or using the subject to branch or transfer to another subject of interest (e.g., a related subject), such as FIC-205, FI-205, etc. For example, the session state handler 242 can reduce the computing power used by the session processor 238 to process additional requests by referencing the session state to generate and / or otherwise package responses. For example, the session processor 238 can provide the user 104 with additional actions that can be performed by the FV-105, notify the user 104 of additional components that are communicatively coupled to the FV-105, etc. by querying the session state handler 242 for the session state instead of processing the request without working from a baseline or starting point.
[0100] In some examples, the session state corresponds to the state of the script being executed by the action processor 240 (e.g., completion state). For example, the action processor 240 can execute a workflow, such as providing the user 104 with instructions on how to replace a field device with a substantially similar field device (e.g., a field device of the same model, manufacturer part number, operating level, hazardous area classification, etc.). Figure 1A-1B In such examples, the action processor 240 may send the current or immediate step or operation being performed by the action processor 240, the subsequent step or operation to be performed, the total number of steps or operations to be performed, etc. to the session state handler 242. In response to receiving the information from the action processor 240, the session state handler 242 may provide the information to the session processor 238 to generate a response to the user 104. For example, the session state handler 242 may send the next step or operation to be performed, the completion status (e.g., the number of steps to be completed, the estimated duration to complete the steps, etc.) to the session processor 238, and the session processor 238 may generate and transmit a response to the user 104 based on the information received from the session state handler 242.
[0101] In some examples, the session state handler 242 modifies or updates the session state. For example, the session state handler 242 may update the session state based on a new topic requested by the user 104, the host application 106, the wearable device 128, 130, 132, the DCS controller component 226, etc. For example, the session state handler 242 may change the session state from FV-105 to FV-106 based on the user 104 asking for information about FV-106. In some examples, the session state handler 242 cancels or deletes the session state. For example, the session state handler 242 may disassociate FV-105 from the session state and / or cancel the session state of FV-105 based on at least one of the user 104 canceling the session with the VA 100, asking for information about another field device such as the FV-104, or the user 104 notifying the VA 100 that additional information corresponding to the FV-105 is not needed.
[0102] In some examples, the session state handler 242 speculatively forks or transitions to a new topic. For example, the session state handler 242 may determine that the user 104 has left a first coverage area of a first beacon 134a and has entered a second coverage area of a second beacon 134b. In such examples, the session state handler 242 may instruct the action processor 240 to query the process control network system 254 to determine a possible next topic of interest based on one or more field devices included in the second coverage area.
[0103] In some examples, when the session state handler 242 determines that the user 104, the host application 106, etc. has exhausted all possible or potential responses associated with the topic associated with filling the process tank 122, the session state handler 242 speculatively branches to a new topic. In such an example, the session state handler 242 can instruct the action processor 240 to query the process control network system 254 to determine the possible next topic of interest. For example, the process control network system 254 can execute and / or otherwise implement a machine learning algorithm to determine other process control systems (e.g., Figure 1A-1BThe process control network system 254 may determine that a topic associated with emptying a process tank is selected after filling the process tank in one or more process control systems external to the process control system 102. For example, the process control network system 254 may determine that a topic associated with emptying a process tank is selected a significant portion of the time (e.g., 40% of the time, 75% of the time, etc.) after filling the process tank. In such examples, the process control network system 254 may send the speculatively identified topic to the session state handler 242 via the action processor 240. In such examples, the session state handler 242 may instruct the session processor 238 to map the new topic to one or more actions, one or more configurations, one or more scripts, etc. contained in the session context database 244.
[0104] By speculatively fetching a new topic, if the user 104 issues a request associated with the new topic, the session processor 238 may provide a response to the user 104. The session processor 238 may attempt to predict the next step and / or otherwise stay ahead of the user 104 during time periods when the session processor 238 may be idle, not processing requests, etc. In some examples, the session processor 238 prompts the user 104 to perform an action associated with the speculatively fetched topic. For example, the user 104 may have forgotten to perform an action and is reminded to perform the action by being prompted by the VA 100 for the speculatively fetched topic. If the user 104 issues a request associated with a topic that is different from the speculatively fetched topic, the session processor 238 may prompt the user 104 to determine whether the user 104 would rather select the speculatively fetched topic. Alternatively, if the user 104 declines to select the speculatively fetched topic, the session processor 238 may instruct the session state handler 242 to replace the speculatively fetched topic with the requested topic.
[0105] exist Figure 2 In the illustrated example of , the session context engine 224 can support sessions instantiated on an external computing system such as the exemplary container repository 256. The container repository 256 includes containers or container images corresponding to lightweight, independent, executable software packages that include everything needed to execute the software, including code, runtime, system tools, system libraries, and settings. Containers isolate software from software environments, such as the difference between a development environment and a staging environment.
[0106] In some examples, the session context engine 224 queries the container repository 256 to determine whether a topic (e.g., a long-running workflow, a complex topic, etc.) has a corresponding container that can execute the topic. In response to determining that the topic has a corresponding container, the session context engine 224 can instruct the corresponding container to execute the topic. For example, a container in the container repository 256 can execute software (e.g., machine-readable instructions) to perform actions associated with the topic. The container can send commands to the system 222, send session states to the session context engine 224, send notifications to the user 104 via the session context engine 224, and so on. In such examples, the session context engine 224 can delegate and / or offload complex topics to an external system (e.g., a container in the container repository 256, one or more of the systems 222, etc.) to reduce the processing utilization, memory resources, storage resources, etc. of the session context engine 224.
[0107] Although in Figure 2 The implementation is shown in Figure 1A-1B The VA 100 is an exemplary method, but Figure 2 One or more of the elements, processes, and / or devices shown in the examples may be combined, divided, rearranged, omitted, eliminated, and / or implemented in any other manner. In addition, the exemplary server robot framework 210, the exemplary framework controller 212, the exemplary parser 214, the exemplary analyzer 216, the exemplary generator 218, the exemplary executor 220, the exemplary session context engine 224, the exemplary session processor 238, the exemplary action processor 240, the exemplary session state handler 242, the exemplary session context database 244, the exemplary theme 246, the exemplary configuration 248a, the exemplary script 248b, the exemplary action 250, and / or more generally, Figure 2The exemplary VA 100 may be implemented by hardware, software, firmware, and / or any combination of hardware, software, and / or firmware. Thus, for example, the exemplary server robot framework 210, the exemplary framework controller 212, the exemplary parser 214, the exemplary analyzer 216, the exemplary generator 218, the exemplary executor 220, the exemplary session context engine 224, the exemplary session processor 238, the exemplary action processor 240, the exemplary session state handler 242, the exemplary session context database 244, the exemplary theme 246, the exemplary configuration 248a, the exemplary script 248b, the exemplary action 250, and / or more generally, any of the exemplary VA 100 may be implemented by one or more analog or digital circuits, logic circuits, one or more programmable processors, one or more programmable controllers, one or more graphics processing units (GPUs), one or more digital signal processors (DSPs), one or more application specific integrated circuits (ASICs), one or more programmable logic devices (PLDs), and / or one or more field programmable logic devices (FPLDs). When reading any device or system claims of this patent covering pure software and / or firmware implementations, at least one of the exemplary server robot framework 210, exemplary framework controller 212, exemplary parser 214, exemplary analyzer 216, exemplary generator 218, exemplary executor 220, exemplary session context engine 224, exemplary session processor 238, exemplary action processor 240, exemplary session state handler 242, exemplary session context database 244, exemplary topic 246, exemplary configuration 248a, exemplary script 248b and / or exemplary action 250 is hereby expressly defined as comprising a non-transitory computer-readable storage device or storage disk, such as a memory, digital versatile disk (DVD), compact disk (CD), Blu-ray disk, etc., including software and / or firmware. Further, Figure 1A-1B The exemplary VA 100 may include in addition to or in lieu of Figure 2 One or more of those elements, processes, and / or devices shown in, and / or may include more than one of any or all of the elements, processes, and devices shown. As used herein, the phrase "in communication," includes variations thereof, including direct communication and / or indirect communication through one or more intermediate components, and does not require direct physical (e.g., wired) communication and / or constant communication, but additionally includes selective communication at regular intervals, scheduled intervals, non-periodic intervals, and / or one-time events.
[0108] Figure 3 Shows the corresponding Figure 1A-1BAn exemplary table of exemplary profiles 300 for a process tank 122 of a process control system 102 is shown in FIG. The profile 300 may correspond to Figure 1A-1B Database 124, Figure 2 The profile 300 may be a portion of the configuration of the process control system 102 loaded into the session context database 244 of the process control system 102. For example, the profile 300 may correspond to a topic. In such an example, the profile 300 corresponds to a topic based on the context of the process control system 102. Figure 1A-1B The subject of the treatment tank 122. In some examples, by placing Figure 1A-1B The configuration associated with the process control system 102 is loaded into the session context database 244 to initialize Figure 1A-2 The configuration may include information associated with one or more components of the process control system 102. For example, the configuration may include one or more parameters associated with the first field device 116, the second field device 118, etc. The configuration may include information about field devices included in the control loop 120.
[0109] In some examples, a configuration includes associations between field devices, control loops, etc. and / or combinations thereof. For example, the configuration may include Figure 1A-1B The association or relationship between FI-207, FIC-207, and FV-106 may include a description of how FI-207, FIC-207, and FV-106 are physically coupled (e.g., wiring diagrams, cable arrangements, termination schematics, etc.), communicatively coupled (e.g., communication protocol addressing schemes, Internet Protocol (IP) address tables, etc.), etc. In some examples, a configuration includes multiple profiles, including Figure 3 profile 300, association of each of the plurality of profiles (eg, subordination of one profile to another), and the like.
[0110] In some examples, session processor 238 generates profile 300. For example, session processor 238 may identify the session information included in a message from user 104, host application 106, etc. Figure 2The subject of the request 201a-b is a first field device 116, a process tank 122, and the like. In such examples, the session processor 238 may map the subject of the first field device 116 to a lookup table or any other data structure included in the session context database 244. In other words, the session processor 238 may map and / or otherwise perform a mapping of the first field device 116 to a lookup table or any other data structure included in the session context database 244. In some examples, the lookup table is based on a configuration. For example, the lookup table may include an association of the first field device 116 with one or more parameters (the one or more parameters corresponding to one or more parameters associated with the first field device 116), one or more actions that the first field device 116 may perform and / or otherwise implement, and the like. The session processor 238 may obtain the one or more parameters, the one or more actions, and the like from the session context database 244, and generate a profile (e.g., Figure 3 The session processor 238 may store the profile 300 in the session context database 244 for future processing.
[0111] exist Figure 3 In the illustrated example of , profile 300 includes fields such as an exemplary level 302 , an exemplary category 304 , an exemplary parameter 306 , an exemplary tag 308 , and an exemplary description 310 . Figure 3 The profile 300 includes levels 302 to organize information associated with the process tank 122 into a hierarchy or order for access by the VA 100. For example, the first level (L1) may correspond to information provided to the VA 100 in response to a request. Figure 1A-2 The first information layer of the user 104, the host application 106, etc. For example, the user 104 can Figure 2 In such examples, the VA 100 may display the information included in L1 to the user 104 via the mobile application (e.g., displaying the information on a display of the mobile device running the mobile application 202). In other examples, the VA 100 may transmit the information included in L1 to the user 104 via the host application 106 (e.g., via a verbal statement coupled to a speaker of the host application 106). In response to the user 104 requesting additional information such as “show me additional information about the treatment tank” or “tell me more about the treatment tank,” the VA 100 may send, transmit, etc. the information included in the second level (L2) to the user 104 via audible communication, the host application 106, etc. Alternatively, the profile 300 may include more than one level of information. Figure 3 Fewer or more levels 302 as shown.
[0112] exist Figure 3 In the illustrated example of , the profile 300 includes categories 304 to organize information associated with the process tank 122 based on the frequency of the information being requested or at least one of the components of the process tank 122. For example, the categories 304 may correspond to how often the information included in the profile 300 is requested. For example, the categories 304 may have values such as common, typical, uncommon, rare, etc., corresponding to the frequency with which the information is requested by the user 104, the host application 106, the wearable device 128, 130, 132, the DCS controller component 226, etc. In other examples, the categories 304 may correspond to components of the process tank 122, such as a balancing cylinder of the process tank 122. Alternatively, the profile 300 may include more than one category 304. Figure 3 Fewer or more categories 304 are shown.
[0113] exist Figure 3 In the illustrated example, profile 300 includes parameter 306 to indicate Figure 1A-1B A value associated with at least one of the corresponding levels 302 or categories 304 of the process tank 122. Figure 3 In the profile 300 of FIG. 1 , the parameters 306 include the vessel level, vessel pressure, inflow / outflow, temperature, and vessel temperature. For example, the VA 100 may return information associated with the vessel level parameters to the user 104 in response to receiving an initial query regarding the process tank 122. For example, the vessel level parameters may correspond to Figure 1A-1B The values measured by FI-206, FI-208, etc.
[0114] exist Figure 3 In the illustrated example of , the profile 300 includes a label 308 to represent an identifier (e.g., a process control identifier) associated with at least the parameter 306. In some examples, the label 308 is a software identifier. For example, the label 308 can correspond to an address and / or label in a communication protocol, a process control scheme, etc., which is assigned to a container level parameter associated with the processing tank 122. In some examples, the label 308 is a physical identifier (e.g., a physical label coupled to the processing tank 122, a label containing or describing the label affixed to the processing tank 122, etc.). For example, the container level parameter is assigned a label LXX27. In such examples, the VA 100 can return the label 308 associated with at least the container level parameter in response to a user 104, a host application 106, a wearable device 128, 130, 132, etc. requesting information associated with the processing tank 122.
[0115] exist Figure 3In the illustrated example of , profile 300 includes description 310 to indicate additional information that may be provided in response to a request. For example, in response to user 104 asking for additional information associated with at least parameter 306, the information included in description 310 may be packaged in response to user 104. For example, user 104 may ask VA 100 "What is the level of the process tank?" In response to the request, VA 100 may verbally reply "The level of the container labeled L XX27 is 80% full." User 104 may make a subsequent request "Give me more information about the level", to which VA 100 may reply "The container level is the most important parameter for the knockout pot." Additionally or alternatively, description 310 may be displayed on host application 106 and / or more generally Figure 3 In other examples, the user 104 may issue a request to "tell me about the balancing cylinder." In response to the request, the VA 100 may verbally reply with the values of the inflow / outflow parameters and / or corresponding labels. The VA 100 may not return temperature parameters and / or temperature labels based on the corresponding description of "if requested." For example, the VA 100 may not return information associated with the balancing cylinder temperature unless requested by the user 104.
[0116] Figure 4 is with Figure 3 Schematic diagram of a first exemplary visualization 400 corresponding to the exemplary profile 300 of FIG. Figure 4 The first visualization 400 corresponds to Figure 3 Alternatively, the first visualization 400 may correspond to a different level. In response to a request from a user 104, a host application 106, a wearable device 128, 130, 132, etc. Figure 2 Requests 201a-b can be made via Figure 1A-2 The host application 106 displays the first visualization 400. The first visualization 400 includes Figure 3 308 associated with L1 of the profile 300 of the process tank 122. For example, the first visualization 400 includes labels 308 associated with a vessel level parameter (L XX27), a vessel pressure parameter (P XX27), and an inflow / outflow parameter (F XX27). In some examples, the first visualization 400 can be updated by the VA 100 based on a request for additional information. For example, a label 308 associated with a temperature parameter (T XX27) can be displayed on the first visualization 400 in response to a request for additional information about the process tank 122.
[0117] Figure 5 is with Figure 3 Schematic diagram of a second example visualization 500 corresponding to the example profile 300 . Figure 5 The second visualization 500 corresponds to Figure 3 The second level visualization associated with the L2 of the profile 300. Figure 5 , second visualization 500 includes information associated with the first and second levels of profile 300. Alternatively, second visualization 500 may show information associated with only the second level of profile 300.
[0118] In response to a request from a user 104, a host application 106, etc., the Figure 1A-2 The host application 106 displays the second visualization 500. The second visualization image 500 includes Figure 1A-2 The second visualization 500 includes a diagram of the process tank 122. Figure 3 The second visualization 500 includes labels 308 associated with the first level and the second level of the profile 300. For example, the second visualization 500 includes labels 308 associated with the vessel level parameter (L XX27), the vessel pressure parameter (P XX27), the inflow / outflow parameter (F XX27), the temperature parameter (T XX27), and the vessel temperature parameter (T XX27). For example, the user 104 may request information associated with the process tank 122 from the VA 100. The VA 100 may generate a visualization including Figure 4 The first response of the label 308 shown in the first visualization 400 of FIG. For example, the host application 106 can display a first response including Figure 4 4. The user 104 may request additional information corresponding to the process tank 122 from the VA 100. In response to the request, the VA 100 may generate a second response including: Figure 5 The second visualization 500 of FIG. 5 shows a label 308. For example, the host application 106 can display a second response including Figure 5 308 shown in FIG. 4 . For example, the host application 106 can replace the first visualization 400 with the second visualization 500. Alternatively, the host application 106 can replace the first visualization 400 with the second visualization 500. Figure 5 The additional label 308 is added to the first visualization 400 .
[0119] exist Figure 6-7 The following table shows a representative method for implementing Figure 1A-2 100 of the VA 100. The machine-readable instructions may be an executable program or a portion of an executable program for execution by a computer processor, such as the following in combination with Figure 8The processor 812 shown in the exemplary processor platform 800 discussed above. The program may be embodied in software stored in a non-transitory computer-readable storage medium, such as a CD-ROM, floppy disk, hard drive, DVD, Blu-ray disk, or memory associated with the processor 812, but the entire program and / or portions thereof may alternatively be executed by a device other than the processor 812 and / or embodied in firmware or dedicated hardware. In addition, although reference is made to Figure 6-7 The flowchart shown in describes an exemplary procedure, but many other methods of implementing the exemplary VA 100 may alternatively be used. For example, the order of execution of the blocks may be changed, and / or some of the blocks described may be changed, eliminated, or combined. Additionally or alternatively, any or all of the blocks may be implemented by one or more hardware circuits (e.g., discrete and / or integrated analog and / or digital circuits, FPGAs, ASICs, comparators, operational amplifiers (op-amps), logic circuits, etc.) configured to perform corresponding operations without executing software or firmware.
[0120] As mentioned above, Figure 6-7 The exemplary processes of can be implemented using executable instructions (e.g., computer and / or machine readable instructions) stored on a non-transitory computer and / or machine readable medium, such as a hard drive, flash memory, read-only memory, compact disk, digital versatile disk, cache, random access memory, and / or any other storage device or storage disk that stores information for any duration (e.g., for an extended period of time, permanently, transiently, temporarily buffered and / or cached information). As used herein, the term "non-transitory computer readable medium" is expressly defined to include any type of computer readable storage device and / or storage disk, and to exclude propagating signals and to exclude transmission media.
[0121] "Include" and "comprising" (and all their forms and tenses) are used herein as open-ended terms. Thus, whenever a claim employs any form of "include" or "comprising" (e.g., includes, comprises, has, etc.) as a preamble to any type of claim recitation or in any type of claim recitation, it should be understood that additional elements, items, etc. may be present without exceeding the scope of the corresponding claim or recitation. As used herein, when the phrase "at least" is used as a transition word, such as in the preamble of a claim, it is open-ended in the same manner as the terms "include" and "comprising" are open-ended. When the term "and / or" is used, such as in a form such as A, B, and / or C, it refers to any combination or subset of A, B, and C, such as (1) only A, (2) only B, (3) only C, (4) A and B, (5) A and C, (6) B and C, and (7) A and B and C. As used herein in the context of describing structures, components, items, objects, and / or things, the phrase "at least one of A and B" is intended to refer to embodiments that include any of the following: (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. Similarly, as used herein in the context of describing structures, components, items, objects, and / or things, the phrase "at least one of A or B" is intended to refer to embodiments that include any of the following: (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. As used herein in the context of describing the execution or performance of processes, instructions, actions, activities, and / or steps, the phrase "at least one of A or B" is intended to refer to embodiments that include any of the following: (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. Similarly, as used herein in the context of describing the execution or implementation of a process, instruction, action, activity, and / or step, the phrase "at least one of A or B" is intended to refer to an implementation that includes any of the following: (1) at least one A, (2) at least one B, and (3) at least one A and at least one B.
[0122] Figure 6 is a flow chart representing example machine readable instructions 600 that may be executed to implement Figure 1A-2 The VA 100 generates and executes a script based on a request. The machine-readable instructions 600 begin at block 602, where the VA 100 determines whether a request has been received. For example, Figure 2 The framework controller 212 may determine that the user 104 sends a signal to the VA 100 via one of the wearable devices 128, 130, 132, the DCS controller component 226, etc. Figure 2 The first request 201a to open Figure 1AIn other examples, the framework controller 212 may determine that the host application 106 generates a second request 201 b to the VA 100 to open the first field device 116 .
[0123] If at block 602, the VA 100 determines that a request has not been received, the VA 100 continues to wait for a request. If at block 602, the VA 100 determines that a request has been received, at block 604, the VA 100 parses the request. For example, Figure 2 The parser 214 of the VA 100 may parse the request 201a-b into one or more vocabulary units. In response to parsing the request at block 604, the VA 100 validates the request at block 606. For example, Figure 2 The analyzer 216 may compare the one or more vocabulary units to valid vocabulary units.
[0124] At block 608, the VA 100 determines whether the request is validated. For example, the analyzer 216 may determine that the request 201a-b is invalid by determining that one or more vocabulary units are invalid, the order of vocabulary units is not a valid order, etc. based on a comparison of the analyzed vocabulary units with valid vocabulary units. In other examples, the analyzer 216 may determine that the request 201a-b is valid based on identifying one or more analyzed vocabulary units as valid vocabulary units. In other words, the analyzer 216 may determine that the request 201a-b is valid based on the identification of (one or more) validated vocabulary units.
[0125] If at block 608, the VA 100 determines that the request is not validated, control passes to block 610 to generate and send a clarification request. Figure 2 The generator 218 can generate a clarification request and send the clarification request to the user 104, the host application 106, one of the wearable devices 128, 130, 132, etc. In such examples, the clarification request can include a prompt to repeat the request, rephrase the request, provide another request, etc. In response to generating and sending the clarification request, control returns to determine whether another request is received at block 602.
[0126] If at block 608, the VA 100 determines that the request has been validated, then at block 612, the VA 100 determines whether the session state is available. For example, the session processor 238 may query Figure 2242 to determine whether the session has been instantiated and / or otherwise initialized. In such examples, the session processor 238 can determine that the session state is unavailable based on the fact that the session state handler 242 has not instantiated the session and has not stored and / or otherwise managed the corresponding session state. In other examples, the session processor 238 can determine that the session state is available based on the fact that the session state handler 242 has instantiated the session and has stored and / or otherwise managed the corresponding session state. For example, the session state handler 242 can send to the session processor 238 such as the session state of the topic, the completion status of the script, the action being executed by the action processor 240, etc.
[0127] If at block 612, the VA 100 determines that the session state is available, control passes to block 616 to identify the subject. If at block 612, the VA 100 determines that the session state is not available, at block 614, the VA 100 establishes the session state. For example, the session processor 238 may initialize the session and send the corresponding session state to the session state handler 242. In response to establishing the session state, the VA 100 identifies the subject at block 616. For example, the session processor 238 may identify the subject based on the session state from the session state handler 242. Figure 2 The server robot framework 210 obtains the processed request and identifies the subject of the first field device 116 .
[0128] At block 618, the VA 100 generates a script. For example, the session processor 238 may Figure 2 The topic 246 is mapped to Figure 2 The session processor 238 may generate a script that includes one or more configurations 248a, one or more scripts 248b, one or more actions 250, etc., and / or combinations thereof, in the session context database 244 of the subject 246. In such examples, the session processor 238 may package the script based on the mapping. For example, the session processor 238 may generate a script that includes one or more configurations 248a, one or more scripts 248b, one or more actions 250, etc., and / or combinations thereof, in which the subject 246 is mapped in the session context database 244.
[0129] In response to generating the script, VA 100 executes the script at block 620. For example, Figure 2 The action processor 240 can send Figure 2 The action processor 240 may generate a command to one of the systems 222 to facilitate execution of the script generated by the session processor 238. For example, the action processor 240 may generate a command to Figure 1A-1B The process control system 102 is configured to open the first field device 116 .
[0130] At block 622, the VA 100 updates the session state. For example, the session state handler 242 can update the session state to complete in response to opening the first field device 116. In other examples, the session state handler 242 can update the session state from opening the first field device 116 to the first field device 116 opened, the first field device 116 opened 95%, etc.
[0131] In response to updating the session state, at block 624, the VA 100 generates and sends a response to the requester. For example, the session processor 238 may package and send the response to the user 104, the host application 106, one of the wearable devices 128, 130, 132, Figure 2 The DCS controller component 226 , etc., indicates that the first field device 116 is open and / or the valve position of the first field device 116 .
[0132] At block 626, the VA 100 determines whether the script is complete. For example, the session state handler 242 may determine that the script associated with the request from the user 104, host application 106, etc. is complete based on the action processor 240 completing all actions included in the script. In other examples, the session state handler 242 may determine that the script is incomplete based on one or more actions to be completed by the action processor 240 and / or the user 104, host application 106, etc. did not issue a confirmation that the script is complete.
[0133] If at block 626, the VA 100 determines that the script is complete, control passes to block 630 to determine whether to continue monitoring requests. If at block 626, the VA 100 determines that the script is incomplete, at block 628, the VA 100 determines whether the requester terminated the session. For example, the session processor 238 may determine whether the user 104, the host application 106, etc., generated a command to the VA 100 to terminate the session.
[0134] At block 630, VA 100 determines whether to continue monitoring for requests. If at block 630, VA 100 determines to continue monitoring for requests, control returns to wait for another request and determines at block 602 whether another request is received. If at block 630, VA 100 determines not to continue monitoring for requests, then Figure 6 The machine readable instructions 600 end.
[0135] Figure 7 is a flow chart representing example machine readable instructions 700 that may be executed to implement Figure 1A-2 The VA 100 generates and displays visualizations based on requests. The machine-readable instructions 700 begin at block 702 where the VA 100 determines whether a request has been received. For example, Figure 2 The framework controller 212 may determine that the user 104 issued a verbal request to the VA 100 via the host application 106 to "show me the processing tank." In other examples, the framework controller 212 may determine that the host application 106 generated a request to the VA 100 to obtain information about the processing tank. Figure 1A-1B Information of processing tank 122.
[0136] If at block 702, the VA 100 determines that a request has not been received, the VA 100 continues to wait for a request. If at block 702, the VA 100 determines that a request has been received, at block 704, the VA 100 parses the request. For example, Figure 2 The parser 214 can Figure 2 201a-b into one or more vocabulary units. In response to the parsed request at block 704, VA 100 validates the request at block 706. For example, Figure 2 The analyzer 216 may compare one or more vocabulary units to valid vocabulary units.
[0137] At block 708, the VA 100 determines whether the request is validated. For example, the analyzer 216 may determine that the request is invalid by determining that one or more vocabulary units are invalid, the order of vocabulary units is not a valid order, etc. based on a comparison of the analyzed vocabulary units with valid vocabulary units. In other examples, the analyzer 216 may determine that the request 201a-b is valid based on identifying one or more analyzed vocabulary units as valid vocabulary units.
[0138] If at block 708, the VA 100 determines that the request is not validated, control passes to block 710 to generate and send a clarification request. Figure 2 The generator 218 may generate a clarification request and send the clarification request to the user 104, the host application 106, etc. In such examples, the clarification request may include a prompt to repeat the request 201a-b, to rephrase the request 201a-b, to provide another one of the requests 201a-b, etc. In response to generating and sending the clarification request, control returns to determine whether another request is received at block 702.
[0139] If at block 708, the VA 100 determines that the request is validated, then at block 712, the VA 100 determines whether the session state is available. For example, the session processor 238 may query Figure 2242 to determine whether the session has been instantiated and / or otherwise initialized. In such examples, the session processor 238 can determine that the session state is unavailable based on the fact that the session state handler 242 has not instantiated the session and has not stored and / or otherwise managed the corresponding session state. In other examples, the session processor 238 can determine that the session state is available based on the fact that the session state handler 242 instantiated the session and stored and / or otherwise managed the corresponding session state. For example, the session state handler 242 can send to the session processor 238 the session state of the topic, the completion status of the script, the action executed by the action processor 240, and the like.
[0140] If at block 712, the VA 100 determines that the session state is available, control passes to block 716 to identify the subject. If at block 712, the VA 100 determines that the session state is not available, at block 714, the VA 100 establishes the session state. For example, the session processor 238 may initialize the session and send the corresponding session state to the session state handler 242. In response to establishing the session state, the VA 100 identifies the subject at block 716. For example, the session processor 238 may identify the subject based on the session state from the session state handler 242. Figure 2 The server robot framework 210 obtains the processed request and identifies the subject of the processing tank 122 .
[0141] In response to identifying the topic, at block 718, the VA 100 maps the topic to a profile. For example, the session processor 238 may map the topic of the process tank 122 to a Figure 2 The session context database 244 Figure 3 In such examples, the session processor 238 can determine, based on the mapping, that the identified subject included in the request from the user 104, the host application 106, etc. corresponds to the process tank 122. The session processor 238 can determine, based on the mapping, information associated with the process tank 122, including Figure 1A-1B The session processor 238 may determine which field devices in the process control system 102 are coupled to the process tank 122, which field devices in the process control system 102 are monitoring or performing measurements associated with the process tank 122, etc. Additionally or alternatively, the session processor 238 may determine information included in the profile 300, including parameters 306, tags 308, descriptions 310, etc.
[0142] At block 720, VA 100 generates a response corresponding to the level of the profile. For example, session processor 238 may package a response including information associated with L1 of profile 300. In such an example, the response may include information associated with Figure 3For example, the response may include at least one of a container level parameter, a container pressure parameter, a corresponding label 308, a corresponding description 310, and the like.
[0143] At block 722, the VA 100 sends the response to the host application. For example, the session processor 238 may send the response to the host application 106 via at least one of the host application bot framework 208 or the server bot framework 210. In such examples, the host application 106 may send the response to the host application 106 via Figure 1B The third wearable device 132, the mobile application 202, the browser application 204, the desktop application 206, etc. generate Figure 4 The host application 106 may display the first visualization 400 on a display of a camera, a mobile device, a desktop computer, a laptop computer, or any other display communicatively coupled to the computing device. In other examples, the session processor 238 may send a response to a server communicatively coupled to the host application 106. Figure 2 The host application 106 is run and / or otherwise executed on the HMI of the DCS controller component 226 .
[0144] At block 724, the VA 100 updates the session state. For example, the session processor 238 may instruct the session state handler 242 to update the session state based on the response. For example, the session state handler 242 may assign L1 to a session state indicating that information associated with L1 has been transmitted to a requestor, such as a user 104, a host application 106, etc. In other examples, the session state handler 242 may assign the subject of the processing tank 122 and / or L1 and / or information sent to the user 104, the host application 106, etc. to a session state.
[0145] At block 726 , the VA 100 displays the visualization on the host application based on the response. For example, the server bot framework 210 may send a response to the host application 106 instructing the host application 106 to display the first visualization 400 on a GUI, HMI, etc. on a device executing the host application 106 .
[0146] In response to displaying the visualization, the VA 100 determines at block 728 whether there are available levels to display. For example, the session processor 238 may determine that L2 has not yet been transmitted to the host application 106. In other examples, the session processor 238 may determine that parameters associated with L1, such as the vessel pressure parameter, have not yet been transmitted because the user 104, host application 106, etc., has only requested the vessel level parameter. In still other examples, the session processor 238 may determine that one of the categories 304 has not yet been transmitted based on requests for different categories in the categories 304. In such examples, the session processor 238 may determine to provide the user 104, host application 106, etc., with information that has not yet been requested, that has not yet been provided, etc., in response to a request for additional information associated with the process tank 122.
[0147] If at block 728, the VA 100 determines that there are no available levels to display, control proceeds to block 734 to determine whether to continue monitoring for requests. If at block 728, the VA 100 determines that there are available levels to display, then at block 730, the VA 100 determines whether a request for more information about the subject has been received. For example, the framework controller 212 may determine whether a request has been received from a user 104, a host application 106, etc. In response to determining that a request has been received, the session processor 238 may determine whether the request is associated with the subject of the process tank 122. If the session processor 238 determines that the request corresponds to a query for more information about the process tank 122, the session processor 238 may obtain a session state from the session state handler 242 in response to the request and determine information included in the profile 300 for packaging. For example, the session processor 238 may obtain a session state for L1 from the session state handler 242 and determine to package information associated with L2 in a response and send the response to the user 104, the host application 106, etc.
[0148] If at block 730, the VA 100 determines that the received request is for more information about the subject, control returns to block 720 to generate a response corresponding to the level of the profile. For example, the session processor 238 may package information associated with L2 of the profile 300 in the response, such as a container temperature parameter, a tag T XX27, etc., and / or a combination thereof. In other examples, the session processor 238 may package information associated with the balanced barrel category, another parameter, a tag, or a description associated with a common category, such as Figure 3In response to generating the response, the VA 100 may continue to send the response to the host application at block 722, update the session state at block 724 (e.g., update the session state to L2, information associated with L1 and / or L2, etc.), and display the visualization on the host application 106 based on at least one of the third wearable device 132 or the host application 106 indicating that the visualization is to be displayed. For example, the VA 100 may instruct the host application 106 to display the visualization on a mobile device, a desktop computer, etc. executing the host application 106. Figure 5 A second visualization 500 .
[0149] If, at block 730, the VA 100 determines that the received request is not for more information about the subject, then at block 732, the VA 100 determines whether a request timeout has occurred. For example, the framework controller 212 may determine that no request has been received from the user 104, the host application 106, etc., within a threshold time period (e.g., 1 minute, 10 minutes, 60 minutes, etc.). In other examples, the session processor 238 may determine that a request has been received, but not for the subject of the process tank 122. In such examples, the session processor 238 may instruct the session state handler 242 to update the session state, replace the session state with a new subject, or disassociate the subject of the process tank 122 from the session state. In other examples, the session processor 238 may instruct the session state handler 242 to instantiate another session state to coexist with the session state associated with the process tank 122.
[0150] If a request timeout has not occurred at block 732, control returns to block 730 to wait for another request. If a request timeout has occurred at block 732, the VA 100 determines whether to continue monitoring for requests at block 734. For example, the frame controller 212 may determine to shut down the VA 100, switch the VA 100 to operate in a low power or sleep mode, etc.
[0151] If at block 734, the VA 100 determines to continue monitoring for requests, control returns to block 702 to wait for another request. If at block 734, the VA 100 determines not to continue monitoring for requests, then Figure 7 The machine readable instructions 700 end.
[0152] Figure 8 is constructed to execute Figure 6-7 Instructions to achieve Figure 1A-2 100. The processor platform 800 may be, for example, a server, a personal computer, a workstation, a DCS controller component (e.g., Figure 2DCS controller component 226), self-learning machines (e.g., neural networks), mobile devices (e.g., cell phones, smart phones, such as iPads TM 1 ), a personal digital assistant (PDA), an Internet device, a headset or other wearable device (e.g., wearable devices 128, 130, 132 of FIG. 1 ), or any other type of computing device.
[0153] The processor platform 800 of the illustrated example includes a processor 812. The processor 812 of the illustrated example is hardware. For example, the processor 812 can be implemented by one or more integrated circuits, logic circuits, microprocessors, GPUs, DSPs, or controllers from any desired series or manufacturer. The hardware processor can be a semiconductor-based (e.g., silicon-based) device. In this example, the processor 812 implements the server robot framework 210, the framework controller 212, the parser 214, the analyzer 216, the generator 218, the executor 220, the session context engine 224, the session processor 238, the action processor 240, the session state handler 242, and / or more generally, the VA 100.
[0154] The processor 812 of the illustrated example includes a local memory 813 (e.g., a cache). The processor 812 of the illustrated example communicates with a main memory including a volatile memory 814 and a non-volatile memory 816 via a bus 818. The volatile memory 814 may be comprised of a synchronous dynamic random access memory (SDRAM), a dynamic random access memory (DRAM), Dynamic Random Access Memory The non-volatile memory 816 may be implemented by flash memory and / or any other desired type of storage device. Access to the main memory 814, 816 is controlled by a memory controller.
[0155] The processor platform 800 of the illustrated example also includes an interface circuit 820. The interface circuit 820 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), interface, near field communication (NFC) interface, and / or PCI Express interface.
[0156] In the example shown, one or more input devices 822 are connected to the interface circuit 820. The input device(s) 822 allow a user to enter data and / or commands into the processor 812. The input device(s) 822 may be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, buttons, a mouse, a touch screen, a trackpad, a trackball, an isopoint device, and / or a voice recognition system.
[0157] One or more output devices 824 are also connected to the interface circuit 820 of the illustrated example. The output device 824 can be implemented, for example, by a display device (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display (LCD), a cathode ray tube display (CRT)), an in-place switch (IPS) display, a touch screen, etc.), a tactile output device, a printer, and / or a speaker. Therefore, the interface circuit 820 of the illustrated example typically includes a graphics driver card, a graphics driver chip, and / or a graphics driver processor.
[0158] The interface circuitry 820 of the illustrated example also includes communication devices, such as transmitters, receivers, transceivers, modems, residential gateways, wireless access points, and / or network interfaces to facilitate the exchange of data with external machines (e.g., any kind of computing device) via the network 826. Communications may be through, for example, an Ethernet connection, a digital subscriber line (DSL) connection, a telephone line connection, a coaxial cable system, a satellite system, a field line wireless system, a cellular telephone system, etc.
[0159] The processor platform 800 of the illustrated example also includes one or more mass storage devices 828 for storing software and / or data. Examples of such mass storage devices 828 include floppy disk drives, hard disk drives, optical disk drives, Blu-ray disk drives, redundant array of independent disks (RAID) systems, and digital versatile disk (DVD) drives. In this example, the mass storage device 828 implements Figure 2 The session context database 244 includes Figure 2 (one or more) models 243.
[0160] You can Figure 6-7 The machine-executable instructions 832 of the computer program product are stored in the mass storage device 828, in the volatile memory 814, in the non-volatile memory 816, and / or on a removable, non-transitory computer-readable storage medium such as a CD or DVD.
[0161] In light of the foregoing, it will be appreciated that exemplary systems, methods, devices, and articles for enhancing process control using a process control virtual assistant have been disclosed. The process control virtual assistant disclosed herein corresponds to a system that enables applications such as process control mobile applications, browser applications, and / or desktop applications to, for example, initiate a session with a robot or robot framework that assists a user in performing tasks associated with process control in a process control environment. The disclosed process control virtual assistant may return parameters, historical data, alarms, or other information specific to a process control component, including equipment, field devices, control strategies, or batches. In some disclosed examples, a basic script may return information including parameters, and a complex script may additionally create a workflow that may in turn execute additional automation scripts to guide a user through a more complex sequence of process control tasks or instructions.
[0162] The examples disclosed herein provide a process-centric virtual assistant framework that can be used to support roles specific to process operations, including engineers, environmental experts, operators, maintenance personnel, supervisors, and the like. The examples disclosed herein identify process control components, actions, tasks, and the like in response to requests from users and / or host applications executed on computing devices. The examples disclosed herein enable a set of actions to be triggered on process components, enabling profiles of information to be returned on process components and / or enabling users to view visualizations of returned information. The examples disclosed herein support multiple users and / or multiple platforms. The examples disclosed herein include a DCS controller component that implements the disclosed process control virtual assistant, which can be set in one or more locations in a process control environment that can be connected via a process control network to facilitate and / or otherwise enhance process control.
[0163] Although certain exemplary systems, methods, devices, and articles have been disclosed herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all systems, methods, devices, and articles that fully fall within the scope of the claims of this patent.
Claims
1. An apparatus for enhancing process control using a virtual assistant, the apparatus comprising: at least one processor; as well as A memory storing instructions, which, when executed, cause the at least one processor to perform the following operations: determining a context of a request for information associated with a field device of a process control system; identifying a subject associated with the request, the subject corresponding to the field device based on the context; mapping the subject to at least one of an action associated with a function to be performed by the field device or a parameter associated with a process control value associated with the field device; generating a profile based on at least one of the action or the parameter; generating a command based on the profile; as well as The command is sent to the field device.
2. The device according to claim 1, wherein: The request is a verbal request transmitted to an input / output module of a programmable logic controller, at least one of the input / output modules of the programmable logic controller including at least one of a microphone or a speaker.
3. The device according to claim 1, wherein: The request is a verbal request transmitted to a wearable device including at least one of a display, a microphone, or a speaker.
4. The device according to claim 1, wherein: The instructions, when executed, further cause the at least one processor to perform the following operations: Establishing a conversation state based on the topic; generating a response including the session state; sending the response to a computing device; and Based on the response, a visualization is displayed on a display associated with the computing device.
5. The device according to claim 1, wherein: The profile includes at least a first level and a second level, and wherein the instructions, when executed, further cause the at least one processor to: mapping the subject matter to the first level; generating a response including data associated with the first level; sending the response to a computing device; and A visualization is displayed on a display associated with the computing device based on the data.
6. The device according to claim 5, wherein: The request is a first request, the data is first data, and the visualization is a first visualization, and wherein the instructions, when executed, further cause the at least one processor to: receiving a second request associated with the subject matter; mapping the second request to the second level; generating a second response including second data associated with the second level; sending the second response to the computing device; and Based on the second data, the first visualization is replaced with a second visualization on the display associated with the computing device.
7. A method for enhancing process control using a virtual assistant, the method comprising: determining a context associated with a request for information associated with a field device of a process control system; identifying a subject associated with the request, the subject corresponding to the field device based on the context; mapping the subject to at least one of an action associated with a function to be performed by the field device or a parameter associated with a process control value associated with the field device; generating a profile based on at least one of the action or the parameter; generating a command based on the profile; as well as The command is sent to the field device.
8. The method according to claim 7, wherein: The request is a verbal request that is transmitted to the programmable logic controller.
9. The method according to claim 7, wherein: The request is a verbal request transmitted to the wearable device corresponding to the glasses, headphones, or wristband.
10. The method according to claim 7, further comprising: Establishing a conversation state based on the topic; generating a response including the session state; sending the response to a computing device; as well as Based on the response, a visualization is displayed on a display associated with the computing device.
11. The method according to claim 7, wherein: The profile comprises at least a first level and a second level, and further comprises: mapping the subject matter to the first level; generating a response including data associated with the first level; sending the response to a computing device; and A visualization is displayed on a display associated with the computing device based on the data.
12. The method according to claim 11, wherein: The request is a first request, the data is first data, and the visualization is a first visualization, and the method further comprises: receiving a second request associated with the subject matter; mapping the second request to the second level; generating a second response including second data associated with the second level; sending the second response to the computing device; and Based on the second data, the first visualization is replaced with a second visualization on the display associated with the computing device.
13. The method according to claim 7, wherein: Determining the context includes: parsing the request into one or more vocabulary units including a first vocabulary unit; validating the request by identifying the first vocabulary unit as a validated vocabulary unit; and In response to validating that the request is valid based on identifying the first vocabulary unit as a validated vocabulary unit, a script including the action is generated.
14. The method according to claim 13, wherein: The request is a first request, and the method further comprises: In response to not verifying that the first request is valid, generating a response corresponding to the clarification request; sending the response to a computing device associated with the user; receiving a second request from the computing device, the second request being from the user; verifying the second request; and The script is generated based on the second request.
15. A non-transitory computer-readable storage medium comprising instructions that, when executed, cause a machine to at least: determining a context of a request for information associated with a field device of a process control system; identifying a subject associated with the request, the subject corresponding to the field device based on the context; mapping the subject to at least one of an action associated with a function to be performed by the field device or a parameter associated with a process control value associated with the field device; generating a profile based on at least one of the action or the parameter; generating a command based on the profile; as well as The command is sent to the field device.
16. The non-transitory computer-readable storage medium of claim 15, wherein: The request is a verbal request that is transmitted to the programmable logic controller.
17. The non-transitory computer-readable storage medium of claim 15, wherein: The request is a verbal request transmitted to the wearable device.
18. The non-transitory computer-readable storage medium of claim 15, further comprising instructions that when executed cause the machine to at least: Establishing a conversation state based on the topic; generating a response including the session state; sending the response to a computing device; and Based on the response, a visualization is displayed on a display associated with the computing device.
19. The non-transitory computer-readable storage medium of claim 15, wherein: The profile includes at least a first level and a second level, and the computer-readable storage medium further includes instructions that, when executed, cause the machine to at least: mapping the subject matter to the first level; generating a response including data associated with the first level; sending the response to a computing device; as well as A visualization is displayed on a display associated with the computing device based on the data.
20. The non-transitory computer-readable storage medium of claim 19, wherein: The request is a first request, the data is first data, and the visualization is a first visualization, and the computer-readable storage medium further includes instructions that, when executed, cause the machine to at least: receiving a second request associated with the subject matter; mapping the second request to the second level; generating a second response including second data associated with the second level; sending the second response to the computing device; as well as Based on the second data, the first visualization is replaced with a second visualization on the display associated with the computing device.
21. The non-transitory computer-readable storage medium of claim 15, further comprising instructions that when executed cause the machine to at least: parsing the request into one or more vocabulary units including a first vocabulary unit; validating the request by mapping the first vocabulary unit to a validated vocabulary unit; and In response to verifying that the request is valid based on the mapping, a script including the action is generated.
22. The non-transitory computer-readable storage medium of claim 21, wherein: The request is a first request, and the computer-readable storage medium further includes instructions that, when executed, cause the machine to at least: When the first request is not verified to be valid based on the mapping, generating a response corresponding to the clarification request; sending the response to a computing device associated with the user; receiving a second request from the computing device, the second request being from the user; verifying the second request; as well as The script is generated based on the second request.
Citation Information
Patent Citations
Clarifying natural language input using targeted questions
US20140316764A1
Intelligent assistant for home automation
US20150348554A1
