1 / 5

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.

crispin-holley
Télécharger la présentation

Modifications follow-up

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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.0the unCPC package is not anymore backward compatible with precedent versions.

  2. 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

  3. FEDeviceInterlocksStartI, StopI UNICOS CPC: TCT definitions FEDeviceManualRequestManReg01,MPosR,… FEDeviceParametersPliOn, PliOff,… FEDeviceEnviromentalInputsHFOn, HFOff,… FEDeviceIOConfigType, Params FEDeviceAutoRequestAUInhFMo, AuOnR,… Process Variables or Object status Control Logic Process Inputs Manual Requests Auto Request Status Order Device Information to other objects or to operator via Scada Process Output or other objects Device Configuration FEDeviceStatus StsReg01, StsReg01,… FEDeviceOutputsStsReg01, …,HFOn, HFOff,… FEDeviceEnvirontmentalOutputs OutOV, OnSt, … PLC

  4. 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)

  5. 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

More Related