Name / DI Michael Swoboda / Session / 6
Company / WIENSTROM / Block / 4
Address / Mariannengasse 4 / Question n°
A-1095 Wien AUSTRIA / Language used on the floor / english
Phone / +43 664 6231511 (+43 676 6107324) / Accompanying visuals on file ?
e-mail /
Dipl.-Ing. Franz Reisinger
Ing. Gerhard Kohler
Dipl.-Ing. Michael Selymes
Dipl.-Ing. Michael Swoboda
Introduction of conditioned based maintenance at WIENSTROM using the knowledge-based expertsystem MABI
WIENSTROM
We are an Austrian utility company which is supplying our capitol city vienna and the area around.
Now some data about WIENSTROM:
- The magnitude of our supplied area is about 2.00km2
- We are running 40 substations
- About 10.000 nettransformers
- 220.000 house service connections
- and nearly 1.5 million electricity meters
- 56km of 380kV Lines
they are mixed in cables and overhead lines - 764km 110kV lines
also cables inside the city and overhead lines outside - ~7.000km medium voltage lines
- and ~14.000km 1kV lines
- the maximum load was 1.918MW on the 11.12.2002
- we have 1.503MW installed power
modern maintenance strategy
The trigger to modern maintenance strategy for WIENSTROM was the deregulation of the Austrian electric power market and the reorganisation at our company. Before we used so called “no risk-oriented strategy.
Our new way is a mixture of the following strategies:
The event oriented strategy
Unforeseen events sometimes need immediately action. E.g. after 5 times auto – reclosing a
Circuit breaker you have to overhaul it.
Time based strategy
Which is often necessary at new systems to keep the guarantee.
Condition based strategy
For this strategy you need knowledge. From a man or an expertsystem.
For the reliability orientated and the risk based strategy you need also information’s about
- break downs (RCM)
- importance (RBM)
The expert system in use
You can divide the system in 3 mean blocks.
- MMI the man machine interface
For this proposal an internet browser like Microsofts internet explorer or netscape is used. So you get maximum flexibility. By connecting the server from any workstation which is connected to the companies IT-network. - The function block
which contains
– the datacare
– the condition catch
– the condition valuation and
– the maintenance planing
You can call it the “calculation block”. - And at last the data bank.
It is the heart of the system for which an Oracle server is in use.
How it works
On this picture you can see the working flow of the system.
From the condition catch you get the working stock data. With this data and the expert knowledge a condition valuation is done.
After this there are 3 states.
- Condition OK (green state)
- the orange state
- the red state
It is the same procedure like a traffic light.
Outgoing from the orange and the red state the system gives you a decision by stratical valuation.
- There are steps necessary at the moment
- There are no steps necessary at the moment maybe later
Break down log
We have two types of break down protocols.
- The working log
Which is for the worker on side. It shows him special steps after a break down.
E.g. the overhaul of a circuit breaker after the last auto – reclosing. - The expert log
It is for the engineer to tune the expert system
E.g. give an alert after 6 times auto-reclosing or 4 times.
Possible interfaces
The systems in use is very flexible.
There are a lot of possible interfaces
- For mobile datamanagement (to connect hand helds, ipaqs, etc.)
It is to catch the data on side. - Interfaces to overhead line calculation programs or global information systems.
- To the record office
E.g. automatically correct setting values. - This days very important is the interface to SAP.
E.g. for planing the maintenance costs. - Also you can design an interface to any other calculations.
Our experience
At last I want to tell you about our experience witch the system.
- Cost minimisation is possible:
- Knowledge is independent from men and can be used by everybody.
- It helps you to get equal rules and equal maintenance all over the company.
- it is possible to get a maintenance process synchronisation.