Industrial Control Engineering UNICOS distributed control  What does it mean?  Why do we need it  Implication for UNICOS device and tools Hervé Milcent UNICOS distributed controlHervé Milcent1

Industrial Control Engineering Outline  Accelerator context  WinCC OA (PVSS) limitations  Distributed control: unDistributedControl  Where is it used?  unDistributedControl in UNICOS UNICOS distributed controlHervé Milcent2

Industrial Control Engineering Accelerator context  The operators have no WinCC OA knowledge  The developer of a UNICOS application has no or little WinCC OA knowledge, he may not decide on the control architecture  The responsible of the infrastructure has usually (or should have) knowledge on UNICOS principles.  The developer of a UNICOS component has WinCC OA knowledge but sometimes not a deep one. UNICOS distributed controlHervé Milcent3

Industrial Control Engineering Accelerator requirements  A lot of data  more than one WinCC OA projects for a given control application  A lot of front-end  At any time and in all cases the operator must know the validity of the device data  Errors in log files or in central log are useless: the operator are not looking at logs  The operation is from a unique point:  The operators start a UI and have access to all the data of a given control application  The operators do not want to care of WinCC OA system availability.  When a system is off, they must see it in the process view  When a system comes back, they must see the data without reloading views.  The control architecture of a given control application is known since the beginning.  System not declared are discarded and data cannot be accessed.  The UI connects to one system which is connected to all the other systems UNICOS distributed controlHervé Milcent4

Industrial Control Engineering Accelerator requirements  Constraints on viewing data on a remote system 1. The remote system was never connected 2. The remote system is connected 3. The remote system was connected and is disconnected  Case 1. and 3.  data not accessible, action not allowed  Case 2.  data displayed and actions allowed  Transition between all states must be without human actions UNICOS distributed controlHervé Milcent5

Industrial Control Engineering PVSS - WinCC OA: a little bit of history  UNICOS in PVSS was designed in the years 2002 with  First PVSSS 2.11  Upgraded to 3.1  Upgrade to 3.6  Upgraded to 3.8  … and will be upgrade to 3.11  UNICOS was designed since the beginning for control application split in many system  Collaboration with IT/CO was active and IT/CO reviewed the design of PVSS-UNICOS  Since the beginning UNICOS re-used the JCOP framework components and added the missing required functionalities. UNICOS distributed controlHervé Milcent6

Industrial Control Engineering PVSS - WinCC OA limitations  Data views based on dpConnect, action via dpSet  Data are on a local (central system, where is connected the Ui) and on a remote system  From 2.11 to now, dpConnect cannot be done across systems  2.11 & 3.1, case 1. and 3.  dpConnect  error and never reconnect and error in the log  dpSet  error in the log  From 3.6 to now  Case 1.  dpConnect  error and never reconnect and error in the log  dpSet  error in the log  Case 3.  dpConnect  callback triggered only if dpConnect includes invalid bit config and with all data set to 0.  dpSet  error in the log  How to differentiate data set to 0 and disconnection? UNICOS distributed controlHervé Milcent7

Industrial Control Engineering unDistributedControl  Invented in 2.11 to cope with PVSS limitation  Upgraded in 3.6  Used in JCOP trending with a modification to allow dynamic distributed connection  Never added in UNICOS  IS-224  Local script running and checking the state of systems  Result saved in internal data point  Drawback: 2 dpConnect CB for each dpConnect on device data  Based on internal DP:  Configuration  State of the remote system  Compatible with fwInstallation tool definition UNICOS distributed controlHervé Milcent8

Industrial Control Engineering unDistributedControl in UNICOS  Used everywhere in UNICOS  Device: widgets, faceplate, device action  Tools: alarm list, event list, tree device overview, etc.  Except in importing devices UNICOS distributed controlHervé Milcent9

Industrial Control Engineering Device configuration UNICOS distributed controlHervé Milcent10

Industrial Control Engineering UNICOS design requirement  List of systems involved in control application known in advance and their interconnection.  strong constraint, no way to see device from system not declared even if connected  System not connected = alarm  New system mean:  Declare it: only in the system that need to access the remote device with widget/faceplate  Restart the scripts handling the remote connections and the dist manager UNICOS distributed controlHervé Milcent11

Industrial Control Engineering Christmas tree effect UNICOS distributed controlHervé Milcent12 unDistributedControl register  CB Device data CB Connected, dpConnect device data CB Animate data field set all data unknown Disconnected, dpDisconnect device data CB,  Conflict if device data CB uses invalid bits  System state variable used in the device data CB for mutex exclusion done, not secure 