Technical Information

30/72-8010-14 EN
Composer

Importing and exporting project data

System version 1.45 or higher

Contents:
1 Importing and exporting data tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1 Data import (CSV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 List of importable project design objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.1 Plant areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.2 Function units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.3 Function diagram generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.4 Process points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.5 Process data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.6 Signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2.7 Utilizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2.8 Field devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.9 Channel allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.10 Signal tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.11 Utilization tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.12 Connection diagrams (documents) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2.13 Documents (Word, Excel, HTML ...) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2.14 Marshalling/distribution data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.15 Plant marshalling area plan data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3 Dokument frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.4 Station allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.5 Data export (CSV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2 Binary data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.1 What can be exchanged? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2 Marginal conditions and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.3 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3.1 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3.2 Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3.3 Procedure when exporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3.4 Import procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3.5 Errors and information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.4 Delivery batches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.2 Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.5 Peculiarities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.5.1 Plant diagrams, area and overview diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.5.2 Cubicle layout diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.5.3 Handling exceptions during importing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1 Importing and exporting data tables
Composer provides an exchange of data pertaining to selected project design objects by means of CSV files.
Data is imported centrally via the "Data import" window. CSV files in the formats
• Prodos 2.11 report generator
• Excel CSV file in Prodos 2.x format
• Composer format

can be read.

Special Excel forms can be used to simplify data input or editing in Excel.

For flexible handling of the import process, it is possible to individual set how many header lines are to be skip-
ped during importing and which text delimiters are to be used.

1.1 Data import (CSV)

• Open the Data import (CSV) window

• Select the import file
• Select the CSV file format and the project design object
• Start the import
• Check the import settings
• Column delimiting: character that separates the columns
• Text recognition character: character with which the texts are delimited
• Import from line: suppresses header lines
• Check the preview
• Header lines are displayed in blue. They are not imported.
• Lines that correspond to the expected file structure are displayed in black.
• Lines that do not correspond to the expected file structure are displayed in red.
These lines have to be checked separately to determine whether they contain data for the required input
format.
• Do column headings correspond to column contents?
If not, select a different import format or a different Excel form.
• Are texts displayed without text delimiters?
If not, set the correct text recognition character.
• Import data once all values are displayed correctly.
• Check the import log
• Save (also possible in the Data import window)

Page 2 30/72-8010-14 EN 10/1999

1.2 List of importable project design objects

The following list contains the importable project design objects, broken down according to the CSV file formats.
It has the following structure:
• CSV file format
• Project design object
• Prodos 2.11 report generator
• Function units
• Process points
• Signals
• Utilizations
• Field devices
• Excel CSV file in Prodos 2.x format
• Function units
• Process points
• Signals
• Utilizations
• Field devices
• Composer format
• Plant areas
• Function units
• Function diagram generation
• Process points
• Process data
• Signals
• Utilizations
• Field devices
• Channel allocation
• Signal tags
• Utilization tags
• Connection diagrams (documents)
• Documents (Word, Excel, HTML ...)
• Marshalling/distribution data
• Plant marshalling area plan data

The project design objects are described in two sections.

• Description of attributes

All attributes of the respective project design object that can be imported by means of CSV files are described in
tabular form.

Meanings of some length information in the "Length" column:

"12": a maximum of 12 characters is available for the object designation.

"E: 14": E=power engineering. In power engineering, up to 14 characters are available for the object designation.

"V: 12": V=process engineering. In process engineering, up to 12 characters are available for the object designa-
tion.
• Description of the CSV file formats

To be able to import data in Composer, CSV files must be created for this purpose in which the attributes of the
objects are specified in a certain order, separated by default by a semicolon. A comma or a tab stop can also be
used as the delimiter. The CSV file can be created directly by means of the editor, taking the order of attributes
into account, or with the aid of Excel forms (see chapter entitled "Excel forms").
A further possibility consists of generating the Excel template from Composer. To do this, call up the Data import
(CSV) window. Set the CSV file format and the CSV file type in the window. Generation of the template is started
in the "Options", "Generate template" menu item.

10/1999 30/72-8010-14 EN Page 3

The order of the attributes in the CSV files is described in the form of tables subsequent to the description of the
attributes. In the CSV file itself, the attributes are placed in successive order, separated by a semicolon and wit-
hout a number. The record is terminated by a hard new line (press the Return key), then followed by the new
record. Columns that are not used are shown in italics . These must be indicated by a semicolon in the CSV file.

1.2.1 Plant areas

Attribute: Data type: Length: Remarks:

Plant area string E:8, V:6 Plant area
Order number string 8 Allocation of an order number. If the entry does not exist for an
import operation, then it is created in the library.
Text string 28 Text on the plant area.
Short text string 12

Composer format

Column: Content:
1 Plant area
2 Text
3 Order number
4 Short text

1.2.2 Function units

Attribute: Data type: Length: Remarks:

Order number string 8 Allocation of an order number If the entry does not exist for an
import operation, then it is created in the library.
Author string 20 Project-authorized author of the function unit. Can currently not
be processed and displayed in Composer!
Remark string 300 The first 28 characters can be displayed in the function diagram.
Can currently not be processed and displayed in Composer!
Function unit string E:8, V:6 Mandatory field
Long text string 60 Long text for the function unit.
Planner string 20 Responsible planner of the function unit. Can currently not be
processed and displayed in Composer!
Text string 28 Text for the function unit.
Type string . Fixed entry: "FE".
Short text string 12 .

Prodos 2.x format:

Column: Contents:
1 Text
2 not used
3 Type
4 Order number
5-7 not used
8 Remark
9 Author
10 Planner

Page 4 30/72-8010-14 EN 10/1999

 11 Short text
12-22 not used
23 Function unit

Composer-Format:

Column: Contents:
1 Function unit
2 Type
3 Text
4 Order number
5 Short text
6 not used
7 not used

1.2.3 Function diagram generation

The "function diagram generation" import functions like the "Copy from..." function. This function is described in
the TI "Copying project data".

Attribute: Data Type: Length: Remarks:

1. Process point target string E:13, V:12 Name of the generated function diagram
1. Process point template string E:13, V:12 Name of the template function diagram
2. Process point target string E:13, V:12 Process point name in the generated function dia-
gram
2. Process point template string E:13, V:12 Process point name in the template function diagram
3. Process point target string E:13, V:12 Process point name in the generated function dia-
gram
3. Process point template string E:13, V:12 Process point name in the template function diagram
... ... ...

Composer format:

Column: Contents:
1 1. Process point target
2 1. Process point template
3 1. Process point target
4 1. Process point template
... ...

10/1999 30/72-8010-14 EN Page 5

1.2.4 Process points

Attribute: Data Type: Length: Remarks:

Alias structure name string 10 Relevant only to recipe process points.
Plant area string 15 Allocation of the process point to a plant area.
Drive type string 20 Only in the case of process points of the "drive"
type.
Kind string 8 Sort criterion for process point according to
which selection is possible.
Order number string 8 Allocation of an order number If the entry does
not exist for an import operation, then it is
created in the library.
Author string 20 Project-authorized author of the process point.
Remark string 30 The first 28 characters can be displayed in the
function diagram. Can currently not be pro-
cessed in Composer!
Dimension string 12 Only in the case of process points of the "mea-
surement" type. The entry must exist in the
library.
Function unit string E:8, V:6; Recipe: 2 Allocation of the process point to a function unit.
Long text string 60 Long text for the process point.
Measuring range start float 8 Measuring range start. Only in the case of
"measurement" type process points.
Mearsuring range end float 8 Measuring range end. Only in the case of "mea-
surement" type process points.
Process point string E:13, V:12 Designation of the process point. Mandatory
field.
Planner string 20 Responsible planner of the process point. Can
currently not be processed and displayed in
Composer!
Diagram string 20 Plant diagram on which the process point is
shown.
Text string 28 Text for the process point.
Type string 2 Permissible entries: see table below
Processing string 20 Processing tag of the process point, in accor-
dance with DIN 19227 Part 1.
Short text string 12 .

Permissible entries for type:

German English
Measurement M M
Drive A D
Processing V P
Alarm unit MA AU
Recipe R R

Page 6 30/72-8010-14 EN 10/1999

Prodos 2.x format:

Column: Contents:
1 Text
2 Function unit
3 Type
4 Order number
5 not used
6 Plant area
7 not used
8 Remark
9 Author
10 Planner
11 Short text
12 Diagram
13,14 not used
15 Processing
16 Measuring range start
17 Measuring range end
18 Dimension
19 not used
20 Drive type
21,22 not used
23 Process point

Composer format:

Column: Contents:
1 Process point
2 Text
3 Type
4 Kind
5 Order number
6 Alias structure name
7 Function unit
8 Plant area
9 Diagram
10 Processing
11 Measuring range start
12 Measuring range end
13 Dimension
14 Drive type
15 Short text
16 Planner
17 Author

10/1999 30/72-8010-14 EN Page 7

1.2.5 Process data

Attribute: Data Type: Length:

Aggregate state string 30
Aggressive components string 30
Connection type string 30
Connection form string 30
Design string 30
Overall height string 30
Overall length string 30
Container type string 30
Remark string 30
Peculiarity string 30
Designation string 30
cos phi string 30
Operating density string 30
Normal density string 30
Form of sealing face string 30
Sealing class string 30
Min. diff. pressure string 30
Dimension string 30
DN string 30
Min. pressure string 30
Min. flow rate string 30
Outer diameter string 30
Inner diameter string 30
Type of sealing string 30
Tapping location string 30
External reference string 30
Ex identifier string 30
Ex zone string 30
Fail Safe string 30
Solid component string 30
Humidity string 30
Type of housing protection string 30
Standard device approval string 30
Certified device approval string 30
Rack string 30
Heating/cooling string 30
Insulation thickness string 30
kvs value string 30
Power string 30
Conductivity string 30
Delivery limit string 30
Max. string 30
Max. pressure string 30
Max. temperature string 30
Mech. design string 30

Page 8 30/72-8010-14 EN 10/1999

 Measurement principle string 30
Process point string E:13, V:12
Standard string 30
Local display string 30
PH value string 30
PN string 30
Pipe class string 30
Pipeline No. string 30
Feedback transmitter string 30
Switchgear string 30
Voltage string 30
Type of voltage string 30
Type of actuation string 30
Setting force string 30
Setting location string 30
Setting signal string 30
Setting time string 30
Current string 30
Temperature string 30
Temperature Min. string 30
Environment string 30
Viscosity string 30
Material string 30
Operating principle string 30
Composition string 30

10/1999 30/72-8010-14 EN Page 9

1.2.6 Signals

Attribute: Data Type: Length: Remarks:

Archive template string 12 Allocated archive template. The entry must exist
in the library.
Kind string 6 Sort criterion for signals according to which selec-
tion is possible.
Dimension string 12 For analog signals. The entry must exist in the
library.
Limit (dimension) float 6 It suffices to specify one limit. The second value
limit (percentage) is determined with the aid of the specified measu-
ring range ("MR signal for limit" attribute).
Which limit is imported depends on the percen-
tage/dimension" switch. The value of the other
data field is ignored during the importing opera-
tion because it is calculated automatically.
Long text string 60 Long text for the signal
Measuring range start float 8 For analog signals
Measuring range end float 8 .
Alarm template string 12 Allocated alarm template. The entry must exist
in the library.
Process point string E: 13, V: 12 Process point where the signal is created. The
process point must exist in the system.
"Percent/Dimension" switch string 8 Mandatory field. Permissible entries: PER-
CENT, PHYSICAL. The corresponding limit is
imported depending on the selection.
Signal string E: 6, V: 8 Mandatory field. Signal tag must be defined in
library in the case of user-defined type pro-
ject.
High signal value string 10 Packed Boolean, Analog, Multisignals: status
value
Binary, limit signal: status value if signal=High.
Low signal value string 10 Binary and limit signal. Status value if
signal=Low.
Text string 28 Text for the signal.
Type string 6 Type of the signal.

Prodos 2.x Format:

Column: Contents:
1 Signal
2 Text
3 High signal value
4 not used
5 Limit (percent)
6 Kind
7 Measuring range start
8 Measuring range end
9 Dimension
10 not used
11 Process point

Page 10 30/72-8010-14 EN 10/1999

Composer format:

Column: Contents:
1 not used
2 Signal tag
3 Text
4 Kind
5 High signal value
6 Low signal value
7 Limit (percent)
8 Limit (dimension)
9 "Percent/Physical" switch
10 Measuring range start
11 Measuring range end
12 Dimension
13 Alarm template
14 Archive template
15 Process point

1.2.7 Utilizations

Attribute: Data Type: Length: Remarks:

Long text string 60 Long text on the utilization.
Process point string E: 13, V: 12 Process point under which the utilization is stored.
Text string 28 Text on the utilization.
Utilization string 6 Mandatory field. Utilization tag must be defined in the
library.
Utilization value string 10 Status value

Prodos 2.x format:

Column: Contents:
1 Utilization
2 Text
3 Utilization value
4 not used
5 Process point

Composer format:

Column: Contents:
1 Process point
2 Utilization tag
3 Text
4 Utilization value

10/1999 30/72-8010-14 EN Page 11

1.2.8 Field devices

Attribute: Data Type: Length: Remarks:

Kind string 8 Sort criterion according to which selection is possible.
Order number string 8 Allocation of an order number If the entry does not exist
for an import operation, then it is created in the library.
Process item tag string 6 6 characters in the database, mandatory field.
Code number string 10 The entry must exist in the library.
Mounting position string 12 Can be inserted in the function diagram as additional infor-
Ruplan 7 mation.
Slot string 12 Can be inserted in the function diagram as additional infor-
Ruplan 6 mation.
Long text string 60 Long text for the process item.
Process point string E:13, V:12 .
Position string 6 Position number for the order number.
Text string 28 Text for the process item.

Prodos 2.x format:

Column: Contents:
1 not used
2 Process item tag
3 Code number
4 not used
5 Text
6 not used
7 Mounting position
8 Slot
9 Position
10 Order number
11 not used
12 Process point

Composer format:

Column: Contents:
1 Process point
2 not used
3 Process item tag
4 Text
5 Kind
6 Code number
7 not used
8 not used
9 Location
10 Mounting position
11 Slot

Page 12 30/72-8010-14 EN 10/1999

1.2.9 Channel allocations

Attribute: Data Type: Length: Remarks:

Location string 25 Location of the module or of the device
Module type string 12 Type of the module (P card)
Process item tag string 6 Process item tag of the module or device
I/O component string 12 I/O component, EBT1, not needed in the case of one-chan-
nel assignment
Mounting position string 12 Mounting position of the module
Ruplan 7
Group string 1 Group identification in the case of several coherent lines,
e.g. A
Channel string 4 Module channel, e.g. 13
Process point string E:13, V:12 Process point, e.g. TIC1005
Position (+.) string 12 Slot of the module, e.g. A03
Ruplan 6
Station string 14 Name of the station
St-F string 1 Control character for deleting (C) and separating (T)

Composer format:

Column: Contents:
1 Station
2 Module type
3 Location
4 Mounting position
5 Position (+.)
6 not used
7 not used
8 Channel
9 Process point
10 not used
11 Process item tag
12 Location
13 Mounting position
14 Position (+.)
15 Channel
16 I/O component
17 St-F
18 Group

10/1999 30/72-8010-14 EN Page 13

1.2.10 Signal tags

Attribute: Data Type: Length: Remarks:

Kind string 6 Sort criterion for signals according to which selection is possi-
ble.
Signal string E: 6, V: 8 Mandatory field. The signal tag must be defined in the
library.
High signal value string 10 Packed Boolean, Analog, Multisignals: status value
Binary, limit signal: status value if signal=High.
Low signal value string 10 Only in the case of binary and limit signal. status value if
signal=Low.
Text string 28 Text for the signal. Is stored for the language set in the
Navigator!
Type string 8 Mandatory field. Permissible entry: BINARY, LIMIT, MUL-
TIPLE, PACKED, ANALOG.

Composer format:

Column: Contents:
1 Type
2 Text
3 High signal value
4 Low signal value
5 Kind
6 Signal

On importing, the text for the signal tag (Column 2) is stored for the language that is set in the Navigator! There-
fore, make sure that the desired language is set before importing.

1.2.11 Utilization tags

Attribute: Data Type: Length: Remarks:

Text string 28 Text for the utilization. Is stored for the language set in the
Navigator!
Type string 6 Mandatory field. Fixed entry: SYSTEM.
Utilization string 6 Mandatory field.
Utilization value string 10 Status value

Composer format:

Column: Contents:
1 Type
2 Text
3 Utilization value
4 Utilization

On importing, the text for the utilization tag (Column 2) is stored for the language that is set in the Navigator! The-
refore, make sure that the desired language is set before importing.

Page 14 30/72-8010-14 EN 10/1999

1.2.12 Connection diagrams (documents)

Composer format:

Column: Contents: Length: Remarks:

1 Process point E:13, V:12
2 Drawing number 20
3 UAS 3
4 Sheet number 6
5 Slot 6
6 Mounting position 8
7 Text for the sheet 28
8 Arb. X 4
9 Arb. Y 4
10 Format 12 Format tag (3Q02D) / identifier
11 Diagram type 6 RUPLAN4 / INGRES interface software switch
12 Sort ID 2
13 Rev. ID 2
14 Amendment date dd.mm.yy
15 Rev. name 3
16 Rev. text 20
17 Customer sheet number 12
18 Customer drawing number 20
19,20 not used

10/1999 30/72-8010-14 EN Page 15

1.2.13 Documents (Word, Excel, HTML ...)

Attribute: Data Type: Length: Remarks:

Owner page number string 12
Owner drawing number string 20
Process item tag string 6
File name string 80
Document type identifier string
Document group string 26
Document title 1 string 30
Document title 2 string 30
Customer page number string 12
Customer drawing number string 20
Path string 80
Position (+.) string 12
Ruplan 6
Cubicle (+) string 12
Ruplan 7
Higher-level tag string Depending on the object
Drawing number string 26

Composer format:

Column: Contents:
1 Document type identifier
2 Document group
3 Drawing number
4 Document title 1
5 Document title 2
6 Typ
7 Higher-level tag
8 Process item tag
9 Customer drawing number
10 Customer page number
11 Owner drawing number
12 Owner page number
13 File name
14 Path
15 Control column (D=delete assignment)

Page 16 30/72-8010-14 EN 10/1999

1.2.14 Marshalling/distribution data

This import operation is not possible without prior Ruplan data.

Composer format:

Column: Contents: Length: Remarks:

1 Mounting position and slot (module) 14 Cabinet name and slot
2 Connection 6 Pin designation of the P card
3 Distributor 14 Marshalling distributor
4 Connection 6 Pin designation on the marshalling distributor
5 Process point 14 Process point
6 Extended process item tag 6 Process item tag of the P card with enumerator

This format is used to import (distributor allocations (marshalling/distribution, ..). The distributor type - and thus
the definition of which data field is written to - is specified during the import operation.

1.2.15 Plant marshalling area plan data

This import operation is not possible without prior Ruplan data.

Composer format:

Column: Contents: Length: Remarks:

1 Distributor
2 Connection
3 Text
4 Short text
5 Marshalling point
6 Process point
7 Possibly process item
14 Subdistribution board
6 Pin designation on the subdistribution board
28 Text for the process point
12 Short text for the process point
6 Designation of the marshalling point
14 Process point
6 Process item tag of the P card with enumerator

1.3 Dokument frame

Column: Contents:
1 Document type key
2 Drawing number
3 Page number
4 Document group
5 Text1 for sheet
6 Text2 for sheet
7 Functional Assignment
8 Upper level tag
9 Type
10 Cubicle (+)
11 Slot (+.)
12 Customer drawing number
13 Customer sheet number
14 End user document tag
15 End user page number
16 Creation Date

10/1999 30/72-8010-14 EN Page 17

 17 Change date
18 Creator
19 Originator
20 Inspector
21 Inspection Date
22 Rev. number
23 Rev. name
24 Rev.Text
25 Rev. Date
26 norm
27 Source
28 subsituteFor
29 subsitueThrough
30 text1
31 text2
32 text3
33 text4
34 text5
35 text6
36 Validationname
37 Validationstatus

Page 18 30/72-8010-14 EN 10/1999

1.4 Station allocation

This import serves to create or modify station allocations. This import can also modify program allocations.

Column: Contents: Length: Remarks:

1 Process point function 12 / 14
2 Program name (old) 3
3 Program name (new) 3
4 Station 14
5 Control flag 1 Control flag for separating the station allocation c or C

1.5 Data export (CSV)

Almost all project design data that can be imported can also be re-exported as a CSV file. CSV exports are
always started from an affiliated mask. The respectively selected filter set is exported.
The following table provides information about which mask in Composer the export is started from.

Project design object Application

Plant areas Mask: Plant area / File / Export / CSV
Function units Mask: Function unit / File / Export / CSV
Function diagram generation No export available
Process points Mask: Process point / File / Export / CSV
Process data Mask: Library overview / Project definitions / Process data / CSV report
context menu
Signals Mask: Signal / File / Export / CSV
Utilizations Mask: Utilization / File / Export / CSV
Field devices Mask: Library overview / System definitions / System catalog devices /
CSV report context menu
Channel allocations Mask: Channel allocations / File / Export / CSV
Signal tags Mask: Library overview / Project definitions / Signal tags / CSV report
context menu
Utilization tags Mask: Library overview / Project definitions / Utilization tags / CSV
report context menu
Connection diagrams (documents) Mask: Document / File / Export / CSV
Documents (Word, Excel, HTML...) No export available
Marshalling/distribution data No export available
Plant marshalling area plan data No export available

10/1999 30/72-8010-14 EN Page 19

2 Binary data exchange

2.1 What can be exchanged?

Under the designations Binary Export and Binary Inport, in Composer you find a possibility of exchanging data
between various Composer projects. The word 'Binary' indicates that the exchange format is not a neutral one.
The CSV Export/Import is another possibility of exchanging data.

Version areas are the smallest elements that you can export and import. All areas that are released and which
have been commissioned can also be exported and imported in binary form. This embraces:
• System
• Island
• Station
• Task
• Cubicle
• Process point function

Plant diagrams, area and overview diagrams can also be exported in binary form although they do not exist in dif-
ferent versions (see Plant diagrams, area and overview diagarams).

All areas can only be exported and imported in the planning phase.

2.2 Marginal conditions and restrictions

An area that is to be exported out of a project contains references to parts of the library and to other areas. These
references must be built up again in the target project, i.e. the area must fit into the target project. Therefore,
• data can only be exchanged between projects with the same Composer version
• the libraries in the source and target projects must be at the same level
• higher-level areas in the hierarchy must exist in the destination project before a subordinate area can be
imported.

The sequence when importing is also important wherever there are no hierarchical relationships. To ensure that
a function diagram with program and channel allocations can be imported, the station must be available with
modules and task in the target as otherwise the function diagram will be imported without program and channel
allocations. In the case of the station delivery batch import/export function (see Delivery batches), the correct
sequence is specified automatically. Otherwise, the following sequence is recommended:
• System
• Island
• Station
• Task
• Process point function

Page 20 30/72-8010-14 EN 10/1999

2.3 Operation

2.3.1 User interface

The following mask is used for importing and exporting; the layout only differs with respect to the title (Import or
Export).

A The directory to which the export files are written or from which the import files
are read is selected in this window.
B Here, data from the project is displayed, i.e. the area that is to be exported or
which has been imported.
C Here, all areas that are in the selected directory as files are displayed.

In the top (Composer) and bottom windows (data medium) the respective actions are called up by way of the
context menu. The entries in the window sections can be selected or cancelled by clicking the button.

In the Composer window, the name, version, version number and change date are entered for each element. In
the Data medium window, you also see the export date, the export ID (see Procedure) and the name of the
export file.

2.3.2 Call

The mask for exporting and importing is called up via the Binary Export and Binary Import menu items from the
tools for editing the respective areas:
• from the masks for editing systems, islands, stations, tasks, cubicles, plant identifiers and function identifiers.
• from the Function and System overviews
• from the function diagram editor and the editor for plant diagrams, area and overview diagrams

The import mask only shows the areas in the Data medium window whose type is defined in the call:

Call from the mask: Import from:

System Systems
Island Islands
Station Stations
Function diagram editor Process point functions
etc.

10/1999 30/72-8010-14 EN Page 21

The import mask can also be called up directly from the Navigator by selecting Binary Import. In this case, all
kinds of areas are displayed in the mask and can therefore be imported. If there are many areas, this can soon
get confusing.

In the Station mask, there are also the Export delivery batch and Import delivery batch calls (see Delivery bat-
ches). For plant diagrams, area and overview diagrams there are the Export hierarchy and Import hierarchy calls
(see Plant diagrams, area and overview diagrams).

2.3.3 Procedure when exporting

• Activate the planning phase in the Navigator.

• Select the export areas with the masks, editors or overviews:
• The displayed area can be exported out of an editor
• The marked areas can be exported out of the overviews
• The filtered areas can be exported out of the masks
• The export mask is opened by selecting the Binary Export menu item.
• The directory to which the export files are to be written is selected in the left-hand section of the window.
• The selected areas are displayed in the Composer window, and the selection can also be narrowed down
here.
• Out of the Composer window, the export operation is started by way of the context menu, and all marked
areas are exported and are displayed in the Data medium window.
• Each exported area is stored in a file. The file name is generated automatically and is assigned the ".cex"
extension. The files must be copied to the target system.

2.3.4 Import procedure

• Activate the planning phase in the Navigator.

• The import mask is called out of one of the editing masks or editors by selection of the Binary Import menu
item.
• The directory where the export files are located is selected in the left-hand window section.
• The exported areas in the directory are displayed in the Data medium window (therefore, depending on the
call, only specific areas or all of them). All marked areas can be imported via the context menu.
• If areas already exist in the target project, a query appears asking whether you wish to overwrite the areas.
• The imported areas are displayed in the Composer window. The imported areas can be called up by way of
the Branch menu item in the context menu.

2.3.5 Errors and information

Errors that occur during exporting and importing and some items of information are displayed in a message box.

An import error prevents importing of area. In the event of a severe error, the complete import operation is ended.
This is the case, for example, if a storage error occurs. If normal errors occur, the import operation is continued
with the next area.

Examples of normal errors:

• A higher-level area in the hierarchy is missing (a station is to be imported, but the island has not been created
in the target project).
• An element from the library is not found (the libraries do not have the same level or a project-specific element
is missing in the target project).

Information is displayed whenever an area has been imported, but not with all information (see also Handling
exceptions when importing), for example:
• A function diagram has been imported without channel allocations or without a task allocation.
• It has not been possible to re-establish the bus allocation for an imported station.

Page 22 30/72-8010-14 EN 10/1999

2.4 Delivery batches

2.4.1 Procedure

To transfer larger portions of a project to another project, users must export and import the affiliated areas. The
Export delivery batch and Import delivery batch functions simplify this for partial deliveries. A delivery batch con-
sists of a station, all affiliated P cards, tasks and the function diagrams that are linked to the station by way of
channel or program allocation.

The procedure for exporting and importing a delivery batch scarely differs from normal exporting and importing:
• In the Station mask or overview, a station is selected and the import mask is called up by selection of the
Export delivery batch menu item.
• In the Composer window, all parts of the delivery batch are displayed, and the elements are all selected and
must be exported together to ensure that they are given the same export ID (visible in the Data medium
window). During importing, the parts belonging to the delivery batch are determined via the export ID.
• The directory containing all files of the delivery batch is transferred to the target system.
• The import mask is called up via the Import delivery batch menu item from the Station mask and the directory
of the export files is selected.
• All parts of the delivery batch appear in the Data medium window and can be imported via the context menu.

The same conditions apply to delivery batches as to individual areas. Exporting and importing takes place in the
planning phase. Higher-level areas, in this case the island to which the station belongs, must exist with the same
name as in the source project.

To ensure that a project can be handled in several delivery batches,

• the project must be split up into delivery batches and it is necessary to define which data belongs to which
delivery batch and where the data is edited.
• the process point functions must not exceed delivery batch boundaries
• the stations must not exceed delivery batch boundaries

The first delivery batch is created in the actual project and goes with it to the construction site. Further delivery
batches are created in a copy of the project and are then incorporated into the project on the site by way of
exporting and importing of a delivery batch. Initialisation and repeated loading of Melody is necessary for the new
delivery batch.

2.4.2 Recommendations

The following procedure is recommended if it is planned to handle a project in delivery batches from the very
onset:
• First create a project and define it as the project master.
• In the project master, enter the system structure of the overall project in relation to CMC, CCC, and CCO.
• Release and commission systems, islands and all stations.
• As early as possible, make all project-specific changes to the library, for example project-specific macros, in
the project master.
• Edit delivery batch 1 in the project master. Create a copy of the project master (subproject) for the further
delivery batches.
• Changes to the system structure must always also be made within the project master. They can then be
exported/imported to a subproject. Changes within a station (number of P cards) can be made in the
subproject.

It goes without saying that it is possible to deviate from this procedure and, in some cases, this cannot be avo-
ided either. This may be the case if the system structure is later expanded by further stations. This is then done in
a copy of the project at the project design location and additional steps are necessary:
• To ensure that a new station can be set to the operation status in the project copy, the existing stations in
operation must be set to unlinked in Composer because the project hardware is not available here. In this
respect, authors depend on service support.
• In additonal to importing the delivery batch, it may be necessary to place the station in the cubicle layout
diagram, or the cubicle layout diagram also has to exported and imported (see Cubicle layout diagrams).

10/1999 30/72-8010-14 EN Page 23

2.5 Peculiarities

2.5.1 Plant diagrams, area and overview diagrams

Plant diagrams, area and overview diagrams can be exported and imported by way of Binary Export and Binary
Import. The functions can be called up from the editors for the plant diagram, area or overview diagram and from
the plant identifier and function identifier masks.

Other plant identifiers or function identifiers and process points, signals and utilisations can be entered in these
diagrams. The diagrams are exported with all information that is needed for them to look exactly the same in the
target project as in the source project. If some displayed elements do not exist in the target project, they are crea-
ted with the displayed information (e.g. process points). However, the displayed elements are not also exported
completely.

Plant diagrams, area and overview diagrams can be arranged hierarchically. When a diagram is imported, the
higher-level area must exist.

By means of the Export Hierarchy function, an area including all subordinate areas can be exported and impor-
ted. Similarly to the delivery batch export, the areas exported together are assigned the same identifier (export
ID) and are imported in the correct order by way of the Hierarchy Import.

2.5.2 Cubicle layout diagrams

Just like other versioned areas, a cubicle layout diagram can be exported by means of Binary Export and can be
imported by means of Binary Import. However, the modules displayed in the diagram belong to separate areas
(islands or stations) and are not also exported when the cubicle layout diagram is exported.

When a layout diagram is imported, an attempt is made to restore the allocations from the source project. If the
modules exist in the target project, they are displayed in the imported diagram. Equally, when a station is impor-
ted, an attempt is made to restore the allocations from the source project. Therefore, in most cases there is no
need to export the layout diagram and to import it in order to get the cubicle layout. Only in cases where the
cubicle does not exist in the target project does it have to be exported and imported together with the station.

2.5.3 Handling exceptions during importing

• Island and stations

• When buses are created, the bus name extensions are assigned randomly. Therefore, during the import
process, it may occur that the bus allocation can no longer be restored. In this case, the area is imported
without bus allocations and the bus allocations have to be defined later on.
• Process point functions
• If function units, plant areas or dimensions entered for the import function do not exist in the target project,
they are then created.
• If order numbers entered for the process point function do not exist in the target project, they are trunkated.
• If the program allocation cannot be restored because the task does not exist, the process point function is
imported without the program allocation.
• If the channel allocation cannot be restored because the corresponding modules do not exist or the
channels are allocated, the process point function is imported without channel allocations.
• Cubicles
• The location entered for the cubicle is truncated if it does not exist in the target project.

Page 24 30/72-8010-14 EN 10/1999

10/1999 30/72-8010-14 EN Page 25
Page 26 30/72-8010-14 EN 10/1999
10/1999 30/72-8010-14 EN Page 27
 Hartmann & Braun ABB Automation Products
Industriestraße 28 Höseler Platz 2 Kohlstraße 4
65729 Eschborn 42567 Heiligenhaus 32425 Minden
Tel. (06196) 800-0 Tel. (0 20 56) 12- 0 Tel. (05 71) 830- 0
Fax (06196) 800-11 19 Fax (0 20 56) 12- 56 79 Fax (05 71) 830- 11 05

Subject to technical changes Printed in the Fed. Rep. of Germany 30/72-8010-14 EN 10/1999 ABB