1. -1- Return Back Next Directory CONCUR CONCUR Brite EuRam BE96-3016 Results

2. -2- Return Back Next Directory CONCUR Presentation Directory Page  Project Summary Project Summary  Demonstration Scenario Demonstration Scenario  Information Management System (IMS) Information Management System (IMS)  Ifc Browser Ifc Browser  LexiCon LexiCon  Inception Modeller Inception Modeller  Facets (Skanska) Facets (Skanska)  PlantPower (Fortum Engineering) PlantPower (Fortum Engineering)  Technical, Commercial and External Exploitation Technical, Commercial and External Exploitation  External Results External Results  The Way Forward The Way Forward  Partners Partners  European Commission Project Details and Contact European Commission Project Details and Contact  Download area Download area

3. -3- Return Back Next Directory CONCUR Project Summary  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.The Way Forward

4. -4- Return Back Next Directory 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.

5. -5- Return Back Next Directory 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  Support concurrent working

6. -6- Return Back Next Directory 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 (IAI- IFC). STEP Data Access Interface was also used. This demonstrated that interoperability was possible but was not commercially robust and flexible.mid-term demonstration  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.results demonstration business scenario  Implement Enhanced Production Software Applications  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.

7. -7- Return Back Next Directory European Commission Project Details and EC Contact CONCURConcurrent Design and Engineering in Building and Civil Engineering Project NumberBE96-3016 Contract NumberBRPR-CT96-0357 Start date 1 February 1997 Duration 4.5 years Finnish date 31 July 2001 Man years30 for eight partners Value5 454 000 Euros Co-ordinating PartnerTaylor Woodrow Construction Ltd. Project ManagerDavid Leonard EC Project OfficerMaria Cristina MAROLDA European Commission Research Directorate-General Competitive and Sustainable Growth E-mailmaria-cristina.marolda@cec.eu.int Phone+32 (0)2 295 83 91 Fax+32 (0)2 296 05 50 MailRue de la Loi/Wetstraat 200, B-1050 Bruxelles/Brussel AddressRue Montoyer/Montoyerstraat 75, B1050 Bruxelles/Brussel Partners

8. -8- Return Back Next Directory Project Partners R & D Partners Classification Construction Companies

9. -9- Return Back Next Directory CONCUR Demonstration Scenario  Description Description  Photograph of the Demonstration Building Photograph of the Demonstration Building  The Business Scenario The Business Scenario  The information Flows The information Flows The CONCUR project included demonstrations of technology using commercial software and realistic industrial information.

10. -10- Return Back Next Directory 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:  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.business activities information flows  A power station typical of that used in the demonstration shown on the photograph with the Turbine House ringed.photograph Business Scenario

11. -11- Return Back Next Directory Demonstration Object Turbine House Fortum Engineering Turbine house

12. -12- Return Back Next Directory COMPARE suggested models and CHOOSE one Fortum Eng. Define SCHEME T- building Taylor Woodrow Scheme modeller Define SCHEME T- building Skanska Scheme modeller MERGE TW models Fortum Eng. Model Merger Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software Define INCEPTION TURBINE BUILDING T.U. Delft Inception Modeller Business Scenario MERGE Skanska models Fortum Eng. Model Merger Client Brief Bid Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Information Flows Business Scenario Description

13. -13- Return Back Next Directory 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..

14. -14- Return Back Next Directory Define SCHEME T- building Skanska FACETS MERGE TW models Fortum Eng. Model Merger Information Flows MERGE Skanska models Fortum Eng. Model Merger ProjectWise EPM-EDM Project IMS Project IMS - I IFC FE1 Project IMS FE1 TW1 SK1 Project IMS - -IV FE1 + SK1 FE1 + TW1 Project IMS III IFC FE1 IFC SK1 IFC TW1 IFC FE2 IFC SK1 IFC TW1 IFC FE1 Project IMS -II FE IMS SK IMS TW IMS Client Brief Web based Project IMS Define SCHEME T- building IFC Browser Taylor Woodrow Define CONCEPT Turbine BUILDING Fortum Eng. PlantPower Design CONFIGURATION for Steam Turbine Plant Fortum Eng. Scopepower Bid Define Building INCEPTION MODELLER TU Delft TUD Software COMPARE suggested models and CHOOSE one Fortum Eng.

15. -15- Return Back Next Directory 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 systemsDOORSmid term trial  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.

16. -16- Return Back Next Directory 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.  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.

17. -17- Return Back Next Directory CONCUR Inception Modeller  The three Level approach  Further information  Reports describing the CONCUR Inception Modelling work are available in the Download Area.Download Area  Contacts at TU Delft are Professor Frits Tolman: F.Tolman@CT.TUDelft.nl and Saban Ozariyildiz ozsariyildiz@ct.tudelft.nlF.Tolman@CT.TUDelft.nlozsariyildiz@ct.tudelft.nl

18. -18- Return Back Next Directory 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  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.nlF.Tolman@CT.TUDelft.nl

19. -19- Return Back Next Directory COMPARE suggested models and CHOOSE one Fortum Eng. FE SW Define SCHEME T- building Skanska Scheme modeller MERGE TW models Fortum Eng. Model Merger Plant configuration MERGE Skanska models Fortum Eng. Model Merger Bid FE IMS Client Brief Project database Define SCHEME T- building Scheme modeller Taylor Woodrow Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Define Building INCEPTION MODELLER TU Delft TUD Software

20. -20- Return Back Next Directory 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:PlantPower  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  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  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 PlantPower Flowchart Back to Information Flows

21. -21- Return Back Next Directory IFC Scope Energy balance LOGICAL LAYOUT PLANT CONFIGURATION FACILITIES Cost Estimate for BID BOQ, Cost Estimate, Time schedules, Procurement, Subcontracts CostPower PLANT DATADASE Invitation to Tender PLANT LAYOUT Main Equipment 1 st Cost Estimate Plant configuration and layout - CONCUR / Fortum Engineering demonstration Back to Information Flows

22. -22- Return Back Next Directory 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  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 PlantPower Flowchart Concept Design Flowchart Back to Information Flows

23. -23- Return Back Next Directory Scope Energy balance LOGICAL LAYOUT PLANT CONFIGURATION FACILITIES Cost Estimate for BID FE/VTT IMS Invitation to Tender PLANT LAYOUT Main Equipment 1 st Cost Estimate Building Conceptual Design - CONCUR demonstration of Fortum Engineering/VTT IMS BOQ, Cost Estimate, Time schedules, Procurement, Subcontracts DocumentsProduct modelData exchange STEP/IFC Back to Information Flows

24. -24- Return Back Next Directory 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.  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.

25. -25- Return Back Next Directory COMPARE suggested models and CHOOSE one Fortum Eng. Define SCHEME T- building Skanska Scheme modeller MERGE TW models Fortum Eng. Model Merger IMS Upload MERGE Skanska models Fortum Eng. Model Merger Bid ProjectWise EPM-EDM Project IMS Project IMS - I IFC FE1 FE IMS Client Brief Project database Define SCHEME T- building Scheme modeller Taylor Woodrow Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Define Building INCEPTION MODELLER TU Delft TUD Software

26. -26- Return Back Next Directory 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 XML Access

27. -27- Return Back Next Directory Real life projects D++ CM Company specific IMS system CONCUR IMS: Web based Project Environment COMPANY 3 Achitect COMPANY 2 Client COMPANY 1 Company specific information repository Internal working environment within company intranet Project mgr Project document & Object database Project information repository: IMS Architecture

28. -28- Return Back Next Directory 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  Further information  Reports describing the IMS system are available in the Download Area  Contact at VTT is Maria Nikolaenko:maria.nikolaenko@vtt.fi

29. -29- Return Back Next Directory IMS system structure

30. -30- Return Back Next Directory IMS user intefaces Document managment system interface Web interface Documents,situated in choosen folder Documents,situated in choosen folder Interface to upload, documents merge models in the system, XML browsing Interface to upload, documents merge models in the system, XML browsing

31. -31- Return Back Next Directory IMS u ser Interface Viewing models in 3D Viewing models in 3D VR window Available methods for the selected objects in VR window Document related to the selected object Document related to the selected object

32. -32- Return Back Next Directory IMS Store product model Main functions of IMS Download files from doc mgt system Merge product models Extract partial product model data End user Upload files to doc mgt system Link file to a product model object

33. -33- Return Back Next Directory IMS Upload files Diagram

34. -34- Return Back Next Directory IMP user interface Upload files Select ”Add file” Add new file form User enters metadata

35. -35- Return Back Next Directory IMS Model Merging Diagram ProjectWiseIMS servlet Merge A, B Get A, B Insert A, B OK Merged model C Merge A, B OK (C stored in ProjectWise) Command to EPM-EDM Start situation: Source model files reside in ProjectWise End situation: Merged model file is stored in ProjectWise User

36. -36- Return Back Next Directory IMS user interface Model Merging form Select ”Merge models” Select ”Merge models” Merge models User enters metadata

37. -37- Return Back Next Directory IMS product model server & XML interface VTT Building Technology, Finland

38. -38- Return Back Next Directory IMS - XML interface Object properties in XML format Request object data

39. -39- Return Back Next Directory 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.  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.Download Area  Contacts: Maria Nikolaenko at VTT: maria.nikolaenko@vtt.fi, EPM Technology website & Jorulv Rangnes at EPM Jorulv.Rangnes@epmtech.jotne.commaria.nikolaenko@vtt.fiEPM Technology Jorulv.Rangnes@epmtech.jotne.com

40. -40- Return Back Next Directory CONCUR EDM and CONCUR - 2  Further information  Reports describing the CONCUR Project’s use of the Express Data Manager are available in the Download Area.Download Area  Contact at VTT is Maria Nikolaenko: maria.nikolaenko@vtt.fi & Jorulv Rangnes at EPM Jorulv.Rangnes@epmtech.jotne.commaria.nikolaenko@vtt.fi Jorulv.Rangnes@epmtech.jotne.com CAD Modelling System Project (IMS) [ProjectWise] EPM-EDM IFC Browser Other Modelling System XML Access by MS-Office products Other Application Type Generation of Derived Attributes Express X Model Merging Services from EDM

41. -41- Return Back Next Directory 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.  Further information  Reports describing the CONCUR Project’s use of the Express Data Manager are available in the Download Area.Download Area  Contact at EPM is Jorulv Rangnes Jorulv.Rangnes@epmtech.jotne.comJorulv.Rangnes@epmtech.jotne.com

42. -42- Return Back Next Directory 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.  Further information  Reports describing the CONCUR Project’s use of the Express Data Manager are available in the Download Area.Download Area  Contact at EPM is Jorulv Rangnes Jorulv.Rangnes@epmtech.jotne.comJorulv.Rangnes@epmtech.jotne.com

43. -43- Return Back Next Directory 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.  Further information  Contact at EPM: Jorulv Rangnes Jorulv.Rangnes@epmtech.jotne.comJorulv.Rangnes@epmtech.jotne.com

44. -44- Return Back Next Directory COMPARE suggested models and CHOOSE one Fortum Eng. Define SCHEME Turbine Building Skanska Scheme modeller Develop Scheme Skanska MERGE Skanska models Fortum Eng. Model Merger Bid ProjectWise EPM-EDM Project IMS Project IMS - I IFC FE1 FE IMS SK IMS Client Brief MERGE TW models Fortum Eng. Model Merger Project database Define SCHEME T- building Scheme modeller Taylor Woodrow Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Define Building INCEPTION MODELLER TU Delft TUD Software

45. -45- Return Back Next Directory 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.

46. -46- Return Back Next Directory Turbine House Building Scheme

47. -47- Return Back Next Directory Turbine House in ArchiCad Explore SKANSKA FACETS

48. -48- Return Back Next Directory Facets Project development with split vision Adina Jägbeck, Lennart Klintmalm - Skanska Teknik AB Pasi Paasiala - Solibri OY

49. -49- Return Back Next Directory 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 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 The use context for Facets Scheme Design is co-ordination between design, cost estimation and process planning. The system imports CAD-information in IFC- format, 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. 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.

50. -50- Return Back Next Directory Concept Scale - 1:1000 Tme -1 Info - 1Concept Scale - 1:1000 Tme -1 Info - 1 Scheme Scale - 1:100 Time -10 Info - 1 000Scheme Scale - 1:100 Time -10 Info - 1 000 Working docs Scale - 1:10 Time -100 Info - 1 000 000 Pre-studyDesign - procurementProgramme Introduction 2: Such phase, such requirements Facets’ context Run - Maintain

51. -51- Return Back Next Directory 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! Experience

52. -52- Return Back Next Directory 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 ? In other words: Complete basis for decision faster

53. -53- Return Back Next Directory Skiss 1 Skiss 2 Skiss 3 Facets Site Developer - ”all in one box” Space use Aesthetic Rent Site Sketch.. Function Economy Experience based figures The boxes contain links. Use the ”back arrow” to return to this page

54. -54- Return Back Next Directory 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  Good basis for decision  Good definition for next phase

55. -55- Return Back Next Directory 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 In other words: coordinated professional project information for procurement and detail design

56. -56- Return Back Next Directory Facets Scheme Design: Coordinate information from professional tools CostTime Product MethodRecipe Test project The boxes contain links. Use the ”back arrow” to return to this page

57. -57- Return Back Next Directory Result of using Facets Scheme Design Product model with several aspect  Product definition from CAD (now: ifc 2.0 import of architectural drawings Planned: also building services)  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

58. -58- Return Back Next Directory COMPARE suggested models and CHOOSE one Fortum Eng. Define SCHEME Turbine Building Skanska Scheme modeller Develop Scheme Skanska MERGE Skanska models Fortum Eng. Model Merger Bid ProjectWise EPM-EDM Project IMS Project IMS - I IFC FE1 Project IMS IFC SK1 IFC FE1 Project IMS -II FE IMS SK IMS Client Brief MERGE TW models Fortum Eng. Model Merger Project database Define SCHEME T- building Scheme modeller Taylor Woodrow Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Define Building INCEPTION MODELLER TU Delft TUD Software

59. -59- Return Back Next Directory COMPARE suggested models and CHOOSE one Fortum Eng. Define SCHEME T- building Skanska Scheme modeller Develop Scheme Taylor Woodrow MERGE Skanska models Fortum Eng. Model Merger Bid ProjectWise EPM-EDM Project IMS Project IMS - I IFC FE1 Project IMS IFC SK1 IFC FE1 Project IMS - II FE IMS SK IMS TW IMS Client Brief MERGE TW models Fortum Eng. Model Merger Project database Define SCHEME T- building Scheme modeller Taylor Woodrow Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software Define Building INCEPTION MODELLER TU Delft TUD Software

60. -60- Return Back Next Directory 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..

61. -61- Return Back Next Directory Turbine House Building Scheme

62. -62- Return Back Next Directory COMPARE suggested models and CHOOSE one Fortum Eng. Define SCHEME T- building Skanska Scheme modeller Develop Scheme Taylor Woodrow MERGE Skanska models Fortum Eng. Model Merger Bid ProjectWise EPM-EDM Project IMS Project IMS - I IFC FE1 Project IMS IFC SK1 IFC TW1 IFC FE1 Project IMS - II FE IMS SK IMS TW IMS Client Brief MERGE TW models Fortum Eng. Model Merger Project database Define SCHEME T- building Scheme modeller Taylor Woodrow Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software Define Building INCEPTION MODELLER TU Delft TUD Software

63. -63- Return Back Next Directory 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  Further information  Reports describing the IFC Browser work are available in the Download Area.Download Area  Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nlP.Bonsma@bouw.tno.nl M.Bohms@bouw.tno.nl

64. -64- Return Back Next Directory CONCUR Ifc Browser Architecture EDM Supervisor IfcBrowser Java Server IFC1.5.1 EXPRESS-to-Java/SDAI Generator in Java Java SDAI-Binding (late) IfcBrowser Java Client + RMI/HTTP Generates Running in Java-enabled Internet Browser Meta-data (DD) Access Java IFC-Binding (early) IFC-data (MD) Access NT4.0/W2KUnix/Microsoft Here: MS IE5 + Sun Java 1.2 Plug-in EDM DB C SDAI-Binding

65. -65- Return Back Next Directory CONCUR Ifc Browser- Screen shot

66. -66- Return Back Next Directory 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  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.Download Area  Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nlP.Bonsma@bouw.tno.nl M.Bohms@bouw.tno.nl

67. -67- Return Back Next Directory 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.  Further information  Reports describing the IFC Browser work are available in the Download Area.Download Area  Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nlP.Bonsma@bouw.tno.nl M.Bohms@bouw.tno.nl

68. -68- Return Back Next Directory CONCUR CONCUR Ifc Developments  PDM MetaData Structures for Documents  Ifc Derived Attributes  Ifc Model Merging  Ifc Property Sets  Further information  Reports describing the IFC Browser work are available in the Download Area.Download Area  Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nlP.Bonsma@bouw.tno.nl M.Bohms@bouw.tno.nl

69. -69- Return Back Next Directory 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:  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.Download Area  Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nlP.Bonsma@bouw.tno.nl M.Bohms@bouw.tno.nl

70. -70- Return Back Next Directory 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: LINKSIMPLICITYNEEDSSUPPORT STEP---  IFC  -  CONCUR  (but  if harmonized with the IAI)  Further information  Reports describing the IFC Browser work are available in the Download Area.Download Area  Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nlP.Bonsma@bouw.tno.nl M.Bohms@bouw.tno.nl

71. -71- Return Back Next Directory 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.  Further information  Reports describing the IFC Browser work are available in the Download Area.Download Area  Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nlP.Bonsma@bouw.tno.nl M.Bohms@bouw.tno.nl

72. -72- Return Back Next Directory CONCUR Ifc - Model merging – Why?  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.Download Area  Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nlP.Bonsma@bouw.tno.nl M.Bohms@bouw.tno.nl

73. -73- Return Back Next Directory CONCUR Ifc - Model Merging Philosophy

74. -74- Return Back Next Directory COMPARE suggested models and CHOOSE one Fortum Eng. Define SCHEME T- building Skanska Scheme modeller MERGE TW models Fortum Eng. Model Merger MERGE Skanska models Fortum Eng. Model Merger Bid ProjectWise EPM-EDM Project IMS Project IMS - I IFC FE1 Project IMS FE1 TW1 SK1 IFC SK1 IFC TW1 IFC FE1 Project IMS -II FE IMS SK IMS TW IMS Client Brief Merge Concept & Scheme Project database Define SCHEME T- building Scheme modeller Taylor Woodrow Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software

75. -75- Return Back Next Directory 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..

76. -76- Return Back Next Directory Ifc Model Merging Views

77. -77- Return Back Next Directory 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.  Further information  Reports describing the IFC Browser work are available in the Download Area.Download Area  Contacts at TNO are Peter Bonsma: P.Bonsma@bouw.tno.nl & Michel Böhms M.Bohms@bouw.tno.nlP.Bonsma@bouw.tno.nl M.Bohms@bouw.tno.nl

78. -78- Return Back Next Directory COMPARE suggested models and CHOOSE one Fortum Eng. Define SCHEME T- building Skanska Scheme modeller MERGE TW models Fortum Eng. Model Merger MERGE Skanska models Fortum Eng. Model Merger Bid ProjectWise EPM-EDM Project IMS Project IMS - I IFC FE1 Project IMS FE1 TW1 SK1 Project IMS - FE1 + SK1 Project IMS III IFC SK1 IFC TW1 IFC FE1 Project IMS -II FE IMS SK IMS TW IMS Client Brief Merge Concept & Scheme Project database FE1 + TW1 Define SCHEME T- building Scheme modeller Taylor Woodrow Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software

79. -79- Return Back Next Directory Define SCHEME T- building Skanska Scheme modeller MERGE TW models Fortum Eng. Model Merger Compare Scheme Solutions MERGE Skanska models Fortum Eng. Model Merger Bid ProjectWise EPM-EDM Project IMS Project IMS - I IFC FE1 Project IMS FE1 TW1 SK1 Project IMS - -IV FE1 + SK1 FE1 + TW1 Project IMS III IFC FE1 IFC SK1 IFC TW1 IFC FE2 IFC SK1 IFC TW1 IFC FE1 Project IMS -II FE IMS SK IMS TW IMS Client Brief Project database Define SCHEME T- building Scheme modeller Taylor Woodrow Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software Description # Fortum Eng. COMPARE suggested models and CHOOSE one

80. -80- Return Back Next Directory Turbine House Plant & Skanska Building Solution

81. -81- Return Back Next Directory Turbine House Plant & TW Building Solution

82. -82- Return Back Next Directory 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.

83. -83- Return Back Next Directory Define SCHEME T- building Skanska Scheme modeller MERGE TW models Fortum Eng. Model Merger Bid MERGE Skanska models Fortum Eng. Model Merger ProjectWise EPM-EDM Project IMS Project IMS - I IFC FE1 Project IMS - -IV Project IMS III IFC FE1 IFC SK1 IFC TW1 IFC FE2 IFC SK1 IFC TW1 IFC FE1 Project IMS -II FE IMS SK IMS TW IMS Client Brief COMPARE suggested models and CHOOSE one Fortum Eng. Project database Define SCHEME T- building Scheme modeller Taylor Woodrow Define CONCEPT Turbine BUILDING Fortum Eng. FE Software Design CONFIGURATION for Steam Turbine Plant Fortum Eng. FE Software Bid

84. -84- Return Back Next Directory 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.Cost Plan  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  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

85. -85- Return Back Next Directory CONCUR Typical Cost Plan

86. -86- Return Back Next Directory CONCUR LexiCon  LexiCon Description 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 LexiCon Explorer  A software tool for preparing, editing and inputting content into a LexiCon database. LexiCon database  Spec Explorer Spec Explorer  A software tool for preparing and editing project composition trees.composition trees  The LexiCon Vision The LexiCon Vision  The LexiCon is continuing to grow as an international collaboration.

87. -87- Return Back Next Directory CONCUR LexiCon Description  Common concept definitions and descriptions for the construction industry  Definition of conceptsconcepts  Definition of relations between conceptsrelations 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 conceptsmultiple concepts  International co-operation  Content of the LexiCon is developed by STABU in co-operation with organizations in Europe, Australia, New Zealand and Canadaorganizations  Further information  Contact at STABU is Kees Woestenenk: kwoestenenk@stabu.nlkwoestenenk@stabu.nl  Reports describing the LexiCon work are available in the Download Area.Download Area

88. -88- Return Back Next Directory CONCUR LexiCon Explorer Browser and Editor of LexiCon Classes  LexiCon Classes (based on ISO PAS 12006-3): LexiCon Classes  Subjects (e.g. Built objects, Spaces, Products) Subjects  Activities (Work associated with Subjects) Activities  Aspects (Grouping of Properties) Aspects  Properties, Measures and Values Properties  Units (e.g. SI units) Units  Descriptions of Classes and associated Names  Names and Descriptions in any languagelanguage  Associations between Classes Associations between Classes  Specialization hierarchy Specialization hierarchy  Composition (Part-of associations) Composition  Associated Aspects, Properties, Measures and Values Associated Aspects  References to external documents  Standards (e.g. ISO standards, local standards)  Classification systems (e.g. SfB, Master Format, EPIC Classification systems

89. -89- Return Back Next Directory CONCUR LexiCon Explorer Screen shot

90. -90- Return Back Next Directory CONCUR SpecExplorer Editor for project specifications  Covers whole lifespan over projects  Based on project compositionproject composition  Stand alone, user defined  Imported from geometrical model (not available yet)geometrical model  Each node in composition tree is treated as a distinct projectcomposition tree  Usage of LexiCon classes as templates  Additional assignment and specification of Tasks Additional assignment  Task specification  Contractual conditions  Participants  Associated Contacts databaseContacts database

91. -91- Return Back Next Directory CONCUR SpecExplorer Screen shot

92. -92- Return Back Next Directory 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:  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.nlkwoestenenk@stabu.nl  Reports describing the LexiCon work are available in the Download Area.Download Area

93. -93- Return Back Next Directory 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

94. -94- Return Back Next Directory 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  Geometrical model - the geometry of Subjects, modelled in another application, such as a CAD application

95. -95- Return Back Next Directory 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

96. -96- Return Back Next Directory CONCUR Results and Exploitation  Technical Results Technical Results  Industrial Results Industrial Results  Partner Exploitation Partner Exploitation  External Exploitation External Exploitation  The Way Forward from CONCUR The Way Forward from CONCUR

97. -97- Return Back Next Directory 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  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 Related R&D Projects

98. -98- Return Back Next Directory 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  Contributed to the development of open standards  Has shown that bidding can take less time and effort

99. -99- Return Back Next Directory 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. All partners have much better knowledge and expertise with which to make investment decisions

100. -100- Return Back Next Directory 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  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!!!

101. -101- Return Back Next Directory CONCUR Links to External Partners  EPM Technology EPM Technology  Solibri Solibri  Elstree Computing Ltd Elstree Computing Ltd  DOORS (Telelogic UK Ltd) DOORS (Telelogic UK Ltd)  Related R&D Projects Related R&D Projects Related Software  Autodesk Autodesk  Nemetschek Nemetschek  ArchiCad ArchiCad

102. -102- Return Back Next Directory CONCUR Related R&D Projects  ProCure ProCure Information & Communication Technology (ICT) at work for the Large Scale Engineering (LSE) ProCurement Chain  OSMOS ??  Globeman ??  eLegal ??  eConstruct eConstruct Electronic Business in the Building and Construction Industry. Preparing for the Next Generation Internet  WeConstruct?? ??

103. -103- Return Back Next Directory 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  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.

104. -104- Return Back Next Directory Taylor Woodrow Construction Limited OrganisationTaylor Woodrow Construction Limited DivisionEngineering Division DepartmentResearch and Development Dept. No.N951 SecretaryReeta Moholkar E-mailreeta.moholkar@taywood.co.uk Phone+44 (0)20 8575 4856 Fax+44 (0)20 8575 4277 MailSee address Address345 Ruislip Road, Southall, Middlesex, UB1 2QX, United Kingdom WWWTaylor Woodrow Construction Ltdhttp://www.twc.co.uk/http://www.twc.co.uk/ Consultancy in Design & Technologyhttp://www.tel-consult.co.uk/http://www.tel-consult.co.uk/ ContactsDavid LeonardJeff Stephens E-maildavid.leonard@taywood.co.ukjeff.stephens@taywood.co.ukdavid.leonard@taywood.co.ukjeff.stephens@taywood.co.uk Phone+44 (0)20 8575 4888 +44 (0)20 8575 4626 GSM+44 (0)7747 756 024+44 (0)7798 831 899 VisitFloor 3 Zone 6Floor 3 Zone 6 Travel Address, MapAddressMap HotelsDetailsDetails

105. -105- Return Back Next Directory OrganisationSkanska Teknik Division Department Dept. No. SecretaryAnne-Marie Beverloo E-mail Phone Fax+46 8 753 60 48 Mail169 83 Solna, Stockholm, Sweden AddressRåsundavägen 2 visits: WWWTeknik Skanska AB ContactsPer Hogard Lennart Klintmalm Adina Jagbeck E-mail per.hogard@teknik.skanska.se Lennart.klintmalm@teknik.skanska.se adina.jagbeck@teknik.skanska.se per.hogard@teknik.skanska.seLennart.klintmalm@teknik.skanska.seadina.jagbeck@teknik.skanska.se Phone+46 8 753 8806 +468 753 8369 +46 8 5043 5000 GSM+4670 659 4871n.a+46 70 835 04 15 Visit Travel Skanska Teknik

106. -106- Return Back Next Directory Fortum Engineering OrganisationFortum Engineering Ltd Division Department Dept. No. Secretary E-mail Phone Fax MailSee address AddressPOB 10, FIN - 000 48 Fortum, Rajatorpantie 8, Vantaa, Finland WWWFortum Engineering Ltd http://www.fortum.comhttp://www.fortum.com ContactsJari PuttonenPekka Valikangas E-mailJari.puttonen@fortum.comPekka.valikangas@fortum.comJari.puttonen@fortum.comPekka.valikangas@fortum.com Phone+358 10 453 2222+358 10 453 2245 Travel

107. -107- Return Back Next Directory STABU OrganisationStichting Standaardbestek Burger-en Utilitsbouw Divisionn.a DepartmentResearch & Development Dept. No.n.a SecretaryTineke Simonse, Christa Bruis E-mailpostmaster@stabu.nl Phone+31 318 633026 Fax+31 318 635957 MailSee address AddressPO Box 36, NL-6710 BA, Ede, The Netherlands Willy Brandtlaan 81 NL-6716 RJ, Ede, The Netherlands WWWhttp://www.stabu.nl/http://www.stabu.nl/ ContactsMaarten van HezikKees Woestenenk E-mailmvanhezik@stabu.nlkwoestenenk@stabu.nlmvanhezik@stabu.nlkwoestenenk@stabu.nl Phone+ 31 318 633 026 +31 318 633026 GSM+ 31 651 36 96 71n.a. TravelRoute, MapRouteMap HotelReehorst, Route, Map (as above)ReehorstRoute

108. -108- Return Back Next Directory VTT OrganisationTechnical Research Centre of Finland DivisionBuilding Technology DepartmentConcurrent Engineering Dept. No.RTE23 SecretaryJaana Streng E-mailjaana.streng@vtt.fi Phone+ 358 9 456 6938 Fax+358 9 4566 251 MailSee address AddressPO Box 1801, FIN-02044 VTT, Finland WWWVTT Building Technology http://cic.vtt.fi/http://cic.vtt.fi/ ContactsMatti HannusMaria Nikolaenko E-mailmatti.hannus@vtt.fimaria.nikolaenko@vtt.fimatti.hannus@vtt.fimaria.nikolaenko@vtt.fi Phone+358 9 456 6948 +358-9-456 6993 GSM+358 40505 4577+358 408259394 VisitFloor 2 RoomFloor 2 Room 203B Travel

109. -109- Return Back Next Directory KTH OrganisationKungliga Tekniska Hogskolan (Royal School of Engineering) Division Department Dept. No. Secretary E-mail Phone Fax MailSee address AddressByggandets Org & Ekonomi, Drottning Kristinas väg 30, S-100 44 Stockholm WWWKTH Contacts Robert Noack Professor Örjan Wikforss E-mail robert.noack@eurostep.com wikforss@recm.kth.serobert.noack@eurostep.comwikforss@recm.kth.se Phone+468 790 9073 + GSM+4670 511 6913+ Visit Travel

110. -110- Return Back Next Directory TUD OrganisationTechnische Universiteit Delft DivisionFaculty of Civil Engineering & Geosciences DepartmentCivil Engineering Informatics Dept. No.n.a. SecretaryGina de Kok E-mailG.deKok@ct.tudelft.nl Phone+31 15 2784239 Fax+31 15 2787700 MailSee address AddressPO Box 5048, NL-2600 GA, Delft, The Netherlands Stevinweg 1, 3th floor Delft, The Netherlands WWWhttp://cti.ct.tudelft.nlhttp://cti.ct.tudelft.nl ContactsProf. Frits TolmanSaban Ozsariyildiz E-mailF.Tolman@ct.tudelft.nl ozsariyildiz@ct.tudelft.nlF.Tolman@ct.tudelft.nl ozsariyildiz@ct.tudelft.nl Phone+31 15 2781652 +3115 278 4330 GSMn.a n.a VisitRoom 3.39n.a Travelhttp://cti.ct.tudelft.nl/general/location.htmlhttp://cti.ct.tudelft.nl/general/location.html Hotelhttp://www.delfthotels.nl/engels/index.htmlhttp://www.delfthotels.nl/engels/index.html

111. -111- Return Back Next Directory TNO OrganisationNederlandse Organisatie voor Toegepast Natuurwetenschappelijk Onderzoek DivisionEngineering Mechanics and Information Technology (MIT) DepartmentInformation Technology for Building and Construction (ITBC) Dept. No.- SecretaryJolanda van der Gaag E-mailITBC@bouw.tno.nl Phone+31(15)2695226 Fax+31(15)2695335 MailSee address AddressPO Box 49, NL-2600 AA, Delft, The Netherlands Schoemakerstraat 97, NL-2628 VK, Delft, The Netherlands TNO Zuidpolder Complex, Building MN, 3th Floor WWWTNO Building and Construction Research (BOUW) http://www.bouw.tno.nl/ ContactsMichel BöhmsPeter Bonsma E-mailM.Bohms@bouw.tno.nl P.Bonsma@bouw.tno.nlM.Bohms@bouw.tno.nl P.Bonsma@bouw.tno.nl Phone+31 15 269 5304 +31 15 269 5306 VisitRoom MN 3.157Room MN 3.152 Travelhttp://www.bouw.tno.nl/TnoBouwWWW/about_us/locations/delft.htmlhttp://www.bouw.tno.nl/TnoBouwWWW/about_us/locations/delft.html Hotelhttp://www.delfthotels.nl/engels/index.htmlhttp://www.delfthotels.nl/engels/index.html

112. -112- Return Back Next Directory CONCUR Mid Term Review Demonstration Scenario

113. -113- Return Back Next Directory CONCUR Mid Term Review - UK Overview Drawings & Calculations Reports Assess Enquiry Analyse Requirements Respond to Requirements Develop Concept Design Price Concept Client Enquiry Reports Bid Cost Plan

114. -114- Return Back Next Directory CONCUR Mid Term Review - UK Detailed Scenario Enquiry Information CostAssessor CATOPro SpecApplier SpecComposer VTT PROMOTE TNO Browser AutoCad Architectural DeskTop IFC Squasher Price Utility MS - Access CATOPro Cost Plan Report Drawings Reports TEXT SPF CSV SPF CSV SPF SDAI JAVA DWG/DXF EPM-EDM Project Information Repository CSTB CSC v2 NATIVE file link SPF SDAI CSV SPF ODBC CSV DOORS CSV = Comma separated Variable File SPF = STEP Physical File (IAI-IFC) SDAI = STEP Data Access Interface

115. -115- Return Back Next Directory CONCUR Download Area  Reports  A list of CONCUR public reports :  ???  A list of other reports :  ???  Software ?  Digital Information Lexicon etc?