Automation Planning With Cloud and Edge Component Hierarchy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a need for improved planning of automation systems that integrates cloud environments and edge devices, allowing for the development and adaptation of sector-specific applications in mechanical engineering, while maintaining proprietary know-how and leveraging existing knowledge of mechanical engineering companies.

Innovation Solution

A method for planning automation systems that integrates cloud environments and edge devices into a project structure, using a technological hierarchy, with defined project elements, program blocks, and device configurations, allowing for the performance of automation tasks both in the cloud and on edge devices, and utilizing existing knowledge and skills of mechanical engineers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud environments and edge devices are integrated into the automation system planning, then the capability to perform automation tasks in the cloud/edge is improved, but the device complexity increases

Engineering Contradiction:
Improvecapability to perform automation tasksVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an edge device as an intermediary component between the automation system and the cloud environment. This edge device handles local processing and communication, mediating between the control system and cloud services, thereby enabling cloud-based automation tasks while managing system complexity through layered architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the automation system into distinct functional layers: control system, edge device, and cloud environment. Each layer has specific responsibilities and can be independently configured and managed, allowing the system to leverage cloud capabilities without monolithically increasing overall complexity.

Inventive Principle:
Principle #1Segmentation

2Reliability

If sector-specific applications are developed with proprietary know-how, then the application quality and suitability are improved, but the knowledge loss to external providers increases

Engineering Contradiction:
Improveapplication qualityVSAvoidproprietary know-how
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent extracts and isolates proprietary know-how within the control system and edge device layers, keeping sensitive mechanical engineering knowledge internal to the automation system. Only anonymized or processed data is transmitted to the cloud, separating critical proprietary information from external cloud services while still enabling cloud-based application development.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If cloud services are used for automation tasks, then the productivity and availability are improved, but the dependency on external infrastructure increases

Engineering Contradiction:
Improveautomation efficiencyVSAvoidsystem independence
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary action by pre-configuring the edge device with local processing capabilities and caching mechanisms. This allows the system to prepare for cloud unavailability by maintaining local functionality, ensuring that automation tasks can continue operating with reduced dependency on external cloud infrastructure.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11169510B2Engineering system and method for planning an automation system
Publication Date: 2021.11.09 SIEMENS AG
  • US11169510B2 patent drawing
  • US11169510B2 patent drawing
  • US11169510B2 patent drawing

AI summary

An engineering system for planning an automation system and method for planning the automation system, wherein a cloud environment and/or an edge device are integrated into a project structure of a planning environment, where the project structure includes components and has at least one hardware component that has project elements, where the integrating includes saving and displaying the cloud environment or the edge device, in a manner structured as a component, accordance to a technological hierarchy, and wherein project elements associated with the cloud environment and/or with the edge device are defined, where at least one program block and a device configuration are stipulated for the cloud environment or the edge device, and where the hardware component and the cloud environment and/or the edge device are via the planning to perform an automation task of the automation system that must partially be performed in the cloud environment and/or edge device.