ProVI

What's New in Version 6.0

1 General
1.1 System Requirements
– ProVI 6.0 (64-bit) is available for AutoCAD 2013-2014, 2015-2016, 2017, 2018
and 2019 and for BricsCAD 18 (minimum version 18.2.05) as well. AutoCAD
versions 2013-2014 are supported for the last time.
– The operating systems Windows 10, Windows 8/8.1, Windows 7 and Windows
Vista are supported.
– Either Access (.mdb files) or SQL Server (since version 2008 R2) can be used as
database engine. However, on 64-bit systems a precondition for Access data-
bases is that MS-Office has not been installed in a 32-bit version, because the re-
quired database drivers cannot be installed in this case. Thus the following cases
can be distinguished:
Windows 64-bit, Office 64-bit or no Office: Access or SQL Server
Windows 64-bit, Office 32-bit: SQL Server

1.2 Project Database

– Due to changes in the structure of the databases, the database version number
was increased to 11.00. Opening an existing database converts it to the new-
est version, thus making it inaccessible to older versions of ProVI! That is
why the change to the newest version of ProVI should happen simultaneously for
the whole project team. When exchanging data with external partners, pay atten-
tion that they use the version 6.0 too.
1.3 Survey Module
– The survey module is based on CAPLAN version 4.7. For new features in
CAPLAN please refer to the text file "Caplan.new" in the sub-directory "Caplan" of
the installation directory of ProVI.

1.4 Excel Macro

– New version (3.3) of the macro for importing the output files (.EXC files) to Excel
is provided in the folder "Addins". To install, please read "Readme.txt".
– The reading speed of .EXC files was significantly improved.

1.5 Project Management

– The project list now saves your lastly opened project as well as the position of the
scrolling bar. These two are restored when starting the program and exiting a pro-
ject.
– A more detailed message occurs when the 32-bit version of the database drivers
is installed.
– If the database driver encounters an error when duplicating a database, the pro-
cess is repeated multiple times. This increases the stability of the process, espe-
cially when copying a database with individual large files (>60MB), like raster ter-
rain models.

1.6 Point Clouds

– The processing of point clouds is now at least 50% faster.
– The point cloud needed to have its reference point in (0, 0, 0) in the .DWG. Now,
the point cloud can be freely moved, rotated and scaled.

1.7 Other
– It is now possible to draw solids in BricsCAD.
– The file with symbols for drawing provi.shx was expanded to include additional
special characters like the Euro symbol and different accented characters.
2 BIM
2.1 MOKEDIT – Edit Model Collections
– "Model collection" is a new file type designed as a container of other ProVI files. It
is deemed as the base of the output of objects and serves as a starting point for
different BIM-output.
– A model collection can currently include the following files: ground model, subsoil
model, route, overhead line, drainage, supply lines, vertical and horizontal align-
ment.
– The model collections are listed in the database in the new folder "Model collec-
tions".
– The new program MOKEDIT can be used to create and edit a model collection file
and its list of included files.
– The files included in a model collection generate a list of components, for exam-
ple courses, noise protection poles, kerbs, platform edges, cable ducts, rails,
sleepers, overhead line masts, retaining walls, manholes, pipes, etc.
– The user can specify the level of detail and the color of every component.

– The output can be optionally limited to a specific project area with a polyline. Only
the components lying within the given polyline will be output.
– The calculation method needed for the calculation of solids from cross sections
can be set. For example, given the maximal angle, the interval of calculation will
be denser in narrow curves.
2.2 Attributes
Configuration File for Attributes
– The individual components get their attributes assigned during an output. There
are two types of attributes: fixed and free attributes. Fixed attributes are proper-
ties of ProVI's internal data, which can be automatically derived from the compo-
nents themselves (like stationing of the overhead line mast or the diameter of a
manhole). Free attributes are additional properties which can be defined and filled
by the user.
– The options for fixed and available free attributes can be set in the configuration
file proviatt.cfg. To create a project-specific or user-specific file, you have to
specify a directory for configuration files in the ProVI options. For detailed infor-
mation, please see "Basics – Configuration File for Component Attributes" section
of the Online Help.
– All attributes have a name, level of detail from which the attribute should be out-
put, and format specifications. An attribute can be excluded from export.
– A free attribute can additionally have a list of values (only the values specified can
be selected), a default value, the type (text, integer or real), and a unit (e.g. m, m³,
kg) defined.
– Free attributes exist for model collection, file, and component. The former two can
be edited in MOKEDIT, while the latter in corresponding editor programs.

QPEDIT – Cross Section Editor

– The button "Attributes" in main dialog opens a dialog, where free attributes of a
route can be specified.
– They can be set for each component individually (like noise protection wall masts)
or all components of a group (like noise protection wall).
– They can also be set for individual objects (like noise protection wall right) or all
objects of same type (like all noise protection walls).
– The attributes can be set independently for different stationing intervals.

KANEDIT – Drainage Editor

– Should there be free attributes defined, these are shown in additional columns of
the pipes and manholes lists.
– Each object's attributes derived from object's category are shown in each row
(e.g. pipe, load bearing, manhole cover).
– The free attributes are included in the Excel- as well as in .csv-output.
– The free attributes can be used as filter criteria in KANEDIT and other programs.

LTGEDIT – Supply Line Editor

– Should there be free attributes defined, these are shown in additional columns of
the supply lines and nodes lists.
– Each object's attributes derived from object's category are shown in each row
(e.g. pipe, load bearing, manhole cover).
– The free attributes are included in the Excel- as well as in .csv-output.
– The free attributes can be used as filter criteria in LTGEDIT and other programs.
BPREDIT – Drilling Profiles Editor
– Should there be free attributes defined, these are shown in additional columns of
the supply lines and nodes lists.
– The free attributes are included in the Excel- as well as in .csv-output.

2.3 Component Output

General
– The components are output as solids together with their attributes in different out-
put formats.
– Because the models can be defined in many ways, some solid calculations may
produce an erroneous or even no output. To combat that, the user can select dif-
ferent calculation methods for courses in MOKEDIT. This can be set for different
stationing intervals for individual component types. In case nothing is set, the de-
fault method is used.
– All export programs now take a model collection file as input and can be started
via its context menu in the project browser.
– Because of the known difficulties of other software suites with bigger coordinates,
an optional translation vector can be set in all export programs. Hence the models
can be moved closer to the coordinate origin.
– The level of detail (LOD) can be specified and all attributes with their LOD smaller
or equal (defined in the attribute configuration file) will be output.

MOKZEI – Draw Model Collection

– New program to draw solids in AutoCAD from a model collection file. The compo-
nent type is included in the layer's name.
– Note that drawing big amounts of objects (especially objects with fine granularity
like sleepers or rails) can take a lot of time.
– AutoCAD objects cannot contain attributes. An optional separate .csv-file can be
written which includes AutoCAD-handles to the corresponding objects in the
drawing.
CPIOUT – CPIXML Export
– New program that writes CPIXML files from a model collection.
– The solids together with their attributes are exported in CPIXML format, which can
in turn be read by Desite MD or iTWO, for example.

IFCOUT – IFC Export

– New program that writes IFC files from a model collection.
– The solids together with their attributes are exported in IFC format, which can in
turn be read by various civil engineering programs, like Allplan, Revit, Navis-
works, Desite MD, iTWO, Solibri to name a few).
– The IFC format is still under development for infrastructure objects. Therefore, the
solids are exported as the generic object IFCBUILDINGELEMENTPROXY and
have a IFCPROPERTYSET attached. The property component type specifies the
type of the object in question.
– We recommend using IFC version 2x3 for export as the versions 4 and 4x1 are
not yet (fully) supported by other vendors.
– Horizontal alignments (optionally with stationing jumps), vertical alignment and
digital terrain models can be exported as true infrastructure objects in IFC4x1.

FBXOUT – FBX Export

– New program that writes FBX files from a model collection.
– The solids without their attributes are exported in FBX format, which can in turn
be used by visualization and VR programs, for example.

ATTROUT – Attribute Output

– New program that writes a component list with its attributes from a model collec-
tion in a .csv-file. This is the same file as exported by MOKZEI, only without the
column for AutoCAD-handle.
– The file can be used for checking if all the attributes are correctly set.
Supported Objects
– All volume items defined in a route (like courses)
– Rails and sleepers
– Kerbs and gutters incl. foundation
– Railway platforms
– Cable ducts incl. covers
– Noise protection wall elements (masts, wall elements, foundation, doors)
– Point-like CS-objects (3D block)
– Continuous CS-objects (boundary line must be on layer "PVI_BOUNDARY")
– Overhead line masts (foundation, mast, catenary)
– Manholes and pipes from a drainage or supply line file
– Subsoil layers (as solids or surface models)
– Digital terrain models (as solids or surface models)

Restrictions
– Track strips of type "Slab track" currently cannot be exported.
– Retaining gabion walls can currently only be exported using a user-defined
course.
– Drainage and supply lines components have only a LOD100 representation.
3 Area-Based Subsoil Model
3.1 General
– Until 6.0, the subsoil model could only be defined along an alignment. Now this is
possible also as an area based model.

3.2 Drilling Profiles File

– The basis for the new surface subsoil model is the new drilling profiles file (rec-
ommended file ending: .bpr) located in the directory "Basic data".
– The drilling profiles file is build analogous to the subsoil file (BG<anum>.<ext>)
and contains a list of courses and a list of drilling profiles with their coordinates.
– The list of courses contains additional columns for input of soil class and homog-
enous area. Moreover, free attributes defined in the configuration file proviatt.cfg
can be filled in. This is also included in the old subsoil file.
– A drilling profile is defined by: description, coordinates, elevation of top of soil,
and a list of courses (name and thickness each).

3.3 BPREDIT – Drilling Profiles Editor

– The new program BPREDIT serves for creating and editing drilling profile files.
– Two pages allow for input of the courses and the drilling profiles. Both lists pro-
vide the usual context-menu options (add, delete, set value in all rows).
– The data can be exported to an Excel file or imported from a .csv-file. At import,
both global coordinates as well as alignment-dependent coordinates are possible
(stationing, distance, and elevation difference).
– Drilling profiles can also be imported from the .csv-file from the Geotechnical
module of AutoCAD Civil 3D.
– Should the courses be defined with depth from top of soil of with their thicknesses
can be set in the context menu of the title row.
– At a later point (when calculating the subsoil model) the program automatically
determines the courses from the drilling profiles. Should this action not produce
expected result, so can the user intervene and change their order.
– A function to define the global list of courses is available over the context menu.
The first approximation is delivered by the program (course types can occur mul-
tiple times) and can be adjusted by the user. At the end, all drilling profiles are set
to this list with suitable courses' thicknesses set to zero.

3.4 Subsoil Model

– The new file type subsoil model (recommended file ending ".bgm") is located in
the directory "Ground" and serves analogous to the terrain model file for specify-
ing subsoil parameters and corresponding files.
– The program BGMEDIT serves for creating and editing subsoil model files.
– There are two types available: area based (new, a terrain model and a drilling
profile file) and alignment oriented (old, an alignment and a subsoil file).
– In an area based model, the user can specify how many courses follow the top of
terrain. Other courses will be interpolated between drilling profiles without regard
for the terrain.
3.5 Subsequent Programs
QPEDIT – Cross Section Editor
– In order to use a subsoil model for volume calculation it needs to be referenced in
the "Ground" dialog.
– The cut volumes can be split in separate courses when calculating.

– In areas where the subsoil model in not defined, the volume items are listed under
"Unknown" category.
– If the subsoil courses do not cover the whole area of terrain, one can set (default
unset) to prolong the lines horizontally. If left unset, the volume items are again
listed under "Unknown" category.

QPZEI – Draw Cross Sections

– The bottom lines of courses as well as their corresponding volumes are drawn.
– These lines are drawn on a separate layer, having the color specified on the
"Lines" page or from the drilling profile or subsoil file.
– The lines can optionally have their labels drawn too.

HPZEI – Draw Grading Plan

– Instead of specifying a subsoil file, a subsoil model should now be included.
– When only the drilling profiles should be drawn, one can specify the maximum
distance from the alignment for a profile to still be considered.

DATKONV – Convert File Types

– Convert a subsoil model to terrain model: for each course a separate terrain
model of type "data type 58" (triangulated network) is produced.
– Convert an alignment based subsoil file to a drilling profile file: for each station,
three profiles are produced: one on the alignment and one a specified distance
away on each side of it.
– Convert a subsoil model to an alignment based subsoil file: the stations of the
subsoil file are calculated either by interpolation or by projecting the drilling pro-
files (within a given margin) on the alignment.

Component Output
– As described in Section 2.3, each course of the subsoil model can be exported as
a solid or a surface model with corresponding attributes.
4 AEDIT – Alignment Editor
4.1 Railway and Road Alignments
– It is now possible to edit railway and road alignments simultaneously in AEDIT.
– Trade, guideline and category can be now set in the options for all new elements.
– The trade of existing alignments can now be changed, given the license and that
the alignment is neither a main nor a branch track of a switch. The cant (rail) and
crossfall (maglev) are deleted.
– The user cannot change the trade of an alignment via project browser's context
menu.
– Road alignments can now also have a reference alignment. It is incorporated in
all drawing programs, where the stationing is given from the reference alignment.

4.2 Alignment Dependencies

– The alignment can now be dependent on other alignments, so that a change in
one automatically propagates to the other. Fixed elements can now be defined as
"parallel" and by "station-angle".
– "parallel": The element is set to a certain distance parallel to an element of anoth-
er alignment. The length can optionally be set to equal.
– "station-angle": The element starts at the given station on the other alignment
(point of intersection) with the given angle relative to the alignment's direction.

– The length of coupling and buffer elements can also be specified with a point of
intersection and a provided length, i.e. the element ends a constant distance
away from the point of intersection.
– Transition curves can now be set as parallel to other transition curves.
– When making a parallel alignment, the option can be set to mark all fixed ele-
ments as "parallel" (switches, deviations and compound curves exclusive). If not,
then the elements are produced without the dependencies.
– Additionally, only individual elements and limited stationing intervals can be pro-
duced when making a parallel alignment.
– The function "Dependencies" opens an overview where all the dependencies be-
tween alignments are hierarchically shown. For a chosen alignment, the align-
ment on which it depends as well as the alignment dependent from it are listed.
– In the standard case, for each reference a dependency between the alignments is
saved. However, should this fail (because of a possible dependency clash), only a
reference is saved and an automatic recalculation is turned off. The elements of
the alignment recalculate themselves when the alignment itself is opened in the
editor (this can be turned off in the options).

4.3 Other
– Clothoid elements can now be split, too.
– An alignment can now be split into two alignment segments at any point.
– Drawn parallels to an alignment are now drawn also in switches.
– Direction angle is now also shown at the end of the alignment in the editor dialog.
– There have been some minor changes implemented from the Swiss rail guide-
lines.
– An option now allows to automatically zoom to the newly added alignment.
5 Switches
5.1 DB Switches
– The problems with curved switches, where code checking engineers did not ac-
cept ProVI's calculations, are done. ProVI's switch calculation is now officially
recognized by DB to be correct.

5.2 Tramway Switches

– The parameters for switch blade and switch heating of grooved rails (BOStrab)
are now stored in the switch catalogue. To use it select "End of blade" as con-
struction end in the switch definition.

– Blade constructions can only be placed in straight lines or curves with the switch's
radius. The blade constructions must be continued by other alignment elements in
order to calculate the whole switch. The position of the switch's end results from
the distance between switch end and the frog, which can be specified, too.
– If the construction end of a switch is set to "End of curve" or "End of blade", the
distance of the last continuous sleeper defined in the switch catalogue can be
overwritten.
– A switch heating can be defined for each switch of those switches. Its starting po-
sition is marked with a block that can be defined in the configuration file for label-
ing. The display of the heating can be switched on and off.
5.3 Draw Switches
– The representation of switch triangle and switch hatch can be set independently
for standard switches and for switches based on blade constructions. Regular
switches can be drawn in DB representation or for Switzerland only with a hatch
up to the crossing. For switches with blade constructions the hatch can be drawn
up to the blade end or up to the switch end or blades will be drawn on the left and
on the right track.
– The program ACHSZEI now has the option to switch off the drawing of the align-
ment line and instead it is possible to draw two parallels representing the track's
rails. This makes it easier to generate switch construction sketches.

– The labeling of switch radii was unified. If the switch is completely inside a spiral,
also the middle gets a label. The radii are only numbered if a numbering is neces-
sary for identification, e.g. if multiple spiral sections follow each other.
– Switches, which have a change in curvature from an inner curved switch to an
outer curved switch, now get the label "ICS/OCS".

5.4 Switch Catalogue

– The switch catalogue was updated to the new version of the guideline 800.0120
from February, 2018.
– It is now possible to create user-defined crossings, slip crossings and switches in
clothoids via the program interface. For clothoid switches the branch elements
can be imported from an alignment file.
– All entries in the catalog can now also be copied, user-defined entries can be de-
leted and the category can be changed via drag and drop.
– The sketches inside the dialog now change dynamically based on the parame-
ters. In special cases an extra bitmap can further be selected.
– The switch parameters are listed in a table. Customization of user-defined switch-
es happens directly inside that table.
– The switch catalogue got these new parameters: track gauge, rail shape, mini-
mum and maximum radius in the branch track for inside curved switches, maxi-
mum speed for main and branch track, dimensions of blade constructions and
switch heating and a column for additional attributes.
– Warnings about geometry errors now occur if the track width is not compatible
with the switch or if the main track and the branch track have different track
widths. The difference between the values can be up to 5 mm before a warning
occurs. The tolerance can be modified in the configuration file provipar.cfg.
– Moreover guideline warnings occur, if switches, crossings or slip crossings are
out of the bending borders. This check is done for each guideline.
– Furthermore warnings occur, if the maximum speed is exceeded in main or
branch track of a switch. If the switch type is changed, the speed in the branch
track will be reduced if necessary.
– For better overview the switch catalogue got a new category for switches from the
Obri-NE guidelines of 1984.

5.5 Other
– The algorithm for calculating the position of connecting switches has been opti-
mized, thus solutions can be found better now.
– Connecting switches may now overlap with other switches and crossings.
– Switch numbers are now listed in the alignment element dialog.
6 Catenary
6.1 Overhead Line File
– The overhead line file (OL<anum>.<Ext.>) is saved in the directory "Horizontal" of
an alignment (usually the reference alignment).
– It contains a list of masts, where each mast has a reference to an alignment (usu-
ally the track alignment) and a vertical alignment.
– The position of a mast can be set with coordinates or with station and distance
from the alignment.
– The elevation of the top edge of foundation can be set in absolute elevation or
with the so-called e-value (difference between top of rail and top edge of founda-
tion).
– The angle of mast and foundation can be given relative to the alignment or in ab-
solute values.
– A mast is defined by its type, its foundation type and its top frame type. The avail-
able types are defined in a configuration file that can be changed by the user.
Thus it is possible for the user to define his own types.
– There are currently no customization options available for
– Possible mast types are "angle mast", "flat mast", "concrete mast", X-sided mast,
and "Peiner mast".
– There are no cantilever types available at the moment, but there is an option to
display a simplified standard cantilever.

6.2 OLAEDIT – Overhead Line Editor

– The new program OLAEDIT enables creating and editing of overhead line files.
– A list of masts can be edited using the familiar functions from the context menu.
– Default values for new masts can be set in the options.
– There are functions available to edit foundation, top frame and mast types.
– Masts can be automatically placed along an alignment using a function from the
context menu.
– It is possible to import csv- or XML-files from the software olaCAD.
– The masts are shown in 2D and 3D in the drawing while editing.

6.3 OLAZEI – Draw Overhead Line in Site Plan

– The new program OLAZEI enables drawing of overhead line files in site plan.
– The masts are represented with symbols (blocks depending on the mast type)
defined in the configuration file for labeling, which therefore can be replaced by
user-defined blocks.
– The masts are labeled with their name, type, station, distance and e-value.
– The text labels can be moved to avoid overlapping analogously to ACHSZEI or
KANZEI.
6.4 Subsequent Programs
QPEDIT – Cross Section Editor
– For the representation of masts in the in cross sections one or multiple overhead
line files can be selected in the cross section editor "QPEDIT". The input of those
files can be found behind the button "Domain obj.".
– A mast in a cross section is shown, if there is a track strip in the route file based
on the same horizontal and vertical alignment like the mast in the catenary file.

QPZEI – Draw Cross Sections

– When drawing cross sections (QPZEI), under the property page "Lines" options
for the representation of masts can be modified. The construction parts can be
handled separately here.
DATKONV – Convert File Types
– Conversion of overhead line files to station files: For each mast a station is calcu-
lated and the mast number is used as station text. That could be used to label
masts as special stations in the grading plan.
– Conversion of overhead line files to point files: For each mast a point is created,
whereas an assignment of mast types to point codes is necessary.
– Conversion of point files to overhead line files: For the existing point codes mast,
top frame, foundation and cantilever types can be associated. It is possible to turn
off single point codes for the conversion. The mast number is generated from the
attribute "Company". If the attribute does not exist, the point number will be used.

Component Output
– As described in chapter 2.3 the content of overhead line files is converted to vol-
umetric objects for mast, top frame, foundation and cantilever.
7 QPEDIT – Cross Section Editor
7.1 New Gutter Strips
– There are three new strip types: box gutter, concrete gutter and slot gutter.
– In road design the strips can be used as inner strips. For railway design they can
be used in context of platforms.
– The type is the main characteristic for those strips. All available gutter types can
be found in configuration file proviibk.cfg, i.e. it is possible to add user-defined
types.
– The type definition contains not only the gutter parameters (e.g. width and height)
but also the necessary values to describe the foundation.
– The position of the foundation projection is independent of the type and can be
selected from the options "Inside", "Outside" and "Inside + outside".
– A lateral kerb can de specified for slot gutters.
– If the gutter is located inside a central platform, the calculation method "Intersec-
tion" (to be found in the track transition strip) preserves the crossfall of the two
strips next to the gutter.
– Gutters are treated in the same way as all the other strips in subsequent drawing
and output functions (e.g. draw cross sections, draw route in site plan, etc.).

7.2 Detect Track Alignment in Point Cloud

– The context menu of track strips contains the new function "Track alignment from
point cloud" for calculating points of an existing track out of a point cloud. It is as-
sumed that the route references a ground model of type "Point cloud" and that
there is an approximate alignment for the track strip.
– Based on a given station interval the program calculates the coordinates of both
rail tops from the corresponding cross sections. If the automatic calculation fails
for some stations, the user can determine the rail positions manually in that cas-
es.

– The rail points are used to determine the corresponding alignment points, which
are saved in a point file. The cant values are stored in attribute "Date".
– Horizontal and vertical alignment of the existing track can be derived from the
point file in two ways: creating a 3D polyline and applying the program PLKONV
on it or using the fitting functions in alignment and gradient editor. Finally the cant
values can be assigned to a cant band in the alignment editor.

7.3 Strips
– The sleeper distance can now be set for track strips.
– The sleeper type now contains the length of the sleeper (in track direction) and
3D blocks for the component output of model collections.
– If there is no intersection between the ballast line of a ballast strip with the sub-
grade line, the ballast will now be displayed up to the subgrade width.
– There are new reference points for ballast strips: subgrade and sleeper bottom
underneath the lower rail. This makes it possible to define a vertical dimensioning
for the ballast thickness.
– The asphalt layer between two track strips of type "slab track" can be defined
more flexible now.
– Platform strips provide the new reference point "Front of pavement" for CS-
objects.

7.4 Constructions
– The foundation type of noise protection walls distinguishes piling pipes from drill-
ing piles.
– Note: For existing routes containing noise protection walls the foundation type is
determined by the existence or non-existence of a blinding course (thickness of
blinding course > 0.0 means piling pipe).
– Some new attributes have been added to the type definitions of noise protection
walls (e.g. material).
– Cable duct types are now taken from the configuration file proviibk.cfg, thus it is
now possible to create user-defined types. New geometry parameters have been
added, e.g. cover width, cover height and component length.

7.5 CS-Objects
– The parameter "Block for site plan" for point-like CS-objects was split into two pa-
rameters "2D block" and "3D block". When drawing a route in the site plan (pro-
gram TRAZEI) the first one will be used for options "2D" and "3D" while the sec-
ond one is used for "Net".
– CS-objects will be considered in the component output of a model collection if a
corresponding checkbox is activated on property page "Site Plan". The attribute
"Component type" can be specified there, too.
– For point-like CS-objects the 3D solids contained in the DWG of the 3D block are
used for component output. For line-like objects an extrusion is made based on
the boundary line contained in the block for the cross section representation.
7.6 Other
– Instead of an alignment related subsoil file a subsoil model is now required in the
ground dialog. Therefore it is now possible to reference area based as well as
alignment oriented subsoil models for cross sections display and volume calcula-
tion.
– In the dialog for setting bundling ranges the stations of the current row are now
marked in the site plan with cross section lines.
– The button in the main dialog used for specifying drainage and supply line files
now has the label "Domain obj.".
– The size of the circles, which mark the outer strip points in the cross section
views, can now be set in the options dialog.
8 Export Platforms to Revit
8.1 QPEDIT – Cross Section Editor
– The platform edge types are now taken from the configuration file proviibk.cfg.
User defined types can be saved in a local version of that configuration file. Pa-
rameters were added, which are necessary for the components output of model
collections (e.g. component length).
– The platform edge type "96cm with safety space" was changed according to the
standards of DB Station & Service. The total height was raised from 1.25 to 1.255
meters.
– According to the construction standards of DB Station & Service it is now possible
to add a horizontal and a vertical distance of the pavement from the edge stone
and of a possibly defined kerb at the backside (the default value is 0.004 meters
for both distances).
– At platform strips now a backfill can be defined for the edge stone and it can be
evaluated during volume calculation (property page "Type"). A backfill that is al-
ready defined in the block (e.g. "BSK 76") can be taken into account as well, if in
the block definition an outline on the layer PVI_HINTERFUELLUNG_LIN exists.
– The new strip types box gutter and concrete gutter (see section 7) can be includ-
ed into the platform design.
– For the platform's backside the kerb type "DB - T 5 x 20" (non-raised kerb) and
several angle brackets are available.

8.2 REVITOUT – Revit Export for Platforms

– The program REVITOUT (platform export for Revit) makes it possible to take a
platform planned in ProVI and importing it into a Revit project. It creates a csv-file
from a platform inside a route. The csv-file contains all parameters necessary for
the construction elements (family instances) in Revit.
– Furthermore ta plugin for the import in Revit is provided (see below).
– Central and side-boarding platforms can be exported.
– Besides the edge stones, their foundation and blinding course elements the fol-
lowing components will be exported: pavement, courses, backfill, closure (non-
raised kerb or angle bracket) and drainage (box and concrete gutter).
– For the guiding system objects of type hatching, guiding strip and finishing strip
can be generated.
– The user can change the Revit families used for the export in the configuration file
provifam.cfg. The families of DB Station & Service are set as default families.

8.3 Revit Addin

– In Revit under the tab section "Add-Ins" the addin ProVIToRevit is provided. It is
used to import the csv-files created by REVITOUT.
– Families that are not already loaded in the current project will be loaded automati-
cally and after this all components from the csv-file are placed in the Revit project.

– It is required that the project's basepoint in the Revit project is set to a meaningful
value.
– Additional ProVI objects from the route (e.g. ballast, rails, sleeper, etc.) can be
imported to Revit via an IFC-file. The IFC export settings must contain the inverse
project base point as displacement vector. Inside Revit the IFC-file has to be im-
ported with the command "IFC reference".
– The addin ProVIToRevit is available for Revit Versions 2017, 2018 and 2019.
– For installation a setup is provided in the sub-directory "AddIns" of the installation
directory as well as on the ProVI DVD.
9 Drainage and Supply Lines
9.1 More Detailed Definition of Manholes
– Manholes can now be defined more detailed than before with the drainage editor
KANEDIT. To make this possible multiple new manhole parameters for its com-
ponents like cover, manhole taper or cover plate, manhole structure and lower
part were added.
– The manhole's cover is defined by its shape (round, angular), diameter or length
and width and its thickness.
– A supporting ring (represented by multiple cover rings and bed joint) can either be
defined by a minimum height (positive value or no value) or by a fixed height
(negative value or 0.0).
– A conic manhole taper or a cover plate can be defined, too. The parameters to be
set are height and alignment ("central", "towards alignment" or "away from align-
ment").
– The manhole structure is described by the manhole's shape (round or angular),
diameter or length and width, angle, wall thickness and the allowed heights of the
manhole rings. For the manhole rings a fixed sequence can be set or alternatively
the program can automatically calculate a fitting sequence using the given height
values.
– The manhole's lower part is defined by the parameters height and floor thickness.

– If manholes parameters are not set, appropriate default values will be used.
– During the construction of the manhole the level compensation (difference be-
tween manhole depth and the sum of the heights of the lower part, manhole rings
and cover) is done with the supporting ring, but only if no value or a minimum val-
ue was specified for its height. In case of a fixed height of the supporting ring, the
manhole depth will be enlarged if necessary.
– For option "Block for site plan" a new value "Standard" was added. In this case
the site plan representation (i.e. the block to be used) automatically results from
the manhole dimensions.
– The manhole representation in the cross sections is now more accurate and con-
siders the parameters mentioned above.
– The new features are currently only implemented in the drainage editor. The cor-
responding changes in the supply line editor will follow.
9.2 KANEDIT – Drainage Editor
– Filtering drainage files now also supports a polyline as filter criteria.
– In the context menu of manhole and pipe list there are the new functions "Delete
selected rows" and "Delete with selection dialog". Both should make it easier to
delete multiple objects at once. For example manholes and all connected pipes
can be deleted, which are outside a specific polyline.
– In the function "Insert ditch or hollow from route" it is now possible to update al-
ready existing pipes and manholes.

9.3 KANALHP – Draw Grading Plan for Drainage

– The new dialog "Bars Outline" can be used to define the order of the labeling
bars. For each bar the title can be specified optionally.
– Furthermore the position of the labels at the vertical lines can be set for each bar
(horizontal or vertical, central above the line). Alternatively to using a labeling bar
the labels for manhole values can be placed at the perpendicular lines.
– The parameter dialog "Supply Lines" has been extended. For crossing supply
lines it is now possible to draw perpendicular lines and to label the stations in the
corresponding bar. Furthermore the elevation of the pipe top can be labeled and
the ground line can be chosen as reference line for the label positions.
– The text labels can now be drawn either to the left or to the right of the perpendic-
ular lines.

9.4 KANMAS – Volume Calculation for Drainage

– There are now different methods available for the partition of the excavation vol-
umes into depth ranges. Either the average excavation depth is used (existing
method: for each pipe there is exactly one entry in one of the depth ranges) or
several pipe sections are build (several depth ranges can occur for the same
pipe). Additionally the user can decide whether the volume of a section should be
divided into the relevant ranges or be assigned completely to the range of the ex-
cavation depth.

– The Excel output of pipes now includes also the distances of the manholes from
the alignment.

9.5 LTGEDIT – Supply Line Editor

– Filtering supply line files now also supports a polyline as filter criteria.
– In the context menu of manhole and pipe list there are the new functions "Delete
selected rows" and "Delete with selection dialog". Both should make it easier to
delete multiple objects at once. For example all nodes, which are outside a specif-
ic polyline, are deleted.
9.6 LTGHP – Draw Grading Plan for Supply Lines
– The new dialog "Bars Outline" can be used to define the order of the labeling
bars. For each bar the title can be specified optionally.
– Furthermore the position of the labels at the vertical lines can be set for each bar
(horizontal or vertical, central above the line). Alternatively to using a labeling bar
the labels for manhole values can be placed at the perpendicular lines.
– For crossing supply lines it is now possible to draw perpendicular lines and to la-
bel the stations in the corresponding bar. Furthermore the elevation of the pipe
top can be labeled and the ground line can be chosen as reference line for the la-
bel positions.
– There is a new option which has the effect that in bars for supply lines successive
labels will be united automatically to one label if they have the same values.
– The elevation labeling can now optionally contain both supply line points and in-
terval points.
– The text labels can now be drawn either to the left or to the right of the perpendic-
ular lines.
10 KMLOUT – Google Earth Export
– The new program KMLOUT (Google Earth export) creates a KML- or KMZ-file
based on the selected part of an AutoCAD or BricsCAD drawing. Those files can
be opened in Google Earth. The drawing can be generated with ProVI or other
programs and will not be changed through the export.
– In the export dialog the user first enters the name that will be shown for the data
in Google Earth. Furthermore the coordinate system has to be assigned, that is
the base for the AutoCAD objects. Right now the coordinate systems of the geo-
detic system Caplan and the systems defined in AutoCAD Map3D are supported
(the latter assumes AutoCAD Civil3D or AutoCAD Map3D is used as platform for
ProVI).
– The complete drawing or selected parts of it can be exported.
– It is also possible to export one or several groups of objects. Each group can
have its own export settings and will be displayed in the tree structure of Google
Earth with its group name. Thus each group can easily be switched on and off.
– The drawing elements can either be projected to the ground surface or be export-
ed with true elevation. In addition an elevation offset can be specified.

– The export of faces, lines and texts is optional.

– The option "Project additionally lines on ground" has the effect, that objects which
are hidden by the ground become visible through their boundary lines.
– Please note that a decrease in performance and representation errors can occur
for large amounts of data in Google Earth. Thus it is recommended to export not
too much elements and to omit objects like rails and sleepers.
11 STAHUELLK – Static Envelope Curves
– STAHUELLK is a new program for calculating static envelope curves for rail-bound
vehicles.
– The program can be used in cases where the module HUELLK (calculate enve-
lope curves) cannot be applied, e.g. if a special calculation method is required.
– First the width of the envelope curve is determined for straight lines and curves.
Starting with a basic width (generally half of the vehicle width) an additional value
is added depending of radius and cant. Finally the resulting parallel lines are con-
nected with suitable transitions.

– The additional values are either taken from user-defined tables or calculated with
appropriate formulas.
– The envelope curves are stored in a route of type road using two special lanes
and/or in two alignment files.
– The envelope lines and the resulting face can be drawn, too.
12 New Auxiliary Programs
12.1 IFCIN – IFC Import
– New interface program for the import of IFC files.
– Supported versions are IFC 2x3, IFC 4 und IFC 4x1, whereas STEP files as well
as XML files can be read.
– With IFC 4x1 it is possible to import horizontal and vertical alignments and ground
models.
– Objects with volumetric geometry are currently not converted into ProVI data. In-
stead AutoCAD objects (3D solids) are drawn.

12.2 TXTTAUSCH – Replace Decimal Points with Commas

– New program for replacing points inside real numbers by commas in AutoCAD
text objects.
– Objects of type text, multiline text and block attribute are considered.
– A possible use case is the generation of plans which are compliant with certain
guidelines (e.g. the German RE).
13 New Features
13.1 DATEDIT – Edit Alignment Related Files
– For range files the context menu has a new function for the import of a speed
band from an alignment.
– A gap flag can now be set for certain stations of an alignment-related subsoil file.
– When editing subsoil files courses of drilling profiles can also be deleted via con-
text menu function "Delete course".

13.2 ABER – Alignment Output

– In railway design the Excel output now additionally contains the calculated values
for lateral jerk (if "radial acceleration" was chosen as output format) and 2nd speed
– Messages that result from guideline checking are now primarily sorted by the or-
der of the alignment elements.

13.3 ACHSZEI – Draw Alignment

– Cant labels (railway design) can optionally be placed at the start and end points of
cant ramps (representation according to Swiss requirements).

13.4 TSZEI – Draw Gradient Indicators

– The configuration file for labeling contains a new flag (FLAG_VZ_LNEI_*) for set-
ting options for labeling longitudinal slope values (either based on the direction of
chainage or on the corresponding point of vertical intersection). This enables the
representation according to Swiss requirements.
– Furthermore the configuration file offers new options to label the curve pitch of
vertical curves using the unit mm instead of m (use {VAL_MM} instead of {VAL}).
– The German configuration file for labeling (pvi_label_ger.cfg) has been adjusted
to the guideline RE 2012. Longitudinal slope and curve pitch will now be labeled
unsigned.

13.5 TRAZEI – Draw Route

– Line-like CS-objects, which refer to a line file, are now considered if the line file
contains exactly one line.

13.6 GVMPLAN – Draw Track Demarcation

– The drawing of versed sines is now optional, because it is no longer contained in
the Db guideline 883.
– Base lines and legend texts are displayed for versed sines of vertical alignments.
– The layer structure was re-organized and some text layers have been split. Thus
the created layers are now compatible with DB requirements.
– Symbol labels (name and chainage) are drawn on a separate layer.

13.7 PTEDIT – Point Editor

– The symbol directory contains blocks for the symbols required for the Bavarian
road authorities.
13.8 GELZEI58 – Draw Ground Model of Type DA58
– The drawing of triangles is much faster now.

13.9 GBER – Level Calculation

– An error message is displayed, if a PVI is in an area where the track alignment
exists but the reference alignment does not.

13.10 HPZEI – Draw Grading Plan

– The German configuration file for labeling (pvi_label_ger.cfg) has been adjusted
to the guideline RE 2012. Longitudinal slope and curve pitch will now be labeled
unsigned.
– For supply lines the pipe top elevation can be labeled.

13.11 QPZEI – Draw Cross Sections

– The theoretical ground cut line and the track alignment lines are now drawn on
separate layers.
– For supply lines the pipe top elevation can be labeled.

13.12 TRABUCH – Level Output

– Output is now also available for CS-objects, which are defined through a line file.
– Laying subgrade points can be considered for the level output in railway design.
– The direction angle of the route alignment has been added to the Excel output of
strips and CS-objects.

13.13 MENGEN – Quantity Calculation

– Line-like CS-objects, which refer to a line file, are now considered if the line file
contains exactly one line.
13.14 KNOEDIT – Junction Editor
– Two new edge rounding types are available: "Four-part compound curve" and
"Compound curve with straight line - arc".

– Names and numbering of input parameter have been changed according to the
German RAL guideline.
– The lane width between splitter and edge rounding and the distance between
splitter and the border of the major route can be labeled now.
– Slope wedges and level points can be identified in the dialog by picking the corre-
sponding AutoCAD entity.

13.15 DATKONV – Convert File Types

– Several input dialogs have been updated.
– For the conversion of REB files (data types 45/49/58) into ground models, GAEB
files (data types 30/49/58) are now also allowed.

13.16 ASCIBAHN – ASCIBAHN Interface

– Reference alignments are considered for import and export.

13.17 OKSTRAIN – OKSTRA Import

– The symbol directory contains blocks for the symbols required for the Bavarian
road authorities. The symbols will be automatically assigned during import.

13.18 VERMOUT – Vermesn Export

– The output of switch main points is optional now. If the corresponding checkbox is
not activated, only the switch's start point is considered.
13.19 DBGISIN – DBGIS Import
– If several alignment fragments exist in different coordinate systems, the vertical
alignment will now be assigned to all created alignments.

13.20 DBGISOUT – DBGIS Export

– The output of switch main points is optional now. If the corresponding checkbox is
not activated, only the switch's start point is considered.

13.21 TOPORAILIN – Toporail Import

– When importing XTR files from Toporail the user can now decide which align-
ments should be imported. For example all alignments can be chosen which exist
at the end of a specific building phase. Alternatively all building phases or only the
final state can be considered.
– The import of existing, new and temporary alignments can be switched on and off.
Example: Import all new and temporary alignments which exist at the end of build-
ing phase 3.
– Furthermore it is possible to connect successive alignment fragments (including
the vertical alignments) to one single alignment. This will dramatically reduce the
number of alignments in some cases.

– The branch track geometry of switches will be imported, too. If possible it will be
connected with the following alignment fragments.
– The import of the chainage alignment is optional.

13.22 TRANSF – Coordinate Transformation

– Geographic coordinates (longitude, latitude, elevation) are supported now for
source and target coordinate systems.
– The recalculation of alignments after the transformation is now optional (useful in
cases where the project is only moved to another location).