A Component-Based Power System Model-Driven Architecture

This letter describes an approach of applying the model-driven development in power systems. A component-based model-driven architecture,that gives full flexibility of the automation in source code generation,is introduced. A design pattern to code generation is described

Establishing an efficient regulatory mechanism — Prerequisite for successful energy activities regulation

An analytic approach to determine appropriate regulatory strategies for the energy sector is proposed in this paper.A basic model of the regulatory system in the energy sector is defined, and the regulatory mechanism functions in this context are outlined. The basic problem of unknown factors (i.e., system entropy) is highlighted. An original algorithm developed to analyze regulatory background context and regulatory mechanism functions is discussed.A useful method for defining existing level of energy activities is also presented using the Croatian regulatory framework as an example

A General-Purpose Symbolically Assisted Numeric Computation Environment as a Support in Power Engineering Education

This paper describes and illustrates a Windowsbased, general-purpose, symbolically assisted numeric computation environment within power engineering education applications. The examples considered include fundamental problems derived from three areas: power system analysis and optimization, electric machinery, and feedback control systems

A component based approach to power system applications development

peer reviewedThis paper addresses issues of reusability of component models. Once a component model is designed, implemented and tested, it should be possible to use it as many times as necessary for a variety of purposes. The main idea of this paper is to introduce a new way for building flexible power system applications. In order to obtain code reusability a "general" non-linear equation handler and solver is implemented. The general-purpose solver does not need to know in advance what kind of problem is going to be solved. Instead, the solver is based on symbolic model handling and evaluation. In order to use the model, each specific application of interest has a converter that transforms input data to the realm of the general purpose solver. Both the application-specific converter and the general purpose equation handler and solver are designed as components. Thus, there is no need to change, or to recode the solver each time when new specific problem of interest arises. It is only necessary to create a new "converter." The result is that the complete development process is less error prone. In addition to describing code reusability, this paper also presents a unique way of collecting input data and model descriptions that make it possible to reuse symbolic models in an effective manner