5
Modifications follow-up JIRA cases SVN “at least” items TCT Type XML, Spec XML/XLS, Documents: Functionality, Modifications Modifications document must specify changes in: Specifications Worksheet (To be used for automatic conversion of the existing specs) Functionality Interface The version 4.3.2 is reserved for cases still pending in the unCPC package. From version v5.0 the unCPC package is not anymore backward compatible with precedent versions.

Modifications follow-up

Embed Size (px)

DESCRIPTION

Modifications follow-up. JIRA cases SVN “at least” items TCT Type XML, Spec XML/XLS, Documents: Functionality, Modifications Modifications document must specify changes in: Specifications Worksheet (To be used for automatic conversion of the existing specs) Functionality Interface. - PowerPoint PPT Presentation

Citation preview

Page 1: Modifications follow-up

Modifications follow-up• JIRA cases

• SVN “at least” items– TCT Type XML, Spec XML/XLS, Documents: Functionality, Modifications

• Modifications document must specify changes in:– Specifications Worksheet (To be used for automatic conversion of the existing specs)– Functionality– Interface

The version 4.3.2 is reserved for cases still pending in the unCPC package. From version v5.0 the unCPC package is not anymore backward compatible with precedent versions.

Page 2: Modifications follow-up

Some facts… • Naming

– Interface Objects– I/O Objects– Field Objects– Control Objects (Controller, Alarm, PCO)

• I/O Objects– AI, AIR, AO, AOR treated as different objects (Unification specs Schneider,

Siemens??)

• TCT – attributes: IsShared is deleted– TargetDeviceInformation needed in SIEMENS (Optimized, LimitSize, Offset)– DeviceTechnicals will be declared with the “extended Configuration” (out of

type)– Candidates for Extended Configuration: DIP, CMW, OPC UA, Laser, Logging,

RBAC, Simulation– Simplification of families (next slide):

• FEDeviceCommunication <-> FEDeviceIOConfig• FEDeviceOutput <-> FEDeviceStatus, FEDeviceEnviromentalOutputs

Page 3: Modifications follow-up

UNICOS CPC: TCT definitions

Device

PLCProcess

Output or other objects

Order

Control Logic

Auto Request

Process Variables or

Object status

Process Inputs Manual Requests

Status

Device Configuration

Information to other objects or to operator

via Scada

FEDeviceStatusStsReg01, StsReg01,…

FEDeviceEnvirontmentalOutputsOutOV, OnSt, …

FEDeviceOutputsStsReg01, …,HFOn, HFOff,…

FEDeviceAutoRequestAUInhFMo, AuOnR,…

FEDeviceManualRequestManReg01,MPosR,…

FEDeviceEnviromentalInputsHFOn, HFOff,…

FEDeviceInterlocksStartI, StopI

FEDeviceParametersPliOn, PliOff,…

FEDeviceIOConfigType, Params

Page 4: Modifications follow-up

Some open issues• TCT

– Combo boxes definitions in XML (list of possible values: text oriented)– Attributes order (is it a problem?, is there a solution?)– Comments in XLS/XML are cut off (too small!!!)

• UNICOS CPC types– Archive definition (PVSS): the same as the corresponding IO types– Alarms: Different messages and color for alarms levels L,LL,H,HH

(Analog alarm)

Page 5: Modifications follow-up

UNICOS CPC Types Assignments• Control:

– PCO: JMB– Controller PID: Benjamin– Alarms: AA, DA: Jacques

• Field:– OnOff: Jeronimo– Analog: JMB– AnaDig: JMB– Local: Ph Durand / D. Willeman

• I/O: (with Jacques input of different cases for the I/O)– AI/ AIR: Jeronimo– AO/ AOR: Jeronimo– DI/DO: Ph Durand / D. Willeman

• Interface:– xPar: APAR, DPAR, WPAR: Jacques– xStat: AS, WS: Jacques

• TCT– Borja