US20200074828A1 - Technologies for managing safety at industrial sites - Google Patents
Technologies for managing safety at industrial sites Download PDFInfo
- Publication number
- US20200074828A1 US20200074828A1 US16/120,863 US201816120863A US2020074828A1 US 20200074828 A1 US20200074828 A1 US 20200074828A1 US 201816120863 A US201816120863 A US 201816120863A US 2020074828 A1 US2020074828 A1 US 2020074828A1
- Authority
- US
- United States
- Prior art keywords
- industrial site
- compute device
- condition data
- compute
- received
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B21/00—Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
- G08B21/02—Alarms for ensuring the safety of persons
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM]
- G05B19/4184—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM] characterised by fault tolerance, reliability of production system
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
- G05B19/0428—Safety, monitoring
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
- G05B19/058—Safety, monitoring
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B27/00—Alarm systems in which the alarm condition is signalled from a central station to a plurality of substations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1408—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
- H04L63/1425—Traffic logging, e.g. anomaly detection
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/24—Pc safety
- G05B2219/24094—Voice alarm
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/30—Nc systems
- G05B2219/31—From computer integrated manufacturing till monitoring
- G05B2219/31359—Object oriented model for fault, quality control
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/30—Nc systems
- G05B2219/37—Measurements
- G05B2219/37337—Noise, acoustic emission, sound
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/30—Nc systems
- G05B2219/45—Nc applications
- G05B2219/45103—Security, surveillance applications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Definitions
- safety practices such as human hazard reporting and safety observation tours (SOTs) address safety hazards as they are identified and dealt with.
- SOTs safety observation tours
- accidents, near misses, and contamination issues still occur.
- safety issues are addressed with quick fixes that result in corrosion of metal, overstressing of electrical systems, and other conditions that eventually lead to equipment malfunctions and new safety hazards.
- some facilities may include sensors to identify specific, isolated safety concerns, such as ingress of liquid past a predefined boundary or electrical overloads, complex and slowly developing safety issues at an industrial site may go unnoticed.
- the present disclosure provides a method for managing safety at an industrial site.
- the method includes receiving, by a compute device in a cloud data center, condition data indicative of a sensed or determined condition at an industrial site.
- the condition data was produced at least in part by an edge device at the industrial site.
- the method also includes analyzing, by the compute device and with a model that associates conditions with corresponding safety statuses, the received condition data to determine a corresponding safety status associated with the industrial site. Further, the method includes determining, by the compute device and as a function of the determined safety status, whether a responsive action is to be performed at the industrial site. Additionally, the method includes sending, by the compute device, to the edge device at the industrial site and in response to a determination that a responsive action is to be performed at the industrial site, responsive data indicative of the responsive action to be performed.
- the present disclosure provides a compute device for a cloud data center.
- the compute device includes a compute engine configured to receive condition data indicative of a sensed or determined condition at an industrial site.
- the condition data was produced at least in part by an edge device at the industrial site.
- the compute engine is further to analyze, with a model that associates conditions with corresponding safety statuses, the received condition data to determine a corresponding safety status associated with the industrial site.
- the compute engine is to determine, as a function of the determined safety status, whether a responsive action is to be performed at the industrial site, and send, to the edge device at the industrial site and in response to a determination that a responsive action is to be performed at the industrial site, responsive data indicative of the responsive action to be performed.
- the present disclosure provides one or more machine-readable storage media including a plurality of instructions stored thereon that, in response to being executed, cause a compute device to receive condition data indicative of a sensed or determined condition at an industrial site.
- the condition data was produced at least in part by an edge device at the industrial site.
- the instructions also cause the compute device to analyze, with a model that associates conditions with corresponding safety statuses, the received condition data to determine a corresponding safety status associated with the industrial site, determine, as a function of the determined safety status, whether a responsive action is to be performed at the industrial site, and send, to the edge device at the industrial site and in response to a determination that a responsive action is to be performed at the industrial site, responsive data indicative of the responsive action to be performed.
- FIG. 1 is a simplified block diagram of at least one embodiment of a system for managing safety at multiple industrial sites
- FIG. 2 is a simplified block diagram of at least one embodiment of an edge device of the system of FIG. 1 ;
- FIG. 3 is a simplified block diagram of a compute device of the system of FIG. 1 ;
- FIGS. 4-6 are a simplified flow diagram of at least one embodiment of a method for managing safety at one or more industrial sites that may be performed by a compute device of FIGS. 1 and 3 .
- references in the specification to “one embodiment,” “an embodiment,” “an illustrative embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may or may not necessarily include that particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
- items included in a list in the form of “at least one A, B, and C” can mean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).
- items listed in the form of “at least one of A, B, or C” can mean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).
- the disclosed embodiments may be implemented, in some cases, in hardware, firmware, software, or any combination thereof.
- the disclosed embodiments may also be implemented as instructions carried by or stored on a transitory or non-transitory machine-readable (e.g., computer-readable) storage medium, which may be read and executed by one or more processors.
- a machine-readable storage medium may be embodied as any storage device, mechanism, or other physical structure for storing or transmitting information in a form readable by a machine (e.g., a volatile or non-volatile memory, a media disc, or other media device).
- a system 100 for managing safety at multiple industrial sites includes cloud data centers 110 , 120 , 122 , each of which includes a set of compute devices 170 capable of executing workloads (e.g., applications) to analyze data received from edge devices 130 , 132 , 134 , 136 , 140 , 142 , 144 , 146 located at industrial sites 180 , 182 .
- workloads e.g., applications
- the edge devices 130 , 132 , 134 , 136 , 140 , 142 , 144 , 146 which may be embodied as relatively-resource constrained devices (e.g., having less compute and memory capacity than the compute devices 170 ), may report, to a corresponding local (e.g., on premise or within a predefined range that is closer to the industrial site 180 , 182 than the cloud data center 110 ) data indicative of conditions at the corresponding industrial sites 180 , 182 .
- the data may be produced by one or more sensors (e.g., visual sensors, audio sensors, thermal sensors, etc.) in each edge device 130 , 132 , 134 , 136 , 140 , 142 , 144 , 146 or entered by a human operator (e.g., as a result of an inspection at the industrial site 180 , 182 ).
- the compute devices 170 in the corresponding local cloud data center 120 , 122 aggregate the received data and apply a model (e.g., a neural network or other artificial intelligence-based model to determine whether a safety hazard exists or is developing).
- a model e.g., a neural network or other artificial intelligence-based model to determine whether a safety hazard exists or is developing.
- the compute devices 170 of a cloud data center 120 , 122 may receive feedback from a human operator (e.g., an expert) and/or from a higher level cloud data center (e.g., the cloud data center 110 , which may utilize a model that has been trained on a larger data set) to identify the presence or development of a safety hazard.
- the compute devices 170 may issue responsive data to the edge devices to take a remedial action, such as broadcasting a warning to avoid a particular safety zone 150 , 152 , 154 , 156 that is affected by a safety hazard, deactivating one or more systems in an affected safety zone, or taking other actions, as described herein.
- the cloud data centers 110 , 120 , 122 refine their models to more accurately identify safety hazards and provide improved safety management over conventional safety management systems.
- the edge device 130 may be embodied as any type of device (e.g., a computer) capable of performing the functions described herein, including sensing one or more conditions in an industrial site 180 , reporting the condition to a local cloud data center 120 , receiving responsive data indicative of an action to be performed to mitigate an identified safety hazard, and performing the action.
- the illustrative edge device 130 includes a compute engine 210 , an input/output (I/O) subsystem 216 , communication circuitry 218 , and one or more data storage devices 222 .
- the edge device 130 may also contain one or more sensors 224 and/or one or more actuators 226 .
- the edge device 130 may include other or additional components, such as those commonly found in a computer, such as peripheral devices 228 . Additionally, in some embodiments, one or more of the illustrative components may be incorporated in, or otherwise form a portion of, another component.
- the compute engine 210 may be embodied as any type of device or collection of devices capable of performing various compute functions described below.
- the compute engine 210 may be embodied as a single device such as an integrated circuit, an embedded system, a field-programmable gate array (FPGA), a system-on-a-chip (SOC), or other integrated system or device.
- the compute engine 210 includes or is embodied as a processor 212 and a memory 214 .
- the processor 212 may be embodied as any type of processor capable of performing the functions described herein.
- the processor 212 may be embodied as a single or multi-core processor(s), a microcontroller, or other processor or processing/controlling circuit.
- the processor 212 may be embodied as, include, or be coupled to an FPGA, an application specific integrated circuit (ASIC), reconfigurable hardware or hardware circuitry, or other specialized hardware to facilitate performance of the functions described herein.
- ASIC application specific integrated circuit
- the main memory 214 may be embodied as any type of volatile (e.g., dynamic random access memory (DRAM), etc.) or non-volatile memory or data storage capable of performing the functions described herein. Volatile memory may be a storage medium that requires power to maintain the state of data stored by the medium. In some embodiments, all or a portion of the main memory 214 may be integrated into the processor 212 . In operation, the main memory 214 may store various software and data used during operation, such as sensor data, instructions for performing remedial actions to mitigate safety hazards, applications, programs, libraries, and drivers.
- DRAM dynamic random access memory
- the compute engine 210 is communicatively coupled to other components of the edge device 130 via the I/O subsystem 216 , which may be embodied as circuitry and/or components to facilitate input/output operations with the compute engine 210 (e.g., with the processor 212 and/or the main memory 214 ) and other components of the edge device 130 .
- the I/O subsystem 216 may be embodied as, or otherwise include, memory controller hubs, input/output control hubs, integrated sensor hubs, firmware devices, communication links (e.g., point-to-point links, bus links, wires, cables, light guides, printed circuit board traces, etc.), and/or other components and subsystems to facilitate the input/output operations.
- the I/O subsystem 216 may form a portion of a system-on-a-chip (SoC) and be incorporated, along with one or more of the processor 212 , the main memory 214 , and other components of the edge device 130 , into the compute engine 210 .
- SoC system-on-a-chip
- the communication circuitry 218 may be embodied as any communication circuit, device, or collection thereof, capable of enabling communications between the edge device 130 and another device (e.g., the compute devices 170 , other edge devices 132 , 134 , 136 , 140 , 142 , 144 , 146 , etc.).
- the communication circuitry 218 may be configured to use any one or more communication technology (e.g., wired or wireless communications) and associated protocols (e.g., Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.) to effect such communication.
- the illustrative communication circuitry 218 includes a network interface controller (NIC) 220 .
- the NIC 220 may be embodied as one or more add-in-boards, daughter cards, network interface cards, controller chips, chipsets, or other devices that may be used by the edge device 130 to connect with another device.
- the NIC 220 may be embodied as part of a system-on-a-chip (SoC) that includes one or more processors, or included on a multichip package that also contains one or more processors.
- SoC system-on-a-chip
- the NIC 220 may include a local processor (not shown) and/or a local memory (not shown) that are both local to the NIC 220 .
- the local processor of the NIC 220 may be capable of performing one or more of the functions of the compute engine 210 described herein. Additionally or alternatively, in such embodiments, the local memory of the NIC 220 may be integrated into one or more components of the edge device 130 at the board level, socket level, chip level, and/or other levels.
- the one or more illustrative data storage devices 222 may be embodied as any type of devices configured for short-term or long-term storage of data such as, for example, memory devices and circuits, memory cards, hard disk drives, solid-state drives, or other data storage devices.
- Each data storage device 222 may include a system partition that stores data and firmware code for the data storage device 222 .
- Each data storage device 222 may also include an operating system partition that stores data files and executables for an operating system.
- the edge device 130 may include one or more sensors 224 , each of which may be embodied as any device or circuitry configured to collect data indicative of conditions in an environment in which the sensor 224 is located.
- the edge device 130 may include a visual sensor 230 , which may be embodied as any device or circuitry (e.g., a camera) configured to obtain visual information (e.g., an image, a video, etc.) about the surrounding environment, such as chafing of nearby wires, corrosion of pipes, and/or other conditions.
- the edge device 130 may include an audio sensor 232 which may be embodied as any device or circuitry (e.g., a microphone) configured to obtain audio information (e.g., dripping sounds, squeaks, rattling, etc. of equipment) from the surrounding environment.
- the edge device 130 may include a thermal sensor 236 , which may be embodied as any device or circuitry (e.g., a thermometer) configured to obtain thermal information from the surrounding environment.
- the edge device 130 may additionally or alternatively include a leak sensor, which may be embodied as any device or circuitry (e.g., a device containing a ribbon with holes through which a liquid may pass, and a conductive solution that experiences a change in electrical resistivity as a result of the introduction of the liquid through the holes, etc.) capable of detecting the ingress of liquid or gas into an area. Additionally or alternatively, the edge device 130 may include other sensors that include devices and/or circuitry capable of detecting the presence of one or more other conditions in the environment.
- a leak sensor which may be embodied as any device or circuitry (e.g., a device containing a ribbon with holes through which a liquid may pass, and a conductive solution that experiences a change in electrical resistivity as a result of the introduction of the liquid through the holes, etc.) capable of detecting the ingress of liquid or gas into an area.
- the edge device 130 may include other sensors that include devices and/or circuitry capable of detecting the presence of one or more other conditions
- the edge device 130 may include one or more actuators 226 , each of which may be embodied as any mechanical or electromechanical device capable of physically controlling a mechanism or system, such as a valve or lock.
- the actuators 226 may include an electric actuator 240 (e.g., a device that is powered by a motor that converts electrical energy into mechanical torque), pneumatic actuator 242 (e.g., a device configured to convert energy formed by vacuum or compressed air into a linear or rotary motion), a hydraulic actuator 244 (e.g., a cylinder or fluid motor that uses hydraulic power to facilitate mechanical operation), and/or other actuators 246 .
- the edge device 130 may include one or more peripheral devices 228 .
- Such peripheral devices may include any type of peripheral device commonly found in a compute device such as a display or other output device and/or one more input devices, such as a touchscreen or buttons, forming a human-machine interface (HMI).
- the edge devices 132 , 134 , 136 , 140 , 142 , 144 , and 146 may have components similar to those described in FIG. 2 .
- the description of those components of the edge device 130 is equally applicable to the description of components of the edge devices 132 , 134 , 136 , 140 , 142 , 144 , and 146 and is not repeated herein for clarity of the description.
- each compute device 170 may be embodied as any type of device (e.g., a computer) capable of performing the functions described herein, including receiving data indicative of conditions at one or more industrial sites, determining from a model that relates condition data to safety statuses, whether a safety hazard is present at an industrial site, receiving feedback on the determination, adjusting the model as a function of the received feedback, and sending responsive data to one or more edge devices to perform an action to mitigate the safety hazard. As shown in FIG.
- the illustrative compute device 170 includes a compute engine 310 , an input/output (I/O) subsystem 316 , communication circuitry 318 , one or more data storage devices 322 , and peripheral devices 324 . Additionally, in some embodiments, one or more of the illustrative components may be incorporated in, or otherwise form a portion of, another component.
- the compute engine 310 may be embodied as any type of device or collection of devices capable of performing various compute functions described below and is similar to the compute engine 210 with reference to FIG. 2 .
- the compute engine 310 may be embodied as a single device such as an integrated circuit, an embedded system, a field-programmable gate array (FPGA), a system-on-a-chip (SOC), or other integrated system or device.
- the compute engine 310 includes or is embodied as a processor 312 and a memory 314 , similar to the processor 212 and memory 214 described with reference to FIG. 2 .
- the compute engine 310 is communicatively coupled to other components of the compute device 170 via the I/O subsystem 316 , which is similar to the I/O subsystem 216 described with reference to FIG. 2 .
- the communication circuitry 318 may be embodied as any communication circuit, device, or collection thereof, capable of enabling communications between the compute device 170 and another device (e.g., other compute devices 170 , the edge devices 130 , 132 , 134 , 136 , 140 , 142 , 144 , 146 , etc.).
- the communication circuitry 318 may be configured to use any one or more communication technology (e.g., wired or wireless communications) and associated protocols (e.g., Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.) to effect such communication.
- the illustrative communication circuitry 318 includes a network interface controller (NIC) 320 , similar to the NIC 220 described above with reference to FIG. 2 .
- the one or more illustrative data storage devices 322 are similar to the data storage devices 222 described above with reference to FIG. 2 and the peripheral devices 324 are similar to the peripheral devices 228 described above with reference to FIG. 2 .
- the edge devices 130 , 132 , 134 , 136 , 140 , 142 , 144 , 146 and the compute devices 170 may include other components, sub-components, and devices commonly found in a computing device, which are not discussed above in reference to the edge device 130 and compute device 170 and not discussed herein for clarity of the description.
- the edge devices 130 , 132 , 134 , 136 , 140 , 142 , 144 , 146 and the compute devices 170 are illustratively in communication via a network 160 , which may be embodied as any type of wired or wireless communication network, including global networks (e.g., the Internet), local area networks (LANs) or wide area networks ( 0 ), cellular networks (e.g., Global System for Mobile Communications (GSM), 3G, Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), etc.), digital subscriber line (DSL) networks, cable networks (e.g., coaxial networks, fiber networks, etc.), or any combination thereof.
- GSM Global System for Mobile Communications
- LTE Long Term Evolution
- WiMAX Worldwide Interoperability for Microwave Access
- DSL digital subscriber line
- cable networks e.g., coaxial networks, fiber networks, etc.
- a compute device 170 may perform a method 400 for managing safety at one or more industrial sites 180 , 182 .
- the method 400 begins with block 402 in which the compute device 170 determines whether to perform safety management.
- the compute device 170 may determine to perform safety management in response to a request from a user to do so, upon determining that a configuration setting has been set to a value indicative of an instruction to perform safety management, upon determining that the compute device 170 is communicatively coupled to the network 160 , and/or based on other factors.
- the method 400 advances to block 404 , in which the compute device 170 receives condition data indicative of sensed or determined conditions at one or more industrial sites (e.g., the industrial site 180 ).
- the compute device 170 may receive sensed data from one or more sensors (e.g., the sensors 230 ) at an industrial site 180 , 182 .
- the compute device 170 may receive an image of one or more components (e.g., wires, pipes, etc.), an audio sample (e.g., a sound of a particular component in a machine during operation), and/or a temperature measurement.
- the compute device 170 may receive data indicative of an analysis of one or more conditions at the industrial site 180 , 182 . In doing so, and as indicated in block 410 , the compute device 170 may receive analysis data from another device in the system 100 . For example, and as indicated in block 412 , the compute device 170 may receive analysis data from an edge device (e.g., the edge device 130 ) located at an industrial site (e.g., the industrial site 180 ).
- an edge device e.g., the edge device 130
- an edge device 130 may still perform an analysis of sensor data, such by performing a mathematical transformation of the sensed data, performing preprocessing such as object recognition and tagging, frequency analysis, or other preprocessing operations, and/or make an initial determination as to whether a particular condition or set of conditions represents a safety hazard.
- the compute device 170 may also receive analysis data produced by another compute device 170 , as indicated in block 414 .
- the compute device 170 may be located in the remote cloud data center 110 and receive analysis data from a compute device 170 in a local data center 120 , 122 .
- the compute device 170 may receive analysis data produced by a human (e.g., an analysis entered by a human into an edge device 136 located at an industrial site 180 , such as during a safety observation tour of the industrial site 180 ), as indicated in block 416 . Subsequently, the method 400 advances to block 418 of FIG. 5 , in which the compute device 170 analyzes the received condition data with a model that associates condition data with safety status data to determine a safety status of each industrial site 180 , 182 .
- a human e.g., an analysis entered by a human into an edge device 136 located at an industrial site 180 , such as during a safety observation tour of the industrial site 180
- the method 400 advances to block 418 of FIG. 5 , in which the compute device 170 analyzes the received condition data with a model that associates condition data with safety status data to determine a safety status of each industrial site 180 , 182 .
- the compute device 170 may perform a majority vote analysis to resolve conflicts in data received from multiple devices (e.g., ignoring data from one edge device 130 that conflicts with data received from multiple other edge devices 132 , 134 ), as indicated in block 420 . As indicated in block 422 , the compute device 170 , in the illustrative embodiment, compares the received data to known patterns indicative of corresponding safety statuses.
- the compute device 170 may compare the received data to patterns identified in condition data from other industrial sites (e.g., the industrial site 182 ) as being related to a particular safety hazard (e.g., early stages of wire chafing that could lead to an electrical system safety hazard, a mating of two metals on a pipe that will lead to corrosion and leaking of the pipe, a characteristic sound of a motor that is failing in a safety system, etc.), as indicated in block 424 . As indicated in block 426 , the compute device 170 may also receive data (e.g., to be incorporated into the model utilized to determine a safety status associated with the received condition data) from one or more external data sources, such as an external database.
- a particular safety hazard e.g., early stages of wire chafing that could lead to an electrical system safety hazard, a mating of two metals on a pipe that will lead to corrosion and leaking of the pipe, a characteristic sound of a motor that is failing in a safety
- the compute device 170 may receive data indicative of conditions that are typically associated with a particular safety status. In doing so, and as indicated in block 430 , the compute device 170 may receive data that associates visual, audio, thermal, or other types of phenomena (e.g., condition data) with a particular safety hazard. As indicated in block 432 , the compute device 170 may receive data that associates a set of phenomena (e.g., condition data) with a leak (e.g. an appearance or sound of a leaking pipe). Additionally or alternatively, the compute device 170 may receive data that associates a set of condition data with a predefined level of wear on a component, as indicated in block 434 .
- a set of phenomena e.g., condition data
- a leak e.g. an appearance or sound of a leaking pipe
- the compute device 170 may receive data that associates a set of condition data with a malfunction of a component, as indicated in block 436 . In analyzing the received condition data, the compute device 170 may determine whether a leak has occurred, as indicated in block 438 . Additionally or alternatively, the compute device 170 may determine whether a component will cause an unsafe condition within a predefined time period, as indicated in block 440 .
- the compute device 170 may determine, from visual or other data produced by sensors of a particular edge device 130 (e.g., a robot), whether the edge device 130 is entering a zone (e.g., the safety zone 152 ) from which humans should be evacuated (e.g., to enable the edge device 130 to safely perform an operation without endangering a human in the vicinity).
- a zone e.g., the safety zone 152
- the compute device 170 may receive feedback on the safety status determined in block 418 .
- the compute device 170 may send the received condition data (e.g., from block 404 ) and the determined safety status (e.g., that a leak has occurred) to a higher-level data center (e.g., from the data center 120 to the remote data center 110 ) for analysis, and subsequently receive feedback from the higher-level data center (e.g., that the condition data is actually indicative of a different safety hazard, that a leak is not present, etc.), as indicated in block 446 .
- the compute device 170 may receive feedback on the determined safety status from a human (e.g., an expert assigned to review determinations made by the compute device 170 ), as indicated in block 448 .
- the compute device 170 may update the model based on the received feedback (e.g., adjust weights in a neural network, etc.).
- the compute device 170 may update the model to produce, from the received condition data, a determination represented in the received feedback rather than the original determination made by the compute device 170 .
- the method 400 advances to block 452 of FIG. 6 , in which the compute device 170 determines whether a responsive action should be performed, based on the determination of the safety status.
- the compute device 170 may determine that a responsive action should be performed if the safety status indicates that a safety hazard is present or is developing.
- the method 400 advances to block 454 , in which the compute device 170 sends responsive data to the industrial site associated with the safety hazard (e.g., the industrial site 180 ).
- the compute device 170 may send instructions to warn one or more humans to avoid a predefined area (e.g., the safety zone 152 ) for a predefined time period (e.g., a specified number of hours, a specified number of days, etc.).
- the compute device 170 may send instructions for an edge device 130 to broadcast a warning to avoid the predefined area.
- the compute device 170 may send instructions to an edge device 130 to perform a corrective action to mitigate a safety hazard (e.g., to terminate a flow of liquid to a leaking pipe, to seal the leak, etc.), as indicated in block 460 .
- the compute device 170 may send instructions to deactivate one or more devices in a predefined area (e.g., the safety zone 152 ) of the industrial site 180 .
- the compute device 170 may distribute at least a portion of the model to other devices in the system 100 , as indicated in block 464 .
- the compute device 170 may distribute one or more portions of the model to another data center (e.g., send the portion of the model that was updated as a result of the feedback in block 450 to the data center 122 or the data center 110 ).
- the compute device 170 may distribute the portion of the model to one or more edge devices 130 , 132 , 134 , 136 , 140 , 142 , 144 , 146 (e.g., to enable those edge devices to correctly identify similar safety hazards in the future), as indicated in block 468 . Additionally, in doing so, the compute device 170 may select, for distribution, a portion of the model associated with a function of the corresponding edge device 130 that is to receive that portion of the model, as indicated in block 470 .
- an edge device 130 includes a camera and the compute device 170 determined that a leak is present based on visual information (e.g., an image or video) provided by the edge device 130 , the compute device 170 may send, to the edge device 130 , the portion of the model that was utilized to identify the condition as leak. Subsequently, the method 400 loops back to block 402 of FIG. 4 to determine whether to continue to perform safety management.
- visual information e.g., an image or video
Abstract
Description
- In typical industrial plants and food processing facilities, safety practices such as human hazard reporting and safety observation tours (SOTs) address safety hazards as they are identified and dealt with. However, despite these efforts, accidents, near misses, and contamination issues still occur. Often, safety issues are addressed with quick fixes that result in corrosion of metal, overstressing of electrical systems, and other conditions that eventually lead to equipment malfunctions and new safety hazards. Further, while some facilities may include sensors to identify specific, isolated safety concerns, such as ingress of liquid past a predefined boundary or electrical overloads, complex and slowly developing safety issues at an industrial site may go unnoticed.
- In one aspect, the present disclosure provides a method for managing safety at an industrial site. The method includes receiving, by a compute device in a cloud data center, condition data indicative of a sensed or determined condition at an industrial site. The condition data was produced at least in part by an edge device at the industrial site. The method also includes analyzing, by the compute device and with a model that associates conditions with corresponding safety statuses, the received condition data to determine a corresponding safety status associated with the industrial site. Further, the method includes determining, by the compute device and as a function of the determined safety status, whether a responsive action is to be performed at the industrial site. Additionally, the method includes sending, by the compute device, to the edge device at the industrial site and in response to a determination that a responsive action is to be performed at the industrial site, responsive data indicative of the responsive action to be performed.
- In another aspect, the present disclosure provides a compute device for a cloud data center. The compute device includes a compute engine configured to receive condition data indicative of a sensed or determined condition at an industrial site. The condition data was produced at least in part by an edge device at the industrial site. The compute engine is further to analyze, with a model that associates conditions with corresponding safety statuses, the received condition data to determine a corresponding safety status associated with the industrial site. Additionally, the compute engine is to determine, as a function of the determined safety status, whether a responsive action is to be performed at the industrial site, and send, to the edge device at the industrial site and in response to a determination that a responsive action is to be performed at the industrial site, responsive data indicative of the responsive action to be performed.
- In yet another aspect, the present disclosure provides one or more machine-readable storage media including a plurality of instructions stored thereon that, in response to being executed, cause a compute device to receive condition data indicative of a sensed or determined condition at an industrial site. The condition data was produced at least in part by an edge device at the industrial site. The instructions also cause the compute device to analyze, with a model that associates conditions with corresponding safety statuses, the received condition data to determine a corresponding safety status associated with the industrial site, determine, as a function of the determined safety status, whether a responsive action is to be performed at the industrial site, and send, to the edge device at the industrial site and in response to a determination that a responsive action is to be performed at the industrial site, responsive data indicative of the responsive action to be performed.
- The concepts described herein are illustrated by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. Where considered appropriate, reference labels have been repeated among the figures to indicate corresponding or analogous elements. The detailed description particularly refers to the accompanying figures in which:
-
FIG. 1 is a simplified block diagram of at least one embodiment of a system for managing safety at multiple industrial sites; -
FIG. 2 is a simplified block diagram of at least one embodiment of an edge device of the system ofFIG. 1 ; -
FIG. 3 is a simplified block diagram of a compute device of the system ofFIG. 1 ; and -
FIGS. 4-6 are a simplified flow diagram of at least one embodiment of a method for managing safety at one or more industrial sites that may be performed by a compute device ofFIGS. 1 and 3 . - While the concepts of the present disclosure are susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and will be described herein in detail. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives consistent with the present disclosure and the appended claims.
- References in the specification to “one embodiment,” “an embodiment,” “an illustrative embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may or may not necessarily include that particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. Additionally, it should be appreciated that items included in a list in the form of “at least one A, B, and C” can mean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C). Similarly, items listed in the form of “at least one of A, B, or C” can mean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).
- The disclosed embodiments may be implemented, in some cases, in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried by or stored on a transitory or non-transitory machine-readable (e.g., computer-readable) storage medium, which may be read and executed by one or more processors. A machine-readable storage medium may be embodied as any storage device, mechanism, or other physical structure for storing or transmitting information in a form readable by a machine (e.g., a volatile or non-volatile memory, a media disc, or other media device).
- In the drawings, some structural or method features may be shown in specific arrangements and/or orderings. However, it should be appreciated that such specific arrangements and/or orderings may not be required. Rather, in some embodiments, such features may be arranged in a different manner and/or order than shown in the illustrative figures. Additionally, the inclusion of a structural or method feature in a particular figure is not meant to imply that such feature is required in all embodiments and, in some embodiments, may not be included or may be combined with other features.
- Referring now to
FIG. 1 , asystem 100 for managing safety at multiple industrial sites includescloud data centers compute devices 170 capable of executing workloads (e.g., applications) to analyze data received fromedge devices industrial sites edge devices industrial site industrial sites edge device industrial site 180, 182). Thecompute devices 170 in the corresponding localcloud data center compute devices 170 of acloud data center cloud data center 110, which may utilize a model that has been trained on a larger data set) to identify the presence or development of a safety hazard. Thecompute devices 170 may issue responsive data to the edge devices to take a remedial action, such as broadcasting a warning to avoid aparticular safety zone cloud data centers - Referring now to
FIG. 2 , theedge device 130 may be embodied as any type of device (e.g., a computer) capable of performing the functions described herein, including sensing one or more conditions in anindustrial site 180, reporting the condition to a localcloud data center 120, receiving responsive data indicative of an action to be performed to mitigate an identified safety hazard, and performing the action. As shown inFIG. 2 , theillustrative edge device 130 includes acompute engine 210, an input/output (I/O)subsystem 216,communication circuitry 218, and one or moredata storage devices 222. Theedge device 130 may also contain one ormore sensors 224 and/or one ormore actuators 226. Of course, in other embodiments, theedge device 130 may include other or additional components, such as those commonly found in a computer, such asperipheral devices 228. Additionally, in some embodiments, one or more of the illustrative components may be incorporated in, or otherwise form a portion of, another component. - The
compute engine 210 may be embodied as any type of device or collection of devices capable of performing various compute functions described below. In some embodiments, thecompute engine 210 may be embodied as a single device such as an integrated circuit, an embedded system, a field-programmable gate array (FPGA), a system-on-a-chip (SOC), or other integrated system or device. Additionally, in some embodiments, thecompute engine 210 includes or is embodied as aprocessor 212 and amemory 214. Theprocessor 212 may be embodied as any type of processor capable of performing the functions described herein. For example, theprocessor 212 may be embodied as a single or multi-core processor(s), a microcontroller, or other processor or processing/controlling circuit. In some embodiments, theprocessor 212 may be embodied as, include, or be coupled to an FPGA, an application specific integrated circuit (ASIC), reconfigurable hardware or hardware circuitry, or other specialized hardware to facilitate performance of the functions described herein. - The
main memory 214 may be embodied as any type of volatile (e.g., dynamic random access memory (DRAM), etc.) or non-volatile memory or data storage capable of performing the functions described herein. Volatile memory may be a storage medium that requires power to maintain the state of data stored by the medium. In some embodiments, all or a portion of themain memory 214 may be integrated into theprocessor 212. In operation, themain memory 214 may store various software and data used during operation, such as sensor data, instructions for performing remedial actions to mitigate safety hazards, applications, programs, libraries, and drivers. - The
compute engine 210 is communicatively coupled to other components of theedge device 130 via the I/O subsystem 216, which may be embodied as circuitry and/or components to facilitate input/output operations with the compute engine 210 (e.g., with theprocessor 212 and/or the main memory 214) and other components of theedge device 130. For example, the I/O subsystem 216 may be embodied as, or otherwise include, memory controller hubs, input/output control hubs, integrated sensor hubs, firmware devices, communication links (e.g., point-to-point links, bus links, wires, cables, light guides, printed circuit board traces, etc.), and/or other components and subsystems to facilitate the input/output operations. In some embodiments, the I/O subsystem 216 may form a portion of a system-on-a-chip (SoC) and be incorporated, along with one or more of theprocessor 212, themain memory 214, and other components of theedge device 130, into thecompute engine 210. - The
communication circuitry 218 may be embodied as any communication circuit, device, or collection thereof, capable of enabling communications between theedge device 130 and another device (e.g., thecompute devices 170,other edge devices communication circuitry 218 may be configured to use any one or more communication technology (e.g., wired or wireless communications) and associated protocols (e.g., Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.) to effect such communication. - The
illustrative communication circuitry 218 includes a network interface controller (NIC) 220. TheNIC 220 may be embodied as one or more add-in-boards, daughter cards, network interface cards, controller chips, chipsets, or other devices that may be used by theedge device 130 to connect with another device. In some embodiments, theNIC 220 may be embodied as part of a system-on-a-chip (SoC) that includes one or more processors, or included on a multichip package that also contains one or more processors. In some embodiments, theNIC 220 may include a local processor (not shown) and/or a local memory (not shown) that are both local to theNIC 220. In such embodiments, the local processor of theNIC 220 may be capable of performing one or more of the functions of thecompute engine 210 described herein. Additionally or alternatively, in such embodiments, the local memory of theNIC 220 may be integrated into one or more components of theedge device 130 at the board level, socket level, chip level, and/or other levels. - The one or more illustrative
data storage devices 222 may be embodied as any type of devices configured for short-term or long-term storage of data such as, for example, memory devices and circuits, memory cards, hard disk drives, solid-state drives, or other data storage devices. Eachdata storage device 222 may include a system partition that stores data and firmware code for thedata storage device 222. Eachdata storage device 222 may also include an operating system partition that stores data files and executables for an operating system. - As discussed above, the
edge device 130 may include one ormore sensors 224, each of which may be embodied as any device or circuitry configured to collect data indicative of conditions in an environment in which thesensor 224 is located. Theedge device 130 may include a visual sensor 230, which may be embodied as any device or circuitry (e.g., a camera) configured to obtain visual information (e.g., an image, a video, etc.) about the surrounding environment, such as chafing of nearby wires, corrosion of pipes, and/or other conditions. Similarly, theedge device 130 may include anaudio sensor 232 which may be embodied as any device or circuitry (e.g., a microphone) configured to obtain audio information (e.g., dripping sounds, squeaks, rattling, etc. of equipment) from the surrounding environment. Additionally or alternatively, theedge device 130 may include athermal sensor 236, which may be embodied as any device or circuitry (e.g., a thermometer) configured to obtain thermal information from the surrounding environment. Theedge device 130 may additionally or alternatively include a leak sensor, which may be embodied as any device or circuitry (e.g., a device containing a ribbon with holes through which a liquid may pass, and a conductive solution that experiences a change in electrical resistivity as a result of the introduction of the liquid through the holes, etc.) capable of detecting the ingress of liquid or gas into an area. Additionally or alternatively, theedge device 130 may include other sensors that include devices and/or circuitry capable of detecting the presence of one or more other conditions in the environment. - Further, and as mentioned above, the
edge device 130 may include one ormore actuators 226, each of which may be embodied as any mechanical or electromechanical device capable of physically controlling a mechanism or system, such as a valve or lock. As such, theactuators 226 may include an electric actuator 240 (e.g., a device that is powered by a motor that converts electrical energy into mechanical torque), pneumatic actuator 242 (e.g., a device configured to convert energy formed by vacuum or compressed air into a linear or rotary motion), a hydraulic actuator 244 (e.g., a cylinder or fluid motor that uses hydraulic power to facilitate mechanical operation), and/orother actuators 246. Additionally or alternatively, theedge device 130 may include one or moreperipheral devices 228. Such peripheral devices may include any type of peripheral device commonly found in a compute device such as a display or other output device and/or one more input devices, such as a touchscreen or buttons, forming a human-machine interface (HMI). Theedge devices FIG. 2 . The description of those components of theedge device 130 is equally applicable to the description of components of theedge devices - Referring now to
FIG. 3 , eachcompute device 170 may be embodied as any type of device (e.g., a computer) capable of performing the functions described herein, including receiving data indicative of conditions at one or more industrial sites, determining from a model that relates condition data to safety statuses, whether a safety hazard is present at an industrial site, receiving feedback on the determination, adjusting the model as a function of the received feedback, and sending responsive data to one or more edge devices to perform an action to mitigate the safety hazard. As shown inFIG. 3 , theillustrative compute device 170 includes acompute engine 310, an input/output (I/O)subsystem 316,communication circuitry 318, one or moredata storage devices 322, andperipheral devices 324. Additionally, in some embodiments, one or more of the illustrative components may be incorporated in, or otherwise form a portion of, another component. - The
compute engine 310 may be embodied as any type of device or collection of devices capable of performing various compute functions described below and is similar to thecompute engine 210 with reference toFIG. 2 . As such, thecompute engine 310 may be embodied as a single device such as an integrated circuit, an embedded system, a field-programmable gate array (FPGA), a system-on-a-chip (SOC), or other integrated system or device. Additionally, in some embodiments, thecompute engine 310 includes or is embodied as aprocessor 312 and amemory 314, similar to theprocessor 212 andmemory 214 described with reference toFIG. 2 . Thecompute engine 310 is communicatively coupled to other components of thecompute device 170 via the I/O subsystem 316, which is similar to the I/O subsystem 216 described with reference toFIG. 2 . - The
communication circuitry 318 may be embodied as any communication circuit, device, or collection thereof, capable of enabling communications between thecompute device 170 and another device (e.g.,other compute devices 170, theedge devices communication circuitry 318 may be configured to use any one or more communication technology (e.g., wired or wireless communications) and associated protocols (e.g., Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.) to effect such communication. Theillustrative communication circuitry 318 includes a network interface controller (NIC) 320, similar to theNIC 220 described above with reference toFIG. 2 . Additionally, the one or more illustrativedata storage devices 322 are similar to thedata storage devices 222 described above with reference toFIG. 2 and theperipheral devices 324 are similar to theperipheral devices 228 described above with reference toFIG. 2 . It should be appreciated that theedge devices compute devices 170 may include other components, sub-components, and devices commonly found in a computing device, which are not discussed above in reference to theedge device 130 and computedevice 170 and not discussed herein for clarity of the description. - In the illustrative embodiment, the
edge devices compute devices 170 are illustratively in communication via anetwork 160, which may be embodied as any type of wired or wireless communication network, including global networks (e.g., the Internet), local area networks (LANs) or wide area networks (0), cellular networks (e.g., Global System for Mobile Communications (GSM), 3G, Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), etc.), digital subscriber line (DSL) networks, cable networks (e.g., coaxial networks, fiber networks, etc.), or any combination thereof. - Referring now to
FIG. 4 , a compute device 170 (e.g., in acloud data center method 400 for managing safety at one or moreindustrial sites method 400 begins withblock 402 in which thecompute device 170 determines whether to perform safety management. In the illustrative embodiment, thecompute device 170 may determine to perform safety management in response to a request from a user to do so, upon determining that a configuration setting has been set to a value indicative of an instruction to perform safety management, upon determining that thecompute device 170 is communicatively coupled to thenetwork 160, and/or based on other factors. Regardless, in response to a determination to perform safety management, themethod 400 advances to block 404, in which thecompute device 170 receives condition data indicative of sensed or determined conditions at one or more industrial sites (e.g., the industrial site 180). In doing so, and as indicated inblock 406, thecompute device 170 may receive sensed data from one or more sensors (e.g., the sensors 230) at anindustrial site compute device 170 may receive an image of one or more components (e.g., wires, pipes, etc.), an audio sample (e.g., a sound of a particular component in a machine during operation), and/or a temperature measurement. As indicated inblock 408, thecompute device 170 may receive data indicative of an analysis of one or more conditions at theindustrial site block 410, thecompute device 170 may receive analysis data from another device in thesystem 100. For example, and as indicated inblock 412, thecompute device 170 may receive analysis data from an edge device (e.g., the edge device 130) located at an industrial site (e.g., the industrial site 180). That is, while thecompute device 170 may utilize a model to analyze condition data as described in more detail herein, anedge device 130, with relatively constrained compute capacity, may still perform an analysis of sensor data, such by performing a mathematical transformation of the sensed data, performing preprocessing such as object recognition and tagging, frequency analysis, or other preprocessing operations, and/or make an initial determination as to whether a particular condition or set of conditions represents a safety hazard. Thecompute device 170 may also receive analysis data produced by anothercompute device 170, as indicated inblock 414. For example, thecompute device 170 may be located in the remotecloud data center 110 and receive analysis data from acompute device 170 in alocal data center compute device 170 may receive analysis data produced by a human (e.g., an analysis entered by a human into anedge device 136 located at anindustrial site 180, such as during a safety observation tour of the industrial site 180), as indicated inblock 416. Subsequently, themethod 400 advances to block 418 ofFIG. 5 , in which thecompute device 170 analyzes the received condition data with a model that associates condition data with safety status data to determine a safety status of eachindustrial site - Referring now to
FIG. 5 , in analyzing the received condition data, thecompute device 170 may perform a majority vote analysis to resolve conflicts in data received from multiple devices (e.g., ignoring data from oneedge device 130 that conflicts with data received from multipleother edge devices 132, 134), as indicated inblock 420. As indicated inblock 422, thecompute device 170, in the illustrative embodiment, compares the received data to known patterns indicative of corresponding safety statuses. In doing so, thecompute device 170 may compare the received data to patterns identified in condition data from other industrial sites (e.g., the industrial site 182) as being related to a particular safety hazard (e.g., early stages of wire chafing that could lead to an electrical system safety hazard, a mating of two metals on a pipe that will lead to corrosion and leaking of the pipe, a characteristic sound of a motor that is failing in a safety system, etc.), as indicated inblock 424. As indicated inblock 426, thecompute device 170 may also receive data (e.g., to be incorporated into the model utilized to determine a safety status associated with the received condition data) from one or more external data sources, such as an external database. For example, and as indicated inblock 428, thecompute device 170 may receive data indicative of conditions that are typically associated with a particular safety status. In doing so, and as indicated inblock 430, thecompute device 170 may receive data that associates visual, audio, thermal, or other types of phenomena (e.g., condition data) with a particular safety hazard. As indicated inblock 432, thecompute device 170 may receive data that associates a set of phenomena (e.g., condition data) with a leak (e.g. an appearance or sound of a leaking pipe). Additionally or alternatively, thecompute device 170 may receive data that associates a set of condition data with a predefined level of wear on a component, as indicated inblock 434. Similarly, thecompute device 170 may receive data that associates a set of condition data with a malfunction of a component, as indicated inblock 436. In analyzing the received condition data, thecompute device 170 may determine whether a leak has occurred, as indicated inblock 438. Additionally or alternatively, thecompute device 170 may determine whether a component will cause an unsafe condition within a predefined time period, as indicated inblock 440. In some embodiments, and as indicated inblock 442, thecompute device 170 may determine, from visual or other data produced by sensors of a particular edge device 130 (e.g., a robot), whether theedge device 130 is entering a zone (e.g., the safety zone 152) from which humans should be evacuated (e.g., to enable theedge device 130 to safely perform an operation without endangering a human in the vicinity). - Subsequently, as indicated in
block 444, thecompute device 170 may receive feedback on the safety status determined inblock 418. For example, thecompute device 170 may send the received condition data (e.g., from block 404) and the determined safety status (e.g., that a leak has occurred) to a higher-level data center (e.g., from thedata center 120 to the remote data center 110) for analysis, and subsequently receive feedback from the higher-level data center (e.g., that the condition data is actually indicative of a different safety hazard, that a leak is not present, etc.), as indicated inblock 446. Additionally or alternatively, thecompute device 170 may receive feedback on the determined safety status from a human (e.g., an expert assigned to review determinations made by the compute device 170), as indicated inblock 448. As indicated inblock 450, thecompute device 170 may update the model based on the received feedback (e.g., adjust weights in a neural network, etc.). For example, thecompute device 170 may update the model to produce, from the received condition data, a determination represented in the received feedback rather than the original determination made by thecompute device 170. Subsequently, themethod 400 advances to block 452 ofFIG. 6 , in which thecompute device 170 determines whether a responsive action should be performed, based on the determination of the safety status. - Referring now to
FIG. 6 , thecompute device 170 may determine that a responsive action should be performed if the safety status indicates that a safety hazard is present or is developing. In response to a determination that a responsive action should be performed, themethod 400 advances to block 454, in which thecompute device 170 sends responsive data to the industrial site associated with the safety hazard (e.g., the industrial site 180). In doing so, and as indicated inblock 456, thecompute device 170 may send instructions to warn one or more humans to avoid a predefined area (e.g., the safety zone 152) for a predefined time period (e.g., a specified number of hours, a specified number of days, etc.). For example, and as indicated inblock 458, thecompute device 170 may send instructions for anedge device 130 to broadcast a warning to avoid the predefined area. In some embodiments, thecompute device 170 may send instructions to anedge device 130 to perform a corrective action to mitigate a safety hazard (e.g., to terminate a flow of liquid to a leaking pipe, to seal the leak, etc.), as indicated inblock 460. As indicated inblock 462, thecompute device 170 may send instructions to deactivate one or more devices in a predefined area (e.g., the safety zone 152) of theindustrial site 180. - Subsequently, or if the
compute device 170 determined inblock 452, that a responsive action should not be performed, thecompute device 170 may distribute at least a portion of the model to other devices in thesystem 100, as indicated inblock 464. For example, and as indicated inblock 466, thecompute device 170 may distribute one or more portions of the model to another data center (e.g., send the portion of the model that was updated as a result of the feedback inblock 450 to thedata center 122 or the data center 110). Additionally or alternatively, thecompute device 170 may distribute the portion of the model to one ormore edge devices block 468. Additionally, in doing so, thecompute device 170 may select, for distribution, a portion of the model associated with a function of thecorresponding edge device 130 that is to receive that portion of the model, as indicated inblock 470. For example if anedge device 130 includes a camera and thecompute device 170 determined that a leak is present based on visual information (e.g., an image or video) provided by theedge device 130, thecompute device 170 may send, to theedge device 130, the portion of the model that was utilized to identify the condition as leak. Subsequently, themethod 400 loops back to block 402 ofFIG. 4 to determine whether to continue to perform safety management. - While certain illustrative embodiments have been described in detail in the drawings and the foregoing description, such an illustration and description is to be considered as exemplary and not restrictive in character, it being understood that only illustrative embodiments have been shown and described and that all changes and modifications that come within the spirit of the disclosure are desired to be protected. There exist a plurality of advantages of the present disclosure arising from the various features of the apparatus, systems, and methods described herein. It will be noted that alternative embodiments of the apparatus, systems, and methods of the present disclosure may not include all of the features described, yet still benefit from at least some of the advantages of such features. Those of ordinary skill in the art may readily devise their own implementations of the apparatus, systems, and methods that incorporate one or more of the features of the present disclosure.
Claims (22)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/120,863 US10573147B1 (en) | 2018-09-04 | 2018-09-04 | Technologies for managing safety at industrial sites |
PCT/US2019/049494 WO2020101791A2 (en) | 2018-09-04 | 2019-09-04 | Technologies for managing safety at industrial sites |
EP19883623.1A EP3847631A4 (en) | 2018-09-04 | 2019-09-04 | Technologies for managing safety at industrial sites |
CN201980057562.0A CN112703537B (en) | 2018-09-04 | 2019-09-04 | Techniques for managing security at an industrial site |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/120,863 US10573147B1 (en) | 2018-09-04 | 2018-09-04 | Technologies for managing safety at industrial sites |
Publications (2)
Publication Number | Publication Date |
---|---|
US10573147B1 US10573147B1 (en) | 2020-02-25 |
US20200074828A1 true US20200074828A1 (en) | 2020-03-05 |
Family
ID=69590850
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/120,863 Active US10573147B1 (en) | 2018-09-04 | 2018-09-04 | Technologies for managing safety at industrial sites |
Country Status (4)
Country | Link |
---|---|
US (1) | US10573147B1 (en) |
EP (1) | EP3847631A4 (en) |
CN (1) | CN112703537B (en) |
WO (1) | WO2020101791A2 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10795758B2 (en) * | 2018-11-20 | 2020-10-06 | Acronis International Gmbh | Proactive disaster recovery based on external event monitoring |
Family Cites Families (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000207019A (en) * | 1999-01-18 | 2000-07-28 | Toshiba Corp | Plant monitor device |
US7409318B2 (en) * | 2000-02-14 | 2008-08-05 | Nextnine Ltd. | Support network |
US7076400B2 (en) * | 2000-02-14 | 2006-07-11 | Nextnine Ltd. | Support network |
US7085684B2 (en) * | 2000-07-04 | 2006-08-01 | Asahi Kasei Engineering Corporation | System for diagnosing a facility apparatus |
TWI227399B (en) * | 2003-12-12 | 2005-02-01 | Ind Tech Res Inst | Real-time monitoring system for abnormal situation and method thereof and real-time monitoring interface for complex abnormal situation |
KR100839071B1 (en) * | 2004-05-13 | 2008-06-19 | 삼성전자주식회사 | A system and method for monitoring conditions of a processing tool |
US8378811B2 (en) * | 2005-03-11 | 2013-02-19 | Aframe Digital, Inc. | Mobile wireless customizable health and condition monitor |
US7660639B2 (en) * | 2006-03-27 | 2010-02-09 | Hitachi, Ltd. | Control system for control subject having combustion unit and control system for plant having boiler |
KR100928205B1 (en) * | 2007-06-05 | 2009-11-25 | 삼성전자주식회사 | Semiconductor manufacturing facility management system and its statistical process control method |
CN101577033A (en) * | 2009-05-26 | 2009-11-11 | 官洪运 | Multiband infrared image-type fire detecting system and fire alarm system thereof |
US20140163759A1 (en) * | 2009-10-30 | 2014-06-12 | The Trustees Of Columbia University In The City Of New York | Digital building operating system with automated building and electric grid monitoring, forecasting, and alarm systems |
US9792808B2 (en) * | 2009-11-19 | 2017-10-17 | Honeywell International Inc. | Alert system with zoning using wireless portable detectors and a central station |
KR101388736B1 (en) * | 2009-12-21 | 2014-04-28 | 인텔 코오퍼레이션 | System and method for detecting and warning against a disaster |
US9361637B2 (en) * | 2010-03-05 | 2016-06-07 | Sears Brands, L.L.C. | System and method for providing diagnostic services |
US8599008B2 (en) * | 2010-07-26 | 2013-12-03 | General Electric Company | Appliance monitoring system and method |
US20130030875A1 (en) * | 2011-07-29 | 2013-01-31 | Panasonic Corporation | System and method for site abnormality recording and notification |
US20130027561A1 (en) * | 2011-07-29 | 2013-01-31 | Panasonic Corporation | System and method for improving site operations by detecting abnormalities |
US8786425B1 (en) * | 2011-09-09 | 2014-07-22 | Alarm.Com Incorporated | Aberration engine |
US8566165B1 (en) * | 2012-03-30 | 2013-10-22 | Palo Alto Research Center Incorporated | Performance-efficient system and method for sampling users for population-centric activity modeling |
US9041530B2 (en) * | 2012-04-18 | 2015-05-26 | Qualcomm Incorporated | Biometric attribute anomaly detection system with adjusting notifications |
US9424731B2 (en) * | 2012-08-01 | 2016-08-23 | Yosef Korakin | Multi level hazard detection system |
US20140214345A1 (en) * | 2013-01-25 | 2014-07-31 | Michael ORDANIS | System and method for monitoring an electrical network |
US20150355245A1 (en) * | 2013-01-25 | 2015-12-10 | Circuitmeter Inc. | System and method for monitoring an electrical network |
CN103150855B (en) * | 2013-02-01 | 2015-07-15 | 深圳市赋安安全系统有限公司 | Independent fire detection alarm and long-distance measuring and controlling method |
JP5914382B2 (en) * | 2013-02-20 | 2016-05-11 | 日立建機株式会社 | Status monitoring system, status monitoring device, and terminal device |
US10649424B2 (en) * | 2013-03-04 | 2020-05-12 | Fisher-Rosemount Systems, Inc. | Distributed industrial performance monitoring and analytics |
US8844050B1 (en) * | 2013-03-15 | 2014-09-23 | Athoc, Inc. | Personnel crisis communications management and personnel status tracking system |
US20140358592A1 (en) * | 2013-05-31 | 2014-12-04 | OneEvent Technologies, LLC | Sensors for usage-based property insurance |
US10984368B2 (en) * | 2013-08-07 | 2021-04-20 | Fedex Corporate Services, Inc. | Methods and systems for managing shipped objects |
CN103617710A (en) * | 2013-12-06 | 2014-03-05 | 文江湖 | Intelligent remote alarm system and intelligent remote alarm method |
US20150244598A1 (en) * | 2014-02-21 | 2015-08-27 | Endgame Systems, Inc. | Remote monitoring of events on a network using localized sensors |
CN103824131A (en) * | 2014-02-28 | 2014-05-28 | 西南石油大学 | System and method for predicating risks of drilling construction working site of oil-gas well |
US20160063387A1 (en) * | 2014-08-29 | 2016-03-03 | Verizon Patent And Licensing Inc. | Monitoring and detecting environmental events with user devices |
US20160063182A1 (en) * | 2014-08-29 | 2016-03-03 | Verizon Patent And Licensing Inc. | Monitoring and detecting anomalies in healthcare information |
US9719881B2 (en) * | 2014-08-29 | 2017-08-01 | Verizon Patent And Licensing Inc. | Scalable framework for managing civil structure monitoring devices |
US10223644B2 (en) * | 2014-09-29 | 2019-03-05 | Cisco Technology, Inc. | Behavioral modeling of a data center utilizing human knowledge to enhance a machine learning algorithm |
WO2016061365A1 (en) * | 2014-10-17 | 2016-04-21 | Avante International Technology, Inc. | Protective headgear including a personnel electronic monitor device |
JP2016107817A (en) * | 2014-12-05 | 2016-06-20 | ダイムラー・アクチェンゲゼルシャフトDaimler AG | In-vehicle accident prevention system |
US9613523B2 (en) * | 2014-12-09 | 2017-04-04 | Unilectric, Llc | Integrated hazard risk management and mitigation system |
GB201423300D0 (en) * | 2014-12-29 | 2015-02-11 | Sprue Safety Products Ltd | Multi alarm remote monitoring system |
US20180033275A1 (en) * | 2015-01-27 | 2018-02-01 | The Sociotech Institute (PTY) Ltd | An Early Warning Device for Detecting and Reporting Dangerous Conditions in a Community |
CN104852992B (en) * | 2015-06-09 | 2018-11-02 | 湖北天盾电子技术有限公司 | A kind of emergent on-line intelligence system of the safety based on multi communication network and sensing equipment |
US9904587B1 (en) * | 2015-12-18 | 2018-02-27 | Amazon Technologies, Inc. | Detecting anomalous behavior in an electronic environment using hardware-based information |
US9998804B2 (en) * | 2016-06-23 | 2018-06-12 | 3M Innovative Properties Company | Personal protective equipment (PPE) with analytical stream processing for safety event detection |
CN106202769A (en) * | 2016-07-15 | 2016-12-07 | 深圳市永达电子信息股份有限公司 | The industrial system detection method that a kind of on-line checking and simulation modeling checking combine |
US10298604B2 (en) * | 2016-09-05 | 2019-05-21 | Cisco Technology, Inc. | Smart home security system |
US10152394B2 (en) * | 2016-09-27 | 2018-12-11 | International Business Machines Corporation | Data center cost optimization using predictive analytics |
US9978256B1 (en) * | 2016-11-03 | 2018-05-22 | Tyco Fire & Security Gmbh | Method and system for monitoring fire alarm systems |
CA3065312A1 (en) * | 2017-05-31 | 2018-12-06 | Alarm.Com Incorporated | Occupancy simulation within a monitored property |
KR102017561B1 (en) * | 2017-08-10 | 2019-09-05 | 울랄라랩 주식회사 | Algorithm and method for detecting error data of machine based on machine-learning technique |
US10951639B2 (en) * | 2017-09-28 | 2021-03-16 | Yokogawa Electric Corporation | Systems, methods and computer program products for anomaly detection |
US10419313B2 (en) * | 2017-11-29 | 2019-09-17 | General Electric Company | Industrial network monitoring |
-
2018
- 2018-09-04 US US16/120,863 patent/US10573147B1/en active Active
-
2019
- 2019-09-04 CN CN201980057562.0A patent/CN112703537B/en active Active
- 2019-09-04 WO PCT/US2019/049494 patent/WO2020101791A2/en unknown
- 2019-09-04 EP EP19883623.1A patent/EP3847631A4/en active Pending
Also Published As
Publication number | Publication date |
---|---|
CN112703537B (en) | 2022-12-27 |
EP3847631A4 (en) | 2022-08-24 |
WO2020101791A3 (en) | 2020-06-25 |
EP3847631A2 (en) | 2021-07-14 |
CN112703537A (en) | 2021-04-23 |
US10573147B1 (en) | 2020-02-25 |
WO2020101791A2 (en) | 2020-05-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10599982B2 (en) | Internet of things based determination of machine reliability and automated maintainenace, repair and operation (MRO) logs | |
KR20200052361A (en) | System and method for cloud-device collaborative real-time user use and performance anomaly detection | |
US10795655B1 (en) | Provisioning of software applications on edge devices in an internet-of-things environment | |
US20130176130A1 (en) | Managing environmental control system efficiency | |
US20190155271A1 (en) | Determining a change in asset performance using a digital twin | |
US20120284211A1 (en) | Identifying abnormalities in resource usage | |
KR102488923B1 (en) | Abnormal data collecting method, apparatus, storage medium and computer program for automatic | |
CN111858111A (en) | Method, apparatus and computer program product for data analysis | |
CN109743209B (en) | Method and device for transmitting information | |
JP2018127209A (en) | Automobile component breakage prevention system, automobile component breakage prevention method, and temporary computer-readable medium | |
KR20200055828A (en) | Artificial Intelligence Platform Service System and Method | |
US20220011169A1 (en) | Thermal management system, method, and device for monitoring health of electronic devices | |
US20190354914A1 (en) | Coordinating Execution of Predictive Models between Multiple Data Analytics Platforms to Predict Problems at an Asset | |
CN111310778A (en) | Detection device, detection method, and recording medium on which detection program is recorded | |
US10573147B1 (en) | Technologies for managing safety at industrial sites | |
US20200160208A1 (en) | Model sharing among edge devices | |
CN112862222A (en) | Air conditioner return air temperature prediction method, abnormality monitoring method and related device | |
US10218722B2 (en) | Method and system for developing an anomaly detector for detecting an anomaly parameter on network terminals in a distributed network | |
US9052881B2 (en) | Discovering thermal relationships in data processing environments | |
CN116627770B (en) | Network card temperature prediction method and device, computer equipment and storage medium | |
US20200226043A1 (en) | Method and System for Developing an Anomaly Detector for Detecting An Anomaly Parameter on Network Terminals in a Distributed Network | |
US11601155B2 (en) | System and method for optimized thermal management of a WWAN modem | |
US11959812B2 (en) | Automated programmable dehumidifier | |
US11610140B2 (en) | Predicting fatigue of an asset that heals | |
CN117092933B (en) | Rotating machinery control method, apparatus, device and computer readable medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: ABB SCHWEIZ AG, SWITZERLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MOUSAVI, MIRRASOUL J.;ACHARYA, MITHUN P.;BARR, BRIAN D.;SIGNING DATES FROM 20181018 TO 20181031;REEL/FRAME:047755/0466 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |