Mathias Dutour / UAB Dev. teamUNICOS regular meeting29 January 2009

Needs to address. Usage: the big

picture. A closer look. Other UAB

capabilities. Current status.

User perspective: Flexible tools to adapt to project specific needs. Extensive and customizable support for

troubleshooting. Traceability and consistency of generated

artefacts.

UNICOS core team perspective: Improve control of tools and UNICOS Device Type

evolution. Minimize new UNICOS Device Type integration. Minimize new target platform code generator

development. Minimize maintenance of software tools on the long run.

Doc SCADA PLC

UNICOS Manager

UNICOS Expert

Project Management

Tool

Process Expert

Control System Developer

Type Creation Tool

Generation Tools

Device Types

Generation templates

Verification rules

or

or

Application configuration

UNICOS Model

UNICOS Core team

B output of A:

A Input of B

A B

A B

UNICOS Model: Mold for the creation of UNICOS Device Types

definitions. Standard UNICOS characteristics Device Types must,

should or may embed. Covers front-end, SCADA aspects and more of Device

Types. Is maintained and controlled by the UNICOS core team. Is platform independent (e.g.:PVSS, Schneider, etc.)

Type Creation Tool (TCT): Guides the user in the creation of custom Device Types

based on UNICOS Model. Improved control of tool and UNICOS Device Type

evolution. Can generate Excel-XML templates for instances edition

and much more.

Doc SCADA PLC

UNICOS Manager

UNICOS Expert

Project Management

Tool

Process Expert

Control System Developer

Type Creation Tool

Generation Tools

Device Types

Generation templates

Verification rules

or

or

Application configuration

UNICOS Model

UNICOS Core team

B output of A:

A Input of B

A B

A B

Generation plugin (platform specific)

Selected generation templates

Application configuration

(Project-specific)

Std. and project-specific

verification rules

Selected Device Type definitions

…Std. and

project-specific plugin

configurations

UAB Core

…

Based on Device Type definitions, one could generate automatically:

Device type documentation. Code skeletons for PLC baseline. Code skeletons for PLC baseline. Etc.

Using UAB Core, it becomes very easy to manipulate:

Jython scripts interacting with other data sources.

Any input XML file (in and out). Configuration information. Target code snippets. Etc.

UNICOS Model and TCT: Comments from UNICOS Core team being collected.

UAB Core: Ready. Schneider PLC instances: Ready, needs Device

Types for evaluation. Schneider PVSS instances: Ready, needs Device

Types for evaluation. Siemens PLC instances: ~80% completed, needs

Device Types for evaluation. Schneider PLC logic: (1 week delay, week 6 to be

confirmed).