Provided herein are systems, methods, and software for preserving timestamp data in an industrial automation environment. In one implementation, one or more computer-readable storage media having program instructions stored thereon to preserve timestamp data in an industrial automation environment, wherein the program instructions, when executed by a computing system, direct the computing system to at least receive, at a controller, event data of an event from an electronic device, wherein the event data comprises a status of the event and the timestamp of the event. The program instructions also direct the computing system to determine an identification value based on the event data and load the status of the event, the timestamp of the event, and the identification value to a queue within the controller. The timestamp of the event includes the timestamp transmitted from the electronic device.

An industrial data presentation system leverages structured data types defined on industrial devices to generate and deliver meaningful presentations of industrial data. Industrial devices are configured to support structured data types referred to as basic information data types (BIDTs) comprising a finite set of structured information data types, including a rate data type, a state data type, an odometer data type, and an event data type. The BIDTs are discoverable by a gateway device on which models of industrial assets can be defined, where the models reference the BIDTs defined on the industrial devices. The gateway device can retrieve industrial data from the data tags, formatted in accordance with the data types and associated user-defined metadata specific to the respective data types. The gateway device or a separate application server system can then generate graphical presentations of the industrial data in accordance with the model and the metadata.

Tracing forged parts over their production process includes: capturing process parameters of a forging process; marking a workpiece with a first identifier; storing the captured process parameters and the first identifier in a database; reading the identifier from the workpiece produced in the previous process step; capturing process parameters during subsequent process steps; storing the process parameters of the subsequent process steps in the database for the read identifier, if legibility of the first identifier of the workpiece remains during the subsequent process step; marking the workpiece produced in the subsequent process step with a further identifier, if legibility of the first identifier of the workpiece does not remain during the subsequent process step of the production process; and storing the process parameters of the subsequent process step together with the further identifier and process parameters of the previous process steps and the first identifier in the database.

A data processing apparatus is deployed at a cloud network, and includes a plurality of data nodes, a receiver circuit, and an aggregation circuit. The receiver circuit is coupled to the plurality of data nodes and is configured to receive downtime records from a plurality of industrial machines, and to selectively route the downtime records to selected ones of the plurality of data nodes based upon a predetermined criteria. Each of the plurality of data nodes comprises a control circuit and a memory. Each control circuit is configured to, in parallel with the other control circuits, to further populate the downtime records with other data related to the operation of the machines, determine one or more time windows for each of the records, and divide the records according to the time windows.

Provided is an information collection system reducing a computer load and a network load. An information collection system 1 includes a data stock device 1b and an event information creating device 1a connected via a network N. The data stock device 1b includes a management area 11 storing data flowing through the network N in a prescribed memory area according to the types of the data, and a change monitoring unit 16 monitoring a data change in the prescribed memory area of the management area 11. When the change monitoring unit 16 detects the data change, a plurality of data stored in the prescribed memory area 11 are collected, and transmitted to the event information creating device 1a. The event information creating device 1a collects the plurality of data received from the data stock device 1b as a series of data set, and creates event information 400.

Operational historian system retrieving summary data values and source data values based on alignment between a summarization cycle duration and a query cycle duration. A retrieval service process executing on a historian device utilizes a summarization cycle duration, including start and/or end times thereof, and a query cycle duration, including start and/or end times thereof, to determine whether to retrieve, via a communications network, source tag data and/or summary tag data from memory storage devices.

An illustrative example system for monitoring a plurality of events in a manufacturing facility includes a plurality of monitoring devices. Each of the monitoring devices obtains data regarding a selected one of the events. A reporting device receives the data obtained by the monitoring devices and provides a report regarding the monitored events. The report includes information regarding at least one characteristic of each of the monitored events. The information in the report is dynamically updated to provide a real time indication of the characteristics of the monitored events. The real time indications are presented in respective cells of the report.

A method includes receiving notifications associated with batch execution instances executed by multiple devices. The notifications identify events occurring in an industrial process control and automation system. The method also includes creating a unique namespace for association with the notifications. The method further includes storing records identifying the notifications in a unified activity hierarchy based on the unique namespace. Creating the unique namespace could include creating an initial namespace using one or more fields associated with a parent process being executed. The parent process can activate a child process, and a namespace for the child process can contain the initial namespace and use one or more fields associated with the child process. The child process can activate a grand-child process, and a namespace for the grand-child process can contain the initial namespace and the namespace for the child process and use one or more fields associated with the grand-child process.

A trace assistance device includes a memory section, an acquisition section, and an output section. The memory section stores a manipulation log and an operation log. When a predetermined trigger event occurs during the board work, the acquisition section acquires at least one target manipulation history related to the trigger event, a target operation history associated with the target manipulation history, a comparison manipulation history that is the same as or similar to the target manipulation history, and a comparison operation history associated with the comparison manipulation history from the manipulation log and the operation log stored in the memory device. The output section is configured to output an operation of the board production line recorded in the target operation history and an operation of the board production line recorded in the comparison operation history, which are acquired by the acquisition section, in a comparable manner.

A computer-implemented method (500) for monitoring a food processing system (100), arranged to produce a food product (102), using a data processing apparatus (112) is provided. The method comprises receiving (502) process traceability data (200) related to the food product (102), wherein the process traceability data (200) comprises information about which food processing units (104a-e) that were involved in processing the food product (102) as well as during which time slots the food processing units were involved for processing the food product (102), receiving (504) process event data (202) related to the food processing units of the food production system (100), wherein the process event data (202) comprises information about state changes of the food production units that occurred during processing of the food product (102) as well as points of time when the state changes occurred, receiving (506) settings (204) of the processing units (104a-e) associated with different states, determining (508) the settings used for the food production units (104a-e) during different time slots by combining the process event data (202) and the settings of the processing units (204) associated with the different states, and determining (510) the settings of the food production units (104a-e) used for processing the food product (102) by combining the process traceability data (200) and the settings used for the food production units during the different time slots, and providing (512) the settings of the food production units (104a-e) used for processing the food product (102).