Siemens Aktiengesellschaft

Siemens Industry, Inc.

Siemens Mobility Gmbh

Siemens Corporation

Florian Ersch

Hartmut Ludwig

Thomas Gruenewald

Lingyun Wang

George Lo

Pornsak Songkakul

Raphael Imhof

Thomas Rule

Michael J Marchi

Paula Hiller

Michael Jaentsch

Yunhua Fu

Heinrich Helmut Degen

Yunsheng Zhou

Andreas Kirsch

Swen Elpelt

Jürgen Löhr

Tejashree Kate

Manuel Schlemelch

Ayushi Sachdeva

Siyu Zhao

A system for providing access to locally stored process image data to other devices in an industrial production environment includes a plurality of controller devices and a process image backbone. Each respective controller device comprises the following: a volatile computer-readable storage medium comprising a process image area; a non-volatile computer-readable storage medium; a control program configured to provide operating instructions to a production unit; an input/output component configured to update the process image area during each scan cycle or upon the occurrence of one or more events with process image data items associated with the production unit; and a historian component configured to locally store the process image data items of the process image area as time series data in the non-volatile computer-readable storage medium. The process image backbone provides the plurality of controllers with uniform access to the process image data items of each programmable logic device.

Universal data access across devices

Service interfaces and data topics can be discovered and retrieved so as to bridge different industrial automation ecosystems, programming languages, platforms, and the like, together. For example, nodes of one ecosystem can discover endpoints (e.g., interfaces and topics) across heterogeneous incompatible ecosystems, without changing the ecosystem. Further, endpoint descriptions are managed across heterogeneous incompatible ecosystems. Endpoint descriptions can be automatically generated based on interface and topic description in an interface description file. Such descriptions can also be automatically exported into registries of other ecosystems.

Endpoint registry across ecosystems

A method and a system are provided for data management in a transport device, in particular in a train. In a first comparison, a first count value stored in a first control device is compared with a count value stored in a second control device. In a second comparison, a count value selected from the first and second count values on the basis of a result of the first comparison is compared with a control count value stored in a safety device. On the basis of a result of the second comparison, control data stored in the safety device and associated with the control count value are acquired by the first or second control device.

Method and system for data management in a means of transport

Current approaches to integrating industrial ecosystems, for instance integrating automation functions across different vendors of programmable logic controllers (PLCs), lack efficiencies and capabilities. In an example aspect, a consumer, for instance a PLC, can poll PLCs for an automation function. In response to the polling, a first PLC that includes a memory defining a plurality of dedicated memory areas, can retrieve an interface from a registry memory area that stores information concerning available interfaces in a provider memory area of the plurality of dedicated memory areas, such that the consumer discovers the interface. The consumer can bind to the interface so as to establish a connection between the consumer and the first PLC at runtime of the automation function. In some cases, the plurality of dedicated memory areas further defines a consumer memory area. The first PLC can track available interfaces associated with the first PLC in the registry memory area of the plurality of dedicated memory areas.

Abstraction of PLC communication

A method of monitoring a track using train cars includes collecting first sensor data corresponding to a track location by a first sensor network on a first train car. Based on the first sensor data, a potential track anomaly at the track location is identified by a diagnostics system on the first train car. A message describing the anomaly is transmitted to diagnostics systems located on other train cars. The message is received by a second diagnostics system on a second train car located behind the first train car. The second diagnostics system determines a time at which the second train car will be passing over track location and, at the determined time, collects second sensor data. If the track anomaly is present in both the first sensor data and the second sensor data at the track location, a train control system is notified of the track anomaly.

Distributed bogie diagnostics for track monitoring

Methods, systems, and apparatuses are described that can encode connection information between consumers and providers for displaying to users. In an example aspect, a distributed control system includes a production network configured to perform automated control operation. The production network can include one or more data extraction nodes and a plurality of devices in communication with the data extraction nodes. The data extraction nodes are configured to collect data from the plurality of devices. The data indicates connection information associated with the plurality of devices. The system can further include a screen configured to display a plurality of interfaces that include the plurality of devices represented as consumers and providers. In some cases, the screen defines a single desktop monitor or a mobile device display.

Monitor and control for distributed system

A system and method for reducing an electrical load in a facility with a building automation system, includes first receiving information for a demand response event from an automated demand response server at an automated demand response client. After receipt of a new demand response event, the system determines a plurality of devices of the building automation system to be controlled during the demand response event. Next, the system prepares a schedule of control actions for the plurality of devices during the demand response event. The system then sends control messages to the building automation system to execute the control actions for the plurality of devices according to the schedule of control actions for the demand response event.

Automated demand response system

Automated demand response scheduling to reduce electrical loads

Systems and methods are described that allow a Programmable Logic Controller (PLC) to receive Demand Response (DR) data and process the data in a PLC Function Block (FB). Embodiments provide a PLC demand response FB that solicits DR data and a demand response load manager FB that compares the DR data with predetermined demand constraints corresponding to electrical equipment. The demand constraints provide energy consumption strategies for buildings and factories.

PLC function block for automated demand response integration

Growing community of inventors

Monmouth Junction, NJ, United States of America

Florian Ersch