UAB Requirements for 2016 Ivan Prieto Barreiro 18/04/2016 UAB Requirements for

Summary Multi Applications Multi Package TIA Portal Integration Default Values Treatment in Templates Common Parameters in a UCPC Project Migration of Specs File to XLSX Integrate WinCC OA Cli Versioning 2 18/04/2016 UAB Requirements for 2016

Multi Applications (case 1) Multiple UCPC applications in a single PLC (multiple specs) 1. UnicosApplication.xml Allow to store many specs and many applications (modify file structure) Output file names depend on the application name! Impact on reverse engineering tools 2. Generators New parameter to trigger the generation specifying the application Select the appropriate specs file (UAB Core) Get the correct application parameter values (UAB Core) Generated files: Any changes in communication files? Different output folders? 3. Templates No impact: Specs provided by plug-ins, same as application name 4. Wizard Allow the definition of multiple applications (new wizard component, tabs?) PLC Configuration (no changes ?) Plug-in panel: Select the application to generate from a combo box (or generate all) Update the output file names depending on selected application Reload the tables (# of instances, logic templates,..) 5. Upgrade Handle many specs UnicosApplication custom upgrade: Move application parameters (from current structure to new one) Move output files to new structure 3 18/04/2016 UAB Requirements for 2016

Multi Applications (cases 2, 3, 4) Multiple UCPC applications same SCADA DS Share devices between two PLC applications Need more details! Multiple UCPC applications different SCADA DS Definition of different DS IP addresses for each application Link application to SCADA DS (PLC params panel) Templates: The way to get the PLC address will be different! Changes in PLC communication files (?) Multiple specs and common generation for all of them From “ After presenting and discussion on PLC SM it's been decided that multi-spec feature has a limited usage (only SURV/CIET-CRYO projects) and it is not worth to request a generic support of it in UAB. ” 4 18/04/2016 UAB Requirements for 2016

Multi Package (Highest Priority) Allow the selection of CPC libraries from CPC Wizard 1. Different resource packages with independent releases 2. Different resource packages combining them for the CPC release 3. Unique resources package containing all the devices 5 18/04/2016 UAB Requirements for 2016

Multi Package (Highest Priority) Allow the selection of CPC libraries from CPC Wizard 1. Different resource packages with independent releases Easy to merge the different packages (just unzip) Many version numbers for the resource packages Merge spec files from different packages New Bootstrap version Organization of RPs in UAB Registry will be messy Detect package updates Different ‘ResourcePackageConfiguration.xml’ have to be merged (used by the bootstrap to detect the application version) A complete release implies releasing each package individually Impacts OLPROC /04/2016 UAB Requirements for 2016

Multi Package (Highest Priority) Allow the selection of CPC libraries from CPC Wizard 2. Different resource packages combining them for the CPC release Different locations in svn Independent releases A complete release implies releasing the individual packages + the combination of all of them Modify the groupId of the individual packages (bootstrap must not install them!) The creation of the final package implies: Combine all the specs into a single one Merge the SpecDoc worksheet Create a new ResourcesPackageConfiguration.xml with all the device types and all the baselines 7 18/04/2016 UAB Requirements for 2016

Multi Package (Highest Priority) Allow the selection of CPC libraries from CPC Wizard 3. Unique resources package containing all the devices Mark each device with the name of the package (base, motion, …) Unique specs file containing all the devices (remove unselected) ResourcePackageConfiguration.xml (only one) Annotate the package of each device New application: remove unused device type definitions, templates and worksheets All devices/templates in the same place No independent releases 8 18/04/2016 UAB Requirements for 2016

Multi Package (Highest Priority) Allow the selection of CPC libraries from CPC Wizard Bootstrap/Wizard Modify the first panel New param to launch the wizard: -Dpackages=… Device Types New field to specify the package Add the value in the specs sheet meta-data Wizard New parameter to launch the wizard: -Dpackages Create application: Remove unused worksheets Remove unused device type definitions Remove unused templates 9 18/04/2016 UAB Requirements for 2016

Multi Package (Highest Priority) Allow the selection of CPC libraries from CPC Wizard Baselines Will be there several baselines? Remove unused baselines from Baseline folder? Type Builder Modify the meta-model / CPC model to add new field (device package) 10 18/04/2016 UAB Requirements for 2016

TIA Portal Integration Wizard New target platform: TIA Portal Rename others? (Step-7, Schneider) Bootstrap back compatibility! New Bootstrap version (?) Integrate plug-ins & panels in CPC Wizard Define PLC types for TIA Portal (S7-1200… ???) Plug-ins Code Refactoring: Avoid duplications (Siemens / TIA plug-ins) Resources Package New PLC params (TIAPlc) New templates 11 18/04/2016 UAB Requirements for 2016

Default Values Treatment in Templates Device Type Definitions Add the default values for the specification attributes Specs Add a new row for the default values The user can modify the default values UAB Core Modify spec API to return the default value if no value is specified Jython Templates Remove the hardcoded default values 12 18/04/2016 UAB Requirements for 2016

Common parameters in a UCPC Project Wouldn’t the previous case alleviate the situation? New worksheet to put ‘additional’ common values (not coming from the specs) Why not to use a Jython file with constant definitions? 13 18/04/2016 UAB Requirements for 2016

Migration of Spec file to XLSX Specs generation Generate the new specs from the device type definitions Maven plug-in to generate the new specs UAB Core New java classes to handle specs in the new format [under testing] New factory class to create specs Use the factory class to get the specs UAB Core CPC Others … Upgrades New plug-in for FlexExtractor to handle XLSX files Modify FlexExtractor API to use a unique spec upgrade config file Modify the spec file upgrade to handle XML and XLSX files Type Builder Generate XLSX instead of XML 14 18/04/2016 UAB Requirements for 2016

Integrate WinCC OA Cli API? How to use it? Panel options? (create project / install /.. ???) Source code (released version)? 15 18/04/2016 UAB Requirements for 2016

Versioning Feedback? 16 18/04/2016 UAB Requirements for 2016