UNICOS redesign

Front End naming

24/04/2013Marco Boccioli

Front End - use cases

1. Rename FE PICSW-107 PICSW-88 IS-10622. Move device to another FE3. Move device to another system4. Expand naming restrictions IS-8165. Hierarchy of FE6. Hierarchical view of devices (user defined

set) IS-10647. Allow FE type+model IS-899

Front End - currently

• FE Dp = system:feType_feName• FE Alias = feName• Device Dp =

system:prefix-feName-feApplication-deviceType-#• Remarks– Cannot rename FE– FE naming restrictions: UNICOS + WinCC OA dp

restrictions– Redundant name information (alias included into dp

name)

Front End - ideas

• Allow renaming• Extend allowed characters for naming• Adopt implementation similar to devices– Dp: treated as an internal identifier– Alias: the only name visible to the user

• Back-compatibility– Import line:PLCCONFIG;feType;[feIdentifier,]feName;…

Front End - proposal

• New convention:– FE Dp = system:feIdentifier– FE Alias = feName– Device Dp =

system:prefix-feIdentifier-feApplication-deviceType-#

• Example:– FE Dp = system:plc_00001– FE Alias = CFP-UA23-CIPAL2– Digital Input Device Dp =

system:un-plc_00001-VISL-CPC_DigitalInput-00001

Front End - implications

• Core redesign– System Integrity– Device Tree Overview– Import / Export– Driver internal dpes– Device List Update– All FE libraries

• Implications for the applications?

Other ideas

1. Type of FE: add “family” of PLC– feType = technology,family– Examples:

• S7,S7-300• unPLC,PREMIUM

2. Shall we keep the FE name in the Device dp name?– Alternative: as device attribute (similar approach as

Domain/Nature)– Devices can be moved from one FE to another

3. Devices: Hierarchy of Domains– [fatherDomain:]domain– Example: D1,D1:D2,D1:D3,D3:D4

D1

D2

D3

D4

Alarms panel

• One single panel for JCOP and UNICOS– TabUtilEx.dll– aesuser.ctl– _AESConfig dpl– AlarmPanel.pnl

• Extend UNICOS panel with JCOP functionalities (alarms groups)

• Adopt new PSEN functionalities (multi tab, custom filters...)