English version 1.0
Common InfraBIM requirements YIV2015
Vol 1.0
MANAGING MODEL BASED PROJECT
Jari Niskanen WSP Finland Oy
Infra
modeling
Quality control Supervision and coordination Gathering of initial data Planning, construction, asset management Coordination of disciplines Interaction and collaborationDocument version history
Version Date Author Description
1.0 5.5.2015 Jari Niskanen Guideline
CONTENT
1 INTRODUCTION ... 4
2 Planning a model-based project ... 5
2.1 Planning phases in Finnish planning system ... 5
2.2 Modeling plan ... 6
2.3 Modeling extent and level of accuracy ... 6
3 GOALS WITH MODELING AND PURPOSE of USE MODEL ... 7
4 PROCESS DESCRIPTION ... 7
4.1 Actors ... 8
4.2 Cooperation and data exchange between actors ... 8
4.3 Schedule ... 8
5 Model description document and list of contents ... 8
6 Quantity and cost management ... 9
7 quality assurance ... 10
1
INTRODUCTION
This document describes management of projects which use modeling. Use of modeling effects project organization, phasing, schedule, approach and exchange of information. Project responsible shall be able to evaluate how information modeling can be used to maximize the added value and how modeling contributes to achieve overall project objectives.
2
PLANNING A MODEL-BASED PROJECT
2.1 Planning phases in Finnish planning system
Workflow in an infra project can be described with following diagram. Time spam of project from its first phases to the end can be long. On the other hand, modeling planning can start at any project phase. Starting point in this document is, that an information modeling plan has to be made regardless of project phase. Contents of modeling plan document vary depending on project phase, but these differences are not dealt with in this context.
Data delivered to orderer in infra project
Final product in document-based, main contract form
project
Investment requirements and preliminary design
Final product in model-based, cooperation form project Preliminary design report,
preliminary drawings
General plan
Preliminary design model
General design model General design report,
complement drawings, electronic data
Early design phases, Road, street or railway design
Construction design
Construction
Operation and maintenance Maintenance manual As built drawings Drawings Work specification Design data to be implemented at sites Working drawings
Construction design model 3D-objects ”Required data” Implementation model As built model Asset management model
Initial data model
Initial data model
Road design, complement drawings,
electronic data
Construction design
Road, street or railway model Initial data model
Int er fac e to ar c h iv in g an d adm in is tr at io n s y s tems
Edited from source: Lehtovirta
2.2
Modeling plan
In initiation stage of project, the project responsible makes model plan, which shows:
• general goals of modeling and purpose of use; what the project or process needs the model for
• process description
o project actors, roles (responsibilities) and tasks o cooperation and exchange of data
o schedule
• modeling extent and level of detail
• cost calculation/administration; procedures
• quality assurance
• principles of model utilization in relation to project phase
o design, construction, implementation o use, administration, maintenance o purchase and contracting techniques
Model plan is an appendix document in design contract. Other central documents in engineering procurement as design principals and design program are closely related to it. Most of data shown in modeling plan belongs more naturally in design plan, but it´s more suitable to keep these as separate documents, as long as model documents and design documents have different content and contractual position in construction.
2.3
Modeling extent and level of accuracy
Requirements for modeling extent and level of accuracy are based on earlier specified goals and purpose of use. When specifying and documenting the modeling accuracy and it´s extent, we can lean on specifications in other parts in this requirement and instruction documentation. Requirements concerning the modeling extent and level of accuracy are recommended to be documented in the corresponding form of design program.
Factors affecting the extent and level of accuracy are specified and documented with designing principals, design program and modeling plan. In goal situations, obligations and requirements of modeling are outlined through design principals and program. General modeling requirements offers a foundation which may be relied on in documents.
Picture 1. Definition of design and modeling task. Design principals
Modeling plan document
Design program
3
GOALS WITH MODELING AND PURPOSE OF USE MODEL
Project goals set on modeling are documented in modeling plan document. General goals are for example benefits in securing execution of project, increase productivity and efficiency in construction, improve quality in design and construction, more cost effective controllability of project, benefits offered by model in understanding and its contents and form a picture of project etc.
Purpose of use for modeling is described in the modeling plan document. These can be for instance:
• Description: communication with outside interest groups
• Description: internal communication and transfer of data in a design or construction project
• Clash detection between disciplines
• Clash detection between existing structures and designs
• Ease the determination of construction qualities: link quality requirements for construction parts to model
• Improve quality of procurement: construction project defined with model reduces risks for tenderer and leads to better tenders
• Production scheduling and production control: linking model to schedule with project division and cost control with a model containing quantity data (4D and 5D modeling)
• Life cycle information management: needed data for operation, management and maintenance systems in an easy accessible form; as built model utilized in maintenance manual or it´s user interface
Visualization helps understanding content solutions in design producing explicit, understandable and higher quality data of design situation. When central features of solutions are portrayed explicit enough in model, visualization supports also design, management, control and decision-making. Visualization can serve apart from project group and users, also outside interest groups like authorities’ \, Part 10,
In model-based procurement, models are part of contract documents. With help of models the intelligibility of designs increases, service providers risk decreases and client gets more profitable and higher quality tenders. With help of a model, efficiency can also be sought in dividing project in different procurement packages.
Quality requirements for construction shown in model, improves the client possibilities to state the quality of construction. At the moment it ś not clear how modeling technology will support this goal in the future.
If the goal is to use the produced data from design and construction for the needs of management and maintenance, this shall be taken into account in procurement phase of construction. Parties responsible for maintenance should have a possibility reserved to affect the contents of a modeling plan document.
4
PROCESS DESCRIPTION
Process description contains actors in project, their role in project organization as well as their tasks and responsibilities regarding producing or using the model. In addition, cooperation between actors and exchange of information as well as schedule of project is described.
4.1
Actors
Most central actor in a project is the client. The client is responsible for project financing, decision-making and management and makes also the decisions and procurement concerning modeling. The client is responsible for project preparations and implementation and receives the final design for their own archives and administration systems. The client can use outside technical experts as support for procurement and quality assurance (contract control). The client's user role to the model is typically a viewing user. Technical experts must have access to use full-scale tools (programs) for checking the model. Project manager appointed by service provider is responsible for modeling management. Project manager can delegate tasks regarding modeling management to model coordinator, but can´t delegate responsibilities regarding modeling, like compatibility of designs (discipline models). Project manager´s user role is viewing user.
Model coordinators ensure that different areas are consistent and compatible. Technical designers are responsible of their own modeling discipline and a model coordinator ensures the combined model is updated according to modeling plan document. To confirm compatibilities, responsibilities can be delegated in many different ways: to many actors, principal designer (road, railway, street) or project manager (who is ultimately responsible for everything). Model coordinator should have tools to consolidate and control models.
Infra model controller is client's controller and responsible for client’s quality assurance tasks.
Designers draw their own designs following design principals, design program and model plans of their own discipline. Designer follows quality assurance tasks. The designer uses needed tools to make and modify the model of their own discipline and applicable tools for controlling the combined model.
4.2
Cooperation and data exchange between actors
The modeling plan document describes cooperation between actors from modeling point of view. Process shall be interwoven with other project work as smoothly as possible.
4.3
Schedule
Schedule of modeling follow the schedule of design, where the modeling tasks are added. When scheduling a model for a project, the attention should be drawn especially to following matters:
• creation of initial data models and delivery well in advance
• preparation of visualization model in such a way it supports communication and meetings in the project
• division of project in a way, that it supports modeling and utilization of model
5
MODEL DESCRIPTION DOCUMENT AND LIST OF CONTENTS
Model description document describes central initial data per design area, purpose of model, content, coverage, modeling methods and level of accuracy as well as possible limits and deviations from general requirements. With help of the report other parts can interpret the general construction of model, naming practices and degree of readiness. Model description document is updated always when the model is released for other users.
Material division in model description document shall follow the principle, where design model and initial data model are separated and initial data model only consist of data of existing conditions.
Out of initial data and model is prepared a listing; model content list with an equivalent structure as an infra model report. The document shows the purpose of files, possible limitations as well as if needed, mistakes in description in comparison with theoretical geometry model. An inspection of documents can be made with help of the table (mark the particular row in the table) before forward delivery to other parties or being generated in to combined model.
Table 1. Example on contents of model description in railway plan.
0 General 3 Railway model
3C Constructions and systems
1 Raw material 3C1 Traffic lanes
1A Terrain model 3C1.1 Railway
1B Ground model 3C1.1.1-1 Railway constructions
1B1 Geotechnical soundings 3C1.1.1-2 Drainage
1C Constructions and systems 3C1.1.4-7 Equipment
1D Map and GIS 3C1.1.9 Service roads
1E Other data 3C1.1.10 Crossing
3C1.1.11 Existing constructions
2 Initial data 3C1.2 Road network
2A Terrain model 3C2 Foundation
2B Ground model 3C2.1 Preloading
2B1 Rock face 3C2.2 Surcharge loading
2B2 Soil type surface.
Peat, lower surface 3C2.3 Replacement of soil
2B3 Soil type surface. Clay, lower surface
3C2.4 Work-time abutment wall 2B4 Soil type surface.
Loam, lower surface
3C2.5 Pile slab
2C Constructions and systems 3C2.6 Loading berm
2D Map and GIS 3C3 Bridges
2E Other data 3C3.1 New bridges
3C3.2 Existing bridges
Model description document is more specifically described in part 2 in this set of instruction.
6
QUANTITY AND COST MANAGEMENT
Quantity and cost management is described in part 8 in this instruction document, Quantity and cost estimates.
How to link models to cost management is at this stage technically unsolved. Nowadays it’s essential to keep cost effects up-to-date in the design phase. Modeling benefits are multiplied, if the model can be linked to other functions as production control and cost management. At time of writing, there aren´t any established ways to deal with model-based quantity and cost management or for instance connect project and construction part calculation systems totally into model-based design systems.
7
QUALITY ASSURANCE
The client receives and accepts the model (models) produced in the project. The client has to ensure, that resources, knowledge and methods needed for this are sufficient. Quality assurance is mainly based on service provider’s inspection of produced models and it´s documentation. In addition the client can implement a separate quality assurance procedure.
Quality assurance is described in part 8
8
UTILIZATION PRINCIPALS OF MODEL IN DIFFERENT PROJECT PHASES
Modeling is used differently in different design phases. In the early phases the central factors are for example to find out the technical implementation, reliable definition of investment and maintenance costs as well as confirm acceptability of design. Central element in modeling is the combined model, which supports the implementation of solutions. The combined model is a virtual portrayal of all discipline models. Virtual model can function as a support to confirm the acceptability of design. Work flow of utilization of virtual model in design phase.
Picture 2. Use of modeling as a controlling tool and support in interaction.
Utilizing model in construction phase is portrayed in following work flow. Design is made to varying extent, for instance depending on procurement model. In principle, the designer is however always also involved in the construction phase. Construction phase has produced model-based designs from different disciplines and produced combined-models of them. From this entity is produce data for the needs of construction including machine control and on site measurements., As construction progresses, specified initial data as well as changes to design solutions at work site are delivered to designer, who up-dates the designs and the combined model.
An administrator has to be appointed before start of construction phase. Most naturally it is the designer. Model coordinator at site is responsible for producing the model for construction.
Picture 3. Utilizing models in construction phase is portrayed in following work flow. The role of model coordinator and responsibility limitations should be defined before start of construction project. Subject significance depends on project procurement model: in the so called integrated implementation models the significance decreases (picture doesn´t take side on procurement model; model-based design may have been made separately before construction phase or it can be made as part of procurement within the frameworks of a traditional contract or an “alliance type”).
Picture 4. Utilization of infra model in operation and maintenance phase.
