CN114945896A

CN114945896A - Automation management interface with multiple asset displays

Info

Publication number: CN114945896A
Application number: CN202080092876.7A
Authority: CN
Inventors: B.M.科菲
Original assignee: Bit Co ltd
Current assignee: Bit Co ltd
Priority date: 2019-11-19
Filing date: 2020-11-19
Publication date: 2022-08-26
Also published as: WO2021102110A1; EP4062271A4; JP2023503001A; KR20220098025A; EP4062271A1

Abstract

A system and method for displaying a combination of automated data collected from one or more assets and simulated data collected from systems or components associated with the assets may be simultaneously displayed on a display screen in a plurality of simultaneously displayed cyclical displays. In response to user input to the display screen, the data display is dynamically manipulated to display different numbers of operational cycles of the asset and associated simulation data collected in real-time as the operational cycles are executed so that patterns and/or correlations between the simulation data and automation data over the displayed timeline can be viewed and analyzed. The automation data is visually differentiated to indicate the operating cycle and the condition status of the asset in real time.

Description

Automation management interface with multiple asset displays

RELATED APPLICATIONS

This international application claims priority and benefit from us patent application No. 16/951,494 filed on day 11, month 18 of 2020 and us provisional application No. 62,937,516 filed on day 11, month 19 of 2019.

Technical Field

The present disclosure relates generally to dynamically displaying automation data to a display screen of a computing device, where the automation data is captured and collected from the automation device using an automation controller in communication with the automation device and the computing device.

Background

The facility may include an automation device including a plurality of machines organized into a plurality of lines. Each machine may be controlled by a Programmable Logic Controller (PLC) or similar controller connected to the machine and/or multiple stations, fixtures (fixtures) and elements of the machine, which may be collectively referred to as assets. Controllers in communication with the assets receive automation data, including inputs to the controllers, indicative of the condition status of various machines, stations, fixtures, and components. The controller may use the automation data to determine a cycle time and a condition status for each cycle of the operation performed by the asset. The data may be output to a display screen of the computing device for display. When the output data is displayed on the display screen for only a single asset, or for only one cycle of the sequence of operations, interactions between assets, such as between machines, workstations, fixtures, and elements, are difficult to identify, changes between cycles are visually insignificant, and opportunities to increase facility efficiency and reduce facility downtime may be missed.

Disclosure of Invention

A system and method for dynamically displaying automation data to a display screen of a computing device is provided, wherein automation data is captured and collected from the automation device into an Automated Operation System (AOS) using an automation controller in communication with the automation device and the computing device. An advantage of the systems and methods described herein is that a plurality of differently configured automated data displays generated from a plurality of corresponding display templates populated with real-time data can be displayed on a display screen to allow a user to monitor and analyze a plurality of automated assets in real-time, and/or to monitor and analyze a plurality of operational cycles of operations performed by the assets in real-time, such that identification of opportunities for improving automated operations and/or assets is accelerated. The system and method described herein also have the advantage of: the user is able to manipulate the automated data display to dynamically zoom in and out of the display, seamlessly transition the display between different levels of information detail, and to manipulate the automated data display to pan between different time periods and cycles of the automated operation. In one example, automation data for multiple assets may be simultaneously displayed on a display screen at different levels of information detail for comparison and analysis. In one example, automation data for multiple cycles of operation of an asset operation may be simultaneously displayed on a display screen.

The systems and methods described herein for displaying automation data of an automation system via an automation data display include, in a non-limiting example, an automation system including a plurality of assets, each asset of the plurality of assets being drivable to perform at least one operation of an ordered Sequence of Operations (SOP) of a plurality of cycles of operations, a server configured to collect automation data from the plurality of assets and store the automation data in a memory in communication with the server, the memory having stored thereon the sequence of operations, an asset tree identifying the plurality of assets, a plurality of automation data templates, and computer-executable instructions configured to generate a plurality of automation data displays and output the plurality of automation data displays and automation data in response to accepting user input from a user device, the user device including a user interface, the user interface is actuatable to display automation data including a plurality of automation data displays. The automation system is configured and actuatable to display an asset tree display on a user interface of the user device, the asset tree display displaying a plurality of assets and receiving a first user input to the user interface, the first user input indicating a selection of a first asset of the plurality of assets. The automation system is further configured to generate, in real-time, a first cyclical display of a first asset performing at least one operation of the plurality of cycles of operations, wherein the first cyclical display is selected from the group consisting of a cyclical state display, a heartbeat cyclical state display, and an operational Sequence (SOP) cyclical display. The automation system is further configured to display, via the user interface, a first loop display and a timeline display, wherein the timeline display displays an actual time associated with a first asset performing at least one operation of each of a plurality of operational loops displayed via the first loop.

The automation system is further configured to generate, via the automation system, an actual cycle time for each of a plurality of cycles of operation performed by the first asset, determine, via the automation system, a condition status for each of the plurality of cycles of operation performed by the first asset, and display, via the first cycle display, an indication of the actual cycle time and an indication of the condition status for each of the plurality of cycles of operation performed by the first asset. In one example, the first cycle display is a cycle status display, the indication of the actual cycle time is a cycle status bar displayed as an accumulated status of actual cycle times determined for the operating cycles performed in the time period displayed by the display timeline, and the indication of the condition status is determined by a comparison of the actual cycle times of the operating cycles to a baseline cycle time. In another example, the first loop display is a heartbeat loop status display, the indication of the actual loop time is an indication of the actual loop time displayed as determined for each operational loop performed by the first asset in the time period displayed by the display timeline, and the indication of the condition status is determined by a comparison of the actual loop time of the operational loop to a baseline loop time. In another example, the first loop is displayed as an SOP loop state display, the indication of actual loop time is an actual loop indicator of at least one operation, the system is further configured to display, via the user interface, the at least one operation performed by the first asset, display, for each cycle of the at least one operation performed by the first asset, the actual loop indicator of the at least one operation for a period of time displayed by the display timeline, wherein the actual loop indicator is displayed relative to the actual time that the cycle of operations was performed by the first asset, and display, for each cycle of the at least one operation performed by the first asset, a baseline loop indicator of the at least one operation, wherein the baseline loop indicator is displayed relative to the actual loop indicator.

In an illustrative example, the indication of the condition status includes a first condition status indication and a second condition status indication, wherein the first condition status indication is a cycle time condition indicated by displaying a baseline cycle indicator relative to an actual cycle indicator, and wherein the second condition status indication is an operating state condition indicated by displaying an actual cycle indicator that includes a condition status specifier corresponding to the operating state condition. In this example, the system may be further configured to determine, via the automation system, a second condition status for each cycle of operation of the at least one operation performed by the first asset, wherein the second condition status is one of an acceptable, blocked, default, or fault condition status, and display an actual cycle indicator including a condition status specifier corresponding to the second condition status.

The automation system may be configured to receive, by the automation system, a second user input to the user interface and modify the first cyclical display in response to the second user input, wherein modifying the first cyclical display may include zooming the first cyclical display or panning the first cyclical display such that zooming the first cyclical display drives zooming the first cyclical display and zooming the timeline display simultaneously and panning the first cyclical display drives panning the first cyclical display and the timeline display simultaneously. The automation system may be configured to receive, by the automation system, a second user input to the first cycle displayed data feature and display an information window in response to the second user input. The information window displays information defined by a data characteristic, wherein in the illustrative example, the data characteristic is one of an indication of an actual cycle time or an indication of a condition status.

In one example, the automation system is further configured to receive, by the automation system, a second user input to the first cyclical display, select, via the second user input, the first time period displayed by the first cyclical display, generate, in response to the second user input, the second cyclical display, and display, via the user interface, the second cyclical display for the first time period. In this example, the second cycle display may be selected from the group consisting of a cycle status display, a heartbeat cycle status display, and an operational Sequence (SOP) cycle display. In this example, the timeline display displays an actual time associated with a first asset performing at least one operation of each of a plurality of operational cycles displayed via the second cycle display, and the second cycle display, the first cycle display, and the timeline display are simultaneously displayed on the user interface. In an illustrative example, the first cycle display may be configured as a cycle status display and the second cycle display may be configured as a heartbeat cycle status display. The automated data display may also display a first director in the first rotation display, where the first director identifies the first time period in the first rotation display.

In a non-limiting example, the automation system is further configured to display a display menu on the user interface, receive, by the automation system, a third user input to the display menu, select, via the third user input, a simulation parameter associated with the sequence of operations, and generate a simulation parameter display in response to the third user input. The simulation parameter display is configured to display simulation data of the selected simulation parameter in real time, wherein the timeline display displays actual times associated with a plurality of cycles of operation displayed via the second cycle display. The example also includes displaying, via the user interface, the simulated parameter display for the first time period such that the simulated parameter display, the second loop display, the first loop display, and the timeline display are simultaneously displayed on the user interface.

The automation system is further configured to receive, by the automation system, a third user input to the second cyclical display, select, via the third user input, a second time period displayed by the first cyclical display, generate, in response to the second user input, a third cyclical display of the second time period in response to the second user input, and display, via the user interface, the third cyclical display, wherein the third cyclical display is selected from the group consisting of a cyclical state display, a heartbeat cyclical state display, and a Sequence of Operations (SOP) cyclical display, and cause the timeline display to display an actual time associated with the first asset performing at least one operation displayed via each of a plurality of operational cycles of the third cyclical display, wherein the third cyclical display, the second cyclical display, the first cyclical display, and the timeline display are displayed simultaneously on the user interface. The automation system may also be configured to display a second director in the second cyclical display, wherein the second director identifies a second time period in the second cyclical display. In a non-limiting example, the first cycle display is a cycle status display, the second cycle display is a heartbeat cycle status display, and the third cycle display is an SOP cycle status display.

The automation system may be further configured to receive, by the automation system, a fourth user input to the user interface, and modify the third cyclical display in response to the fourth user input, wherein modifying the fourth cyclical display may include zooming the third cyclical display and/or panning the third cyclical display, such that zooming the third cyclical display drives the third cyclical display and the timeline display to zoom simultaneously, and such that panning the third cyclical display drives the third cyclical display and the timeline display to pan simultaneously.

In an illustrative example, the automation system is configured to receive a first input to an asset tree displayed on the user interface, the first input indicating a selection of a first asset of a plurality of assets displayed by the asset tree, and receiving a second user input to the user interface, the second user input indicating a selection of a second asset of the plurality of assets, wherein at least the operation performed by the first asset is at least a first operation of a Sequence of Operations (SOP), and wherein the second asset is drivable to perform at least a second operation of a Sequence of Operations (SOP) of the plurality of cycles of operations, and generating, via the automation system and in real-time, a second cyclical display of a second asset performing at least one operation of the plurality of cycles of operations, wherein the second cycle display is selected from the group consisting of a cycle status display, a heartbeat cycle status display, and an operational Sequence (SOP) cycle display. In this example, the automation system is further configured to display, via the user interface, the second loop display and the timeline display, such that the timeline display displays an actual time associated with a second asset performing at least a second operation of each of the plurality of operational loops displayed via the second loop display, and such that the second loop display, the first loop display, and the timeline display are simultaneously displayed on the user interface.

The automation system is further configured to generate, via the automation system, an actual cycle time for each of a plurality of cycles of operation performed by the second asset, determine, via the automation system, a condition status for each of the plurality of cycles of operation performed by the second asset, and display, via the second cycle display, an indication of the actual cycle time and an indication of the condition status for each of the plurality of cycles of operation performed by the second asset. In one example, the first looping display is a looping status display of a first asset and the second looping display is a looping status display of a second asset.

The above features and advantages and other features and advantages of the present teachings are readily apparent from the following detailed description of some of the best modes and other embodiments for carrying out the present teachings when taken in connection with the accompanying drawings.

Drawings

FIG. 1 is a schematic, exemplary representation of an automated data display generated by the system shown in FIG. 27 for display on a display screen of the user device shown in FIG. 29, the exemplary representation displaying a menu and an asset tree for receiving user input to drive the automated data display;

FIG. 2 is a schematic illustration of an automated data display generated by the system shown in FIG. 27 showing an expanded asset tree and a rotation status display of a selected asset from the asset tree via user input to the automated data display;

FIG. 3 is a schematic illustration of an automated data display generated by the system shown in FIG. 27 showing an expanded view of the loop status display shown in FIG. 2;

FIG. 4 is a schematic illustration of an automated data display generated by the system shown in FIG. 27 showing a selected time period including a selected loop status bar selected by user input while displaying an information window activated by selection of the loop status bar;

FIG. 5 is a schematic illustration of an automated data display generated by the system shown in FIG. 27 showing a heartbeat cycle status display for a selected time period shown in FIG. 4, while displaying an information window activated by user input to one or more heartbeat cycle bars; simultaneously displaying the circulatory state display of fig. 4 and an orienter for orienting the heartbeat circulatory state display to a selected time period of the circulatory state display;

FIG. 6 is a schematic, exemplary representation of an automated data display generated by the system shown in FIG. 27, displaying the heartbeat cycle status and cycle status display shown in FIG. 5, and concurrently displaying a user input selecting a time period including one or more heartbeat cycle bars;

FIG. 7 is a schematic illustration of an automated data display generated by the system shown in FIG. 27, the illustration showing the heartbeat cycle status and cycle status displays shown in FIG. 6, and concurrently displaying a Sequence of Operations (SOP) performed by a selected asset, wherein the SOP timeline corresponds to a time period of the selected heartbeat cycle bar, the heartbeat cycle status display including an orienter for orienting a selected time of the heartbeat cycle status display to the SOP timeline;

FIG. 8 is a schematic illustration of an automated data display generated by the system shown in FIG. 27 showing the heartbeat cycle status display, and SOP timelines shown in FIG. 7, while simultaneously displaying baseline and actual cycle time indicators, cycle status, and condition status messages for each of a plurality of cycles of the sequence of operations performed by the selected asset within the time period of the selected heartbeat cycle bar;

FIG. 9 is a schematic, exemplary representation of an automated data display generated by the system shown in FIG. 27, the exemplary representation displaying the automated data display shown in FIG. 8, wherein the SOP cycle status display is enlarged in response to user input to the user interface;

FIG. 10 is a schematic illustration of an automated data display generated by the system shown in FIG. 27, the illustration showing the automated data display shown in FIG. 9, wherein the SOP cycle status display is further enlarged in response to user input to the user interface;

FIG. 11 is a schematic illustration of an automated data display generated by the system shown in FIG. 27, the illustration showing the automated data display shown in FIG. 10, wherein the SOP cycle status display is shifted to the right along the SOP timeline in response to user input to the user interface;

FIG. 12 is a schematic exemplary representation of an automated data display generated by the system shown in FIG. 27, the exemplary representation displaying the automated data display shown in FIG. 11, wherein in response to user input to the user interface, the SOP cycle status display is scaled to display a single cycle of SOP and concurrently displays an information window of a cycle of operation of the SOP displayed in response to user input to the user interface;

FIG. 13 is a schematic illustration of an automated data display generated by the system shown in FIG. 27, the illustration showing the automated data display shown in FIG. 12 with an SOP cycle status display expanded to display sub-operations of an operation selected by a user input to the user interface;

FIG. 14 is a schematic, exemplary representation of an automated data display generated by the system shown in FIG. 27, the exemplary representation displaying the automated data display shown in FIG. 13, wherein the SOP cycle state display is collapsed to no longer display sub-operations of an operation selected by a user input to the user interface, and the cycle state display is collapsed such that the SOP cycle state display is vertically expanded in the user interface;

FIG. 15 is a schematic illustration of an automated data display generated by the system shown in FIG. 27, showing the automated data display shown in FIG. 14, further showing a display options menu for selecting display features including a simulation parameter display;

FIG. 16 is a schematic illustration of an automated data display generated by the system shown in FIG. 27, the illustration showing the automated data display shown in FIG. 15 and further showing a selected simulation parameter display, the simulation parameter data being displayed in real time with a corresponding cycle indicator shown in the SOP cycle status display;

FIG. 17 is a schematic illustration of an automated data display generated by the system shown in FIG. 27 showing the automated data display shown in FIG. 16 zoomed out to show additional cycles and to see variability of parameter data over a longer period of time;

FIG. 18 is a schematic, exemplary representation of an automated data display generated by the system shown in FIG. 27 showing an expanded asset tree and indicating a selection of a plurality of assets from the asset tree by user input to the automated data display;

FIG. 19 is a schematic illustration of an automated data display generated by the system shown in FIG. 27, the illustration showing a cyclical state display of the selected asset of FIG. 18 and concurrently displaying a first SOP cyclical state display of the first asset and a second SOP cyclical state display of the second asset, each of the first and second SOP cyclical state displays corresponding to a time period selected from the cyclical state display and indicated in the cyclical state display by the director data feature;

FIG. 20 is a schematic exemplary representation of an automated data display generated by the system shown in FIG. 27, the exemplary representation displaying the automated data display shown in FIG. 19, zoomed-in to expand the view of the loop in the first SOP loop state display and the second SOP loop state display, and displaying user input to a "collapse" icon associated with the loop state display;

FIG. 21 is a schematic illustration of an automated data display generated by the system shown in FIG. 27, the illustration showing the automated data display shown in FIG. 20 with the cycle state display collapsed and the first SOP cycle state display and the second SOP cycle state display vertically expanded in the user interface;

FIG. 22 is a schematic illustration of the automated data display generated by the system shown in FIG. 27 showing the automated data display shown in FIG. 21 enlarged and translated to show a horizontally expanded view of a selected loop executed by the first and second assets and displayed via the first and second SOP loop status displays;

FIG. 23 is a schematic exemplary representation of an automated data display generated by the system shown in FIG. 27, the exemplary representation displaying the automated data display shown in FIG. 22, further enlarged and further illustrating an information window displayed in response to user input to a selected cycle bar of the first SOP cycle status display;

FIG. 24 is a schematic illustration of an automated data display generated by the system shown in FIG. 27, the illustration showing display of the automated data display shown in FIG. 23, further expanding the first SOP cycle status display via user input to the first asset icon to display an SOP cycle indicator for each operation performed by the first asset over a plurality of cycles of operations performed by the first asset;

FIG. 25 is a schematic illustration of an automated data display generated by the system shown in FIG. 27, the illustration showing the automated data display shown in FIG. 24 further developing a first SOP cycle status display via user input to a first action icon associated with a first asset to display an SOP cycle indicator for each sub-operation of a selected operation performed by the first asset over a plurality of operation cycles performed by the first asset;

FIG. 26 is a schematic, exemplary representation of an automated data display generated by the system shown in FIG. 27, the exemplary representation displaying a legend in response to user input to a legend menu icon indicating various specifiers (diffiers) including color coding and shading for differentiating various data features, wherein each specifier is associated with an identified condition status:

FIG. 27 is a schematic view of an example of an automated operations and management system (AOS) including first, second, third, and fourth level controllers;

FIG. 28 is a schematic view of an example of a machine of the AOS shown in FIG. 27, the machine including a first level controller and a second level controller;

FIG. 29 is a schematic diagram of an example of the user equipment of FIG. 27; and

FIG. 30 is a schematic illustration of a method of dynamically displaying automation information using the system of FIG. 27.

Detailed Description

Referring to the drawings, wherein like reference numbers represent like components throughout the several views, the elements shown in fig. 1-30 are not to scale or to scale. Thus, the particular dimensions and applications provided in the figures provided herein should not be considered limiting. Fig. 1-26 show examples of an automation data display 138 that may be generated by server L of Automation Operating System (AOS)10 as shown in fig. 27-28 by populating one or more display templates 137 with data stored in AOS 10 in communication with user device U for display on display screen 74 of user device U as shown in fig. 29. The display screen 74 of the user device U may also be referred to herein as the user interface 74. An exemplary method 200 of dynamically modifying the automated data display 138 shown on the display screen 74 in response to user input 153 received by the user interface 74 is shown in fig. 30 and in fig. 1-26, which methods will be described in further detail herein.

In an illustrative example, fig. 1 shows a display screen 74 for displaying automation information, also referred to herein as automation data, in one or more automation data displays 138, also referred to herein as information displays and/or automation displays 138. Each automation data display 138 is generated by populating the data template 137 in real-time with automation data collected by an automation operation and management system (such as the automation operation and management system 10 shown in fig. 27-29), where the automation operation and management system (AOS)10 is configured to control a facility 14, a system SY, a machine 16, a station ST, an element E, a sensor S, etc. operating within the enterprise 12. The enterprise 12 includes an enterprise server L4 for receiving and merging data from multiple facilities 14 within the enterprise 12. Each facility 14 includes a facility server L3 for receiving and merging data from a plurality of facility systems SY within each facility 14. Each facility server L3 communicates with an enterprise server L4. At least one of the facility systems SY in each facility 14 includes a plurality of machines 16. Machine 16 may be any machine that performs coordinated operations, including an automated machine. In the illustrative and non-limiting examples described herein, machine 16 may be a machine such as an automated machine that performs operations in a manufacturing plant and/or assembly facility.

Each machine 16 may include one or more stations ST for performing an ordered sequence of operations OP to be performed by the machine 16, where the sequence of operations 39 includes operations OP to be performed by the machine 16 in a predetermined order that is controlled by a controller L in communication with the machine 16. The predetermined order in which the operations OP are performed may be defined by a sequence 39 of operations of the machine 16 by the controller L. It will be appreciated that the machine 16 will in operation under the control of the machine controller L repeatedly perform a sequence of operations 39 comprising ordered operations OP such that the automation data collected from the machine 16 will comprise automation data from each cycle of repeated operations 15 whereby a cycle time for performing each cycle of repeated operations 15 can be determined for the operation OP being performed.

Each station ST may include one or more elements E for performing various operations and/or tasks of the respective station ST. Using the illustrative example of manufacturing and/or assembly enterprise 12, examples of elements E for performing various operations of the manufacturing and/or assembly operations performed by machines 16 and/or stations ST may include clamps, cylinders, grippers, pins, slides, fixtures, trays, and the like, with the examples provided herein being non-limiting. Herein, facilities, areas, lines, machines, stations, fixtures and elements may be referred to individually and collectively as assets 151, and/or as automated assets and/or as digitized assets.

The automation data collected and/or generated by AOS 10 may include condition status data for assets 151, where, as used herein, a status, which may be referred to as a condition status or condition, refers to a status of an asset, an object (such as a workpiece) operated by an asset, a condition, a state, a parameter, a location, or other monitored, measured, and/or sensed attribute. Non-limiting examples of condition states include a cycle start time, a cycle stop time, a component start time, a component travel, a component stop time, a position of a component or object, dimensional measurements or parameters of an object, dimensional measurements or parameters of which may include dimensional measurements of features of component E, features of machine 16, features of a workpiece on which machine 16 or component E is performing operations, conditions of one or more of component E, machine 16 or a workpiece, or environmental conditions within facility 14. The condition states may further include, for example, operating conditions of the asset 151, such as open, closed, automatic, manual, stalled, blocked, default, travel, stopped, failed, row, good, bad, within tolerance, out of tolerance, present, absent, extended, retracted, high, low, etc., and may include, for example, measurements of physical properties, such as chemistry, temperature, color, shape, location, dimensional conditions (such as size), surface finish, thread form, functional parameters such as voltage, current, torque, pressure, force, etc., such that it is understood that the terms state, condition state, and/or parameter describing the inputs of the AOS 10 are intended to be broadly defined.

The predetermined sequence of operations performed in the operational cycle 15 may be defined by the sequence of operations 39 defined for the machine 16 by the controller L controlling the machine 16. The machine 16 will in operation repeatedly perform one or more operations OP comprising a sequence of operations 39 under the control of the controller L. The condition status data collected during the execution of each operational cycle 15 of the operations OP in the operational sequence 39, including, for example, one or more of a cycle start time, a cycle stop time, an element start time, an element stop time, etc., may be used by the machine controller L, the facility server L3, and/or the enterprise server L4 to calculate an actual cycle time for the execution of each operation OP by the asset 151 executing the operation OP, where the actual cycle time is determined in real-time in the preferred example. The operating cycle times may be collected and stored in AOS memory 90 as automation data for populating display template 137 to generate automation data display 138 for display on display screen 74 of user device U, which may be configured as user device U shown in fig. 29 in a non-limiting example.

For illustrative purposes and as a non-limiting example, enterprise 12 may be a manufacturing enterprise including a plurality of manufacturing and/or assembly facilities 14, and the plurality of manufacturing and/or assembly facilities 14 may be co-located within manufacturing enterprise 12. In another example, each facility 14 may be a stand-alone plant that may be geographically separated from each other and in communication with each other with enterprise server L4, e.g., via network 80. For purposes of illustration, at least one of the facilities 14 includes a facility server L3 in communication with a plurality of systems SY operating in the facility 14. In the example shown, one of the systems SY comprises a manufacturing and/or assembly operation involving a plurality of machines 16.

Another system SY in the facility 14 may be a facility management system, which may be referred to herein as a facility infrastructure system SY, for monitoring, measuring and/or controlling various factors of the infrastructure and operating environment of the facility 14, such as the supply of electrical power provided to various machines 16, the supply of water provided to hydraulic and/or coolant systems within the facility 14 and/or coolant systems associated with the machines 16, the supply of compressed air provided within the facility 14, e.g. to the pneumatic and/or pneumatically operated elements E of the machines 16, the ambient temperature of the machine environment, the ambient humidity of the machine environment, etc. It will be appreciated that variability in each power source, water supply, compressed air supply, ambient temperature and ambient humidity may affect the operation, efficiency and downtime of one or more of machines 16 and/or elements E, and therefore, measuring one or more of these system parameters while machines 16 are operating will provide parametric data that may be correlated in real time with automation data collected from automation assets including machines 16 for use in conjunction with the automation data to analyze the cause of the change in the operating cycle time of operations OP performed by automation assets 151. In one example, infrastructure and/or parameter data may be measured and output as simulation data 167, the simulation data 167 being saved to AOS memory 90 and associated by enterprise server L4 in real time with automation data collected by facility and machine controllers L3, L for populating display template 137 to generate automation data display 138 for display on display screen 74 of user device U. This example is non-limiting, and it should be understood that automation data collected from automation assets 151 may include both digital and analog data, such that the term automation data as used herein may include both digital and analog data.

Referring to the figures, AOS 10 may further include one or more user devices U in communication with enterprise 12 via a wired connection or a wireless connection, such as via network 80. By way of non-limiting example, user device U may be a personal computing device such as a personal computer, tablet, laptop, smartphone, personal digital assistant, or other personal computing device for viewing information including data related to enterprise 12 and/or data provided by enterprise 12 via AOS 10. User device U may include a user interface 74, such as a touch screen, for viewing automated data displays 138 generated by AOS 10 and for interacting with automated data displays 138 and the displayed information and automated data via user input 153 to display screen 74. The user interface 74 may also be referred to herein as a display screen, touch screen, and/or Graphical User Interface (GUI). In one example, the user device U may simultaneously display multiple automated data displays 138 on the display screen 74 of the user device U, where each automated data display 138 may be manipulated by user input 153 to the display screen 74, e.g., zoomed in and out and/or panned, collapsed and/or expanded, activated to display associated text, and as further shown in fig. 1-6.

The user device includes a processor 76 and memory 78, some of which is computer-readable tangible, non-transitory memory disposed on a printed circuit board or otherwise available to the processor 76. For example, the memory 78 may include sufficient Read Only Memory (ROM), optical memory, flash or other solid state memory, or the like. Temporary memory such as Random Access Memory (RAM) and Electrically Erasable Programmable Read Only Memory (EEPROM) may also be included, as well as other circuitry as desired (not shown), including but not limited to a high speed clock, position sensing circuitry, analog-to-digital (a/D) circuitry, digital-to-analog (D/a) circuitry, a digital signal processor, and any necessary input/output (I/O) devices, as well as other signal conditioning and/or buffer circuitry. The user device U may include a connector port 72 for connecting the user device to another device (not shown). User device U includes a communication interface, which may be a wireless or wired interface, for connecting user device U to network 80 for communication with one or more of controller and/or server L, another of user devices U, and/or AOS data storage memory 90. The user device U includes a Graphical User Interface (GUI)74, which in the preferred example is a graphical touch screen, such that a user may provide user inputs 153, including commands, to the user device U via the touch screen 74 and/or the standard toolbar 82. The graphical user interface 74 may also be referred to herein as a display screen, touch screen, and/or user interface 74. Non-limiting examples of user inputs 153 include stylus and/or touch gestures applied to the display screen 74, including one or more of a tap, double tap, drag, swipe, hold/press, sweep, pinch and spread gesture, for manipulating the automated data display 138. Non-limiting examples of user input 153 may further include one or more inputs including, for example, point and click, click and drag, scroll, keystroke inputs via a keyboard, touchpad, trackpad, trackball, and/or mouse in communication with user device U and/or display screen 74.

Fig. 1-26 show examples of automated data displays 138 that may be generated by a server L of an AOS by populating one or more display templates 137 with data stored within AOS 10 for display on a display screen 74 of a user device U. 1-26 illustrate a method of dynamically modifying an automated data display 138 displayed on the display screen 74 in response to user input received by the display screen 74. In the example shown in the figure, display screen 74 shows one or more automated data displays 138 that are generated by populating display templates 137 with data, such as automated data collected from enterprise 12 and stored in AOS storage 90. In an illustrative example, an automated data display 138, such as any of the automated data displays 138 shown in the figures, may be generated by the facility server L3 by populating the display template 137 with automation data collected from the facility 14, machines 16, elements E, stations ST and/or infrastructure or environmental data collected from the system SY, where the data is collected and stored to a memory, such as the data store storage 90, for use by the server L in generating the automated data display 138. A plurality of display templates 137 may be stored on the data storage 90 and retrieved by the facility server L3 to generate corresponding automated data displays 138 in real-time. Data store 90 may be a stand-alone enterprise memory store 90, in communication with enterprise 12 via network 80, and/or may comprise a distributed memory store within enterprise 12. A plurality of automation data displays 138 generated from corresponding data templates 137 are shown in fig. 1-26, including, for example, a heartbeat cycle state display 11, a Sequence of Operations (SOP) cycle state display 13, a plurality of asset displays 65, an asset tree display 152 (also referred to herein as an object tree display), a cycle state display 155, and a simulation display 165.

The automation data, including simulation parameter data, is collected and stored in real-time to the data storage 90 so that a server, e.g., facility server L3 in this example, can populate the display template 137 to generate the automation data display 138 in real-time. The term "real-time" as used herein refers to the level of responsiveness of computing devices included in enterprise 12, including, for example, servers and controllers L, data storage memory 90, user devices U, etc., that is perceived by a user as sufficiently immediate that the computing devices' responsiveness in collecting and displaying data in automated data display 138 is not delayed, e.g., perceived as occurring at substantially the same time and rate as the displayed data. In this example, data is collected from the automated assets and systems SY in real time, e.g., without delay, so that the data may be populated into the display template 137 and displayed on the user device U as the automated data display 138 in real time, e.g., so that the data displayed on the automated data display 138 is displayed sufficiently immediately when the data is generated by an originating source (e.g., sensor S) so that the user may view the data displayed in the automated data display 138, e.g., through the display screen 74 of the user device U, immediately when the data is generated, and/or immediately when an event occurs that the data is generated, e.g., immediately when the machine 16 performs an operation. When the data is collected and stored in the data store storage 90, it may be associated in the data store storage 90, for example, in a data matrix provided for this purpose, with identification information, which may include data sources, such as sensors identifying the generated data, condition states and/or parameters represented by the data, e.g., data characteristics 141 corresponding to the data, one or more of the operations Op, machines 16, elements E, facilities 14 and/or systems SY associated with the data, and data times associated with the data. The data time associated with the data may be one of the times at which the data was generated, e.g., the time at which the data was sensed by the machine, element, fixture, station, sensor, etc. that is generating the data, and the time at which the data was stored to the data storage device. In real-time, the time at which data is sensed and the time at which data is stored should be substantially equal, as these events are direct to each other in the real-time system described herein. This example is non-limiting, and it is understood that another time, such as a timestamp applied by the controller or server, may be used as the data time. In one example, the data feature 141 may be displayed as a distinguishing data feature 142, the distinguishing data feature 142 being distinguished, for example, by appearance (color, shading, shape, contour, etc.) to indicate a condition state associated with the data feature 141. In the non-limiting example shown by the legend shown in fig. 26, different colors and/or shading may be associated with different condition states to visually distinguish data features 141 such as cycle status bar 158, heartbeat cycle bar 15, actual cycle time indicator 31, cycle status 19, condition status message 163, etc., and as shown herein and by the figures.

Referring again to the figures, fig. 1-26 and 30 are described herein to illustrate a method of displaying automation data in real time using an Automation Operating System (AOS) as shown in fig. 27-29. In one example, one or more operational cycles 15 of one or more operations OP performed by the asset 151 are displayed on the display screen 74 of the user device U simultaneously with an actual timeline display 33 displaying an actual (clock) time 33 corresponding to the operational cycle 15. In response to user input 153 to the display screen 74, the automation data display 138, including the actual timeline display 33, may be dynamically manipulated to display different levels of detail of the selected operational cycles 15 of automation data, and so that the displayed operations OP and/or variability between operational cycles 15 may be viewed and analyzed relative to the actual clock time 37 associated with each operational cycle 15. In one example, one or more respective ones of the one or more operational cycles 15 performed by the plurality of assets 151 may be simultaneously displayed on the display screen 74, and in response to user input 153 to the display screen 74, the automated data display 138 may be dynamically manipulated to display different numbers of assets 151, different numbers of operational cycles, and different levels of detail of the selected operational cycle 15 simultaneously displayed with the actual timeline 33 and/or the clock time 37 associated with each operational cycle 15, and such that variability between the assets and the operational cycles 15 may be viewed and analyzed in real time and/or within the time period shown in the timeline 33. In one example, a combination of automation data collected from one or more assets and simulation data collected from, for example, systems or components associated with the assets, may be simultaneously displayed on a display screen, and in response to user input to the display screen, the automation data display 138 may be dynamically manipulated to display a different number of operational cycles 15 of the assets and the associated simulation data collected in real-time as the operational cycles 15 are executed so that patterns and/or correlations between the simulation data and the automation data may be viewed and analyzed on the displayed timeline 33.

Referring to FIG. 1, there is shown a user device U including a user interface 74 for displaying one or more automated data displays 138, wherein each automated data display 138 is generated in real-time by populating a corresponding data template 137 with automated data retrieved, for example, from AOS memory 90. The user interface 74 may also be referred to herein as a display screen 74. In one example, the user device U communicates with the enterprise server L4 or one or more of the facility or machine controllers L3, L, communicates with the AOS memory such that when a user input 153 is input to the display screen 74 of the user device U, the user input 153 drives a modification of the automated data display 138 and/or a display of additional information, such as another automated data display 138, an information box 61, etc., via the display screen 74. In the example shown in FIG. 1, the example of the initial display screen 74 presented to the user may include a display menu 150, a legend icon 156, a toolbar 82, and an options menu 164. The display menu 150 includes an icon that can be selected by the user input 153 to drive the display of the type of automated data display 138 associated with the icon. In the illustrated example, the display menu 150 includes an object tree icon 154A for driving the object tree display 152, a dashboard icon 154B for driving the dashboard display, a cycle icon 154C for driving a selected one of a plurality of cycle displays including a cycle status display 155, a heartbeat cycle status display 11, and an SOP cycle status display 13, and a message icon 154D for driving the condition status message display 162. The object tree 152 may also be referred to herein as an asset tree 152.

In the example shown in FIG. 1, a user input 153, such as a touch click or a mouse click, has been entered into an object tree icon 154A of the display screen 74 to drive the display of the asset tree 152. In the non-limiting example, the asset tree 152 is initially displayed on the display screen 74 as shown in FIG. 1, displaying the enterprise assets 12, which in the illustrated example include the assets identified in FIG. 1 as the

facilities

14A and 14B. In the example shown in asset tree display 152, each of the assets 151 associated with a corresponding expand/collapse icon and a corresponding selection box is shown, each of which may be used to drive the screen display 74 to modify information and/or data displayed on the screen display 74.

In the example shown in fig. 2, user input 153 is input to display screen 74 to an expansion icon corresponding to facility 14A, AOS 10 is driven to display a next level asset 151 of facility 14A, as shown in fig. 2, facility 14A includes a system SY. In the example shown in fig. 2, the user input 153 is input to the display screen 74 to an expansion icon corresponding to the system SY driving the display of the next level asset 151 of the system SY, which, as shown in fig. 2, comprises the machine 16. In the example shown in FIG. 2, user input 153 is input to display screen 74 to an expansion icon corresponding to machine 16, driving the display of next level assets 151 of machine 16, as shown in FIG. 2, machine 16 includes first station ST1 and second station ST 2. In the example shown in FIG. 2, the user input 153 is input to the expansion icon corresponding to the first stop ST1, driving the display of the next level asset 151 of the first stop ST1, the next level asset 151 including the first element E1 and the second element E2 as shown in FIG. 2. In the example shown, in asset tree 152, E1 is identified as a fixture having an asset description of "S01 fixture" and E2 is identified as a station element having an asset description of "R01".

In the example shown in FIG. 2, user input 153 is entered into a checkbox corresponding to element E1, which automatically populates the checkbox for the higher level asset 151, including element E1, and further drives display screen 74 to generate and display a cyclical status display 155 for the selected asset 151 in FIG. 6, which asset 151 is element E1 in this example, identified in asset tree 152 as "S01 fixture". As shown in fig. 2 and 3, the display screen 74 gradually transitions to the recurring status display 155 generated for the asset "S01 fixture" and displays the selected asset 151, in this example "S01 fixture", associated with the recurring status display 155 being generated at 160. The cyclical state display 155 is generated by populating in real time the display template 137 corresponding to the cyclical state display 155 with data retrieved from the AOS memory 90. The data retrieved from AOS 90 may include data retrieved in real-time from a selected asset 160, which selected asset 160 in this example is element E1, i.e., "S01 fixture".

In the example shown in fig. 2 and 3, the cycle status display 155 includes a plurality of cycle status bars 158, each representing the cumulative status of an operating cycle completed by a selected asset 160 over a time period 157. In the present example, the duration of the time period 157 is one hour, such that each cycle status bar represents the cumulative status of the operating cycles performed by element E1 over that hour. The cycle status bar 158, which may also be referred to herein as a data feature 141, is a distinguishing data feature 142 in this example, having

bar portions

159A, 159B distinguished, for example, by color, by shading, and/or by a combination of these, to indicate a condition status of a percentage of the total bars that are in that condition status in the corresponding one-hour time period 157. Referring to FIG. 26, a legend 77 is shown that cross-references the condition states to the specifiers shown in the figure. In the specification, the specifier may be represented by a color, and in the drawings, the specifier may be represented by a hatching pattern associated with the color described in the legend 77 so as to reproduce the drawings as black and white. In this example, the orange color of the bar portion 159A represents the percentage of the total operating cycles 15 performed in that time period 157, the total operating cycles 15 completed over a cycle, e.g., completed in an actual cycle time that is longer than the baseline cycle time, and the red color of the bar portion 159B represents the percentage of the total operating cycles 15 that were in the fault state during that time period 157, with the shading pattern corresponding to each of the orange and red colors being shown as legend 77 of fig. 26. This example is illustrative so that the cycle bar 158 can include other colored portions 159 to indicate other condition states, such as green for operating cycles performed within an acceptable range of baseline cycle times, or orange for warning operating cycles that should be observed or investigated.

In the example shown in FIG. 3, the user input 153 is input into a "collapse" icon included in the toolbar 82 that drives the display 74 to transition to the display shown in FIG. 3 by collapsing the object tree 152 and increasing the number of time periods 157 and loop status bars 158 that may be displayed in the display 74. In the example shown in FIG. 3, a parameter descriptor 166 is displayed to identify the parameters shown in the automation data display 138. In this example, the parameter descriptor 166A is displayed as "percent of cycled state per hour," identifying the automation data display 138 shown in FIG. 3 as the cycled state display 155.

In the example shown in FIG. 3, user input 153 is input to the display screen 74 at the status bar 158A, driving the display screen to display an information box 61, the information box 61 including data and/or other information in the AOS memory 90 associated with the operational cycle 15 performed by the selected asset 151 during the selected time period 157A, such as the operational cycle 15 performed by the S01 fixture. In the example shown, the information box 61 includes a legend of color codes and associated conditions and reports the actual number of operating cycles 15 at each condition during the selected time period 157A. In the example shown, information box 61 reports a total of 358 operating cycles, including 319 over-cycle time (orange) operating cycles (89%) and 39 fault (red) operating cycles (11%), performed by the S01 fixtures (e.g., the selected asset 160) during the one-hour period 157A.

In the example shown in fig. 4 and 5, the user input 153 is applied to the display screen 74 to select the cycle status bar 158A and the time period 157A, for example, by a touch input such as a drag or double-click, or by scrolling over the cycle status bar 158A to drive the screen display 74 to generate another automated data display 138 shown in fig. 5 that is displayed concurrently with the currently displayed cycle status display 155. In the example shown in fig. 5, the second automated data display 138 is configured as a heartbeat cycle status display 11, also referred to herein as heartbeat display 11, wherein each vertical bar in the heartbeat display 11 indicates an actual cycle time of the operational cycle 15 performed by the selected asset 160 (e.g., by the S01 fixture in this example) during the selected time period 157 a. As shown in FIG. 5, the heartbeat display 11 and the circulatory state display 155 are displayed simultaneously, with the time period 157A displayed in the heartbeat display 11 being directed to the circulatory state display 155 by the directional feature 161A. In this example, the orientation feature 161A is a white background surrounding the selected cycle status bar 158A so that it is displayed in the heartbeat display 11 which operational cycles 15 are instantaneously visible. The heartbeat display 11 includes a parameter descriptor 166B identifying the heartbeat display 11, where the identifier "cycle" is followed by a display period 157A in clock time.

In the example shown in fig. 5, the cycle bar indicating each operation cycle 15 is a data feature 141 of the heartbeat display 11 and may be characterized as a distinguishing data feature 142, wherein the condition status of each operation cycle 15 is indicated by the display color of the corresponding cycle bar. For example, a consistent color coding may be used for easy identification by a user/viewer of the display screen 74, such that in this example, an orange cycle bar indicates an over cycle operating cycle 15 and a red cycle bar indicates a failed operating cycle 15. In one example, a numeric indicia 101 may be associated with an operation cycle 15, which is displayed as a vertical line in the heartbeat display 11, indicating that additional information, such as an observation or corrective action related to the associated operation cycle 15, has been stored in the AOS memory 90 associated with the respective operation cycle 15. In one example, user input 153 applied to digital marking 101 drives display screen 74 to display additional information, for example, in information box 61.

In the example shown in fig. 6, user input 153 is input to the display screen 74 by selecting one or more of the operational cycles 15 shown in the heartbeat display 11. In this example, a set of operating cycles 15 performed during the time period 157B is selected by the user input 153, driving the display screen 74 to display the third and fourth automated data displays 138 simultaneously with the heartbeat display 11 and the cycle status display 155. As shown in fig. 7-13, the third automated data display 138 is configured as a Sequence of Operations (SOP) cycle status display 13, also referred to herein as an SOP cycle status display 13, and the fourth automated data display 138 is configured as a condition status message display 163 overlaid on the SOP cycle status display 13. In the example shown in fig. 7-13, the time period 157A displayed in the heartbeat display 11 is directed to the cycle status display 155 by the orientation feature 161A, and the time period 157B, which is a subset of the time period 157A, is directed to the SOP cycle status display 13 and the conditional status message display 162 by the orientation feature 161B. In this example, the directional feature 161B is a white background surrounding the selected operational cycle 15 selected in the heartbeat display 11, such that it is displayed in the SOP cycle status display 13 and the conditional status message display 162 which operational cycles 15 are instantaneously visible. In addition, the clock time within the time loop 157B is indicated in a horizontal timeline along the top (as viewed on the page) of the SOP loop status display 13 and the overlay condition status message display 162 to direct the displayed operational loop 15 to the selected time segment 157B.

In the example shown in FIG. 7, in response to the user input 153 selecting the time period 157B, the third display template 137 corresponding to the SOP state cycle display 13 is populated with data associated with the selected asset 160, e.g., E1, also described in the example as "S01 fixtures," including a Sequence of Operations (SOP)39A performed by the selected asset E1, wherein the SOP 39A is performed during each cycle of operations 15 performed by the selected asset E1. In the illustrated example, the SOP 39A includes operations OP1, OP2, OP3, OP4 that are performed sequentially in an order defined by the SOP 39A shown in the SOP loop display 13, wherein the operations OP1, OP2, OP3, OP4 are performed sequentially during each cycle of operations 15 performed by the selected asset E1. As shown in fig. 8 and in more detail in fig. 9 and 10, for each cycle of operations 15 performed by the selected asset 160, the SOP cycle state display 13 is populated with a baseline cycle time indicator 29 and an actual cycle time indicator 31 for each operation OP1, OP2, OP3, and OP4 in the SOP 39A performed by the selected asset 160. For each operational cycle 15 performed by the selected asset 160 (e.g., by the S01 fixture in this example), the SOP cycle status display 13 is additionally populated with a baseline cycle time indicator 29 and an actual cycle time indicator 31 for the cumulative cycle time taken by the selected asset 160 to complete the SOP 39A. In this example, the parameter descriptor 166C is displayed as "cycle time" identifying the cycle display 13 shown in fig. 7 as the SOP cycle state display 13.

As shown in fig. 8-13, a respective baseline cycle time indicator 29 is displayed and associated with each respective actual cycle time indicator 31. A baseline cycle time indicator 29, shown in a non-limiting example as a horizontal blue bar, extends the duration of the baseline cycle time defining the operation OP and/or SOP 39, the baseline cycle time indicator 29 being associated with the OP and/or SOP 39 such that a difference in the horizontal lengths of the baseline cycle time indicator 29 and the actual cycle time indicator 31 provides a visual display of whether the actual cycle time is greater than, equal to, or less than the baseline cycle time for rapid visual identification of the deterioration and/or improvement in the actual cycle time relative to the baseline cycle time. The baseline cycle time indicator 29 ends with a vertical blue line that overlays the actual cycle time indicator 31 associated with the baseline cycle time indicator 29, providing an additional visual indicator to determine the change in actual cycle time from the baseline cycle time. In the examples shown in fig. 8-13, and in detail in the examples shown in fig. 9-12, each actual cycle time indicator 31 is a distinct data feature 142, a conditional state that is differentiated by color to indicate the cycle time of the respective operation OP and/or the respective SOP 39a associated with the respective actual cycle time indicator 31, as another rapidly visible indicator of the deterioration and/or improvement of the actual cycle time relative to the baseline cycle time. For example, referring to fig. 9, the green actual cycle time indicator 31 identifies an actual cycle time equal to the baseline cycle time (or within an acceptable range of variation); an orange actual cycle time indicator 31 identifies an actual cycle time that varies from the baseline cycle time by more than an acceptable time, where the variation may indicate an actual cycle time that is greater than or less than the baseline cycle, either condition potentially indicating a condition that requires attention; the red actual cycle time indicator 31 identifies the actual cycle time of the operation for which a fault has occurred. As shown in fig. 12, the user input 153 applied to the selected

cycle time indicator

29, 31 drives the SOP cycle state display 13 to display an information box 61, the information box 61 showing additional information related to the selected operation OP and the operation cycle. In this example, additional information such as the model identifier of the S01 fixture, the tray number associated with the S01 fixture, the actual cycle time visually represented by the selected actual cycle time indicator 31, and the design intent cycle time visually represented by the baseline cycle time indicator 29 associated with the selected actual cycle time indicator 31 are displayed for the information box 61 displayed for the selected operating cycle 15B of operation OP2 performed in the SOP 39A by the selected asset 160 (e.g., by the S01 fixture).

In the example shown in FIG. 7, in response to the user input 153 selecting the time period 157B, the fourth display template 137 corresponding to the conditional status message display 162 populates message tags associated with the observed conditional status for the selected asset 160 (e.g., E1, also described in the example as "S01 fixture"), including the conditional status tags of "failed," "blocked," and "default," where the display messages 163 associated with each of these are the distinguishing data features 142 of the conditional status message display 162. In the example shown in fig. 8-13, the "failure" message 163A is distinguished by being displayed in the rust display window, the "blocking" message 163B is distinguished by the blue display window, and the "default" message is distinguished by the gold display window. As shown in fig. 8-17, each message display window 163 extends across one or more cycles of operation 15 for which the messages shown in the display window 163 are valid. For example, the message displayed in fault message display window 163A may indicate "machine powered off," where message display window 163A is displayed over a plurality of operating cycles 15 affected by a loss of power to machines 16 including affected assets 160 (in this example, S01 fixtures).

In the examples shown in fig. 8-13, and in detail in the examples shown in fig. 9 and 10, the SOP loop state display 13 additionally displays a loop state indicator 19, indicated by a vertical line, for each operating loop 15 shown in the display 13, where each loop state indicator is a distinguishing data feature 142, distinguished in this example by a color code. For example, referring to the operational loop 15B shown in fig. 9 and 10, the default loop status indicator 19a is distinguished by a peach color corresponding to the state of the default condition (stationary condition), indicating that during execution of the operational loop 15B, the selected asset 160 (e.g., S01 fixture) is in the default state for the duration indicated by the default loop status indicator 19 a. In one example, the default condition state is referred to herein as a suspend (Sus/suspend) condition state, wherein in the default and/or suspend condition state, the selected asset 160 suspends or stops waiting for a precondition to be satisfied, wherein the precondition may be, for example, waiting for an entry section, waiting for completion of another operation of one or more of operations OP1, OP2, OP3, OP4 feeding the SOP 39A, or the like. In the example shown in fig. 9-10, the default condition status message 163C shown in the condition status message display 162 that extends partially through the cycle time of the operational cycle 15B may include a message explaining, for example, the reason for the default condition and/or corrective action taken to override the default condition. For example, referring to the operational loop 15B shown in fig. 9-10, the blocking loop status indicator 19B is distinguished by a light blue color corresponding to the blocking (Bl/Block) condition state, indicating that during execution of the operational loop 15B, the selected asset 160 (e.g., S01 fixture) is in the blocking condition state for the duration indicated by the blocking loop status indicator 19B. In one example, in the blocked condition state, the selected asset 160 is suspended or stopped to wait for completion of subsequent operations, where completion of subsequent operations is required as a prerequisite to completion of the blocked operation. In the example shown in fig. 9-10, the congestion condition status message 163B shown in the condition status message display 162 extending over the cycle time of the operating cycle 15B may include a message explaining the cause of the congestion condition, for example.

In the example shown in FIG. 9, the Fault cycle status indicator 19C is distinguished by a rose color corresponding to the Fault (Fault/Fau) condition status, indicating that the selected asset 160 is in the Fault condition status for the duration indicated by the Fault condition status indicator 19C.

In the example shown in fig. 8, the SOP loop state display 13 fills in loop data for each operational loop 15 executed in the selected time period 157B in real time. For purposes of illustration and description, the operational loop 15 executed in the selected time period 157B is identified in fig. 8-13 as including

operational loops

15A, 15B, 15C, 15d.. 15m, 15n +1.. 15n + x, executed in the order A, B, C, d.. m, n +1.. n + x during the selected time period 157B, and displayed in the SOP loop state display 13 in order from left to right (as shown on the page), as shown in fig. 8-13. Each of the operation cycles 15 is displayed relative to the clock time shown in the horizontal timeline displayed at the top of the SOP cycle state display 13 (as shown on the page) such that the clock time at which the respective operation cycle 15 is performed can be used to orient the respective operation cycle 15 in the selected time period 157B.

In the examples shown in fig. 8-13, various examples of user inputs 153 that may be input to the display screen 74 to modify the

circular displays

11, 13, 155 and/or the message display 162 that are simultaneously displayed in the display screen 74 are shown. For example, fig. 8-12 illustrate progressive enlargement of the SOP cycle state display 13, for example, by inputting one or more user inputs 153, such as an unfolding touch gesture or equivalent touchpad, mouse, or keyboard input, to horizontally unfold the displayed operational cycles 15 relative to each other. See, for example, the expanded appearance of the operational cycle 15n in fig. 10 compared to fig. 9, and the expanded appearance of the

operational cycles

15A and 15B in fig. 10 compared to fig. 9. In another example shown in fig. 16 and 17, one or more user inputs 153, such as a pinch gesture or equivalent touchpad, mouse, or keyboard input, may be input to the display screen 74 to gradually narrow the SOP loop state display 13, such as shown by the relatively contracted appearance

operational loop

15A, 15B, 15C, 15D in fig. 17 as compared to fig. 9-11.

In another example shown in fig. 10 and 11, one or more user inputs 153, such as a swipe gesture applied to the display screen 74 or an equivalent mouse, touchpad, or keyboard input 153 input to the user device U, may be used to horizontally translate the SOP loop state display 13 to the left and/or right (as shown on the page) to view the loop state information displayed for the adjacent operational loop 15. For example, the user input 153 applied to the SOP loop status display 13 pans the display 13 to the right (as shown on the page) to see additional details of the operational loop 15A. For example, user input 153 applied to SOP loop state display 13 pans display 13 to the left in fig. 11 (as shown on the page) as compared to fig. 10 to fully display the loop state information of operational loop 15C.

When the SOP loop state display 13 is dynamically transitioned and/or modified, for example, by zooming and/or panning the user input 153, the directional visual relationship between the loop displays 11, 13, 155 provided by a combination of the displayed time period 157 and the directional feature 161A identifying the time period 157A shown in the loop state display 155, the directional feature 161B of the text display identifying the time period 157B and the clock time of the time period 157A in the descriptor 166B shown in the heartbeat display 11, and the horizontal timeline of the clock time of the time period 157B shown in the SOP loop state display 13, while the orientation of each of the viewed loop displays 11, 13, 155 to the

other loop display

11, 13, 155 is maintained.

The examples shown in fig. 10-11 of inputting user input 153 to zoom, pan, collapse, expand, and/or otherwise manipulate and/or modify SOP loop state display 13 are non-limiting and illustrate methods of manipulating and/or modifying other automated data displays 138, including, for example, one or more of loop displays 11, 13, 155 and/or message displays 162 described herein, and/or data displays generated by populating display template 137 with data collected via AOS 10.

Referring now to fig. 13 and 14, in the example shown in fig. 13, user input 153 is input to a drop-down icon, also referred to herein as an expand/contract icon, associated with operation OP1 in displaying SOP 39A to drive the SOP loop state display 13 to expand operation OP1 to display a sub-operation Sequence (SOP) 39B. In the example shown in FIG. 13, sub-SOP 39B includes operations OP1.1, OP1.2, OP1.3, OP1.4 performed in the order defined by sub-SOP 39B to complete the execution of operation OP1. Thus, the performance of operations OP1.1, OP1.2, OP1.3, OP1.4 and the corresponding cycle times determine the performance and cycle times of operation OP1, enabling the SOP cycle state display 13 to be driven with user input 153 to immediately view and analyze operations OP1.1, OP1.2, OP1.3, OP1.4 when analyzing operation OP1 is an advantage of the AOS 10 system described herein. In response to the user input 153, and as shown in FIG. 13, the SOP cycle state display 13 expands vertically and displays the baseline cycle time indicator 29 and the actual cycle time indicator 31 for each of the operations OP1.1, OP1.2, OP1.3, OP1.4 of the sub-SOP 39B performed by the selected asset 160, e.g., by the S01 fixture in this example. In the example shown in fig. 13, the user input 153 applied to the cycle time indicator 31 corresponding to the operation OP3 drives the SOP cycle state display 13 to display an information box 61, the information box 61 showing additional information related to the selected operation OP3 and the operation cycle 15B.

In the example shown in fig. 13 and 14, various user inputs 153 are input to the display screen 74 to modify how one or more of the

circular displays

11, 13, and 155 are displayed in the display screen 74. In the example shown in fig. 14, the user input 153A is input to a "collapse" icon associated with the looping status display 155, driving the display screen 74 and/or the user device U to collapse the looping status display 155 such that only the display descriptor 166A remains displayed on the display screen 74 as a visual indicator for the user/viewer to drive the looping status display 155 in the display screen 74. As shown in FIG. 14, when the loop state display 155 is collapsed, the displayed SOP loop state 13 automatically expands vertically (as viewed on the page) in the display screen 74 to fill the screen space available through the collapse of the loop state display 155. A subsequent user input 153 to the "switch view" icon adjacent to the "collapse" icon may be entered to expand the looping state display 155 so that the display 155 is again visible in the display screen 74. Thus, the method provides flexibility for instantly folding and unfolding varying display screens 11, 13, 155, 162 to facilitate quick viewing of automated data displayed by each of these

displays

11, 13, 155, 162 without having to switch or transition between multiple screens. Further, selective collapsing of one or more of the plurality of

displays

11, 13, 155, 162, etc. simultaneously displayed in the display screen 74 provides the user with the option of selecting an expanded view of one or more of the

displays

11, 13, 155, 162, among others. For example, the folding SOP cycle state display 13 automatically folds the overlaid conditional state message display 162, automatically unfolds the remaining cycle state display 155 and heartbeat display 11 into the screen space vacated by the folding SOP cycle state display 13 such that as the SOP cycle state display 13 folds, the display screen 74 appears as shown in fig. 6.

In another example shown in fig. 14, the user input 153B is input to the expand/contract icon in the display SOP 39A associated with the operation OP1 to drive the SOP cycle state display 13 to contract the display of the sub-SOP 39B so that the sub-SOP 39B and the

cycle time indicators

29, 31 associated with the operations OP1.1, OP1.2, OP1.3, OP1.4 are no longer displayed by the SOP cycle state display 13, and the

cycle time indicators

29, 31 associated with the operations OP1, OP2, OP3, OP4 of the SOP 39A are vertically expanded in the space vacated by the sub-SOP 39B. Thus, the method provides flexibility for the immediate folding and unfolding of the changing sub-SOPs 39 of one or more of the operations OP1, OP2, OP3, OP4 to facilitate rapid viewing of automated data displayed by each of these sub-SOPs 39 without having to switch or transition between multiple screens.

In another example shown in fig. 14-16, a user input 153C is input to a display menu icon 164 as shown in fig. 14 to drive the display screen 74 as shown in fig. 15 while opening the display menu 164 and to drive a transparent (see-through) window on the

cycle display

11, 13, 155 while the display menu 164 is open. In the example shown in FIG. 15, user input 153 is entered into display menu 164 to display a drop down list of items included in the display. In the example shown in FIG. 15, the "loop," "status," and "baseline" items are selected. As shown in fig. 15, the user input 153 is entered into a selection box associated with "simulation" to drive the display screen 74, as also shown in fig. 15, to display another automated data display 138, identified as simulation display 165, on the display screen 74. The simulation display 165 displays a parameter descriptor 166D that describes the simulation parameters to be displayed, such as "hydraulic pressure", "oil pressure", "temperature", and the like. As shown in fig. 16, the simulation display 165 is populated with simulation data 167 for selected simulation parameters 166D, where the simulation data 167 is displayed in real-time with a horizontal timeline 157B shown in the SOP cycle state display 13, such that the simulation data 167 can be visually associated in real-time with the cycle state indicators 31 shown in the SOP cycle state display 13 for the various operational cycles 15, and such that the horizontal timeline 157B orients the simulation display 165 with respect to the SOP cycle state display 13. As shown in fig. 15-17, the display screen 74 simultaneously displays the heartbeat display 11, SOP loop status display 13, condition status message display 162, simulation display 165, and loop status display 155 (shown in a collapsed view), enabling the user/view to manipulate the various data displays 11, 13, 155, 162, 165 through one or more user inputs 153 input to the display screen 74 to view, compare, and analyze automated data from multiple operational loops 15 and multiple operations OP from various Operational Sequences (SOPs) 39 including sub-SOPs.

In the example shown in fig. 16-17, one or more user inputs 153 are input to the display screen 74 and/or to the user device U to manipulate the

data display

13, 165. In one example, the simulated display 165 is associated with the SOP loop status display 13 via the horizontal timeline 157B such that the user input 153 zooms and/or pans one of the

displays

165, 13, automatically zooms and/or pans the other of the

displays

165, 13, the overlay condition status message display 162, and the horizontal timeline 157B, such that during the input of the zoom and/or pan user input 153 to either of the

displays

13, 165, as shown during progressive zooming out of the data displays 13, 165 shown in fig. 16 and 17, the

displays

162, 165, 13, and the horizontal timeline 157B are dynamically and automatically reoriented to each other and to the actual timeline display 33. The ability to zoom out to show an increasing number of operational cycles 15 in the display screen 74, as shown in fig. 16-17, provides the advantage of being able to visually observe the variability in the simulated data 167, which is not perceptible when viewing only one or a few operational cycles 15, as shown in fig. 16.

Referring now to fig. 18-26, a method of simultaneously displaying automation data from multiple assets 151 is shown and described herein. Fig. 18 shows an asset tree 152 as previously described herein with respect to fig. 2. In the example shown in FIG. 18, user input 153 is entered into a checkbox corresponding to element E1, which automatically populates a checkbox for advanced asset 151 including element E1, and user input into a checkbox corresponding to element E2, causing two assets 151 of station ST1 to be selected for display in display screen 74, with a first selected asset 160A (element E1) identified in this example as "S01 fixture" and a second selected asset 160B (element E2) identified in this example as "R01". In this example, as shown in FIG. 3 and previously described with respect to FIG. 3, the display screen 74 generates and displays a cycle status display 155 of a first selected asset 160A selected in FIG. 18, in this example, the first selected asset 160A being element E1 as previously described herein in relation to FIG. 2, in response to the user input 153 selecting assets E1 and E2. The loop status display 155 is displayed relative to the actual timeline display 33 showing the clock time 37 corresponding to each loop status bar 158. As shown in fig. 2 and 3 and as previously described herein, the user input 153 is input to the display screen 74 to select the cycle status bar 158A and the time period 157A, for example, by a touch input such as a drag or double-click, or by scrolling over the cycle status bar 157A to select the cycle status bar 158A and the time period 157A. As shown in FIG. 4, selection of the cycle status bar 158A drives the screen display 74 to generate additional second and third automated data displays 138 for the time period 157A shown in FIG. 19, which are displayed simultaneously with the currently displayed cycle status display 155. In the example shown in fig. 19-20, the second data display 138 is configured as an SOP cycle status display 13A generated for a first selected asset 160A (element E1, "S01 fixture" in this example), and the third data display 138 is configured as an SOP cycle status display 13B generated for a second selected asset 160B (element E2 in this example, identified as "R01" in the asset tree 152).

In the example shown in fig. 19-20, each of the first and second SOP cycle state displays 13A, 13B is displayed simultaneously with the cycle state display 155. In the example shown in fig. 19-20, the time period 157A displayed in the cycle status display 155 is oriented to each of the first and second SOP cycle status displays 13A, 13B by the orientation feature 161A such that which time period of the operating cycle 15 is instantaneously visible is displayed in the SOP cycle status displays 13A, 13B. In addition, the actual clock time 37 within the time period 157A is indicated in the horizontal timeline display 33 along the top of the SOP cycle state display 13A (as viewed on the page) to direct the displayed operational cycle 15 to the selected time period 157A.

In the example shown in fig. 19-20, the SOP cycle state display 13A displays an actual cycle time indicator 31 and a baseline cycle time indicator 29 for each operational cycle 15 executed by the selected element 160A and displayed on the display screen 74, with the

cycle time indicators

29, 31 indicating the cycle time of the operational Sequence (SOP)39A (see fig. 24) executed by the selected asset 160A, for example, executed by the first element E1. The SOP cycle state display 13B displays the actual cycle time indicator 31 and the baseline cycle time indicator 29 of each operational cycle 15 performed by the selected element 160B and displayed on the display screen 74, with the

cycle time indicators

29, 31 indicating the cycle time of an operation OP of the Sequence of Operations (SOP)39 performed by the selected asset 160B, such as the operation OP performed by the second element E2. In the example shown in fig. 19-20, one or more pan user inputs 153, such as swipe gestures, may be input to the display screen 74 to pan the SOP

cycle status display

13A, 13B left and/or right (as shown on the page) to view and/or analyze various operational cycles 15 of the selected

assets

160A, 160B displayed on the display screen 74. The SOP cycle state displays 13A, 13B are synchronized such that a pan user input 153 to one of the

displays

13A, 13B drives the display screen 74 while panning the cycle state displays 13A, 13B and the timeline display 33 such that the operational cycle 15 displayed by each of the

displays

13A, 13B remains aligned with the horizontal timeline 33 showing the actual clock time 37 at which each operational cycle 15 was executed within the time period 157A. Advantageously, by displaying the SOP cycle status displays 13A, 13B of multiple selected

assets

160A, 160B, a user/view may visually analyze the operational performance of multiple assets 151 within the same display screen 74 without having to transition between multiple displays or display windows. Further, the multiple asset displays shown in fig. 19-26 are advantageous in that the operational loop 15 performed by each of the multiple selected

assets

160A, 160B directed to the selected time period 157A and the actual timeline display 33 is shown such that the relative performance of the

assets

160A, 160B at the same actual time 37 is visually assessed and/or the performance of the

assets

160A, 160B relative to each other over the selected time period 157A is visually assessed, the latter being advantageous, for example, when one of the selected

assets

160A, 160B is performing one or more operations OP, the operation OP being a previous one or more operations OP of an operation performed by the other of the selected assets 160A in analyzing blocking and default conditions, e.g., feeding an operation to an operation OP performed by the other of the selected assets 160A.

In the example shown in fig. 20-21, the user input 153 is input to a "fold" icon associated with the loop status display 155, such that the display screen 74, in response to the user input 153 and as shown in fig. 20 and 21, immediately folds the loop status display 155, displaying a descriptor 166A as a visual indicator that the display 155 can expand for viewing by the user input to a "switch view" icon adjacent to the "fold" icon, after folding the display 155. Concurrently with the collapsing of the loop status display 155, as shown in FIG. 21, the SOP loop status displays 13A, 13B are immediately deployed into the screen space vacated by the collapsed display 155 such that the

displays

13A, 13B are enlarged for user/view viewing of the display screen 74.

Referring to fig. 22-23, additional examples of methods for manipulating multiple asset displays are shown, including inputting one or more user inputs 153 to the display screen 74 to zoom the SOP

loop state display

13A, 13B, for example, by inputting user inputs 153, such as an expand gesture for zooming in and/or a pinch gesture for zooming out. As described previously herein with respect to the pan user input 153, the zoom user input 153 input to one of the

displays

13A, 13B will drive simultaneous zooming of both the SOP cycle state displays 13A, 13B and the timeline display 33 such that the operational cycles 15 displayed in each of the

displays

13A, 13B remain oriented to the horizontal timeline 33 and the actual clock time 37 associated with each operational cycle 15 and to each other in real time. As shown in fig. 23, the user input 153 to the actual cycle time indicator 31 drives the cycle display 13A in the example shown to display the information box 61 simultaneously with the cycle displays 13A, 13B to provide additional detailed information associated with the selected actual cycle time indicator 31.

In the example shown in fig. 23-24, user input 153 to the expand/contract icon associated with the selected element 160 (in this example, selected element 160A) drives SOP loop display 13A to expand to display the Sequence of Operations (SOP)39A performed by the selected element 160 (in this example, "S01 fixture"). In this example, the operations OP1, OP2, OP3, OP4 of the SOP 39A are displayed, along with the actual and

baseline cycle indicators

29, 31 for each of the operations OP1, OP2, OP3, OP4, to provide additional visual information for analyzing the cycle of operations 15 performed by the selected asset 160A. In the example shown in fig. 23-24, when the SOP loop state display 13A is expanded to display the SOP 39A, the SOP loop state display 13B is simultaneously collapsed such that the modification and transition of the displayed automation data is seamless without any loss of data visibility to the user/viewer and without having to switch or change the display screen between display windows.

As shown in fig. 24-25, user input 153 into the expand/contract icon in the display associated with operation OP1 facilitates expansion of the SOP loop state display 13A to display the sub-SOP 39B, including operations OP1.1, OP1.2, OP1.3, OP1.4 and their associated actual and

baseline loop indicators

29, 31. In the example shown in FIG. 25, the user input 153 input to the actual cycle time indicator 31 associated with the first selected asset 160A drives the cycle display 13A in the example shown to display the information box 61 simultaneously with the cycle displays 13A, 13B to provide additional detailed information associated with the selected asset 160A and the selected actual cycle time indicator 31.

The examples shown in fig. 24-25 are non-limiting and illustrative. For example, additional user inputs 153 may be input to the display screen 74 shown in fig. 23-25 to expand the Sequence of Operations (SOP) performed by the second selected asset 160B, and/or to expand another operation, such as OP2 or OP1.3 by way of illustrative example, to display additional detailed automation data to the display screen 74. The user/viewer may selectively expand and/or collapse the sequence of operations 39 performed by each of the selected

assets

160A, 160B to dynamically view and/or analyze the operational performance of the displayed plurality of assets via a plurality of user inputs 153 to the display screen 74. In one example, a user may select additional assets 151 from the asset tree 152 for display concurrently with the displayed

assets

160A, 160B, and/or may deselect one or more of the previously selected

assets

160A, 160B and select one or more assets 151 from the asset tree 152, such that the display of automated data from the plurality of assets 151 may be dynamically manipulated by the user input 153 to the display screen 74.

In the example shown in FIG. 26, the additional displays may be driven by user inputs 153, as shown in the example including a legend 77, which legend 77 may be displayed in response to user inputs 153 to legend icons 156 to assist the user/view in interpreting the distinguishing data features 142 displayed in the various displays 138. In this example, the legend 77 is encoded by color, shading, or other distinguishing features to help explain the various color codes and/or shading patterns of the other distinguishing features displayed by the distinguishing data features 142 shown in the example data displays 11, 13, 155, 162, 165 described herein.

The examples shown in fig. 18-26 are exemplary and non-limiting, such that the multi-asset display shown in fig. 18-26 is not limited to a display of two selected

assets

160A, 160B. For example, a plurality of selected assets 160a … 160n, including three or more assets 151, may be selected from the asset tree 152 for simultaneous display of at least one automated data display 138 associated with each of the selected assets 160a.. 160n, where the term "associated" as used in the context herein indicates that the automated data display 138 associated with the selected asset 160x is generated using automated data collected from and/or defined by the selected asset 160 x. For example, the automated data display 138 displayed for each of the plurality of selected assets 160A … 160n may be a respective heartbeat cycle display 11 associated with each of the respective selected assets 160A … 160 n.

Referring to fig. 30, an exemplary method 200 for generating the automated data display 138 and for dynamically modifying the automated data display 138 displayed on the display screen 74 in response to user input 153 received by the user interface 74 is illustrated, as shown in fig. 1-26. At 205, the initial automation data display 138 is generated, displaying the selection menu 150 including the icons 154 for selecting the object tree 152, the dashboard, the cycle displays 11, 13, 155, the messages 162, and the like. At 210, user input is entered into the selected menu icon 154, such as the object tree icon 154A, and the asset tree display 152 is generated and displayed on the user interface 74. Additional user inputs 153 are input at 210, for example, asset tree 152 is expanded to show various levels of assets 151 and/or to select one or more assets 151. At 215, in response to the user input 153 selecting one or more assets, the automated system generates and displays, in real-time, at least one

cycle display

11, 13, 115 corresponding to each of the selected assets, and displays a plurality of operational cycles of a Sequence of Operations (SOP) performed by each of the selected assets. The method continues at 220, where the automated operating system receives additional user input 153 to the user interface 74 and modifies the data display 138 in response to the user input 153. As shown in FIG. 30, in response to user input 153 entered into the user interface 74, the method 200 may continue by returning to one or more of 210, 215, 220 so that dynamic operation and modification of the automated data display 138 may occur continuously to provide relevant data to the user in real-time for monitoring and diagnosing automated operations in real-time and to expedite identification and performance of corrective, refining and preventative actions related to the automated operations.

Other configurations of multiple asset displays are included within the scope of the present disclosure. For example, multiple asset displays, such as those of fig. 2-4 and 19-26, may be generated for multiple system SY1 … SYn selected, for example, from the asset tree 152 of the facility 14 and/or enterprise 12, where the system SY may each generate simulation parameter data, such that the methods disclosed herein may be used to simultaneously display respective simulation parameter data for each of the multiple selected system SY1 … SYn. In one example, a method of simultaneously displaying automation from a plurality of selected assets includes selecting assets 151 from different levels of the asset tree 152 and/or from asset trees 152 of different facilities 14 to compare operational behavior of assets 151 from a first facility 14 to operational behavior of substantially similar assets 151 operating in a second facility 14.

The illustrative examples provided by the figures are non-limiting and it should be understood that display template 137, shown herein as data-populating automated data display 138, is only representative of a portion of display template 137 and automated data display 138 that may be generated by the systems described herein and/or using data of AOS 10. For example, as shown in the display menu 150 of the figure, an automated data display 138 configured as a dashboard may be selected and displayed via the display screen 74 simultaneously with another automated data display 138 described herein.

The detailed description and drawings or figures are supportive and descriptive of the invention, but the scope of the invention is defined only by the claims. While some of the best modes and other embodiments for carrying out the invention have been described in detail, there are various alternative designs and embodiments for practicing the invention defined in the appended claims.

Claims

1. A method for displaying automation data of an automation system via an automation data display, the method comprising:

displaying an asset tree display on a user interface of a user device;

the asset tree display displays a plurality of assets;

each asset of the plurality of assets is drivable to perform at least one operation of an ordered Sequence of Operations (SOP) of a plurality of cycles of operations;

receiving, by an automated system comprising at least one processor, a first user input to the user interface, the first user input indicating a selection of a first asset of the plurality of assets;

generating, via the automation system and in real-time, a first cyclical display of the first asset performing the at least one operation of a plurality of cycles of operations;

wherein the first cycle display is selected from the group consisting of:

displaying a circulation state;

displaying the heartbeat cycle state; and

operation Sequence (SOP) cycle display;

displaying the first cycle display and a timeline display via the user interface; and

the timeline display displays an actual time associated with the first asset performing the at least one operation of each of the plurality of operational cycles displayed via the first cycle.

2. The method of claim 1, further comprising:

generating, via the automation system, an actual cycle time for each of the plurality of operational cycles performed by the first asset;

determining, via the automation system, a condition status of each of the plurality of operational cycles performed by the first asset; and

displaying, via the first loop display, an indication of the actual loop time and an indication of the condition status for each of the plurality of operational loops performed by the first asset.

3. The method of claim 2, wherein:

the first cycle display is the cycle status display;

the indication of the actual cycle time is a cycle status bar displayed as an accumulated status of actual cycle times determined for cycles of operation performed in a time period displayed by the display timeline; and

determining the indication of the condition status by a comparison of an actual cycle time of the operating cycle to a baseline cycle time.

4. The method of claim 2, wherein:

the first cycle display is the heartbeat cycle status display;

the indication of the actual cycle time is a heartbeat cycle bar that displays an actual cycle time determined for each cycle of operation performed by the first asset in a time period displayed by the display timeline; and

determining the indication of the condition status by a comparison of the actual cycle time of the operating cycle to a baseline cycle time.

5. The method of claim 2, wherein:

the first cycle display is an SOP cycle status display;

the indication of the actual cycle time is an actual cycle indicator for the at least one operation;

the method further comprises the following steps:

displaying, via the user interface, the at least one operation performed by the first asset;

displaying, for each cycle of operation of the at least one operation performed by the first asset, an actual cycle indicator of the at least one operation within a time period displayed by the display timeline, wherein the actual cycle indicator is displayed relative to an actual time that the cycle of operation was performed by the first asset;

for each operational cycle of the at least one operation performed by the first asset, displaying a baseline cycle indicator for the at least one operation, wherein the baseline cycle indicator is displayed relative to the actual cycle indicator.

6. The method of claim 5, wherein the indication of the condition status comprises a first condition status indication and a second condition status indication;

wherein the first condition status indication is a cycle time condition indicated by displaying the baseline cycle indicator relative to the actual cycle indicator;

wherein the second condition status indication is an operating state condition indicated by displaying the actual cycle indicator, the actual cycle indicator including a condition status specifier corresponding to the operating state condition;

the method further comprises the following steps:

determining, via the automation system, a second conditional state for each operational cycle of the at least one operation performed by the first asset;

wherein the second conditional state is one of an acceptable, blocked, default or fault condition state; and

displaying the actual cycle indicator, the actual cycle indicator including the condition state specifier corresponding to the second condition state.

7. The method of claim 1, further comprising:

receiving, by the automation system, a second user input to the user interface;

modifying the first cyclical display in response to the second user input;

wherein modifying the first rotation display comprises scaling the first rotation display or panning the first rotation display;

wherein scaling the first rotating display drives the first rotating display and the timeline display to scale simultaneously; and

wherein translating the first cycle display drives the first cycle display and the timeline display to translate simultaneously.

8. The method of claim 2, further comprising:

receiving, by the automated system, a second user input to the first cycle displayed data feature;

displaying an information window in response to the second user input;

wherein the information window displays information defined by the data feature; and

wherein the data characteristic is one of the indication of the actual cycle time or the indication of the condition status.

9. The method of claim 1, further comprising:

receiving, by the automated system, a second user input to the first loop display;

selecting, via the second user input, a first time period displayed by the first cyclical display;

generating a second cyclical display in response to the second user input;

displaying, via the user interface, the second cyclical display over the first time period;

wherein the second cycle display is selected from the group consisting of:

displaying a circulation state;

displaying the heartbeat cycle state; and

operation Sequence (SOP) cycle display;

the timeline display displays the actual time associated with the first asset performing the at least one operation of each of the plurality of operational cycles displayed via the second cycle; and

wherein the second cycle display, the first cycle display, and the timeline display are displayed simultaneously on the user interface.

10. The method of claim 1, wherein:

the first cycle display is the cycle status display; and

the second cycle display is the heartbeat cycle status display.

11. The method of claim 1, further comprising:

displaying a first director in the first recurring display, wherein the first director identifies the first time period in the first recurring display.

12. The method of claim 9, further comprising:

displaying a display menu on the user interface;

receiving, by the automation system, a third user input to the displayed menu;

selecting, via the third user input, a simulation parameter associated with the sequence of operations;

generating a simulation parameter display in response to the third user input;

wherein the simulation parameter display displays simulation data of the selected simulation parameter in real-time, wherein the timeline display displays the actual times associated with the plurality of cycles of operation displayed via a second cycle display;

displaying the simulated parameter display via the user interface for the first period of time; and

wherein the simulation parameter display, the second cycle display, the first cycle display, and the timeline display are simultaneously displayed on the user interface.

13. The method of claim 9, further comprising:

receiving, by the automated system, a third user input to the second loop display;

selecting, via the third user input, a second time period displayed by the first cyclical display;

generating a third cyclical display in response to the second user input;

displaying, via the user interface, the third cyclical display over the second time period;

wherein the third loop display is selected from the group consisting of:

displaying a circulation state;

displaying the heartbeat cycle state; and

operation Sequence (SOP) cycle display;

the timeline display displays the actual time associated with the first asset performing at least one operation of each of the plurality of operational cycles displayed via the third cycle; and

wherein the third circular display, the second circular display, the first circular display, and the timeline display are displayed simultaneously on the user interface.

14. The method of claim 13, wherein:

the first cycle display is the cycle status display;

the second cycle display is the heartbeat cycle status display; and

the third cycle display is the SOP cycle status display.

15. The method of claim 13, further comprising:

displaying a second director in the second cyclical display, wherein the second director identifies the second time period in the second cyclical display.

16. The method of claim 13, further comprising:

receiving, by the automation system, a fourth user input to the user interface;

modifying the third cyclical display in response to the fourth user input;

wherein modifying the fourth rotation display comprises zooming the third rotation display or panning the third rotation display;

wherein scaling the third rotation display drives the third rotation display and the timeline display to scale simultaneously; and

wherein translating the third cyclical display drives the third cyclical display and the timeline display to translate simultaneously.

17. The method of claim 1, further comprising:

receiving, by an automation system including at least one processor, a second user input to the user interface, the second user input indicating a selection of a second asset of the plurality of assets;

wherein the at least operation performed by the first asset is at least a first operation of the Sequence of Operations (SOP);

wherein the second asset is drivable to perform at least a second operation of the Sequence of Operations (SOP) of the plurality of cycles of operations;

generating, via the automation system and in real-time, a second loop display of the second asset performing the at least one operation of the plurality of cycles of operations;

wherein the second cycle display is selected from the group consisting of:

displaying a circulation state;

displaying the heartbeat cycle state; and

operation Sequence (SOP) cycle display;

displaying the second cycle display and the timeline display via the user interface; and

the timeline display displays an actual time associated with the second asset performing the at least second operation of each of the plurality of operational cycles displayed via the second cycle; and

wherein the second cycle display, the first cycle display, and the timeline display are displayed on the user interface simultaneously.

18. The method of claim 17, further comprising:

generating, via the automation system, an actual cycle time for each of the plurality of operational cycles performed by the second asset;

determining, via the automation system, a condition status of each of the plurality of operational cycles performed by the second asset; and

displaying, via the second loop display, an indication of the actual loop time and an indication of the condition status for each of the plurality of operational loops performed by the second asset.

19. The method of claim 17, wherein:

the first cycle display is the cycle status display of the first asset; and

the second cycle display is the cycle status display for the second asset.

20. A system for displaying automation data of an automation system via an automation data display, the system comprising:

an automation system, comprising:

a plurality of assets;

a server configured to collect automation data from the plurality of assets and store the automation data in a memory in communication with the server;

the memory having stored thereon the sequence of operations, an asset tree identifying the plurality of assets, a plurality of automation data templates, and computer-executable instructions configured to generate a plurality of automation data displays and output the plurality of automation data displays and automation data in response to accepting user input from a user device;

the user device includes a user interface actuatable to display automation data including the plurality of automation data displays;

the automation system is drivable to:

displaying an asset tree display on the user interface of the user device;

the asset tree display displays the plurality of assets;

receiving a first user input to the user interface, the first user input indicating a selection of a first asset of the plurality of assets;

generating, in real-time, a first cyclical display of the first asset performing the at least one operation of a plurality of cycles of operations;

wherein the first loop display is selected from the group consisting of:

displaying a circulation state;

displaying the heartbeat cycle state; and

operation Sequence (SOP) cycle display;

wherein the timeline display displays an actual time associated with the first asset performing the at least one operation of each of the plurality of operational cycles displayed via the first cycle.

21. The system of claim 20, further configured to:

22. The system of claim 21, wherein:

the first cycle display is the cycle status display;

23. The system of claim 21, wherein:

the first cycle display is the heartbeat cycle status display;

24. The system of claim 21, wherein:

the first cycle display is an SOP cycle status display;

the system is further configured to:

25. The system of claim 24, wherein the indication of the condition status comprises a first condition status indication and a second condition status indication;

the system is further configured to:

26. The system of claim 20, further configured to:

receiving, by the automation system, a second user input to the user interface;

modifying the first cyclical display in response to the second user input;

27. The system of claim 21, further configured to:

displaying an information window in response to the second user input;

28. The system of claim 20, further configured to:

generating a second cyclical display in response to the second user input;

displaying the second cyclical display via the user interface for the first period of time;

wherein the second cycle display is selected from the group consisting of:

displaying a circulation state;

displaying the heartbeat cycle state; and

operation Sequence (SOP) cycle display;

29. The system of claim 20, wherein:

the first cycle display is the cycle status display; and

the second cycle display is the heartbeat cycle status display.

30. The system of claim 20, further comprising:

31. The system of claim 28, further configured to:

displaying a display menu on the user interface;

receiving, by the automation system, a third user input to the displayed menu;

generating a simulation parameter display in response to the third user input;

32. The system of claim 28, further configured to:

generating a third cyclical display in response to the second user input;

wherein the third cycle display is selected from the group consisting of:

displaying a circulation state;

displaying the heartbeat cycle state; and

operation Sequence (SOP) cycle display;

wherein the third cycle display, the second cycle display, the first cycle display, and the timeline display are simultaneously displayed on the user interface.

33. The system of claim 32, wherein:

the first cycle display is the cycle status display;

the second cycle display is the heartbeat cycle status display; and

the third cycle display is the SOP cycle status display.

34. The system of claim 32, further configured to display a second orienter in the second cyclical display, wherein the second orienter identifies the second time period in the second cyclical display.

35. The system of claim 32, further configured to:

receiving, by the automation system, a fourth user input to the user interface;

modifying the third cyclical display in response to the fourth user input;

36. The system of claim 20, further configured to:

wherein the second cycle display is selected from the group consisting of:

displaying a circulation state;

displaying the heartbeat cycle state; and

operation Sequence (SOP) cycle display;

37. The system of claim 36, further configured to:

38. The system of claim 36, wherein:

the first cycle display is the cycle status display of the first asset; and

the second cycle display is the cycle status display of the second asset.