Brite-EuRam BE 96-3016
CONCURrent Engineering in Building and Civil Engineering
The Virtual Project Prototype
Main ContributorsJeff Stephens, Taylor Woodrow
Adina Jägbeck, Skanska
Pekka Välikangas, Fortum Engineering
Distribution / Draft 1 / Draft 2 / Report Reference
Date / 5/4/00 / 11/7/00
TW / * / *
FORTUM / * / * / No.
R3401
SKA / * / *
TNO / * / *
DUT / * / * / Status Draft/Issued/Revised
Draft / Rev.
2b
VTT / * / *
KTH / * / *
STABU / * / * / Date
24/7/00 / Rel. to CEC
-
WWW
CEC
Rev. 1
BE96-3016 CONCURR3401 – The Virtual Project Prototype1
Document Control Sheet
Amendment Record
Revision / Status / Page Nos. / Amendment / Date / By1 / Draft / All / For contributions and comments / 5/4/00 / TW
2 / Draft / All / Scenario Diagrams added.
Heading structure included and partner contributions defined / 11/7/00 / TW
3 / Draft / All / FE contribution / 24/7/00 / FE
Table of Contents
1Summary......
2Introduction......
3Generic Project-IMS Scenarios......
3.1Get / Save Documents......
3.2Model merging......
4Fortum Engineering Scenario......
4.1Scenario Description......
4.2Engineering Business Environment......
4.3Software Used......
4.3.1PlantPower......
4.3.2SOLVO......
4.3.3CostPower/CM-Pro......
4.3.4TUD Inception Modeller......
4.3.5STABU Lexicon......
4.3.6IFC Export/Import, VRML......
4.3.7VTT ProMote, ConCur IMS web site......
5Skanska Scenario......
5.1Scenario Description......
5.2Software Used:......
5.2.1FACETS......
5.2.2Other software??......
6Taylor Woodrow Deployment Trial Scenario......
6.1Scenario Description......
6.2Software used:......
6.2.1Inception Support System......
6.2.2CAD applications:......
6.2.3TNO Ifc151Browser......
6.2.4SpecDefiner/SpecComposer......
6.2.5SpecApplier......
6.2.6Estimators Desktop......
6.2.7IFC Squasher......
6.2.8EPM EXPRESS Data Manager......
6.2.9Model Merging and Versioning......
APPENDIX A- TW System requirements......
Appendix B - SpecComposer Export file examples......
B.1IFC Property Set Library using IfcSimpleProperties
B.2IFC Property Set Library using IfcpropertyWithUnits
Appendix C - IFC Squasher export files......
C.1IFX File......
C.2Derived Attribute CSV/PRN file......
C.3Property Set CSV/PRN file......
Table of Figures
Figure 1 – Overview of Deployment Trial Scenarios (diagram needs amending!)
Figure 2 –The Mocel merging process......
Figure 3 – The Project-IMS and Model Merging process......
Figure 4 – Fortum Engineering Deployment Trial Scenario......
Figure 5 – PlantPower in Engineering Business......
Figure 6 – Flow of design information in PlantPower......
Figure 7 – Attachment of responsibilities for sub-contractors in ScopePower......
Figure 8 – Main flow diagram of equipment, steam turbine-generator plant of CHP......
Figure 9 – Site Layout of FGD facilities and buildings of CHP......
Figure 10 – Facility layout of equipment and structures, steam turbine-generator plant of CHP......
Figure 11 – Design rules and cost estimates in PlantPower......
Figure 12 – Design rule in PlantPower......
Figure 13 – Process requirements from SOLVO analyses to Product Model of PlantPower......
Figure 14 – VRML model from direct export from CAD file......
Figure 15 – VRML model from IFC data and ProMote......
Figure 16 – User interface of ProMote......
Figure 17 – Open schema supported by ProMote......
Figure 18 – Data browsing by ProMote......
Figure 19 – Concur IMS Web site – needs an update
Figure 16 – Skanska Deployment Trial Scenario......
Figure 17 - Scenario Architecture......
Figure 18 – Egham building viewed using ArchiCAD......
Figure 19 – Egham building viewed using ALLPLAN......
Figure 20 – Egham building viewed using Architectural Desktop......
Rev. 2
BE96-3016 CONCURR3401 – The Virtual Project Prototype1
1Summary
To be completed by TW
2Introduction
During the design stages of a project the overall costs need to be evaluated at various stages of the design process. For example at the Inception stage, Concept Design stage, Scheme Design stage, Detailed Design stage etc. At each stage the costs will get more accurate and the design will probably change to keep within the overall budget for the project.
Figure 1 – Overview of Deployment Trial Scenarios (diagram needs amending!)
3Generic Project-IMS Scenarios
Introduction by TW
3.1Get / Save Documents
Text and diagram by TW
3.2Model merging
Text by TW
Figure 2 –The Mocel merging process
Figure 3 – The Project-IMS and Model Merging process
4Fortum Engineering Scenario
Fortum Engineering scenario describes the bidding of Combined Heat and Power (CHP) plant within a consortium, where FE as a leading partner is co-operating with construction partners TW and SK. The scenario includes all technical design needed during tender phase. FE defines the type of power plant, makes the first versions of the site and facility layouts and communicates actively with construction partners. Final technical specifications for bid are developed concurrently in consortium.
4.1Scenario Description
Fortum Engineering scenario is shown in Figure 4 below. It covers the following stages in the design of a power plant: Clients brief, Choice of the type of plant, Configuration, Conceptual Design and Schema Design.
Figure 4 – Fortum Engineering Deployment Trial Scenario
Client has identified a facility need and has prepared Tender package including the scope of the facility, securities, financial information and possible feasibility study of the investment. The consortium has been formed and it begins to establish understanding of Client business and facility needs. Client feasibility study and plant technology will be refined and general implementation concept developed. This will lead to basic selection of power plant type.
The net performance value (NPV) of selected power plant type will be optimised with SOLVO. This will define process requirements of CHP and final selection of power plant type will be made.
According the power plant process and described type of power plant, principal construction needs are defined with TUD inception modeller. The scope of delivery and limits of responsibilities in consortium are defined with the ScopePower module of PlantPower. Configuration of power plant is developed with PlantPower. First cost estimates are received from CostPower in PlantPower.
According to configuration, first version of plant layout and layout of steam turbine generator plant is generated with PlantPower. Cost estimates are updated during the process.
First version of layouts are distributed between partners for further design using IFC format in Concurs IMS – see Concur IMS scenario in chapter 3. Feedback from partners are received within Concur IMS and reviewed with VTT´s IFC browser ProMote.
Price for the options, which are not originally included in the client’s scope, but have appeared during the tendering process, will be collected to optional contracts.
4.2Engineering Business Environment
The engineering business environment and related integration of software is shown in Figure 5. PlantPower, expert system for tender phase design, supports the engineering business. Knowledge module is the core of PlantPower, which includes the rules for defining power plants scopes and technical solutions of facilities/buildings and equipment/structures.
Applications will commence by a Plant Scope so, that the identification system of power plant (KKS) and responsibilities between partners are defined. This action is concurrent with process specifications of SOLVO. SOLVO´s output will be taken as process requirements so, that equipment of power plant are specified according to rules in PlantPower. After that facilities/buildings and equipment/structures are generated. User can review cost libraries by CM-Pro, when making decisions. Also different schedules are available in future from MS Project. User has 3 dimensional CAD view and dialogues for selecting and defining technical solutions.
Figure 5 – PlantPower in Engineering Business
PlantPower is connected to Integrated Plant DataBase (IPDB). Integration between business partners is based on IFC data exchange and Concur IMS platform between other design environments, see chapter 3. After successful bidding, integration to delivery project design is based on IPDB and data export to P&ID of Bentley and other CAD tools used in execution design.
4.3Software Used
4.3.1PlantPower
Introduction
PlantPower is an expert system for tender phase design of power plants. It is an artificial intelligent system, where knowledge is collected from different area of power plant technology and application is developed to create technical definitions for extensive amount of facilities of Combined Heat and Power (CHP) plants. All facilities will be defined accurate enough for bidding. The system has three fundamental features: it forms the product model of power plant delivery, generates quickly information and shares it within consortium and different technical areas on power plant design.
Current application supports the design of Flue Gas Desulphurization (FGD) and Steam Turbine Generator (STG) facilities of CHP plants. FGD facilities are defined on site layout / civil engineering level. STG is defined on facility layout / building level.
Flow of Design Information
Figure 6 – Flow of design information in PlantPower
The invitation of tender starts the tender phase design. Plant type and the power plant identification system (KKS/ScopePower) will be defined according to the inception data, where construction data will be defined with the support of TUD´s Inception Modeller. Clients requirements will be studied with energy balance simulation (SOLVO). Simulation results are requirements to process equipment.
Power plant processes in product model will be formed by design rules according to the selected Power Plant type (KKS). The results are placed in product model as Logical Layout. SOLVO results (SOLVO Flow Sheet) will be read to the Product model.
Main equipment and significant auxiliary equipment will be formed by design rules according to specified KKS and SOLVO data. This result will be presented in Main Flow Diagram. The proposed equipment is specifying requirements to site layout design.
Site layout will be formed by design rules according to the equipment list and selected facility composition. In plant layout is specified connections between different facilities and outside world. When the site layout and main equipment is defined, it is possible to calculate first cost estimate inside 10-20% accuracy level.
More detailed rules for facility layout can be executed after the site layout has been developed. All requirements and a suggestion for relevant auxiliary and ancillary systems will be defined. Building and civil engineering belong in ancillary systems. BOM, BOQ and time schedules are based on facility layout level and they will be stored in Integrated Plant Database (IPDB). This information enables the cost estimation inside 2% accuracy level. IPDB will serve in possible implementation project.
Facility layout of building and civil engineering requirements and a suggested solution will be written into IFC 1.5 file, which can be convert to VRML format. This enables 3D viewing in accordance with BOM, BOQ and scheduling lists.
ScopePower
ScopePower as a part of PlantPower supports marketing and sales personnel in the tendering phase. All scope limits of delivery and the responsibilities are defined between consortium partners and sub contractors. The KKS system code usage is harmonised with the product model of PlantPower. The product model of PlantPower will be cross-checked with marketing and sales definitions.
Table 1 below shows the structure of responsibility phases. Possible more detailed equipment and structure attachments overrun the KKS system and facility attachments. If no specific structure and equipment are defined, KKS system and facility attachments are applied for all equipment and structures within current system.
Table 1 Design and responsibility division phases (see also Fig. 7 below)
ID / Initial design: Qualitative determination of overall concepts by merging standard engineering with specific requirements and determination of main technical data for layout.BD / Basic design: Performs initial quantitative determination of design
DD / Detailed design: Performs definitive quantitative determination up to the level of contract
DEL / Delivery: Purchasing, prefabrication, fabrication, pre-assembly, packing and storage up to transport.
TRA / Transport: Actual transport between storing up to transport and storing at site.
ES / Erection supervision: All expert services to erection and installation contractors.
EW / Erection work: Material receiving, inspection, unloading, and storing at site, transportation to erection location, preparation and execution of works, pre-operational tests and commissioning support.
CS / Commissioning supervision: Included in EW
C / Commissioning: Preparation and execution of all activities necessary for start-up of plant equipment and systems
Figure 7 – Attachment of responsibilities for sub-contractors in ScopePower
Main Flow Diagram of Power Plant Equipment
Figure 8 – Main flow diagram of equipment, steam turbine-generator plant of CHP
Power plant configuration will be listed and presented in main flow diagram. Main flow diagram will be drawn in CAD file of MicroStation of Bentley Inc. so, that it can be further implemented to P&ID application of Bentley. All components will be stored in IPDB, which will integrate more applications during delivery design after successful bidding.
Site Layout of facilities and buildings
Figure 9 – Site Layout of FGD facilities and buildings of CHP
Figure 9 describes the site layout of FGD facilities and buildings of CHP. The data contents in site layout and information needs for civil engineering is tested with FGD facilities of CHP.
Facility Layout of equipment and buildings
Figure 10 – Facility layout of equipment and structures, steam turbine-generator plant of CHP
Figure 10 describes the facility layout of equipment and structures of STG plant of CHP. The data contents in facility layout and information needs for building construction design is tested with STG plant of CHP.
Design rules of PlantPower
Figure 11 – Design rules and cost estimates in PlantPower
Figure 11 above describe design rules and cost estimates of PlantPower in different design levels: plant concept (selection of plant type), plant site layout (configuration of STG plant) and plant facility layout (conceptual design of steam turbine building).
Figure 12 – Design rule in PlantPower
Figure 12 above shows as an example instance in the product model of PlantPower and properties and rules related to it.
Technical data of PlantPower
The product model and design rules inside it are coded with Design++ 4.2 of Design Power Inc. Database is MS Access. Graphical user interface (GUI) is coded in JAVA. In GUI is integrated MicroStationJ of Bentley Inc. Interaction between product model, database and GUI is based on SQL.
The minimum needs of the workstation are: Pentium II MMX 400 MHz processor, 128 MB RAM, 2 MB display memory, 1 GB hard disk, 19 inch screen and Windows NT 4.0 operating system.
4.3.2SOLVO
SOLVO is Fortum´s in house program and it is used to get an optimal Net Performance Value (NPV) out from the power plant process in order to get as much power energy from the consumed fuel. The optimisation is based on balance calculations between mass flows and power energy in power plant processes.
Power plant processes are studied under different circumstances and seasons. Clients need to have different energy power combinations of electricity, process steam, district heat, etc. under the total power capacity of boilers and gas turbine. The set of energy balance calculations is defining process requirements for main equipment of power plant – see Figure 13 below.
ConCur project is concentrated to receive results from SOLVO analyses and to make further definitions in order to get initial data to construction design.
The implementation and development of SOLVO is out of ConCur scope.
Figure 13 – Process requirements from SOLVO analyses to Product Model of PlantPower
4.3.3CostPower/CM-Pro
CostPower is implemented from commercial software CM-Pro of CM-System so, that it can be used both stand alone and integrated with PlantPower. Basic structures of Cost libraries are developed within ConCur so, that common cost objects are consistent with Product Model of PlantPower.
Cost estimates are based on BOQ and BOM so, that quantities are received from the specification made by PlantPower and unit prices are maintained in CM-Pro´s cost libraries.
Tender calculations are partly based on cost estimate so, that extra expenses, risks, gross margin are added to unit price breakdown.
Budgeting is based on cost estimate. CM-Pro is used also on supervision of project economy during the delivery of power plants.
4.3.4TUD Inception Modeller
The Inception Modeller has been developed by the TUD. Analysis between the Client Inception and the Power Plant Concept is based on knowledge received in FE and coded into the application.
TUD Inception Modeller is a Prototype of Expert System to Civil Engineering part of the Product Model of FE´s PlantPower. The application is written in Java.
Saban, more text?
TUD is responsible for this work
4.3.5STABU Lexicon
Analysis of the structure of the Product Model will be done with STABU Lexicon. Information Structures are browsed as well as dependencies between different components. Properties and measurements will explain the nature of different components and the structure of product model.
Kees, more text?
STABU is responsible for this work
4.3.6IFC Export/Import, VRML
Data exchange between the Product Model of PlantPower and different partner´s commercial CAD applications is based on IFC 1.5.1 standard.
VRML models, see examples in Figures 14 and 15, can be generated two ways: directly from CAD file with MicroStationJ of Bentley or from IFC file with ProMote of VTT. Figures 14 and 15 show that direct export CAD file to VRML file give more robust outlook, but at the same time property and structural information of the product model get lost.
Figure 14 – VRML model from direct export from CAD file
Figure 15 – VRML model from IFC data and ProMote
4.3.7VTT ProMote, ConCur IMS web site
ProMote is developed in VTT. It is a tool for browsing STEP data. The application is coded in JAVA. ProMote supports multiple schemas so, that it is possible to browse different kind of STEP schemas and their data contents. In Concur, FE is concentrated in IFC 1.5.1.
ProMote translates VRML description from IFC data so, that it is possible to review three-dimensional presentation also with common VRML browsers. Cosmo Player is used in VRML viewing. This is also a basis in Concur´s IMS web site at VTT so, that it is possible to point out also documents relation with product model in 3D.
Maria, more text?
VTT is responsible for this work
Figure 16 – User interface of ProMote