CI-3 Industry Foundation Classes for GIS (IFG)

There is a significant overlap between the AEC world and the GIS world. Buildings are constructed facilities that are placed within the world. Satisfaction of the scope of the project provides sufficient information from stored GIS data to enable the various design requirements of a building to proceed.

Business needs:

There is a significant overlap between the AEC world and the GIS world. Buildings are constructed facilities that are placed within the world. Satisfaction of the scope of the project provides sufficient information from stored GIS data to enable the various design requirements of a building to proceed. When the building has been designed, it can undergo regulatory checks. These can include conventional prescriptive and/or performance based building regulation checks (similar to those supported by the present IFC Code Checking View and implemented by the Singapore Building and Construction Authority). Additional regulatory checks can be undertaken at the interface between AEC/FM and GIS information and may include such aspects as zoning requirements, access and delivery provision, connection to utility services, fire safety provision, environment, pollution and sustainability provision, buildability, natural risk factors (flood, earthquake, subsidence etc.) and more. Satisfactory regulation checking enables the building to be completed. Once this has been achieved, completion data about the building can be provided back to the central property and building registry. Both AEC and GIS share the concept of lifecycle based information provision and will have similar approaches to portfolio and capital project development, design processes, costing and cost management, asset management, maintenance and other factors. AEC and GIS share an interest in systems development for purposes of distribution systems. Whilst in GIS, these are generally utility systems within regional infrastructure as opposed to the local distribution mechanisms applied in AEC, the approaches for system definition are likely to be remarkably similar. Features and benefits in summary: GIS interests provide to IFC significant potential for: global location through map information provision regional information relevant to building planning and provision utility information relevant to the services within a building risk information from nearby geographical features AEC provides to GIS the facility to be able to see a building and component entities as real objects and not just as illustrations pasted onto a map. In the long term, this can be beneficial in providing real building data for security and emergency services.

Solution:

IFC-GIS models or mapping of entities to IFC models will extend through multiple schema within the IFC model at all levels of the IFC model architecture. It is anticipated that there will be substantial requirements for the development of property sets.

Scope of work:

In Scope:

To provide GIS information through IFC by leveraging developments that have occurred within IAI (for the AEC community) and ISO TC211 (for the GIS community). define the interface between the AEC world and the GIS world and to develop strategies to improve interoperability and collaboration. define model development and/or mapping approaches that build upon GIS developments within ISO TC211. Development of the project will focus on support on making the zoning plan and building plan submission process more efficient. Key to this is the integration of GIS information in a central building and property registry with AEC/FM information about the individual buildings that are registered. By doing this, the following scenario can be supported as in the scope (see diagram).

For a building that is to be developed, information is taken from the registry to provide information about: Location map data Property data Utility services Demographics Zoning Risk factors An objective of the project will be to provide a demonstration of the concept of using the Industry Foundation Classes (IFC) model as the specification for the exchange of limited but meaningful information between GIS and AEC CAD systems and vice versa. The aim is to use entities that are already established within the Coordination and Code Checking views of IFC 2x so as to be able to reuse insofar as possible the tools, techniques and capabilities already developed by vendors at the AEC side of the demonstration. Demonstration scope for GIS -> AEC The scope for the exchange of information from GIS to AEC shall be the provision of: semantic identification of a 'site'; the geometry of a site in the form of a simple digital terrain model; specification of a site boundary; provision of additional properties within property sets as deemed necessary. Demonstration scope for AEC -> GIS The scope for the exchange of information from AEC to GIS shall be the provision of: semantic identification of a building and the building elements that are relevant for representation within GIS including, amongst others, building, wall, window, door, opening; primary elements of the building spatial structure including building storey and individual space; geometry of the building, building elements and spatial structure elements concerned; provision of additional properties within property sets as deemed necessary.

Out-of scope:

All aspects of GIS and AEC/FM systems that do not directly support the integration of GIS and AEC/FM information so as to provide an integrated repository from within which planning, zoning and building regulatory checks can be undertaken are deemed to be out of scope of the project. Within the GIS context, this is considered to include the following topics: The development of capabilities for detailed topographical maps. The development of water resource/hydographic model capabilities Analysis of performance of utility services Detailed road modeling that enables road design including road contouring, intersection planning, verge/median arrangement, lane allocation, pavement and sidewalk layout. Transport and communication planning except where the provision of transportation or communication facilities may be deemed to have a direct effect on planning, design or provision of a constructed facility at a place. Planning for local authority service provision other than as may be directly relevant to regulatory checking Bridge design (subject to separate IAI project with which an association will be established) Landscape design and layout Natural resource management Long term land use planning

Project schedule

Project start month/year: October 2003 Targeted completion month/year: October 2004 Process model: March 2004 Domain model: July 2004 Pre integration: July 2004 Integration: October 2004 Test data: October 2004

Project team: Project leader Chapter Roles Contact email Øivind Rooth NO G rooth@be.no Alternate project leader Wenche Stinessen NO G stinessen@be.no Technical leader Chapter Roles Contact email Jeffrey Wix UK I MSG jeffrey.wix@jwix.co.uk Alternate technical leader Lars Bjorkhaug NO T lbj@byggforsk.no Participants Chapter Roles Contact email Lars Bjorkhaug NO T lbj@byggforsk.no Morten Borrebekk NO S Morten-borrebekk@statkart.no Lars Christensen NO I lars.c.christensen@selvaag.no Francois Grobler NA G Francois.Grobler@erdc.usace.army.mil David Horner NA G david.h.horner@erdc.usace.army.mil Andreas Kohlhaas GS S akohlhaas@graphisoft.de Thomas Liebich GS I MSG tl@aec3.de Nick Nisbet UK I nick.nisbet@jwix.co.uk Jorulv Rangnes NO S jorulv.rangnes@epmtech.jotne.com Øivind Rooth NO G rooth@be.no Wenche Stinessen NO G stinessen@be.no Jeffrey Wix UK I MSG jeffrey.wix@jwix.co.uk

Supporting Activities

ISO TC 211 Form of Support: Resource persons from the ISO TC211 Secretariat in Norway will give their input through the Norwegian Reference Committee on Building Standards, which is chaired by the IFG Principal, Øivind Rooth.

Project addresses

Project web site: http://www.iai.no/ifg/index.html Project FTP site: Project email:

Remarks