Facility monitoring

Abstract

The illustrative systems, apparatus, devices, and methods described herein may be configured to monitor a plurality of different machines in a facility. In particular, the illustrative systems, apparatus, devices, and methods may be configured to monitor at least energy and carbon usage of a plurality of machines to provide energy and carbon accounting thereof. In one embodiment, a monitoring collection may be defined by a plurality of sensor nodes, each sensor node corresponding to and monitoring an aspect or parameter of a machine. Each machine may be associated with or correspond to more than one sensor node. Each sensor node may monitor a different aspect or parameter of a machine. For example, one sensor node may monitor energy consumption of a machine while another sensor node may monitor vibrations of the machine, thermal data of the machine, etc.

Description

FACILITY MONITORING

[0001] This disclosure generally relates to systems, apparatus, devices, and methods to monitor a facility, and in particular, one or more sensor nodes forming, or defining, a monitoring collection (e.g., monitoring route) with the facility.

[0002] A facility, such as an industrial facility, may utilize a plurality of different machines that are used separate from or in conjunction with each other to perform a common task or merely associated with each other. For example, a grain drying facility may include roller grinders, hammermills, mixers, and elevators that are configured and utilized together to dry and store harvested grain. Each machine of a facility may use, or utilize, a power source such as, for example, electricity or natural gas. Additionally, each machine may be monitored by one or more sensors monitoring one or more parameters, or aspects, of the machines. For example, a machine may be monitored by a vibration sensor to monitor the vibrations of the machine, which may be indicative of the performance of the machine.SUMMARY

[0003] The illustrative systems, apparatus, devices, and methods described herein may be configured to monitor a plurality of different machines in a facility. Further, the illustrative systems, apparatus, devices, and methods are configured to interoperate with, or work with, a variety of different machines from differing manufactures so as to be able to provide a universal, easy-to-use monitoring of such machines. Further, it may be described that the illustrative systems, apparatus, devices, and methods simplify and streamline the monitoring of a plurality of machines.

[0004] In particular, the illustrative systems, apparatus, devices, and methods may be configured to monitor at least energy and carbon usage of a plurality of machines to provide energy and carbon accounting thereof. In one embodiment, a monitoring collection (e.g., monitoring route) may be defined by a plurality of sensor nodes, each sensor node corresponding to and monitoring an aspect or parameter of a machine. Each machine may be associated with or correspond to more than one sensor node. Each sensor node may monitor a different aspect or parameter of a machine. For example, one sensor node may monitor energy consumption of a machine while another sensor node may monitor vibrations of the machine.

[0005] To monitor the plurality of machines using the sensor nodes defining a monitoring route, the illustrative systems, apparatus, devices, and methods including various apparatus configured to receive data representative of a parameter from each sensor senor node, convert the data into a common transport format, translate the data into a common storable format, and then upload the data in a data store. Performance data covering the entire monitoring collection or route may be stored and presented to a user so as to provide convenient monitoring, tracking, and context of such data. For example, a monitoring collection or route may follow a manufacturing line, and thus, the performance data associated with the monitoring collection or route may provide insight in the energy and carbon costs for the entire manufacturing line. In one embodiment, the performance of data of the monitoring routes as well as individual sensor nodes making up, or defining, the monitoring routes may be presented, or displayed, to a user on an interactable user interface (e.g., graphical user interface). The user may utilize, or use, the user interface to adjust the monitoring routes, add sensor nodes, remove sensor nodes, start and stop monitoring jobs or tasks, etc. Further context is provided via the output of routes in the account history function for further opportunities of analysis or reporting of aggregated data.

[0006] In one aspect, the present disclosure provides an industrial facility monitoring system to monitor a plurality of machines. The system includes a plurality of sensor nodes, each sensor node of the plurality of sensor nodes operably coupled to a machine of the plurality of machines and configured to sense at least one parameter of the machine representative of one or more of an electrical, mechanical, and electromechanical property of the machine and transmit data representative of the at least one parameter, and at least one computing apparatus including one or more processors and operably coupled to the plurality of sensor nodes. The at least one computing apparatus is configured to receive the data representative of the at least one parameter from each of the plurality of sensor nodes, extract the at least one parameter from each of the plurality of sensor nodes from the data representative of the at least one parameter from each of the plurality of sensor nodes, provide a monitoring collection (e.g., monitoring route) defined by a subset of sensor nodes of the plurality of sensor nodes that are associated with each other (e.g., that are utilized to perform a task), allow a user to add or remove a sensor node from the subset of sensor nodes defining the monitoring collection, and determine performance data for the monitoring collection based on the extracted at least one parameter of the sensor nodes of the subset of sensor nodes defining the monitoring route.

[0007] In another aspect, the present disclosure provides an industrial facility monitoring system to monitor a plurality of machines. The system includes a plurality of sensor nodes, each sensor node of the plurality of sensor nodes operably coupled to a machine of the plurality of machines and configured to sense at least one parameter of the machine representative of one or more of an electrical, mechanical, and electromechanical property of the machine and transmit node data representative of the at least one parameter, and at least one computing apparatus including one or more processors and operably coupled to the plurality of sensor nodes. The at least one computing apparatus is configured to receive first node data representative of the at least one parameter from a first sensor node of the plurality of sensor nodes, the first node data being formatted in a first data format, receive second node data representative of the at least one parameter from a second sensor node of the plurality of sensor nodes, the second node data being formatted in a second data format different from the first data format, generate translated first data representative of the at least one parameter from the first sensor node of the plurality of sensor nodes based on the first node data, wherein the translated first data is formatted in a third data format different from the first data format, and generate a first data block representative of the translated first data over a period of time.

[0008] In yet another aspect, the present disclosure provides a system to monitor a plurality of machines, each machine monitored by at least one sensor node of a plurality sensor nodes. The system includes a display including a graphical user interface, and a computing apparatus including one or more processors and operably coupled to the display. The computing apparatus is configured to define at least one collection (e.g., monitoring) route defined by a subset of sensor nodes of the plurality of sensors nodes monitoring a subset of machines of the plurality of machines that are associated with each other (e.g., to perform a task), receive machine performance data from each sensor node of the subset of sensor nodes defined by the at least one monitoring route, display, on the graphical user interface, a plurality of node graphical elements, each node graphical element corresponding to and representative of a different sensor node of the plurality of sensor nodes, wherein each node graphical element includes the machine performance data monitored by the corresponding sensor node, and display, on the graphical user interface, a route card (e.g., route area, route portion, etc.) for each of the at least one monitoring routes, wherein each route card includes route performance data that is an aggregation of the machine performance data monitored by each sensor node of the subset of sensors nodes of the at least one monitoring route.BRIEF DESCRIPTION OF DRAWINGS

[0009] FIG. 1 depicts an illustrative monitoring system.

[0010] FIG. 2 depicts the computing apparatus of the system of FIG. 1.

[0011] FIG. 3 depict an illustrative computing apparatus of FIGS. 1-2.

[0012] FIG. 4 depicts a plurality of the illustrative systems of FIG. 1 operably coupled to a node analysis computing apparatus.

[0013] FIG. 5 is an illustrative method of determining performance data for a monitoring route.

[0014] FIG. 6 is an illustrative method of generating blocks of translated data for storage in a data store.

[0015] FIG. 7 depicts an illustrative node graphical element for use in a graphical user interface (GUI) provided by the illustrative systems, apparatus, devices, and methods described herein.

[0016] FIG. 8 A depicts an illustrative GUI including an operation region provided by the illustrative systems, apparatus, devices, and methods described herein.

[0017] FIG. 8B depicts another illustrative GUI include an operation region, a total route card, and status graphical element provided by the illustrative systems, apparatus, devices, and methods described herein.

[0018] FIG. 8C depicts the GUI of FIG. 8B including a status graphical area.

[0019] FIG. 8D depicts the GUI of FIG. 8B including another status graphical area.

[0020] FIG. 9 depicts an illustrative GUI including a settings region including an equipment area provided by the illustrative systems, apparatus, devices, and methods described herein.

[0021] FIG. 10 depicts an illustrative GUI including a settings region including a route tracking area provided by the illustrative systems, apparatus, devices, and methods described herein.

[0022] FIG. 11 depicts an illustrative GUI including an editor region provided by the illustrative systems, apparatus, devices, and methods described herein

[0023] FIG. 12 depicts an illustrative GUI including a history area.

[0024] FIG. 13 depicts an illustrative data visualization region.DETAILED DESCRIPTION

[0025] In the following detailed description of illustrative embodiments, reference is made to the accompanying figures of the drawing which form a part thereof, and in which are shown, by way of illustration, specific embodiments which may be practiced. It is to be understood that other embodiments may be utilized, and structural changes may be made without departing from (e.g., still falling within) the scope of the disclosure presented hereby.

[0026] Illustrative systems, apparatus, devices, and methods shall be described with reference to Figures 1-13. It will be apparent to one skilled in the art that elements or processes from one embodiment may be used in combination with elements or processes of the other embodiments, and that the possible embodiments of such systems, apparatus, devices, and methods using combinations of features set forth herein is not limited to the specific embodiments shown in the Figures and / or described herein. Further, it will be recognized that the embodiments described herein may include many elements that are not necessarily shown to scale. Still further, it will be recognized that timing of the processes and the size and shape of various elements herein may be modified but still fall within the scope of the present disclosure, although certain timings, one or more shapes and / or sizes, or types of elements, may be advantageous over others.

[0027] An illustrative industrial facility monitoring system 100 is diagrammatically depicted in FIG. 1. The system 100 may be configured to monitor a facility 10, and more specifically, a plurality of machines 12 within the facility 10. Each machine 12 may be any machine or device that utilizes energy to perform at least part of a task. For example, a machine 12 may be an electric or gas motor that may be configured to rotate a drive shaft to perform as task with the movement provided by the drive shaft such as, for instance, a grinder. Further, for example, a machine 12 may be an electric or gas heater that may be configured to heat, and ultimately dry, a material such as grain. The plurality of machines 12 may include one or more of a motor, a dryer, a screw, a conveyor, a mixer, a blower, and a breaker panel.

[0028] One or more parameters of each machine 12 may be monitored by the illustrative system 100 using a plurality of sensor nodes 102. The plurality of sensor nodes 102 may include any number of sensor nodes 102a-n. Each sensor node 102 may be operably coupled to a machine 12 so as to be able to sense at least one parameter of the machine 12 representative ofone or more of an electrical, mechanical, and electromechanical property, or aspect, of the machine 12. To do so, each sensor node 102 may be physically coupled to the machine 12 or coupled to one or more apparatus related to the machine 12. For example, a sensor node 102 including a vibration sensor may be physically coupled to a motor housing of a machine 12 to monitor vibrations of the machine 12. Further, for example, a sensor node 102 including an electrical parameter monitoring circuit or sensor may be coupled to a breaker panel or other portion of an electrical circuit configured to provide energy to a machine 12 to monitor electrical parameters of the machine 12. The electrical properties or aspects of a machine 12 that may be monitored by a sensor node 102 may include energy consumption, voltage, current, harmonics, calculated carbon usage, and voltage imbalance. The mechanical properties or aspects of a machine 12 that may be monitored by a sensor node 102 may include temperature, vibration across multiple axes, and flow or level per analog sensor. The electromechanical properties or aspects of a machine 12 that may be monitored by a sensor node 102 may include breaker tripped status, and motor controller operational status.

[0029] As shown in FIG. 1, the facility may include a plurality of machines 12, and a plurality of sensors nodes 102 that correspond to and are operably coupled to each of the plurality of machines 12. Some machines 12 may only be associated with and be operably coupled to a single sensor node 102 while other machines 12 may be associated with and operably coupled to more than one sensor node 12 (e.g., a plurality of sensor nodes 12) each monitoring a different or the same aspect as one another. For example, the sensor node 102a may be configured to monitor energy consumption of the machine 12a. Further, for example, the sensor node 102b may be configured to monitor energy consumption of the machine 12b while the sensor node 102c may be configured to monitor vibrations of the same machine 12b. Additionally, in one embodiment, a single sensor node 102 may be associated with and operably coupled to multiple machines 12 so as to monitor one or more parameters of the machines 12 separately or together, depending on the configuration. For example, the sensor node 102d may be configured to monitor energy consumption of the machine 12c and the machine 12d, and the energy monitored therefrom may be monitored separately or together. For instance, in one embodiment, a sensor node 102 may be a breaker panel that is configured to monitor energy usage of a plurality of machines 12 operably coupled thereto to receive energy therefrom. In other embodiments, each circuit breaker of a breaker panel may be considered to be a separate sensor node 102, each circuit breaker associated with andmonitoring a different machine 12. As another example, any number of machines 12w can be monitored by one or more nodes 102e.

[0030] Each sensor node 102 may be operably coupled to at least one computing apparatus 110 of the system 100 to transmit data representative of the parameters monitored by the sensor node 102 to the at least one computing apparatus 110. Conversely, the at least one computing apparatus 110 may be operably coupled to each sensor node 102 to receive data representative of the parameters monitored by the sensor node 102. The operable coupling between the sensor nodes 102 and the at least one computing apparatus 110 may be wired or wireless. For example, the operable coupling between the sensor nodes 102 and the at least one computing apparatus 110 may utilize an intermediary coupling component to facilitate efficient wiring and deployment. Further, for example, the operable coupling between the sensor nodes 102 and the at least one computing apparatus 110 may utilize a radio communication protocol (e.g., Bluetooth, Zigbee, etc.). Further, for example, the operable coupling between the sensor nodes 102 and the at least one computing apparatus 110 may utilize a Wi-Fi network connection.

[0031] The at least one computing apparatus 110 may include any computing apparatus operable to receive, process, generate, and transmit data from the sensor nodes 102 so as to provide or support the illustrative monitoring processes and methods described herein. As will be described further herein with respect to FIG. 2, in one embodiment, the at least one computing apparatus 110 may include a converter 22, a real-time computing apparatus 24, and an edge computing apparatus 26 operably coupled to each other to provide or support the illustrative monitoring processes and methods described herein.

[0032] The at least one computing apparatus 110 may also be operably coupled to a data store 114 via a network 111 such as, e.g., the internet. The data store 114 may include and / or be implemented by one or more storage mediums such as hard drive disks, solid state drives, other random-access memory, read only memory, and / or other suitable storage devices. The data store 114 may include an organized set of data that facilitates efficient lookup and storage of the performance data. For example, the data store 114 can include a database, a hash table, a distributed ledger (e.g., blockchain), or any other suitable storage design.

[0033] The at least one computing apparatus 110 may also be operably coupled to a node analysis computing apparatus 112. The node analysis computing apparatus 112 may be described a user-facing computing apparatus (e.g., a personal computer) configured to allow a user to monitor the performance of one or more facilities 10 from the data located on the datastore 114. As shown, the node analysis computing apparatus 112 may be operably coupled to the computing apparatus 110 and the data store 114 via a network (such as, e.g., the Internet). Additionally, the node analysis computing apparatus 112 may be operably coupled to a plurality of different computing systems and data stores via the network 111 such as, e.g., public utility computing systems and data stores (e.g., to acquire utility cost information), weather computing systems and data stores, artificial intelligence systems and data stores (e.g., to process data utilizing artificial intelligence and / or machine learning processes), etc. The node analysis computing apparatus 112 may be configured to allow a user to set one or more node monitoring settings or configurations of the at least one computing apparatus 110 using, e.g., the user interfaces described further herein with respect to FIGS. 8-11. For example, the node analysis computing apparatus 112 may be configured to allow a user reset monitoring routes such that cumulative energy and cost performance data may be reset for the monitoring routes. The node analysis computing apparatus 112 will be described further herein with respect to the GUIs in FIGS. 8-11, as well as the methods and processes of FIGS. 5-6.

[0034] A number of devices for use as the at least one computing apparatus 110 as depicted in FIG. 1 are depicted in FIG. 2. Generally, the at least one computing apparatus 110 may include a number of different computing apparatus configured to perform different tasks performed by the at least one computing apparatus 110. For example, the at least one computing apparatus 110 may include a converter 22 configured to convert, or cast, node data in a first transport format to a second transport format. The first transport format may be one or more of a MODBUS RTU format, 4-20 ma analog signal format, an IO-Link signal format, a 0-10V analog signal format, and an AC vibration sensor signal format. The second transport format may be a MODBUS TCP / IP format. The converter 22 may be configured to cast multiple different first transport formats to the second transport format. More specifically, the converter 22 may receive first node data in a first transport format (e.g., MODBUS RTU format) and second node data in a second transport format (e.g., 4-20 ma analog signal format), and then cast each of the first node data and the second node data to a single third transport format (e.g., MODBUS TCP / IP format). In at least one embodiment, the converter 22 may utilize a Banner Engineering DXMR90 industrial controller.

[0035] The at least one computing apparatus 110 may include a real-time computing apparatus 24. Generally, the real-time computing apparatus 24 may generate translated data representative of the at least one parameter monitored by each sensor node 102a-w. Even after the converter 22 casts the node data into a single transport format (e.g., MODBUS TCP / IPformat, EtherNet / IP, PROFINET, EtherCat, BACNet, etc.), the node data may be further translated into a common data format. Different industrial machine and / or digital computing device manufacturers may use different data format (even when using the same transport format). The real-time computing apparatus 24 can generate translated data based on the node data formatted in the single transport format by the converter 22. The translated data can unify the node data into a single data format that is manufacturer-independent. The real-time computing apparatus 24 may be configured to translate the node data based on a predetermined translation protocol that includes manufacturer-specific, sensor-specific, and / or data formatspecific translation protocols that specifies how to translate data in various data formats to a common data format. The common data format may be associated with a common data array. The real-time computing apparatus 24 may be configured to generate data packets that conform to the common data array. The real-time computing apparatus 24 enables the node analysis computing apparatus 112 to work with sensor nodes 102a-w of various types (e.g., a meter, a sensor, a data source, etc.). The real-time computing apparatus 24 is configured to learn and read a data array associated with each sensor node 102a-w. Each sensor node 102a- / / can be configured to generate data packets associated with a predetermined data array. More specifically, each data packet may be formatted according to the data array. Each data packet can include data representative of the at least one parameter monitored by each sensor node 102a- / / . The translation protocol may include translation information for each sensor node included in the sensor nodes 102a-n. More specifically, the translation protocol may include translation information for how to translate data packets formatted according to the data array associated with each sensor node into data packets formatted according to the common data array. By generating data packets that conform to the common data array, the real-time computing apparatus 24 can convert data packets from the sensor nodes 102a- / / into common data format packets. After the real-time computing apparatus 24 is configured to read the data array of a sensor node 102a- / / , the real-time computing apparatus 24 can cast data included in each data packet into the common data format.

[0036] Further, the converter 22 may be configured to receive data packets at a native sample rate of the sensor node 102a- / / . In one or more embodiments, the converter 22 may receive data packets from each sensor node 102a- / / at the fastest native sample rate of the sensor node 102a- / / . If the sample rate of the sensor node 102a- / / is twice the frequency of the highest harmonic component of the waveform the converter 22 and / or the real-time computing apparatus 24 may be able to detect inrush current. If the converter 22 and / or the real-timecomputing apparatus 24 are configured to detect inrush current, the computing apparatus 110 and / or the node analysis computing apparatus 112 may be configured to determine the starting and stopping of routes based on the detected inrush current.

[0037] In this way, the real-time computing apparatus 24 can allow a user to monitor and analyze a facility that includes sensor nodes having different data formats, that are different sensor types, and / or that are from different manufacturers. Data from sensor nodes that monitor the same parameter (e.g., current) but have different data formats (e.g., a data format associated with a first manufacturer and another data format associated with a second manufacturer) may be translated into a common data format by the real-time computing apparatus 24. For example, the real-time computing apparatus 24 may translate voltage data from a first sensor node and voltage data from a second sensor node to the common, or same, data format regardless of their initial data formats and / or transport formats associated with the sensor nodes.

[0038] Additionally, the real-time computing apparatus 24 may be configured to generate data blocks based on the translated node data. Each data block can correspond to data generated during a predetermined period of time by a sensor node. In this way, the real-time computing apparatus 24 may be described as binning translated node data into data blocks representative of the translated node data over a period of time. The period of time may be between about 1 second and about 35 seconds. In at least one embodiment, the period of time may be twenty seconds. In at least one embodiment, the period of time may be less than one second. In at least one embodiment, the real-time computing apparatus 24 may be a programmable logic controller (PLC).

[0039] The at least one computing apparatus 110 may include an edge computing apparatus 26. Generally, the edge computing apparatus 26 may be configured to receive translated node data and / or data blocks from the real-time computing apparatus 24 and upload, or transmit, the translated node data and / or the data blocks to the data store 114 and / or the node analysis computing apparatus 112 via the network 111. The edge computing apparatus 26 may also store translated node data and / or data blocks on a local storage medium, such as a hard drive and / or a solid-state drive.

[0040] In some aspects, the real-time computing apparatus 24 may perform some or all of the duties of the converter 22 and / or the edge computing apparatus 26. In some aspects, the real-time computing apparatus 24 may be configured to convert, or cast, input node data in a first transport format to a second, unified transport format. In some aspects, the real-timecomputing apparatus 24 may be configured to upload translated node data and / or data blocks to the data store 114 and / or the node analysis computing apparatus 112 via the network 111. In some aspects, if the real-time computing apparatus 24 cannot receive node data from all of the sensor nodes and / or the converters 22 in a facility (e.g., if the real-time computing apparatus 24 does not have sufficient input ports), then the edge computing apparatus 26 may be used to collate data from multiple real-time computing apparatuses 24.

[0041] In one or more embodiments, sensor data including each data packet generated by the sensor nodes 102a- / / may be communicated to the real-time computing apparatus 24. The real-time computing apparatus 24 may aggregate the sensor data (e.g., voltage data, current data, effective power data, etc.). The real-time computing apparatus 24 may transmit the aggregated sensor data to, e.g., a cloud-based storage device. In one embodiment, the cloud- hosted application may display the data of each sensor in a corresponding node within the configured GUI contributing to each configured route calculation.

[0042] A functional block diagram of an illustrative computer apparatus 50 for use as at least one computing apparatus 110 as depicted in FIGS. 1-2 is shown in FIG. 3. For example, the computing apparatus 50 may be representative of any of the converter 22, the real-time computing apparatus 24, and the edge computer 26 of FIG. 2 and the node analysis computing apparatus 112 of FIG. 1. The computing apparatus 50 may include a processing apparatus, or a processor, 52, input device(s) 60 and a display 64. Generally, the input device 60 may be operably coupled to the processing apparatus 52 and may include any one or more devices configured to allow a user to provide input to the processing apparatus 52. The input device 60 may include any apparatus, structure, or devices configured to receive input from a user. For example, the input device 60 may include one or more keyboards, mice, microphones, touchscreens, smart pens, etc.

[0043] Additionally, the input device 60 may be further described in terms of the various input modalities. For example, the input device 60 may be configured to receive touch inputs from a user using a touchscreen display, keystrokes of a keyboard, voice commands, gesture commands, etc. In essence, the input device 60 may be configured to provide input capabilities to, e.g., to modify and / or generate monitoring routes, view and / or analyze node data and / or data blocks, generate carbon cost and / or economic cost information, etc. In one or more embodiments, the processing apparatus 52 may be configured to receive voice commands or audible input from a user.

[0044] The computing apparatus 50 may additionally include a display 64 operably coupled to the processing apparatus 52. The display 64 may include any one or more devices configured to provide visual and / or tactile information to a user. For example, the display 64 may include one or more monitors, screens, liquid crystal display panels, organic light emitting diode panels, tactile displays (e.g., braille or moveable bump displays), lights, etc. The display 64 may be configured to display a graphical user interface to a user, and the graphical user interface may be configured to display a plurality of different types of information related to facility monitoring /

[0045] Further, the processing apparatus 52 includes data storage 54. Data storage 54 allows for access to processing programs, processes, or routines 56 and one or more other types of data 58 that may be employed to carry out the exemplary methods, processes, and algorithms of generating and analyzing sensor node data. For example, processing programs or routines 56 may include programs or routines for performing computational mathematics, matrix mathematics, Fourier transforms, compression algorithms, calibration algorithms, image construction algorithms, inversion algorithms, signal processing algorithms, normalizing algorithms, deconvolution algorithms, averaging algorithms, standardization algorithms, comparison algorithms, vector mathematics, audio comparison, learning algorithms, or any other processing required to implement one or more embodiments as described herein.

[0046] Data 58 may include, for example, power data, voltage data, current data, electrical cost data (e.g., acquired in real-time or periodically from a public utility), gas cost data (e.g., acquired in real-time or periodically from a public utility), motor status information, mechanical data, electromechanical data, breaker panel data, vibration data, calculated carbon data, aggregated power data, aggregated voltage data, aggregated current data, statistical metrics, mathematical metrics, aggregation metrics, user-generated metrics, totals, averages, ranges, trends, patterns, extremes, outliers, comparisons, absolute groupings, directional groupings, operational status of a machine, an electrical parameter of a machine, a temperature parameter of the machine, a natural gas consumption parameter of a machine, a machine health parameter of a machine, a water consumption parameter of a machine, a weight parameter of a machine, machine type, serial numbers, hardware-identifying information, manufacturer, or any data generated by the node analysis processes 56.

[0047] In one or more embodiments, the computing apparatus 50 may be controlled using one or more computer programs executed on programmable computers, such as computers that include, for example, processing capabilities (e.g., microcontrollers, programmable logicdevices, etc.), data storage (e.g., volatile or non-volatile memory and / or storage elements), input devices, and output devices. Program code and / or logic described herein may be applied to input data to perform functionality described herein and generate desired output information. The output information may be applied as input to one or more other devices and / or processes as described herein or as would be applied in a known fashion.

[0048] The programs used to implement the processes described herein may be provided using any programmable language, e.g., a high-level procedural and / or object-orientated programming language that is suitable for communicating with a computer system. Any such programs may, for example, be stored on any suitable device, e.g., a storage media, readable by a general or special purpose program, computer, or a processor apparatus for configuring and operating the computer when the suitable device is read for performing the procedures described herein. In other words, at least in one embodiment, the computing apparatus 50 may be controlled using a computer readable storage medium, configured with a computer program, where the storage medium so configured causes the computer to operate in a specific and predefined manner to perform functions described herein.

[0049] The processing apparatus 52 may be, for example, any fixed or mobile computer system (e.g., a cellular phone, a personal computer, minicomputer, etc.). The exact configuration of the computing apparatus is not limiting and essentially any device capable of providing suitable computing capabilities and control capabilities (e.g., control the display of the computing apparatus 50, converting data from sensor nodes, translating data from sensor nodes, generating node data and / or data blocks, etc.) may be used. Further, various peripheral devices, such as a computer display, mouse, keyboard, memory, printer, scanner, etc. are contemplated to be used in combination with the processing apparatus 52. Further, in one or more embodiments, the data 58 (e.g., power data, voltage data, current data, electrical cost data, motor status information, mechanical data, electromechanical data, breaker panel data, vibration data, calculated carbon data, aggregated power data, aggregated voltage data, aggregated current data, statistical metrics, mathematical metrics, aggregation metrics, usergenerated metrics, totals, averages, ranges, trends, patterns, extremes, outliers, comparisons, absolute groupings, directional groupings, operational status of a machine, an electrical parameter of a machine, a temperature parameter of the machine, a natural gas consumption parameter of a machine, a machine health parameter of a machine, a water consumption parameter of a machine, a weight parameter of a machine, etc.) may be analyzed by a user, used by another machine that provides output based thereon, etc. As described herein, a digitalfile may be any medium (e.g., volatile or non-volatile memory, a CD-ROM, a punch card, magnetic recordable tape, etc.) containing digital bits (e.g., encoded in binary, trinary, etc.) that may be readable and / or writeable by processing apparatus 52 described herein. Also, as described herein, a file in user-readable format may be any representation of data (e.g., ASCII text, binary numbers, hexadecimal numbers, decimal numbers, audio, graphical) presentable on any medium (e.g., paper, a display, sound waves, etc.) readable and / or understandable by a user.

[0050] In view of the above, it will be readily apparent that the functionality as described in one or more embodiments according to the present disclosure may be implemented in any manner as would be known to one skilled in the art. As such, the computer language, the computer system, or any other software / hardware that is to be used to implement the processes described herein shall not be limiting on the scope of the systems, processes, or programs (e.g., the functionality provided by such systems, processes, or programs) described herein.

[0051] The methods described in this disclosure, including those attributed to the systems, or various constituent components, may be implemented, at least in part, in hardware, software, firmware, or any combination thereof. For example, various aspects of the techniques may be implemented by the processing apparatus 52, which may use one or more processors such as, e.g., one or more microprocessors, DSPs, ASICs, FPGAs, CPLDs, microcontrollers, quantum computers, or any other equivalent integrated or discrete logic circuitry, as well as any combinations of such components, image processing devices, or other devices. The term "processing apparatus," "processor," or "processing circuitry" may generally refer to any of the foregoing logic circuitry, alone or in combination with other logic circuitry, or any other equivalent circuitry. Additionally, the use of the word "processor" may not be limited to the use of a single processor but is intended to connote that at least one processor may be used to perform the exemplary methods and processes described herein.

[0052] Such hardware, software, and / or firmware may be implemented within the same device or within separate devices to support the various operations and functions described in this disclosure. In addition, any of the described components may be implemented together or separately as discrete but interoperable logic devices. Depiction of different features, e.g., using block diagrams, etc., is intended to highlight different functional aspects and does not necessarily imply that such features must be realized by separate hardware or software components. Rather, functionality may be performed by separate hardware or software components, or integrated within common or separate hardware or software components.

[0053] When implemented in software, the functionality ascribed to the systems, devices and methods described in this disclosure may be embodied as instructions on a computer- readable medium such as RAM, ROM, NVRAM, EEPROM, FLASH memory, magnetic data storage media, optical data storage media, or the like. The instructions may be executed by the processing apparatus 52 to support one or more aspects of the functionality described in this disclosure.

[0054] FIG. 4 depicts a plurality of the illustrative systems of FIG. 1 operably coupled to the node analysis computing apparatus 112. A multi-facility monitoring system 400 can include a plurality of facilities 410a- / / . Each facility of the plurality of facilities 410a- / / can be operably coupled to the node analysis computing apparatus 112 via the network 111 (e.g., the Internet). As described above, the node analysis computing apparatus 112 can be operably coupled to the data store 114 also via the network 111. In this way, the node analysis computing apparatus 112 can monitor and / or analyze any number of facilities. In at least one embodiment, the plurality of facilities 410a- / / may be associated with a single customer (e.g., a corporation). In at least one embodiment, a first portion of the facilities included in the plurality of facilities 410a- / / may be associated with a first customer, and a second portion of the facilities included in the plurality of facilities 410a- / / may be associated with a second customer. The system 400 may further include a web server 113, which is operably coupled to the node analysis computing apparatus 112 and the data store 114. The web server 113 may be accessible anywhere via a web browser to view and / or edit information of or from the node analysis computing apparatus 112 and the data store 114. Additionally, the node analysis computing apparatus 112 may be configured to send email, text messages, or other communications to users based on the data monitoring from the facilities 410 / / .

[0055] FIG. 5 is an illustrative method 500 of determining performance data for a monitoring route. The method 500 can be implemented as executable instructions on a storage medium (e.g., the data storage 54) and executed by a processing apparatus (e.g., the processing apparatus 52).

[0056] At 510, the method 500 can receive data representative of at least one parameter from each of a plurality of sensor nodes. Each sensor node of the plurality of sensor nodes may be operably coupled to a machine of the plurality of machines and configured to sense at least one parameter of the machine. The at least one parameter may be representative of one or more of an electrical, mechanical, and electromechanical property of the machine. The parametermay be inrush current. The sensor nodes may be configured to transmit data representative of the at least one parameter.

[0057] At 520, the method 500 can extract the at least one parameter from each of the plurality of sensor nodes from the data representative of the at least one parameter from each of the plurality of sensor nodes. The method 500 may extract the at least one parameter from each of the plurality of sensor nodes by generating translated data as described above.

[0058] At 530, the method 500 can provide a monitoring collection defined by a subset of sensor nodes of the plurality of sensor nodes that may be associated with each other. In one embodiment, a monitoring collection may be or include a monitoring route defined by a subset of sensor nodes of the plurality of sensor nodes that are utilized to perform a task. The task may be drying grain, extruding metal, injection molding plastic parts, etc. The task may require the use of multiple machines in a facility. Each machine may be operably coupled to one or more sensor nodes. For a given task, only a subset of the sensor nodes may provide meaningful and / or relevant information. For example, certain tasks may not require the use of a particular motor included in the facility. The task may be associated with a predetermined subset of sensor nodes.

[0059] At 540, the method 500 can allow a user to add or remove a sensor node from the subset of sensor nodes defining the monitoring route. The user may generate a request to add or remove a sensor node from the subset of sensor nodes defining the monitoring route. For example, the user may wish to add a sensor node corresponding to a vibration sensor to the monitoring route. As another example, the user may not be interested in electricity consumed by a particular motor and remove a sensor node operably coupled to that motor and configured to generate electrical consumption information corresponding to that motor. The user may add or remove the sensor node from the subset of sensor nodes defining the monitoring collection (e.g., monitoring route) by dragging and dropping (e.g., with a computer mouse or a touchscreen interface), by selecting or deselecting the node from a list, or another suitable technique of choosing to add or remove the sensor node from the subset of sensor nodes defining the monitoring route. The method 500 may then update the route based on the usergenerated request.

[0060] At 550, the method 500 can determine performance data for the monitoring collection (e.g., monitoring route) based on the extracted at least one parameter of the sensor nodes of the subset of sensor nodes defining the monitoring route. The method 500 maygenerate data blocks representative of the extracted parameter over a period of time. The period of time may be twenty seconds. The method 500 may generate the performance data based on the data blocks. In some aspects, the performance data can include calculated carbon data generated based on a source of energy. The source (e.g., user-defined source) of energy may be one or more of solar, wind, natural gas, coal, hydroelectric, biomass, other fossil fuel, oil, geothermal, nuclear. The performance data can be user-defined (e.g., user input) or automatically received via a network (e.g., the Internet) from other systems (e.g., real-time pricing information regarding source of energy). The calculated carbon data can be calculated based on any authoritative set of math standards, such as, for example, Environmental Protection Agency and / or European Union carbon math standards. The European Union carbon math standard may be the Carbon Border Adjustment Mechanism (CBAM). For example, for a facility in France, the method 500 may automatically determine that the calculated carbon data should be calculated based on European Union carbon math standards, and generate the calculated carbon data based on European Union carbon math standards. The source of energy may be an internal power source and / or an external power source. The performance data may be averaged and / or aggregated based on the data blocks. The performance data may be a binary, trinary, quaternary, or n-state status of a machine, such as an operation status (e.g., no concerns, mild concerns, high concern, etc.). In other words, the performance data may be any number of states such as two (e.g., binary status) or over a thousand states. For example, the performance data may be color coded to millions of different colors in a continuously variable color-coding heat map. The performance data may include power data, voltage data, current data, electrical cost data, motor status information, mechanical data, electromechanical data, breaker panel data, vibration data, calculated carbon data, aggregated power data, aggregated voltage data, aggregated current data, statistical metrics, mathematical metrics, aggregation metrics, user-generated metrics, totals, averages, ranges, trends, patterns, extremes, outliers, comparisons, absolute groupings, directional groupings, operational status of a machine, an electrical parameter of a machine, a temperature parameter of the machine, a natural gas consumption parameter of a machine, a machine health parameter of a machine, a water consumption parameter of a machine, and / or a weight parameter of a machine. The method 500 may transmit the performance data to an external computing apparatus and / or display the performance data at in graphical user interface. The method 500 may store the performance data in a data store (e.g., the data store 114) for a predetermined period of time. The predetermined period of time may be ten years.

[0061] FIG. 6 is an illustrative method 600 of generating blocks of translated data for storage in a data store. The method 600 can be implemented as executable instructions on a storage medium (e.g., the data storage 54) and executed by a processing apparatus (e.g., the processing apparatus 52).

[0062] At 610, the method 600 can receive first node data representative of at least one parameter from a first sensor node of a plurality of sensor nodes, the first node data being formatted in a first data format. The first data format may be associated with a first transport format such as a MODBUS RTU format, RS-485 signals, a 4-20 ma analog signal format, an IO-Link signal format, a 0-10V analog signal format, a 0-5V analog signal format, a + / -10V analog signal format, a 1-5V analog signal format, an AC vibration sensor signal format, EtherNet / IP format, PROFINET format, EtherCat format, BACNet format, etc. The first data format may be a manufacturer-specific and / or sensor-specific data format. The first node data can include a plurality of data packets, each data packet being associated with a discrete time period (e.g., one millisecond, five milliseconds, ten milliseconds, etc.). The plurality of data packets may be a time series of data packets. The data packet can include a data array that specifies how the data is formatted by the sensor node.

[0063] At 620, the method 600 can receive second node data representative of at least one parameter from a second sensor node of a plurality of sensor nodes, the second node data being formatted in a second data format different from the first data format. The second data format may be associated with a second transport format such as a MODBUS RTU format, a 4-20 ma analog signal format, an IO-Link signal format, a 0-10V analog signal format, and / or an AC vibration sensor signal format. The second data format may be a manufacturer-specific and / or sensor-specific data format. For example, the first data format may be associated with a 4-20 ma analog signal transport format and a first manufacturer, and the second data format may be associated with the 4-20 ma analog signal transport format and a second manufacturer. As another example, the first data format may be associated with a 4-20 ma analog signal transport format and a manufacturer, and the second data format may be associated with a MODBUS RTU transport format and the same manufacturer. In some aspects, sensor nodes associated with the same manufacturer and transport format may still have different data formats. In a common data format, for each parameter in a plurality of parameters, data representative of parameter is stored in the same format. In other words, a data format specifies the storage protocol for each parameter in the plurality of parameters. The second node data can include a plurality of data packets, each data packet being associated with a discrete time period (e.g.,one millisecond, five milliseconds, ten milliseconds, etc.). The plurality of data packets may be a time series of data packets. Each data packet may include a parameter value for each parameter included in the at least one parameter.

[0064] At 630, the method 600 can generate translated first data representative of the at least one parameter from the first sensor node of the plurality of sensor nodes based on the first node data. The translated first data may be formatted in a third data format different from the first data format. The third data format may be referred to as a common data format. The common data format can be associated with a third transport format such as a MODBUS TCP / IP transport format. To convert the first node data to the translated first data, the method 600 may convert the first node data into the third transport format from the first transport format. Before or after the conversion into the third transport format, the method 600 may reformat the first node data based on the first sensor node. The third data format may be independent of manufacturer and sensor node types. The method 600 may reformat the first node data based on a predetermined translation protocol that includes manufacturer-specific, sensor-specific, and / or data format-specific translation protocols that specifies how to translate data in various data formats to a common data format. By using the predetermined translation protocol, the method 600 can generate translated data in a unified format that can be easily disseminated by the node analysis computing apparatus. The method 600 may generate translated second data representative of the at least one parameter from the second sensor node of the plurality of sensor nodes based on the second node data. The translated second data may be formatted in the data format. The method 600 may generate the translated second data based on the predetermined translation protocol. In some aspects, each data packet included in the first node data and the second node data can be translated at 630.

[0065] At 640, the method 600 can generate a first data block representative of the translated first data over a period of time. The period of time may be twenty seconds (which, for example, may be a “rolling” time period, may include multiple parallel times frames that overlap each other, etc.). The method 600 can average, aggregate, or otherwise process the plurality of data packets included in the translated first data into one of more data blocks representative of the translated first data over the period of time. The method 600 may average and / or aggregate data included in a subset of the data packets included in the translated first data, the subset of the data packets corresponding to the period of time. For example, if each data packet is associated with a discrete ten millisecond period, and the period of time is twenty seconds, the first data block may be generated based on, and representative of, two thousandconsecutive data packets. The first data block may include an average value of the parameter of the subset of the data packets. The first data block may include an aggregated value of subset of the data packets (e.g., a sum of the parameter values included in the subset of packets). The method 600 may generate the first data block based on a predetermined threshold value. For example, if any of the value of the parameter in any of the data packets in the subset of the data packets is at and / or above the threshold, the first data block may be a discrete status value (e.g., a binary status value, a trinary status value, a quaternary status value, an n-state status value etc.). More specifically, the method 600 may determine that an inrush current value is above a predetermined threshold value in one or more data packets included in the subset of data packets, and generate the first data block having a warning status indicator value. The method 600 may generate the first data block based on a mode, median, minimum, maximum, slope, minimum slope, maximum slope, etc. of the parameter values included in the subset of the data packets. For example, the method 600 can determine the mode or median of the parameter values included in the subset of the data packets and include the mode or median in the first data block. The method 600 may also generate a second data block representative of the translated second data over the period of time.

[0066] As described herein, the illustrative systems, apparatus devices, and methods may be configured to, among other things monitor at least one parameter of each of a plurality of machines representative of one or more of an electrical, mechanical, and electromechanical property of the machine using a plurality of sensor nodes and determine performance data for one or more monitoring routes based on the monitored at least one parameter. The performance data may then be used to determine costs (e.g., monetary costs, carbon costs, etc.) associated with each machine and each monitoring route. One illustrative way to view and show the determined performance data as well as the costs is through a graphical user interface (GUI). For example, performance data of a monitoring collection (e.g., monitoring route) may be viewed and / or downloaded using a GUI. The performance data may be stored (e.g., in a nonvolatile memory), integrated into other performance data, and / or analyzed with historical performance data associated with a specific account. Additionally, the configuration of an illustrative system described herein may be performed using a GUI. For example, monitoring routes may be created or edited using a GUI. Illustrative GUIs provided by the illustrative systems, apparatus, devices, and methods are described herein with respect to FIGS. 7-11.

[0067] Each sensor node of a monitoring system may be represented in an illustrative GUI using a node graphical element 200 as shown in FIG. 7. The node graphical element 200 maybe described as a graphical representation of a node sensor including, among other things, information measured using the node sensor that may be depicted on an illustrative GUI. In this example, the node graphical element 200 is defined, in part, by a circular node identifier area 202 circumscribed by a node information area 210. The node identifier area 202 may include, among other things, graphical and / or textual identification information 204 for the node graphical element 200 such that a user may be able to view and / or read the graphical and / or textual identification information 204 to quickly ascertain the node sensor, and in turn, the machine, for which the node graphical element 200 is associated with and represents on a GUI. In the example shown in FIG. 7, the text “Screw Conveyor” is depicted within the circular node identifier area 202 thereby indicating that the node graphical element 200 is associated with and represents a node sensor operably coupled to a Screw Conveyor apparatus. As will be described further herein with respect to an equipment area of a settings region of an illustrative GUI as shown in FIG. 9, the graphical and / or textual identification information 204 may be the actual equipment name as provided when initially configured, an illustrative monitoring system, or a nickname added by a user following the initial configuration. In at least embodiment, the graphical and / or textual identification information may include an icon or graphical depiction of the machine represented by and associated therewith. For example, a graphical depiction of a screw conveyor (e.g., an actual digital photograph of the screw conveyor) may be shown, or displayed, in the node identifier area 202. Additionally, although the node identifier area 202 is depicted as being circular in this example, it is to be understood that the node identifier area 202 may be depicted in any shape or size so as to be able to convey to a user the sensor node and / or machine associated with the node identifier area 202. Additionally, the graphical and / or textual identification information 204 may also indicate a status of the node. For example, the graphical and / or textual identification information 204 may display a particular color indicative of the status of node. In one embodiment, the graphical and / or textual identification information 204 may be colored green to indicate that a node is being used, colored white to indicate that a node is not being used, colored red to indicate that there is an error or problem at a node, and colored yellow to indicate that there is a warning at a node. In one or more embodiments, the thresholds utilized to determine which color the identification information should be based on standards set for the various machinery or apparatus (e.g., ISO standards).

[0068] As noted previously, the node graphical element 200 includes a node information area 210. The node information area 210 includes information and / or values of the at least oneparameter monitored by the associated sensor node of the associated machine representative of one or more of an electrical, mechanical, and electromechanical property of the machine. The node information area 210 is positioned with respect to the node identifier area 202 such that the information and / or values depicted, or displayed, in the node information area 210 is associated with the node identifier area 202 and not confused with another node graphical element 200. In this example, to do so, the node information area 210 is depicted as a concentric ring around the node identifier area 202 to convey to a user that the node information area 210 is related to and correspond with the sensor node and / or machine identified in the node identifier area 202. Although the node information area 210 is depicted as four separate areas equally divided in a concentric ring around the node identifier area 202, it is to be understood that the node information area 210 may be depicted in any way, shape, size, or form so as to convey the information provided thereby is associated with the sensor node and / or machine identified in the node identifier area 202.

[0069] In this example, the node information area 210 may include a cost area 212, a current area 214, a voltage area 216, and an energy area 218. The cost area 212 may include a numerical depiction the cumulative, or running, energy cost of the machine monitored by the associated sensor node or the present energy cost of the machine monitored by the associated sensor node. The current area 214 may include a numerical depiction the present current in Amps (A) of the machine monitored by the associated sensor node, and the voltage area 216 may include a numerical depiction the present voltage in Volts (V) of the machine monitored by the associated sensor node. The energy area 218 may include a numerical depiction one or more of the cumulative, or running, power usage in Kilowatts-Hours (KWh), cumulative, or running, carbon cost in metric tons, and current power cost in dollars per KWh.

[0070] Additionally, as described herein, each sensor node may monitor more machine performance data than just energy information from the associated machine such as, for example, vibration information, temperature information, etc. The node graphical element 200 may be configured to depict, or display, such information in relation to the node identifier area 202 similar to as described with respect to the node information area 210. Additionally, based on the energy information and other information of the machine performance data, operational status of the sensor node and / or machine may be generated, or derived, and also displayed with respect to the node graphical element 200. Thus, as shown additional information with respect sensor node and / or associated machine may be depicted in additional information elements 220 positioned proximate to the node information area 210. In this example, the additionalinformation elements 220 are depicted as arcuate portions extending partially around the circumference of the node information area 210. The additional information elements 220 may be temporary or not persistent (as indicated by the dashed lines in FIG. 7) as the additional information elements 220 may only be shown when the information contained, or depicted, therein is determined to be shown to a user. It is to be understood that any information or data shown in the node graphical elements 200 may be temporary to not persistent. For example, when a node is inactive, the node graphical elements 200 may not display any information, including zero values. Further, for example, when data of a node has been consistent or unchanged for a period of time, the node graphical elements 200 may not display such detailed information. These temporary or not persistent information configurations for the node graphical elements 200 may be selectable by a user.

[0071] For example, an operational status indicative of the status of the functionality, or operation, of the associated machine may be depicted in one of the additional information elements 220. For instance, an operational status additional information element 222 is depicted in FIG. 7 that includes the text “Unacceptable” to indicated that the operational status of the machine associated with the node graphical element 200 is not acceptable. In one embodiment, the operational status may be one of an optimal status, a sub-optimal status, an unacceptable status, and an inactive status (e.g., based on industry stands, based on ISO standards, based on user-defined levels, etc.). Further, for instance, a temperature additional information element 224 is depicted in FIG. 7 that includes a numerical depiction pf the present temperature monitored by the sensor node. Additionally, each of the additional information elements 220 may include further graphical indication (e.g., color, size, shape, animation, etc.) of a severity or need of attention for the particular information depicted in the additional information elements 220. For example, the operational status additional information element 222 may be the color red if it is indicating an unacceptable status or the color yellow if it is indicating a suboptimal status. In this way, a user may quickly ascertain any problems during a brief glance at a node graphical element 200.

[0072] Furthermore, each node graphical element 200 may include additional information representative or reflective of the particular machine the node graphical element 200 is associated therewith. For example, each node graphical element 200 may include (e.g., show, display, depict, etc.) technical info on what the node represents such as, for example, load type, manufacturer, model, serial number, unique ID, construction date, installation date, last serviced date, various load specs, etc.). Such information may be implemented as a simpletable, bulleted text, etc. with possible graphical indicators like manufacturer logo images, photos of the device, etc. Additionally, some of this additional information may not be directly shown on the node graphical element 200 but may be accessed by selecting (e.g., touching, clicking, etc.) a graphical item located on or proximate to the node graphical element 200 such as, for example, a textual “i” within a circle, which in turn, may provide (e.g., display, pop-up, etc.) another graphical area, region, or element containing or showing the additional information.

[0073] An illustrative graphical user interface (GUI) 250 provided by the illustrative systems, apparatus, devices, and methods described herein is shown in FIG. 8A. In this example, the GUI 250 includes a selection region 252, an operation region 260, and a route region 270. The selection region 252 includes a dashboard graphical element 254 that is selectable by a user to depict, or display, the operation region 260 and the route region 270 as shown in FIG. 8A. The dashboard graphical element 254 is highlighted in FIG. 8A (e.g., circumscribed) to indicate that the operation region 260 and the route region 270 are presently being shown.

[0074] The selection region 252 further includes a settings graphical element 256 that is selectable by a user to depict, or display, a settings region 280 as shown in FIGS. 9-10 and an editor graphical element 258 that is selectable by a user to depict, or display, an editor region 290 as shown in FIG. 11.

[0075] Additionally, the selection region 252 further includes a history graphical element 259 that is selectable by a user to depict, or display, a history region where users may be able to view and download historical data (e.g., spreadsheets, comma separated values, etc.) from one or more monitor routes and / or sensors that are configured as part of the monitoring system. The history graphical element 259 may enable the user to download either all available data or a subset of data, e.g., based on a user-selected date range. The user may select any gathered data to which the user has access for download, including data not currently displayed in the GUI. For example, data not currently displayed in the GUI may include energy costs in monetary terms (e.g., U.S. Dollars, Euros, Yen, etc.) or in carbon terms (e.g., Metric tons of carbon), depending on which metrics the user has currently chosen to display in the GUI. The history graphical element 259 may offer the user a choice of further download options, such as a choice between downloading plain datasets (e.g., a spreadsheet in CSV format) or downloading formatted reports (e.g., a carbon emissions report for a specified subset of data detailing the carbon emissions caused by the work tracked by one or more specific routes acrossa length of time, and enhanced by additional information, such as, e.g., the customer’s contact information in a formal report header, the names of customer staff responsible for tracking and validating the carbon emissions reported on, etc.).

[0076] As shown, the operation region 260 includes a plurality of node graphical elements 200 and a plurality of route indicators 262. Each route indicator 262 extends between two node graphical elements 200 corresponding to the sensor node included in a monitoring route to graphically indicate the monitoring route. For example, two monitoring routes are depicted using route indicators 262: the first route, or “Route #1” as it will be referred to further herein, is indicated by a long-dash line extending between node graphical elements 200. In particular, the first route extends from the “W Hammer Mill” node graphical element 200 to the “SE Hammer Mill” node graphical element 200 to the “Dry Leg” node graphical element 200 to the “Screw Conveyor” node graphical element 200, and finally to the “Out Conveyor” node graphical element 200. The second route extends from the “SE Hammer Mill” node graphical element 200 to the “Dry Leg” node graphical element 200 to the “Screw Conveyor” node graphical element 200, and finally to the “Out Conveyor” node graphical element 200. In this way, each of the first and second monitoring routes are different as the first route includes an additional node graphical element 200, i.e., the “W Hammer Mill” node graphical element 200. Although in this example, the route indicators 262 utilized differently dashed lines, it is to be understood that the route indicators 262 may utilize any different graphical indicia or parameter to distinguish each other. For example, the route indicators 262 may be different colors for each different route. In some aspects, the node graphical elements 200 may be configured to provide additional information when a user hovers over them with a cursor or other input device. When hovering, a tooltip or pop-up element may appear, displaying the latest data update timestamp for that particular node. This feature may allow users to quickly ascertain the recency of the displayed information without needing to navigate to a separate interface. Additionally, the hover functionality may indicate whether predictive maintenance data, such as vibration or temperature information, is available for the specific node. This indication may be presented through an icon, text, or color coding within the hover element, potentially enabling users to identify nodes with more comprehensive monitoring capabilities at a glance.

[0077] Although the node graphical elements 200 and route indicators 262 are shown in two-dimensions, it is be understood that the operation region 260 could depict the node graphical elements 200 and route indicators 262 to provide a more effective and efficient user interface. For example, a plurality of the node graphical elements 200 could be grouped andthen “stacked” (e.g., visually represented on top of each other) to indicate that such plurality of the node graphical elements 200 are grouped or in a group. More specifically, for example, a plurality of the node graphical elements 200 may be grouped if the plurality of the node graphical elements 200 are all part of or associated with a particular machine or process. In this way, once a group of the node graphical elements 200 (stacked or otherwise graphically depicted together) are selected (e.g., clicked, touched, etc.), such node graphical elements 200 may visually expand (e.g., explode, spread apart, or otherwise move) such that each of the grouped graphical elements 200 may now be viewed and selected separately. In one or more embodiments, the size of a selected (e.g., clicked, touched, etc.) node graphical element 200 may be increased such that a user may more easily view and / or select the data contained therein. In one or more embodiments,

[0078] In one or more embodiments, underneath the plurality of node graphical elements 200 and the plurality of route indicators 262, a background image 299 may be displayed, or depicted, that is representative of a real-world physical location of the sensor nodes and machines represented by the plurality of node graphical elements 200. In this way, the plurality of node graphical elements 200 may be positioned with respect to the real-world physical location of the sensor nodes and machines shown on the background image 299 such that a user may quickly ascertain which node graphical elements 200 are associated with and correspond to the actual sensor nodes and associated machines. To move the node graphical elements 200 and add a background image, a user may select the editor graphical element 258 to depict, or display, an editor region 290 as shown in FIG. 11.

[0079] In the editor region 290, a user may select the “Move Nodes” graphical element 292 (e.g., toggle, switch, etc.) to allow the node graphical elements 200 to be moved about the editor region 290 with respect to each other and the background image 299. In one embodiment, a user may “touch” or “click” and “drag” or “move” the node graphical elements 200 about the editor region 290 using a finger or other pointing device such as a computer mouse. Additionally, a user may switch the energy area 218 from including a numerical depiction the cumulative, or running, power usage in Kilowatts-Hours (KWh) to carbon cost in metric tons, and vice versa, using the “Carbon View” graphical element 294 (e.g., toggle, switch, etc.). As shown in FIG. 11, the switch is toggled to show cumulative carbon cost in metric tons in each of the node graphical elements 200. Additionally, a user may change or add a background image 299 using the background image graphical element 296, which may initiate, or pop-up,an image selection dialog where a user may select an image file to be used as the background image 299.

[0080] The route, or collection, region 270 of the GUI 250 may include a plurality of collection cards 272 (e.g., route cards). Each collection card 272 may be associated with and representative of a different monitoring collection (e.g., route) as depicted by the node graphical elements 200 and the route indicators 262. Each collection card 272 may include performance data that is an aggregation of the machine performance data monitored by each sensor node of the subset of sensors nodes of the corresponding monitoring collection (e.g., monitoring route). Additionally, each collection card 272 may include additional information related to the route such as collection or route name, collection or route nickname, customer namejob name, product name, energy source name, feature name, start date and time, end date and time, cumulative energy cost, cumulative carbon cost, present energy cost, and present carbon cost. As shown, each collection card 272 includes collection or route name, customer name, job name, product name, energy source name, feature name, start date and time, cumulative energy cost, and cumulative carbon cost. Some of the information of the collection card 272 may not be directly shown on the collection card 272 but may be accessed by selecting (e.g., touching, clicking, etc.) a graphical item located on or proximate to the collection card 272 such as, for example, a textual “i” within a circle, which in turn, may provide (e.g., display, pop-up, etc.) another graphical area, region, or element containing or showing the additional information. A customer name may be associated with one or more users. It is to be understood that, while this embodiment depicts the collection cards 272 in a “card-like” graphical fashion, the collection cards 272 may be graphically depicted in any manner so as to provide the appropriate information to a user regarding the associated collection (e.g., route). For example, the collection cards 272 may be depicted as a stack of cards or any sort of graphical depiction. In one embodiment, the collection cards 272 may be any visualization that aggregates or summarizes data from the plurality of nodes defined as the monitoring collection (e.g., monitoring route) associated therewith. This visualization may use one or more of numbers, shapes, graphics, graphics, graphical vales, graphical shapes, time-series graphs, imagery, or other visible elements to indicate or display the aggregated or summarized collection-level information.

[0081] Moreover, each collection card 272 includes a reset graphical element 274 configured to be selected (e.g., touched, clicked, etc.) by a user to reset the information shown on the collection card 272 and reset the start date and time. As shown, the reset graphicalelement 274 is a button-style area containing the text “Reset Route” located within the bounds, or boundary, of the collection card 272. Additionally, the selection of the reset graphical element 274 may be noted or recorded in the data that is transmitted to and stored in the data store 114 such that, for example, a user may be able to sort the data based on when each collection card 272 has been reset based on, e.g., different customers and / or jobs.

[0082] Additionally, in one or more embodiments, route resetting may occur automatically based on one or more measure criteria or metrics. For example, a collection or route could be reset based on power usage and vibration data. More specifically, for example, when power usage reaches below a particular threshold, it may indicate that a process has been completed, and thus, the collection or route may be reset such that the route accumulation data is associated with and reflective of the completed process.

[0083] Each collection card 272 may provide indicia, or graphical indication, linking, or identifying, the collection card 272 with a particular collection or route depicted using the route indicators 262. For example, the border, or outline, 273 of each collection card 272 may be similar to or the same as the route indicators 262. As shown, the border 273 of the topmost collection card 272 is represented by a long dash line indicative of Route #1, which is the same or similar indicia as the route indicators 262 extending between node graphical elements 200 associated with Route #1. Further, the border 273 of the bottommost collection card 272 is represented by a short dash line indicative of Route #2, which is the same or similar indicia as the route indicators 262 extending between node graphical elements 200 showing Route #2. Similar to the route indicators 262, the borders 273 or other equivalent route card indicia may be any different graphical indicia or parameter to distinguish each other. For example, the borders 273 may be different colors for each different route.

[0084] Each of the collection cards 272 includes a color associated with the route designated by the user. The selection of a collection card 272 may highlight, or graphically emphasize, the route indicators 262 defining, or making up, the monitoring collection represented by selected collection card 272, and / or may highlight, or graphically emphasize, the node graphical elements 200 defining, or making up, the monitoring collection represented by selected collection card 272. Additional machine information may be presented in an additional machine information area 275 in response to the user clicking on a specific node graphical element 200. In this example, the additional machine information area 275 is depicted below the collection cards 272. The additional machine information area 275 may include additional information related to the node graphical element 200 selected. For example, theadditional machine information area 275 may include various data or information such as line graphs showing, for example, time vs. current, time vs. voltage, and time vs. power, as updated per the update rate as, for example, shown in FIG. 13 or other information such as, for example, shown in FIGS. 8C & 8D.

[0085] In at least one embodiment, a color of the route indicators 262 between the node graphical elements can be the same color as the collection card 272. In at least one embodiment, the collection card 272 displays active or last completed route as chosen in a settings interface. The collection card 272 may include energy costs in $(Euro / Yen) / kW & Carbon in Metric tons. In at least one embodiment, route data such as the energy costs can be transmitted to an account history portion of the data store 114. A user may access the account history portion of the data store 114 to select a date range and download some or all of historical data included in the account history portion. The historical data may be sortable by route, customer, date, costs, carbon, etc. The GUI may allow a user to extract information for reporting to regulatory authorities based on the historical data. In at least one embodiment, that extracted historical data may reflect the carbon emissions created in operating the route monitored by the application for a user-specified duration, as, for example, may be required for carbon reporting requirements related to the European Union’s Carbon Border Adjustment Mechanism (CBAM).

[0086] In at least one embodiment, the GUI can include a facility graphic that may provide enhanced visual representation of machines and / or sensor nodes to a user. In at least one embodiment, routes can be associated with a user-created route name and / or a user-created job name. The collection card 272 may be associated with a color corresponding to a route between the node graphical elements 200. In at least one embodiment, placement of the node graphical elements 200 may be user-defined within an editor interface. The facility graphic can aid in adding context to each node graphical element 200 and may enable the user to quickly see where to put their focus based on the information and / or alerts presented by the GUI. In at least one embodiment, the collection card 272 may include information about two different motors in order to highlight differences in operation between the two motors (e.g., motor variance). In at least one embodiment, the node graphical elements 200 are configurable by a user within an editor screen to include kw / h or another energy cost metric in a bottom second quadrant of the node graphical element 200. In at least one embodiment, one or more node graphical elements 200 may be configured to show a temperature alarm. The node graphical elements 200 may each include a 3rd concentric circle depicting vibration, a vibration alert, a temperature alert,and / or a tripped indicator (e.g., an indication of a tripped circuit breaker). The node graphical elements 200 may each include a user-selected carbon indicator included in a bottom portion of a second concentric circle of the bubble. In at least one embodiment, the collection card 272 may include both a total route cost in total $ / kWh indicator and a metric tons of CO2 indicator. In at least one embodiment, any of the above metrics and / or indicators may be reviewed later via a history region interface. The history region may enable the user to review some or all route data and sort by date, route, customer, etc. In at least one embodiment, warnings or indicators included in the second or third concentric circles may trigger a notification (e.g., a text message) to be communicated to one or more users or computer systems. For example, a text message or an email may be sent to one or more users associated with (e.g., supervising) the route. For example, a message may be sent to one or more computer systems via an application protocol interface (API). For example, a message may be sent to one or more Al agents configured to monitor one or more routes. In at least one embodiment, a frequency interval for notification may also be selected by the user.

[0087] Another illustrative GUI 250 including the operation region 260 that is substantially the same or similar to the GUI 250 of FIG 8A. The GUI of FIG. 8B, however, further includes a total collection or collection card 279 and a status graphical element 300. The total collection card 279 may be similar to the collection cards 272 described herein except that instead of being associated with and representative of different monitoring collections or routes, the total collection card 279 may be associated with and representative of all the routes of the operation region 260. In other words, the total collection card 279 may include cumulative data for all the collections or routes and collection cards 272. More specifically, the total collection card 279 may include performance data that is an aggregation of the machine performance data monitored by each sensor node of all of the collections or routes. Additionally, the total collection card 279 may include additional information related to all collections or routes such as, e.g., start date and time, end date and time, cumulative energy cost, cumulative carbon cost, present energy cost, and present carbon cost. Although not shown, the total collection card 279 may include a reset graphical element configured to be selected (e.g., touched, clicked, etc.) by a user to reset the information shown on the total collection card 279 and reset the start date and time.

[0088] Additionally, each of the total collection card 279 and the collection cards 272 of the GUI 250 of FIG. 8B may include status indicators 277. The status indicators 277 may indicate or show a status of the associated with the facility or route associated therewith. Forexample, as shown, the status indicators 277 of the collection cards 272 display the text, “Event in Progress,” thereby indicating that an event is in progress in each of the collections or routes. Further, for example, the status indicator 277 of the total collection card 279 display the text, “Energy Being Used,” thereby indicating that an energy is being used at the facility via at least one of the collections or routes.

[0089] Selection of the status graphical element 300 in FIG. 8B may initiate, or trigger, the display of a status graphical area 310, e.g., as a pop-up overlay on the GUI 250. This functionality may allow users to access more detailed status information without navigating away from the GUI 250. The display of the status graphical area 310 may also be initiated, or triggered, by selection of one or more portions or areas of a node graphical element 200 such as, e.g., additional information elements 220. As shown, the status graphical element 300 includes the title, or description, of “Vibration Status Table” as, in this embodiment, the status graphical element 300 may be configured to display vibration status information regarding the nodes.

[0090] The status graphical area 310 shown in FIG. 8C displays vibration severity data for a W Hammermill 20HP. The status graphical area 310 includes a node title 312 identifying the node, and arrows 314 that may allow navigation between different nodes. The status graphical area 310 further includes, or presents, status data elements 318 that are indicative of various status data for the associated node. As described herein, this status graphical area 310 is associated with, at least, vibration data. As shown, this status graphical area 310 of FIG. 8C includes status data elements for "X Velocity" vibration, "Z Velocity" vibration, and Temperature. In this instance, both the X and Z Velocity vibrations readings are shown as "Good" while the Temperature reading is marked as "N / A.”

[0091] The status graphical area 310 shown in FIG. 8D displays vibration severity data for a Screw Conveyor. The status graphical area 310 includes a node title 312 identifying the node, and arrows 314 that may allow navigation between different nodes. The status graphical area 310 further includes, or presents, status data elements 318 that are indicative of various status data for the associated node. As described herein, this status graphical area 310 is associated with, at least, vibration data. As shown, this status graphical area 310 of FIG. 8D includes status data elements for "X Velocity" vibration, "Z Velocity" vibration, and Temperature for both "E Vibe" and "W Vibe" components. In this instance, the E Vibe X and Z Velocity vibration readings are shown as "Unsatisfactory," while the W Vibe X and Z Velocity vibration readings are shown as "Good." The Temperature readings for E Vibe and W Vibe are markedas "OK" and "N / A" respectively. The status graphical area 310 may provide a more detailed and comprehensive view of the vibration status for multiple components of the Screw Conveyor, allowing users to quickly identify and assess potential issues or anomalies in the equipment's operation.

[0092] Selection by user of the settings graphical element 256 may depict, or display, a settings region 280 as shown in FIGS. 9-10. The settings region 280 may include three sections, namely, the account information section, the equipment section, and the route tracking section, each of which are displayable upon selection of an account information graphical element 284, an equipment graphical element 286, and a route tracking graphical element 288 from a section selection area 282 depicted near the top of the settings region 280. The account information section, which is not depicted herein, may be configured to allow a user to enter various information with respect to their account such as, e.g., company name, primary contact name, primary contact email address, primary contact phone number, secondary contact phone number, text messaging timeouts, interval polling, electrical power source information (e.g., one or more of solar, wind, natural gas, coal, hydroelectric, biomass, other fossil fuel, oil, geothermal, and nuclear), etc.

[0093] The equipment section 281 shown in FIG. 9 displays a list of each of the node graphical elements 200 that are part of the monitoring system and displayed on the operation region 260 of the GUI 250. Each line of the list may include a different node graphical element 200, a nickname that may be entered for each node graphical element 200, and a device notification status 283. The device notification status 283 may be a selectable element (e.g., toggle, button, switch, etc.) that may be selectable by a user to enable or disable notifications from that associated node graphical element 200. For example, if a user would not like to receive notifications from sensor node monitoring a machine, then a user may select the device notification element to disable notifications from the sensor node associated with the node graphical element 200. Conversely, if a user would like to receive notifications from sensor node monitoring a machine, then a user may select the device notification element to enable notifications from the sensor node associated with the node graphical element 200. Additionally, a selectable checkbox 269 may be associated with each different node graphical element 200, which may be used to select or not select the node graphical element to be included in the list of equipment to have a node graphical element 200 usable in the system 100 and GUI 250 (e.g., selectable to be part of a route, usable to monitor data associated therewith, etc.). For example, a user may de-select the W Hammermill, and thus, the nodegraphical element 200 associated therewith may not be shown in the GUI 250. As shown, each of the lines, and thus, equipment, are selected (indicated by the “X” with the checkbox 269 located on the left of each line) such that each of the equipment listed may be used in the system 100 and GUI 250.

[0094] The route tracking section 285 shown in FIG. 10 displays one or more route configuration portions, or cards, 287. In particular, two route configuration portions 287, one for Route #1 and one for Route #2, are depicted in the route tracking section 285. Each of the route configuration portions 287 may be configured to allow a user to add or remove sensor nodes, and correspondingly, node graphical elements 200 from a monitoring route. For example, in this embodiment, a user may add a sensor node by selecting the “+Add” graphical element 289 located on the route configuration portion 287, which will initiate display of a list of remaining sensor nodes from the monitoring facility (which are also show on the equipment section 281 of FIG. 9. Additionally, a user may be able to delete a monitoring route using the “Delete” graphical element shown on the route configuration portion 287. Further, if a user would like to remove a sensor node from a monitoring route, the user may select the sensor node within the route configuration portions 287 (e.g., selecting the sensor node or the triangular pull-down icon associated therewith) to initiate display of a menu that allows deletion of the sensor node.

[0095] The route configuration portion 287 may include a "Displayed" toggle 295 that allows users to control the visibility of the associated route on the GUI 250. When enabled, this toggle 295 may cause the corresponding route to be shown in the operation region 260, including the relevant node graphical elements 200 and route indicators 262. If the toggle 295 is disabled, the route may be hidden from view in the GUI 250, potentially simplifying the display for users focusing on other routes or equipment.

[0096] The "Displayed" toggle 295 may provide users with flexibility in managing the visual complexity of the GUI 250. Users may choose to show only the routes they are currently interested in monitoring, which may enhance the clarity and usability of the interface. This feature may be particularly useful in facilities with numerous routes, allowing users to customize their view based on current monitoring priorities or troubleshooting needs. In some cases, the state of the "Displayed" toggle 295 may be saved as part of the user's preferences, allowing the interface to remember which routes should be visible when the user returns to the GUI 250 in future sessions. The toggle may also interact with other interface elements, such aspotentially graying out or hiding the corresponding collection card 272 when a route is not displayed.

[0097] The route tracking section 285 further allows a user to add a new monitoring route using the “Add a Route” graphical element 291. Selection of the “Add a Route” graphical element 291 may add a route configuration portion 287 to the route tracking section 285, which may then be configured using the route configuration portion 287. Lastly, the route tracking section 285 further allows a user to save the monitoring routes using a “ Save” graphical element 293.

[0098] Selection by user of the history graphical element 259 may depict, or display, a history area 390 as shown in FIG. 12. The history area 390 may include a table displaying historical data for various monitoring routes. The table may include columns for Start Time, Finish Time, Customer Name, Route Cost ($), Route Name, and Route Carbon (MT CO2 eq). Each row in the table may represent a specific monitoring event or route execution.

[0099] The history area 390 may allow users to view and analyze past monitoring data across different routes, customers, and time periods. For example, the table shows entries for customers such as "StormChaser" and "Hintgen" with their associated route names like "Single Crush Rte 1" and "Double Crush Rte 1". The table may display specific start and finish timestamps for each route execution. The "Route Cost" column may show the monetary cost associated with each route execution in dollars, while the "Route Carbon" column may display the carbon emissions in metric tons of CO2 equivalent. The history area 390 may also include one or more entries for a site total execution (e.g., all of the routes combined). This information may allow users to track both economic and environmental impacts of their operations.

[0100] An export element 392, which may be a button labeled “Export," may be positioned at the top of the table. This element 392 may allow users to export the displayed data for further analysis or reporting purposes. The export functionality may support various file formats such as CSV, Excel, or PDF to accommodate different user needs.

[0101] The layout of the history area 390 may be designed for clarity and ease of use, with well-defined column headers and aligned data entries. This organization may allow users to quickly scan and compare data across different routes and time periods. In some implementations, the history area 390 may include sorting and filtering capabilities, allowing users to organize the data by various parameters such as date, customer, route name, or cost.This functionality may enhance the user's ability to identify trends, compare performance across different routes or time periods, and generate insights from the historical data.

[0102] Selection by user of one or more portions of a node 200 or another portion of the illustrative GUI 250 may depict, or display, a data visualization region 350, examples of which are shown FIG. 13. For example, the data visualization region 350 of FIG. 13 may be displayed in response to selection of a circular node identifier area 202 of a node such as a node representative of a "Roller Grinder 60HP." Although not shown in the context of the GUI 250, it is to be understood that the data visualization regions 350 may be displayed anywhere on the GUI 250 such as, e.g., over or on-top of the operation region 260 of the GUI 250 similar to the static graphical areas 310 of FIGS. 8C and 8D or in the machine information area 275.

[0103] The data visualization region 350 of FIG. 13 shows a time series graph of power consumption data 351 for a node, and in particular, a Roller Grinder 60HP. The power consumption data 351 is depicted in a data area 354 of the data visualization region 350. The data visualization region 350 further includes data selection element 352 configured to be used by a user to select the type of data 351 to display in the data area 354. For example, although power data (“KWh”) is selected and shown in the data area 354, it is be understood that carbon cost (“CO2”) may be selected by a user using the data selection element 352, which in turn, would display the carbon cost data instead of power consumption data in the data area 354.

[0104] The data visualization region 350 of FIG. 13 further includes navigation arrows 356 for moving through different time periods and time granularity elements 359, labeled “xl min,” “xlO min,” “xl hr,” and “xl day,” for adjusting the time scale shown in the data area 354. Additionally, the data visualization region 350 further includes reset indicators 358 marking specific points in the timeline where a route was reset thereby indicating effectively when a route was started and stopped. Further, various other metrics may be displayed in the data area 354 such as maximum values, minus values, values at particular time stamps such as the beginning and end of the data 351 shown in the data area 354. It is to be understood that the data visualization region 350 is only one example, and illustrative data visualization regions may include more or less data and functionality than shown in FIG. 13. For example, the data visualization region 350 may be further include a download graphical element configured to allow a user to download the data 391 being displayed in the data visualization region 350.ILLUSTRATIVE EXAMPLES

[0105] Example Exl : An industrial facility monitoring system to monitor a plurality of machines, the system including a plurality of sensor nodes, each sensor node of the plurality of sensor nodes operably coupled to a machine of the plurality of machines and configured to sense at least one parameter of the machine representative of one or more of an electrical, mechanical, and electromechanical property of the machine and transmit data representative of the at least one parameter, and at least one computing apparatus including one or more processors and operably coupled to the plurality of sensor nodes, the at least one computing apparatus configured to receive the data representative of the at least one parameter from each of the plurality of sensor nodes, extract the at least one parameter from each of the plurality of sensor nodes from the data representative of the at least one parameter from each of the plurality of sensor nodes, provide a monitoring route defined by a subset of sensor nodes of the plurality of sensor nodes that are utilized to perform a task, allow a user to add or remove a sensor node from the subset of sensor nodes defining the monitoring route, and determine performance data for the monitoring route based on the extracted at least one parameter of the sensor nodes of the subset of sensor nodes defining the monitoring route.

[0106] Example Ex2: A method of monitoring a plurality of machines in an industrial facility, the method including receiving data representative of at least one parameter from each of a plurality of sensor nodes, each sensor node of the plurality of sensor nodes operably coupled to a machine of the plurality of machines and configured to sense the at least one parameter of the machine representative of one or more of an electrical, mechanical, and electromechanical property of the machine, extracting the at least one parameter from each of the plurality of sensor nodes from the data representative of the at least one parameter from each of the plurality of sensor nodes, providing a monitoring route defined by a subset of sensor nodes of the plurality of sensor nodes that are utilized to perform a task, allowing a user to add or remove a sensor node from the subset of sensor nodes defining the monitoring route, and determining performance data for the monitoring route based on the extracted at least one parameter of the sensor nodes of the subset of sensor nodes defining the monitoring route.

[0107] Example Ex3 : The industrial facility monitoring system of Example Exl or method of Example Ex2, wherein the at least one computing apparatus is further configured to execute or the method further comprises receiving a user-generated request to add or remove a sensor node from the subset of sensor nodes defining the monitoring route, and update the monitoring route based on the user-generated request.

[0108] Example Ex4: The industrial facility monitoring system or method as in any one of Examples Exl-Ex3, wherein the performance data includes one or more of power data, voltage data, current data, electrical cost data, motor status information, mechanical data, electromechanical data, breaker panel data, vibration data, and calculated carbon data.

[0109] Example Ex5: The industrial facility monitoring system or method as in any one of Examples Exl-Ex4, wherein determining the performance data includes receiving a source (e.g., user-defined source) of energy, wherein the source of energy includes one or more of solar, wind, natural gas, coal, hydroelectric, biomass, other fossil fuel, oil, geothermal, and nuclear, and determining calculated carbon data based on the source of energy and the extracted at least one parameter of the sensor nodes of the subset of sensor nodes defining the monitoring route.

[0110] Example Ex6: The industrial facility monitoring system or method as in any one of Examples Exl-Ex5, wherein the performance data includes one or more of aggregated power data, aggregated voltage data, and aggregated current data.

[0111] Example Ex7: The industrial facility monitoring system or method as in any one of Examples Exl-Ex6, wherein each of the aggregated power data, the aggregated voltage data, and the aggregated current data includes one or more of statistical metrics, mathematical metrics, aggregation metrics, and user-generated metrics.

[0112] Example Ex8: The industrial facility monitoring system or method as in any one of Examples Exl-Ex7, wherein the performance data includes one or more of totals, averages, ranges, trends, patterns, extremes, outliers, comparisons, absolute groupings, and directional groupings.

[0113] Example Ex9: The industrial facility monitoring system or method as in any one of Examples Exl-Ex8, wherein determining performance data includes determining an operational status of the machine coupled to each sensor node of the subset of sensor nodes defining the monitoring route, wherein the operational status is indicative of an optimal status, a sub-optimal status, an unacceptable status, and an inactive status.

[0114] Example ExlO: The industrial facility monitoring system or method as in any one of Examples Exl-Ex9, wherein the at least one computing apparatus is further configured to execute or the method further comprises displaying, on a graphical user interface, at least one of the one or more of power data, voltage data, current data, electrical cost data, and motor status information.

[0115] Example Exl 1 : The industrial facility monitoring system or method as in any one of Examples Exl-ExlO, wherein the at least one parameter includes one or more of an electrical parameter of the machine, a natural gas consumption parameter of the machine, a temperature parameter of the machine, a machine health parameter of the machine, a water consumption parameter of a machine included in the plurality of machines, and a weight parameter of the machine.

[0116] Example Exl2: The industrial facility monitoring system as in any one of Examples Exl and Ex3-Exl l , wherein the at least one computing apparatus includes a translator computing apparatus, an edge computing apparatus, and a node analysis computing apparatus, wherein the translator computing apparatus is configured to receive the data representative of the at least one parameter from each of the plurality of sensor nodes, and extract the at least one parameter from each of the plurality of sensor nodes from the data representative of the at least one parameter from each of the plurality of sensor nodes, the edge computing apparatus configured to determine the performance data for the monitoring route based on the extracted at least one parameter of the sensor nodes of the subset of machines defining the monitoring route, and the node analysis computing apparatus is configured to provide the monitoring route defined by the subset of sensor nodes of the plurality of sensor nodes that are utilized to perform the task.

[0117] Example Exl3: The industrial facility monitoring system as in Example Exl2, wherein the translator computing apparatus is further configured to generate translated first data representative of the at least one parameter from a first sensor node of the plurality of sensor nodes based on the data associated with the first sensor node formatted in a first data format, the translated first data being formatted in a second data format, the second data format being different from the first data format.

[0118] Example Exl4: The industrial facility monitoring system as in Example Exl3, wherein the second data format is configured to store the translated first data in a data store.

[0119] Example Exl 5: The industrial facility monitoring system as in any one of Examples Ex 13 and Ex 14, wherein the at least one computing apparatus further includes a real-time computing apparatus configured to receive the extracted at least one parameter from the translator computing apparatus, and transmit the extracted at least one parameter to the edge computing apparatus.

[0120] Example Exl6: The industrial facility monitoring system as in any one of Examples Exl2-Exl 5 , wherein the extracted at least one parameter includes a time series of data packets, and wherein the real-time computing apparatus is further configured to generate a first data block representative and based on a first subset of the time series of data packets, and generate a second data block based on a second subset of the time series of data packets.

[0121] Example Exl7: The industrial facility monitoring system as in Example Ex 16, wherein the generating the first data block based on the subset of the time series of data packets includes averaging the data included in the first subset of the time series of data packets.

[0122] Example Exl 8: The industrial facility monitoring system as in any one of ExamplesExl6 and Exl7, wherein each of the first subset and the second subset of the time series of data packets is associated with a twenty second time period of the time series of data packets.

[0123] Example Exl 9: The industrial facility monitoring system or method as in any one of Examples Exl-Exl8, wherein the data representative of the at least one parameter from each of the plurality of sensor nodes is in one or more transport formats including one or more of a 4-20 ma analog signal format, an IO-Link signal format, a 0-10V analog signal format, MODBUS TCP / IP, and a MODBUS RTU signal format.

[0124] Example Ex20: The industrial facility monitoring system or method as in any one of Examples Exl-Exl9, wherein the plurality of machines includes at least one of a motor, a dryer, a screw, a conveyor, a mixer, a blower, or a breaker panel.

[0125] Example Ex21 : The industrial facility monitoring system or method as in any one of Examples Exl-Ex20, wherein the at least one parameter includes inrush current.

[0126] Example Ex22: The industrial facility monitoring system or method as in any one of Examples Exl-Ex21, wherein the at least one computing apparatus is further configured to execute or the method further comprises storing the performance data in a user account database for at least ten years.

[0127] Example Ex23: The industrial facility monitoring system or method as in any one of Examples Exl-Ex22, wherein the determining the performance data includes receiving a source of energy being at least one of an internal power source or an external power source, and determining calculated carbon data based on the source of energy and the extracted at least one parameter of the sensor nodes of the subset of sensor nodes defining the monitoring route.

[0128] Example Ex24: An industrial facility monitoring system to monitor a plurality of machines, the system including a plurality of sensor nodes, each sensor node of the plurality of sensor nodes operably coupled to a machine of the plurality of machines and configured to sense at least one parameter of the machine representative of one or more of an electrical, mechanical, and electromechanical property of the machine and transmit node data representative of the at least one parameter, and at least one computing apparatus including one or more processors and operably coupled to the plurality of sensor nodes, the at least one computing apparatus configured to receive first node data representative of the at least one parameter from a first sensor node of the plurality of sensor nodes, the first node data being formatted in a first data format, receive second node data representative of the at least one parameter from a second sensor node of the plurality of sensor nodes, the second node data being formatted in a second data format different from the first data format, generate translated first data representative of the at least one parameter from the first sensor node of the plurality of sensor nodes based on the first node data, wherein the translated first data is formatted in a third data format different from the first data format, and generate a first data block representative of the translated first data over a period of time.

[0129] Example Ex25: A method of monitoring a plurality of machines in an industrial facility, the method including receiving first node data representative of at least one parameter from a first sensor node of a plurality of sensor nodes, each sensor node of the plurality of sensor nodes operably coupled to a machine of the plurality of machines and configured to sense at least one parameter of the machine representative of one or more of an electrical, mechanical, and electromechanical property of the machine and transmit node data representative of the at least one parameter, the first node data being formatted in a first data format, receiving second node data representative of the at least one parameter from a second sensor node of the plurality of sensor nodes, the second node data being formatted in a second data format different from the first data format, generating translated first data representative of the at least one parameter from the first sensor node of the plurality of sensor nodes based on the first node data, wherein the translated first data is formatted in a third data format different from the first data format, and generating a first data block representative of the translated first data over a period of time.

[0130] Example Ex26: The industrial facility monitoring system as in Example Ex24, wherein the at least one computing apparatus includes a transport converter and a real-time computing apparatus, wherein the transport converter is configured to receive the first nodedata from the first sensor node of the plurality of sensor nodes in a first transport format and the second node data from the first sensor node of the plurality of sensor nodes in a second transport format, convert the first node data into a third transport format from the first transport format, and convert the second node data into the third transport format from the second transport format, wherein the real-time computing apparatus is configured to generate the translated first data and generate the first data block.

[0131] Example Ex27: The industrial facility monitoring system or method as in any one of Examples Ex24-Ex26, wherein the third transport format is MODBUS TCP / IP format.

[0132] Example Ex28: The industrial facility monitoring system or method as in any one of Examples Ex24-Ex27, wherein the first transport format is one or more of a MODBUS RTU, a MODBUS TCP / IP format, 4-20 ma analog signal format, an IO-Link signal format, a 0-10V analog signal format, and an AC vibration sensor signal format.

[0133] Example Ex29: The industrial facility monitoring system or method as in any one of Examples Ex24-Ex28, wherein the at least one computing apparatus is further configured to execute or the method further comprises generating translated second data representative of the at least one parameter from the second sensor node of the plurality of sensor nodes based on the second node data, the translated node data being formatted in the third data format, the third data format being different from the second data format.

[0134] Example Ex30: The industrial facility monitoring system or method as in any one of Examples Ex25-Ex29, wherein the third data format is configured to store the first data block associated with the period of time in a data store.

[0135] Example Ex31 : The industrial facility monitoring system or method as in Example Ex30, wherein the data store includes one or more of a database, an array, a hash table, and a distributed ledger.

[0136] Example Ex32: The industrial facility monitoring system or method as in any one of Examples Ex24-Ex31 , wherein the translated first data includes a time series of data packets, and wherein the generating the first data block includes generating the first data block based on a subset of the time series of data packets.

[0137] Example Ex33 : The industrial facility monitoring system or method as in Example 32, wherein the generating the first data block based on the subset of the time series of data packets includes at least one of aggregating or averaging the data included in the subset of the time series of data packets.

[0138] Example Ex34: The industrial facility monitoring system or method as in any one of Example 32 and Example 33, wherein the subset of the time series of data packets is associated with a twenty second time period of the time series of data packets.

[0139] Example Ex35: The industrial facility monitoring system or method as in any one of Examples Ex24-Ex34, wherein the first data block includes one or more of power data, voltage data, current data, electrical cost data, and motor status information.

[0140] Example Ex36. The industrial facility monitoring system or method as in any one of Examples Ex24-Ex35, wherein the first data block includes one or more of average power data, average voltage data, and average current data.

[0141] Example Ex37: The industrial facility monitoring system or method as in any one of Examples Ex24-Ex36, wherein the first data block includes one or more of power data, voltage data, current data, electrical cost data, and motor status information, and wherein the at least one computing apparatus is further configured to execute or the method further comprises displaying, on a graphical user interface, the first data block.

[0142] Example Ex38: The industrial facility monitoring system or method as in any one of Examples Ex24-Ex37, wherein the plurality at least one parameter includes one or more of an electrical parameter of the machine, an electromechanical parameter of the machine, a mechanical parameter of the machine, a temperature parameter of the machine, a natural gas consumption parameter of the machine, a machine health parameter of the machine, a water consumption parameter of a machine included in the plurality of machines, and a weight parameter of the machine.

[0143] Example Ex39: A system to monitor a plurality of machines, each machine monitored by at least one sensor node of a plurality of sensor nodes, the system including a display including a graphical user interface, and a computing apparatus including one or more processors and operably coupled to the display, wherein the computing apparatus is configured to define at least one monitoring route defined by a subset of sensor nodes of the plurality of sensors nodes monitoring a subset of machines of the plurality of machines to perform a task, receive machine performance data from each sensor node of the subset of sensor nodes defined by the at least one monitoring route, display, on the graphical user interface, a plurality of node graphical elements, each node graphical element corresponding to and representative of a different sensor node of the plurality of sensor nodes, wherein each node graphical element includes the machine performance data monitored by the corresponding sensor node, anddisplay, on the graphical user interface, a route card for each of the at least one monitoring routes, wherein each route card includes route performance data that is an aggregation of the machine performance data monitored by each sensor node of the subset of sensors nodes of the at least one monitoring route.

[0144] Example Ex40: A method of monitoring a plurality of machines, each machine monitored by at least one sensor node of a plurality of sensor nodes, the method comprising defining at least one monitoring route defined by a subset of sensor nodes of the plurality of sensors nodes monitoring a subset of machines of the plurality of machines to perform a task, receiving machine performance data from each sensor node of the subset of sensor nodes defined by the at least one monitoring route, displaying, on a graphical user interface, a plurality of node graphical elements, each node graphical element corresponding to and representative of a different sensor node of the plurality of sensor nodes, wherein each node graphical element includes the machine performance data monitored by the corresponding sensor node, and displaying, on the graphical user interface, a route card for each of the at least one monitoring routes, wherein each route card includes route performance data that is an aggregation of the machine performance data monitored by each sensor node of the subset of sensors nodes of the at least one monitoring route.

[0145] Example Ex41 : The system as Example Ex39 or method as in Example Ex40, wherein the computing apparatus is further configured to execute or the method further comprises displaying, on the graphical user interface, a plurality of route indicators, each route indicator extending between two node graphical elements corresponding to the at least one sensor node included in the at least one monitoring route to graphically indicate the at least one monitoring route.

[0146] Example Ex42: The system or method as in any one of Examples Ex39-Ex41, wherein the machine performance data of each node graphical element includes one or more of average power, average voltage, average current, current cost of operation, and calculated carbon data.

[0147] Example Ex43: The system or method as in any one of Examples Ex39-Ex41, wherein the computing apparatus is further configured to execute or the method further comprises determining the route performance data by receiving a source of energy, wherein the source of energy includes one or more solar, wind, natural gas, coal, hydroelectric, biomass,other fossil fuel, oil, geothermal, and nuclear, and determining calculated carbon data based on the source of energy and the machine performance data.

[0148] Example Ex44: The system or method as in any one of Examples Ex39-Ex41, wherein the machine performance data of each node graphical element includes an operational status indicative of one of an optimal status, a sub-optimal status, an unacceptable status, and an inactive status.

[0149] Example Ex45: The system or method as in Example Ex44, wherein the operational status is graphically indicated proximate to or on each node graphical element included in the plurality of node graphical elements.

[0150] Example Ex46: The system or method as in any one of Examples Ex44 and Ex45, wherein each node graphical element includes an arcuate element indicating the operational status.

[0151] Example Ex47: The system or method as in any one of Examples Ex39-Ex46, wherein an operational status of the machine associated with each sensor node is graphically indicated using at least one of a color or size of the node graphical element.

[0152] Example Ex48: The system or method as in any one of Examples Ex39-Ex47, wherein each node graphical element includes a plurality of concentric rings, and wherein an operational status of the machine associated with each sensor node is graphically indicated by adding a concentric ring to the plurality of concentric rings.

[0153] Example Ex49: The system or method as in any one of Examples Ex39-Ex48, wherein the computing apparatus is further configured to execute or the method further comprises displaying, on the graphical user interface, a background image underneath the plurality of node graphical elements representative of a real-world physical location of the sensor nodes represented by the plurality of node graphical elements.

[0154] Example Ex50: The system or method as in any one of Examples Ex39-Ex49, wherein the computing apparatus is further configured to execute or the method further comprises allowing a user to add a node graphical element corresponding to a sensor node defining the at least one monitoring route and remove a node graphical element corresponding to a sensor node defining the at least one monitoring route.

[0155] Example Ex51 : The system or method as in any one of Examples Ex39-Ex50, wherein at least one monitoring route includes a first monitoring route and a second monitoringroute, wherein the subset of sensor nodes defining the first monitoring route is different than the subset of sensor nodes defining the second monitoring route.

[0156] Example Ex52: The system or method as in Example Ex51, wherein one or more sensor nodes of the subset of sensor nodes defining the first monitoring route is the same as one or more sensor nodes of the subset of sensor nodes defining the second monitoring route.

[0157] Example Ex53: The system or method as in any one of Examples Ex39-Ex52, wherein the computing apparatus is further configured to execute or the method further comprises allowing a user to select a sensor node included in the plurality of sensor nodes, and display additional machine performance data that is associated with the sensor node in a dedicated space included in the graphical user interface, the additional machine performance data including one or more of electrical data and performance data plotted against time.

[0158] Example Ex54: The system or method as in any one of Examples Ex39-Ex53, wherein the computing apparatus is further configured to execute or the method further comprises allowing a user to select a node graphical element of the plurality of node graphical elements, and display a machine graphical region including additional machine performance data monitored by each sensor node monitoring the machine that is additive to the machine performance data displayed in the selected node graphical element.

[0159] All references and publications cited herein are expressly incorporated herein by reference in their entirety for all purposes, except to the extent any aspect directly contradicts this disclosure. This disclosure has been provided with reference to illustrative embodiments and is not meant to be construed in a limiting sense. As described previously, one skilled in the art will recognize that other various illustrative applications may use the techniques as described herein to take advantage of the beneficial characteristics of the apparatus and methods described herein. Various modifications of the illustrative embodiments, as well as additional embodiments of the disclosure, will be apparent upon reference to this description.

[0160] Unless otherwise indicated, all numbers expressing feature sizes, amounts, and physical properties used in the specification and claims may be understood as being modified either by the term “exactly” or “about.” Accordingly, unless indicated to the contrary, the numerical parameters set forth in the foregoing specification and attached claims are approximations that can vary depending upon the desired properties sought to be obtained by those skilled in the art utilizing the teachings disclosed herein or, for example, within typical ranges of experimental error.

[0161] As used herein, the term “configured to” may be used interchangeably with the terms “adapted to” or “structured to” unless the content of this disclosure clearly dictates otherwise.

[0162] The singular forms “a,” “an,” and “the” encompass embodiments having plural referents unless its context clearly dictates otherwise.

[0163] As used herein, “have,” “having,” “include,” “including,” “comprise,” “comprising” or the like are used in their open-ended sense, and generally mean “including, but not limited to.” It will be understood that “consisting essentially of,” “consisting of,” and the like are subsumed in “comprising,” and the like.

[0164] Reference to “one embodiment,” “an embodiment,” “certain embodiments,” or “some embodiments,” etc., means that a particular feature, configuration, composition, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. Thus, the appearances of such phrases in various places throughout are not necessarily referring to the same embodiment of the disclosure. Furthermore, the particular features, configurations, compositions, or characteristics may be combined in any suitable manner in one or more embodiments.

[0165] The words “preferred” and “preferably” refer to embodiments of the disclosure that may afford certain benefits, under certain circumstances. However, other embodiments may also be preferred, under the same or other circumstances. Furthermore, the recitation of one or more preferred embodiments does not imply that other embodiments are not useful and is not intended to exclude other embodiments from the scope of the disclosure.

Claims

CLAIMSWhat is claimed is:

1. An industrial facility monitoring system to monitor a plurality of machines, the system comprising: a plurality of sensor nodes, each sensor node of the plurality of sensor nodes operably coupled to a machine of the plurality of machines and configured to sense at least one parameter of the machine representative of one or more of an electrical, mechanical, and electromechanical property of the machine and transmit data representative of the at least one parameter; and at least one computing apparatus comprising one or more processors and operably coupled to the plurality of sensor nodes, the at least one computing apparatus configured to: receive the data representative of the at least one parameter from each of the plurality of sensor nodes; extract the at least one parameter from each of the plurality of sensor nodes from the data representative of the at least one parameter from each of the plurality of sensor nodes; provide a monitoring collection defined by a subset of sensor nodes of the plurality of sensor nodes that are associated with each other; allow a user to add or remove a sensor node from the subset of sensor nodes defining the monitoring collection; and determine performance data for the monitoring collection based on the extracted at least one parameter of the sensor nodes of the subset of sensor nodes defining the monitoring collection.

2. A method of monitoring a plurality of machines comprising: receiving data representative of at least one parameter from each of a plurality of sensor nodes, wherein the each sensor node of the plurality of sensor nodes operably coupled to a machine of the plurality of machines and configured to sense the at least one parameter of the machine representative of one or more of an electrical, mechanical, and electromechanical property of the machine and transmit the data representative of the at least one parameter;extracting the at least one parameter from each of the plurality of sensor nodes from the data representative of the at least one parameter from each of the plurality of sensor nodes; providing a monitoring collection defined by a subset of sensor nodes of the plurality of sensor nodes that are associated with each other; allowing a user to add or remove a sensor node from the subset of sensor nodes defining the monitoring collection; and determining performance data for the monitoring collection based on the extracted at least one parameter of the sensor nodes of the subset of sensor nodes defining the monitoring collection.

3. The system as in claim 1 or the method as in claim 2, wherein the at least one computing apparatus is further configured to execute or the method further comprises: receiving a user-generated request to add or remove a sensor node from the subset of sensor nodes defining the monitoring collection; and updating the monitoring collection based on the user-generated request.

4. The system or method as in any one of claims 1-3, wherein the performance data comprises one or more of power data, voltage data, current data, electrical cost data, motor status information, mechanical data, electromechanical data, breaker panel data, vibration data, and calculated carbon data.

5. The system or method as in any one of claims 1-4, wherein determining the performance data comprises: receiving a source of energy, wherein the source of energy comprises one or more of solar, wind, natural gas, coal, hydroelectric, biomass, oil, geothermal, and nuclear; and determining calculated carbon data based on the source of energy and the extracted at least one parameter of the sensor nodes of the subset of sensor nodes defining the monitoring collection.

6. The system or method as in any one of claims 1-5, wherein the performance data comprises one or more of aggregated power data, aggregated voltage data, and aggregated current data.

7. The system or method as in any one of claims 1-6, wherein determining performance data comprises determining an operational status of the machine coupled to each sensor node of the subset of sensor nodes defining the monitoring collection, wherein the operational status is indicative of an optimal status, a sub-optimal status, an unacceptable status, and an inactive status.

8. The system or method as in any one of claims 1-7, wherein the at least one computing apparatus is further configured to execute or the method further comprises: displaying, on a graphical user interface, at least one of the one or more of power data, voltage data, current data, electrical cost data, and motor status information.

9. The system or method as in any one of claims 1-8, wherein the at least one parameter comprises one or more of an electrical parameter of the machine, a temperature parameter of the machine, a natural gas consumption parameter of the machine, a machine health parameter of the machine, a water consumption parameter of a machine included in the plurality of machines, and a weight parameter of the machine.

10. The system as in any one of claims 1 and 3-9, wherein the at least one computing apparatus comprises a translator computing apparatus, an edge computing apparatus, and a node analysis computing apparatus, wherein the translator computing apparatus is configured to: receive the data representative of the at least one parameter from each of the plurality of sensor nodes; and extract the at least one parameter from each of the plurality of sensor nodes from the data representative of the at least one parameter from each of the plurality of sensor nodes, wherein the edge computing apparatus is configured to:determine the performance data for the monitoring collection based on the extracted at least one parameter of the sensor nodes of the subset of machines defining the monitoring collection, and the node analysis computing apparatus is configured to: provide the monitoring collection defined by the subset of sensor nodes of the plurality of sensor nodes that are associated with each other.

11. The system as in claim 10, wherein the translator computing apparatus is further configured to: generate translated first data representative of the at least one parameter from a first sensor node of the plurality of sensor nodes based on the data associated with the first sensor node formatted in a first data format, the translated first data being formatted in a second data format, the second data format being different from the first data format.

12. The system as in claim 11, wherein the second data format is configured to store the translated first data in a data store.

13. The system as in claim 12, wherein the at least one computing apparatus further comprises a real-time computing apparatus configured to: receive the extracted at least one parameter from the translator computing apparatus; and transmit the extracted at least one parameter to the edge computing apparatus.

14. The system as in claim 13, wherein the extracted at least one parameter comprises a time series of data packets, and wherein the real-time computing apparatus is further configured to: generate a first data block representative and based on a first subset of the time series of data packets; and generate a second data block based on a second subset of the time series of data packets.

15. The system or method as in any one of claims 1-14, wherein the at least one parameter comprises inrush current.

16. The system or method as in any one of claims 1-15, wherein the determining the performance data comprises: receiving a source of energy being at least one of an internal power source or an external power source; and determining calculated carbon data based on the source of energy and the extracted at least one parameter of the sensor nodes of the subset of sensor nodes defining the monitoring collection.

17. A system to monitor a plurality of machines, each machine monitored by at least one sensor node of a plurality sensor nodes, the system comprising: a display comprising a graphical user interface; and a computing apparatus comprising one or more processors and operably coupled to the display, wherein the computing apparatus is configured to: define at least one monitoring collection defined by a subset of sensor nodes of the plurality of sensors nodes monitoring a subset of machines of the plurality of machines that are associated with each other; receive machine performance data from each sensor node of the subset of sensor nodes defined by the at least one monitoring collection; display, on the graphical user interface, a plurality of node graphical elements, each node graphical element corresponding to and representative of a different sensor node of the plurality of sensor nodes, wherein each node graphical element comprises the machine performance data monitored by the corresponding sensor node; and display, on the graphical user interface, a route card for each of the at least one monitoring collections, wherein each route card comprises route performance data that is an aggregation of the machine performance data monitored by each sensor node of the subset of sensors nodes of the at least one monitoring collection.

18. A method of monitoring a plurality of machine, each machine monitored by at least one sensor node of a plurality sensor nodes, the method comprising: defining at least one monitoring collection defined by a subset of sensor nodes of the plurality of sensors nodes monitoring a subset of machines of the plurality of machines that are associated with each other; receiving machine performance data from each sensor node of the subset of sensor nodes defined by the at least one monitoring collection; displaying, on a graphical user interface, a plurality of node graphical elements, each node graphical element corresponding to and representative of a different sensor node of the plurality of sensor nodes, wherein each node graphical element comprises the machine performance data monitored by the corresponding sensor node; and displaying, on the graphical user interface, a route card for each of the at least one monitoring collections, wherein each route card comprises route performance data that is an aggregation of the machine performance data monitored by each sensor node of the subset of sensors nodes of the at least one monitoring collection.

19. The system as in claim 17 or the method as in claim 18, wherein the computing apparatus is further configured to display, on the graphical user interface, a plurality of route indicators, each route indicator extending between two node graphical elements corresponding to the at least one sensor node included in the at least one monitoring collection to graphically indicate the at least one monitoring collection.

20. The system or method as in any one of claims 17-19, wherein determining the route performance data comprises: receiving a source of energy, wherein the source of energy comprises one or more solar, wind, natural gas, coal, hydroelectric, biomass, oil, geothermal, and nuclear; and determining calculated carbon data based on the source of energy and the machine performance data.

Images