BVBS-Guideline I Data exchange of reinforcement data I Version 3.

BVBS-Guideline
Data exchange of reinforcement data
Interface description - Version 3.1

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 1
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

This guideline „Data exchange of reinforcement data“ – definition and description of the interface –
was developed with the cooperation of the following construction software companies, rebar machine
manufacturers, rebar shops, construction companies and institutions.

ALLPLAN D 81829 München

AUG.PRIEN D 21079 Hamburg
Dobler GmbH & Co. KG Bauunternehmung D 87600 Kaufbeuren
GLASER Programmsysteme GmbH D 30974 Wennigsen
Institut für Stahlbetonbewehrung e.V. D 40474 Düsseldorf
LENNERTS & PARTNER GmbH D 96450 Coburg
mb AEC Software GmbH D 67657 Kaiserslautern
RIB Engineering GmbH D 70567 Stuttgart
RIB SAA A 1100 Wien
SOFiSTiK AG D 85764 Oberschleißheim
Trimble Germany GmbH D 65479 Raunheim
Unitechnik D 51674 Wiehl
Ed. Züblin AG D 70567 Stuttgart

Publisher:

BVBS - Bundesverband Bausoftware e.V.

Budapester Straße 31
10787 Berlin
Germany

Fon: +49 30 2575 7750

Email: [email protected]
Web: www.bvbs.de

Status: May 2021

BVBS assumes no liability or any other obligation to be derived from this publication. Reprinting, even
in extracts, only with the written permission of the BVBS.

All rights reserved

Copyright 1995 - 2021

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 2
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Contents Page

Contents 3

Foreword 4

Procedure for the exchange of reinforcement data 5

Initial situation 7

Main groups 7

Basic conditions 8

Header block 10

Checksum block 12

Geometry block 13

Spacer block 15

Bar block 16

Coupler block 18

Private block 19

Examples with barcodes - test data 20

BF2D Examples - two dimensional bending shapes 20

BF3D Example - three dimensional bending shape 26

BFWE Examples - helixes and spirals 27

BFMA Examples - reinforcing steel meshes 28

BFGT Example - lattice girders 31

BFAU Examples - spacers and supporting cages 32

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 3
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Foreword

The Bundesverband Bausoftware e.V. (BVBS) published the first version of this guideline for the data
exchange of reinforcement data in 1995. From the beginning, construction software companies, rebar
shops and machine manufacturers, institutions and steel suppliers worked closely together in drafting
this guidline. The publication of the revised version 2.0 followed in 2002. In 2019 significat extensions
were made and version 3.0 was completed. For the present version 3.1, an editorial revision of version
3.0 including additional explanations was carried out.

We would like to thank all those involved in the development of version 3.0 and 3.1 for their constructive
and trusting cooperation. We are happy to take suggestions for the further development of the
guideline.

BVBS - Bundesverband Bausoftware e.V.

Dr.-Ing. Ines Prokop

Geschäftsführerin

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 4
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Procedure for the exchange of reinforcement data

Each data provider/-receiver needs to create only one converter (software).

With the CAD software a bending schedule, in .abs format along side the .pdf format, for the exchange
of reinforcement data, is being produced. The .abs format can be read during the bending process and
it can be transferred to other bending machines.

Example of .abs data with the according bar bending schedule:

BF2D@HjZEICON
Bewehrungslis@rZEICON@i1@p1@l6000@[email protected]@d25@gBSt500S@s175@v@Gl6000@w0@C7
6@

BF2D@HjZEICON
Bewehrungslis@rZEICON@i1@p2@l3000@[email protected]@d14@gBSt500S@s56@v@Gl150@w-
135@l640@w90@l590@w90@l700@w60@l313@w165@l-66@w0@C68@

BF2D@HjZEICON
Bewehrungslis@rZEICON@i1@p3@l4600@[email protected]@d16@gBSt500S@s64@v@[email protected]
@l350@w90@l1630@w90@[email protected]@l1135@w0@C72@

BF2D@HjZEICON
Bewehrungslis@rZEICON@i1@p4@l6700@[email protected]@d20@gBSt500S@s140@v@Gl400@w90@l
[email protected]@[email protected]@[email protected]@l700@w-
37.87@[email protected]@l1350@w90@l400@w0@C92@

BF2D@HjZEICON
Bewehrungslis@rZEICON@i1@p5@l3500@[email protected]@d16@gBSt500S@s64@v@[email protected]@l
[email protected]@[email protected]@[email protected]@l620@w0@C82@

BF2D@HjZEICON
Bewehrungslis@rZEICON@i1@p6@l6100@[email protected]@d14@gBSt500S@s56@v@Gl400@w-
60@l150@w60@l5000@w60@l150@w-60@l400@w0@C90@

BF2D@HjZEICON
Bewehrungslis@rZEICON@i1@p7@l7000@[email protected]@d12@gBSt500S@s48@v@Gl970@w90@l8
40@w90@l1170@w90@l1040@w90@l1170@w90@l840@w90@l970@w0@C77@

BF2D@HjZEICON
Bewehrungslis@rZEICON@i1@p8@l3604@[email protected]@d14@gBSt500S@s56@v@Gl1095@w-
45@l1414@w45@l1095@w0@C83@

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 5
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 6
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Initial situation
Basically, the following requirements are placed on this interface.

The data format should:

• be as flexible and extensible as possible

• only contain data known to the designer (machine neutral)
• be compact (no more than 1000 characters per bending shape)
• also be evaluable without CAD.

Due to the different geometric possibilities, the reinforcement shapes are divided into groups. Each of
these groups is given its own designation. This makes it possible, for example, to decide immediately
at a bending machine for 2D bending shapes whether suitable data is provided without having to
analyze the entire data set. The following identifiers are used.

Main groups
• BF2D two dimensional bending shapes
• BF3D three dimensional bending shapes
• BFWE helixes and spirals
• BFMA reinforcing steel meshes
• BFGT lattice girders
• BFAU spacers an supporting cages

Each bending shape has geometry-independent data (e.g. schedule number, position, quantity, , etc.).
These data are summarized in a header block (block identifier H). The block opening identifier H can
be followed by various numbers of data fields. Each starts with a lower case letter as field identifier
(a…-z) and ends with an “@“ as field end character. The end of the header block is reached when a field
end identifier @ is followed by a capital letter. The order of the data fields within the block is fixed.

The geometry data (block identifier G) follows in another block. This block can also contain various
numbers of data fields. Each data field starts with a lower case letter as the field indentifier (a…-z) and
ends with @ as field end character. In this block the order of the data is also fixed.

The field identifiers used (a…-z) are only unique in conjunction with the block identifier. In block H, for
example, r = schedule number, but in block G r = radius. The set of data is teminated with CRLF (ASCII
13+10).

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 7
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Basic conditions
General convention for the data are:

• ASCII will be used as character code. The character “@” is used as the separating character.
Therefore, the character “@” has to be avoided in the free text.

• All length specifications are in mm – especially, with regard to the desired compactness of
data, the use of decimal places should be avoided for all specifications that already are in
milimeters (diameter and total length in the header block, individual leg lengths or radii in the
geometry block, as well as vectors for three dimensional curved positions).

• All length specifications of the 2D shapes are referred to the outer dimension, analogous to the
printed bending schedule. For the 3D bending shape the length specifications in coordinate
notation refer to the axis dimension. Diameters and radii are inner dimensions.

• All weight specification in kg

• All angle specification in degrees (right angle is 90°). Decimal places may be used.

• Positive values without sign, negative values with preceding “–“ (minus), decimal separator “.“
(dot)

• All field identifiers must be included in the specified order of the block descriptions. The
indicator mus always be specified, even if no value is present.

• Each data set ends with a checksum block as the last block before CRLF.

• Solely for BFMA:

o The basis of all data is a spatial coordinate system. The flat mesh lies in the X-Y plane.
Negative values for X and Y coordinates are not permitted.
o Longitudinal bars are always at the bottom
o X-bars are transverse bars
o Y-bars are longitudinal bars

• Certain postitions cannot be described due to the definition of the reinforcement interface (e.g.
three dimensional curved postitions with radially curved legs). These should nevertheless be
exported. The header block and the cecksum block must be specified here. The geometry block
is not to be specified.
• If the data exchange is done with files, the files have the extention .ABS (General Reinforcement
Interface = German: “Allgemeine-Bewehrungs-Schnittstelle” )
Each line consists of:

Header always 1*
Geometry block optional 1* or
Spacer block optional 1*
Coupler block optional 1*
Rod block n times
Private block optional 1*
Checksum block always 1*

The data of the header, geometry or spacer, private blocks are always valid for all following bar blocks.

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 8
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Definition of segment lengths

Legend:

A basic distinction is made between bends (with standard diameter of mandrel 4*ds) and arches
(with specification of angle and radius). Bends are marked with the bending pin symbol in the picture.

For further explanations of segment lengths see the current version of EN ISO 3766.

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 9
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Header block

H Header block BF2D BF3D BFWE BFMA BFGT BFAU

field description
identificator
j Project number X X X X X X
(optional)
r Schedule number of X X X X X X
the associated
drawing
i Revision of the X X X X X X
associated drawing
p Bar mark / mesh X X X X X X
position/ supply
position
l Bar length [mm] / X X X X X X
mesh length [mm] /
supporting length
n Quantity of reinforcing X X X X X X
bar / mesh/ supply
e Bar mark / mesh / X X X X X X
accessory weight [kg]
d Steel diameter [mm] X X X
g Steel grade e.g. 500S X X X X X
s Diameter of mandrel X X X X
[mm]
m Mesh type e.g. Q188 / X X X
Spacer type /
supporting type
b Mesh width [mm] X
h Lattice girders / X X
spacer or supporting
height [mm]
v Designer (is not to be X X X X X
currently)
a Layer (optional) X X
Numerica, ascending
from bottom to top
t Delta I for staggered X
rebars (optional)
c Group of staggered X X X
rebars (optional)

* All field idenfications permissible for a main group must be completed and in the listed order.

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 10
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

New from version 2.0

• The main group BFGT for the describtion of lattice girders (Gitterträger).
The length (l), width (b) and type are transfered as information.
• The field @a (layer) is required, in addition to the Z-position contained in the bar block, for the
insertion sequence in automatic bar placing machines (automatische Eisenanlagen).
• Staggered rebars:
The field identifier t as indicator for varying lengths and c for the last length.
“c” as indicator for the length of the last bar in the geometry block (c can also be used with
radii)
Note: This assumes a linear division course ( (c - 1)/ t ).
From version 3.1. onwards, it is recommened to specify the varying positions individually. The
field identifier t will still be used to make for the compatibility with version 2.0.

New from version 3.0

• Since non-linear staggered rebars must be described as single items, an indicator is specified
as a group of staggered rebars, by which it is recognizable which single items belong to a group
of staggered rebars. For this purpose, the same indicator is specified in the respective line
items. It is recommendes to use the fixed component of the bar mark.
• New reinforcement group BFAU for spacers and supporting cages.

Notice:
There is only one diameter of mandrel for a bending shape (parameter “s” [mm] defined in header
block). Each bend of the position is carried out with this diameter of mandrel.
If it is necessary to deviate from this value for nominal reasons, the specifics have to be made as
a separate curved element in the bending shape using the “r” parameter in the geometry block (the
radius is always larger than half diameter of mandrel, according to the header block).

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 11
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Checksum block
last block before CR/LF

C Checksum block BF2D BF3D BFWE BFMA BFGT BFAU

field description
identificator
value checksum X X X X X

* The checksum is calculated with the following algorithm (analogous to the checksum calculation
for the calcompplotters)
(IP - 96) +[ ∑ 𝑛
𝑖=1
𝐶𝑖] MODULO 32 = 0

provided that

IP = checksum
n = number of ASCII characters from the beginning of the record up to and including the C of the
checksum block
Ci = The ASCII characters inside the checksum loop.

In FORTRAN, the routine would like this:

ISUM = 0
DO 10 I = 1,N
10 ISUM = ISUM + ICHAR(C(I))
IP = 96-(MOD(ISUM,32)

In C, the routine would look like this:

int i, IP, n; II declare variables

int iSum = 0; II declare variables
char* C = "abcde@C"; II example data

n = strlen(C); II calculate amount of characters

for ( i=0; i<n; i++)
{
iSum += C[i]; II sum ASCII value of the characters
}
IP = 96 - iSum % 32; II calculate checksum

example::

The checksum is to be formed for the character string "abcde@C".

IP = 96 - MOD( (a+b+c+d+e+@+C), 32) 1 a=ASCll(a)=97; b=ASC ll(b)=98,

IP = 96 - MOD((97+ 98+99+100+101+64+67), 32)

IP = 96 - MOD(626, 32) = 96 -18 = 78

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 12
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Geometry block

G(x/y)* Geometry block BF2D BF3D BFWE BFMA BFGT BFAU

field description
identificator
l** Leg length [mm] X X X
r**, *** Radius of bend X X X
w** Angle of the following bend X X X

x**** X-coordinate for 3D- X

reinforcing bars
y**** Y-coordinate for 3D- X
reinforcing bars
z**** Z-coordinate for 3D- X
reinforcing bars

n Number of turns for helixes X

g Helix pitch [mm] X

c Last length staggered rebars X

(only in conjunction with “t”
in the header block)

An empty geometry block G@ or a non-existent geomety block is a special form that cannot be
displayed

Running meter positions (lfm) are specified in the geometry block as a straight bar with total length,
see BF2D – example 10.

The total length of the bended reinforcing bar is calculated from the data of the geometry block, the
length specifications in the header or in the bar is to be ingored.

* Gx / Gy only for bended mesh, can only occure once.

The coordinate system is a tracking coordinate system.
Gx – the X bars are bent.
Gy - the Y bars are bent.

** Always enter the length or the radius first, then the angle. If a reinforcing bar ends without an
angle, a w0@ must be appended. After a radially bent leg, where the inner radius as well as the
angle of the circular arc is specified, the transition into the following leg does not have to be
straight but can also follow with a preceding bending angle. Therefore, to specify the bending
angle, another value can be specified with “w…@” following the angle of the circular arc
(opening angle).

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 13
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

*** The radius is always larger than half diameter of mandrel defined by the header block

**** The dimensions for the three-dimensional curved positions refer to the axis dimension. The
right-handed coordinate system is used for the coordinate system.

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 14
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Spacer block

A Spacer block BF2D BF3D BFWE BFMA BFGT BFAU

field description
indenficator
t Spacer type X X
a First and following distances X X
of the spacer (@a200;500@
values separated by
semicolon)
p Absolute position of the X X
spacers

The spacer block is used for precast concrete units and defines the positions of the spacers on the
reinforcing bar. The spacers can be specified either in the form of

Attype@afirst; following@ or in the form of

Attype@pfirst@psecond@ ... @pn-ter@.

Spacer block and geometry block cannot be included in the same line.

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 15
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Bar block

X/Y/E* Bar block BF2D BF3D BFWE BFMA BFGT BFAU

field (can occure several times)
identificator description
d Bar diameter r [mm] if X
necessary with decimal „.“
attached d for double bar
x** Bar start in X-direction X X X
y** Bar start in Y-direction X X X
l Bar length in [mm] X X
e*** Bar spacing in [mm] X X
w Angle of the bars to the X- X X X
axis,
specification only for E-
block
(X=0;Y=0;E=Indication w
necessary)
z Bar position in Z-direction X X X

The bar block E defines diagonal reinforcing bars.

The angle of the bar block X is always 0°,
the angel of the bar block Y is always 90°,
the angle of the bar block E has to be specified (e.g. @w45)

The Z-position of the reinforcing bar is specified in the field @z. (This is of importance for the insertion
sequence in automatic production)

* Equal bars are combined in a X- or Y- bar block. Bars count as equal, if diameter, starting point
coordinates of the bar and bar length are equal. The space between the individual bars can
differ.

** The coordination system must be chosen, so that the smallest x-value and the smallest y-value
are zero.

*** In order to be able to describe a mesh of identical bars, with varying distances between each
other, but as compactly as possible, the e-parameter is to be defined as followed

In the first part of a X or Y block, the first bar of this block is defined with its location. If this
block includes several bars, the e-parameter follows. The field indentifier is followed by sub-
blocks separated by semicolon, which describes spacing and number in mm,n. mm stands for
the spacing in mm related to the previous bar. n (amount) defines how often the bar is repeated
at this spacing. If n is not specified, n=1.
Notice! Since the first bar is already defined only the amount of distances may be specified, not
the amount of bars.

Example: 8 cross bars d=6mm, L=2500mm, x=100mm, y=500mm, 7*e=400mm

Xd6@x100@y500@l2500@e400;400;400;400;400;400;400@ or
Xd6@x100@y500@l2500@e400,7@

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 16
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Double bars:

Double bars are bars with the same diameter, placed right next to each other. Their position in the bar
direction is not referred to the single bar, but to the common axis between the two bars. In the simplest
case, double bars can be of equal length and both bars have the same initial coordinates. However,
bars of the same length can also be staggered and thus have unequal initial coordinates. Finally, bars
of different lengths with the same or different initial coordinates are possible. In all cases a double bar
is formed from two bars which is treated like a single bar.

A double bar therefore has:

• One diameter
• Two x-values
• Two y-values
• Two lengths

For the description, this means that both values are specified separated by semicolons. The first value
always refers to the first bar, the second value always to the second bar. If the second value is not
specified, the two values are equal.

Examples:

Double bar on full length

Yd6d@x500@y100;100@l4000;4000@e ... @

or Yd6d@x500@y100@l4000@e ... @

staggered double bar

Yd6d@x500@y1100;100@l4000;4000@e .. @

Short additional bar in the field

Yd6d@x1500@y100;1100@l4000;2000@e .. @

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 17
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Coupler block (german: Muffenblock)

M Coupler block BF2D BF3D BFWE BFMA BFGT BFAU

field description
identificator
a Connection method at the X X X
beginning of the bar (in
practice usually the
manufacturer specifications
of the connecting parts)
b Type of connection at the X X X
beginning of the bar ( in
practice usually the
manufacturer specific type of
the connecting parts)
c Indicator of the coupler / X X X
thread at the beginning of the
bar:
• 0 or empty – no
connection part
• 1 – coupler
• 2 – thread
n Connection method at the end X X X
of the bar (in practice usually
the manufacturer
specifications of the
connecting parts)
o Type of connection method at X X X
the end of the bar (in practice
usually the manufacturer
specific type of the connecting
parts)
p Indicator of the coupler / X X X
thread at the end of the bar
• 0 or empty – no
conntection part
• 1 – coupler
• 2 – thread

The beginning and the end of the bar are determined by the data in the geometry block. The first leg
mentioned is the beginning of the bar.

Couplers are included in the outer dimension of the bending form dimension. The leg length specified
in the geometry block may therefore have to be shortened in practice, by a factor depending on the
respective coupler.

Also for threads, the type of coupler to be connected to it later should be specified, since different
coupler require different threads.

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 18
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Private block

P Private block BF2D BF3D BFWE BFMA BFGT BFAU

field description
identificator
This block can be used for X X X X X X
project or company internal
data. The data block must
be terminated with „@“.

As seperator @ is also used in the private block, where @ + uppercase letter must not occur. End of the
private block is @ as for all other blocks.

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 19
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

Examples with barcodes - test data

BF2D Examples - two dimensional bending shapes

As an example the plan 417, index a of the project TestPFD , position 1, quantity 10, diameter 12, grade
B500A and diameter of mandrel 4*ds=48, is used. For a better overview, the data is printed in bold and
the block identifiers are printed larger.

Thus, the header block results as follows:

BF2D@HjTestPDF@r417@ia@p1@l1000@[email protected]@d12@gB500A@s48@v@

BF2D - Example 1:

The geometry block is:

Gl400@w90@l600@w0@
The complete dataset is:

BF2D@HjTestPDF@r417@ia@p1@l1000@[email protected]@d12@gB500A@s48@v@
Gl400@w90@I600@w0@
C72@CRLF
(86 Characters)

BF2D - Example 2:

The geometry block is:

Gl100@w180@l800@w180@l100@w0@
Notice:
In this bending shape, both ends are bended with 180° hooks with 48 mm diameter of mandrel, the total
length is 800 mm.

The complete dataset is:

BF2D@HjTestPDF@r417@ia@p1@l800@[email protected]@d12@gB500A@s48@v@
Gl100@w180@l600@w180@l100@w0@
C71@CRLF (96 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 20
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BF2D - Example 3:

The geometry block is:

Gl100@w90@l300@w45@l424@w-45@l300@w-90@l100@w0@
The complete dataset is:

BF2D@HjTestPDF@r417@ia@p1@l1224@[email protected]@d12@gB500A@s48@v@
Gl100@w90@l300@w45@l424@w-45@l300@w-90@l100@w0@
C82@CRLF
(115 Characters)

BF2D - Example 4:

The geometry block is:

Gl400@w0@r400@w90@w0@l400@w0@
The complete dataset is:

BF2D@HjTestPDF@r417@ia@p1@l1428@[email protected]@d12@gB500A@s48@v@
Gl400@w0@r400@w90@w0@l400@w0@
C79@CRLF
(95 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 21
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BF2D - Example 5 (opening angle):

The geometry block is:

Gl400@w45@r400@w90@w45@l400@w0@

The complete dataset is:

BF2D@HjTestPDF@r417@ia@p1@l1428@[email protected]@d12@gB500A@s48@v@
Gl400@w45@r400@w90@w45@l400@w0@
C93@CRLF
(97 Characters)

BF2D - Example 6 (coupler):

The geometry block is:

Gl200@w0@

The coupler block is:

MaLenton@bA12@c1@n@o@p@

The complete dataset is:

BF2D@HjTestPDF@r417@ia@p1@l200@[email protected]@d12@gB500A@s48@v@
Gl200@w0@
MaLenton@bA12@c1@n@o@p@
C78@CRLF
(96 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 22
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BF2D - Example 7 (thread):

The geometry block is:

Gl150@w90@l200@w0@

The coupler block is

MaAncon@bTTS@c2@n@o@p@

The complete dataset is:

BF2D@HjTestPDF@r417@ia@p1@l350@[email protected]@d12@gB500A@s48@v@
Gl150@w90@l200@w0@
MaAncon@bTTS@c2@n@o@p@
C90@CRLF
(104 Characters)

BF2D - Example 8 (coupler and thread):

The geometry block is:

Gl200@w0@

The coupler block is:

MaLenton@bA12@c1@nLenton@oP13@p2@

The complete dataset is:

BF2D@HjTestPDF@r417@ia@p1@l200@[email protected]@d12@gB500A@s48@v@
Gl200@w0@
MaLenton@bA12@c1@nLenton@oP13@p2@
C88@CRLF
(106 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 23
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BF2D - Example 9 (Staggered rebars):

There are three postitions that belong to one group of staggered rebars.

The complete datasets are:

BF2D@HjTestPDF@r417@[email protected]@l700@[email protected]@d12@gB500A@s48@v@c10@
Gl400@w90@l300@w0@
C65@CRLF
(89 Characters)

BF2D@HjTestPDF@r417@[email protected]@l1000@[email protected]@d12@gB500A@s48@v@c10@
Gl400@w90@l600@w0@
C68@CRLF
(90 Characters)

BF2D@HjTestPDF@r417@[email protected]@l1300@[email protected]@d12@gB500A@s48@v@c10@
Gl400@w90@l900@w0@
C74@CRLF
(90 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 24
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BF2D – Example 10 (Running meter positions - lfm):

The geometry block is:

Gl500000@w0
The complete dataset is:

BF2D@HjTestPDF@r417@ia@p1@l500000@[email protected]@d12@gB500A@s48@v@
Gl500000@w0@
C81@CRLF
(81 Characters)

BF2D – Example 11 (Spacer block):

A straight bar with three type „6“ spacer blocks at position 140 mm, 667 mm and 1194 mm measured
from the start of the bar.

The geometry block is:

At6@p140@p667@p1194

The complete dataset is:

BF2D@HjTestPDF@r417@ia@p1@l1334@n1@d10@gIV@s40@a1@At6@p140@p667@p1194@C
78@

(74 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 25
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BF3D Example - three dimensional bending shape

As an example the plan 417, index a of the TestPFD project, position 1, quantity 10, diameter 12, grade
B500A and diameter of mandrel 4*ds=48, is used. For a better overview, the data is printed in bold and
the block identifiers are printed larger.

The header block is as follows:

BF3D@HjTestPDF@r417@ia@p1@l1500@[email protected]@d12@gB500A@s48@v@

This 3-D reinforcingt bar uses only the coordinate nottation, specifying only the coordinates that
actually change.

The geometry block is:

Gx294@y0@z0@_
x0@y288@z0@_
x0@y0@z288@_
x0@y-288@z0@_
x294@y0@z0@

The complete dataset is:

BF3D@HjTestPDF@r417@ia@p1@l1500@[email protected]@d12@gB500A@s48@v@
Gx294@y0@z0@x0@y288@z0@x0@y0@z288@x0@y-288@z0@x294@y0@z0@
C82@CRLF
(125 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 26
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BFWE Examples - helixes and spirals

Helixes and spirals can be represented with the existing blocks. In the G block, the plane shape is
displayed first, this can be a circle or a polygon. The only requirement is that all angles must be greater
than 0 and the sum of the bending angles must be 360°. Then n and g elements follow in pairs (any
numbers), n=number of turns, g=pitch.

As an example the plan 417, index a of the TestPFD project, position 1, quantity 10, diameter 12, grade
B500A and diameter of mandrel 4*ds=48, is used. For a better overview, the data is printed in bold and
the block identifiers are printed larger.

BFWE – Example 1:

Square column 40/40, reinforcement

340mm/340mm, with 6 turns at both the
base and the top with a pitch of 100 mm
and 12 turns in the middle with a pitch
of 200 mm.

The complete dataset is:

BFWE@HjTestPDF@r417@ia@p1@l32856@[email protected]@d12@gB500A@s48@v@
Gl340@w90@l340@w90@l340@w90@l340@w90@n6@g100@n12@g200@n6@g100@
C69@CRLF
(130 Characters)

BFWE – Example 2:

Circular column with a helical diameter

of 60 cm, with 6 turns at both the base
and the top with a pitch of 100 mm and
12 turns in the middle with a pitch of
200 mm.

The complete dataset is:

BFWE@HjTestPDF@r417@ia@p1@l45398@[email protected]@d12@gB500A@s48@v@
Gr300@w360@n6@g100@n12@g200@n6@g100@
C69@CRLF
(104 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 27
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BFMA Examples - reinforcing steel meshes

BFMA – Example 1 – stock mesh:

As an example the plan 417, index a of the TestPFD project, position 1, quantity 10, stock mash Q257,
length 4000 mm, width 2150 mm, grade B500A is used. For a better overview, the data is printed in bold
and the block identifiers are printed larger.

The header block is as follows:

BFMA@HjTestPDF@r417@ia@p1@l4000@[email protected]@gB500A@s48@mQ257@b2150@v@

The number is in reference to the respective mesh position

BFMA@HjTestPDF@r417@ia@p1@l4000@[email protected]@gB500A@s48@mQ257@b2150@v@
C68@CRLF
(74 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 28
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BFMA – Example 2 – customized mesh:

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 29
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

The customized mesh has the name ZMPDF, with a length of 5000 mm and a width of 3000 mm. In
longitudinal direction it consist of 13 double bars, diameter 6, with partly different spacings and lengths.
In transverse direction, it consists of 19 single bars, diameter 5, with consistent spacing but partially
different lengths.

The data record structure with the same header data set, as the example of the stock mesh, would look
as follows (the values, underlined italic, can be omitted):

BFMA@
HjTestPDF@r417@ia@p1@l5000@[email protected]@gB500A@s48@mZMPDF@b3000@v@
Yd6d@x175;175@y600;600@l4400;4400@e25,1;250,1@
Yd6d@x700;700@y0;0@l5000;5000@e250,9@
Xd5@x500@y250@l2500@e250,1@
Xd5@x0@y750@l3000@e250,16@
C68@CRLF
(209 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 30
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BFMA – Example 3 – bent customized mesh:

If the previous customized mesh should be additionally bent, a geometry block has to be inserted. In
the example the logitudinal bars (Y bars) are to be bent. The diameter of mandrel is consistently 4*ds
= 24 mm.

Welding pattern see BFMA – example 2

BFMA@
HjTestPDF@r417@ia@p1@l5000@[email protected]@gB500A@s48@mZMPDF@b3000@v@
Gyl200@w-90@l2000@w90@l600@w90@l2000@w-90@l200@w0@
Yd6d@x175;175@y600;600@l4400;4400@e25,1;250,1@
Yd6d@x700;700@y0;0@l5000;5000@e250,9@
Xd5@x500@y250@l2500@e250,1@
Xd5@x0@y750@l3000@e250,16@
C73@CRLF
(259 Characters)

BFGT Example - lattice girders

The complete dataset is:

BFGT@HjTestPDF@r417@ia@p1@l2356@[email protected]@mKT80910@h90@a1@Ex10@y300@l2356
@w0@z38@C81@
(85 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 31
 BVBS-Guideline I Data exchange of reinforcement data I Version 3.1

BFAU Examples - spacers and supporting cages

BFAU – Example 1 – Spacers

As an example the plan 417, index a of the TestPFD project, position 1, quantity 5, with a spacer of
2000 mm length and 160 mm height is described. The value of the height h is optional. For a better
overview, the data is printed in bold and the block identifiers are printed larger.

The complete dataset is:

BFAU@HjTestPDF@r417@i@p1@l2000@[email protected]@mDS16@h160@
C68@CRLF
(56 Characters)

BFAU – Example 2 – Supporting Cages

As an example the plan 417, index a of the TestPFD project, position 1, quantity 150, with a spacer
height of 200 mm is described. The value of the height h is optional. For a better overview, the data is
printed in bold and the block identifiers are printed larger.

The complete dataset is:

BFAU@HjTestPDF@r417@i@p1@l1@[email protected]@mDBV-200-L1/F/T@h200@
C88@CRLF
(67 Characters)

May 2021 I Bundesverband Bausoftware e.V. I Budapester Str. 31 I 10787 Berlin I Germany 32