IED Configuration Using Platform Capability Description Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IED configuration tools (ICTs) are specific to device families, requiring new tools for new IEDs, limiting flexibility and efficiency, and users often pay for unused functionalities without the ability to customize data models or restrict usage.
Innovation Solution
A platform capability description (PCD)-based approach that generates PCD files defining IED capabilities, licenses, and rules, allowing an IED-agnostic configuration using a bundle of files to configure any IED platform, including a manifest and configuration files.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If IED-specific configurator tools are used for each device family, then configuration accuracy for specific devices is improved, but device complexity and the number of required tools increase
Solution Approach 1:
The patent implements a universal configurator tool that can configure multiple IED device families through a standardized configuration interface. The system uses an IED-agnostic configuration model that translates device-specific parameters into a common configuration language, allowing one configurator tool to serve multiple device families while maintaining configuration accuracy for each specific device type.
Solution Approach 2:
The patent introduces an intermediate configuration model that acts as a mediator between device-specific requirements and the universal configurator interface. This intermediate layer translates IED-specific parameters into standardized configuration objects, enabling the configurator tool to handle multiple device families without requiring device-specific tooling while preserving configuration precision.
2Adaptability or versatility
If IED-specific configurator tools are developed for each device family, then device-specific configuration requirements are met, but development time and cost increase
Solution Approach 1:
The patent creates a single universal configurator tool that can configure multiple IED device families, eliminating the need to develop separate tools for each device family. The standardized configuration interface and translation layer enable the tool to adapt to different device families without requiring re-development, significantly reducing development time and costs while maintaining device-specific configuration capabilities.
Solution Approach 2:
The patent uses parameter-based configuration models that can be adjusted to accommodate different device families. By defining configuration parameters in a standardized, extensible format, the system can adapt to new device families by updating configuration parameters rather than developing new tools, thereby reducing development time while maintaining adaptability to device-specific requirements.
3Adaptability or versatility
If comprehensive IED functionality is provided, then users have access to all possible features, but users pay for unused functionalities
Solution Approach 1:
The patent segments IED functionality into modular configuration objects that can be selectively enabled or disabled. The configuration model allows users to choose only the specific features and functions they need, rather than requiring comprehensive functionality. This segmentation enables users to pay only for the features they actually use while maintaining access to the full range of capabilities when needed.
Solution Approach 2:
The patent implements dynamic configuration capabilities where IED functionality can be adjusted and customized based on user needs. The configuration system allows users to enable or disable specific functions, adapt the configuration to match actual usage patterns, and modify capabilities over time. This dynamic approach ensures users pay for functionality they actually utilize rather than being locked into comprehensive, unused features.
Data Source
AI summary
Devices, systems, and methods for platform capability description (PCD) file-based configuring of intelligent electronic devices (IEDs) may include generating, by at least one processor, PCD files for an IED, the PCD files defining the capabilities of the IED, a license of functions of the IED for a user, and rules applying to settings of the IED; generating, using an IED configurator tool from which IED rules are absent, based on the PCD files, a bundle of files for the IED, the bundle comprising a manifest and configuration files for the IED; and providing, by the IED configurator tool, to the IED, the bundle, the license of functions, and the rules, wherein the IED is configured based on the bundle, the license of functions, and the rules.