UAB Versioning: Definition - PowerPoint Presentation

Slide1

UAB Versioning:Definition

02/04/2014

1

Resources Package Split

The resources package will be split into different modules

:

Common/Core (

name to define) module, containing:Device Type DefinitionsSpecs TemplateSemantic RulesIO Commissioning TemplateUpgrade script (?)Modules for each target/technology (Siemens, Schneider, Codesys, WinCC OA, TouchPanel(?) ):BaselineTemplates (Instance, Logic, PLC Parameters)It’s necessary to make a distinction between baseline and templates modules as the wizard will do different actions with them.

2

02/04/2014

Release Definition

A release descriptor will define all the modules

and

targets/ technologies

for the specific release.The descriptor will have the following features:The modules can be grouped by target/technology (e.g.: Siemens, Schneider, WinCC OA(?), Touch Panels(?), …) (PLC Technology?)Each module can be annotated to:Specify the changes since the previous released version. (uab release or module release?)Actions for the user. (Free-text or there are a set of

predefined actions?)

The

Common/Core

(R.P.) and Wizard modules can be annotated to specify if there are changes specific to a target/technology. Is this annotation generic or related to specific changes/actions? (e.g. Change A  Action B  Affects target C )Each PLC platform will describe their different relevant modules (excluding Common/Core and Wizard) (group definition).

3

02/04/2014

Release Definition Example

Common/Core (R.P.) v #:Release affecting

ALL

platforms

Wizard v #:Release affecting SiemensSiemens:Baseline v #Changes: …Actions: …Templates v #Schneider:Baseline v #Templates v #Codesys:Baseline v #Templates v #

4

Siemens

Schneider

CodesysSiemens Baseline v#Schneider Baseline v#CodeSys Baseline v#

Siemens Templates v#Schneider Templates v#

Codesys

Templates

v#

WinCC

OA v#WinCC OA v#WinCC OA v#Touch Panels v#Touch Panels v#Touch Panels v#

Table: Release summary

02/04/2014

Version Numbers

When a new version is released the following situations can occur:The new release is meaningful for all the PLC platforms

The new release is meaningful for a subset of PLC platforms (one or more)

5

SiemensSchneiderReason6.06.0First release

6.1

New Schneider Baseline

6.2

New Siemens Baseline6.36.3New device types

Consequences:

UAB tools will allow the

creation

and

upgrades

of

applications

for the

relevant versions only

. (E.g. Not possible to create/upgrade Siemens applications for CPC v6.1)

When a new release is done a

versions table

(similar to the example) will be created and published in the web for documentation.

02/04/2014

Application UpgradesWhen an application is about to be upgraded:

Only the relevant versions will be offered to the user.A table will be displayed to show the

changes since

the previous release.

6Changes in CPC (Siemens) for v6.26.0First release6.2New BaselineWhen the target version for the upgrade is selected, the tool will show information about the modules changed since the application version.

Upgrade CPC Siemens application

from v6.0 to v6.3

Common

WizardPLC Baseline

Siemens TemplatesWinCC OA

Baseline

WinCC

OA

Templates

Touch PanelBaselineTouch PanelTemplates -

* Table format to be defined* Table format to be defined

02/04/2014

QuestionsWill this release model be applied to all UAB components?

Special cases:TCT: Unique module without other dependencies.

Olproc

++: Uses all versions of CPC R.P. (it could be linked to non-

cpc r.p.)What to do with already released UAB components?Keep they as they are:Bootstrap has to deal with two different kind of releasesThey contain two version numbers (Wizard + R.P.)Redeploy using new versioning mechanism:Deploying only the release descriptor : How to number the already released versions? Wizard displays v1.4.0 and can see r.p. 1.4.0 & 1.4.1

7

CPC

v#

Wizard v#Resources v#1.4.01.4.01.4.0

1.4.11.4.0

1.4.1

02/04/2014