ALSPA Control System Controcad V5.3 Configuration of Data Models Reference Manual

ALSPA Control System
Controcad V5.3
Configuration of Data Models
Reference Manual
ACCESSIBILITY OPERATING & MAINTENANCE MANUAL
DATE 2014-11-14 STAT. CFE - Published
SH/SH
REFERENCE LG REV ENTITY FORMAT NUM SH
END
GFR-020C04010-EDC-201149 en B Power/PAC A4 1/92 92
© ALSTOM 2014 - All rights reserved. We reserve all rights in this document and in the
information contained therein. Reproduction, use or disclosure to third parties without express
authority is strictly forbidden.
TABLE OF CONTENTS
Section 1 Introduction ............................................................................................................ 4

1.1 Purpose of the Document ......................................................................................................................... 4
1.2 Important Information ............................................................................................................................... 4
1.3 Notice to Reader....................................................................................................................................... 5
1.4 Risks & Protection .................................................................................................................................... 6
1.5 Standards & Codes .................................................................................................................................. 6
1.6 Glossary ................................................................................................................................................... 7
1.7 List of Referenced Documents ................................................................................................................. 9
Section 2 Description of the Library Tree ........................................................................... 10
Section 3 Project ................................................................................................................... 12
3.1 Project Contextual Menu ........................................................................................................................12
3.2 Searching for Elements ..........................................................................................................................13
3.2.1 Element found ...................................................................................................................................14
3.2.2 Element not found .............................................................................................................................14
3.3 Exporting Libraries..................................................................................................................................15
3.4 Importing Libraries ..................................................................................................................................15
3.5 Issuing Library Elements ........................................................................................................................15
3.6 Extracting Library Elements ...................................................................................................................16
3.7 Configuring IEC61850 Logical Node Types ...........................................................................................18
Section 4 Libraries ................................................................................................................ 20
4.1 Creating a Library ...................................................................................................................................20
4.2 Library Contextual Menu ........................................................................................................................21
4.3 Library Properties ...................................................................................................................................22
Section 5 Library Elements .................................................................................................. 23
5.1 Description ..............................................................................................................................................23
5.2 Functional Blocks ...................................................................................................................................23
5.2.1 Description ........................................................................................................................................23
5.2.2 Creating a Functional Block ..............................................................................................................24
5.2.3 Functional Block contextual menu ....................................................................................................25
5.2.4 Functional Block properties ...............................................................................................................27
5.2.5 Cross References..............................................................................................................................33
5.2.6 Raw code of the element ..................................................................................................................34
5.2.7 Features of FB diagrams ...................................................................................................................34
5.2.8 Particularity of the Transformation Schematic FB / Standard FB .....................................................35
5.2.9 FBs Transformed into BFs ................................................................................................................36
5.2.10 Selection Window of the Argument Type ..........................................................................................37
5.3 High Functional Blocks ...........................................................................................................................38
5.3.1 Description ........................................................................................................................................38
5.3.2 Creating a High Functional Block ......................................................................................................39
5.3.3 High Functional Block contextual menu ............................................................................................40
5.3.4 High Functional Block properties ......................................................................................................41
5.3.5 Cross References..............................................................................................................................44
© ALSTOM 2014 - All rights reserved. We reserve all rights in this document and in the information contained therein. Reproduction, use or disclosure to third parties without express authority is strictly forbidden.
ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

Configuration of Data Models - Reference Manual 2/92
5.4 Objects Models .......................................................................................................................................45
5.4.1 Creating an Object Model .................................................................................................................45
5.4.2 Contextual Menu of an Object Model ................................................................................................46
5.4.3 Object Model Properties ....................................................................................................................48
5.4.4 List of the consumptions of a model..................................................................................................54
5.5 Variable Models ......................................................................................................................................54
5.5.1 Description ........................................................................................................................................54
5.5.2 Single Variable Models......................................................................................................................55
5.5.3 Multiple Variable Models ...................................................................................................................61
5.5.4 Variable Validants and Sensor Faults ...............................................................................................72
5.5.5 Internal Variables ..............................................................................................................................78
5.5.6 Configuration Variables .....................................................................................................................80
Section 6 Basic Function Editor .......................................................................................... 81
6.1 Introduction .............................................................................................................................................81
6.2 Menu Bar ................................................................................................................................................82
6.2.1 Menu File ...........................................................................................................................................82
6.2.2 Edit Menu ..........................................................................................................................................84
6.2.3 Insert Menu .......................................................................................................................................84
6.3 Tree ........................................................................................................................................................85
6.4 Tabs ........................................................................................................................................................86
6.4.1 Library Tabs ......................................................................................................................................86
6.4.2 BF Tabs .............................................................................................................................................87
6.5 Installing a Library ..................................................................................................................................88
6.5.1 Checks ..............................................................................................................................................88
6.5.2 Installation .........................................................................................................................................89
6.5.3 Modifications .....................................................................................................................................90
Section 7 Controcad Terminology for Variable Exchange Families .................................. 91

Section 1 Introduction
1.1 Purpose of the Document
This manual describes the elements of the Library tree structure (Lib tab of
Controcad).
It is made for the engineering and commissioning teams. It is part of the Operating &
Maintenance Manuals (OMM) and can be used by the maintenance team on site.
This manual is applicable to Controcad version 5.3.
1.2 Important Information
Alstom Power is committed to high quality products in compliance with

our high standards of quality.
Users and installation staff who operate on the equipment are qualified
and trained.
Before performing any action on the equipment, you must read and
understand the Operating and Maintenance Manual.
To reduce risks for yourself and your equipment, only an accredited
technician shall service your equipment or work inside it.
Alstom is committed to top customer assistance services.

If you need further information or encounter a serious problem, please
contact:
Alstom Power
Automation & Control - Customer Support
Hardware repair
Annual preventive maintenance
Telephone, e-mail, fax, remote maintenance, Web facilities
On site intervention
Software maintenance
Training session for commissioning engineers and customer users.
Contact: helpdesk.control-systems@power.alstom.com

1.3 Notice to Reader
DANGER
Indicates a situation of imminent danger which, if it is not avoided, will

lead to death or serious injury. This indication is restricted to the most
extreme circumstances.
WARNING
Indicates a potentially dangerous situation, which if it is not avoided will

lead to death or serious injury.
CAUTION
Indicates a potentially dangerous situation which, if it is not avoided, may

cause minor or moderate injuries. This indication may also be used to
warn against unsafe practices.
ELECTRICAL WARNING
Indicates a potential electrical danger related to voltages, currents,

temperature, or other conditions that may cause an electric shock or burn.
Turn off and disconnect any electrical power supply before servicing.
Highlights instructions or other important information which must be

strictly respected.
Points out important information.
Refers to a document.
Refers to a Medium.
This document is based on information available at the time of its publication. While efforts have been
made to be accurate, the information contained herein does not purport to cover all details or variations
in hardware or software, nor to provide for every possible contingency in connection with installation,
operation, or maintenance.
Features may be described herein which are not present in all systems. Alstom assumes no obligation
of notice to holders of this document with respect to changes subsequently made.
In this publication, no mention is made of rights with respect to trademarks or trade names that may
attach to certain words or signs. The absence of such mention, however, in no way implies there is no
protection.
Partial reproduction of this document is authorized, but limited to internal use, for information only and
for no commercial purpose. However, such authorization is granted only on the express condition that
any partial copy of the document bears a mention of its property, including the copyright statement.
ALSTOM, the ALSTOM logo and any alternative version thereof are trademarks and service marks of
ALSTOM. The other names mentioned, registered or not, are the property of their respective
companies.

1.4 Risks & Protection
ELECTRICAL WARNING
ELECTRICAL PROTECTION
The equipment presents dangers to the personnel and to the equipment

itself. These dangers are mainly electrical in nature, such as:
electric shock
transient increases and decreases in electrical power
electrostatic discharge
Working inside the equipment may have an impact on the physical integrity
of the person or the equipment itself.
During installation, the equipment must be powered down.
 Shut down properly your equipment and power it off before hardware
installation.
CAUTION
RADIO FREQUENCY INTERFERENCE
Most electronic equipment is affected by radio frequency interference

(RFI). Caution should be taken when using mobile communications
equipment near such equipment. Signs are on display near to the
equipment to warn against the use of mobile communications equipment.
CAUTION
STATIC SENSITIVE DEVICES
ALSPA system equipment contains components sensitive to electrostatic

discharges which can be damaged as a result of incorrect handling.
Working procedures (e.g. extracting a module) are described in the
manufacturer's documentation and must be followed. Equipment is fitted
with labels so that staff can take anti-static precautions during handling.
1.5 Standards & Codes
The ALSPA control system equipment has been developed, manufactured and
tested to comply with the relevant standards.
All these standards are indicated in the following document
[STD&COD] - ALSPA Series 6 - Standards and Codes - refer to the
documents list of the project.
In order to achieve optimum operation of the equipment you must always keep in
mind that the standards should be complied with.

The above-mentioned document details the certification and the operating and
electromagnetic environment in which your equipment must be used.
1.6 Glossary
ALSPA Series 6 Distributed Control System (DCS) of Alstom Power.

ALSPA OPTIPLANT Plant Optimization Solutions. OPTIPLANT applications can be
added to the DCS in order to manage the performances, the
maintenance and the scheduling of the plant.
ALSPA HMI Architecture, equipment and control room workstations. Also
refers to the control room software functions.
ALSPA Controcad Engineering and commissioning tool of the ALSPA Control
System. With this tool, engineers can configure the ALSPA
System for the plant, download the controllers and tune and
maintain the system.
ALSPA Automation Automation level of the ALSPA system. It is constituted of
Cell master controllers, I/O, field controllers and field networks.
C10 Local ALSPA HMI station which manages the Real Time server
function and the HMI functions.
C30 ALSPA HMI provided with several separated stations
comprising multi-screen operator stations, Real Time and
Historian servers.
CE1000 / CE1500 / Inputs/outputs and field controllers of the ALSPA System.
CE2000 / CE3000
CE3500 Safety This kind of controllers ensures the safety functions IEC61508
Controller SIL2 & SIL3 level.
HMI Gateway or ALSPA HMI Gateway type CSS-G offers a panel of
CSS-G communication protocols between the ALSPA HMI and third
party systems. The CSS-G is often seen as data
server/controlled part.
Automation Cell ALSPA Automation Cell Gateway type CSS-F offers a panel of
Gateway or CSS-F communication protocols at the controller level with third party
systems. The CSS-F is often seen as client/controlling part.
Data Attribute (DA) In the IEC61850 standard, a Data Object consists of several
Data Attributes. Data Attributes define the name (semantic),
format, range of possible values and representation of values
while being communicated.
Data Object (DO) In the IEC61850 standard, Data Objects represent the data
exchanged between Logical Nodes. From an object-oriented
point of view, a data object is an instance of a data class.
Ethernet Enterprise ALSPA Enterprise bus. It connects the ALSPA HMI stations
bus together for maintenance purposes or non-critical function. It
can connect third party functions.
Ethernet process ALSPA Ethernet network connecting all the cell controllers of a

Bus or S8000 plant unit together with the ALSPA HMI. This network is based
on Ethernet technology. It is also named S8000.
Field Bus or E8000 Network which connects the master controllers to the field
controllers based on Ethernet Powerlink technology. It is also
named E8000.
Historian Function for long term history of the events and measurements
of the plant. This function comprises data servers and HMI
viewers.
IMS Information Management System of ALSPA HMI. It provides
statistics computation and reports generation. This function
includes data servers, report generator and report viewers.
I/O Controller These controllers manage the inputs and outputs coming from
Field Controller the sensors and devices of the plant. It can be placed near the
devices and be remote from the main controller.
Logical Node (LN) In the IEC61850 standard, all the functions of a system are
decomposed into Logical Nodes which may reside in one or
more physical devices. A Logical Node represents an indivisible
part of a function that exchanges data. It is defined by its data
and methods.
Master Controller Main controller of the automation cell. It executes application
or Cell Controller software with the data coming from the I/O controllers and
controls the process by sending orders.
MFC3000 / Master controllers of the ALSPA system.
MFC1000
OMM Operating & Maintenance Manual.
OS or CVS Operator stations which supports the operating HMI functions of
ALSPA HMI.
RTDS or CIS Real Time Data Server: this function of ALSPA HMI manages in
real time the process data coming from the plant. The RTDS
function uses the OPC function to exchange data with the OS
and third party applications.
The RTDS function communicates with the automation cell
through the process bus.
Notation for Signals used in ALSPA Control System.

cASig Controller analog signal
ihASig Internal HMI analog signal
ohASig Operator parameter HMI analog signal
phASig Program HMI analog signal
cBSig Controller boolean signal
ihBSig Internal HMI boolean signal
shBSig System HMI boolean signal
phBSig Program HMI boolean signal

dhBSig Controller default boolean signal
cMSig Controller multi-state signal
ihMSig Internal HMI multi-state signal
phMSig Program HMI multi-state signal
ccCmd Controller Command
ihCmd Internal HMI Command
ccSPt Controller setpoint
ihSPt Internal HMI setpoint
1.7 List of Referenced Documents
[CCAD_INTRO] Refer to the Operating and Maintenance Manuals of

the project for ALSPA Controcad Introduction.
[CCAD_HARD] Refer to the Operating and Maintenance Manuals of
the project for ALSPA Controcad Hardware
Architecture Configuration.
[CCAD_FUNCT] Refer to the Operating and Maintenance Manuals of
the project for ALSPA Controcad Applications & Data
Configuration.
[CCAD_VIEW] Refer to the Operating and Maintenance Manuals of
the project for ALSPA Controcad Mimic Views
Configuration.
[CCAD_IEC61850] Refer to the Operating and Maintenance Manuals of
the project for ALSPA Controcad CSS-F IEC 61850
Gateway Configuration.
[CCAD_CE61850] Refer to the Operating and Maintenance Manuals of
the project for ALSPA Controcad IEC61850 for ALSPA
CE1500.

Section 2 Description of the Library Tree
The Library tree is accessed via the tab of Controcad.

It serves several purposes:
to define the project data and processing models including:
- the SVMs and MVMs for the variables
- the functional and high functional blocks for the diagrams
- the configuration variables, associated to the controllers, necessary for
operation of the ALSPA system
to organize the project models
to position components (functional blocks and operators) in the diagram editor.
A library contains a set of application data models. This set is either:

supplied by Controcad
The library is generated from the Controcad reference data. It can be modified for
special project adaptations by an Administration level user. The «System» name
is shown in bold characters in the tree. In the rest of this document, this library
type will be designated as System Library. It contains all the models associated
to the ALSPA System and to the standard Control & Supervision activities.
produced specifically for the project:
These libraries are developed for the specific needs of the project by a
Configuration level user. This library type will be designated as Project library in
the rest of the document
These libraries will include Business Libraries specific to the different types of
control & supervision (thermal, hydro, rotating machine control etc.), which are
the responsibility of the Design Office.
A library can be divided into several sub-libraries, which are themselves organized
as libraries. This hierarchical division is used to organize the models in order to
facilitate searches for models among the different sets.
The name of a sub-library is unique in the library to which it is affiliated. However,
the name of a model is unique in the project.
The content of a library is classed by model type, the models themselves being
classed in alphabetical order. An icon is associated to the libraries and to each
model type in the tree. For the models, an additional icon indicates the state:
Masked or Extracted. A model in one of these two states is not visible in the tree
(and is therefore inaccessible) for users with a level inferior to the Configuration
level.

The following sections detail the functions provided by the libraries via the
contextual menus associated to each element of the tree.

Section 3 Project
3.1 Project Contextual Menu
The following contextual menu is associated to the Project element in the Libraries
tree:
Description of the options:

Option Description
New (Ctrl N) Creates a library in the project (cf. 4.1,Creating a Library).
Find (Ctrl F) Opens a window to find Functional Blocks, SVMs, MVMs
and object models elements (cf. 3.2,Searching for
Elements).
Refresh (F5) Updates the Libraries tree.
Library Export... Used to export libraries from the current project (cf.
3.3,Exporting Libraries).
Library Import... Used to import libraries from the current project (cf.
3.4,Importing Libraries).
IEC61850 MVM For projects with a CSS-F IEC61850 gateway.
Configure ...
This item is used to import in a Controcad library the SCD
file containing the IEC61850 network architecture
description. See [CCAD_IEC61850] for more information in
1.7 List of Referenced Documents.
IEC61850 Logical For projects with CE1500 controllers configured on a
Node Types IEC61850 network.
Configure ...
This item opens the window used to create a MVM
IEC61850 library representing the Logical Nodes (cf.
3.7,Configuring IEC61850 Logical Node Types).

Option Description
Issue Library Opens the window used to issue the different elements of
Elements the project (cf. 3.5,Issuing Library Elements).
Extract Library Opens the window used to extract the different elements of
Elements the project (cf. 3.6,Extracting Library Elements).
Draw Out Extracts the Libraries tree to a new window. This window
can be iconified, resized and displayed in all the main
Controcad windows. This mechanism is used to provide
permanent access to the Libraries tree and thus to enable
navigation in the models while another tree is active.
3.2 Searching for Elements
Click the Find option to open the following window:
Description of the fields:

Ty Name Description
pe
Search String Name of the element sought.
The character * can be used to replace a character
string.
In Functional Block Search in Functional Blocks.
In SVM Search in SVMs.
In MVM Search in MVMs.
In Object Model Search in Object Models.
Description of the buttons:
The OK button starts the search operation: the window closes and is replaced by
another window showing the result of the search.
The Cancel button is used to quit the search function.
The Help button is used to obtain contextual help for this screen.

3.2.1 Element found
When the result of the search is successful, a window opens to display a list of the
library elements found which contain the string.

Type Name Description
Location Indicates the library element that contains the
relevant character string. The element is identified
by an icon that defines its type, its name and its
complete path in the library tree.
The Close button is used to close the result window.
3.2.2 Element not found
When the search is unsuccessful, a dialogue box opens to show that no data was
found. This dialogue box is closed by clicking on the OK button.

3.3 Exporting Libraries
Click the Library Export... option to open the FEFS library export screen. The user
can then choose a list of the libraries to be exported, the directory in which the data
will be placed and whether or not the data should be archived.
3.4 Importing Libraries
Click the Library Import... option to open the FEFS library export screen. The user can
then choose a list of the libraries to be exported, the directory in which the data will
be placed and whether or not the data should be archived. These are imported into
the tree below the Project element.
3.5 Issuing Library Elements
Clicking the Issue Library Elements option opens the following window:
This window displays all the elements of the project that are in an issued state and
that can be used to issue the elements chosen by the user.

Library Path of the library owning the element.
Type Icon representing the type of the element.
Component Name of the element.
To Issue Defines the elements to be issued.
Is Issued Indicates the elements that have been issued since
the opening of the window.

The All button is used to select all the elements in the window.
The button is used to select all the Object Models in the window.
The button is used to select all the Functional Blocks in the window.
The button is used to select all the Multiple Variable Models in the window.
The button is used to select all the Simple Variable Models in the window.
The None button is used to deselect all the elements in the window.
The Invert button is used to invert the state of selection of all the elements.
The Issue button is used to issue the elements selected.
The Exit button is used to close the window.
3.6 Extracting Library Elements
Clicking the Extract Library Elements option opens the following window:
This window displays all the elements of the project, or of the library selected, that
can be extracted.
Library Path of the library owning the element.
Type Icon representing the type of the element.
Component Name of the element.

To Extract Allows selecting the elements to be extracted.
Is Extracted Indicates the elements that have already been
extracted.

The All button is used to select all the elements in the window.
The button is used to select all the Object Models in the window.
The button is used to select all the Functional Blocks in the window.
The button is used to select all the Multiple Variable Models in the window.
The button is used to select all the Simple Variable Models in the window.
The None button is used to deselect all the elements in the window.
The Invert button is used to invert the state of selection of all the elements.
The Extract button is used to extract the elements selected.
The Exit button is used to close the window.

3.7 Configuring IEC61850 Logical Node Types
Clicking on the IEC61850 Logical Node Types Configure ... option opens the following
window:
This window is used for IEC61850 data modelling which is the first step in the
configuration of the IEC61850 function on ALSPA CE1500 controllers.
The user can create and configure the IEC61850 data types which will then be
mapped into Controcad MVM, SVM and SVM attributes.
For more information about IEC61850 data modelling, see
[CCAD_CE61850] in 1.7 List of Referenced Documents.
The window includes a tree view and a properties table.

Description of the tree view:
The data types are created and explored in the tree view. The user has to define
only the Logical Node (LN) types. Data Objects (DO) and Data Attributes (DA) types
are automatically generated by the tool.
Description of the properties table:
The properties table displays the properties of the selected data type. Some of them
can be modified.

The Import button is used to import in Controcad the models created. All the
IEC61850 data types will be converted to MVM, SVM and SVM attributes.
The Close button is used to close the window.

Section 4 Libraries
4.1 Creating a Library
Click the New option from the contextual menu associated to the Project element to
open the following window:
Click the New option from the contextual menu associated to the Library elements to

The library is created in the tree below the element from which the creation has
been requested.

Typ Name Description
e
Library Creation of a library. Checked by default.
Element of Dropdown list that allow the creation of different library
Library elements listed in the list (Functional Block/ High Functional
Block/SVM/ MVM/ Model of Object)
Note: This dropdown menu does not appear when the
creation is requested via the contextual menu of the project.
Name Name of the library
Label Label of the library
Version Version number of the library

The OK button confirms the user's choice and creates the new library.
The Cancel button is used to abort the input and quit the function.
4.2 Library Contextual Menu
The following contextual menu is associated to the Library element in the Libraries
tree:

Option Description
Properties Opens the library properties window (cf. 4.3,Library
Properties).
New (Ctrl+N) Creates a library (cf. 4.1,Creating a Library) or library
elements (Functional Blocks /SVMs / MVMs / Model of
Objects)
Delete Deletes the library. If elements in the library are currently in
use, the user is informed and the deletion option is disabled.
Paste (Ctrl+V) Used to paste a library element (FB, MVM or SVM) in the
selected library. An element must first be Cut for this option to
be valid.
Find (Ctrl+F) Option unavailable at this level. Available only at Project
level.
Library Export... Opens the project library export window.
Library Import... Opens the project library import window.
Extract Library Opens the window used to extract the elements of the library
Elements selected (cf. 3.6,Extracting Library Elements).
Variables Models Displays the variable models associated to the library in the
variable grid.
SVM Displays the SVMs.
MVM Displays the MVMs.
Edit Linked Used to configure links with a document. The document type
Document may vary (.doc, .mpg, .html, URL etc.).
Display Linked Used to display linked documents.
Document
4.3 Library Properties
The Properties window of a library is similar to the New library window (cf. 4.1,Creating
a Library).
If the user is logged on as Administrator, an additional field is shown:
Protection: This field indicates whether or not the library is protected, (Yes) or
(No).
If a library is protected:
The System name is shown in bold characters in the tree.
The New, Delete and Paste options in the contextual menu are no longer available,
The elements of the library cannot be modified.
Note : Library protection extends across the entire library tree. For example, if the library is
protected at the project root level, all the elements, FBs, MVs and libraries located below
this level will be protected. Deprotection also extends in the same manner.

Section 5 Library Elements
5.1 Description
A library element is a variable or processing model. It is affiliated to only one library

and has a unique name in the project.
There are four types of historical data:
Functional Blocks (FB).
High Functional Blocks (HFB).
Objects models.
Variable exchanges.
An element may be in one of the following three states:
Current: the element can be used in the project.
Extracted: the element is being modified.
Masked: the element cannot be used directly in the project.
5.2 Functional Blocks
5.2.1 Description
There are 3 types of FB:

Icon Variable Types
FB whose code is written in LEA.

FB whose code is described by means of a
FBD diagram.
FB transformed into BF (Basic Function).
In the tree, a green LED is displayed to the left of icons with valid models. A red
signal light is displayed beside icons with invalid models. This indicator concerns
all the FBs, with the exception of the operators ( ) that cannot be modified.

5.2.2 Creating a Functional Block
Click the New option associated to the contextual menu of a library to open the
following window:

Element of Library Selecting 'Functional Block' from the list enables
creation of a new functional block.
Name Name of the functional block.
Label Label of the functional block.
Author Author of the functional block. By default, the author is
the current user.

The OK button confirms the user's choice and creates the new FB.
By default, the Functional Block created is a standard FB in issued state. The
diagram is created in the tree below the function from which the creation has been
requested. The user can then modify the type and define the content of the
functional block (cf. 5.2.4,Functional Block properties).

5.2.3 Functional Block contextual menu
The following contextual menu is associated to a functional block:

Icons in the Options column indicate the types of Functional Blocks for which the
option is available.
Option Description
Properties Opens the functional block properties window (cf.
5.2.4,Functional Block properties).
If the element is in extracted state, the definition of the
functional block can be modified.
Delete Deletes the Functional Block.

Option not available if the element is issued or hidden.
Cut Cuts the element. The icon of the element cut appears in gray
(for example: becomes ).

Option Description
Paste Pastes the element previously cut.
Find Option in grey (available only at project level).

Issue Used to switch the element of issued state to current state.
The modifications made to the issued element are
implemented when the Issue command is executed;
modifications are applied in all the diagrams consuming the
element.
Extract Used to switch the element from current state to issued state.
For example, a current FB shown as , switches to
extracted state .
The version number of the element is incremented
automatically. In the extract state, the modifications to the
element are authorized without disturbing the variables using
this element.
Cancel Cancels the extraction of the element. The current state of
the element is not modified. The version number switches
back to that of the current state. If the element has no current
state, the element is deleted.
Hide Used to hide the element. Depending on the user's access
level, either the element does not appear in the tree, or it
appears with the icon to its left.
This function enables a configuration level user to hide
elements of library invisible to prevent their being used in the
project.
Option not available if the element is issued.
Show Used to unmask the element.
Select Component Used to select the component to be placed in a diagram

opened in the diagram editor.
Option not available on an issued element.
Variable Models > Displays the internal variables associated to the element in
Internal Variables the variable grid (cf. 5.5.5,Internal Variables).

Option Description
Edit Linked Used to configure links with a document; the document type
Documents may vary (.doc, .mpg, .html, URL etc.).

Documents
Cross References Used to display the consumption of the element in the

diagrams (cf. 5.2.5,Cross References).
Open Diagram Opens the diagram in read/write mode if the element is

issued or in read only mode if the element is current (cf.
5.2.7,Features of FB diagrams).
Code Used to display the raw code of the element and identify any
errors(cf. 5.2.6,Raw code of the element).
Create BF from FB Transforms an FB into a BF (Basic Function) (cf. 5.2.9,FBs
Transformed into BFs). For example: becomes ).
Cancel BF creation Cancels the transformation of an FB into a BF. (cf. 5.2.9,FBs
Transformed into BFs).
Option available only for FBs transformed into BFs.
The following rules must be observed to enable project (or part project)
imports/exports to manage associated file type documents fully.
Files to be associated to library elements must be located on the server in
the following tree in the project directory (xxxlog):
\\< UNC name server>\P320Share\Ccad\<xxxlog>\docuser\Lib
The association must be executed using the UNC name of the server.
5.2.4 Functional Block properties
The properties window of a Functional Block is accessible in modification if it is

opened from an issued element. If the window is opened from a current element, all
the fields of the window are shown in grey: there is no modification possible.

This window is composed of a header and three tabs.
5.2.4.1 Header and "Arguments" Tab
Select the Properties option or double click the issued element to open the following
window:

Header
Name Indicates the name of the Functional Block.
Type Defines the Functional Block type: LEA (standard FB) or
FBD (schematic FB).
For the consequences of changing the type please refer to
section on transformation of schematic FB /standard FB. (cf.
5.2.8,Particularity of the Transformation Schematic FB /
Standard FB)
Sequence Indicates whether the Functional Block is used as a
sequence header or as a sequence step during sequence
monitoring.
Label Indicates the label of the Functional Block Model.
Author Indicates the name of the author of the Functional Block
Model.
Component Used to input the instance of the Functional Block model in
instance the diagrams.
variable type
Indicates the type or the model of the variable that must be
used for the name of the Functional Block when it is

positioned. The instance of the Functional Block will be
identified by the process ID of the selected variable.
Validity Indicates the validity of the Functional Block. The validity is
produced when the user clicks on the Apply or OK buttons. It
is the result of a set of consistency checks on the definition
of the model. If the value of the indicator is Yes, the model
can be issued, i.e. it can be consumed in the project in its
new version.
Width (FBD Used to re-dimension the width of an FB. By default, the
grid square) value is equal to the minimum width which is 6 grid units in
a diagram. This value can be modified by step of 0.5 grid
units. The width can automatically vary according to the
arguments location.
The Arguments tab (inputs, outputs) defines the arguments of the functional block:
Nb. Order number of the argument in the code that will be
generated for the functional block.
Name Name of the argument. The name will be used in the code
generated for the functional block.
Display Display name of the argument when the functional block is
Name positioned in a diagram. If this field is not input, NAME is
used.
Basic Types Defines the basic models of the argument (Boolean, double,
duration, integer, long, real, word etc.). The field is input via
the List of Types… option in the associated contextual menu
(cf. 5.2.10,Selection Window of the Argument Type). The List
of Types… option is made available when the mouse is
positioned on the relevant element in the Basic Type column.
The user chooses the basic models authorized for the
argument, which means that when the functional block is
placed in a diagram, only those variables with these basic
models can be assigned to the argument.
Length Sets the size of the table for a argument accepting table
variables.
Label Label of the argument.
Sense Indicates if the argument is an input or an output of the
Functional Block.
Side Defines the location of the argument in the graphic
representation of the functional block (Top, Bottom, Left or
Right).
Graphic Defines the graphic position of the argument relative to the
position SIDE chosen.
Default Sets a default value for the argument when it is not
value associated to a variable, a link or a literal value in a diagram.

This field is significant if the argument is an input.
Mandatory When this field is checked, the argument must be assigned
Connection to a variable, a literal value or an expression (operator
output). If the MANDATORY DATA field is also checked, the
argument must only be assigned to a variable or a literal
value.
Mandatory When the field is checked, an assigned argument must be
Data assigned to a variable or a literal value. In the diagram
editor, the argument is displayed in red.
Negation The argument can be complemented in a diagram.
Supported
Sequence Defines the sequence monitoring criteria.
Criteria
Control Creates a link from the control block to the argument. Any
Block Link variable assigned in a diagram will automatically be attached
to the control block created.
Tuned Value Sets a default value for the initial tuned value in the diagram.
Tuned Level Indicates a tuning authorization level.
Modifying the name of a FB argument used in diagrams deletes the

assignment of variables linked to this argument.
To avoid reassigning these variables, it is preferable to modify the
argument display name whether than the name used by the code.
This Arguments tab is used to define the FB arguments. In this tab, the
following contextual menu accessible by a right-click in the tab zone can be used to
create an argument:

5.2.4.2 "Codes" Tab
Clicking on the Codes tab opens the following window:
This tab is used to input the functional block model code. The programming
language used is Controcad LEA language. In the code, internal variables are
identified in the functional block model by their names (Name field in the variable
grid).
The code can be imported from a file and saved in a file (Load from file and Store to
file buttons). These files are .txt files.
When the user clicks on the Apply or OK buttons the code is checked syntactically
relative to LEA language and semantically relative to the arguments of the model.
Errors detected are displayed in a window that also shows the number of the code
lines concerned.
If the Functional Block is described diagrammatically (FBD type), the code zone is
locked and cannot be modified.
Note : If Author of Functional Block is 'SYSTEM', then code zone cannot be modified.

5.2.4.3 "Arguments Group" Tab
Click the Arguments Group tab to open the following window:
This tab is used to associate MVMs to the functional block model and assign each of
the fields of these MVMs to the arguments.
Name of Argument Name of the argument group
Group
MVM defining the Name of the MVM associated to the argument
Argument Group group.
Argument Name Name of the component argument.
MVM Field Path Name of the MVM field associated to the
argument. The fields proposed in the list are the
fields that are compatible with the argument type.
A contextual menu is available in the tab window to:
create, delete, copy and paste a new argument group in the “List of arguments
groups” section.
create, delete, copy and paste a new field used to associate a component
argument to an MVM field in the “Mapping between component arguments and
MVM field” section.
The OK button confirms the user's choice and closes the window.
The Apply button confirms the user's choice without closing the window.
The Help button displays contextual help for the current window.

5.2.5 Cross References
Select the Cross References option from the contextual menu associated to a
Functional Block to open the following window:
The Functional Diagrams tab displays the consumption of the selected element in all
the functional tree diagrams.
The Workspace Diagrams tab displays the consumption of the selected element in the
diagrams used in the last code generation.
The OK button closes the window.

5.2.6 Raw code of the element
Click the Code option to open the following window:
This screen is used to identify errors in the raw code of the element.
Line Number of the line of code
Error Indicates the number of errors in the line of code
Code Line of code
The Save as… button is used to save the screen in the form of a file (several
formats are proposed: text, Excel, html, etc).
The Close button closes the window.
5.2.7 Features of FB diagrams
A FB diagram is described by means of an FBD. A diagrammatically described

component is defined in the same way as the other components (standard FBs):
Its general parameters (names, variables of instance, FB type etc.) and argument
groups are defined by the component definition screen accessible from the
Properties option in the contextual menu associated to the extracted functional
block.

Its input/output arguments are also defined by the component definition screen
and may have the same characteristics as the parameters of an LEA component.
Two points must be specified:
A non-mandatory argument can only be used if it is assigned to a non-mandatory
FB argument placed in the diagram.
An array type argument can only be assigned to an FB argument that is itself an
array type argument of the same length.
Its internal variables (private or shared) are defined by the variable grid of the
component accessible from the Variables Models > Internal Variables option in the
contextual menu associated to the functional block.
The component diagram can only be created or the modified if the component is
issued. Select the Open Diagram option in the contextual menu associated to a FB
diagram to open its diagram in the FBD editor. Only the internal variables of the
component and the input/output arguments provided for the component can be
assigned.
The input/output arguments (defined from the component definition screen) are
displayed in the diagram by means of slots. In order to differentiate analog type
arguments from logic type arguments, the outline of the slots of the analog
arguments is thicker than that of the logic arguments.
Icon Description
Slot corresponds to an analog input argument.

Slot corresponds to an analog output argument.
Slot corresponds to a logic input argument.
Slot corresponds to a logic output argument.
It is possible to duplicate the input slots of a schematic FB. This action can be
performed thanks to the contextual menu accessible by right-clicking the input slot.
This menu cuts, pastes and deletes an input slot.
Duplicated input slots are presented with a blue background.
Example of duplicated slots: or
The FBD is translated into LEA code each time the component diagram is saved.
The code can be displayed from the cell properties window of the FB but cannot be
modified.
5.2.8 Particularity of the Transformation Schematic FB / Standard FB
It is possible to transform an FB diagram into a standard FB and vice versa. This

action can only be performed on an issued component.
The transformation of a standard FB into a FB diagram results in a loss of the
component code.
The transformation of an FB diagram into a standard FB results in a loss of the
descriptive diagram and its code.

5.2.9 FBs Transformed into BFs
FBs are transformed into BFs (Basic Functions) in order to reduce the size of the
code generated when a large FB is accessed several times within a single program.
This transformation is applicable to all types of FB (LEA or FBD).
The functionality of BFs is inferior to that of FBs, so certain FBs cannot be translated
into BFs. The following functionalities are missing:
#IF instruction using the variable $TARGET_TARGET,
#IF instruction testing the connection of an argument,
#EVAL instruction,
Transport validant test,
Utilization of library variables.
Select the Create BF from FB option from the contextual menu associated to an FB to
transform an FB into a BF.
To make the transformation of a FB into a BF possible, the input/output argument of
a FB has to be of one type.
If the FB is of FBD type, it will become an LEA type after transformation: graphic
data, although now inaccessible, is not deleted in order to permit backtracking.
If the FB is of LEA type a line of code containing the call to the BF is inserted and
the old FB code is placed as a comment, also to permit backtracking.
After the transformation of the FB into a BF, the BF must be saved in an .fbl file:
the inputs of the BF then correspond to the inputs of the FB,
the outputs of the BF then correspond to the outputs of the FB and to all the
internal variables of the FB.
It is not possible to modify or delete in the BF editor, BFs produced from an FB
transformation. These BFs are identifiable by having names starting with
CCAD_BF_.
The transformed FB becomes a BF type in the Properties window of the component.
Select the Cancel BF creation option from the contextual menu associated to an FB
transformed into a BF to backtrack and to restore the FB as it was before the
transformation.

5.2.10 Selection Window of the Argument Type
Click the List of types… option to open the following window:

Basic Types Indicates the basic models selection for arguments.
This field is checked by default and cannot be
modified.
Type Is used to choose the basic models of the argument:
boolean, double, duration, integer, long, real, sint,
usint et word. Several basic models can be assigned
to the same argument; a contextual menu accessible
from right-clicking in this screen is used to add or
delete a type of variable.
A right-click on the Type field opens the following contextual menu. It can be used to
add, remove, copy and paste more than one type for selected argument in the
Function Block properties window.

5.3 High Functional Blocks
5.3.1 Description
The High Functional Blocks (HFB) used in diagrams do not generate code. They are
represented by a picture or by a text configurable when the component is placed in
a diagram.
They can be put in libraries containing other types of library elements such as MVM,
SVM, FB.
They are described literally and have a specific icon according to their type which
identifies them in the Libraries tree:
Icon Type
Graphic HFB: represented by a picture in the diagrams.

Literal HFB: represented by a text in the diagrams.
Their name must be unique among the libraries elements.
In the tree, a green LED appears to the left of icons with valid models. A red signal
light appears beside icons with invalid models.
The High Functional Blocks have no code, no internal variables and no
association between arguments and MVM.

5.3.2 Creating a High Functional Block
To create a High Functional Block, click the New option of the contextual menu of a
library.
The New/Properties window opens.
Select High Functional Block in the drop-down menu of the Element of Library field to
create a HFB:

Element of Library Used to select the type of element of library to
create.
Name Indicates the name of the high functional block.
Label Indicates the label of the high functional block.
Author Indicates the author of the high functional block. By
default, the author is the current user.
Type Used to choose how the high functional block will be
represented in the diagrams: text or image.
The Ok button confirms the user’s choice and creates a new high functional block.
The Cancel button is used to discard the changes and close the window.
The Help button displays contextual help for the window.

5.3.3 High Functional Block contextual menu
The following contextual menu is associated to a high functional block:
Item Description
Properties Opens the properties window of the high functional block.
If the element is in the extracted state, the high functional
block definition can be modified.
Delete Deletes the high functional block, if it is not in use.
This option is not available if the element is extracted or
hidden.
Cut Cuts the high functional block. The icon of the cut element
is greyed out.
Paste Pastes the element that has been cut previously.
Find Available only at the project level.
Issue Allows the user to change the state of the high functional
block from extracted to current.
The modifications carried out on an extracted element are
taken into account when selecting the Issue option.
Extract Allows to change the state of the high functional block from
extracted to current.
Cancel Cancels the extraction of the high functional block. The
current state of the element is not modified. The version
number is lowered to the one of the current state. If the
element has no current state, the element is deleted.

Item Description
Hide Allows the user to mask the high functional block.
According to the user level, the element disappears from
the treeview or appears with the icon on its left.
Show Unmasks the high functional block to allow any user to see
it.
Select Component Allows the user to select the component to put it in an
open diagram in the diagram editor.
This element is not available on an extracted element.
Edit Linked Documents Allows the user to configure the link with a document of
different types (.doc, .mpg, .html, URL, …).
Display Linked Allows the user to view the linked documents.
Documents
Cross References Displays the variables belonging to the diagram and used
in other diagrams.
5.3.4 High Functional Block properties
The Properties window of a high functional block is accessible both from an extracted
or a current element.
If you open the window from a current element, you cannot modify it. All
the fields are greyed out.
5.3.4.1 Header and “Arguments” tab
Double click a high functional block or select the Properties item of its contextual
menu to open the High Level Block Model: Properties window.

Header
Name Indicates the name of the high functional block.
Label Indicates the label of the high functional block.
Author Indicates the author’s name of the high functional
block model.
Validity Indicates the validity of the high functional block.
It is defined when the user clicks on the Apply or
Ok buttons.
Height Allows the user to configure the height of the
HFB. By default, the value is equal to the minimal
height, which corresponds to 2 grid units in a
diagram. This value can be modified by 0.5 pitch
unit.
Width Allows the user to configure the width of the HFB.
By default, the value is equal to the minimal width,
which corresponds to 2 grid units in a diagram.
This value can be modified by 0.5 pitch unit.
Arguments tab
Nb. Indicates the sequence number of the argument.
Name Indicates the name of the argument.
Basic Types Defines the basic models of the argument.
Non modifiable. By default, the value is
”VARIANT” (meaning ”all type of variable”).
Label Indicates the label of the argument.
Side Defines the argument position in the graphic
representation of the functional block (Top,
Bottom, Left or Right).
Graphic Position Defines the graphical position of the argument
with respect to the selected SIDE.
Negation Supported The argument can be added to the diagram.
In the list of arguments, the user can create, delete, copy or paste an
argument thanks to the contextual menu accessible from a right-click
within the tab area.

5.3.4.2 “Graphical Aspect” tab

Text Used to represent the HFB by a text in the
diagrams.
Modifiable Text Used to define whether the text written in the text
zone below will be editable when put in the
diagram editor.
Picture Used to represent the HFB by a picture in the
diagrams.
Thickness of the Used to define the thickness of the picture border
Border (from 0 to 6).
0 = no border.
Button Browse Used to search for the picture that will represent
the HFB.


5.3.5 Cross References
Select the Cross References item of the HFB contextual menu to open the Cross
References of the Component window:
The Functional Diagrams tab displays the diagrams used in the selected element of all
the diagrams of the functional tree.
The Workspace Diagrams tab displays the diagrams used in the selected element of
the hardware tree.

5.4 Objects Models
5.4.1 Creating an Object Model
Click the New option in the contextual menu associated to a library to open the
following window:

Library Element Indicates the creation of a model or a functional
block.
Name Name of the model.
Label Label of the model.
Author Indicates the author of the object model. By default,
the author is the current user.
The OK button confirms the user's choice and creates the new model.
The model created is in an Extract state. In the tree view, the model appears under
the library from which the creation has been asked. Then, the user can define the
content of the model.

5.4.2 Contextual Menu of an Object Model
The following contextual menu is associated to a model:

Item Description
Properties Opens the properties window of the model.
If the element is in an extract state, then the model definition can
be modified.
Delete Deletes the model.
This option in unavailable if the element is extract or hidden.
Cut Cuts the element.
The icon of the cut element appears greyed.
Example: becomes
Find Greyed item (only available on the project level).
Issue Is used to change the project from an extract state to a current
state.
The modifications made on the extract model are taken into
account while issuing the model and impact all the objects
produced from the model.
Extract Is used to change the project from a current state to an extract
state.
Example: Current FB .

Item Description
Extract state FB .
The version number of the model is then automatically
incremented. In an extract state, modifications on a model are
authorized with no impact on instantiated objects.
Cancel Cancels the model extraction. The current state of the model is
not modified. The number of the version becomes the one of the
current state again. If the model has no current state, it is
deleted.
Hide Is used to hide the model. According to the level of the user, the
model appears with the icon on its left or doesn’t appear at all
in the treeview.
This functionality allows a configuration engineer to hide models
to avoid their use in the project.
This option is unavailable if the element is extract.
Show Is used to unhide the model and show it to everybody.
Edit Linked Is used to configure the link with a document (.doc, .mpg, .html,
Documents URL,...).
Display Linked Is used to display linked documents.
Documents
Cross Is used to display the consumption of the model in the objects of
References the project (cf. 5.4.4,List of the consumptions of a model).
To allow the projects (or part of projects) import/export to completely

manage the associated files type documents, the user has to respect the
following rules:
The files to associate to the library elements have to be placed on the
server in the (xxxlog) project directory under the tree structure below:
\\<UNC name of the server>\P320Share\Ccad\<xxxlog>\docuser\Lib
Their association has to be done with the UNC name of the server.

5.4.3 Object Model Properties
The model properties window is accessible in modification mode only if this one is
opened from an extract model.
Select the Properties option or double click an extract model to open the following
window:

Header part
Name Name of the object model.
Label Label of the object model.
Author Author of the object model.
Version Version of the model, this version is automatically
incremented when an « issue » on the model is made.
Validity Validity of the model. It is produced when a user clicks on
the Apply or Ok buttons. The validity is produced when the
user clicks on the Apply or OK buttons. It is the result of a set

of consistency checks on the definition of the model. If the
value of the indicator is Yes, the model can be issued, i.e. it
can be consumed in the project in its new version.
Icon Icon used to represent the object in the functional tree
structure selected in the list of icons defined in the
‘p320share\ccad\<project>\icones\model directory on the
Controcad server.
The object issued from the model is created with the icon
that has been associated to the model.
View Part
Name Name of the view associated to the model.
List of Functional Blocks part

This zone contains the list of FBs used by the model, it is input with a drag and drop
between the library and this window.
Note : The content of the FB can be represented graphically or in LEA code. There is no graphic
links described in the model between these FBs.

Name Name of the functional block.
If the user clicks on this field, a contextual help

appears to display the path and name of the library that
contains the FB, the name and the label of the FB.
Tag Tag of the FB in the object model.
This tag, which is unique in the model, is used in the

object properties file.
By default:it is input with the type of the FB and a order
number of the FB in the model.
Contextual menu associated to the list of FBs

In the list of FBs, the following menu associated to a FB is the following:

Option Description
Delete Deletes the FB from the model. If the FB is used in an object, the
user is notified.
Properties Opens the properties window of the FB
Links Opens a window that displays the list of elements linked to the
FB tree-structured organized.
Double-click an FB of the list to display its properties.
List of Models of Variable part

This zone contains the list of MVMs and SVMs used by the model. It corresponds to
the MVMs associated to FBs put in the graphical description of the model and to a
set of MVM/SVM dragged and dropped in the model from the library tree.
Link Indicates if the variable model is linked to an FB put in
the List of Functional Blocks part or if the variable model
is linked to another MVM of the model.
Used Indicates if a MVM, linked or not to an FB of the
model, is used on the object.
Name Name of the variable model.
If the user clicks on this field, a contextual help

appears to display the path and name of the library
that contains the FB, the name and the label of the
variable model.
Tag Tag of the variable model in the object model.
This tag, which is unique in the model, is used in

the object properties file.
By default:
For the FBs used to manage names applied to FB,
the tag is input with the tag of the FB in the model.
For the MVM used to manage the FBs argument
groups , the tag is input with the tag of the FB in the
model linked with the argument group identifier.
For the MVMs and SVMs added in the model by
the user, it is input with the model of the variable
followed by the order number.
HMI Label Label associated to the model element displayed for
the HMI.
This label can be translated in a second

language.

Contextual menu associated to the list of variable models:
The contextual menu associated to the variable models in the List of variable models
part is the following:

Option Description
Properties Opens the variables grid and displays:
the list of library MVMs that contain the SVM,
the list of the MVM fields.
Delete Deletes the variable model from the object. If the variable
model is used in an object, the user is notified.
Variable models linked to FBs or another MVM cannot be

deleted from the variable model list.
Double-click a variable model to display its properties.
Note : When a filter is applied in a variable grid, the column header becomes green to notify the
user.

The Magnifying glass button is used to visualize properties file of the objects
produced from this model.
The FB/MVM button is used to visualize the links between MVM fields and FB
arguments.
The MVM/MVM button is used to manage the list of links between MVM links.
The Control block button is used to visualize the list of links between MVM links
and control blocks.
The Dynamic drawing button is used to visualize the list of links between MVM
fields and dynamic drawings.
The Hardware button is used to model the objects connections on I/O boards.
The Help button is used to display contextual help for this screen.
The Apply button confirms the choice without closing the window.
Description of HMI links
This screen is used to describe the links between a MVM field or a SVM
corresponding to a HMI variable and other SVM or MVM fields belonging to the
model.
The screen is divided into three parts:
The list of SVMs or « master » MVM fields,
The list of SVM or « associated » MVM fields,

The list of all the SVMs and MVM fields of the model corresponding to HMI
variables.
Zone A
The zone A contains all the “Masters” of the model (SVM and MVM fields that have
to be linked to other SVM or MVM fields of the model.
MVM Type of the MVM containing the field.
Path Path of the MVM field.
Tag Tag of the MVM in the model.
Label Label of the field.
Zone B
The zone B displays the different possible links selected for « Master » in the A
zone. The number and types of authorized links are conditioned by the type of the
« Master » field.
MVM Type of the MVM containing the field.
Tag Tag of the MVM in the model.
Label Label of the field.
Type of Link Type of the link to input.
Zone C

The zone C contains all the SVM and MVM fields defined in the model that
correspond to HMI variables.
Affec. Indicates if the MVM is already associated in the
model.
MVM Type of the MVM containing the fields.
ID Tag of the MVM in the model.
Label Label of the MVM field.
The Tree view button is used to visualize all the SVMs and MVMs tree-structured
organized.
The List button is used to visualize all the SVMs and MVM fields corresponding to
HMI variables presented as a list.
The Left-oriented chevron button is used to copy the SVM or the selected MVM
field in the right side zone to the left side zone of the chevron.
The Right-oriented chevron button is used to delete the SVM or MVM field selected
from the left side zone.
The Help button is used to display the contextual help of the current window.
The Close button quits the function. If the user forgot to save the changes, he is
asked to confirm.
It is possible for the user to input the zones A and B by dragging a selected field of
zone C to one of these zones.
If an HMI link is added (resp: deleted) application objects are not updated.

5.4.4 List of the consumptions of a model
Select Cross References from the contextual menu associated to a model to open the
following window:
This window lists the objects referencing the model selected.

The Print button is used to print the content of the window.
The Close button closes the window.
The Help button is used to display the contextual help of the current window.
5.5 Variable Models
5.5.1 Description
The variables managed by Controcad are single, multiple or internal to the functional
block models. All these variables are constructed from models that are defined in
the variable grid via the Libraries tree.
There are two types of variable model:
Icon Model
SVM (Single Variable Model)

MVM (Multi Variable Model)

5.5.2 Single Variable Models
Single variable models (SVM) are used to create single variables, i.e. variables
corresponding to basic types such as Boolean, word, real etc.
5.5.2.1 Creating an SVM
following window:

Element of Selecting 'SVM' from the list enables the creation of a
Library new SVM.
Library Library that contains the SVM from which the new model
will be created. The list proposed is the list of the project
libraries containing SVMs. Each library is presented with
its complete path in the Libraries tree. By default,
Controcad proposes the selected library during the last
creation. Click [none] to select no library and obtain a list
of all the project SVMs in the next field.
SVM Name of the SVM from which the new model will be
created. The list proposed is the list of the SVMs in the
selected library in the Library field.
Name Name of the new model.
Label Label of the new model
Author Author of the SVM. By default, the author is the current
user.

The OK button confirms the user's choice and creates the new SVM.
An SVM is always created from another single variable model.
The creation of a single variable (SV) consists in creating a reference to an SVM.
The new variable is defined automatically with the characteristics of the model. This
mechanism is used to create variables consistently and rapidly.
Defining a single variable model consists therefore in defining the values that will
characterize the resulting variables.
The SVM is created below the library from which the variable grid has been
activated. Its state is extracted. The model is shown in the Libraries tree once the
grid is saved.
5.5.2.2 SVM Contextual Menu
The following contextual menu is associated to a SVM in the Libraries tree:

Option Description
Cut Cuts the element. The icon of the element cut appears in grey
Modifications made to models have no effect on variables
already created. New variables created after the model is
modified will integrate the modification.
Hide Used to hide the element. depending on the user's access level,
either the element does not appear in the tree, or it appears with
the icon to its left.

Option Description
This function enables a configuration level user to hide elements

of library invisible to prevent their being used in the project.
Show Used to unmask the element and make it visible for all types of
users.
Edit Linked Used to configure links with a document; the document type may
Documents vary (.doc, .mpg, .html, URL etc.).
Documents
\\< server UNC name >\P320Share\Ccad\<xxxlog>\docuser\Lib
5.5.2.3 Characteristics of an SVM
Clicking on the Variable Models > SVM option of a library contextual menu displays all
the single variable models in this library in the grid.
The SVM characteristics are the common variable characteristics (for their
description, see [CCAD_FUNCT] in 1.7 List of Referenced Documents) with in
addition:
Version The version number of the SVM is managed by
Controcad in accordance with extractions and issues
of the SVM.
State Indicates the state of the model (Current, Extract or
Masked).
Profile Is used to automate the construction of the process ID
of variables produced from this SVM. The field
contains the prefix of the ID of the variable to be
constructed. This prefix will be completed by a number
that will be incremented for each new variable. The
uniqueness of the tags is thus guaranteed.
Profile High Limit Defines the limit upper of the number incremented
during construction of the ID.
Profile Low Limit Defines the initial value of the number incremented
during construction of the ID.
Author Author of the SVM.

The following contextual menu is associated to this variable grid:

Option Description
Properties… Displays the properties of the SVM (cf. 5.5.2.4,Properties of an
SVM).
New… Creates a SVM.
Delete Deletes the SVM if it is not used in the project and if it is issued.
Save Saves the variable grid
Filter Opens the filter screen
Find Opens the search window
Replace Opens the replace window
Note : The column headers change color to indicate to the user that a filter is being applied.
These column headers are shown in green.

5.5.2.4 Properties of an SVM
In the variable grid, select the Properties option or double click the line of the current
SVM to open the following window:
This window displays the same characteristics as those in the grid, but the
information is presented in a less condensed form (cf. 5.5.2.3,Characteristics of an
SVM). It is synchronized with the grid; i.e. the model in the window always
corresponds to the current line in the grid.
The user can modify the value of the attributes if the model has previously been
extracted. The model can also be modified directly in the grid.

Select the Dynamic Drawings tab to open the following screen:
The Dynamic Drawings tab is used to assign dynamic sub-drawings to an SVM having
exchanges with the control room.
Dynamic sub-drawings are created from the views tree and are stored by category
(see [CCAD_VIEW] in 1.7 List of Referenced Documents).
Category Name of the dynamic sub-drawing category. The
[None] option is used to select no specific category
and thus to obtain the list of all the dynamic sub-
drawings of the project in the zone "List of Dynamic
Drawings".
Filter Used to filter the list of dynamic sub-drawings.
List of Dynamic List of the dynamic sub-drawings belonging to the
Drawings selected category.
Dynamic Drawings Lists the dynamic sub-drawings assigned to the
affected variable model.

5.5.3 Multiple Variable Models
Just as an SVM is a single variable model, an MVM is a multiple variable model. An

MVM models a group of functionally linked application variables (e.g. a logic state
and its validant, a motor or a valve). An MVM is defined hierarchically: an MVM is
composed of a root and of a set of fields that may be single or multi-variable
models.
According to the diagram above, a multiple variable model MVM1 will be composed
of 10 variables:
4 multiple variables corresponding to the root and to fields 1, 2 and A.
6 simple variables corresponding to fields 3, B, Z, W, C and D.
A MVM is created in two phases: the root is created first then the fields.
MVMs are identified by their unique roots. The root is shown in the Libraries tree.

5.5.3.1 MVM Contextual Menu
The following contextual menu is associated to an MVM in the Libraries tree:

Option Description
Cut Cuts the element. The icon of the element cut appears in grey
Modifications made to models have no effect on variables
already created. New variables created after the model is
modified will integrate the modification.
Hide Used to hide the element. Depending on the user's access
level, either the element does not appear in the tree, or it
appears with the icon to its left.
This function enables a configuration level user to hide
elements of library invisible to prevent their being used in the
project.
Show Used to unmask the element.
Variable Models > Opens the MVM fields in the variable grid.
MVM Fields
Edit Linked Used to configure links with a document; the document type
Documents may vary (.doc, .mpg, .html, URL etc.).
Documents
Edit MVM Rank Used to create variable groups within an MVM, in order to be
Grouping able to assign these groups to external exchange arrays (cf.
5.5.3.8,Edit MVM Rank Grouping).

\\<server UNC name>\P320Share\Ccad\<xxxlog>\docuser\Lib
5.5.3.2 Creating a MVM Root
following window:

Element of Library Selecting 'MVM' from the list enables the
creation of a new MVM.
Nature Defines the nature of the MVM (modulable or
fixed).
Name Name of the MVM This must be unique in the
project library set.
Label Label of the MVM
Author Author of the MVM. By default the author is the
current user.

The OK button confirms the user's choice and creates the MVM root.
The MVM is created below the library from which the variable grid has been
activated. Its state is extracted. The model is shown in the Libraries tree once the
grid is saved.
5.5.3.3 Characteristics of an MVM Root
Clicking on the Variable Models > MVM option from a library displays the roots of all the
multi-variable models contained in this library in the variable grid.
The screen is as shown below:

Version The version number of the model is managed by
Controcad in accordance with extractions and issues
of the model.
State Indicates the state of the model (Current, Extract or
Masked).
MVM Name Name of the MVM.
Nature Defines the rules governing use of the model in the
project (System, Fixed or Modulate).
Model Aspect This is significant for a System MVM. It shows:
Controller if the MVM is recognized exclusively by the
controller.
HMI if the MVM is recognized exclusively by the
control room HMI.
Mixed if the MVM is recognized by the controller and
by the control room HMI.
Profile Used to automate the construction of the process ID
of the variables issued from this model. The field
contains the prefix of the ID of the variable to be
constructed. This prefix will be completed by a number
that will be incremented for each new variable. The
uniqueness of the tags is thus guaranteed.

Profile Low Limit Defines the initial value of the number incremented
during construction of the ID
Profile High Limit Defines the limit upper of the number incremented
during construction of the ID
Author Author of the MVM. By default the author is the
current user.
Note : The MVM Name, Label, Nature, Profile and Author MVM root fields can be modified if
the MVM is in the ’Extract’ state.
An MVM reflects an ALSPA System variable structure. It can neither be created nor
modified in the project.
A fixed MVM is used to define a project data model that requires the multiple
variables created to have a fixed structure.
A modulate MVM is used to define a project data model that allows the structure of
the variables created from the MVM to be modified.
The profile attributes are optional. They are necessary if the user wishes the ID of
the multi-variables to be constructed automatically during creation.

Option Description
Properties… Displays the properties of an MVM root (cf. 5.5.3.4,Properties
of an MVM root).
New…
Create Creates an MVM (cf. 5.5.3.2,Creating a MVM Root).

Duplicate Duplicates the selected MVM.
Delete Deletes the MVM if it is not used in the project and if it is
issued.
Save Saves variable Grid
Replace Opens the replace window .

5.5.3.4 Properties of an MVM root
Clicking on the Properties option, or double clicking on a MVM line in the variable grid
showing the MVM roots from a library, opens the following window:
This window displays the same attributes as those in the grid (cf.
5.5.3.3,Characteristics of an MVM Root)), but it displays the attributes in a less
condensed form. It is synchronized with the grid; i.e. the MVM displayed in the file
always corresponds to the current line in the grid.
The user can modify the value of the attributes if the MVM has previously been
extracted. The attributes can also be modified directly in the variable grid line.

5.5.3.5 Creating a MVM Field
Select the New… option from the contextual menu associated to the variable grid
showing the fields of an MVM to open the following window:

MVM / SVM Indicates whether the field is to be created from a
multiple (MVM) or single (SMV) variable model.
Library Library that contains the SVM or the MVM from
which the new model will be created. The list
proposed is that of the project libraries containing
SVMs or MVMs. Each library is presented with its
complete path in the Libraries tree. By default,
Controcad proposes the selected library during the
last creation. The [None] option is used to select no
library and thus enables a list of all the project
SVMs or MVMs to be obtained in the next field.
Model Name of the SVM or of the MVM from which the
new field will be created. The list proposed is that
of the SVMs or MVMs of the selected library in
Library.
Name Name of the field. Used to construct the path
Pattern Character string identifying the new field in the
MVM and in the names of the variables created
from the MVM.
Label Label of the field. The metacharacters * and ? are
accepted and managed in the same way as in the
pattern.

The OK button confirms the user's choice and creates the MVM field.
5.5.3.6 Characteristics of an MVM Field
Clicking on the Variables Models > MVM Fields option from the contextual menu
associated to an MVM displays the MVM root (in the first line) and the fields in the
grid.
The characteristics of a MVM are common variables with in addition:
Level Gives the level of the field in the hierarchy of the MVM.
The level 0 is that of the root.
Path Path from the root to the field in the MVM hierarchy.
The path is constructed by concatenating the names of
the fields of the hierarchy separated by dots. The name
of the root is omitted. The name of the field is given
when the path is created,
Pattern Character string identifying the field and used in the
construction of the name of the variable that
corresponds to the field during creation of a “multi-
variable” from the MVM. The pattern is expressed by
means of the characters * and ? where * designates a
series of characters and ? a single character. The
pattern is also used to construct the patterns of the
fields issued from MVMs.
Aspect This is significant for the fields issued from SVMs and
for fields issued from System MVMs. It shows:
Controller if the field is recognized exclusively by the
controller
HMI if the field is recognized exclusively by the control
room HMI
Mixed if the field is recognized by the controller and the
control room HMI
Ctrl Block Model Name of the control block model to be associated to the
MVM.
In the project, model grids are defined in the
Configuration menu (see [CCAD_INTRO] in 1.7 List of
Referenced Documents).
During creation of the variable, a control block will be
created automatically from the model indicated.
The user can modify the values of the MVM field if the MVM has previously been
Extracted.


Option Description
Properties… Displays the properties of the MVM field.
New… Creates an MVM field (cf. 5.5.3.5,Creating a MVM Field).
Delete Deletes the MVM field if it is level 1 and if it is not used in the
project.
Save Saves variable Grid
Hierarchy Opens the window that gives access to the list of the MVMs
associated to the library. The tree can be deployed to obtain
the list of SVMs associated to each MVM.
Replace Opens the replace window
5.5.3.7 Properties of an MVM field
Clicking on the Properties… option, or double clicking on the line of the MVM field in
the variable grid, opens the following window:

The screen opened from the General tab displays the same attributes as those of the
grid (cf. 5.5.3.6,Characteristics of an MVM Field), but it presents them in a more
expanded form. It is synchronized with the grid; i.e. the field displayed in the window
always corresponds to the current line in the grid.
The user can modify the values of the MVM field if the MVM has previously been
extracted. The attributes can also be modified directly in the variable grid line.
Select the Dynamic Drawings tab to open the following screen:
This window is used to assign dynamic sub-drawings to an SVM or to an MVM

having exchanges with the control room.
The dynamic sub-drawings are created from the tree view and are sorted by
categories (see [CCAD_VIEW] in 1.7 List of Referenced Documents).
Category Name of the dynamic sub-drawing category.
The [None] option is used to select no specific
category and thus to obtain the list of all the
dynamic sub-drawings of the project in the zone
"List of Dynamic Drawings".
Filter Used to filter the list of dynamic sub-drawings.
List of Dynamic Drawings List of the dynamic sub-drawings belonging to
the selected category.
Dynamic Drawings Lists the dynamic sub-drawings assigned to the
affected variable model.

5.5.3.8 Edit MVM Rank Grouping
In the Libraries tree, select the Edit MVM Rank Grouping option from the contextual
menu associated to an MVM to open the following window:
This window is used to create groups composed of SVMs within an MVM. Only
SVMs defined as a field of the MVM can be associated to these groups. Each SVM
in a group must have a rank in order for all the SVMs in the group to be structured.
The groups created can then be assigned to external exchange arrays. So instead
of assigning the variables one after the other, it is possible to assign the group
containing these variables directly. For the procedure to assign variables to an
exchange array, see [CCAD_HARD] in 1.7 List of Referenced Documents.
MVM part
Name Name of the MVM.
Rank Grouping List of the Current MVM part

Name Name of the group.
Label Label of the group.
Array Type Type of the group.

Selected Rank Grouping part
Rank Rank of the SVM in the group.
SVM Name of the SVM assigned to the group.
Size (byte) Size of the SVM (in bytes).
The Save button confirms the user's input without closing the window.
The Close button quits the function.
5.5.4 Variable Validants and Sensor Faults
5.5.4.1 Variable Validant
The validant that is the source of the alarm must not relate to a communication fault.
This presumes that the ALSPA HMI discriminates between an invalidity originating
from the controllers (cell validant) and a communication fault type invalidity. The
HMIs must display this data separately.
5.5.4.2 Sensor Faults
The requirement exists to transmit this data instead of creating one or more
additional cBSig variables.
Explicitly show the validant bit _V of the variable and the communication fault
between the cell and the ALSPA HMI.
5.5.4.3 SMCA Group Faults
These groups are composed of 3 analog values and 6 logic variables.

RCMs are created in Controcad from C2K_Cmd_AS112 MVMs and RPCs from
C2K_SPt_AS112 MVMs.
The 3 analog values are visible in the CCAD variable grid with the suffixes _C, _X,
_D for commands (RCM) and _U, _B, _C for setpoints (RPC).
They are transmitted to the ALSPA HMI where they are shown as normal cASig
variables.
The 6 logic values are visible in the CCAD variable grid with the suffixes _P, _F, _E,
_I, _H, _A for both commands AND setpoints.
The first 3 values _P, _F, _E are transmitted to the ALSPA HMI where they are
shown as normal cBSig variables.
The last 3 values _I, _H, _A are transmitted but are not used.

The table below supplies a functional name for these suffixes (for information only).
Data RCM RPC Name
Suffix Suffix
Ana 0 _C Actuator command

Ana 0 _U Value of order
Ana 1 _X Auxiliary value
Ana 1 _B Analog signal value
Ana 2 _D Bias value
Ana 2 _C Automatic order value
Bit 0 _P Auto/manu position
Bit 0 _P Auto/manu order position
Bit 1 _F Auto/manu forcing
Bit 1 _F Auto/manu order forcing
Bit 2 _E Command value forcing
Bit 2 _E Order value forcing
Bit 3 _I _I First station inhibition
Bit 4 _H _H Second station inhibition
Bit 7 _A _A Application Variables
The requirement is to ensure that the logic value _A is seen as a fault and is
processed in the same way as the validant and sensor faults described above.
It has been decided that the values _I and _H will not be used and therefore do not
require processing.
5.5.4.4 Controcad HMI DB
The variable properties window changes to enable a degree of urgency to be

assigned to the new Sensor fault alarm validant variable (Sensor default alarm
degree).
Assigning a value between 1 and 4 means that this variable will generate an alarm
event when the variable validant is set to 1 on the occurrence of a sensor fault.
The value 0 means that the variable does not generate an alarm event on the
validant on the occurrence of a sensor fault.
A new project will set this variable by using the variable models (described below).
The user can then modify this variable as necessary.

5.5.4.5 Controcad variable
In the variable grid, the characteristic Sensor default alarm degree is used to assign a
degree of urgency to the alarm produced by the validant. The value of a given
variable can be:
null the function is not used (no alarm).
0 the variable will not cause an alarm when its validant is set to 1 or on the
occurrence of a sensor fault.
1 , 2 , 3 or 4 the variable will cause an alarm if the validant is set to 1 or on the
occurrence of a sensor fault.
The characteristic is accessible in the variable grid and the variable models if the
variable or the model:
is recognized by the supervisory system and by the controllers,
is multiple and if its supervision object type is cASig or cBSig,
is simple and is both an input and is of Signal or SignalInput supervision
exchange type.
Library documentation Model Urgency_def
CE2000 System/Control/I C2K_AI_CJC Path 1_Input 3

analog nput-
C2K_AI_HLL Path 1_Input
inputs Output/CE2000
C2K_AI_T Path 1_Input

AS112 System/Control/I C2K_Cmd_AS1 Path 3
nput- 12 01_Actuator
Output/CE2000 Output
C2K_Spt_AS11 Path
2 01_UsefulVal
ue
CE2000 System/Control/I C2K_DI Path 1_Value 3
Boolean nput-
inputs Output/CE2000
Boolean System/Control/ cBSig Path 1_Value 2
signal Cell<->HMI Data
models
System/Control/ IHR_DI Path 1_Value 2
Input-Output/IHR
Analog System/Control/ ccASig_D Path 1_Value 2
Signals Cell<->HMI Data
ccASig_I Path 1_Value
models
ccASig_R Path 1_Value

Boolean System/Reserve GEMST_C1 3

inputs d/Aliens
GEMST_GT 0
Models/GEMST
ART GEMST_SFT 0
Gemstart System/Reserved/ GEMST_PWR 3

analog Aliens
inputs Models/GEMSTA
RT
System/Reserved/ GEMST_CUR 0
Aliens
Models/GEMSTA
RT
DI103 System/Reserved/ DI103_D000 3
Boolean Aliens
inputs Models/DI103
System/Reserved/ DI103_D001 to 0
Aliens DI103_D003
Models/DI103
DI103_D007 to
DI103_D009
DI103_D016 to
DI103_D018
DI103_D020 to
DI103_D067
DI103_D084
DI103_D098 to
DI103_D0115
DI103_D124 to
DI103_D126
DI103_D130 to
DI103_D140
DI103_D160 to
DI103_D167
DI103_D176 to
DI103_D183
DI103_D192 to
DI103_D194

DI103_D198 to
DI103_D204
DI103_D206 to
DI103_D212
DI103_DMIX
DI103 System/Reserved/ DI103_GM5_1 3
analog Aliens 8
inputs Models/DI103
DI103_GM1_0 0
0
DI103_GM2_0
0
DI103_GM2_0
2
DI103_GM3_0
0
DI103_GM3_0
2
DI103_GM3_0
4
DI103_GM3_0
6
DI103_GM4_1
2
DI103_GM4_1
4
DI103_GM5_2
0
DI103_GM5_2
2
DI103_GM5_2
4
DI103_GM5_2
6
DI103_GM5_2
8
DI103_GM5_3
0
DI103_GM5_3
2
DI103_GM5_3
4

DI103_GM6_4
6
DI103_GM6_5
0
DI103_GM6_5
4
DI-OPC System/Control/ INP_HMI_VT_I Path 0
analog Input-Output/DI- 1 1_Value
inputs OPC
INP_HMI_VT_I Path
2 1_Value
INP_HMI_VT_I Path
2_SWAP 1_Value
INP_HMI_VT_I Path
4 1_Value
INP_HMI_VT_I Path
4_SWAP 1_Value
INP_HMI_VT_ Path
R4 1_Value
INP_HMI_VT_ Path
R4_SWAP 1_Value
INP_HMI_VT_ Path
UI1 1_Value
INP_HMI_VT_ Path
UI2 1_Value
INP_HMI_VT_ Path
UI2_SWAP 1_Value
DI-OPC System/Control/ INP_HMI_VT_ Path 0
analog Input-Output/DI- BOOL 1_Value.
inputs OPC
EPL System/Control/In EPL_AI Path 3
(E8000) put-Output/EPL 1_Input
analog
inputs
EPL System/Control/In EPL_DI Path 3
(E8000) put-Output/EPL 1_Input
boolean
inputs

5.5.5 Internal Variables
Internal variables are single variables used in functional block code. They are
defined for the functional block model by a configuration level user.
5.5.5.1 Characteristics of an Internal Variable
Clicking on the Variables Models > Internal Variables option from a functional block
model in a library displays the internal variables of the functional block model in the
grid.
Internal variables are characterized:
by a sub-set of common characteristics:
Kind / Model / Basic Type / Name / Label / Msg State / Unit / Origin / Length /
Constant / Initial value / Setting / Memory Area / Redundancy / Range / Alarm /
Annotation.
by a specific characteristic:
Private: indicates whether the variable is private (Yes) or shared (No). A private
variable is an internal variable specific to each of the instances of the functional
block in the diagrams. A shared variable is an internal variable common to all the
instances of the functional block in the diagrams. If an internal variable is private, a
variable will be created each time the block is placed in a diagram. If an internal
variable is shared, only one copy will exist per controller however many functional
blocks are used in the controller diagrams.
The following contextual menu is associated to the internal variable grid:

Option Description
Properties… Displays the properties of the internal variable.
New… (cf. 5.5.5.2,Creating an Internal Variable)
Delete Deletes the internal variable selected.
Save Saves variable Grid.
Filter Opens the filter screen.
Find Opens the search window.
Replace Opens the replace window.
The New, Delete and Save fields are only shown if the functional block is in extract
mode.

5.5.5.2 Creating an Internal Variable
Select the New… option from the contextual menu associated to the internal variable
grid to open the following window:

Library Name of the library that contains the SVM from
which the internal variable will be created. The list
proposed is the list of the project libraries
containing SVMs. Each library is presented with
its complete path in the Libraries tree. By default,
Controcad proposes the selected library during
the last creation. Click [none] to select no library
and obtain a list of all the project SVMs in the next
field.
SVM Name of the SVM from which the internal variable
will be created. The list proposed is the list of the
SVMs in the selected library in Library.
Name Name of the variable. This must be unique for the
functional block model
Label Label of the variable.
The OK button confirms the user's choice and creates the variable.
The Cancel button cancels the operation.

5.5.5.3 Properties of an internal variable
Clicking on the Properties option or double clicking on the line of an internal variable
in the grid opens the following window:
This window displays the same characteristics as those in the grid, but the
information is presented in a less condensed form. The window is synchronized with
the grid; which means that the variable displayed in the window always corresponds
to the current line of the grid.
The user can modify the value of the attributes if the functional block has previously
been extracted. The variable can also be modified directly in the grid under the
same conditions.
5.5.6 Configuration Variables
Normally, these are system variables and variables necessary to the ALSPA System
domain. They appear in the libraries tree with the icon and have associated
target types. They are produced from the Controcad reference list.

Section 6 Basic Function Editor
6.1 Introduction
The Basic Function Editor tool is accessible by clicking on the Basic Function Editor
option of the Configuration menu of the main Controcad window.
Clicking on this option opens the following window:
The editor screen is divided into three zones:

The menu bar used for editing and manipulating the libraries (file.fbl) and the BFs
(Basic Function) that they contain.
The tree used to display and select the library opened or a BF in the library.
The tabs are used to choose the data to be displayed or modified. The fields on a
white ground can be modified.
It is possible to open several BF editors at the same time. This enables
several libraries to be accessed at once.

6.2 Menu Bar
6.2.1 Menu File
This section describes the File menu of the BF Editor:

Option Description
New Used to create a new library. A dialogue box asks the user
to indicate the name of the library to be created. The
libraries must be created in the project "fbl" directory.
Open Used to open an existing library. A dialogue box opens
allowing the directories to be browsed to indicate the access
path to the BFL file. By default the "fbl" directory of the
project opens.
If another library is open when the user clicks on the New or
Open command of the editor a message requests a closing
confirmation from the user. If the response is affirmative, the
current library closes and the user can choose to edit a new
library.
If no other person is already accessing the library, it will be
opened with read/ write privileges.
If the user wishes to open a library that is already open in
another BF editor the username and the station of the
person that has opened the library will be displayed. This
library will only be accessible in read mode.
Close Terminates the printout of the current library without closing
the editor if there have been no modifications since it was
last saved. If the library has been modified, the command
asks the user if the modifications should be saved or not
before the closure of the library, or if the Close command
must be canceled. The closure of the library enables any
other user to open this library with read/write access
privileges.

Option Description
Save Used to save the modifications made to the current library (if
it is open in write mode).
Save as… Used to save the library that is currently accessed by the
user under another name. During the save operation, the
user indicates the new name and location where the file
must be saved in a dialogue box. A default location will be
displayed which corresponds to the directory of the current
library.
Install Used to install the library on the targets chosen by the user
(CE2000, C8035, C8075, MFC3000, RX3i, Simulator). The
information (Reinstall) appears next to the name of the target
when the library is already installed. (cf. 6.5,Installing a
Library)
Uninstall Used to uninstall a library that has been installed on one or
more targets. (cf. 6.5,Installing a Library)
Installed Libraries… Opens a window indicating the libraries installed and the
targets on which they are installed.
It is possible to reinstall or uninstall a library from this
window via the contextual menu opened by right clicking on
a library. (cf. 6.5,Installing a Library)
Properties Opens a window showing the library inputs (size, location of
the FBL file, dates of creation, modification, installation etc.
Remove Used to delete the library, the compiler C files and the
controller files. (cf. 6.5,Installing a Library).
Check Used to generate a library (checks the FBD file syntax,
creates the C compiler .h and .lib files) to be able to test the
BF with Visual Studio. This command requires Visual Studio
on the station and is used to save the file.(cf. 6.5,Installing a
Library)
Quit Closes the BF editor.

6.2.2 Edit Menu
This section describes the Edit menu of the BF Editor:

Option Description
Cut Deletes the active selection and places it in the clipboard.
Copy Copies the selection into the clipboard.
Paste Inserts the content of the clipboard at the designated
point and replaces the selection. This command is only
available if text has previously been cut or copied.
Delete row or item Deletes a line in the grid if the grid is selected ( Delete row
in the grid of the Global variables, Inputs, Outputs, internal
variables, Constants tabs) or a BF if the tree is selected
(Delete item).
Go to line Opens the window used to input the number of the line to
be attained in the .fbl library already opened. Following
the input of this field, the name of the BF concerned and
the code corresponding to the line are displayed, the
cursor is then positioned on the asked line ( in the
corresponding tab: BF code, Inputs, Outputs, Internal
variables or Constants).
6.2.3 Insert Menu
This section describes the Insert menu of the BF Editor:
or
The Insert menu displayed depends on whether the root library or a BF from the
library is selected.
Description of the options if the library is selected:
Option Description
Basic Function Used to create a BF in the library.
Global variable Used to create a global library variable.

Options if a BF is selected:
Option Description
Input Used to create an input in the BF.
Output Used to create an output in the BF.
Internal variable Used to create an internal variable in the BF.
Constant Used to create a constant in the BF.
Variables are inserted at the end of the list in a grid and BFs are inserted in the last
position in the tree.
A dialogue box asks the user to enter the various mandatory parameters of the
object to be inserted. If an object with the same name already exists, the dialogue
box indicates that the object exists and asks the user if he wishes to overwrite the
existing object or change the name field of the object he wishes to insert.
6.3 Tree
The tree takes the following form:

a root element corresponding to the library (file.fbl),
sub-elements corresponding to the BFs in the library.
The sign indicates that the tree below the element is deployed.
The sign indicates that the tree below the element is not deployed.
Using the left mouse button in the tree:
Click the name of the library in the tree to see and modify the data contained in
the library tabs, such as the name, the comment and the global variables.

Click the name of a BF to see and modify the data contained in the BF tabs such
as the name, the comment and the variables. Changing the FB in the tree will not
change the current tab, but will change its content.
Using the right mouse button in the tree:
Click the name of a BF to display its contextual menu. This menu contains the
Delete BF option used to delete the selected BF.
6.4 Tabs
The different tabs give access to the display, modification and the creation of the
data relative to the BF and to the current library.
Only the fields on a white ground can be modified.
The mandatory fields are fields that must have a value (text or number).
If the field is a field name the first character must be a letter and the name must
not contain any special characters with the exception of the underscore.
If the field is a number such as the length of an array or the position of an input or
an output, the value must be a number.
If the field is a variable type, the type required must be selected from a pull-down
menu.
Optional fields such as initial values must comply with a syntax. There are no
mandatory conditions for comments.
All the mandatory and optional fields can be modified by a simple click. Commands
in the Insert menu should be used to add a variable. The Delete (Delete row) command
in the Edit menu or in the contextual menu must be used to delete a variable from a
line in a grid.
The Copy, Paste and Cut commands accessed by right clicking in a field correspond
to the commands with the same names in the Edit menu. They only function on the
content of a field. An object in a tab field must be selected to prevent the Cut and
Copy commands being deactivated in the contextual menu.
6.4.1 Library Tabs
The General tab gives information on:

- The name of the library (non-modifiable field).
- The date of the last modification
The attribute of the file indicates the file access rights (non-modifiable field).
The Global variables tab provides information on the global variables in a grid. The
different columns of this grid indicate:
- The name (mandatory field).
- The type of variable: Boolean, real etc. (mandatory field).
- The length of the array (modifiable field, mandatory if an array).
- An initial value (optional field).

- The name of the array associated to the cursor, if the variable is declared as
being a cursor (modifiable field, mandatory if a cursor).
- A comment explaining the role of the global variable (optional field).
Summary of the different variable types:
Type Number of Definition Value Value
bits
BOOLEAN 1 Boolean 0 1
CURSOR 16 Cursor Index of an array element
DOUBLE 32 Double - 2 147 483 647 2 147 483 647
DURATION 32 Timeout 0 ms 248 days
INTEGER 16 Integer -32 768 32 768
LONG 32 Long integer 0 4 294 967 295
REAL 32 Real
WORD 16 Word 0 65535
6.4.2 BF Tabs
The General tab gives information on:

- The name of the BF (modifiable mandatory field).
- The author (optional field).
- The version (character string, optional field, default value 1).
- The language used for the LEA or C code (mandatory fields, default value
LEA).
- The date of the last modification (non- modifiable field automatically input by
the editor).
- The comment (or label) on the function that produces the BF (optional field).
The Description tab provides a description of the BF.
The BF code tab gives access to the BF code via a text box.
The Inputs tab gives access to information on the BF inputs via a grid. The
following elements are shown in the different columns of this grid:
- The type of variable, example: Boolean, real etc. (mandatory field).
- A comment on its use (optional field).
- A number indicating the position of the input parameter during access to the
BF (optional modifiable field, by default the value starts at 1 and is
incremented in the order of creation of the variables).

The Outputs tab gives access to information on the BF outputs. The different
columns of this grid show:
- A number indicating the position of the output parameter during access to the
BF (optional modifiable field, by default the value starts at 1 and is
incremented in the order of creation of the variables).
The Internal variables tab gives access via a grid to information on the internal
variables of the BF. The different columns of this grid show:
- The name of the array associated to the cursor, if the variable is declared as
being a cursor (modifiable field, mandatory if a cursor).
- A parameter indicating if the variable is specific (PRIVATE: P) to each call or
if it is shared (SHARED: S) on each call by different BF (mandatory field).
The Constants tab gives access to information on the constants of the BF. The
following fields can be consulted and modified:
- A value (mandatory field).
- A comment on the constant represented (optional field).
6.5 Installing a Library
The BF editor is used to edit a library, check its syntax (Check option), create files
used for C compiler tests and install (Install option) the library or not in the
CTOOLKIT for use on target.
6.5.1 Checks
The Check option in the File menu checks the syntax of the FBL file and, if the syntax
is correct, creates the ".h" and ".lib" files used to test the library in the C compiler.
These two files are in the project folder named VC.
While the Check command is being used, a report window opens to show the status
of the syntax check for each FB and the creation of the C compiler files. This
window can only be closed via the close window icon. The Check command can be
stopped but only from this window.
In error messages, the lines indicated are numbered from the start of the library file.
Use the Go to line command and input the line number to display the line that
contains the error.

6.5.2 Installation
Installation corresponds to the creation of the ".h" and ".lib" files for the C8035 and
C8075 controllers. These files have the same name as the library that has created
them. The installation of these files enables one or more BFs in the library to be
used on a chosen controller.
Note : There may not be two BFs with the same name in two libraries installed in the CTOOLKIT.
If the Uninstall command and the Remove command are available in the File menu, the
library is installed.
The files that are installed are independent of modifications to the library. If the files
installed need to be updated, use the Install command in the File menu.
Note : Library installation is common for MFC3000 targets and for the simulator.
The installation of the library is traced in a command prompt as shown below:
The window shows the complete path of the library being installed and lists the BFs
installed or in error one by one. The window can be closed when the installation of
the library is completed.
The Uninstall command is used to uninstall the files generated for the controllers
without deleting the library.
When the uninstallation runs a command prompt opens showing the complete path
of the library. This window can be closed when the uninstallation is completed.
The Remove command is used to delete the library and the files that it has
generated.

The list of libraries installed can be consulted; select the Installed Libraries… option to

Library Indicates the name of the library installed.
Target Indicates the type of target on which the library is
installed. The Simulator indication includes the
MFC3000.
The Close button is used to close the window.
6.5.3 Modifications
If the BFs are updated, this can affect the operation of the Functional Blocks. To
avoid problems it is advisable to extract the Functional Blocks using the modified
BFs and then to reissue them.
The table below shows whether or not extraction / issue is mandatory depending on
the type of modification.
Modifications Extraction - Issue
Input Mandatory
Outputs Mandatory
Variables Mandatory
Code Non-mandatory

Section 7 Controcad Terminology for Variable Exchange Families
In accordance with the principal exchanges for which they are configured, the
variables receive an "exchange family name" that enables them to be characterized
rapidly. The rule for determining this family name takes account of the type of the
transmitting equipment, the type of exchange (HMI or network exchange), the sense
of the exchange and the variable type (Boolean or analog).
Variables associated to the ALSPA System

General rule:
<Equipment_><Equipment type ><1st level format><Variable type><_2nd level
format>
Equipment (optional):
- DI80, DI103
- C8075, C8035, CE2000 and Gemstart equipments are contracted to C75,
C35, C2K and GM.
-
Nature (optional):
ol = Open loop and cl = Closed loop
Equipment type:
in = Process input
c = Controller (integrates cc and fc)

cc = Cell Controller
fc = Field Controller (CE2000 or C8035)
ol = Open loop and cl = Closed loop
ih = Internal HMI, ph = Program HMI, sh = System HMI, dh = Default Hmi.
oh = Operator HMI
Omitted for process inputs/outputs and inter-controller exchanges
1st level format

B = Boolean
A = Analog
M = Multi-state
Omitted for process inputs/outputs
Variable type
DI = Discrete or Digital Input
DO = Discrete or Digital Output
AI = Analog Input
AO = Analog Output
Sig = Signal
Cmd = Command
SPt = Set Point
IC = Inter Controller (integrates UIC, FIC, ICU and ICD)
UIC= Unit Inter Controller
FIC = Field Inter Controller
ICU = Inter Controller Up
ICD = Inter Controller Down
2nd level format (optional):

For Boolean commands: S = Single and D = Double
For analog: I = Integer, D = Double, R = Real and W = Word
E.g.
AI can be specified in C35_AI: C8035 Analog Input
BICU can be specified in C2K_BICU_R: CE2000 Field Controller Boolean Inter-
controller Up in Real format.


ALSPA Control System Controcad V5.3 Configuration of Data Models Reference Manual

Uploaded by

Copyright:

Available Formats

You might also like

ALSPA Control System Controcad V5.3 Configuration of Data Models Reference Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ALSPA Control System Controcad V5.3 Configuration of Data Models Reference Manual

Uploaded by

Copyright:

Available Formats

ALSPA Control System

Configuration of Data Models

ACCESSIBILITY OPERATING & MAINTENANCE MANUAL

DATE 2014-11-14 STAT. CFE - Published

GFR-020C04010-EDC-201149 en B Power/PAC A4 1/92 92

Section 1 Introduction ............................................................................................................ 4

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

1.1 Purpose of the Document

1.2 Important Information

Alstom Power is committed to high quality products in compliance with

Alstom is committed to top customer assistance services.

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

Indicates a situation of imminent danger which, if it is not avoided, will

Indicates a potentially dangerous situation, which if it is not avoided will

Indicates a potentially dangerous situation which, if it is not avoided, may

Indicates a potential electrical danger related to voltages, currents,

Highlights instructions or other important information which must be

Points out important information.

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

The equipment presents dangers to the personnel and to the equipment

RADIO FREQUENCY INTERFERENCE

Most electronic equipment is affected by radio frequency interference

STATIC SENSITIVE DEVICES

ALSPA system equipment contains components sensitive to electrostatic

1.5 Standards & Codes

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

ALSPA Series 6 Distributed Control System (DCS) of Alstom Power.

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

Notation for Signals used in ALSPA Control System.

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

1.7 List of Referenced Documents

[CCAD_INTRO] Refer to the Operating and Maintenance Manuals of

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

The Library tree is accessed via the tab of Controcad.

A library contains a set of application data models. This set is either:

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

3.1 Project Contextual Menu

Description of the options:

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

3.2 Searching for Elements

Click the Find option to open the following window:

Description of the fields:

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

Description of the fields:

3.2.2 Element not found

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

3.4 Importing Libraries

3.5 Issuing Library Elements

Description of the fields:

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

3.6 Extracting Library Elements

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

Description of the buttons:

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

The window includes a tree view and a properties table.

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B

ALSPA Control System - Controcad V5.3 GFR-020C04010-EDC-201149-en Rev.B