CONCUR IMS implementation

advertisement
CONCUR
Brite EuRam BE96-3016
Concurrent Design and
Engineering in Building
and Civil Engineering
Next
Back
Directory
Return
-1-
Results
CONCUR
Presentation Directory Page
 Project Summary
 Demonstration Scenario
 Information Management System (IMS)
 Ifc Browser
 LexiCon
 Inception Modeller
 Facets (Skanska)
 PlantPower (Fortum Engineering)
 Technical, Commercial and External Exploitation
 External Results
 The Way Forward
Next
Back
Directory
 Partners
 European Commission Project Details and Contact
Return
-2-
 Download area
CONCUR
Project Summary
Next
Back
Directory
Return
-3-
 CONCUR was aimed at exploiting the developments that were made in Product Data Technology
specifically for the construction industry during the mid 1990s. Mechanical, aeronautical, automobile and
maritime engineering were successfully exploiting the STEP advances of the 1980s, AP225 and CIMsteel
had made a start, but here were technologies aimed specifically at the wider construction industry. In
particular, the CONCUR partners wanted to exploit the IAI-IFCs in the processes that were used in the
pre-tender phases of construction.
 The CONCUR partners examined the processes and the information flows with the aim of using ICT
and open standards for integration. The project looked at the project inception stage, the concept design
phase with links to power engineering processes, the scheme design phase and estimating. A common
thread through the project was the desire to use product models and 3D modelling throughout the process
and to move the start of modelling higher up the chain.
 Where possible, established commercial software was used so that the project results could be
deployed for commercial use. Technical assistance was both received from and given to software
vendors. A number of vendors were involved as associate partners and undertook major enhancements
to their software to support the goals of the CONCUR project.
 Technically CONCUR has made major advances in: inception modelling, using web based Information
Management Systems, linking these systems to advanced object oriented Product Data Technology, a
method for PDT model merging, a method for using XML to interface with a PDT database, a metadata
schema for the IAI, a set of derived attributes for the IAI-IFCs, driving forward the creation of a lexicon
of construction terms which will support the needs of both PDT and eCommerce for construction,
showing that IFCs can be used for storing models as well as exchanging them, and in methods for
browsing and adding to the the contents of IFC models.
 CONCUR has helped to move the IAI-IFCs closer to widespread use by using them on industrial
information and by critiquing the IFC translators developed by the major vendors of modelling systems.
 CONCUR has demonstrated that IFCs can integrate the processes of different companies using different
software applications being used for different purposes.
 CONCUR partners are deploying the results commercially and have a clearer vision of how to
profitably extend the use of PDT further into their businesses.
 CONCUR has identified weaknesses and gaps in these technologies and has helped initiate work to
improve and strengthen them – The Way Forward.
CONCUR
Industry Need- Why Undertake the project?
 Client Demand
 Clients are demanding: higher quality, greater predictability of time and cost, faster project delivery,
better documentation and better value for money.
 Market Differentiation
 The construction industry needs: greater involvement in client planning, faster response to client
requirements, better defined processes and MOST OF ALL SATISFIED delighted clients.
 Increasing Regulatory Drive
 Society is expecting: increased safety, improved sustainability, reduced energy consumption, reduced
waste, greater accountability and better documentation.
 Quantifying Risk
 The construction industry needs to: reduce the cost of tendering, improve the accuracy of tenders and
quickly quantify the risks associated with a new project.
 Integrate the Extended Enterprise
 The construction industry needs to: integrate the use of information in a dynamic supply chain, support
concurrent working in the supply chain, speed up the processes supporting tendering.
Next
Back
Directory
Return
-4-
CONCUR
Initial Aims & Goals
 Halve the cost of tendering
 Speed up the processes supporting
tendering
 Improve the accuracy of bids
 Integrate the processes
 Integration of information use
Next
Back
Directory
Return
-5-
 Support concurrent working
CONCUR
Project Tactical Approach
 Review Industrial Practice
 The partners rigorously examined the processes undertaken by commercial construction organisations
when preparing a bid. The results were presented in the form of IDEF0 diagrams with notes. The
processes include: client brief, inception design, concept design, scheme design and preparing estimates.
 Implement File based Architecture for Tendering
 CONCUR prepared a mid-term demonstration which linked the software applications using file tranfers
between the applications. The transfer files used comma separated variable, STEP Physical files (IAIIFC). STEP Data Access Interface was also used. This demonstrated that interoperability was possible
but was not commercially robust and flexible.
 Implement Client/server based Architecture for Tendering
 The second half of the project concentrated on using a web based IMS system to support realistic
exchanges including an integration with a STEP database to provide a model server. Significant advances
in using IFCs were also made. The results demonstration supported a realistic business scenario and is
described in this web site.
 Implement Enhanced Production Software Applications
Next
Back
Directory
Return
-6-
 The project encouraged the development of IFC translators by major software vendors to the industry,
encouraged the enhancement of existing software to support the new ways of working required by the
CONCUR partners, initiated the development of new commercial software applications to support the new
ways of working and created prototype software for inception modelling and browsing IFC information
models. New approaches for capturing and manipulating construction industry terms were also initiated.
 Deploy in Trials
 The CONCUR industrial showed a realistic exchange in a demonstration and are starting to implement the
technology in their businesses. Taylor Woodrow are using the approach in their supply chain to integrate
with architects, structural designers and steelwork fabricators; Fortum Engineering are integrating their
internal use of information and Skanska are implementing an integration of 3D modelling, cost estimation
and time programming systems using information from a company database of resources.
European Commission
Project Details and EC Contact
Next
Partners
Back
Directory
Return
-7-
CONCUR
Project Number
Contract Number
Start date
Duration
Finnish date
Man years
Value
Concurrent Design and Engineering in Building and Civil Engineering
BE96-3016
BRPR-CT96-0357
1 February 1997
4.5 years
31 July 2001
30 for eight partners
5 454 000 Euros
Co-ordinating Partner
Project Manager
Taylor Woodrow Construction Ltd.
David Leonard
EC Project Officer
Maria Cristina MAROLDA
European Commission
Research Directorate-General
Competitive and Sustainable Growth
E-mail
Phone
Fax
Mail
Address
maria-cristina.marolda@cec.eu.int
+32 (0)2 295 83 91
+32 (0)2 296 05 50
Rue de la Loi/Wetstraat 200, B-1050 Bruxelles/Brussel
Rue Montoyer/Montoyerstraat 75, B1050 Bruxelles/Brussel
Project Partners
Construction Companies
Classification
Next
Back
Directory
Return
-8-
R & D Partners
CONCUR
Demonstration Scenario
The CONCUR project included demonstrations of
technology using commercial software and
realistic industrial information.
 Description
 Photograph of the Demonstration Building
 The Business Scenario
 The information Flows
Next
Back
Directory
Return
-9-
CONCUR
Demonstration Scenario Description
 The demonstration scenario covers the activities in the process of moving from a client brief to
preparing a bid for the building to house the steam powered turbine/generator for a small power station.
 The demonstration mostly uses commercially available software applications and generally uses IAI
IFCs for transferring and storing building and construction objects between partners and their software.
 Fortum Engineering perform the role of the principal contractor who undertakes the plant design with
alternative solutions from civil engineering contractors.
 The demonstration scenario includes:
 Inception Design
 Concept Design
 Scheme Design
 Programme Planning
 Preparing Cost Plans
 The innovations include:
Business Scenario
Next
Back
Directory
Return
-10-
 Using IAI-IFCs for exchanging information
 Using IAI-IFCs for storing information
 Using a web based IMS which includes an IFC model server
 Using a web based browser for viewing and using IFC objects
 Using an XML interface for interfacing with IFC models
 This presentation shows the business activities being addressed, the information flows between the
activities and further information on the activities which can be accessed by clicking on the activity
boxes or information flow lines.
 A power station typical of that used in the demonstration shown on the photograph with the Turbine
House ringed.
Demonstration Object
Turbine House
Fortum Engineering
Turbine house
Next
Back
Directory
Return
-11-
Business Scenario
Define INCEPTION
TURBINE BUILDING
T.U. Delft
Inception Modeller
Taylor Woodrow
Define
SCHEME
T- building
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
FE Software
Business Scenario Description
Information
Next
Flows
Back
Directory
Return
-12-
Fortum Eng.
Scheme modeller
Fortum Eng.
MERGE TW
models
Model Merger
Fortum Eng.
Define
COMPARE
CONCEPT Turbine
BUILDING
suggested
models and
CHOOSE one
FE Software
Skanska
Fortum Eng.
Define
SCHEME
T- building
MERGE Skanska
Scheme modeller
models
Model Merger
Bid
CONCUR
Business Scenario Description
 A flow diagram showing the business scenario for the CONCUR demonstration.
 A client needing a power station approaches Fortum Engineering for a solution and a bid.
 Fortum Engineering will be the principal contractor responsible for the delivery of the complete power
station.
 Fortum Engineering undertake the design of the plant and equipment in the power station.
 Fortum Engineering invite Taylor Woodrow and Skanska to bid to design and construct alternative
solutions for the Turbine House building.
 Fortum Engineering merges each of the competing alternative solutions for the Turbine House with
the plant and equipment scheme before choosing one.
 Fortum Engineering prepares the bid for the client.
.
Next
Back
Directory
Return
-13-
Information Flows
Client Brief
TU Delft
Bid
Define Building
INCEPTION
MODELLER
TUD Software
Fortum Eng.
Taylor Woodrow
MERGE TW
Define
SCHEME
T- building
Fortum Eng.
Fortum Eng.
Design
models
Fortum Eng.
Model Merger
IFC Browser
COMPARE
suggested models
and CHOOSE one
Define
CONFIGURATION
for Steam Turbine
Plant
Scopepower
CONCEPT Turbine
BUILDING
TW IMS
PlantPower
FE IMS
Skanska
Fortum Eng.
Define
SCHEME
T- building
MERGE Skanska
models
Model Merger
FACETS
SK IMS
Next
Back
Directory
Return
Web based
Project IMS
Project IMS - I
ProjectWise
Project IMS - III
Project IMS - II
IFC
FE1
Project IMS
EPM-EDM
-14-
IFC
FE1
IFC
IFC
SK1
TW1
Project IMS
SK1 TW1
FE1
IFC
FE1
IFC
SK1
IFC IFC
FE1+
TW1 SK1
Project IMS- IV
IFC
FE1+
TW1
Project IMS
FE1 +
TW1
FE1 +
SK1
IFC
FE1
IFC
SK1
IFC
TW1
IFC
FE2
Project IMS
CONCUR
Client Brief
 Determining the client brief is a key role for the principal contractor. The client does not always know
how to do this and usually requires assistance to do this. The client will have a business plan within
which the new project will perform in terms of finance, operating costs, generating revenue and
delivering a profit. The client requires input from the supplying contractor to support his business
plans.
 When the client brief is fully understood and agreed by the client and supplier, the supplier can
develop the scheme and prepare a bid and programme for delivering the project.
 There are systems for capturing client requirements and recording requirement revisions and the
supplier response options. One such system is called Dynamic Object Oriented Requirement
System (DOORS). This system was trialled in the first half of the CONCUR project and featured in
the Mid Term Review Demonstration. DOORS, from Telelogic UK Ltd, can support the whole life
cycle of a project. The mid term trial showed how information exported from DOORS could be
imported into corporate systems
Next
Back
Directory
Return
-15-
 The development of the client brief takes place concurrently with the Inception modelling of a project,
the assessment of risk to the supplier and the effect on the potentially new project on the supplier
business plan. Currently information is manually transferred between client brief and into inception
modelling.
CONCUR
Inception Modeller
Inception Modelling
 The developing of an Inception Support Modeller was one of the most research oriented parts
of the CONCUR-project. At the start of the project it was quite clear that the inception stage
of large-scale construction projects involves a number of heavy and interrelated information
processing tasks. Clients have to establish the feasibility of the project. Facility designers
and construction companies have to decide how to meet the client requirements. This means
that in a relatively short period of time a tremendous amount of not well defined information
and knowledge related to all the aspects of power plants has to be processed.
 It was quite clear that an Inception Support Modeller could be quite beneficial and potentially
could help to support the projects goals.
 It was also known that, in principle, Product Data Technology could also be used in the
inception and concept design stages where the information is normally less precisely defined.
 The solution implemented in the CONCUR-project focuses, as an example, on the
international power plant market.
 The main characteristics of the approach implemented in the project are (1) the adoption of a
three level approach and (2) the application of a hierarchy of power plant objects divided into
functional and technical perspectives.
Next
Back
Directory
Return
-16-
 The three level approach, illustrated on the next screen, supports the work of the clients, power
plant vendors and construction companies in one dynamic system. Changes in requirements can
flow down stream to be solved, and changes in power plant solutions of construction solutions can
flow up stream to be evaluated, thus the dynamic system allows for non-monotonic design.
 The functional-technical object hierarchy supports the consistent modelling of knowledge in the
form of rules of thumb.
 Many of the ideas and solutions explored in the Inception Support development tasks have
found their way to the industrial partners.
CONCUR
Inception Modeller
The three Level approach
market situation knowledge
power plant knowledge
Win, Design
and Realize
Power Plant
Project A0
power plant project
construction knowledge
Further information
Next
Back
Directory
Return
-17-
 Reports describing the CONCUR Inception Modelling work are available in the Download
Area.
 Contacts at TU Delft are Professor Frits Tolman: F.Tolman@CT.TUDelft.nl and Saban
Ozariyildiz ozsariyildiz@ct.tudelft.nl
CONCUR
The importance of Inception Modelling
 Why Inception Modelling?
 Inception modelling is a neglected phase of construction projects even though it is a key activity. It is
always done but tends to be a stand-a-lone manual process. CONCUR has looked at how company
knowledge can be collected and presented to produce initial estimates. The work has not been
integrated into the information flow.
 Initial Assessment of Projects
 Inception modelling takes place when preparing the client brief and results in a first assessment of cost,
programme, resource requirement, cash flow and financial risk and ultimately whether or not a
supplying company wants to proceed. It could easily interface with corporate financial and risk planning
systems. It is potentially a customer facing tool as follows:
 Interface with Customers
 Inception modelling can be used to support the client in his business planning because it can give him
information required to help assess the viability of a project, namely: Initial cost, time to complete, cash
flow to first revenue, key figures such as floor area, maintenance cost, operating cost. When combined
with his estimate of revenue potential , based on for example floor area, it can support his business
planning.
 Initiation of Contractor Downstream Processes
Next
Back
Directory
Return
-18-
 Inception modelling is a knowledge based process requiring access to company data on costs and
planning. It is difficult to undertake in a generalised way and in concur was limited to numerical
modelling , but without shape. However, it could be developed to first-guess the information required by
downstream processes such as estimating and programming, and even be used to propose a model for
structural engineering design and analysis. This would provide an easy route into starting the use of 3D
modelling on a project and the first stages of 3D visualisation
 Scope for Development
 A number of the CONCUR partners have realised the potential of linking Inception modelling to Product
Data Technology and plan to undertake further development.
For information contact Professor Frits Tolman: F.Tolman@CT.TUDelft.nl
Plant configuration
TU Delft
Client Brief
Define Building
INCEPTION
MODELLER
Taylor Woodrow
TUD Software
Define
SCHEME
T- building
Fortum Eng.
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
FE IMS
Next
Return
Project
database
-19-
MERGE TW
models
Model Merger
Fortum Eng.
Define
COMPARE
CONCEPT Turbine
BUILDING
suggested
models and
CHOOSE one
FE
SW
FE Software
FE Software
Back
Directory
Scheme modeller
Fortum Eng.
Skanska
Fortum Eng.
Define
SCHEME
T- building
MERGE Skanska
Scheme modeller
models
Model Merger
Bid
CONCUR
Fortum Engineering: PlantPower
 Fortum Engineering use a suite of software called PlantPower
which have been customised for the purpose of defining the
requirements for power plant construction. The design procedure
is:
 Scoping Module
 In order to meet clients requirements, a scoping module called ScopePower is used for identifying a structure of power
plant delivery. This is a logical layout based on KKS code, forming a skeleton of the information technical product model
for further study
 Energy Balance
 Energy balance studies are made by Fortum Engineering’s process simulation tool Solvo. These results are defining
requirements for power plant processes as input data for further design
Back to
Information
Flows
PlantPower
Flowchart
 Energy Balance Flow Charts
 In practice it means, that there is unambigious dependence between energy balance flow charts and IT product model
 Design Rules
 A knowledge module holding design rules, design dialogues, plant scope and and artificial intelligence facility based on
Design++ is used for initial dimensioning of main equipment in order to fulfil process requirements. The results are
presented in the main flow diagram.
 Dimensions
 Dimensioning of main equipment continues for over all dimensions of the site so, that suitable plant layout can be
selected. The first cost estimate is carried out in order to support decision making at investment level
Next
Back
Directory
Return
-20-
 Cost Estimation
 Knowledge modules support more detailed design on steam turbine plant. Cost estimation on facility level will define
costs accurate enough for tendering purpose. Actual cost data is in cost libraries of CostPower, where the commercial
software of CM-Pro is used on cost estimation and further budgeting during pre-tender phase
 Company IMS
 All design, cost estimation and scheduling information are stored in product model and in the attached relational
database. In the CONCUR demonstration data was exchanged with IFC files between project partners: Fortum
Engineering, Taylor Woodrow and Skanska
Plant configuration and layout
- CONCUR / Fortum Engineering demonstration
Invitation
to Tender
Scope
LOGICAL LAYOUT
Energy
balance
PLANT CONFIGURATION
PLANT LAYOUT
Main Equipment
CostPower
FACILITIES
1st Cost Estimate
Cost Estimate for BID
PLANT DATADASE
IFC
Back to
Information
Flows
Next
Back
Directory
Return
-21-
BOQ,
• Cost Estimate,
• Time schedules,
• Procurement,
• Subcontracts
CONCUR
Fortum Eng.: Building Conceptual Design
 In the CONCUR demonstration Fortum Engineering defined construction
requirements from the client’s requirements and distributed the
information by VTT’s Information Management System to other industrial
partners. The used software was :
 ScopePower
 for the definition of the delivery scope
 Solvo
 for energy balance studies
 Knowledge Modules
Back to
Information
Flows
PlantPower
Flowchart
Concept
Design
Flowchart
Next
Back
Directory
Return
-22-
 for component dimensioning and layout design
 MicroStation J
 for shape modelling and for interactive part of 3D modelling in CAD
 CostPower
 for cost libraries, cost estimation and budgeting
 Company IMS
 Fortum Engineering will be using their company Information Management System (IMS) for storing and exchanging
documents and models
 Project IMS
 VTT’s IMS is the Communication Module for information management and data exchange between partners in
CONCUR project
Building Conceptual Design
- CONCUR demonstration of Fortum Engineering/VTT IMS
Invitation to
Tender
LOGICAL LAYOUT
PLANT CONFIGURATION
Scope
Energy
balance
PLANT LAYOUT
Main Equipment
FACILITIES
Product model
Back to
Information
Next
Flows
Back
Directory
Return
-23-
FE/VTT IMS
Documents
• BOQ,
• Cost Estimate,
• Time schedules,
• Procurement,
• Subcontracts
1st Cost Estimate
Cost Estimate for BID
Data exchange
• STEP/IFC
CONCUR
Fortum Internal IMS & Information exchange
 Most companies have an internal information management
system
 To support their internal engineering and business processes.
 They also have internal protocols for exchanging information between software applications.
 The protocols are usually based on proprietary native exchanges because they are information rich.
 Why use open standards?
 Even though open standards are less rich than proprietary native standards for exchange they offer a
common denominator when exchanging information with other companies, especially when active
trading relationships are short.
 Proprietary standard are not particularly good at handling objects that are not supported by that
software. At best they import and export the objects without altering them. At worst they corrupt them
of just lose them so that they are not available for downstream activities. This usually happens at the
interfaces between different engineering or business disciplines.
 There are internal advantages to using open standards when using different types of software or
purchasing new software.
Next
Back
Directory
Return
-24-
 Why use a web based IMS?
 Easy universal access.
 Partner companies like web based project IMS systems because they feel that they have a share in its
ownership.
 The web based systems can be transferred to the client to support downstream life cycle support.
IMS Upload
TU Delft
Client Brief
Define Building
INCEPTION
MODELLER
Taylor Woodrow
TUD Software
Define
SCHEME
T- building
Fortum Eng.
Scheme modeller
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
Model Merger
Project
suggested
models and
CHOOSE one
Skanska
Fortum Eng.
Define
SCHEME
T- building
MERGE Skanska
Scheme modeller
database
Project IMS - I
ProjectWise
IFC
FE1
Project IMS
EPM-EDM
Fortum Eng.
COMPARE
Next
-25-
models
Define
CONCEPT Turbine
BUILDING
FE IMS
Return
MERGE TW
FE Software
FE Software
Back
Directory
Fortum Eng.
models
Model Merger
Bid
CONCUR
Web based Project IMS
(Information Management System)
VTT Building Technology, Finland
•Summary
•IMS System Structure
•IMS User Interfaces
•IMS Main Functions
•Uploading & Downloading documents
•Model Merging
Next
Back
Directory
Return
-26-
•XML Access
Internal
working
environment
within
company
intranet
D++
IMS Architecture
COMPANY 1
CM
Company
specific
information
repository
COMPANY 2
Client
Company specific
IMS system
COMPANY 3
Project mgr
Achitect
CONCUR IMS: Web based Project Environment
Next
Back
Directory
Return
-27-
Project information
repository:
Project document
& Object database
Real life projects
Real life projects
Summary
Web Based Project IMS
 Used for information sharing between all project participants
 Can be hosted on a web site located anywhere
 Based on Bentley ProjectWise document management
system and incorporates the Express Data Manager software
from EPM Technology
 Combine functionalities of a document based system with
product model server
 Used IFC based models for exchanging information
Next
Back
Directory
Return
-28-
Further information
Reports describing the IMS system are available in the Download Area
Contact at VTT is Maria Nikolaenko:maria.nikolaenko@vtt.fi
IMS system structure
Next
Back
Directory
Return
-29-
IMS user intefaces
Document managment
system interface
Next
Back
Directory
Return
-30-
Documents,situated
in choosen
folder
Web interface
Interface to upload, documents
merge models in the system,
XML browsing
IMS user Interface
Viewing models in 3D
VR
window
Available
methods for
the selected
objects in
VR window
Next
Back
Directory
Return
-31-
Document related
to the selected object
Main functions of IMS
IMS
Upload files
to doc mgt system
Download
files from doc mgt
system
Link file to
a product model
object
Merge product
models
Next
Back
Directory
Return
-32-
End user
Extract partial
product model data
Store
product
model
IMS
Upload files Diagram
Next
Back
Directory
Return
-33-
IMP user interface
Upload files
Select
”Add file”
User
enters
metadata
Add new file form
Next
Back
Directory
Return
-34-
IMS
Model Merging Diagram
User
IMS servlet
ProjectWise
Command to
Get A, B
Merge A, B
OK
Insert A, B
Merge A, B
OK
Next
Back
Directory
Return
-35-
EPM-EDM
OK
(C stored in
ProjectWise)
OK
OK
Merged model C
Start situation:
Source model files
reside in ProjectWise
End situation:
Merged model file is stored
in ProjectWise
IMS user interface
Model Merging form
Select
”Merge
models”
User
enters
metadata
Merge models
Next
Back
Directory
Return
-36-
IMS product model server &
XML interface
VTT Building Technology, Finland
Next
Back
Directory
Return
-37-
IMS - XML interface
Request
object
data
Next
Back
Directory
Return
-38-
Object
properties
in XML
format
CONCUR
EPM Technology’s Express Data Manager™ (EDM) - 1
 How has CONCUR used EXPRESS Data Manager™ version 4.0 ?
 IMS support – EXPRESS Data Manager™ is used by the CONCUR project to implement a Product Model Server
(PMS) as an integral part of the Project Information Management System (IMS). The IMS is responsible to ensure
consistency between the contractual document management system and the 3D project database stored in the
PMS according to the IAI IFC151 specification. The PMS provides a facility for selective viewing, download and
upload of 3D project data and their link to the contractual documents.
CONCUR is making use the ultimate object technology: Objects are defined as industry standard objects in IFC and
the ISO Express-X language is used as a data manipulation language (DML) for improving the capability of these
objects - independently of any particular software system.
Next
Back
Directory
Return
-39-
 Project database functionality:
 Partial download – Using a 3D browser (Promote) to select IFC objects to download using P21 and XML
 Upload and merge – Import IFC objects and merge the result using P21 and XML..
 XML Access to IFC Models – EDM provides an access interface to objects, their attributes and properties
based on XML to enable the integration with material take-off applications in Excel and similar.
 IFC Browser - EDM provides the object database used by the TNO IFC Browser application which can
view IFC models and be used to add, edit and extract the properties and attributes of the IFC objects in the
models.
 Calculation of derived Attributes - EXPRESS Data Manager™ provides a virtual machine that interprets
all Express and Express-X executable statements. CONCUR has used this capability to add semantics to
the IFC151 schema by adding ‘Derived Attributes’ such as volume and surface area of the IFC 1.5.1 objects.
This is a convenience to any application that does not include a geometric engine.
 Further information
 Reports describing the CONCUR Project’s use of Express the Data Manager are available in the Download Area.
 Contacts: Maria Nikolaenko at VTT: maria.nikolaenko@vtt.fi, EPM Technology website & Jorulv Rangnes at EPM
Jorulv.Rangnes@epmtech.jotne.com
CONCUR
EDM and CONCUR - 2
Other
Application Type
IFC Browser
CAD
Modelling
System
Project (IMS)
[ProjectWise]
Other
Modelling
System
EPM-EDM
Generation of
Derived Attributes
XML Access by
MS-Office products
Express X
Model Merging
Next
Back
Directory
Return
-40-
Services from EDM
 Further information
 Reports describing the CONCUR Project’s use of the Express Data Manager are available in the Download Area.
 Contact at VTT is Maria Nikolaenko: maria.nikolaenko@vtt.fi & Jorulv Rangnes at EPM
Jorulv.Rangnes@epmtech.jotne.com
CONCUR
Express Data Manager (EDM)- 3
 What is EPM Technology EDM?
 EXPRESS Data Manager™ (EDM) is a suite of applications providing an out-of-the-box solution for easily creating
data-models conforming to international standards.
 EDM's pick-and-place icon driven user interface allows anyone to easily learn EDM's data modeling methodology.
 Once familiar with EDM, the user can quickly implement data-models in conform-ance with ISO 10303 (STEP), and
other standards like IAI, STEP/NC, OIL & GAS and P-LIB making use of XML, Java and other environments.
 How can EPM Technology EDM help construction industry users?





EDM helps users to take a great leap towards cost efficient and reliable use of ICT in their organizations.
EDM helps users to take ownership of their product data by using a single data source based on standards.
EDM helps users to apply a unified methodology and a set of products that take them from concept to solution.
EDM can assist users in the change of the design world from 2D to a 3D object based environment.
The interoperability and re-use of building models will translate to increased collaboration amongst industrial
partners.
 In particular the knowledge stored in IFC based building models could be used for facility management and other
purposes during design, construction and after the building project is completed.
Next
Back
Directory
Return
-41-
 Further information
 Reports describing the CONCUR Project’s use of the Express Data Manager are available in the Download Area.
 Contact at EPM is Jorulv Rangnes Jorulv.Rangnes@epmtech.jotne.com
CONCUR
Express Data Manager (EDM) - 4
 What can EDM do?
 A powerful object-oriented database management system capable of being a users single source of information.
 A web enabler due to its thin-client technology. Complete applications written in EXPRESS and EXPRESS-X are
fully executed by the EDM-expressVM™ (Virtual Machine) within the database. These applications are controlled
through local EDM interface™ calls.
 A unified methodology for product data solutions. All functionality of the system is configured by EXPRESS and
EXPRESS-X schemas, which are the ISO and industry standards for information requirement specifications.
 An EXPRESS-G modelling environment which uses EDM visual-Express™ to design users data models and to
publish them, for example on the web.
 A Rule Engine to define a users corporate knowledge by constraining information models using the rules
capabilities of EXPRESS and EXPRESS-X.
 A standards solution in its support for EXPRESS (all statements, expressions, built-in functions and procedures),
Part 21, and SDAI.
Next
Back
Directory
Return
-42-
 Further information
 Reports describing the CONCUR Project’s use of the Express Data Manager are available in the Download Area.
 Contact at EPM is Jorulv Rangnes Jorulv.Rangnes@epmtech.jotne.com
CONCUR
Express Data Manager (EDM) - 5
 Whats new in EDM version 4.5
 EXPRESS-X implementation has been extended - among others with full exception handling to be the one built-in database control language (including EXPRESS) for EXPRESS Data
Manager™ 4.5. It provides the user with functionality and performance for building entire
applications on top of the users information models at reduced costs for programming and
maintenance. With the one language for modelling, storage, and use of information models,
the user avoids technology compatibility problems.
 The Business Object layer of EXPRESS Data Manager™ 4.5 hides the complexity of an
underlying data model and adds application specific functionality. The Business Object defines
views and methods for the underlying database by means of the powerful EXPRESS based
Query and Update Language in EXPRESS Data Manager™ 4.5. Business Objects are
created on the server instead of locally, enabling thin clients and reducing network traffic.
Business Objects tailor the same underlying information to the needs of the many disparate
applications of data.
 The Query and Update Language of EXPRESS Data Manager™ 4.5 is using EXPRESS-X.
Any EXPRESS-X logical expression can be passed to a query as a parameter. This
functionality is fully comparable to SQL.
Next
Back
Directory
Return
-43-
 Further information
 Contact at EPM: Jorulv Rangnes Jorulv.Rangnes@epmtech.jotne.com
Develop Scheme
Skanska
TU Delft
Define Building
Client Brief
INCEPTION
MODELLER
Taylor Woodrow
TUD Software
Define
SCHEME
T- building
Fortum Eng.
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
FE Software
Scheme modeller
Model Merger
suggested
models and
CHOOSE one
FE Software
Scheme modeller
SK IMS
Next
Project
database
Fortum Eng.
CONCEPT Turbine
BUILDING
FE IMS
-44-
models
COMPARE
Define
SCHEME
Turbine Building
Return
MERGE TW
Define
Skanska
Back
Directory
Fortum Eng.
Project IMS - I
ProjectWise
IFC
FE1
Project IMS
EPM-EDM
Fortum Eng.
MERGE Skanska
models
Model Merger
Bid
CONCUR
Skanska Design Development
 Skanska download the Conceptual Model and supporting documentation for the
Turbine house from the project database.
 Skanska design a scheme and prepare a cost plan and construction programme
using ArchiCad, MS-Project and bespoke software from Solibri. They use their
company IMS during this process.
 The end result is uploaded to the Project Database as IFC-SK1 plus information
such as the cost plan and construction programme.
Next
Back
Directory
Return
-45-
Turbine House
Building Scheme
Next
Back
Directory
Return
-46-
Turbine House in ArchiCad
1
Explore
SKANSKA
FACETS
Next
Back
Directory
Return
-47-
Facets
Project development with split
vision
Next
Back
Directory
Return
-48-
Adina Jägbeck, Lennart Klintmalm Skanska Teknik AB
Pasi Paasiala - Solibri OY
Introduction 1
Facets
Skanska Teknik has since 1999 worked on the development of a new tool to
combine information about the different aspects of a project. The purpose
and functionality of the system have been defined by Adina Jägbeck and
Lennart Klintmalm. It has been named "Facets".
Facets deals with information from CAD, cost estimation and process planning. Or, rather, it allows the user to create
– otherwise sub-understood – relations between the various aspects, and display them. The development started as
a part of a EU-supported project - Concur. The system has been built by Solibri OY and is certified for import of ifc
2.0 from CAD. It contains functions for two different project stages.
Facets Site Developer – functions for the concept phase
The use context for Facets Site Developer is the very early project phase. The
prerequisite for using Facets in this stage is that one needs to graphically
investigate different alternatives for accommodating a space requirement
schedule on a site and, at the time, calculate investment costs and rental levels
based on rough estimates of.
Facets Site Developer was developed during the spring of 2001 in cooperation
with a group of project developers in Skanska Hus, - Ingela Lindholm and Anders
Rådestad.
Facets Scheme Design – functions for scheme phase
Next
Back
Directory
Return
-49-
The use context for Facets Scheme Design is co-ordination between design, cost
estimation and process planning. The system imports CAD-information in IFCformat, while cost recipes and process schedules are imported as databases. By
relating building objects to cost items, recipes and activities the system
automatically creates, on-line, quantity take-off item and activity, calculation of
recipe based costs and displaying building a 4D-view of time schedules.
The functions in Facets Scheme Design were developed during 2000 and 2001 in
cooperation with a production group within Skanska Hus, including Katrin Eriksson.
Introduction 2:
Such phase, such requirements
Facets’ context
Concept
Scale - 1:1000
Tme -1
Info - 1
Scheme
Scale - 1:100
Time -10
Info - 1 000
Working docs
Scale - 1:10
Time -100
Info - 1 000 000
Next
Back
Pre-study
Directory
Return
-50-
Programme
Design - procurement
Run - Maintain
Introduction 3:
All aspects in every phase
Concept phase Quick run through

Customer’s area and function req

Site possibilities

Volume studies

Time frame and economical picture

Alternatives
Scheme phase Worked model with spaces and building
objects
 Architectural design, cost estimate, time
schedule
 Coordination between knowledge fields
 Reuse of key figures
Instant control!
Face to face!
Professional tools!
Standard exchange format!
Next
Back
Directory
Return
-51-
Experience
Concept phase –
”the target is to achieve a well studied
project suggestion, with the client, here and
now.”
 What is needed?
 What does the site allow?
 Do we have the space?
 Is it attractive?
 How much is it?
 Test another idea?
 Move on to next phase?
Next
Back
Directory
Return
-52-
In other words:
Complete basis for decision faster
Facets Site Developer ”all in one box”
Aesthetic
Site
The boxes contain links.
Use the ”back arrow” to
return to this page
Function
Space use
Next
Back
Directory
Return
-53-
Economy
Experience
Sketch
..
Skiss
32
based figures
Skiss
Skiss 1
Rent
Result of using Facets Site Developer:
Project suggestion at client meeting
 Coordinated aspects
(built spaces, space use, rent)
 Experience from previous projects
(key figures)
 More alternatives investigated
(volume studies, space use, construction period, effects of interest rate...)
 Informative presentation
(bird’s eye, 3D-sketches, rent/m2)
 Direct communication with client
 Interactive way of work
Next
Back
Directory
Return
-54-
 Good basis for decision
 Good definition for next phase
Scheme phase
”The target is to facilitate coordination between professionals”
 Product definition – building objects and spaces with geometry and other
attributes
 Quantity take-off adjusted to cost structure
(t.ex. BSAB, project divisions ....)
 Cost estimation with different requirements degree of detail
(e.g. recipes for walls, key-figures for HVAC, quotation sum for painting... )
 Time schedule appropriate to planning needs
(e.g. phases production activities with concerned building parts)
 Every party works based on the same, updated information
Next
Back
Directory
Return
-55-
In other words:
coordinated professional project information
for procurement and detail design
Facets Scheme Design:
Coordinate information from
professional tools
Cost
Test project
Recipe
Next
Back
Directory
Return
-56-
Time
Method
Product
The boxes contain links.
Use the ”back arrow” to
return to this page
Result of using Facets Scheme Design
Product model with several aspect




Next
Back
Directory
Return
-57-
Product definition from CAD
(now: ifc 2.0 import of architectural drawings
services)
Planned: also building
Cost calculation based on cost databases
(now: recipe databases through odbc e.g. Mängda,
Planned: through ifc)
Time schedule from project planning software
(Now: database access to MS Project…
Planned: ifc)
Relations between products, costs and activities
 support for project leaders need of coordination:
designed  costed  planned
Develop Scheme
Skanska
TU Delft
Define Building
Client Brief
INCEPTION
MODELLER
Fortum Eng.
Taylor Woodrow
TUD Software
MERGE TW
Define
SCHEME
T- building
Fortum Eng.
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
FE Software
models
Model Merger
Scheme modeller
Define
COMPARE
CONCEPT Turbine
BUILDING
suggested
models and
CHOOSE one
FE Software
Fortum Eng.
Skanska
MERGE Skanska
Define
SCHEME
Turbine Building
FE IMS
models
Model Merger
Scheme modeller
SK IMS
Next
Back
Directory
Return
Project
database
-58-
Fortum Eng.
Project IMS -II
Project IMS - I
ProjectWise
IFC
FE1
IFC
FE1
Project IMS
EPM-EDM
IFC
SK1
Project IMS
Bid
Develop Scheme
Taylor Woodrow
TU Delft
Define Building
Client Brief
INCEPTION
MODELLER
Fortum Eng.
Taylor Woodrow
TUD Software
MERGE TW
Define
SCHEME
T- building
Fortum Eng.
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
FE Software
models
Model Merger
Scheme modeller
Define
COMPARE
CONCEPT Turbine
BUILDING
suggested
models and
CHOOSE one
TW IMS
FE Software
FE IMS
Skanska
Fortum Eng.
Define
SCHEME
T- building
MERGE Skanska
models
Model Merger
Scheme modeller
SK IMS
Next
Back
Directory
Return
Project
database
-59-
Fortum Eng.
Project IMS - II
Project IMS - I
ProjectWise
IFC
FE1
IFC
FE1
Project IMS
EPM-EDM
IFC
SK1
Project IMS
Bid
CONCUR
Taylor Woodrow Design Development
 Taylor Woodrow download the Conceptual Model and supporting documentation for the
Turbine house from the project database.
 Taylor Woodrow design a scheme and prepare a cost plan and construction programme.
Taylor Woodrow show how the full IAI-IFC schema can be viewed and used as a source of
information for generating a cost plan and how specification information can be included in
the model. Taylor Woodrow use the estimators desktop software to assist with this task.
 Taylor Woodrow use their company IMS during this process
 The end result is uploaded to the Project Database as IFC-TW1 plus information such as the
cost plan and programme
 A view of the major structural components of the Taylor Woodrow solution is shown in the IFC
Browser Viewer screen shots.
Next
Back
Directory
Return
-60-
.
Turbine House
Building Scheme
Next
Back
Directory
Return
-61-
Develop Scheme
Taylor Woodrow
TU Delft
Define Building
Client Brief
INCEPTION
MODELLER
Fortum Eng.
Taylor Woodrow
TUD Software
MERGE TW
Define
SCHEME
T- building
Fortum Eng.
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
FE Software
models
Model Merger
Scheme modeller
Define
COMPARE
CONCEPT Turbine
BUILDING
suggested
models and
CHOOSE one
TW IMS
FE Software
FE IMS
Skanska
Fortum Eng.
Define
SCHEME
T- building
MERGE Skanska
models
Model Merger
Scheme modeller
SK IMS
Next
Back
Directory
Return
Project
database
-62-
Fortum Eng.
Project IMS - II
Project IMS - I
ProjectWise
IFC
FE1
IFC
FE1
Project IMS
EPM-EDM
IFC
IFC
SK1
TW1
Project IMS
Bid
CONCUR
Ifc Browser
 Client Server JAVA application which uses the Microsoft
Internet Explorer to view Ifc 1.5.1 in HTML and VRML
 Works on a network, intranet, extranet or internet. Can work
with a modem connection.
 Minimal system requirements; UNIX or Windows with
freeware plug-ins for viewing.
 Uses Ifc data stored in an EPM Technology Express Data
Manager database on the server
 Undertakes IFC to HTML translation on the client
 Undertakes IFC to VRML (3D) translation on the client
 Independent of proprietary modelling systems
Next
Back
Directory
Return
Further information
Reports describing the IFC Browser work are available in the Download Area.
Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nl
-63-
CONCUR
Ifc Browser Architecture
NT4.0/W2K
IfcBrowser
Java Server
Unix/Microsoft
RMI/HTTP
+
Generates
Java
IFC-Binding
(early)
EXPRESS-to-Java/SDAI
Generator in Java
Java
SDAI-Binding
(late)
Meta-data (DD)
Access
IFC-data (MD)
Access
IFC1.5.1
C SDAI-Binding
Next
Back
Directory
Return
-64-
EDM Supervisor
EDM DB
IfcBrowser
Java Client
Running in
Java-enabled
Internet Browser
Here:
MS IE5 +
Sun Java 1.2 Plug-in
CONCUR
Ifc Browser- Screen shot
Next
Back
Directory
Return
-65-
CONCUR
Ifc Browser Functionality
 Browse through the complete IFC 1.5.1 structure.
 Browse through the complete model.
 Show HTML or 3D based on every possible IFC object
selection, object selection help tools:
 Make a selection by hand in the modeltree
 Select all objects in the model based on a certain subset of the IFC 151
structure
 Filter out specific object types within the current selection
Next
Back
Directory
Return
 Add properties to the objects on the server through the
client.
 Show derived properties from an IFC object selection.
 Highlight a certain selection in the current 3D view.
Further information
Reports describing the IFC Browser work are available in the Download Area.
Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nl
-66-
CONCUR
Ifc Browser Details
 All data is password protected
 Data is managed by EPM Express Data Manager (EDM)
object database.
 Which is accessed by the TNO Java/SDAI binding which is…
 Built on top of the third layer in the EPM Technology SDAI+
Toolkit using the Java Native Interface
 The base product developed by TNO and CSTB (VRML
generation) in the Esprit VEGA Project.
Next
Back
Directory
Return
Further information
Reports describing the IFC Browser work are available in the Download Area.
Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nl
-67-
CONCUR
CONCUR Ifc Developments
 PDM MetaData Structures for Documents
 Ifc Derived Attributes
 Ifc Model Merging
 Ifc Property Sets
Next
Back
Directory
Return
Further information
Reports describing the IFC Browser work are available in the Download Area.
Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nl
-68-
CONCUR
PDM Meta data Structures for Documents
 End users require metadata to automate the sorting, finding,
storing and exchanging of files and documents.
 The CONCUR Project has specified a simple PDM schema for
documents for use in the project IMS.
 The schema is in line with Ifc 2.0
 A simplified version has been incorporated in Ifc 2x
 Metadata Criteria:




Next
Back
Directory
Return
LINK - Easy link to PDT (Ifc 1.5.1 compliant in 1999)
SIMPLICITY - Simple to understand and implement
NEEDS - Satisfying the CONCUR Demonstration industrial need
SUPPORT - IT vendor support
 Analysed solution and described on the next sheet.
 The CONCUR schema is being used by IT vendors in ProCure
Further information
Reports describing the IFC Browser work are available in the Download Area.
Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nl
-69-
CONCUR
PDM Metadata Development
 CONCUR analysed 3 different Metadata solutions before
preparing the CONCUR Schema:
 STEP PDM Schema 1.1 (by the PDM Implementers Forum- Usage guide for the STEP PDM Schema, Jim
Kendrick ERIM/PDES Inc. and Markus Hauser, ProSTEP GmbH, May 1999)
 IAI Ifc 2.0 CD
 New CONCUR specific, top down approach (using Document Classification work prepared by Steve Race
in 1999)
 Analysis Summary:
LINK
SIMPLICITY
NEEDS
SUPPORT
-
--


IFC


-

CONCUR



STEP
Next
Back
Directory
Return
 (but  if harmonized
with the IAI)
Further information
Reports describing the IFC Browser work are available in the Download Area.
Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nl
-70-
CONCUR
Ifc – Derived Attributes- Why?
 IAI-Ifc contains direct data on building elements such as:
 Height, Width, Length
 However, users are also interested in properties like:
 Volume, Surface Area, Area
 So CONCUR extended the standard Express Ifc 1.5.1 schema
with derived property values which can be derived using the
shape representation in Ifc 1.5.1
 The EPM Technology Express Data Manager database can
calculate the Derived Attributes in real time
 The TNO IfcBrowser can view them via the client interface,
calculating them on the server when the user requests them.
Next
Back
Directory
Return
Further information
Reports describing the IFC Browser work are available in the Download Area.
Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nl
-71-
CONCUR
Ifc - Model merging – Why?
Next
Back
Directory
Return
 Commercial modelling software applications support their own
specific disciplines and sometimes ignore or lose information from
other disciplines!!!
 End users often need to combine models from different disciplines
 End users often need to mix and match alternative solutions
 CONCUR developed a simple Model Merging technique using
Express-X
 The technique can merge models complying with the same Ifc
schema
 If the construction and related industries are to exploit object
modelling to the full, they will need sophisticated model merging
technology.
 CONCUR has not addressed the legal, responsibility ownership or
model locking issues associated with multiple users taking parts of
models, modifying them and merging the results back into the model.
 The model merging is controlled by the Web based project IMS
system and undertaken by the EPM-EDM database.
Further information
Reports describing the IFC Browser work are available in the Download Area.
Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nl
-72-
CONCUR
Ifc - Model Merging Philosophy
Next
Back
Directory
Return
-73-
Merge Concept & Scheme
Client Brief
Fortum Eng.
Taylor Woodrow
MERGE TW
Define
SCHEME
T- building
Fortum Eng.
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
FE Software
models
Model Merger
Scheme modeller
Define
COMPARE
CONCEPT Turbine
BUILDING
suggested
models and
CHOOSE one
TW IMS
FE Software
FE IMS
Skanska
Fortum Eng.
Define
SCHEME
T- building
MERGE Skanska
models
Model Merger
Scheme modeller
SK IMS
Next
Back
Directory
Return
Project
database
-74-
Fortum Eng.
Project IMS - I
ProjectWise
IFC
FE1
Project IMS
EPM-EDM
Project IMS - II
IFC
FE1
IFC
IFC
SK1
TW1
Project IMS
SK1 TW1
FE1
Bid
CONCUR
Model Merging Rationale
 The civil engineering companies have delivered alternative building solutions to the
project database. The project database will have the facility to maintain the
confidentiality of information where necessary.
 Fortum Engineering can view both alternative schemes and can merge either with
the original conceptual design for the plant and equipment or with an alternative
design for the plant and equipment. It is also possible for Fortum to merge models
for other parts of the plant into the same model.
 Model merging requires the EPM-EDM part of the project database. Model merging
instructions are assembled via a web based form.
 The EPM-EDM software can also be used to extract individual objects from the
Models.
 The merged models have been loaded into the project database as IFC FE1+SK1
and IFC FE1+TW1. After the merging has been completed, the source and merged
files are deleted from EPM-EDM.
 The next view shows merged models.
Next
Back
Directory
Return
-75-
.
Ifc Model Merging Views
Next
Back
Directory
Return
-76-
CONCUR
Ifc – Property Sets
 Part of the content in IFC files is put in the properties.
 Property Sets can be defined to combine several properties
in a subgroup.
 This way we can define relations between different
properties.
 This saves a lot of space because we can refer to a specific
property set instead of a set of references to properties
 A property set can have 0 to many properties.
 One property can be found in several property sets.
Next
Back
Directory
Return
Further information
Reports describing the IFC Browser work are available in the Download Area.
Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nl
-77-
Merge Concept & Scheme
Client Brief
Fortum Eng.
Taylor Woodrow
MERGE TW
Define
SCHEME
T- building
Fortum Eng.
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
FE Software
models
Model Merger
Scheme modeller
Fortum Eng.
Define
COMPARE
CONCEPT Turbine
BUILDING
suggested
models and
CHOOSE one
TW IMS
FE Software
FE IMS
Skanska
Fortum Eng.
Define
SCHEME
T- building
MERGE Skanska
models
Model Merger
Scheme modeller
SK IMS
Next
Back
Directory
Return
Project
database
-78-
Project IMS - I
ProjectWise
IFC
FE1
Project IMS
EPM-EDM
Project IMS - III
Project IMS - II
IFC
FE1
IFC
IFC
SK1
TW1
Project IMS
SK1 TW1
FE1
IFC
FE1
IFC
SK1
IFC IFC
FE1+
TW1 SK1
IFC
FE1+
TW1
Project IMS
FE1 +
TW1
FE1 +
SK1
Bid
Compare Scheme Solutions
Client Brief
Fortum Eng.
Taylor Woodrow
MERGE TW
Define
SCHEME
T- building
Fortum Eng.
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
FE Software
models
Model Merger
Scheme modeller
Fortum Eng.
Define
COMPARE
CONCEPT Turbine
BUILDING
suggested
models and
CHOOSE one
TW IMS
Bid
FE Software
FE IMS
Skanska
Fortum Eng.
Define
SCHEME
T- building
MERGE Skanska
models
Model Merger
Scheme modeller
SK IMS
#
Next
Description
Back
Directory
Return
Project
database
-79-
Project IMS - I
ProjectWise
IFC
FE1
Project IMS
EPM-EDM
Project IMS - III
Project IMS - II
IFC
FE1
IFC
IFC
SK1
TW1
Project IMS
SK1 TW1
FE1
IFC
FE1
IFC
SK1
IFC IFC
FE1+
TW1 SK1
Project IMS- IV
IFC
FE1+
TW1
Project IMS
FE1 +
TW1
FE1 +
SK1
IFC
FE1
IFC
SK1
IFC
TW1
IFC
FE2
Project IMS
Turbine House
Plant & Skanska Building Solution
Next
Back
Directory
Return
-80-
Turbine House
Plant & TW Building Solution
Next
Back
Directory
Return
-81-
CONCUR
Compare Scheme Solutions
Compare Solutions
 The different solutions offered by the building and civil engineering contractors are
compared.
Try Combinations of Models
 Model merging offers the opportunity to try different combinations of plant and building
models. For example the mechanical engineering plant model may have changed or the
principal contractor may want to try a new arrangement in an existing building model or try
an existing plant arrangement in a different building. This could could occur when buildings
are designed for a specific country or climate.
Choose the Most Appropriate Solution
 The principal contractor chooses the most appropriate combination to incorporate in the
bid.
Next
Back
Directory
Return
-82-
Bid
Client Brief
Fortum Eng.
Taylor Woodrow
MERGE TW
Define
SCHEME
T- building
Fortum Eng.
Fortum Eng.
Design
CONFIGURATION
for Steam Turbine
Plant
Bid
models
Model Merger
Scheme modeller
Fortum Eng.
Define
COMPARE
CONCEPT Turbine
BUILDING
suggested
models and
CHOOSE one
TW IMS
FE Software
FE Software
FE IMS
Skanska
Fortum Eng.
Define
SCHEME
T- building
MERGE Skanska
models
Model Merger
Scheme modeller
SK IMS
Next
Back
Directory
Return
Project
database
-83-
Project IMS - I
ProjectWise
IFC
FE1
Project IMS
EPM-EDM
Project IMS - III
Project IMS - II
IFC
FE1
IFC
IFC
SK1
TW1
Project IMS
IFC
FE1
IFC
SK1
IFC IFC
FE1+
TW1 SK1
Project IMS
Project IMS- IV
IFC
FE1+
TW1
IFC
FE1
IFC
SK1
IFC
TW1
IFC
FE2
Project IMS
CONCUR
Bid to Client
The bid to the client usually includes:
 The Proposed Scheme Solution
 In the past, proposed scheme solutions were usually described on drawings which were contractual documents. In the
future it is expected that this information will be presented as models which can be re-used. The models can be used to
create views (drawings) for construction purposes. Models are presenting challenges to how contracts are written and
undertaken. CONCUR has explored some of the practical technical requirements.
 Cost Plan
 All bids require a price. How this is provided varies from country to country and even varies for different types of
construction project. Although detailed bills of quantities are still prepared for pricing, the construction industry is tending
to use cost plans which are easier to prepare and use. They also relate to the object oriented way of thinking and
working. A typical UK Cost Plan format for commercial buildings is shown which will be recognisable to most of the
European construction industry.
Taylor Woodrow and Skanska, in particular, have addressed how models can support the preparation of cost plans.
External software partners have developed this further.
 Programme
 The bid usually includes a programme for executing the work. Fortum Engineering and Skanska have developed this
aspect during the project.
 Specifications
 Specifications are a key component of bids. This is the speciality of STABU. The TNO IFC Browser can be used to
insert specification information relating to building objects into the models.
 Schedules
Next
Back
Directory
Return
-84-
 Schedules of principal components such as doors and windows. Schedules can be created from the information models
 Company Supporting Information




Financial Statements
Health & Safety Plan – including Construction Design & Management (CDM) risk assessments
Quality Plans and Company Procedures
Company Policies on issues such as safety, sustainability and environmental protection
CONCUR
Typical Cost Plan
FUNCTION SUMMARY and COST PLAN
Job Nr
Version
Job Name
Job Location
Client
L97198
1
Turbine House
None remote England
Fortum Engineering
Office
Contact
Southall
D. Williams
SfB Code
BCIS Region
162.1
Northern
Contract Type
Contract Period
Tender Date
Start on Site
Practical Completion
Date of Cost Plan
JCT 81
29 weeks
Nov-00
Apr-01
Sep-01
Oct-00
Cost Base Date
Nov-00
Gross Floor Area
Basement Area
Ground Slab Area
Upper Floors Area
Wall Area
Wall to Floor Area
Average Storey Height
Nr of Storeys
FUNCTION
Function Total
€
1
2
3
4
5
6
7
8
Substructure
Structure
Envelope Completion
Cellular Completion
Finishes
Fittings
Services
External Works
Sub-total of all Functions
Next
Preliminaries
9.7%
TOTAL EXCLUDING CONTINGENCIES
Back
Directory
Return
-85-
Contingencies
3.0%
Total cost plan at base date
Inflation between base date & completion date
TOTAL COST PLAN AT COMPLETION
3.5%
2,785
0
1385
1400
600
0.22
5
2
Cost/m2
of Gross
Floor Area
€
m2
m2
m2
m2
m2
m
% of Job
at
Base Date
%
280,375.00
331,500.00
423,530.00
195,940.00
141,189.00
26,600.00
833,499.00
314,497.00
100.67
119.03
152.08
70.36
50.70
9.55
299.28
112.93
9.7%
11.5%
14.7%
6.8%
4.9%
0.9%
29.0%
10.9%
2,547,130.00
914.59
88.5%
247,071.61
88.72
8.6%
2,794,201.61
1,003.30
97.1%
83,826.05
30.10
2.9%
2,878,027.66
1,033.40
100.0%
100,730.97
36.17
3.5%
2,978,758.63
1,069.57
103.5%
CONCUR
LexiCon
 LexiCon Description
 A collection of common concept definitions and descriptions used by the
construction industry in multiple languages. They are presented in
classes with associations to other classes and associated aspects.
 LexiCon Explorer
 A software tool for preparing, editing and inputting content into a
LexiCon database.
 Spec Explorer
 A software tool for preparing and editing project composition trees.
 The LexiCon Vision
 The LexiCon is continuing to grow as an international collaboration.
Next
Back
Directory
Return
-86-
CONCUR
LexiCon Description
 Common concept definitions and descriptions for the
construction industry
 Definition of concepts
 Definition of relations between concepts
 Naming of concepts
 Based on Framework of ISO PAS 12006-3
 Building construction
Organization of information about construction works
Part 3: Framework for object-oriented information exchange
 Multi-lingual, support for synonyms and homonyms
 Concepts can have an unlimited set of names in any language, and names may refer multiple concepts
 International co-operation
Next
Back
Directory
Return
 Content of the LexiCon is developed by STABU in co-operation with organizations in Europe, Australia,
New Zealand and Canada
Further information
Contact at STABU is Kees Woestenenk: kwoestenenk@stabu.nl
Reports describing the LexiCon work are available in the Download Area.
-87-
CONCUR
LexiCon Explorer
Browser and Editor of LexiCon Classes
 LexiCon Classes (based on ISO PAS 12006-3):





Subjects (e.g. Built objects, Spaces, Products)
Activities (Work associated with Subjects)
Aspects (Grouping of Properties)
Properties, Measures and Values
Units (e.g. SI units)
 Descriptions of Classes and associated Names
 Names and Descriptions in any language
 Associations between Classes
 Specialization hierarchy
 Composition (Part-of associations)
 Associated Aspects, Properties, Measures and Values
Next
Back
Directory
Return
-88-
 References to external documents
 Standards (e.g. ISO standards, local standards)
 Classification systems (e.g. SfB, Master Format, EPIC
CONCUR
LexiCon Explorer
Screen shot
Next
Back
Directory
Return
-89-
CONCUR
SpecExplorer
Editor for project specifications
 Covers whole lifespan over projects
 Based on project composition
 Stand alone, user defined
 Imported from geometrical model (not available yet)
 Each node in composition tree is treated as a distinct project
 Usage of LexiCon classes as templates
 Additional assignment and specification of Tasks
 Task specification
 Contractual conditions
 Participants
Next
Back
Directory
Return
-90-
 Associated Contacts database
CONCUR
SpecExplorer
Screen shot
Next
Back
Directory
Return
-91-
CONCUR
The LexiCon Vision
 A common language for the Construction Industry
 The LexiCon provides definitions and descriptions of concepts that are of interest for the construction
industry.
 The definitions and descriptions are structured according to a model that allows both human and
computer interpretation.
 The conceptual language of the LexiCon may use any lexical human language to express its contents.
The formal definition of a concept consists of its set of associated properties, whereas the names and
descriptions given to that concept allow humans to quickly associate that concept with their own
understanding of the meaning of that concept.
 Framework for information exchange
 The LexiCon concepts live in the background, providing templates that help structuring information in
such a way that this information can be interpreted by different applications, as long as these
applications have access to the LexiCon concepts. Hence, end users won’t see much of the LexiCon in
practice because the LexiCon will often be hidden by the user application’s interface.
 Examples of applications using the LexiCon are:
Next
Back
Directory
Return
 CAD applications which want to combine gemotrical object descriptions and quality data
 Product information systems and Catalogues describing products
 Specification systems, cost estimating system and the like.
Further information
Contact at STABU is Kees Woestenenk: kwoestenenk@stabu.nl
Reports describing the LexiCon work are available in the Download Area.
-92-
CONCUR LexiCon Glossary - 1
 Lexicon Concepts - are abstractions of things that exist in the real world. A
concept groups similar things into one thing, e.g. the concept of Door is the
abstraction of all doors and represents the meaning of what a door is
 Multiple Concepts - any set of concepts
 Relations between Concepts - are properties of, part of and type of
relationships that exist between concepts
 LexiCon Classes - Concepts defined in the LexiCon are called Classes. The
main categories of Classes in the LexiCon are: subjects, activities, properties,
property collections, measures and units
 LexiCon Subjects - are the more or less tangible things being described, such
as buildings, parts of buildings, spaces and products
 LexiCon Activities - are the processes causing changes in the state of a
subject, e.g. the activity of casting concrete
 Assignment - assigning names to concepts and setting relationships between
concepts
Next
Back
Directory
Return
-93-
CONCUR LexiCon Glossary - 2
 LexiCon Aspects - characteristics of Subjects or Activities consisting of a set of
related properties. Most aspects in the LexiCon describe a function or role of a
Subject or Activity, e.g. the function Fire Barrier
 Associated Aspects - Aspects associated to a Subject or an Activity
 Lexicon Database - the actual storage of the LexiCon data
 Lexicon Properties - characteristics and quantities describing Subjects and
Activities
 Composition - the components that together constitute a Subject or an Activity,
e.g. door leaf and frame are components of a door set
 Project Composition - all the components of any Subject or Activity in a
project
 Composition Trees - the hierarchical structure of Subjects or Activities based
on their composition
Next
Back
Directory
Return
-94-
 Geometrical model - the geometry of Subjects, modelled in another
application, such as a CAD application
CONCUR LexiCon Glossary - 3
 Contacts Database - a database containing names and addresses of persons
and organizations
 Associated Aspects - Aspects describing a Subject or an Activity
 Specialization hierarchy - the hierarchical structure of concepts based on the
type-of relationship, e.g. a door is a type of separation construction
 Classification systems - a set of interrelated classification tables
 Collaborating organizations in LexiCon development
STABU foundation, the Netherlands
Construction Information Systems (CIS), Australia
Construction Information Limited, New Zealand
Norwegian Council for Building Standardization (NBR)
Digicon Information Inc., Canada
Next
Back
Directory
Return
-95-
CONCUR
Results and Exploitation
 Technical Results
 Industrial Results
 Partner Exploitation
 External Exploitation
 The Way Forward from CONCUR
Next
Back
Directory
Return
-96-
CONCUR Technical Results
 Common concepts for naming and definition in AEC (Lexicon)
 The development of common concepts for naming and defining construction terms for international use and in multiple
languages starting with Dutch, English, German, Norwegian and French.
 STABU have also developed tools for collecting and manipulating definitions.
 Moving IFC product models into use
 CONCUR has contributed to the the development of IFCs and provided criticism to the developers. The major
contribution was in the area of document metadata.
 The project partners have provided a test bed for trialling the advanced use of IFCs with industrial information.
 CONCUR has demonstrated early applications of IFC v1.5.1 and IFCv2.0
 CAD system translators for IFCs have been tested and feedback has been provided to software vendors.
 Encouraging software vendors
 IFCs were originally intended for exchanging information. CONCUR has show that they can also be used for storage.
 CONCUR has shown how IFCs can be used in in STEP (Express) object databases for both storage and manipulation
(Model Merging).
 The partners showed how XML could be used to interface with models in a STEP database. This showed that models
can be used without the need for sophisticated modelling systems. (none CAD tools)
 The partners developed a prototype IFC/Browser for viewing and extracting information from IFC models. (a none CAD
tool)
 Technical Issues
 IFCs and their translators are still immature and are very limited in their application. Serious general commercial
exploitation is unlikely to happen before 2004. There is a need for funding to develop the depth and breadth of the
models, especially in the product area.
 Currently cost and time are not being supported by vendors.
 There is a need for JAVA 3D development for viewing to replace the limited VRML.
 The modelling technology needs to keep pace with XML developments so that IFCs can be integrated with eCommerce
applications
Next
Back
Directory
Return
-97-
 Technical adoption
 Vendor uptake and translator production is at least 9 months behind model development. Different vendors are using
different versions of IFC which leads to incompatiblity
 There is an increasing vendor interest in IFCs, especially from the smaller vendors.
 Related R&D Projects
CONCUR Industrial Results
What has CONCUR Achieved?
 Used commercially available software
 Used open standard product models
 Established a web based multi-user environment for exchanging project
information
 Demonstrated a link between Electronic Document Management
Systems (EDMS) and a Product Data Technology (PDT) object database
 Demonstrated with real industrial information
 Deployed on real projects
Next
Back
Directory
Return
-98-
 Contributed to the development of open standards
 Has shown that bidding can take less time and effort
CONCUR
Results: Partner Commercial Exploitation
 Taylor Woodrow
Taylor Woodrow is making extensive use of project web sites. The company is wanting to move from a
project to product way of doing business. A live construction project is using IFC and CIS standards
for exchanging information down and integrating the supply chain. The company is now starting to
address the human and organisational issues. The project results are influencing the TW ICT
investment programme for product and project modelling.
 Skanska
Skanska is developing and investing in the the Facets work where modelling is supporting the
programming and estimating for projects. IFCs are a important part of this thinking.
 Fortum Engineering
Fortum Engineering are also moving to a product way of doing business. CONCUR has helped the
company to start integrating processes and the results are the basis of data warehouse plans for
corporate information. The project has helped Fortum to integrate the use of information so that
risks can be quantified quickly.
 STABU
The Lexicon development is the basis of an international standardisation initiative to identify a taxonomy
of construction terms with definitions. These can be used for eCommerce purposes and will
eventually provide a logical integration with Product Data Technology and specifications. STABU
are also exploiting the work commercially by populating the taxonomy with construction product and
service information which will complement their existing business.
Next
Back
Directory
Return
-99-
All partners have much better knowledge and expertise with
which to make investment decisions
CONCUR
Results: External Commercial Exploitation
 Software Vendors using CONCUR Results
 Directly:
 EPM Technology Ltd (Express Data Manager)
 Solibri (Facets)
 Elstree Computing Ltd (Cost Planning)
 Indirectly:
 Autodesk (Arcitectural Desktop)
 Nemetschek (All-Plan)
 Graphisoft(ArchiCad)
 Significant interest from the Smaller Vendors
 Smaller vendors usually provide specialist software
 Smaller vendors see interoperability as a route to a wider market
 Smaller vendors can react and customise more quickly
 Commercial Software is expensive to Develop
 Research Projects and partners do not have the resource to develop commercial software
which requires 10x the resource required for a prototype.
 Commercial software requires maintenance and a commercial support infrastructure
 Therefore it is essential to involve commercial vendors
Next
Back
Directory
Return
-100-
 Open standards are developing Slowly





Many vendors are wary of open standards
With proprietary standards being an issue
Open standards development is under funded and often voluntary
Vendors are driven by the market which has an 18 month cycle
Demand & demand – and you might get – sometime in the not too distant future!!!
CONCUR
Links to External Partners
 EPM Technology
 Solibri
 Elstree Computing Ltd
 DOORS (Telelogic UK Ltd)
 Related R&D Projects
Related Software
 Autodesk
 Nemetschek
 ArchiCad
Next
Back
Directory
Return
-101-
CONCUR
Related R&D Projects
 ProCure
Information & Communication Technology (ICT) at work for the
Large Scale Engineering (LSE) ProCurement Chain
 OSMOS
??
 Globeman
??
 eLegal
??
 eConstruct
Electronic Business in the Building and Construction Industry.
Preparing for the Next Generation Internet
Next
Back
Directory
Return
-102-
 WeConstruct??
??
CONCUR - The Way Forward
 Make better use of information models
 CONCUR used IFC based object models throughout the project where the objects are the building elements. The project
explored the limits of using these models and found that although the objects can be used there is a great need to deepen
and broaden the IFCs. It is also clear that models which are native to modelling systems will always be richer than
standard models but with the penalty of limited or no interoperability. The partners found that it is essential for users to
create project models from an object point of view based on the building elements. Major advantages of using IFCs were
the facility to exchange objects between different sectors of industry without losing or corrupting information and the ability
to exchange and store property and attribute information in addition to geometry for use in other systems, such as
estimating. The effective use of standard models aids the change from project to product ways of thinking.
 Do more work on the inception area
 During the project it became clear that the front end work with the client and the inception modelling area requires more
R&D effort. This is a key area which can initiate models, programmes and cost plans. There are clear links with knowledge
management, data warehouses and artificial intelligence systems to ‘first guess’ project models to speed up the conceptual
work downstream. There is a need for Building Wizards.
 Make links to E-commerce & business
 There is a need to develop links between the worlds of Product Data Technology and eCommerce. This will widen the
usefulness of project models to support the needs of estimating, purchasing and facilities management. This will move
product modelling into the mainstream of business. This will result in models being used by software other than modelling
systems. Access will be required to extract and add information to the models by applications such as spreadsheets. The
VTT XML interface to a STEP database is a move in this direction. It is important to have compatibility between PDT, EDI,
catalogue formats and eCommerce.
 Continue RTD investment
Next
Back
Directory
Return
-103-
 European and national bodies need to find ways to support the development of model schemas and research into related
applications. It is of general use throughout the industry but beyond the scope of individual companies. The work is
currently being moved forward by member based (not for profit) organisations which supply funding for the work.
 Involve vendors
 It is essential that the software vendors are involved in the R&D work. Experience has shown that vendors value being
kept informed about developments. Within CONCUR software vendors became involved towards the end of the project as
associate contractors where they implemented the research ideas and brought them to market. This was a good fit with
their development programmes which are usually less than 24 months. Only commercial vendors have the skills and
resources to commercially robust software and support.
Taylor Woodrow Construction Limited
Next
Back
Directory
Return
-104-
Organisation
Division
Department
Dept. No.
Secretary
E-mail
Phone
Fax
Mail
Address
WWW
Taylor Woodrow Construction Limited
Engineering Division
Research and Development
N951
Reeta Moholkar
reeta.moholkar@taywood.co.uk
+44 (0)20 8575 4856
+44 (0)20 8575 4277
See address
345 Ruislip Road, Southall, Middlesex, UB1 2QX, United Kingdom
Taylor Woodrow Construction Ltd
http://www.twc.co.uk/
Consultancy in Design & Technology
http://www.tel-consult.co.uk/
Contacts
E-mail
Phone
GSM
Visit
David Leonard
david.leonard@taywood.co.uk
+44 (0)20 8575 4888
+44 (0)7747 756 024
Floor 3 Zone 6
Travel
Hotels
Address, Map
Details
Jeff Stephens
jeff.stephens@taywood.co.uk
+44 (0)20 8575 4626
+44 (0)7798 831 899
Floor 3 Zone 6
Skanska Teknik
Next
Back
Directory
Return
-105-
Organisation
Division
Department
Dept. No.
Secretary
E-mail
Phone
Fax
Mail
Address
visits:
Skanska Teknik
WWW
Teknik Skanska AB
Contacts
E-mail
Per Hogard
Lennart Klintmalm
Adina Jagbeck
per.hogard@teknik.skanska.se
Lennart.klintmalm@teknik.skanska.se
adina.jagbeck@teknik.skanska.se
Phone
+46 8 753 8806
+468 753 8369
+46 8 5043 5000
GSM
+4670 659 4871
n.a
+46 70 835 04 15
Visit
Travel
Anne-Marie Beverloo
+46 8 753 60 48
169 83 Solna, Stockholm, Sweden
Råsundavägen 2
Fortum Engineering
Organisation
Division
Department
Dept. No.
Secretary
E-mail
Phone
Fax
Mail
Address
WWW
Fortum Engineering Ltd
Contacts
E-mail
Phone
Jari Puttonen
Jari.puttonen@fortum.com
+358 10 453 2222
Next
Back
Directory
Return
-106-
Travel
See address
POB 10, FIN - 000 48 Fortum, Rajatorpantie 8, Vantaa, Finland
Fortum Engineering Ltd
http://www.fortum.com
Pekka Valikangas
Pekka.valikangas@fortum.com
+358 10 453 2245
STABU
Organisation
Division
Department
Dept. No.
Secretary
E-mail
Phone
Fax
Mail
Address
Next
Back
Directory
Return
-107-
WWW
Stichting Standaardbestek Burger-en Utilitsbouw
n.a
Research & Development
n.a
Tineke Simonse, Christa Bruis
postmaster@stabu.nl
+31 318 633026
+31 318 635957
See address
PO Box 36, NL-6710 BA, Ede, The Netherlands
Willy Brandtlaan 81
NL-6716 RJ, Ede, The Netherlands
http://www.stabu.nl/
Contacts
E-mail
Phone
GSM
Maarten van Hezik
mvanhezik@stabu.nl
+ 31 318 633 026
+ 31 651 36 96 71
Travel
Hotel
Route, Map
Reehorst, Route, Map (as above)
Kees Woestenenk
kwoestenenk@stabu.nl
+31 318 633026
n.a.
VTT
Next
Back
Directory
Return
-108-
Organisation
Division
Department
Dept. No.
Secretary
E-mail
Phone
Fax
Mail
Address
WWW
Technical Research Centre of Finland
Building Technology
Concurrent Engineering
RTE23
Jaana Streng
jaana.streng@vtt.fi
+ 358 9 456 6938
+358 9 4566 251
See address
PO Box 1801, FIN-02044 VTT, Finland
VTT Building Technology
http://cic.vtt.fi/
Contacts
E-mail
Phone
GSM
Visit
Matti Hannus
matti.hannus@vtt.fi
+358 9 456 6948
+358 40505 4577
Floor 2 Room
Maria Nikolaenko
maria.nikolaenko@vtt.fi
+358-9-456 6993
+358 408259394
Floor 2 Room 203B
Travel
KTH
Organisation Kungliga Tekniska Hogskolan (Royal School of Engineering)
Division
Department
Dept. No.
Secretary
E-mail
Phone
Fax
Mail
See address
Address
Byggandets Org & Ekonomi, Drottning Kristinas väg 30, S-100 44 Stockholm
WWW
Contacts
E-mail
Phone
GSM
Visit
Next
Back
Directory
Return
-109-
Travel
KTH
Robert Noack
robert.noack@eurostep.com
+468 790 9073
+4670 511 6913
Professor Örjan Wikforss
wikforss@recm.kth.se
+
+
TUD
Organisation
Division
Department
Dept. No.
Secretary
E-mail
Phone
Fax
Mail
Address
Next
Back
Directory
Return
-110-
WWW
Technische Universiteit Delft
Faculty of Civil Engineering & Geosciences
Civil Engineering Informatics
n.a.
Gina de Kok
G.deKok@ct.tudelft.nl
+31 15 2784239
+31 15 2787700
See address
PO Box 5048, NL-2600 GA, Delft, The Netherlands
Stevinweg 1, 3th floor
Delft, The Netherlands
http://cti.ct.tudelft.nl
Contacts
E-mail
Phone
GSM
Visit
Prof. Frits Tolman
F.Tolman@ct.tudelft.nl
+31 15 2781652
n.a
Room 3.39
Travel
Hotel
http://cti.ct.tudelft.nl/general/location.html
http://www.delfthotels.nl/engels/index.html
Saban Ozsariyildiz
ozsariyildiz@ct.tudelft.nl
+3115 278 4330
n.a
n.a
Organisation
Division
Department
Dept. No.
Secretary
E-mail
Phone
Fax
Mail
Address
WWW
Next
Back
Directory
Return
-111-
TNO
Nederlandse Organisatie voor Toegepast Natuurwetenschappelijk Onderzoek
Engineering Mechanics and Information Technology (MIT)
Information Technology for Building and Construction (ITBC)
Jolanda van der Gaag
ITBC@bouw.tno.nl
+31(15)2695226
+31(15)2695335
See address
PO Box 49, NL-2600 AA, Delft, The Netherlands
Schoemakerstraat 97, NL-2628 VK, Delft, The Netherlands
TNO Zuidpolder Complex, Building MN, 3th Floor
TNO Building and Construction Research (BOUW)
http://www.bouw.tno.nl/
Contacts
E-mail
Phone
Visit
Michel Böhms
M.Bohms@bouw.tno.nl
+31 15 269 5304
Room MN 3.157
Peter Bonsma
P.Bonsma@bouw.tno.nl
+31 15 269 5306
Room MN 3.152
Travel
Hotel
http://www.bouw.tno.nl/TnoBouwWWW/about_us/locations/delft.html
http://www.delfthotels.nl/engels/index.html
CONCUR
Mid Term Review Demonstration Scenario
Next
Back
Directory
Return
-112-
CONCUR
Mid Term Review - UK Overview
Client Enquiry
Assess Enquiry
Analyse Requirements
Respond to
Requirements
Develop Concept Design
Drawings & Calculations
Reports
Price Concept
Next
Back
Directory
Return
-113-
Reports
Cost Plan
Bid
CONCUR
Mid Term Review - UK Detailed Scenario
Enquiry Information
TEXT
NATIVE file link
Reports
DOORS
SPF
CSV
CATOPro
CSV
SPF
SpecComposer
CSV
SDAI
SpecApplier
ODBC
MS-Access
CostAssessor
SPF
CSTB
CSC v2
Report
SPF
SDAI
JAVA
TNO Browser
Back
Directory
Return
-114-
VTT PROMOTE
DWG/DXF
Drawings
EPM-EDM
Project
Information
Repository
SPF
Next
AutoCad
Architectural DeskTop
Cost Plan
IFC Squasher
CSV
CATOPro
CSV
CSV
CSV = Comma separated Variable File
SPF = STEP Physical File (IAI-IFC)
SDAI = STEP Data Access Interface
Price Utility
SPF
CONCUR
Download Area
 Reports
 A list of CONCUR public reports :
 ???
 ???
 A list of other reports :
 ???
 ???
 Software ?
 Digital Information Lexicon etc?
Next
Back
Directory
Return
-115-
Download