Interfaces and Integration Solution.pdf

8/18/2019 Interfaces and Integration Solution.pdf

http://slidepdf.com/reader/full/interfaces-and-integration-solutionpdf 1/47

For internal use only / Strictly confidential / Copyright © Siemens AG 2007. All rights reserved.

Interfaces and Integration Solutions

Ulrike Sachs



page 1

Different Tasks to solve with Interfaces

1. Import ready to use network models from other systems(exchange data between systems/countries, change over to other software)positive:

all relevant data are availableimport results can be compared by loadflow/short circuit results

issues:

only the elements which are supported by both systems can be transferredproperlythe input data may have different reference valuesthe element models may be differenthave to solve “gaps” with lacking elementsonly load flow data (and may be short circuit data) will be transferredgraphical presentation often is a problemoften only import capabilities are offered

All solutions proposed in this sections are “Adapters” which need filled andstructured input files! – In other applications these are called “Interfaces”



page 2

Different Tasks to solve with Interfaces2. Build a model from different application sources

(make usage of existing data for network simulation and planning)positive:background images from GISlarge network models without manual digitizingmaintenance of the models is done in central applicationsissues:

different data sources for the same object need a common ID systema mapping between different systems is necessaryno standard interface for all customer possibleone application has to be defined as master system – corrections approx 10-15%

not all data availabletracing in GIS systems takes time – exports not directly on demand or only for smallareasdifferent view (schematic and topological) have to be linked togetherlarge network need „intelligent“ transfer (reduce nodes, delete unnecessary elements)update of networks



page 3


3. Import/ update time-dependant values, e.g. metering data(have benefit from smart meters and gain additional information)positive:metering data are already stored an aggregated in MDMS systemsSCADA systems have actual data for switches and transformers

better knowledge of the actual network situation helps to operate the networks moreeffectivly and increase the loading to the maximumissues:Data model between SCADA system and network simulation software often differslarge number of data increases to data base to an extent where simulations are nearlyimpossiblenetwork simulation tools needs other algorithms and much more evaluation options tooffer the right information to the user



page 4


4. Interfaces for dynamic models(share models with other users and use vendor models)positive:large amount of models availabletested models

quicker setup of dynamic modelsissues:no common definition for the valid range for a modelparameter have to be adjusted – knowledge of the internals may be necessarymodels for EMT or for EVAmodeling of the elements in other simulation methods



page 5

DataDictionary

COM-Interfaces: Data base access layer

Input data

Graphic data

Results

SINCAL DB

SQL-DB Librariesglobal / localglobal / local global / local

elements protection macros

Object oriented access layer (models, methods, cases)

G U I

C a l c u

l a t i o n

m e

t h o

d s

T a

b u l a r

E d i t o r

R e p o r t s

( C r y s

t a l )

D i a g r a m s

E v a

l u a

t i o n s

M e s s a g e s

….

WorkspaceXML

PSS®SINCAL Architecture

I n t e r f a c e s

( A P I , C O M )

Standard Interfaces:•GIS Smallworld(Mettenmeier)•DVG•DGS•UCTE•PSS E•Adept•Viper•NETOMAC•CIM•ODMS

EXCEL-Import

Scripting(any language)

Customized:SCADAGISSAP….

CustomizedApplications

Data Bus - (virtual) Data Ware House - Middle ware IEC 61968 - CIM/XML

G I S

S C A D A

E R P

M e

t e r i n g

A s s e

t s

M a

i n t e

n a n c e

…

CIM/XML

O D M S



page 6

PSS®SINCAL Import/Export Options



page 7

SINCAL data exchange to Siemens systems

Import of network models from PSS®Adept und PSS®VIPERsupporting version 11,14 and 15 (*.hub, *.dmp)for Load flow and short circuitincluding the graphical information

taking over construction files, protection data bases

Export of PSS®NETOMACnetwork modelmacrossignals from network modelsdisturbances

Import ready to use network models from other systems



page 8


SINCAL data exchange to Siemens systems

Import and Export of PSS/E network models

supports version 27,29,30,31 and 31 for Import and the newest format for exportimports *.raw, *.seq, *.dyr, *.drw, *.loc, *.sld

exports *.rawSINCAL data base can hold full PSS/E network modelunique node names can be created by default

For the import of dynamic data, PSS/E Standard models are requested. They will be replaced bythe corresponding models form NETOMAC/SINCALUser-defined models will be supported in short time, too, by placing them into a container macrogeneric wind models and FACTs models (for dynamic simulation) are available as libraries



page 9


SINCAL data exchange to other systems

Import and Export of DVGnetwork models (FGH, INTEGRAL, Transmission Networks in Europe)

supports version 1.1.2000 and higher

imports *.net, *.bildexports *.netallows error-tolerant importZero-phase system data are createdExtended Ward, Equivalence Networks and Boundary Injection available



page 10


SINCAL data exchange to other systems

Import and Export of DGS ASCII-based formatnetwork models (Digsilent, PowerFactory)

The following PSS SINCAL network elements can be imported or exported:

Node/busbar LoadInfeeder Shunt impedanceSynchronous machine Shunt reactorAsynchronous machine Shunt capacitorLine Serial reactorTwo-winding transformer Serial capacitorThree-winding transformerGraphics can also be imported from the DGS file.Importing multiple views is also supported, as long as these are contained in the DGS file.



page 11


SINCAL data exchange to Standard Exchange Formats

Import and Export of UCTE ASCII-based formatImport of version 1 and 2Export of version 2

no graphics available

Import and Export of CIM/XML Formats (IEC 61970-301)Import and Export of version 10,11,12 and 13Profiles: CIM Standard, CIM for Planning, CIM for ENTSO-Eno graphics in profiles availableSINCAL offers graphical import and export via locationsSINCAL offers unbalanced network structures in addition



page 12


Enhancements for CIM 14 withENTSO-E Profile

The following illustration shows thefile organization for a CIM UCTEnetwork. It consists of the followingfiles:

UCTE Common ObjectsTSO Equipment ModelTSO TopologyX-NodesState Variables

CIM import and CIM export functions in PSS SINCAL have been enhanced so that now either individual ormultiple files can be used to describe a CIM 14 UCTE network:•When you import, any number of CIM files can be selected. These must be semantically and syntactically correct.Then they will be processed.•When you export, there is a new option as to whether a single complete CIM file will be generated or a split CIM

file is created. In a split CIM file, all objects are distributed according to the specification from ENTSO-E profile.

SINCAL Import and Exportof CIM/XML Formats(IEC 61970-301)



page 13

Special Import : EXCEL Interface

Import (parts of) models with EXCEL

Import ofnetwork modelprofilesgraphics

updates of element dataoptions for error-tolerant importwhole interfaces from GIS possiblewithout programming – only mapping

limitation:no value calculation possible

Export by simple copy and paste from table editor



page 14

Special Import: COM-Interfaces - ScriptingImport models with prepared scripts (VBA or C++)(all languags are possible including Python, Java, *.net,…)Import of

network modelgraphics

from a prepared network source via a temporary data base in SINCAL Data Base structure…….' Execute the selected optionSelect Case strParam

Case "E" bElectro = TrueCall InitIDs()Call ReadNodes( 1 )Call ReadLines( 1 )Call ReadLoads( 1 )Call ReadTransformers( 1 )

Case "W" bElectro = FalseCall InitIDs()Call ReadFlowNodes( 1 )Call ReadFlowLines( 1 )

Case Else Call Usage()End Select

If ErrorCheck( "Error while reading input data!" ) Then WScript.Quit

' Write data from arrays to SINCAL databaseCall WriteSINCAL()

If ErrorCheck( "Error while writing data!" ) Then WScript.Quit…….

Example-Script:-> C:\Program Files\PTI\PSS SINCAL

6.5\Project\Batch\Advanced:“ImportDB.VBS”



page 15

Type uni directional –bi directionaldown-load - Engines

Frequency one time/ on request – SynchronizationGIS - SCADA

Executable - Exchange of ASCII-files (alpha- data, Graphics)(Standard formats or spec. definitions)

- transfer of EXCEL /Data base formats(on different levels)

- developing scripts/programs(Standard in GIS/ SCADA- world)

- communication with COM- Interfaces(modern concept, which is used by Microsoft , too)

- Engines Concept (API)

(own applications)

concepts for Integration2. Build a model from different application sources



page 16

uni directional – onetime – ASCII – Example DVG

2. Build a model from different application sources



page 17

uni directional – onetime – EXCEL with or without Graphics2. Build a model from different application sources



page 18

uni directional – on request – Scripting2. Build a model from different application sources



page 19

Customer-specific Integration always is a project!

Steps:have a workshop with the customer to evaluatewhich data sources are availablewhich ID systems can be used (-> or mapping)

quality of datawhere to find and how to model the loadsdemands of the customer for the interface

offer an “interface” = Integration of different application to fill SINCALdata base for a read to use network modelproject takes between 4 months and 1 year (mainly depends on thedata quality and the amount of corrections in the source systems)

cost approx 50.000- 100.000 €




page 20


ID1

2

4

5

6

7

8

9

10

11

12

13

Projektstart

A) Erstellung der Projektdefinition

B) Realisierung

B1 Bereitstellung der Quelldaten

C) Übergabe

C2 Anwendertest

Projektende

W-2 W-1 W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12 W13 W14 W15 W16 W17



page 21


ID Task Name1 PROJEKTSTART

2 PHASE DEFINITION

3 A) Erstellung der Projektdifinition

4 A1) Spezifikation der BOF

5 A2) Spezifikation der Vordatenbank

6 A3) Spezifikation der SINCAL-Datenbasis

7 A4) Verifikation und Freigabe

8 PHASE REALISIERUNG

9 B) Bereitstellung der Werkzeuge I.

10 B1) zur BOF

11 B2) zur Erstellung der Vordatenbank

12 B3) Übergabe testgebiet

13 C) Bereitstellung der Werkzeuge II.

14 C1) zur Datenübernahme in SINCAL

15 PHASE ÜBERGABE UND ABNAHME

16 E) Übergabe

17 E1) Installation

18 E2) Schulung19 F) Produkionstest

20 F1) Anwendertest

21 F2) Einarbeiten von Änderungswünschen

22 G) Abnahme

23 G1) Abnahme

24 PROJEKTENDE

9/1

PHASE DEFINITION

GIS-Admin

GIS-Admin,L&MARK

L&MARK

SIN-Anwender

PHASE REALISIERUNG

GIS-Admin

GIS-Admin

GIS-Admin

L&MARK

PHASE ÜBERGABE UND ABNAHME

GIS-Admin,L&MARK

SIN-Anwender,GIS-Admin,L&MARK

SIN-Anwender

GIS-Admin,L&MARK

SIN-Anwender,GIS-Admin,L&MARK

1/31

-1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25Month 1 Month 2 Month 3 Month 4 Month 5 Month 6



page 22

Engines Solution (for GIS, NIS or SCADA systems)SINCAL simulation (*.dll) gets a part of the master-application !

connection with COM-Interfaceno data transfer necessarydata base is a virtual data base in the memory of the master-applicationvery quick simulation times

no SINCAL GUI visible


Client Applikationsprozess

COM-Interface

PSS™SINCAL Berechnung"Simulate.dll"

Client Applikationsprozess

COM-Interface

SimulateSrv.exe

PSS™SINCAL Berechnung"Simulate.dll"

External ServerIn-Prozess Server



page 23

bi directional – synchronous – Engines API (COM-Server)




page 24

Example: ESRI GIS & SINCAUT Spectrum

Interface to PSS™SINCAL

• GIS – PSS™SINCAL Interface• DMS – PSS™SINCAL Data Import Tool

• Network Analysis in PSS™SINCAL



page 25

GIS – PSS SINCAL Interface

Interface Toolbar in GIS



page 26


Step 1: Preparation, Setting of Barriers



page 27


Step 2: Selection of Network Area



page 28


Step 3: Conversion



page 29

GIS – PSS SINCAL InterfaceStep 3: Conversion Completed



page 30

Optional:DMS Data Import Tool to PSS™SINCAL

Load Scaling

• Average and peak measurement data• Corresponding Switching status

can be read from the DMS. Measured load data can be usedor Load Scaling can be carried out.

Load profilescan be loaded so that load flows at different point in time canbe analyzed.



page 31

DMS – PSS™SINCAL Data Import Tool



page 32

Converted Network in PSS™SINCAL Interface



page 33

Converted Network in PSS™SINCALZoomed to primary substation



page 34

Converted Network PSS™SINCALEvaluation of results



page 35

Converted network area in PSS™SINCALwith exported GIS landbase



page 36

Converted network area in PSS™SINCALColor-coded visualization of loads and overloads



page 37

Converted network area in PSS™SINCALResult evaluation in tabular view



page 38

3. Import/ update time-dependant values, e.g. metering data

Smart Metering



page 39


Smart Metering



page 40




page 41




page 42


page 43


Network State in an XML File

• This function exports/imports PSS SINCAL network states (i.e. the switch positions,operating states and controller data of network elements) into/to an XML file

• updates from e.g. SCADA systems could be derived

<?xml version="1.0" encoding="UTF-8"?><sincase xmlns="http://www.simtec.cc/sincase/1.0"><Document><name>test</name><Settings><ExportRange>Full</ExportRange><Content>SwitchState</Content><Content>OperatingState</Content><Content>Graphic</Content>

</Settings><NetworkData><Node id="N1" objId="1" type="Node"><Name>N1</Name>

<ShortName>N1</ShortName></Node><Node id="N2" objId="2" type="Node"><Name>N2</Name><ShortName>N2</ShortName>

</Node><Element id="E1" objId="1" type="Line" node1="N1" node2="N2"><Name>L1</Name><ShortName>L1</ShortName><State>1</State>

</Element>



page 44

4. Interfaces for dynamic models- user defined models



page 45

4. Interfaces for dynamic models – user defined models



page 46

4. Interfaces for dynamic models – Matlab Simulink Models

Interfaces and Integration Solution.pdf

Documents

Transcript of Interfaces and Integration Solution.pdf