Substation P&C Orchestration for Non-Critical Application Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing P&C systems in electrical substations face challenges in efficiently deploying and managing non-critical applications due to resource limitations, vendor-specific hardware, and inflexible deployment strategies, leading to wasted resources and high engineering costs.

Innovation Solution

A P&C system with application execution resources, memory, and an orchestrator that dynamically deploys and monitors subordinate applications, allowing them to self-adjust their operation based on available resources and predefined requirements, ensuring they do not disrupt critical applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dedicated hardware is used for priority P&C applications, then real-time execution and fault tolerance are guaranteed, but resource utilization efficiency deteriorates and engineering costs increase

Engineering Contradiction:
Improvefault tolerance guaranteeVSAvoidresource utilization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements a universal hardware platform that can execute both priority P&C applications and subordinate applications. The application execution resources are designed to dynamically allocate capacity between different application types, allowing the same physical infrastructure to serve multiple functions. This eliminates the need for separate dedicated hardware for priority applications while maintaining their reliability requirements through virtualization and resource partitioning mechanisms.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system employs dynamic resource allocation where the computing resources are not statically assigned but can flexibly adjust based on current workload demands. The orchestrator continuously monitors system state and dynamically schedules subordinate applications on available capacity without compromising priority applications. This dynamic approach allows the system to adapt to varying operational conditions and maximize resource utilization while preserving real-time performance guarantees for critical functions.

Inventive Principle:
Principle #15Dynamics

2Reliability

If dedicated hardware is used for priority P&C applications, then execution constraints are met, but device complexity and engineering effort increase

Engineering Contradiction:
Improvereal-time execution guaranteeVSAvoidhardware configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an orchestrator as an intermediary software layer that manages the complexity of resource allocation and application deployment. This orchestrator handles the sophisticated tasks of monitoring system state, scheduling subordinate applications, and ensuring priority applications meet their execution constraints. By placing this intelligence in software rather than hardwiring complex hardware configurations, the system achieves real-time guarantees without proportionally increasing hardware complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service mechanisms where the orchestrator autonomously manages resource allocation and application lifecycle without requiring manual hardware configuration or intervention. The platform automatically detects available capacity, schedules appropriate subordinate applications, and adjusts resource allocation in response to changing conditions. This self-managing capability reduces engineering effort and operational complexity while maintaining reliable execution of priority applications.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If subordinate applications are added to the P&C system, then system functionality is improved, but system stability and integrity may deteriorate

Engineering Contradiction:
Improvesystem functionalityVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the application execution environment into distinct priority levels and isolation boundaries. Priority P&C applications run in protected environments with guaranteed resource allocation and execution constraints, while subordinate applications execute in separate, non-critical environments. This segmentation creates firewalls that prevent subordinate applications from interfering with or compromising the stability of priority applications, allowing enhanced functionality without sacrificing system integrity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The orchestrator implements continuous feedback mechanisms that monitor the execution state of both priority and subordinate applications. It tracks resource utilization, performance metrics, and system health indicators in real-time. Based on this feedback, the orchestrator dynamically adjusts the scheduling and resource allocation for subordinate applications to ensure they do not adversely affect priority applications. This closed-loop control maintains system stability while enabling flexible addition of new functionalities.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4641382A1Protection and control system for an electrical substation, and method for application orchestration of a protection and control system
Publication Date: 2025.10.29 ABB (SCHWEIZ) AG
  • EP4641382A1 patent drawingFigure 1~2
  • EP4641382A1 patent drawingFigure 3
  • EP4641382A1 patent drawingFigure 4

AI summary

A Protection and Control, P&C, system (1) for an electrical substation includes a plurality of application execution resources (100, 200, 300, 400, 500) each configured to execute one or more priority P&C applications (101, 102, 201, 202, 301, 302, 401, 501), and configured to execute one or more subordinate applications, a memory (30) for holding one or more subordinate applications (31, 32) to be additionally executed by the application execution resources (100, 200, 300, 400, 500), an application orchestrator (10) configured to determine, among each of the application execution resources, a subordinate execution capability for a subordinate application in the memory (30), and to instruct each of the application execution resources (100, 200, 300, 400, 500) determined to have a subordinate execution capability to execute an instance (110, 210, 220, 310, 320, 410, 510) of the subordinate application (31, 32), one or more application monitors (111, 211, 311, 411, 511) configured to, for an executed subordinate application instance, determine whether an execution condition (112, 212, 312, 412, 512) is met, and when it is determined that the execution condition is not met, terminate the instance.