Siemens Aktiengesellschaft

Siemens Corporation

Siemens Industry Software Gmbh

Oswin Noetzelmann

Rainer Heller

Rami Reuveni

Victor Robert Hambridge

Attila Labas

Dirk Schaumburg

Marine Durel

Andrew Dylla

Prithvi Raju

Edward Slavin

Georg Muenzel

Andreas Wannagat

Sarvananthan Ragavan

Amir Davari Jazin

Karoly Kiraly

Wilfried Barth

Igor Usykov

Dirk Schwarz

Marcel Wolff

Venkata Prasad Reddy Mukka

Engelbert Blumenthal

Venkata Prasad Mukka

Metin Kaplan

Daniela Stederoth

Reinhard Simon

Tobias Lange

Marko Bogeljic

Jochen Handels

A system for industrial application package management includes a computing device having a processor and a memory having executable programs and applications stored thereon, including plurality of industrial application programs running an engineering project involving multiple different disciplines, and a package manager client. The package manager client communicates with a remote repository server that hosts application packages, and sends requests for packages and receives package deliveries. The package manager client unbundles package metainformation relevant to a domain specific application and according to an industrial package information schema. A dependency tracking module identifies dependencies of a current package to other packages and generates a dependency tree that includes the name and version of each dependent package. An upgrade analyzer compares dependency trees to identify dependency incompatibilities as conflicting packages based on inconsistencies and performs an automated resolution of the dependency incompatibilities.

Industrial application package management

The preferred embodiments described below include methods, systems and computer readable media for cross discipline data validation checking in a multidisciplinary system. One or more multidisciplinary validation rules are used to perform cross discipline data validation checking to determine whether multidisciplinary data is consistent across engineering disciplines. The multidisciplinary validation rules define the scope of the validation checking within the engineering application () associated each engineering discipline. The results of the validation check are provided to the user.

Method and system for cross discipline data validation checking in a multidisciplinary engineering system

A method for planning a technical system by providing a number of engineering objects in which each engineering object describes a technical component of the technical system, includes types that refer to a function of the engineering object and information about to what which domain of a plurality of domain each type belongs to and includes electrical information that includes a schematic symbol description, an electrical behavior and electrical characteristics, a number of coherence requirements for the technical system are provided, where the coherence requirements include object patterns defining objects of a same kind to be grouped together and a required order of a sequence of the objects in the object patterns, an engineering object is selected, a schematic is generated by placing the schematic symbol description of the selected engineering object and associated engineering objects of an object pattern belonging to the selected engineering object on a plan, and electrical connections between all objects of the object pattern of a same kind to be grouped together are generated in accordance with the coherence requirements.

Method for computer assisted planning of a technical system

The preferred embodiments described include methods, systems, and computer readable media for linking data in a multidisciplinary engineering system. One or more multidisciplinary templates are created for a multidisciplinary engineering system. Reusable multidisciplinary templates link engineering objects and parameters between engineering disciplines. The objects and parameters in the template may be linked to one or more disciplines based on role, responsibility, department or other criteria. Changes to the template may be propagated to each discipline affected by the changes. The template may also link data entered at the engineering applications () and facilitate workflows and sign-off procedures between applications ().

Templates in a multidisciplinary engineering system

The preferred embodiments described below include methods, systems and computer readable media for generating programmable logic controller (PLC) code based on a connectivity model in a multidisciplinary engineering system. The connectivity model provides interfacesandand connectionsbetween various aspects of the multidisciplinary engineering system to provide engineering data, code scripts, executables, calls and other information that is used to generate PLC code. Code generation rulesare employed utilizing the engineering data, code scripts, executables, calls and other information received using the connectivity model to generate PLC code.

Method and system for generating PLC code with a connectivity model

A visual representation of a mechanical-electrical machine behavior model is presented that utilizes a non-linear time scale to best illustrate multiple details occurring in a relatively short time frame without affecting the amount of information contained in the complete model. In particular, time periods without user-relevant details are identified and minimized so as to allow for the display space to adequately represent the details associated with the actions of each machine. By 'folding' these longer time periods to occupy relatively short lengths along the time axis, additional space along the time axis is then available to illustrate the details of each operation (i.e., by using a non-linear time scale).

Non-linear time scale optimization for mechanical-electrical machine behavior model visualization

A method for splitting and merging runtime software for a programmable logic controller, wherein the runtime software is splittable between a plurality of programmable logic controllers. After the runtime software has been split, the runtime software of a programmable logic controller may be merged into the runtime software of a different programmable logic controller.

Split and merge sequence description

The present disclosure provides a dynamic view in a modeling of an automation system. A first portion of the model may be described in a first sequence description and a second portion of the model may be described in a second sequence description. The sequence descriptions are linked together. In one embodiment, the links are visually provided.

Dynamic views in a modeling of an automation system

A visualization of an electrical machine operation model of logic controller behavior is displayed on a display such as a two-dimensional computer display. The display includes separate spaces representing separate devices in the model. For each device, several characteristics are shown in the model, including mechanical steps, electrical steps and electrical signal outputs. The electrical steps are shown superimposed on the mechanical steps, and electrical transitions link sequential electrical steps in time. Representations of conditions link the electrical transitions with signal outputs upon which the electrical transitions are conditioned.

Visualization method for electrical machine operation models based on mechanical machine operation models

Growing community of inventors

Monmouth Junction, NJ, United States of America

Oswin Noetzelmann