1. CIET Generation Process in UAB Technical Committee
CIET: Cryogenics Instrumentation Expert Tool UAB: Unicos Application Builder
Adrien CHIRON
26/11/2012

2. CIET CIET: Cryogenics Instrumentation Expert Tool
An application allowing Cryogenics Instrument Engineers to configure & diagnose their signal conditioners based on in-house rad-tol electronics.

3. Overview UAB CPC plugin UAB CIET plugin Cryo Control
Cryo Configuration
WinCC OA (UNICOS)
(CPC package)
WinCC OA (UNICOS)
(CIET package)
PLC
(UCPC)
IEPLC
FEC (FESA)
WFip
Agent
Agent
Agent
Cryogenics Instrumentation

4. CIET components WinCC OA: CIET package FEC: FESA application IEPLC
UNICOS based
Front-end & Devices
FEC: FESA application
Devices: Classes TT, PT, LT, EH, DI, AGT, SGT and SGTPLC
Format: binary + xml files (instances)
IEPLC
Configuration
PLC files
One Fesa class

5. What is the generator for?
Automatically generate all
Fesa instances
IEPLC files
importation line for PVSS
for one application per spec file definition.

6. INPUT OUTPUTS (…) LTDeviceData.xml PTDeviceData.xml TTDeviceData.xml
Utilities
CIET
UAB Core
LTDeviceData.xml
PTDeviceData.xml
TTDeviceData.xml
IEPLC files
OUTPUTS
PVSS files
(…)

7. Why incorporate the generator in UAB?
Unified approach with CPC (Continuous Process Control).
Benefit from existing UAB framework.
Whole API (java part and python part).

8. Some constraints due to UAB:
With the previous generator, we did not have formalized types (The device types).
The specification header was done by hand but now this header has to be done respecting some UAB requirements.

9. Creation of the spec file header
Generated automatically by a UAB tool called TCT according to the Device Type Definition files
Utilities
TCT
UAB Core
Specification header TT PT LT EH

10. Summary of Complete Process
Preliminary step (once):
Unicos Metamodel
Specification header
Utilities
TCT
UAB Core
EHDevice Type definition
LT Device Type definition
PT Device Type definition
TT Device Type definition TT PT LT EH
Generation step (as many times as specification files):
Fill the
spec
IEPLC files
Outputs TT PT LT EH
Specification
A LD ll 33 true false W
B LD JJ 3 false false W
IEPLC files
Utilities
CIET
UAB Core
WinCC OA
Importation
line OR
LTDeviceData.xml 10

11. Summary of Complete Process
Preliminary step (once):
Fesa Metamodel
Unicos Metamodel
Specification header
XSLT
sheet
Utilities
TCT
UAB Core
EH Fesa
class
EHDevice Type definition LT
Fesa Class
LT Device Type definition
PT Fesa
Class
PT Device Type definition
TT Fesa
Class
TT Device Type definition TT PT LT EH
Generation step (as many times as specification files):
Fill the
spec
IEPLC files
Outputs TT PT LT EH
Specification
A LD ll 33 true false W
B LD JJ 3 false false W
IEPLC files
Utilities
CIET
UAB Core
WinCC OA
Importation
line OR
LTDeviceData.xml 11

12. How I created the Device Type Definition?
Convert Fesa Class for each device to a Device Type Definition compatible with UAB.
Transformation rules in XSLT (and a bit by hand)
Fesa Metamodel
Unicos Metamodel
XSLT
sheet
EH Fesa
class
EHDevice Type definition LT
Fesa Class
LT Device Type definition
PT Fesa
Class
PT Device Type definition
TT Fesa
Class
TT Device Type definition

13. Details, how to respect UNICOS meta-model?
FESA UNICOS
Data-field FEDeviceParameters
Value-item (set) FEDeviceOutputs
Value-item (get) FEDeviceManualRequests

14. Questions