byggeri

informationsteknologi

produktivitet

samarbejde

ICT Services specification

Standard specification
F202 e
Sta
nda
rd
s
vice

Pro
ject
Ser
c
hni
Tec

2008-06-30
Translation, February 2009
byggeri

informationsteknologi

produktivitet

samarbejde

bips
Lautrupvang 1 B
DK-2750 Ballerup

Telephone (+45) 7023 2237

Fax (+45) 7023 4237
E-mail bips@bips.dk
Internet www.bips.dk

F202, ICT services specification, bips standard specification - June 2008, translated February 2009

This publication was drawn up under the auspices of bips and bips retains all rights, including the copyright, to the publication
in both printed and digital forms.

This publication is designed to be used by those with technical expertise in the individual disciplines; such use shall in no way
absolve users of the publication of their normal responsibilities. Users of the publication therefore do so wholly at their own
risk, as is the case with individually tailored solutions. Neither bips nor those professionals who have been involved in the
drafting of the publication may be held responsible for how the publication may be applied in practice.

All mechanical, photographic or other reproduction of this publication or parts thereof is forbidden in accordance with
the Danish Copyright Act. The exception to this is short extracts for use in reviews.

Project participants
Steering group bips Coordinating Committee

Project officers
Stig Brinck, NIRAS, project manager
Jens Kirk, PLH architects
Erik Falck Jørgensen, Gottlieb Paludan
Lene Ravnholt, NIRAS
Bent Emil Sørensen, Holm Engberg
Andres Kudsk, NCC
Katrine Fusager, Gentofte Municipality
Thomas Lundsgaard, Rambøll
Kikki Gyldenvang Steffensen, Rambøll
- formerly Universitetets- og Bygningsstyrelsen (Danish University and Property Agency)
Bent Feddersen, Rambøll,

Consultation
F202, ICT services specification, bips standard specification is a part of bips F102, ICT specifications for construction,
instructions, which has been the subject of consultation with construction organisations and bips’ members.

Publication and distribution in digital edition only

bips
Date of issue: 2008-06-30, translated February 2009
1st edition
ISBN 978-87-7293-188-3

Translation
Kurir Sprogservice ApS

2 bips F202 e / 2009-02-28

Contents

Forword 5

Introduction and structure 7

1. Basis 9

2. Digital communication 9

3. CAD 11

4. Electronic call for tenders 13

5. Digital handover 14

6. Other services 15

bips F202 e / 2009-02-28 3

4 bips F202 e / 2009-02-28
Forword

bips has drawn up F102 Byggeriets IKT-specifikationer / F102e, ICT

specification for Construction to replace all CAD- or ICT agreements
up till now.

bips F102e contains among other things this standard specification, which is
aimed to guide the parties of a construction project in completing the construc-
tion process digitally, and to ensure, that each party precisely knows, to which
services, he has committed himself, and which services he may expect from the
other parties.

bips F202e contains Digital services specifications, bips standard specification.

For more information about use of bips standard specification, see bips F102e,
ICT specification for Construction, instructions.

bips F202 e / 2009-02-28 5

6 bips F202 e / 2009-02-28
Introduction and structure

ICT services specification

The specification of digital services for a construction project is composed of the
following two parts:

 a standard specification
 a project-specific specification

The sum of the two parts is the ICT services specification.

ICT Services specifications

bips F202 Project-

Standard specific
specification specification

The Project-specific specification is appended to the relevant contracts for the

construction project, i.e. those contracts that relate to the parties covered by
the digital services. To ensure a common basis between the parties, the same
ICT services specification must be used for all the contracts.

As not all digital services can be defined at the time when the project-specific
specification has to be drafted, subsequent supplements and revisions are
achieved by issuing an updated version of the project-specific specification.

The bips Standard specification is a collection of provisions that function as a

common basis of reference, i.e. regulations that are generally applicable and in-
dependent of the individual construction project.

The bips Standard specification has been drafted so as to provide as

extensive a common basis of reference as possible. The content of the bips
Standard specification is comprehensive and contains frequently occurring regu-
lations. The bips Standard specification may thus contain provisions that are not
relevant to an individual construction project. Relevant
provisions are set out in the project-specific specification.

This principle corresponds to the use of codes of practice, standards, executive

orders etc., as these apply in their entirety even if not all provisions are
relevant.

The bips Standard specification has been drawn up by bips, and only bips is
entitled to update this specification.

bips F202 e / 2009-02-28 7

To avoid confusion as to the current version of the bips Standard specification,
this will not be updated on an ongoing basis.

The bips Standard specification will only be revised when major updates are re-
quired and/or a number of small revisions need to be collated.
As continuous amendments are made to the standard specifications, as a result,
for example, of amended executive orders, standards, instructions, experience
etc., bips will incorporate such updates by entering changes to the bips Stan-
dard specification in the paradigm for the project-specific
specification. The paradigm is available on the website for bips ICT
services specification.

When a new ICT services specification is to be drafted, it is important that it

should always be based on the paradigm for the project-specific specification
on the bips website, such that the specification is up to date, as this paradigm
contains adjustments, updates etc. in relation to the bips Standard
specification.

The bips Standard specification for the ICT services specification is included in
these specification guidelines, and also published independently as publication
F202. The bips Standard specification can be downloaded from the website for
bips ICT services specification by subscribers to the site.

The content of the bips Standard specification is numbered, such that its
contents can be referred to in a simple, straightforward manner.

When an ICT services specification is built up in the same way from project to
project using a Danish de facto standard, communication between the parties
becomes unequivocal, leading to greater productivity and higher quality.

The project-specific specification contains:

 selected items from the bips Standard specification
 any additions to and/or deviations from the bips Standard specification
 project-related regulations

Selected items from the bips Standard specification relate to the extent of
digital services, as services are selected by placing a tick in the project-specific
specification. The provisions associated with the selections are stated in the
bips Standard specification.

Any additions to and/or deviations from the bips Standard specification are the
regulations for the current construction project which amend the provisions of
the bips Standard specification, so that they are in accordance with the
requirements for the construction project concerned. The paradigm for the
project-specific specification sets out framed fields for stating
additions or deviations.

Project-related regulations are requirements that are not covered by the

standard specifications, i.e. services that are to be included, but which do
not form part of the bips Standard specification.

8 bips F202 e / 2009-02-28

1. Basis
(1)
In the case of all parties who act as designers and are required to provide ICT
services, an identical version of the ICT services specification must be appended
to the parties’ contracts for design service.

(2)
The Project-specific ICT services specification takes precedence over this bips
Standard specification.

(3)
The requirements of chapters 2-7 of this bips Standard specification only come
into force if a tick is placed in the ”Selected” field in the project-
specific specification.

(4)
Requirements that apply do so only in respect of data that is exchanged bet-
ween the parties to the construction project, i.e. the parties’ in-house data is
not covered by the agreement.

2. Digital communication
(1)
The parties to the construction project must communicate with each other in
accordance with the construction project ICT technical communications specifi-
cation.

2.1 Scope
(1)
All documents between the parties must be exchanged digitally.

(2)
The documents which have been ticked in the project-specific specification must
be exchanged digitally.

2.2 Communications manager

(1)
The communications manager must:
• prepare and maintain the ICT technical communications specification
and ensure that this is applied to the parties to the construction project,
including the contractors if they are covered by the requirement for
digital communication
• administer the project web, i.e. administer users, rights and folders
• check that all parties to the construction project communicate digitally
in the agreed manner
• hold a start-up meeting, at which the parties to the construction
project jointly review and add detail to the ICT technical
communications specification.

(2)
The communications manager must obtain the client’s approval of the
ICT technical communications specification.

bips F202 e / 2009-02-28 9

2.3 Data structure
(1)
When exchanging documents on a project web, the file and folder structure
must comply with ibb publication 10, March 2003 and bips C212, CAD filer og
mapper 2008 [CAD files and folders 2008].

(2)
On exchange, each document must as a minimum be assigned the
following metadata:
 Title

A short description of the contents of the document

 Status

Status of the file (provisional/current/archive)

• Date

Date of the document

 Organisation

Party responsible
 ProjectID

Unique project identification (bips project ID)

 RevisionID

(3)
Metadata must be added to each document:
 DocumentClassID

2.4 Project web

(1)
All digital exchange of documents between the designers, excluding suppliers
who perform designs, must be via the project web.

(2)
The use of the project web applies to all parties involved in construction.

(3)
The extent of internet and A3 printing facilities on the construction site must be
specified in the construction project specification and/or works specifications.

(4)
The project web must:
 have a user interface which supports the working language of the
construction project
 create a history of documents, users and actions
 be able to show the documents in a particular status group

(5)
The responsibility for providing a project web covers both setting up and opera-
tion throughout the active period.

10 bips F202 e / 2009-02-28

(6)
”Free access to the project web” means that each party is allocated an
adequate number of users and adequate space.

If the parties have to pay to use the project web, the party which provides
the project web is required to list the unit rates to be used by the parties
in their tender calculations.

2.5 E-mail
(1)
E-mails containing exchange of information between the parties to the con-
struction project must be placed on the project web.

(2)
bips C206, E-mail standard for byggeprojekter [E-mail standard for con-
struction projects], must be used.

3. CAD
All requirements to discipline models stated in this standard specification
solely apply to discipline models, that shall be exchanged between parties
in the project.

3.1 General
(1)
The use of CAD on the construction project must be structured in accor-
dance with ICT technical CAD specification for the construction project.

(2)
All parties that act as designers are obliged to make discipline models and
drawings available for use and checking by the client and other parties as
specified in 3.4. The requirements for CAD modelling ensure the exchange
and use of discipline models between the parties to the construction project.

3.2 Project CAD manager

(1)
The project CAD manager must:
 prepare and maintain the ICT technical CAD specification and ensure
that it is applied to all parties who use CAD
 communicate the CAD requirements set out in the tender documents
insofar as the contractors’ deliverables are affected by CAD
requirements
 hold a start-up meeting at which the parties review the ICT technical
CAD specification
 be responsible for overall coordination of the CAD work, including
ensuring that CAD exchange comply with the ICT technical CAD
specification
 ensure that the latest version of the ICT technical CAD specification
is always available to all parties

(2)
The project CAD manager must obtain the client’s approval of the ICT
technical CAD specification.

bips F202 e / 2009-02-28 11

3.3 Production
(1)
When working with building models using 2D geometry, the CAD input consists
of production and exchange of 2D discipline models on the
basis of:
• the bips Lagstruktur [Layer structure], latest version
• the bips CAD manual, latest version

(2)
When working with building models using 3D geometry, the CAD input consists
of production and exchange of both 2D and 3D discipline models on the basis
of:
 the bips Lagstruktur [Layer structure], latest version
 the bips CAD manual, latest version

(3)
When working with 3D models using construction objects, the CAD input
consists of production and exchange of 2D and 3D discipline models using
construction objects on the basis of:
 the bips CAD manual, latest version
 the bips Objektstruktur 2008 [Object structure 2008],
latest version

(4)
Classification must be carried out in accordance with:
 DBK 2006 Results domain 1 - Structure and classification tables for
complexes, buildings and spaces
 The DBK 2006 Results domain 2 – Structure and classification tables
for building elements, Rev. A
 Errata to Results Domain 1 and 2

3.4 The use of CAD models

(1)
If one of the following applications listed in sections 3.4.1 – 3.4.7 is selected,
but no party is stated under ”Performed by”, it means that the party will be
appointed later.

(2)
For those parties who are to provide one of the services listed in 3.4.1 – 3.4.7,
and where several discipline models are to be used, part of the
service will be to ensure correct assembly of the discipline models
into the aggregate model.

3.4.1. Drawing production

(1)
Design drawings are the drawings prepared by the designer. These are not ne-
cessarily suitable for production on the construction site.

(2)
Working drawings are the drawings used for production on the construction
site. Working drawings to be used on the construction site must be legible when
plotted in A3 format. This requirement must be passed on to the contractors
named in the construction project specification and/or works specifications.

12 bips F202 e / 2009-02-28

3.4.2. Simulation

3.4.3. Digital consistency control

3.4.4. Visualisation

3.4.5. Data extracts

3.4.6. Aggregate model

(1)
An aggregate model must be built up from the discipline models prepared by
the specified disciplines. The aggregate model must be updated and maintained
at the specified intervals.

3.4.7. Other uses

4. Electronic call for tenders

(1)
The electronic call for tenders must be carried out in accordance with the ICT
technical tender specification.

4.1 Call for tenders platform/Tendering platform

(1)
A call for tenders platform must be used, onto which the electronic tendering
manager must load the tender documents. The manager must also ensure that
tenderers have access to download the documentation from the call for tenders
platform.

(2)
Tendering must be performed electronically, by the tenderers submitting their
tenders electronically to a tendering platform.

(3)
Procurement of the call for tenders platform/tendering platform with functio-
nality in accordance with the Danish Tendering Act covers both acquisition and
operation.

4.2 Electronic tendering manager

(1)
The electronic tendering manager must:
 prepare and maintain the ICT technical tender specification in
accordance with the ICT services specification completed for the
construction project and ensure that it is applied to all parties
that produce tender documentation
 load the tender documents and updates to them onto the call for
tenders platform
 administer access and rights, including distribution of the tender
documents
 ensure that queries are responded to
 submit the tenders received to the client

(2)
The electronic tendering manager must obtain the client’s approval of
the ICT technical tender specification.

bips F202 e / 2009-02-28 13

4.3 Structure of the tender documents
(1)
Call for tenders and tendering must be classified in accordance with DBK as per
the ICT technical tender specification. The relevant basis is
provided by:
 DBK 2006 Results domain 1 - Structure and classification tables for
complexes, buildings and spaces
 The DBK 2006 Results domain 2 – Structure and classification tables
for building elements, Rev. A
 Errata to Results Domain 1 and 2

(2)
The specifications must be structured and prepared in accordance with bips
B1.000 – Beskrivelsesanvisning, struktur [Specification guidelines, structure].

(3)
The tender documents must include 3D building models which as a minimum
comprise geometry. The scope and content of the 3D building models must be
described in the tender documents.

(4)
The tender documents must contain 3D building models based on construction
objects. The scope and content of the 3D building models must be described
in the tender documents.

4.4 Bills of quantities

(1)
The tender documents must include bills of quantities in which quantities are
listed.

5. Digital handover
(1)
The handover procedure for O&M documentation must be completed in
accordance with the ICT technical handover specification.

5.1 Scope of digital O&M documentation

(1)
O&M documentation for the client must be handed over digitally.

(2)
Only the O&M documentation specified for the client must be handed over
digitally.

5.2 Digital handover manager

(1)
The digital handover manager must:
 prepare and maintain the ICT technical handover specification for the
handover of digital data and ensure that it is applied to all parties who
produce handover data
 ensure that the latest version of the ICT technical handover specification
is available to the parties who produce handover data
 clarify the concepts of data structure and data model with the client

14 bips F202 e / 2009-02-28

 to the extent that contractors must hand over O&M documentation,
ensure that the requirement is included in the project specification
and/or works specifications
 collate, check and hand over the digital O&M documentation to the client

(2)
The digital handover manager must obtain the client’s approval of the ICT tech-
nical handover specification.

5.3 Purpose, format, method and time of digital handover

5.3.1. Data structure

(1)
On the basis of the client’s requirements, the digital handover manager must
specify the data structure in which the O&M documentation must be handed
over.

5.3.2. O&M documentation

(1)
Documents must be handed over in the file format specified and in accordance
with the method stated.

5.3.3. ‘As Built’ documents

(1)
This service consists of the handover of the full ‘as built’ design documentation
digitally. The structure and format must follow the data structure used during
design and construction.

5.3.4. Data model

(1)
Based on the client’s requirements, the digital handover manager must specify
the data model in which the O&M documentation must be handed over.

5.4 Digital snagging lists

(1)
bips C207, Digitale mangellister [Digital snagging lists], must be used to detail
defects.

6. Other services

bips F202 e / 2009-02-28 15

 ISBN nr. 978-87-7293-188-3

16 bips F202 e / 2009-02-28