10 1 1 195 2934

IAI Project ST-5 Structural Timber Model Part I Overview
by Prof. Dr.-Ing. Peter Osterrieder, Dipl.-Ing. Stefan Richter Chair for Structural Analysis Brandenburg Technical University Cottbus, Germany dth@statik.tu-cottbus.de
document rev.: 1.rc1
document status: release candidate
02 July 2004
IAI Project ST-5 Structural Timber Model Part I: Overview Table of Contents
Table of Contents
1 Abstract ...................................................................................................................4
Document history.....................................................................................................................4 Abbreviations...........................................................................................................................5
2 Introduction ............................................................................................................6 2.1 Motivation for product modeling.....................................................................6 2.2 Existing product models ..................................................................................7
2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 STEP............................................................................................................................7 IFC...............................................................................................................................8 DtH ..............................................................................................................................8 Product model developments in neighboring industries ..............................................9 Data models for manufacturing of structural timber components .............................11
2.3 Integration of DtH into IFC ...........................................................................12 2.4 The concept of partial models........................................................................14 3 Information Requirements ..................................................................................16 3.1 Scope of the Structural Timber Model...........................................................16
3.1.1 3.1.2 3.1.3 Scope by AEC sectors ...............................................................................................16 Scope by actors, disciplines.......................................................................................16 Scope by project stages..............................................................................................17
3.2 Vertical and horizontal information sharing, model evolution ......................17 3.3 Information requirements by actors, disciplines ............................................18
3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 3.3.7 3.3.8 3.3.9 3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 3.4.7 3.4.8 3.4.9 Architect ....................................................................................................................18 Structural engineer.....................................................................................................19 Design engineer, draftsman .......................................................................................20 Building services engineer (HVAC, electric equipment, plumbing) .........................21 Contractor, manufacturer...........................................................................................21 Building materials industry, supplier.........................................................................22 Project manager .........................................................................................................22 Client (building owner) .............................................................................................22 Building authorities ...................................................................................................23 Building construction process framework .................................................................23 Data exchange use case: From requirements management to design ........................24 Data exchange use case: Between designs.................................................................25 Data exchange use case: Manufacturers/ suppliers product information to design ...26 Data exchange use case: From design to construction planning................................27 Data exchange use case: Between project management, construction and deliveries28 Data exchange use case: General project management .............................................29 Data exchange use case: From design and construction to use and maintenance......30 Data exchange use case: Between use and maintenance ...........................................31
3.4 Information requirements by project stages...................................................23
IAI Project ST-5 Structural Timber Model Part I: Overview Table of Contents
4 DtH 2.0 Walkthrough...........................................................................................32 4.1 Basics .............................................................................................................32

4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.2.1 4.2.2 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5 4.4.1 4.4.2 4.4.3 4.4.4 4.4.5 4.4.6 4.5.1 4.5.2 4.5.3 4.5.4 4.6.1 4.6.2 4.6.3 4.6.4 4.6.5 File format .................................................................................................................32 Parameter tokens, units..............................................................................................32 Coordinate systems....................................................................................................33 Version control ..........................................................................................................33 External references and component catalogs.............................................................33 Standard ISO 1030321 headers ...............................................................................34 DtH headers ...............................................................................................................34 Generic classes ..........................................................................................................35 Groupings ..................................................................................................................35 Geometry ...................................................................................................................36 Grids ..........................................................................................................................37 Other defined data types ............................................................................................38 Building sections, floors ............................................................................................38 Building parts ............................................................................................................39 Openings....................................................................................................................40 Stairs..........................................................................................................................41 Foundations ...............................................................................................................41 Comparison to IFC ....................................................................................................41 Materials ....................................................................................................................42 Cross sections ............................................................................................................43 Structural analysis......................................................................................................48 Comparison to IFC ....................................................................................................54 Materials, cross sections ............................................................................................55 Members ....................................................................................................................55 Processing features ....................................................................................................58 Connections ...............................................................................................................65 Comparison to IFC ....................................................................................................70
4.2 General project data .......................................................................................34
4.3 Common classes.............................................................................................35
4.4 Architectural model .......................................................................................38
4.5 Structural analysis model ...............................................................................42
4.6 Structural detailing model..............................................................................55
4.7 Cost estimation, bid preparation, billing........................................................70 4.8 Gaps in DtH 2.0 .............................................................................................71
4.8.1 4.8.2 Missing building services model ...............................................................................71 Limited production model .........................................................................................71
5 Appendix ...............................................................................................................73 5.1 References......................................................................................................73 5.2 List of figures .................................................................................................74
IAI Project ST-5 Structural Timber Model Part I: Overview 1 Abstract
1 Abstract
This document covers the integration of a product model for timber buildings and timber structures into the Industry Foundation Classes of the International Alliance for Interoperability (IAI). It is based on the work of the IAI project group ST-5 and of the research project Innovative timber building systems through optimized fabrication and integrated planning methods; partial project 3: Product model DtH under project number 0330424. The DtH project is carried out by the Brandenburg Technical University Cottbus, Germany, Chair for Structural Analysis under guidance of the German Association for Wood Research (Deutsche Gesellschaft fr Holzforschung, DGfH) with funding by the German Federal Ministry of Education and Research between July 2003 and December 2004. Chapter 2 of this document outlines the business need for a product data model in the timber construction industry and introduces available data models. The integration of DtH into IFC is commented on, and the concept of partial product models that is underlying both of these standards is briefly defined. Chapter 3 describes the intended scope of the Structural Timber Model and determines the required information to be exchanged within timber construction projects. Chosen as the main basis for the Structural Timber Model, the current DtH standard is explained in chapter 4. All existing entities are introduced. (Refer to [5] for complete attribute definitions.) Shortcomings and differences to IFC are pointed out. The document will be complemented by Structural Timber Model Part II: Schema Reference and Part III: Implementation Guide.
Document history
rev 1.rc1 02 Jul 2004 numerous updates and edits in chapter 2 section 3.4 rewritten using material provided by FinnTimber-IFC subsection 2.2.5 added subsections 4.6.34.6.5 extended 06 Nov 2003 fig. 4-8, fig. 4-9 extended; fig. 4-20, fig. 4-21 added comparisons to PSS added in subsection 4.6.3 30 Sep 2003 subsection 2.2.4, fig. 2-3, fig. 2-5, fig. 4-8 added sections 3.4, 4.3.1, MEMBER_LTYP, CUTOUT_TIMBER clarified section 4.8 extended 03 Sep 2003 first draft
rev 1.3
rev 1.2
rev 1.1
IAI Project ST-5 Structural Timber Model Part I: Overview 1 Abstract
Abbreviations
AEC AVA architecture, engineering, and construction Ausschreibung, Vergabe und Abrechnung (bid preparation, placing of contracts, billing) CIMsteel Integration Standards Deutsches Institut fr Normung e.V., German institute for standardization Datentransfer im Holzbau (data transfer in timber construction) facility management heating, ventilation, air conditioning International Alliance for Interoperability Industry Foundation Class(es) International Organization for Standardization ISO Publicly Available Specification life cycle cost(ing), life cycle analysis laminated veneer lumber, an orthotropic engineered wood product used in beam-like applications oriented strand board, an orthotropic engineered wood product used in plate-like applications and stress skins Produktschnittstelle Stahlbau (product interface for steel construction) structural insulated panel, a sandwich made of OSB skins and foam core service live planning Standard for the Exchange of Product Model Data Standardleistungsbuch fr das Bauwesen (standard construction services manual for building construction; a German classification system used in bills of quantities) vertical nailed planks, also known as vertically laminated timber decks or board stacks
CAD/CAM computer aided design, computer aided manufacturing CIS DIN DtH FM HVAC IAI IFC ISO ISO PAS LCC/LCA LVL OSB PSS SIP SLP STEP STLB
VNP
IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction
2 Introduction
2.1 Motivation for product modeling
Rising labor costs, shortages of skilled workers, consolidation in the builder business, demand for higher product quality and for more resource saving production all these trends stimulate efforts in enhanced industrialized building production. More and larger components are prefabricated, and automation in builders' shops is increasing. Prefabrication and automation are actually vital for the timber construction sector to remain competitive with the concrete, masonry, and steel construction. On the other hand, flexible building designs with an increasing degree of installed building services are in demand. New construction methods and building systems emerge as a result. These developments pose new requirements on the planning process. The various planning stages have to be more tightly integrated, and the way all involved parties are planning and communicating has to improve in time and cost efficiency. This is especially important for timber construction: It involves a higher degree of detail in planning and a closer link between planning and manufacturing than masonry and concrete construction. It also features a broader mix of traditional and modern materials and technologies than structural steelwork. Currently available solutions for electronic data exchange are however unable to cover the needs of all parties in a construction project (fig. 2-1), and they are unable to ensure information sharing continuously during the complete project. Limitations of existing data exchange interfaces lead to project information being spread over disparate documents and files which are hard to keep synchronized during the project. Moreover, proprietary interfaces are in use that complicate implementation and defy long-term accessibility of data.
FIG.
2-1 DATA TRANSFER THROUGH

CONVENTIONAL INTERFACES
FIG.
2-2 INFORMATION SHARING VIA

A PRODUCT MODEL
Architect Engineer Work Prep. Machine A Bldg.Services Draftsman Machine B
Architect Engineer Work Prep.

Product Model
Bldg.Services Draftsman
Machine A
Machine B
Therefore, a new data model is required that combines information requirements of all actors involved in construction projects. Such a data model ultimately focuses on
the product (the building) instead of individual applications, which is why such a data model is called a product model. Some of the benefits of a product model become immediately clear from fig. 2-2: The number of interfaces necessary to connect all information endpoints decreases considerably. All endpoints are equally well connected. Redundancies and therefore sources for errors are minimized. Design changes are passed on faster, and conflicts can be detected and resolved in a timely manner. Moreover, product modeling recognizes building design and construction planning as multidisciplinary optimization tasks. The goal is a product that delivers maximum value to the owner within given limits of money, time, and other restrictions. A product model supports optimization by allowing views upon the project as a whole, as it combines information about all the different aspects that influence the optimum. A product model typically fulfills the following criteria: Context is provided. Just like we expect it from a decent technical drawing, electronically transmitted data shall have clear meaning and shall reflect the designers intent. Relationships between different project aspects must be expressed. System independency is maintained. System independency means more than computer platform independency. The way how project data are structured shall not be determined by a single tool, discipline, or process. Instead, the great diversity of processes and planning tools involved in construction projects must be taken into account in the first place. This leads necessarily to a focus on the product instead of a focus on an application. Information grows during the projects whole time span. To design is to learn and to solve problems, as is production planning. Previously generated information has to be reevaluated, supplemented, or rectified while the project is progressing. The data model carrying design information must support this iterative process. Successive planning processes reuse existing information and accumulate newly obtained information. Data formats shall be non-proprietary. Conformance shall be assessed. The methods of presenting information in electronic form shall be neutrally developed and openly published. Implementations shall be tested for conformance using formalized methods.
2.2 Existing product models

2.2.1 STEP
The ISO 10303 family of standards a.k.a. STEP [1] provides methods and models for product data representation and exchange for a wide range of industry sectors. STEP essentially consists of
IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction description methods, implementation methods, and conformance testing methodology, generic models (common resources),
specialized models (Application Protocols, which have been supplemented by Application Modules more recently). STEP documentation is distributed subject to charges by national standards institutes. As aid for implementations, there is a free STEP Class Library available from NIST as well as a variety of commercial software development tools and data management solutions for STEP.
2.2.2 IFC
After several product modeling projects within the ISO and STEP context, it became apparent that neither the ISO standardization process nor the initially monolithic approach taken by STEP Application Protocols are well suited to the requirements of the multi-disciplinary AEC/FM industries. This situation lead to development of the Industry Foundation Classes [2] as an industry standard (instead of a formal standard). The IFC addressed the problem of cross-disciplinary interoperation on its conceptual level in the first place. The IFC are layered in common resources, core, interoperability layer (interdisciplinary),
domain layer (special to disciplines). The IFC are based on the STEP low level and have adopted parts of the STEP mid level in the resource layer (STEP parts 41, 42, 43). The withdrawn STEP part 106 Building Construction Core Model was one of the major foundations of IFC development. The high level of first releases of IFC covered architecture, HVAC, FM, and cost estimating. Recent releases added basic structural engineering, further building services and FM elements. IFC documentation is freely distributed. Implementation support and certification is provided under the terms of IAI. Software toolboxes for STEP as well as dedicated toolboxes like EPM Technology EXPRESS/IFC toolbox, Eurostep IFC Toolbox, or QualiSTEP CSC are available. Abstraction layers like the SABLE APIs of the BLIS project are being developed.
2.2.3 DtH
DtH is a German product model specification that was developed by the Brandenburg Technical University Cottbus and several software vendors for the DGfH, a nonprofit research organization of the German forest and wood industry and timber construction industry. The DtH specification has its roots in PSS, the German product model industry standard for steel construction [3]. Both PSS and DtH are based on STEP. DtH is targeted to timber engineering construction, carpentry, and prefabricated residential buildings. It is oriented towards the viewpoint and language of engineers, architects, and builders.
The first release version 1.05 (02.1996) contained three partial models: Structural design model, detailing design model, and a simple building costs model [4]. Version 2.0 (12.1999) added an architectural model, enhanced the detailing model, and addressed ISO 10303 conformance issues [5]. DtH uses feature based parametric descriptions of building elements in order to cover information requirements of both engineering and fabrication. Low redundancy on the level of the model concept is maintained with the goal of low data redundancy in populated DtH models. Another characteristic of DtH is its low complexity; no inheritance relationships, inverse attributes, or local rules are used. DtH documentation is freely available. Implementation support was made available only during the time spans of the version 1.0 and 2.0 research projects. DtH implementers can utilize STEP development tools since DtH 2.0.
2.2.4 Product model developments in neighboring industries

Steel construction industry Within the steel construction industry, the CIMsteel Logical Product Model (CIS/2 LPM, maintained by Steel Construction Institute, UK) and the German DSTV PSS [3] are in use. Newer incarnations of LPM do not only cover information requirements of analysis, design, and manufacturing of structural steel frames but also to some extent more general processes of the construction industry such as scheduling and costing. Capabilities of LPM that are not yet available in IFC include dynamic analysis, and dimensions with tolerances. The possibility of mapping between LPM and IFC is currently investigated by the American Institute of Steel Construction. PSS is a model with similar scope but lesser capability than LPM. PSS is thereby less complex and easier to implement. PSS was the primary source for the IAI ST-4 project, yielding the Structural Analysis domain that is already part of IFC 2x Edition 2, plus several extensions in lower IFC levels and the Structural Elements domain. The work done in the ST-4 project provides an important basis for the IAI ST-5 extensions derived from DtH. Proprietary AEC product models Several architectural CAD and steel CAD application suites are based upon proprietary product models, also called building information models. These models are the result of customer demand for tight integration of CAD with other AEC applications like quantity take-off, analysis software, and fabrication software. Unlike standardized product models, proprietary models are limited to single-vendor solutions that are able to integrate only business processes within a single organization, e.g. within a design office or a construction company.
FIG.
1973
ICAM program
1980 SET Standard d'Echange

AFNOR
et de Transfert
1982 XBF VDA-PS CADLIB VDA-FS Freiformflchen-Schnittstelle
[9], [10], [11], [12]
1984
IGES 1.0 Initial Graphics Exchange Specification PDES

Product Data Exchange Specification
U.S.AF
1986
DIN
IGES 3.0
1987 CALS
initial proposed standard
CIMsteel
1988
STEP
1991 ATLAS project COMBI project

parts 1, 11, 21 etc pt.201 - 2D drawing pt.203 - 3D drawing
1993
1994 CIS/1.0
CIMsteel Integration Standards
Esprit
Standard for the Exchange of Product Model Data initial ISO 10303 (STEP) release:
Computer Integrated Manufacturing for Constructional Steelwork
DSTV NC protocol DSTV uniform material designations DSTV interface between structural analysis and CAD
Ein Produktmodell fr den Stahlbau (Haller)
1995
IFC
Industry Foundation Classes IFC 1.0
1996
PSS
Produktschnittstelle Stahlbau IFC 1.5.1 IFC 2.0 ST-1 IFC 2x ST-4 ifcXML PSS 04.2000
1997 CIS/1 finished CIS/2 started

Eureka
DtH 1.05 Datentransfer im Holzbau

DtH 2.0
2-3 TIMETABLE OF PRODUCT MODEL DEVELOPMENTS1
1998
ISO 10303-225 IS published
circa 30 APs in the works, e.g. pt.225 - building elem. pt.228 - HVAC pt.230 - steel frames pt.106 - BCCM (bldg. constr. core model) interoperability models in the works
1999
2000
2001
2002 CIS/2.1 IFC 2x2 ST-5

ISO SCI IAI DSTV DGfH
2003
IGES 6.0
2004
ANSI
10
11
Furniture industry The European funSTEP project lead to an Application Protocol for the furniture industry, which is currently prepared to become ISO 10303236. Numerous high- and low-level parts of ISO 10303 are reused by funSTEP. Main interest of the funSTEP project is the exchange of product data between furniture manufacturers, furniture retailers, and decoration studios. In scope of funSTEP are: product definition, product catalogues, simple furniture and modular furniture, geometry, dimensions, parameterization, configuration, finishing, accessories, price,
interior decoration, room space definition and representation, furniture placement. While an intersection of scopes of IFC and funSTEP exists with respect to furniture as facilities objects, there is no intersection with respect to manufacturing of woodbased products. Whereas the ST5 IFC extensions consider machining and jointing of engineered wood materials, there are no provisions in funSTEP for integration of detailed design and manufacturing.
2.2.5 Data models for manufacturing of structural timber components

European and North American timber construction is characterized by rising degrees of prefabrication using numerically controlled and semi-automatic fabrication equipment. Consequently, a tight integration of workshop design and manufacturing is practiced. Two examples of data models that are widely deployed in such integration solutions are given below. A unilateral interest of the CAD software industry exists to replace the various data models by a unified product data model such as DtH or IFC. CAM integrators however have so far shown little to no interest in non-proprietary solutions. The North American initiative WINStep (Wood Industry Standard for the Exchange of Product data), comprised of members of the CAD software industry as well as of machinery retailers, is aiming to resolve this situation by means of a common data protocol for CAD/CAM integration in woodworking. The protocol is to cover product data, process data, and technology data; a specification is however not yet available. Hundegger data interface between CAD and NC joinery machines The interface defined by Hans Hundegger Maschinenbau GmbH is used for integration solutions between timber detailing CAD and woodworking machines for processing of beams. The interface uses line-oriented tabulated text files, i.e. with fixed positions of characters. The files contain essentially a short header with designation of the project, a list of all beam types to manufacture. Each beam type is described by amount of beams to manufacture, material grade, parameterized raw geometry, and destination with respect to packeting and installation.
IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction Associated with each beam type are processing features. Each feature is identified as a machining macro; in other words, the type of feature is determined from the viewpoint of functionality of the machine, not from the viewpoint of feature geometry.
12
Features are parametrically defined; again the meaning of parameters depends solely on the chosen machining macro. However the parameters essentially describe the features shape, not the exact path and velocities of the tools. The set of available machining macros depends on machine type and control firmware revision. More than 80 macros may be available. In essence, not only building element data but also knowledge about machine functions and their optimal use is required in order to create the files used by the Hundegger data interface; but lowlevel NC code is not transmitted. Weinmann data interface between CAD and timber framing machines The interface developed by Weinmann Holzbausystemtechnik GmbH, SEMA GmbH, and GranIT GmbH is used for integration solutions between CAD and CAM for production of building components in light timber frame construction style. The interface uses line-oriented text files with comma separated fields. Each file describes one assembly. The files contain essentially a header with overall parameters of the assembly, a list of all framing members, including their size, placement, and applied machining processes,
a list of all sheathing panels with their material, shape, placement, machining processes, and nail rows. The interface was originally based on a 2D coordinate system with layer information. A third coordinate was recently added to accommodate more complex building styles. Virtually no machine specific information is transmitted by this interface. Although keywords for sawing, milling, and drilling exist, the actual tool is selected afterwards by the machines firmware. Like in the Hundegger data interface, processing parameters describe the shape to create, not actual tool paths.
2.3 Integration of DtH into IFC

Benefits DtH and IFC are both STEP based and share the concept of partial models (see section 2.4). The current IFC specification features extensive support for architectural design, building services, project management, and facility management while structural engineering tasks have not been covered until recently. DtH on the other hand explicitly supports structural design for timber structures while other areas are less comprehensively defined or even missing. It is therefore an obvious idea to merge DtH and IFC. The benefit for existing DtH implementations of this transition is to gain connectivity to major architectural CAD applications and to building services design and to
13
overcome the limitation to the national AEC software market. The benefit for IFC is the improved versatility of IFC implementations. The fact that DtH is already implemented and used in practice is an important advantage for the new Structural Timber Model since the process of standard definition, documentation, and testing is considerably accelerated.
FIG.
2-4 SCOPE OF CURRENT IFC AND DTH SPECIFICATIONS

demolition
preliminary design
conversion
conservation
design, struct. calculation building lifecycle detailing
prefabrication
erection
Dt
Modeling strategy The ST-5 model extensions are designed according to following rules: Avoid deep interventions into the IFC architecture in order to allow for quick integration of the proposal. Do not duplicate functionality that is already available in IFC or will be made available by ongoing projects. Aim at compatibility to the other structural domains: Steel construction, reinforced concrete, and precast concrete domain. Maintain independence of national building codes. Do not delete functionality of the DtH model (unless it is agreed upon obsolescence of a functionality).
Several necessary extensions are already provided by the IAI project ST-4 Structural Analysis Model and Steel Construction2 and the IAI project ST-3 Precast Concrete Constructionsee fig. 2-5. These provisions will enable the ST-5 project to concentrate the majority of its additions into the domain layer in a mostly self-contained form. Limitations of DtH/IFC harmonization For several reasons among them naming conventions IFC files using the future Timber Construction domain will not be compatible with DtH files.
The ST-4 project is currently continued by a follow-up project that adds IFC extensions for detailing of steel members and steel connections.
2. 0
IF C
use 2x 2
14
However, while files are incompatible, the IFC model including the future Timber Construction domain will be a superset of the complete DtH model. It should thus be possible to convert DtH files into IFC files.
FIG.
2-5 EXTENSIONS TO IFC 2X BY THE ST-3, ST-4, AND ST-5 PROJECTS3

Architecture Domain Construction Mgmt Domain Precast Concrete Construction Domain Structural Analysis Domain Steel Construction Domain Timber Construction Domain
HVAC Domain
Electrical Domain
FM Domain
Domain Layer
Shared Bldg Services Elements Shared Spatial Elements Shared Management Elements Shared Facilities Elements Shared Building Elements Shared Bldg Elements Extension
Additions
Interoperability Layer
IFC 2x platform ISO/PAS 16739 non-platform part: next candidates out of platform Control Extension Process Product Exten- Extension sion Kernel Product Exten. Extn.
Additions
Core Layer
Material Resource Geometry Resource
IFC 2x ST-3 ST-4 ST-5

project
... ... ... ...
project
harmonization with PSS, CIS/2
project
harmonization with DtH
harmonization with BEC
Material Property Resource
Geometric Model Resource
Profile Resource
Measure Resource
Representation Resource
Topology Resource
Resource Layer
Additions Geometric
Model Extension
Profile Extension Resource
Measure Extension Resource
Representation Extension
Topology Extension Resource
Profile Property Resource
Structural Load Resource
Additions
2.4 The concept of partial models

For reasons of general applicability in the international AEC/FM business, product models for building construction consist of partial models (see [8], section 2) . In the following chapters, the terms architectural model, structural analysis model, structural detailing model, production model,
See [13] and [14]. Most of the ST-3 and ST-4 proposals were integrated into IFC 2x2. A new Structural Elements Domain schema subsumes the Steel and PC Construction Domain schemas. The Timber Construction Domain is targeted to become part of the Structural Elements Domain.
15
physical building model will be used. A complete product model for building construction in general and for timber construction in particular contains of course further partial models, e.g. for HVAC design, for cost estimation, or for project control. The architectural model describes geometrical, functional, and aesthetic aspects of the building. It contains representations of tangible elements like floors, walls, columns, and representations of intangible elements such as room functions or escape routes. The structural analysis model idealizes the load carrying system of a building together with actions. It contains mechanical abstractions as well as design code dependent means for verification of structural safety, serviceability, and durability. The structural detailing model provides information about the building parts: Materials, shapes, treatments, connections and so forth. The production model is a specification of the structural detailing model. It contains information related to prefabrication, transport, and erection. The physical building model contains all tangible (physical) elements of the building structure and thus contains parts of the architectural model and the structural detailing model. Elements of the structural analysis model are associated to parts of the physical building model. It is a three-dimensional virtual building including all structural and non-structural components. As such it constitutes the core of the product model. All other partial models are related to or directly derived from it. Partial models may share objects. Optimal product model formulation aims at least possible redundancy with respect to the meta modelin order to avoid ambiguitiesand with respect to the instantiated modelin order to avoid sources of errors during product design changes.
IAI Project ST-5 Structural Timber Model Part I: Overview 3 Information Requirements
16
3 Information Requirements
3.1 Scope of the Structural Timber Model
3.1.1 Scope by AEC sectors
In scope: building sector, especially: prefabricated house construction, structural timber engineering,
carpentry. Partially in scope: faade construction, finishing trades (fixtures and equipment), bridge engineering, scaffolding and formwork, building materials industry.
3.1.2 Scope by actors, disciplines4

In scope: architect, structural engineer, design engineer/ draftsman, contractor,
building materials supplier. Partially in scope: client (building owner), project manager, building authorities, building services engineer (HVAC, electric equipment, plumbing), building services (sub-)contractor.
The concepts of actors, roles, and disciplines are freely intermixed in this document. One actor may take over several roles as well as several actors may fulfill one and the same role.
17
3.1.3 Scope by project stages

The main application of the structural timber model are new building projects. The structural timber model is furthermore relevant in reconstruction & rehabilitation and, to a certain degree, to demolition projects. Within a project, these stages are primarily in scope of the structural timber model: structural design, structural detailing, workshop drawing, production planning.
In scope are furthermore pre-fabrication, site construction, as-built documentation.
Partially in scope is preliminary design.
3.2 Vertical and horizontal information sharing, model evolution

Vertical information sharing occurs between actors with different roles in a project. An example is the shared use of geometry information by a CAD program and a finite element analysis program. Horizontal information sharing occurs between actors who fulfill the same role, e.g. the shared use of geometry and feature information between two detailing CAD programs. An intermediary case is information sharing between actors with similar roles, e.g. shared use of building member data between an architectural CAD application and a detailing CAD program. While the latter maintains processing details as features, the architectural CAD program will certainly only provide a geometry-oriented view on these details. Evolution: The amount of information increases during the various design and realization stages: Superstructures are subdivided into members. Details are added to members. Qualitatively new information is added, additional partial models are developed. Relations between partial models are established.
IAI Project ST-5 Structural Timber Model Part I: Overview 3 Information Requirements Designs are optimized, inappropriate decisions are corrected, designs are readjusted to changed boundary conditions (e.g. client requirements).
18
Hence the model structure has to support the development of the specific from the generic. It has to provide shared elements of separate partial models and links between partial models. Version information has to be stored to reflect the iterative nature of the planning process. Information provided by the structural timber model serves (but is not limited to) the derivation of the load carrying structure from the architectural model, the structural analysis of the timber structure, working design of timber members after analysis, connection design together with connection analysis, production planning based on working design and connection design.
3.3 Information requirements by actors, disciplines

3.3.1 Architect
receives various functional, technical, and non-technical requirements from building client and from authorities, receives topological situation from surveyor; creates spatial, functional, and formal model of the building; generates parts of the structural system of the building; checks final structural design from engineers or contractor for functional, formal, and other aspects; checks building services model for inconsistencies.
The level of detail of the architect's planning varies to great extend depending on the type of building, contractual constellations, and local practice. The architect generally defines superstructures like walls and decks and chooses construction type and material. The job of structural design and structural detailing of the final building structure is left to the structural engineer (consulting engineer) or/ and the technical office of the contractor. The final structural model as submitted from the engineer or contractor to the architect for approval does not necessarily need to provide complete explicit
19
geometry of secondary components like bolts, nails, fasteners etc., except if aesthetic aspects are of concern.5 It is important that visual representation data (geometry, annotations) that were generated by specific CAD tools for timber structures is also accessible by CAD programs that implemented only the IFC CAD view but not the structural timber domain. If components are referenced (not copied) from a library or electronic catalog, the library has to be accessible by all relevant project participants. The availability of the library has to be ensured for the whole lifetime of the building model data repository which, as mentioned, may by far outlast the actual project duration.
3.3.2 Structural engineer

starts with the architectural model; considers geotechnical boundary conditions; creates structural model of the building; decides on structural materials and principles of structural details; checks structural detailing model for aspects of structural safety, serviceability, and durability.
Main task of the structural engineer is to create a structural analysis model on the basis of the architectural model. Aside from 3D geometry, various contextual information is required, e.g. identification of floor of a residential building, structural/ non-structural wall, and fire resistance requirements. If this information is provided as formalized data, partial automation of structural modeling would be facilitated. The structural analysis model consists of several sub-models that are more or less coupled. All building structures are basically 3D structures but can and will often be simplified as 2D models.6 Structural components of timber structures are generally modeled with linear, 2-node beam elements. Nodes may represent bearings or connections, which often allow for local elastic deformation. Some structural analysis methods for structural timber design use mechanical systems on a higher level than beam structures. An example is the simplified design of shear walls provided by several design codes where certain practical assumptions about distribution of internal forces and deformations are made.
Examples: It may be desirable for exposed glulam structures with concealed connectors to show explicit geometry of dowel faces considering that joints substantially contribute to the visual appearance of a timber structure. On the other hand, conventional beam hangers in a clad floor deck could be presented by abstract symbols.
A timber structure is actually a 4D problem since the time dimension is also important. Static calculations reduce the 4th dimension to some relevant discrete points, like t = 0 (tinst) and t (tfin).
20
Materials used for timber structures are in general anisotropic.7 Since the structural behavior of wood-based materials depend on time and moisture content, contextual information from the architectural model is important for generation of the structural analysis model. Moreover, timber material properties depend on profile properties.8 If material properties are stored for horizontal data sharing, the associated design code should be referenced because it provides necessary context for these values. It should also be explicitly noted whether mechanical properties are given as factored resistances (limit state design method, using partial safety factors) or as allowable values (allowable stress design method).9 If the product model was limited to factored resistances only, its adoption could be delayed for a very long time until all design codes and vendor catalogs are converted from allowable stress design method to limit state design method. It is even conceivable that building materials and accessories that are not standardized in design codes continue to use allowable stresses or allowable forces.
3.3.3 Design engineer, draftsman

receives architectural model and structural analysis model; finishes the structural details of the building; checks building services model for collisions.
The structural detailing model is derived partly from the architectural model and from the structural analysis model. The mapping from structural load carrying members to structural analysis elements is, in general, an M : N mapping. E.g. several beam elements in the structural analysis may represent one solid timber beam, or one beam element in the structural analysis may represent a series of parallel deck joists. The mapping from the architectural model to the structural detailing model is generally an M : N mapping as well, but in most cases it is a simple 1 : N mapping. E.g. a wall consists of several studs, panels, fasteners, etc.. A similar mapping exists between architectural and structural analysis model. These mappings must be expressed by and stored as relationship entities, thus easing eventual changes during the planning process, e.g. if the building owner requests changes of the space program. However, while the initial generation of these relationship entities is rather simple, the maintenance of these relations can be difficult. For instance, if an architectural CAD program splits a wall into two or if it
7 8
As of yet, IFC contain only isotropic material descriptions.
Examples: The bending strength of solid timber according to Eurocode 5 increases below a certain reference depth in bending. The capacity of a glued laminated timber beam depends not only on its dimensions but also on the so-called lamination layup. Laminations of different grades can be arranged throughout the depth of a glulam member.
9
This will not only facilitate horizontal data sharing during the project execution but it will also support future assessment of applied materials long after erection when vendor-provided data sheets or then withdrawn design codes are not available anymore.
21
removes a wall, either the architectural CAD program has to rebuild a valid mapping, or the engineering CAD/CAE applications have to detect and to react on outdated relations. While the coupling between partial models and the resolution of conflicts due to concurrent planning processes is still a matter of scientific research, IFC already provide the means (but not the policy) for inter-model coupling. Policy, like functionality for semi-automated conflict resolution, is and will remain out of scope of IFC.
3.3.4 Building services engineer (HVAC, electric equipment, plumbing)

receives architectural model; considers details of the structural model where necessary; creates energetic model of the building (part of this task is sometimes carried out by the architect or structural engineer); creates models of services networks; checks architectural/ structural model for collisions and incompatibilities.
The physical building model must provide explicit geometrical information wherever installation equipment shall be routed. For instance, the location and shape of studs within timber walls must be specified if there is no extra installation layer in a multilayered wall. The explicit shape of components like metal fasteners is not required in any case. However, information about minimal distances of openings from joints and from member edges is necessary for proper layout of services networks. This information is at present not explicitly given to the building services engineer, which often results in time-consuming and error-prone iteration during the planning process (repeated exchange and stepwise revision of plans). Furthermore HVAC and plumbing design requires information provided by the structural engineer whether members are part of the load carrying system. To derive the energetic building model, contextual information (like classification in outer and inner walls and decks) and functional data of building spaces are to be acquired, as well as thermal and hygroscopic properties of materials or compounds.
3.3.5 Contractor, manufacturer

acts on the basis of architectural, structural, and building services model and checks these models for compatibility, feasibility, economy; creates the production model (manufacturing, transport, and erection model).
The production model contains production information like construction schedules and parts lists.
22
Modern timber construction features a high degree of prefabrication. For improved competitiveness, demand for higher automation of the production of timber building parts conflicts with demand for highest possible flexibility of the buildings design. To resolve this conflict, the design process has to be continuous and consistent from early design until production. Fast, easy, and accurate deduction of manufacturing information from the structural detailing model is necessary. Hence feature based parametric models for timber members and joints are required. Models that solely provide explicit geometry data are not sufficient for generation of machine control data. For instance holes, notches, tenons, fasteners etc. have to be formulated as features of a timber member in order to prepare fabrication with numerically controlled joinery machines.
3.3.6 Building materials industry, supplier

provides technical product information to architect, engineer, contractor. External electronic catalogs or libraries of materials and accessories are of enormous importance for the structural timber model. Such catalogs and libraries need to be maintained by the building materials industry. Submits bids to contractor or client; receives material order from contractor or client. Especially in the North American and Scandinavian markets, more and more building components are prefabricated already by the supplier instead of by the builder. The supplier needs therefore access to design data. However the design data handed out to the supplier are often taken out of their original context in a project (relating to a building) and put into a new context relating to a delivery order.
3.3.7 Project manager

checks and approves documentation from architect and engineer; prepares bill of quantities, calls for bids, awards contracts; creates project schedules;
checks and approves technical and non-technical documentation from contractor. The building model submitted to the project coordinator for approval, cost control, and scheduling of production must not necessarily provide complete explicit geometry of secondary components, e.g. fasteners.
3.3.8 Client (building owner)

specifies functional and aesthetic requirements and sets cost frame; authorizes technical and non-technical documentation from architect, engineer, contractor; receives complete technical documentation from architect, engineer, and contractor at the end of the project.
23
In early project stages the architect typically visualizes his idea of the building by means of drawings and computer or true-scale models. At this stage specific timber construction related information is generally not required, except for sophisticated, exposed timber structures where a detailed rendering of typical details may be desirable. At the end of the project the client requires handover of complete documentation, asbuilt documentation included. This information, stored in a product model, will allow the client to access any data required for renovation, extension, conversion, sale or wrecking of the building.
3.3.9 Building authorities

check submitted building application for technical, formal and legal requirements with respect to urban development, fire protection, energy consumption, sound insulation, etc.; inspect construction site;
finally check the finished building with respect to conformance to approved specifications. The required level of detail depends on national and local regulations and on type of the building, as does the required form of physical representation of the documentation. Electronic data exchange with authorities will become more common in the future.
3.4 Information requirements by project stages

The content of this section was kindly provided by the FinnTimber-IFC project.
3.4.1 Building construction process framework

The following main project stages are identified: Requirements definition, building design, construction planning, construction, use and maintenance. Important milestones of a construction project are 1 2 project decision, design decision,
3 building permit decision, 4 construction decision,
5 building commissioning decision. Throughout and after the construction project, the following tasks are carried out: Project management, authority control, requirements management, design coordi-
24
nation, architectural/ structural/ HVAC/ other design, construction, component production, material supply, use, maintenance. Subsequent sections analyze data exchange use cases during individual project stages and tasks.
3.4.2 Data exchange use case: From requirements management to design

FIG.
3-1 DATA EXCHANGE FROM REQUIREMENTS MANAGEMENT TO DESIGN

Requirements definition Building design
Marketing Project planning Design control
Construction planning
4
Construction
Construction control Construction supervision
Use and Maintenance
Project management Authority control
Feasibility study
Project management
Authority control of design
Authority control of construction
Requirements management Design coordination Architectural design Structural design HVAC design Other design
Requirements management
Requirements definition
Design coordination
Construction supervision / DC
Preliminary design
Detailed design
Construction supervision / ARCH
Preliminary design
Detailed design
Construction supervision / STRUCT
Preliminary design
Detailed design
Construction supervision / HVAC
Preliminary design
LCC / LCA / SLP
Detailed design
Construction supervision / Other
Construction Component production Material supply Use
Tendering
Procurement planning
Procurement
Construction
Marketing of product solutions
Component design
Tendering
Production planning
Procurement
Component production
Component delivery
Marketing of product info
Tendering
Material deliveries
Use of the building
Maintenance
Building maintenance
Project phase Sender Sending app. Receiver Receiving application Information content
the whole project design coordinator, architect requirements definition and management applications designers (arch., structural, buildg. services, LCC, LCA, SLP) design applications (CAD modeling), LCC, LCA and SLP applications spatial requirements spaces, building elements, building service systems related requirements: quality requirements, energy efficiency, service life, use of non-renewable resources, environmental impact
25
3.4.3 Data exchange use case: Between designs

FIG.
3-2 DATA EXCHANGE BETWEEN DESIGNS

4
Construction
Use and Maintenance
Feasibility study
Project management
Design coordination
Preliminary design
Detailed design
Preliminary design
Detailed design
Preliminary design
Detailed design
Preliminary design
LCC / LCA / SLP
Detailed design
Tendering
Procurement
Construction
Component design
Tendering
Production planning
Procurement
Component delivery
Tendering
Material deliveries
Use of the building
Maintenance
design designers (arch., structural, buildg. services, LCC, LCA, SLP) CAD modeling; LCC, LCA and SLP applications designers (arch., structural, buildg. services, LCC, LCA, SLP) design applications (CAD modeling) visualization, collision detection LCC, LCA and SLP applications spaces, building elements, building service elements construction types and equipment types 3D shape, location materials (LCC, LCA, and SLP analysis) change requests
26
3.4.4 Data exchange use case: Manufacturers/ suppliers product information to design
FIG.
3-3 DATA EXCHANGE SUPPLIERS PRODUCT INFORMATION TO DESIGN
design manufacturers and suppliers product libraries designers (arch., structural, buildg. services, LCC, LCA, SLP) early design applications design applications (CAD modeling) LCC, LCA and SLP applications building elements, building service elements construction types and equipment types 3D shape, (location) specific properties service life in use condition, service life declaration cost information price information
27
3.4.5 Data exchange use case: From design to construction planning

FIG.
3-4 DATA EXCHANGE FROM DESIGN TO CONSTRUCTION PLANNING
design, construction planning designers (arch., structural, building services) design applications (CAD modeling) construction planners component designers quantity take-off and cost estimation applications construction planning applications component design applications building elements, building service elements construction types and equipment types 3D shape, location specific properties
28
3.4.6 Data exchange use case: Between project management, construction and deliveries
FIG.
3-5 DATA EXCHANGE BETWEEN PROJECT MANAGEMENT, CONSTRUCTION,

DELIVERIES
construction planning, construction project management manufacturers and suppliers project management applications delivery management applications project management manufacturers and suppliers project management applications delivery management applications deliveries, delivery time schedule requirements for receiving of the delivery: storage, lifting equipment
29
3.4.7 Data exchange use case: General project management

FIG.
3-6 DATA EXCHANGE BY PROJECT MANAGEMENT

4
Construction
Use and Maintenance
Feasibility study
Project management
Project management
Design coordination
Project management
Preliminary design
Detailed design
Project management
Preliminary design
Detailed design
Project management
Preliminary design
Detailed design
Project management
Preliminary design
LCC / LCA / SLP
Detailed design
Project management
Tendering
Procurement
Construction
Project management
Component design
Tendering
Production planning
Procurement
Component delivery
Project management
Tendering
Material deliveries
Use of the building
Maintenance
the whole project project management all actors project management and time scheduling applications cost monitoring applications project management all actors project management and time scheduling applications cost monitoring applications tasks, task decomposition task sequences, timing task dependencies task results cost monitoring information
30
3.4.8 Data exchange use case: From design and construction to use and maintenance
FIG.
3-7 DATA EXCHANGE TO USE AND MAINTENANCE
commissioning of the building designers, constructors design applications, as-built applications users, maintenance maintenance applications LCC applications building maintenance planning information: spaces, building elements, building service elements; maintenance plans life cycle information service life information
31
3.4.9 Data exchange use case: Between use and maintenance

FIG.
3-8 DATA EXCHANGE BETWEEN USE AND MAINTENANCE

4
Construction
Use and Maintenance
Feasibility study
Project management
Design coordination
Preliminary design
Detailed design
Preliminary design
Detailed design
Preliminary design
Detailed design
Preliminary design
LCC / LCA / SLP
Detailed design
Tendering
Procurement
Construction
Component design
Tendering
Production planning
Procurement
Component delivery
Tendering
Material deliveries
Use of the building
Maintenance
Project phase Sender Sending app.
building use and maintenance owners, service providers, (users) maintenance planning maintenance applications fault reporting applications owners, service providers, (users) maintenance planning maintenance applications fault reporting applications fault reporting service requests maintenance tasks, timing, execution
Receiver Receiving application Information content
IAI Project ST-5 Structural Timber Model Part I: Overview 4 DtH 2.0 Walkthrough
32
4 DtH 2.0 Walkthrough

4.1 Basics
4.1.1 File format
The file format is described in ISO 1030321. The files are divided into a header section and a data section:
ISO-10303-21; HEADER; /* mandatory headers from ISO 10303-21 header_section_schema, see section 4.2.1 */ keyword(parameter list); /* DtH headers, see section 4.2.2 */ keyword(parameter list); ENDSEC; DATA; /* entity instances from DtH schema: */ #number = keyword(parameter list); ENDSEC; END-ISO-10303-21;
4.1.2 Parameter tokens, units

Parameter lists in DtH files may contain these ISO 1030321 tokens:
INTEGER REAL STRING ENTITY_NAME ENUMERATION LIST
e.g. 1 e.g. 1.50 e.g. 'example' e.g. #0250 e.g. .STEEL. e.g. (#1,#2,#3) mm N K kg s (millimeter) (Newton) (degree) (Kelvin) (kilogram) (second)
All values are measured in following base units and in units derived thereof: Lengths Force Angle Temperature difference Weight Time (duration)
Positive angles move counterclockwise. Date and time are expressed in strings of the format 'dd.mm.yyyy' and 'hh:mm'.
33
If optional attributes are omitted, the $ sign appears in the DtH file as a placeholder.
4.1.3 Coordinate systems

The global coordinate system is a right-handed Cartesian system with the xy plane being horizontal and the positive z dimension directed upwards. Local coordinate systems can be nested. In other words a local coordinate system can relate to the global system or to another local system. A local coordinate system is defined by three points within the parent coordinate system: KI KJ KR origin of the locale coordinate system a point at the positive x axis of the locale coordinate system a point at the first quadrant of the xz plane of the coordinate system
Points in two-dimensional spaces e.g. contours of cut-outs carry x and z coordinates in DtH, unlike IFC where they carry x and y coordinates. Exceptions are the shapes of cross sections which are defined in the yz plane. The local coordinates of straight beam-like members are hence oriented with the x axis along the member center axis. The local y axis of plate-like members is aligned to the direction of the plate depth.
4.1.4 Version control

All DtH entities provide a NR attribute which serves as a unique identifier. It is sufficient to ensure uniqueness per type of entity. The value of NR has to be preserved throughout every modification of the STEP file until an entity instance is deleted. Furthermore there is a DATE attribute which denotes the day of last modification of the entity instance. Whenever any other attribute of an entity instance is modified, the DATE attribute has to be updated.10
4.1.5 External references and component catalogs

Numerous attributes denote short names or descriptors that should be machine readable. Such attributes are strings of a precisely defined form. Several classification systems provide such descriptor definitions, e.g. DIN standards that are concerned with material properties. A special German classification system is the Bauteilkatalog Holz (timber building parts catalog) which was developed by the DGfH along with DtH. The referred classification system is denoted in a string attribute by a prefixed source symbol. The prefix is delimited by a colon. The prefix symbols are declared by a SOURCES record. Example:
10
Exception: The date must not be modified if reference attributes are renumbered during re-ordering of STEP file records.
34
A header line SOURCES(('B:BTK1.0','D4047:DIN 4074-2')); introduces two classification sources. An attribute 'B:BTK=01.RNA;TG=DIN1052;D=6;L=260;OB=GV;TFK=III' denotes an galvanized ring-shank nail of the size 6mm 260mm and capacity class III, while the most often used German timber grade would be denoted as 'D4047:NH II'. A special case are the attributes AVA_POSITION.STLB and AVA_POSITION.STLNR which reference keys according to the German classification system Standardleistungsbuch STLB without need for a header entry and string prefixes. Another special kind of reference is used in MEMBER_LTYP which may contain the file name of a DXF file with member geometry data.
4.2 General project data

4.2.1 Standard ISO 1030321 headers
The following file headers are defined by the ISO 1030321 header_section_schema.
ENTITY file_description; description : LIST [1:?] OF STRING (256); implementation_Level : STRING (256); END_ENTITY; ENTITY file_name; name time_stamp author organization preprocessor_version originating_system authorisation END_ENTITY; ENTITY file_schema; schema_identifiers END_ENTITY; : : : : : : : STRING (256); STRING (256); LIST [1:?] OF STRING (256); LIST [1:?] OF STRING (256); STRING (256); STRING (256); STRING (256); -- can't decide on en-us or en-gb
: LIST [1:?] OF STRING (256);
The schema identifier of the current version of DtH is 'DtH 2.0'.
4.2.2 DtH headers

ENTITY OWNER; OWNER_NAME END_ENTITY; : STRING; -- building owner
ENTITY BUILDING_SITE; BS : STRING; END_ENTITY; ENTITY ARCHITECT; ARCH : STRING; END_ENTITY;
-- location of site (e.g. postal address)
-- name and address of architect
35
ENTITY SPECIFICATION; SPECI : STRING; END_ENTITY; ENTITY SOURCES; SOURCE_STRINGS : LIST OF STRING; END_ENTITY;
-- description of the projected building
-- external references (see section 4.1.5)
The DtH spec adds these entities to the ISO 1030321 header_section_schema, not to the DtH schema. Hence they appear in the HEADER of a STEP file, unlike all following entities that belong to the DATA section.
4.3 Common classes

4.3.1 Generic classes
ENTITY STRING_VALUE; NR : OPTIONAL INTEGER; DATE : OPTIONAL INTEGER; VALUE1 : STRING; END_ENTITY; ENTITY INTEGER_VALUE; NR : OPTIONAL INTEGER; DATE : OPTIONAL INTEGER; VALUE1 : INTEGER; END_ENTITY; ENTITY REAL_VALUE; NR : OPTIONAL INTEGER; DATE : OPTIONAL INTEGER; VALUE1 : REAL; END_ENTITY;
These entities are provided for vendor-specific extensions, e.g. as reference to inhouse libraries of prefabricated components or for 3D visualization parameters.
4.3.2 Groupings
ENTITY STRUCTURE; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; TYP : STRUCTURE_TYP; BEZ : OPTIONAL STRING; ENT : LIST OF SEL_ALL_ENT; END_ENTITY;
-- kind of group, see below -- designation of group -- group members
TYPE STRUCTURE_TYP = ENUMERATION OF (CONSTRUCTION, -- group of detailing data DESIGN, -- group of architectural data STRUCTURAL_ANALYSIS, -- group of structural data PRODUCTION, -- group of fabrication data AVA, -- group of bid/bill data USER, -- arbitrary group; provide context in STRUCTURE.BEZ STRUCTURAL, -- group of load-bearing members NON_STRUCTURAL); -- group of non-bearing members END_TYPE;
36
STRUCTURE allows to group arbitrary entities into logical groups. Note that there are entities for special groups, e.g. BUILDING_PART or DESIGN_CALCULATION. Hence STRUCTURE should only be used if none of the special group entities fits.
ENTITY STRUCTURE_LOCATION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; STRCT : STRUCTURE; KI : SELECT_VERTEX_XYZ; KJ : SELECT_VERTEX_XYZ; KR : SELECT_VERTEX_XYZ; END_ENTITY;
-- local coordinate system of group relative to -the global coordinate system --
Building components that are grouped by a STRUCTURE can be placed collectively into the building geometry by STRUCTURE_LOCATION once or multiple times.
4.3.3 Geometry
ENTITY VERTEX; NR : OPTIONAL DATE : OPTIONAL X : REAL; Y : OPTIONAL Z : REAL; ALPHA : OPTIONAL END_ENTITY; INTEGER; STRING; -REAL; --REAL; --
coordinate coordinate coordinate enclosing angle
By convention of DtH, two-dimensional geometric objects are to be defined in an xz plane. IFC uses xy coordinates in two-dimensional space.
TYPE XYZ_POINT = ARRAY [0:2] OF REAL; END_TYPE; TYPE SELECT_VERTEX_XYZ = SELECT (VERTEX, XYZ_POINT); END_TYPE;
This select data type offers the alternative between references to vertexes and direct insertion of coordinate values into parameter lists.
ENTITY POLYLINE; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; V : LIST OF VERTEX; END_ENTITY;
A polyline is a sequence of n1 lines and arcs between n points defined by VERTEX entities. Arcs are distinguishable from straight lines by a non-zero angle given in the endpoint VERTEX.
37
4.3.4 Grids
ENTITY GRID; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; BEZ : OPTIONAL STRING; TYP : GRID_TYP; GL : LIST OF GRID_LINE; END_ENTITY; TYPE GRID_TYP = ENUMERATION OF (ACHSRASTER, BANDRASTER); END_TYPE;
-- label -- kind of grid, see below
-- axial grid -- strip grid
Axial grids usually comprise center lines of building elements. Strip grids consist of boundaries of longish building elements. IFC does not differentiate these types of grids.
ENTITY GRID_LINE; NR : OPTIONAL DATE : OPTIONAL BEZ : OPTIONAL TYP : GL_TYP; KI : OPTIONAL KJ : OPTIONAL KR : OPTIONAL PL1 : OPTIONAL PL2 : OPTIONAL A1 : OPTIONAL A2 : OPTIONAL A3 : OPTIONAL N1 : INTEGER; N2 : OPTIONAL N3 : OPTIONAL S1 : OPTIONAL S2 : OPTIONAL S3 : OPTIONAL END_ENTITY; INTEGER; STRING; STRING; SELECT_VERTEX_XYZ; SELECT_VERTEX_XYZ; SELECT_VERTEX_XYZ; POLYLINE; POLYLINE; GL_ABSTAND; GL_ABSTAND; GL_ABSTAND; INTEGER; INTEGER; STRING; STRING; STRING;
-----------------
label (visible labels in attrib. S1S3) kind of grid line, see below KIKR = local coordinate system of grid relative to global coordinate system PL1PL2 = root polyline A1A3 = distances N1N3 = number of repetitions or of grid divisions S1S3 = names of the root polyline of each dimension; names of subsequent grid lines are incrementally derived
The semantics of PL1N3 depend on GL_TYP.

TYPE GL_TYP = ENUMERATION OF (RECTANGULAR, -- composed by repetition of 23 orthogonal lines POLYGONAL, -- composed by repetition of a polygon CIRCULAR, -- composed of repeated segments of concentric circles II_ORDER); -- grid on a quadric surface END_TYPE; TYPE GL_ABSTAND = SELECT (REAL_TYPE, XYZ_POINT, VERTEX); END_TYPE;
While DtH allows for spatial grids, e.g. 3D rectangular grids or even warped 2nd order grids, IFC contains only planar grids: rectangular, radial, and triangular grids.
38
4.3.5 Other defined data types

TYPE REAL_TYPE = REAL; END_TYPE; TYPE INTEGER_TYPE = INTEGER; END_TYPE; TYPE STRING_TYPE = STRING; END_TYPE; TYPE SEL_ALL_ENT = SELECT (INTEGER_VALUE, REAL_VALUE, STRING_VALUE, VERTEX, POLYLINE, GRID, GRID_LINE, STRUCTURE, STRUCTURE_LOCATION, BUILDING_PART, OPENING, FOUNDATION, MATERIAL, CROSS_SECTION, COMPOSITE_CROSS_SECTION, DESIGN_CALCULATION, NODE, BOUNDARY_CONDITION, ELEMENT, ELASTIC_SUPPORT, ELEMENT_NODE_CONNECTIVITY, ELEMENT_ECCENTRICITY, ACTION, ACTION_COMBINATION_RULE, ACTION_COMBINATION, NODAL_ACTION, ELEMENT_ACTION, NODAL_REACTION, ELEMENT_REACTION, MEMBER, SURFACE, MITER_SQUARE, CUTOUT, CUTOUT_TIMBER, HOLE, SIGNATURE, COLD_BEND, MEMBER_LOCATION, BOLT, WELD, GLUE, TIMBER_CONNECTION, CONNECTION, AVA_TITEL, AVA_POSITION); END_TYPE;
4.4 Architectural model

4.4.1 Building sections, floors
ENTITY BUILDING_SECTION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; BEZ : STRING; BS_TEXT : OPTIONAL LIST OF STRING_VALUE; END_ENTITY; ENTITY FLOOR; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; BEZ : STRING; FL_TEXT : OPTIONAL LIST OF STRING_VALUE; END_ENTITY;
-- label, e.g. 'east wing' -- descriptive texts
-- label, e.g. 'ground floor' -- descriptive texts
There are select data types that allow simple strings as alternative to the above entities:
TYPE SEL_SECT END_TYPE; = SELECT (STRING_TYPE, BUILDING_SECTION);
TYPE SEL_FLOOR = SELECT (STRING_TYPE, FLOOR); END_TYPE;
The assignment of building parts to building sections and floors happens in DtH by specification of building section and floor as attributes of building parts.
39
4.4.2 Building parts

ENTITY BUILDING_PART; NR : OPTIONAL DATE : OPTIONAL PROD_SPEC : OPTIONAL TYP1 : BP_TYP1; TYP2 : OPTIONAL TYP3 : OPTIONAL INTEGER; STRING; STRING_VALUE; BP_TYP2; BP_TYP3;
-----
product identifier kind of building part external part? load bearing part?
-- placement in global coordinates KI : OPTIONAL SELECT_VERTEX_XYZ; KJ : OPTIONAL SELECT_VERTEX_XYZ; KR : OPTIONAL SELECT_VERTEX_XYZ; -- location FLOOR SECTION -- geometry CONTOUR THICK ALIGN CONTOUR_TEXT FABRIC -- components PARTS OPEN : OPTIONAL SEL_FLOOR; : OPTIONAL SEL_SECT; : : : : : LIST OF POLYLINE; OPTIONAL REAL; OPTIONAL BP_ALIGN; OPTIONAL LIST OF STRING_VALUE; OPTIONAL LIST OF BP_FABRIC;
: OPTIONAL LIST OF MEMBER_LOCATION; : OPTIONAL LIST OF OPENING;
-- values for structural analysis AXIAL_STIFF : OPTIONAL REAL; BENDING_STIFF : OPTIONAL REAL; SHEAR_STIFF : OPTIONAL REAL; STAT_TEXT : OPTIONAL STRING_VALUE;
-- description conc. structural analysis
-- special zones of the building part SPECIAL_POLY : OPTIONAL LIST OF POLYLINE; SPECIAL_TEXT : OPTIONAL LIST OF STRING_VALUE; -- physical properties F : OPTIONAL STRING; K : OPTIONAL REAL; RW : OPTIONAL REAL; END_ENTITY; TYPE BP_TYP1 END_TYPE; TYPE BP_TYP2 END_TYPE; TYPE BP_TYP3 END_TYPE; TYPE BP_ALIGN END_TYPE; -- fire resistance classification -- thermal transmittance in W/mK (U) -- sound transmission loss in dB
= ENUMERATION OF (WALL, ROOF, SLAB, COLUMN, GIRDER); = ENUMERATION OF (EXTERNAL, INTERNAL); = ENUMERATION OF (STRUCTURAL, NON_STRUCTURAL); = ENUMERATION OF (N, M, P);
TYPE BP_FABRIC = SELECT (SURFACE, CUTOUT, CUTOUT_TIMBER, HOLE, SIGNATURE); END_TYPE;
The geometry of a wall can be specified in three ways: by one polygon in CONTOUR, wall thickness in THICK, alignment in y direction relative to the polygon in ALIGN (P = thickness in positive y direction, N = thickness in negative y direction, M = centered);
IAI Project ST-5 Structural Timber Model Part I: Overview 4 DtH 2.0 Walkthrough by two polygons in CONTOUR for inner surface and outer surface;
40
by more than two polygons in CONTOUR for inner and outer surface and all other boundaries. CONTOUR_TEXT may provide designations for the wall surfaces and edges like 'ridge', 'eaves', 'verge'. The number of strings in the CONTOUR_TEXT list depends on how CONTOUR is given. The components of a wall are members and openings except for bore holes, notches, and the like for which the FABRIC (fabrication) attribute exists. Note that MEMBER_LOCATION entities are located relative to the global coordinate system while OPENING entities are placed relative to the local coordinate system of the BUILDING_PART.
4.4.3 Openings
ENTITY OPENING; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; PROD_SPEC : OPTIONAL STRING_VALUE; TYP1 : OP_TYP1; TYP2 : OPTIONAL OP_TYP2; TYP3 : OPTIONAL OP_TYP3; TYP4 : OPTIONAL OP_TYP4; KI : OPTIONAL SELECT_VERTEX_XYZ; KJ : OPTIONAL SELECT_VERTEX_XYZ; KR : OPTIONAL SELECT_VERTEX_XYZ; CONTOUR : LIST OF POLYLINE; END_ENTITY;
----------
product identifier kind of opening external opening? door/window panel operation operation direction relative to y placement in coordinates of the BUILDING_PART local coordinate system geometry
TYPE OP_TYP1 = ENUMERATION OF (DOOR, WINDOW, STAIRS_X, CHIMNEY, OTHER); END_TYPE; TYPE OP_TYP2 = ENUMERATION OF (EXTERNAL, INTERNAL); END_TYPE; TYPE OP_TYP3 = ENUMERATION OF (FIXED, LEFT, RIGHT, LR, LEFT_P, RIGHT_P, LR_P, TOP, BOTTOM, V_PIVOT, H_PIVOT, V_SLIDE, H_SLIDE, LOUVRE, OTHER); END_TYPE; TYPE OP_TYP4 = ENUMERATION OF (POS, NEG); END_TYPE;
The CONTOUR of an opening is constructed of polylines as described for the BUILDING_PART entity.
41
4.4.4 Stairs
ENTITY STAIRS; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; BEZ : OPTIONAL STRING; PROD_SPEC : OPTIONAL LIST OF STRING_VALUE; TYP1 : ST_TYP1; TYP2 : ST_TYP2; FLOOR : OPTIONAL SEL_FLOOR; SECTION : OPTIONAL SEL_SECT; WALKLINE : POLYLINE; STEPS : OPTIONAL INTEGER; GOING : OPTIONAL REAL; RISE : OPTIONAL REAL; ML : OPTIONAL LIST OF MEMBER_LOCATION; BP_O : OPTIONAL BUILDING_PART; BP_U : OPTIONAL BUILDING_PART; OPEN : OPTIONAL OPENING; END_ENTITY;
---------------
label product identifier kind of construction geometric type location location walking line number of risers tread length riser height components upper support lower support opening within BP_O
TYPE ST_TYP1 = ENUMERATION OF (CONCRETE, CARRIAGE, STRINGER, CANTILEVER, HANGING, BOLTS, OTHER); END_TYPE; TYPE ST_TYP2 = ENUMERATION OF (STRAIGHT, RECT, ANGLE, CURVED, SPIRAL); END_TYPE;
4.4.5 Foundations
ENTITY FOUNDATION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; BEZ : OPTIONAL STRING; PROD_SPEC : OPTIONAL STRING_VALUE; TYP : FOU_TYP; KI : OPTIONAL SELECT_VERTEX_XYZ; KJ : OPTIONAL SELECT_VERTEX_XYZ; KR : OPTIONAL SELECT_VERTEX_XYZ; SEC : OPTIONAL SEL_SECT; CONTOUR : LIST OF POLYLINE; THICK : OPTIONAL REAL; FABRIC : OPTIONAL LIST OF FOU_FABRIC; ASXO : OPTIONAL REAL; ASYO : OPTIONAL REAL; ASXU : OPTIONAL REAL; ASYU : OPTIONAL REAL; AS_TEXT : OPTIONAL STRING; STAT_TEXT : OPTIONAL STRING_VALUE; END_ENTITY;
-----
label product identifier kind of foundation placement in global coordinates
-- location -- geometry -- maximum upper reinforcement -- maximum lower reinforcement -- description of reinforcement -- description conc. structural analysis
TYPE FOU_TYP = ENUMERATION OF (SINGLE, STRIP, SPREAD); END_TYPE; TYPE FOU_FABRIC = SELECT (SURFACE, CUTOUT, HOLE, SIGNATURE); END_TYPE;
4.4.6 Comparison to IFC

IFC 2x2 already provide extensive support for architectural design. The respective entities reside mainly in the Interoperability layer, IfcSharedBldgElements schema.
42
4.5 Structural analysis model

4.5.1 Materials
ENTITY MATERIAL; NR DATE BEZ : OPTIONAL INTEGER; : OPTIONAL STRING; : OPTIONAL STRING; -- short name according to a classification REAL; REAL; REAL; REAL; REAL; REAL; -----------------elastic modulus along the grain elastic modulus across the grain shear modulus specific gravity moisture content, in % shrinkage and swelling: dimensional change coefficient in % per 1% change in moisture content bending stress along the grain tensile stress along the grain tensile stress across the grain compressive stress along the grain compressive stress across the grain ditto, larger deformation accepted shearing stress (splitting along the grain) shear stress (under transverse load) torsional stress
-- general properties E_P : OPTIONAL E_S : OPTIONAL G : OPTIONAL RHO : OPTIONAL U : OPTIONAL ALPHA_S : OPTIONAL -- allowable stresses ZUL_SIGMA_B : OPTIONAL ZUL_SIGMA_ZP : OPTIONAL ZUL_SIGMA_ZS : OPTIONAL ZUL_SIGMA_DP : OPTIONAL ZUL_SIGMA_DS1 : OPTIONAL ZUL_SIGMA_DS2 : OPTIONAL ZUL_TAU_A : OPTIONAL ZUL_TAU_Q : OPTIONAL ZUL_TAU_T : OPTIONAL
REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL;
-- properties of wood-based panels LABFU : OPTIONAL REAL; -- number of plies in plywood PND : OPTIONAL REAL; -- nominal thickness -- elastic modulus along the face grain E_PXY : OPTIONAL REAL; -- out-of-plane bending E_PXZ : OPTIONAL REAL; -- in-plane bending/ compression/ tension -- elastic modulus across the face grain E_SXY : OPTIONAL REAL; -- out-of-plane bending E_SXZ1 : OPTIONAL REAL; -- in-plane bending/ compression/ tension E_SXZ2 : OPTIONAL REAL; -- in-plane compression/ tension -- shear modulus G_XY : OPTIONAL REAL; -- out-of-plane bending (rolling shear) G_XZ : OPTIONAL REAL; -- in-plane bending (shear through thickness) -- allowable stresses of wood-based ZUL_SIGMA_B_PXZ : OPTIONAL REAL; ZUL_SIGMA_B_SXZ : OPTIONAL REAL; ZUL_SIGMA_B_PXY : OPTIONAL REAL; ZUL_SIGMA_B_SXY : OPTIONAL REAL; ZUL_SIGMA_Z_PX : OPTIONAL REAL; ZUL_SIGMA_Z_SX : OPTIONAL REAL; ZUL_SIGMA_D_PX : OPTIONAL REAL; ZUL_SIGMA_D_SX : OPTIONAL REAL; ZUL_SIGMA_D_PZ : OPTIONAL REAL; ZUL_SIGMA_D_SZ : OPTIONAL REAL; ZUL_TAU_PZX : OPTIONAL REAL; ZUL_TAU_SZX : OPTIONAL REAL; ZUL_TAU_PYX : OPTIONAL REAL; ZUL_TAU_SYX : OPTIONAL REAL; panels -- in-plane bending, stress along the grain -- in-plane bending, stress across the grain -- out-of-plane bending, stress along the grain -- out-of-plane bending, stress across the grain -- in-plane tension along the grain -- in-plane tension across the grain -- in-plane compression along the grain -- in-plane compression across the grain -- out-of-plane compression along the grain -- out-of-plane compression across the grain -- in-plane shear, component along the grain -- in-plane shear, component across the grain -- rolling shear, component along the grain -- rolling shear, component across the grain
-- allowable bearing stress on bolt holes (intrados pressure) ZUL_SIGMA_PL : OPTIONAL REAL; -- along the grain ZUL_SIGMA_SL : OPTIONAL REAL; -- across the grain END_ENTITY;
43
The terms along the grain/ across the grain are used in in-line comments above for shortness. The terms parallel to the grain and perpendicular to the grain are more common and more accurate. Sometimes fiber is used instead of grain, or a strength axis of panels is referred to. German design codes symbolize these terms and the term at an angle to the grain by indexed glyphs ||, , and while the European design code uses the indexes 0 (null), 90, and . Furthermore, the direction of the load that generates stresses is usually referred to where mechanical properties are considered. For solid timber (and for dowel-type connectors), the terms axially loaded and laterally loaded are used. The terms axially loaded, loaded perpendicular to wide faces of lamination, and loaded parallel to wide faces of lamination are common for glulam.11 For wood-based panels, the terms loaded out of plane and loaded in plane are used. The name provided by BEZ is meant to be machine-readable. Such names are humanreadable in most cases as well. However, in case of a hard-to-read classification system, an additional attribute for a human-readable clear text name would be helpful. Such a name attribute could also provide supplemental information not covered by the classification system, like trade names. The LABFU attribute may be insufficient to describe some less common types of plywood. A complete identification requires the number of layers along with the number of plies.12 The attribute ALPHA_S is actually a mean value, also known as the selected or weighted dimensional change coefficient cC. This value derives from the according directed dimensional change coefficients of solid timber, cR (radial to growth ring grain orientation) and cT (tangential to growth ring orientation). cC is the value of most practical importance for solid timber and glulam. Wood-based panels would be better characterized by RLE (relative linear expansion; within panel plane)13 and RTS (relative thickness swell). The less significant property modulus of rupture is not provided.
4.5.2 Cross sections

ENTITY CROSS_SECTION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; TYP : CS_TYP; -- section type, see CS_TYP below DEF : CS_DEF; -- used if TYP is one of CCS, PL1, or PL2 BEZ : OPTIONAL STRING; -- label
11
DtH does not provide this differentiation for glulam, consistent with traditional German design practice. The differentiation becomes necessary in order to utilize the full load-carrying capacity of newer high-strength glulam layups. A plywood consists of layers. Each layer consists of one or two plies with grain in the same direction. A notation common in North America is number of plies/ number of layers. Strictly spoken, RLE is not a constant but a function of moisture content.
12
13
44
-- geometric dimensions and angles; semantics depend H : OPTIONAL REAL; B : OPTIONAL T_S : OPTIONAL REAL; T_G : OPTIONAL R_1 : OPTIONAL REAL; R_2 : OPTIONAL R_3 : OPTIONAL REAL; K : OPTIONAL H_2 : OPTIONAL REAL; H_3 : OPTIONAL B_2 : OPTIONAL REAL; B_3 : OPTIONAL F_1 : OPTIONAL REAL; F_2 : OPTIONAL F_3 : OPTIONAL REAL; T_1 : OPTIONAL C : OPTIONAL REAL; ALPHA_S : OPTIONAL ALPHA_G : OPTIONAL REAL; E_Y : OPTIONAL E_Z : OPTIONAL REAL; ALPHA : OPTIONAL
on TYP REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL;
-- mechanical section properties A : OPTIONAL REAL; -- area I_Y : OPTIONAL REAL; -- moment of inertia I_Z : OPTIONAL REAL; -- ditto I_ETA : OPTIONAL REAL; -- moment of inertia around principal axis I_XI : OPTIONAL REAL; -- ditto I_T : OPTIONAL REAL; -- torsional moment of inertia W_YP : OPTIONAL REAL; -- moment of resistance (max. y coordinate) W_YN : OPTIONAL REAL; -- ditto (min. y coordinate) W_ZP : OPTIONAL REAL; -- ditto (max. z coordinate) W_ZN : OPTIONAL REAL; -- ditto (min. z coordinate) W_T : OPTIONAL REAL; -- torsional moment of resistance C_M : OPTIONAL REAL; -- resistance to warping torsion W_PLY : OPTIONAL REAL; -- plastic moment of resistance W_PLZ : OPTIONAL REAL; -- ditto A_Y : OPTIONAL REAL; -- area for calculation of shear deflection A_Z : OPTIONAL REAL; -- ditto A_SY : OPTIONAL REAL; -- area for calculation of shear stress A_SZ : OPTIONAL REAL; -- ditto Y_M : OPTIONAL REAL; -- position of shear center Z_M : OPTIONAL REAL; -- ditto -- other G : OPTIONAL REAL; G_H : OPTIONAL REAL; U : OPTIONAL REAL; END_ENTITY; -- nominal weight per length -- commercial weight per length -- circumferential area per length
TYPE CS_DEF = SELECT (CS_DEF_PL, COMPOSITE_CROSS_SECTION); END_TYPE; TYPE CS_DEF_PL = LIST OF POLYLINE; END_TYPE; TYPE CS_TYP (I, -L, -U, -B, -RU, -RO, -M, -C, -T, -Z, -SO, -KA, -KF, -KQ, -CCS, -PL1, -PL2); -END_TYPE; = ENUMERATION OF hot-rolled I steel section hot-rolled L steel section hot-rolled U steel section rectangular section, optionally beveled circular section, optionally a sector only circular steel tube section rectangular steel tube section cold-rolled or folded C steel section hot-rolled T steel section hot-rolled Z steel section special hot-rolled steel crane rail section, German type A hot-rolled steel crane rail section, German type F hot-rolled steel crane rail section, German type Q composite cross section, see COMPOSITE_CROSS_SECTION arbitrary, defined by outer and inner boundary lines arbitrary cold-rolled steel section, defined by sheet center line
45
Several attributes and cross section types typical to steel structures were adopted from PSS because timber structures may contain steel elements as well. Unlike German design practice, structural performance of plywood panels is often calculated using effective values of A and I in American practice. These effective values depend on stress direction relative to grain orientation of the plywood layers. In DtH, mechanical section properties of CROSS_SECTION are meant to be real values solely based on geometry, not on material. Wood-based I beams and other composed sections where effective values of A and I are required are meant to be described by COMPOSITE_CROSS_SECTION instances. Effective section properties can easily be computed from real properties of the parts of a composed cross section. However, a simplified representation of prefabricated I beams and similar commodity products by one MATERIAL and one CROSS_SECTION instead of COMPOSITE_CROSS_SECTION is conceivable.
FIG.
4-1 RECTANGULAR AND CIRCULAR CROSS SECTIONS
TYP=.B.
TYP=.RU.
FIG.
46
4-2 CROSS SECTION TYPES
47
ENTITY COMPOSITE_CROSS_SECTION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; CS : LIST OF CROSS_SECTION; CS_Y : LIST OF REAL; CS_Z : LIST OF REAL; CS_ALPHA : LIST OF REAL; CS_SP : LIST OF CCS_CS_SP; CS_MA : OPTIONAL LIST OF MATERIAL; V_CS_1 : OPTIONAL LIST OF CROSS_SECTION; V_CS_2 : OPTIONAL LIST OF CROSS_SECTION; V_Y : OPTIONAL LIST OF REAL; V_Z : OPTIONAL LIST OF REAL; WHERE WK1: SIZEOF(CS) = SIZEOF(CS_Y); WK2: SIZEOF(CS) = SIZEOF(CS_Z); WK3: SIZEOF(CS) = SIZEOF(CS_ALPHA); WK4: SIZEOF(CS) = SIZEOF(CS_SP); WK5: SIZEOF(CS) = SIZEOF(CS_MA); WK6: SIZEOF(V_CS_1) = SIZEOF(V_CS_2); WK8: SIZEOF(V_Y) = SIZEOF(V_Z); END_ENTITY;
-----------
partial cross sections insertion coordinates insertion coordinates insertion angle insert flipped around z axis partial materials connected partial cross sections connected partial cross sections coordinates of connections coordinates of connections
TYPE CCS_CS_SP = ENUMERATION OF (MIRRORED, UNMIRRORED); END_TYPE;
FIG.
4-3 EXAMPLES OF COMPOSED CROSS SECTIONS
48
4.5.3 Structural analysis

FIG.
4-4 HIERARCHIES IN THE STRUCTURAL ANALYSIS MODEL
structural analysis model mechanical systems elements nodes boundary conditions load combinations load combination rules load cases loads nodal loads: forces and displacements element loads: forces, temperature loads, imperfections reactions (results) nodal reactions: support reactions, node displacements element reactions: internal forces, element displacements Model layout The structural analysis model may contain several mechanical systems, each grouping nodes, elements, loads, and reactions.14 A mechanical system can be three- or twodimensional. DtH 2.0 contains only linear elements; in other words there are so far no shells, plates, solids, contact elements, et cetera. Elements connect to nodes. The connections can be eccentric. Elements can be continuously elastically supported. One node can of course be connected to more than one element. Load cases group loads. Load combinations actually group both load cases as well as reactions. Load combination rules define how load cases come together in a combination.
14
A node, element, or load could theoretically be part of more than one mechanical system. Practical reasons stand against that however.
49
For example, wind may be a load case, snow another one. Wind snow comprise a load combination. According to the German code DIN 1055-5:06.1975, the deterministic rules wind + snow/2 and wind/2 + snow may be used. The results (reactions) of the load combination shall be calculated using the most unfavorable rule. Nodal loads and nodal reactions provide references to the according nodes. Likewise, element loads and element reactions reference their respective elements. One instance of a load may be associated to multiple nodes or elements and thus can represent actually a multitude of real loads.
FIG.
4-5 DTH ENTITIES FOR STRUCTURAL ANALYSIS, SIMPLIFIED EXPRESS-G
Apart from the references depicted in fig. 4-5, the ELEMENT entity references MATERIAL and CROSS_SECTION, entities which are shared with the structural detailing model. Material and cross section of an element may alternatively be determined by reference to a MEMBER_LOCATION entity of the structural detailing model. Such a reference also allows for implementation of consistency checks between the two models. Mechanical systems
ENTITY DESIGN_CALCULATION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; TYP : DC_TYP; BEZ : OPTIONAL STRING; EL : OPTIONAL LIST OF ELEMENT; AC : OPTIONAL LIST OF ACTION_COMBINATION; KI : OPTIONAL SELECT_VERTEX_XYZ; KJ : OPTIONAL SELECT_VERTEX_XYZ; KR : OPTIONAL SELECT_VERTEX_XYZ; END_ENTITY;
--------
dimensionality label members combined loads placement in global coordinates
50
TYPE DC_TYP = ENUMERATION OF (TWO_DIM, -- planar structure THREE_DIM, -- spatial structure BEAM_GRID, -- grid of beams CONT_BEAM); -- continuous span beam END_TYPE;
Nodes and boundary conditions

ENTITY NODE; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; K : SELECT_VERTEX_XYZ; BC : OPTIONAL BOUNDARY_CONDITION; END_ENTITY; ENTITY BOUNDARY_CONDITION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; ALPHA_X : OPTIONAL REAL; ALPHA_Y : OPTIONAL REAL; ALPHA_Z : OPTIONAL REAL; FX : OPTIONAL BC_TYP; FY : OPTIONAL BC_TYP; FZ : OPTIONAL BC_TYP; MX : OPTIONAL BC_TYP; MY : OPTIONAL BC_TYP; MZ : OPTIONAL BC_TYP; MW : OPTIONAL BC_TYP; END_ENTITY;
-- placement -- supports
-- angle between bearing reactions and -superior coordinate system --- translational components -- rotational components -- warpage
TYPE BC_TYP = SELECT (BC_FC, -- free, or rigid constraint REAL_TYPE, -- spring coefficient INTEGER_TYPE); -- coupled with the same degree of freedom of another node, END_TYPE; -node number is given as a negative integer number TYPE BC_FC = ENUMERATION OF (FREE, CONSTRAINED); END_TYPE;
Structural elements
ENTITY ELEMENT; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; TYP : ELEMENT_TYP; N : LIST OF EL_N; K : OPTIONAL SELECT_VERTEX_XYZ; ALPHA : OPTIONAL REAL; ML : OPTIONAL MEMBER_LOCATION; CS_1 : OPTIONAL CROSS_SECTION; CS_2 : OPTIONAL CROSS_SECTION; MAT : OPTIONAL MATERIAL; ES : OPTIONAL ELASTIC_SUPPORT; END_ENTITY; TYPE ELEMENT_TYP = ENUMERATION (BEAM, -- member TRUSS, -- member TENSION_MEMBER); -- member END_TYPE;
-- local orientation -- local orientation -- cross section at starting point -- cross section at end point
OF carries bending moment, transversal and axial force carries axial force only carries axial tensile force only
TYPE EL_N = SELECT (NODE, ELEMENT_NODE_CONNECTIVITY, ELEMENT_ECCENTRICITY); END_TYPE;
IAI Project ST-5 Structural Timber Model Part I: Overview 4 DtH 2.0 Walkthrough continuous elastic support of an element:
ENTITY ELASTIC_SUPPORT; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; RI : RICHTUNG; -X : OPTIONAL REAL; -L : OPTIONAL REAL; -C1 : REAL; -C2 : OPTIONAL REAL; -D : OPTIONAL REAL; -END_ENTITY;
51
direction start abscissa length bedding value at starting point bedding value at end point eccentricity
TYPE RICHTUNG = ENUMERATION OF (FX, FY, FZ, MX, MY, MZ, MW); END_TYPE;
eccentric connection of an element to a node:

ENTITY ELEMENT_ECCENTRICITY; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; N : EE_N; KS : EE_KS; EX : OPTIONAL REAL; EY : OPTIONAL REAL; EZ : OPTIONAL REAL; END_ENTITY; TYPE EE_N = SELECT (NODE, ELEMENT_NODE_CONNECTIVITY); END_TYPE; TYPE EE_KS = (WCS, -SCS, -ECS); -END_TYPE; ENUMERATION OF world coordinates coordinates in local coordinate system of DESIGN_CALCULATION element coordinates
type of connection of an element to a node:

ENTITY ELEMENT_NODE_CONNECTIVITY; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; N : ENC_N; KS : ENC_KS; FX : OPTIONAL ENC_CON; -- translational components FY : OPTIONAL ENC_CON; FZ : OPTIONAL ENC_CON; MX : OPTIONAL ENC_CON; -- rotational components MY : OPTIONAL ENC_CON; MZ : OPTIONAL ENC_CON; MW : OPTIONAL ENC_CON; -- warpage END_ENTITY; TYPE ENC_N = SELECT(NODE, ELEMENT_ECCENTRICITY); END_TYPE; TYPE ENC_KS = ENUMERATION OF (WCS, -- world coordinates SCS, -- coordinates in local coordinate system of DESIGN_CALCULATION ECS); -- element coordinates END_TYPE; TYPE ENC_CON = SELECT (ENC_CON_E, -- free or rigid REAL_TYPE); -- spring coefficient END_TYPE;
52
TYPE ENC_CON_E = ENUMERATION OF (FREE, CONSTRAINED); END_TYPE;
Loads load case:

ENTITY ACTION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; TYP : ACTION_TYP; GAMMA : OPTIONAL REAL; BEZ : OPTIONAL STRING; ACT : LIST OF ACTION_ACT; END_ENTITY;
-----
semi-probabilistic category partial safety factor, or arbitrary load factor label forces and displacements
TYPE ACTION_TYP = ENUMERATION OF (IMPERFECTION, -- imperfection PERMANENT, -- dead load VARIABLE, -- life load EXTRAORDINARY); -- accidental load END_TYPE; TYPE ACTION_ACT = SELECT (NODAL_ACTION, ELEMENT_ACTION); END_TYPE;
The attributes TYP and GAMMA were adopted from PSS. The German design code for steel structures has been based on the limit state design method since the early 1990s, hence these attributes were chosen with partial factor method in mind. The German design code for timber structures is still based on allowable stresses.15 However, the distinction between dead loads, life loads, and accidental loads is significant nonetheless. Allowable stresses can be modified according to the kind of load. Furthermore the ratio between dead loads and live loads is important for the determination of flexure. load combination:
ENTITY ACTION_COMBINATION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; ACR : OPTIONAL ACTION_COMBINATION_RULE; ACT : OPTIONAL LIST OF ACTION; -- list of load cases to combine PSI : OPTIONAL LIST OF REAL; -- list of combination factors MODE : AC_MODE; -- mechanical theory REA : OPTIONAL LIST OF AC_REA; -- results END_ENTITY; TYPE AC_MODE = ENUMERATION OF (E_TH_I_O, -- elastic materials, 1st order theory E_TH_II_O); -- elastic materials, 2nd order theory END_TYPE; TYPE AC_REA = SELECT (NODAL_REACTION, ELEMENT_REACTION); END_TYPE;
15
The national design code is now in the process to be replaced by the Eurocode, or a national derivative of the Eurocode respectively. The Eurocode is based on limit state design.
IAI Project ST-5 Structural Timber Model Part I: Overview 4 DtH 2.0 Walkthrough collection of load combination rules:
ENTITY ACTION_COMBINATION_RULE; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; ACT : LIST OF LIST OF ACTION; -- list of mutually exclusive combinations PSI : LIST OF LIST OF REAL; -- list of combination factors MODE : ACR_MODE; -- mechanical theory WHERE WK1: SIZEOF(ACT) = SIZEOF(PSI); WK2: SIZEOF(ACT[I]) = SIZEOF(PSI[I]); END_ENTITY; TYPE ACR_MODE = ENUMERATION OF (E_TH_I_O, -- elastic materials, 1st order theory E_TH_II_O); -- elastic materials, 2nd order theory END_TYPE;
53
nodal forces and displacements:

ENTITY NODAL_ACTION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; N : LIST OF NODE; -KS : NA_KS; -RI : RICHTUNG; -TYP : NA_TYP; -F_K : REAL; -END_ENTITY;
location(s) of occurrence reference coordinate system load direction, see definition below ELASTIC_SUPPORT type of load load value (characteristic value)
TYPE NA_KS = ENUMERATION OF (WCS, -- world coordinates TCS); -- coordinates in local coordinate system of DESIGN_CALCULATION END_TYPE; TYPE NA_TYP = ENUMERATION OF (FORCE, DISPLACEMENT); END_TYPE;
element forces and displacements:

ENTITY ELEMENT_ACTION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; EL : LIST OF ELEMENT; KS : EA_KS; X : REAL; L : REAL; RI : RICHTUNG_2; TYP : EA_TYP; F_K1 : REAL; F_K2 : OPTIONAL REAL; END_ENTITY;
---------
location(s) of occurrence reference coordinate system start abscissa length load direction type of load load value (characteristic value) at starting point load value (characteristic value) at end point
TYPE EA_KS = ENUMERATION OF (WCS, -- world coordinates WCS_ECS, -- world coordinates; F_K1 and F_K2 relate to the true element length SCS, -- coordinates in local coordinate system of DESIGN_CALCULATION SCS_ECS); -- ditto; F_K1 and F_K2 relate to the true element length END_TYPE; TYPE RICHTUNG_2 = ENUMERATION OF (FX, FY, FZ, MX, MY, MZ, MW, X, Y, Z); END_TYPE; TYPE EA_TYP = ENUMERATION OF (FORCE, TEMPERATURE, IMPERFECTION); END_TYPE;
IAI Project ST-5 Structural Timber Model Part I: Overview 4 DtH 2.0 Walkthrough Results (reactions) nodal forces (support reactions) and nodal displacements:
ENTITY NODAL_REACTION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; N : NODE; -FX : OPTIONAL REAL; -FY : OPTIONAL REAL; FZ : OPTIONAL REAL; MX : OPTIONAL REAL; -MY : OPTIONAL REAL; MZ : OPTIONAL REAL; MW : OPTIONAL REAL; -END_ENTITY;
54
location translation, or force rotation, or clamping moment warping deformation, or warping moment
It depends on the boundary condition of each degree of freedom if the attributes FXMW denote a displacement or a force. Generally only displacements are stored and support reactions have to be calculated using the spring coefficient at the respective degree of freedom. Only if a rigid support is present, the particular value denotes a force or moment. element forces (internal forces) and element displacements (deflections):
ENTITY ELEMENT_REACTION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; EL : ELEMENT; X : REAL; -TYP : ER_TYP; -FX : OPTIONAL REAL; -FY : OPTIONAL REAL; FZ : OPTIONAL REAL; MX : OPTIONAL REAL; -MY : OPTIONAL REAL; MZ : OPTIONAL REAL; MW : OPTIONAL REAL; -END_ENTITY;
abscissa type of reaction deflection, or internal force rotation, or bending moment warping deformation, or warping moment
TYPE ER_TYP = ENUMERATION OF (DEFORMATION, -- deflection MEMBER_FORCE); -- internal force END_TYPE;

IFC 2x2 already provide support for structural analyzing tasks, mainly by the IfcStructuralAnalysisDomain schema in the Domain layer. Materials and cross sections are described in the IfcMaterialPropertyResource, IfcProfileResource, and IfcProfilePropertyResource within the lowest IFC layer. Minor extensions for timber structures are necessary.
55
4.6 Structural detailing model

4.6.1 Materials, cross sections
The MATERIAL and CROSS_SECTION classes of the structural analysis model are used by the structural detailing model as well.
4.6.2 Members
Principles DtH discerns between configuration and placement of members, i.e. there are separate objects for member types and for member occurrences. The member configuration contains a parametric description of the shape. Only raw shapes are stored; shape modifications are separately added by additional feature objects (subsection 4.6.3). Member configuration
ENTITY MEMBER; NR : OPTIONAL DATE : OPTIONAL CS : OPTIONAL MAT : OPTIONAL PR : OPTIONAL PNR : OPTIONAL BEZ : OPTIONAL LTYP : OPTIONAL PL1 : OPTIONAL CATCH : OPTIONAL C_SEL : OPTIONAL G : OPTIONAL G_H : OPTIONAL U : OPTIONAL END_ENTITY; INTEGER; STRING; CROSS_SECTION; MATERIAL; LIST OF MEMBER_PR; STRING; STRING; MEMBER_LTYP; POLYLINE; MEMBER; MEMBER_C_SEL; REAL; REAL; REAL;
-----------
processing features position number (alphanumeric label) descriptor (name, label) geometry gluing direction for cutting into two members ditto norm weight commercial weight circumferential area
TYPE MEMBER_PR = SELECT (SURFACE, MITER_SQUARE, CUTOUT, CUTOUT_TIMBER, HOLE, SIGNATURE, COLD_BEND); END_TYPE; TYPE MEMBER_LTYP = SELECT (REAL_TYPE, -- length POLYLINE, -- variant 1: MEMBER.LTYP is the center axis, MEMBER.CS provides -- profile geometry. First and last point of MEMBER.LTYP differ. -- variant 2: MEMBER.LTYP is the contour, MEMBER.CS provides -- thickness. First and last point of MEMBER.LTYP are identical. STRING_TYPE); -- file name of a DXF file holding explicit 3D member geometry END_TYPE; TYPE MEMBER_C_SEL = ENUMERATION OF (L, -- left R); -- right END_TYPE;
There is a possibility to define two members being cut out of one raw member. The benefit is optimized utilization of joinery machines. The two parts which are created by a severing process (CUTOUT_TIMBER, TYP=.T1.) are caught by two MEMBER entities. The attribute CATCH of these members refers to the sawed original member.
56
C_SEL selects which of the two parts is caught. The attributes CS, MAT, LTYP and PL1 are ignored and must be set to $.
FIG.
4-6 CUTTING A RAW MEMBER INTO TWO

MEMBER 0
with CUTOUT_TIMBER of TYP = .T1.
MEMBER 1A
with CATCH = MEMBER 0 and C_SEL = .L.
MEMBER 1B
with CATCH = MEMBER 0 and C_SEL = .R.
After a member has been defined by one MEMBER instance, it can be inserted into the structure by MEMBER_LOCATION multiple times. Placement of members
ENTITY MEMBER_LOCATION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; MEM : OPTIONAL MEMBER; ML : OPTIONAL MEMBER_LOCATION; PNR : OPTIONAL STRING; BEZ : OPTIONAL STRING;
-----
member configuration structure superordinate to this member position number (alphanumeric label) descriptor (name, label)
-- placement in global coordinates or in local coordinates of superordinate member KI : SELECT_VERTEX_XYZ; KJ : SELECT_VERTEX_XYZ; KR : SELECT_VERTEX_XYZ; -- offset LAGE : ALPHA : DX1 : DX2 : DY : DZ : between MEMBER_LOCATION local coordinates and MEMBER local coordinates ML_LAGE; -- shift from MEMBER center to MEMBER edge OPTIONAL REAL; -- rotation around MEMBER x axis OPTIONAL REAL; -- x translation for alignment of the MEMBER start point OPTIONAL REAL; -- x translation for alignment of the MEMBER end point OPTIONAL REAL; -- y translation OPTIONAL REAL; -- z translation -- weight
GK : OPTIONAL REAL; END_ENTITY;
TYPE ML_LAGE = ENUMERATION OF (NYNZ, -- NY and NZ NY, -- shift in negative NYPZ, -- NY and PZ NZ, -- shift in negative M, -- no shift PZ, -- shift in positive PYNZ, -- PY and NZ PY, -- shift in positive PYPZ); -- PY and PZ END_TYPE;
y direction z direction z direction y direction
The attribute ML is set if the member is part of an assembled configuration (if the member is attached to a superordinate member).
PNR, BEZ, GK are typically only set if the member is a superordinate member (if this instance of MEMBER_LOCATION represents an assembled unit). Superordinate members may have an empty MEM attribute.
57
Translations by DX1 are in fact identical to those by DX2. Only one of these attributes should be used, otherwise they must be set to the same value. The differentiation between DX1 and DX2 gives a hint whether the translation serves to align the start point of the member or its end point.16
FIG.
4-7 ALIGNMENT OF A MEMBER BY OFFSETS
= 0 LA = .M. Dx = 0 Dy = 0 Dz = 0
= 0 LA = .NYNZ. Dx = 0 Dy = 0 Dz = 0
=-20 LA = .NYNZ. Dx = 0 Dy = 0 Dz = 0
=-20 LA = .NYNZ. Dx = 0 Dy =-100 Dz = 0
FIG.
4-8 DTH ENTITIES FOR STRUCTURAL DETAILING, SIMPLIFIED EXPRESS-G

assembly
MEMBER_LOCATION
building part
L
connection
L
division
MEMBER
L
CROSS_SECTION
L
MATERIAL
COMPOSITE_CROSS_SECTION
HOLE
SURFACE
MITER_SQUARE
COLD_BEND
CUTOUT
CUTOUT_TIMBER
SIGNATURE
16
There is however no hint to which other member surface, grid line, or expansion joint etc. the member is actually aligned to. Furthermore, the case where no particular alignment was intended is indistinguishable from cases with intended alignment.
58
4.6.3 Processing features

Following entities describe surface treatment, mitering, contour out-cutting, spatial cutting and severing cuts, bore holes and hole patterns, signatures (imprints),
and cold bending of sheet metal in a feature-oriented manner. Not only geometry information is provided by the following entities but also high-level information about the type of feature. This allows for subsequent modification of these features using specialized CAD modules and potentially helps to derive NC machine control protocol. Surface treatment
ENTITY SURFACE; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; BEZ : OPTIONAL STRING; -- description TYP : SURFACE_TYP; -- process type D : OPTIONAL REAL; -- thickness, penetrated depth, or insertion time V_PL : OPTIONAL LIST OF POLYLINE; -- geometry of treated area END_ENTITY; TYPE SURFACE_TYP= ENUMERATION OF (PLANING, -- planing ROUGHLY_PLANING, -- rough-planing PAINTING, -- brush application SPRAYING, -- spray application DIPPING, -- dip application TANK, -- tank steeping PRESSURE, -- boiler pressure impregnation ALTERNATING_PRESSURE, -- alternating pressure process VACUUM, -- vacuum impregnation BANDAGE, -- wrapping INJECTION); -- injection process END_TYPE;
If V_PL is omitted, the whole member is to be treated. Mitering

ENTITY MITER_SQUARE; NR : OPTIONAL DATE : OPTIONAL ORT : MS_ORT; ALPHA_Y : REAL; ALPHA_Z : REAL; END_ENTITY; INTEGER; STRING; -- location -- angle around local y axis -- angle around local z axis
TYPE MS_ORT = ENUMERATION OF (BEGINNING_OF_MEMBER, END_OF_MEMBER); END_TYPE;
FIG.
59
4-9 DEFINITION OF MITER ANGLES

a y= 25
a y= 40
x y z
a z= 42
a z= 19
There is no explicit definition of positive and negative angles given in the DtH specification, only an explanation by example as shown in fig. 4-9, which was derived from PSS. The miter feature was eventually taken out of PSS whereas the CUTOUT entity of PSS was extended for miters. Contour out-cutting
ENTITY CUTOUT; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; PL : POLYLINE; KI : OPTIONAL SELECT_VERTEX_XYZ; KJ : OPTIONAL SELECT_VERTEX_XYZ; KR : OPTIONAL SELECT_VERTEX_XYZ; Y1 : REAL; Y2 : REAL; END_ENTITY;
-------
2-dimensional subtrahend contour placement of the subtrahend contour, given in local member coordinates upper y ordinate of subtrahend volume lower y ordinate of subtrahend volume
A cut-out is a Boolean subtraction of an extruded polyline from a member.

FIG.
4-10 MEMBER WITH CUT-OUT
In PSS, the CUTOUT entity was extended by another attribute that describes by enumeration whether the cut-out is a miter, a cope, a preparation for welding, an interior cut-out (i.e. an arbitrarily shaped hole), or an arbitrary exterior cut-out.
IAI Project ST-5 Structural Timber Model Part I: Overview 4 DtH 2.0 Walkthrough Spatial cutting, severing cuts, drilling, other surface processing
ENTITY CUTOUT_TIMBER; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; TYP : CT_TYP; -- type of feature SUB_TYP : OPTIONAL CT_SUB_TYP; -- subtype of feature BEZ : OPTIONAL STRING; -- description (artisanal term) V : LIST OF VERTEX; -- geometry by significant points K : OPTIONAL LIST OF REAL; -- edge qualities or radii A : OPTIONAL LIST OF CT_A; -- plane qualities, entrance and exit of borer -- SUB_TYP may only be set if TYP = .F1. .F8. -- number and meaning of values in V, K, and A depend on the type of feature -- order of values in V, K, and A is significant END_ENTITY; TYPE CT_TYP = ENUMERATION OF -- CUTOUT_TIMBER.V defines -- shaping (F1, -- 3 points, 1 plane, no edges F2, -- 4 points, 2 planes, 1 edge F3, -- 6 points, 3 planes, 2 edges F4, -- 4 points, 3 planes, 3 edges F5, -- 6 points, 4 planes, 5 edges F6, -- 8 points, 5 planes, 8 edges F7, -- 8 points, 6 planes, 12 edges F8, -- subtype dependent -- drilling B1, -- one or more bore holes B2, -- one or more pocket holes B3, -- a keyway for a ring connector -- severing T1, -- 3 points of the dividing plane -- marking O1, -- 2 points of a marker line (chalk line or keyway) -- planing O2); -- n points of an area that is to be planed END_TYPE; TYPE CT_SUB_TYP = ENUMERATION OF (ALLGEMEIN, -- arbitrary shape ABGRATUNG, -- edge cut KERVE, -- birds mouth, perpendicular to member axis SCHLEIFKERVE, -- birds mouth BLATT, -- scarf FALZ, -- rabbet GRAT, -- ridge, e.g. on a hip rafter KEHLE, -- chase, e.g. on a valley rafter HEXENSCHNITT, -- end face of hip rafter or valley rafter towards eaves FIRSTBLATT, -- scarf to join rafters at the ridge AUSBLATTUNG, -- cogging, seating KLAUENKERVE, -- cogging, seating ZAPFENLOCH, -- mortise NUT, -- groove, dado ZAPFEN, -- tenon (with 2 shoulders) ZAPFEN_ABGESETZT, -- stub tenon (tenon with 34 shoulders) ZAPFEN_GEDREHT, -- stub tenon, not parallel to member side faces VERSATZ, -- stepped joint: strut end VERSATZ_KERVE, -- stepped joint: seating GERBER, -- splayed scarf HAKENBLATT); -- splayed and tabled scarf END_TYPE;
60
61
TYPE CT_A = ENUMERATION OF -- quality of cut planes (AE0, -- the plane is preserved AE1, -- the plane may be destroyed at the edges AE2, -- the plane may be destroyed -- quality of bore holes AB0, -- unspecified AB1, -- drill entry must be splinter-free AB2, -- drill exit must be splinter-free AB3, -- AB1 and AB2 AB4, -- hole is mechanically prepared as a pocket hole and manually finished -- as a drilled-through hole AB5); -- AB1 and AB4 END_TYPE;
The CUTOUT_TIMBER entity focuses on processing of straight work pieces with originally rectangular cross section. The working planes are defined by intersection points. High-level type information is provided to allow CAD software to edit the processing features by parametric routines. The shape parameters (intersection points) actually comprise a face based surface model (an open faceted B-rep) with some unique characteristics: A limited set of possible face topologies is supported. The face topology is explicitly given by CUTOUT_TIMBER.TYP. Depending on the topology type, only a subset of all vertices are stored. Missing vertices have to be reconstructed by receiving applications based on the feature information and on the raw shape of the member before feature creation. No edges and faces are stored. Their topology and geometry is to be derived from vertices and the feature topology type information.
Since a fixed order of sequence of vertices, edges, and faces is implied, it is easy to address selected edges and faces within the surface model. This is used to attach information about manufacturing quality to individual edges and faces. There is some overlapping between CUTOUT_TIMBER and processing entities inherited from PSS (MITER_SQUARE, CUTOUT, HOLE). This redundancy was accepted in order to support steel members by DtH in a limited way, preserving similarity to PSS. The CUTOUT_TIMBER.A attribute allows for appropriate selection of processing tool and speed when NC code is generated, according to the desired quality of cuts and holes.
FIG.
62
4-11 CUTOUT_TIMBER, TYPE F1: A SINGLE CUT
.F1. two times

FIG.
4-12 CUTOUT_TIMBER, TYPE F2: TWO CUTS
.F2. two times

FIG.
4-13 CUTOUT_TIMBER, TYPE F3: THREE CUT PLANES,

MEETING IN TWO EDGES
FIG.
4-14 CUTOUT_TIMBER, TYPE F4: THREE CUT PLANES,

MEETING IN THREE EDGES
FIG.
63
4-15 CUTOUT_TIMBER, TYPE F5: FOUR CUT PLANES TYPE F6: FIVE CUT PLANES FOR MORTISES AND GROOVES TYPE F7: TENONS
FIG.
4-16 CUTOUT_TIMBER, TYPE F8: POLYGONAL INTERSECTION
stepped joint strut
splayed and tabled scarf
seating
Circular holes, hole patterns

ENTITY HOLE; NR : OPTIONAL DATE : OPTIONAL V : OPTIONAL TYP : OPTIONAL D : OPTIONAL T : OPTIONAL ALPHA_E : OPTIONAL KI : OPTIONAL KJ : OPTIONAL KR : OPTIONAL END_ENTITY; INTEGER; STRING; LIST OF VERTEX; -- for hole patterns: placements of holes HOLE_TYP; -- type of hole REAL; -- diameter REAL; -- depth of pocket hole, thread, or countersink REAL; -- angle of countersink or thread end SELECT_VERTEX_XYZ; -- placement of the hole or of the SELECT_VERTEX_XYZ; -hole pattern, given in local SELECT_VERTEX_XYZ; -member coordinates
TYPE HOLE_TYP = ENUMERATION OF (DRILLING, -- bore hole PUNCHING, -- punched hole FLAME_DRILLING, -- autogenous drilling TAPPING, -- threaded hole CENTRE_DRILLING, -- center punch COUNTERSINKING); -- pocket hole or countersink END_TYPE;
FIG.
64
4-17 HOLE PATTERN
Multiple HOLE instances may be needed for one actual hole according to the fabrication steps. E.g. a pocket hole, a countersink, and a thread comprise a threaded pocket hole. The technologic sequence is however not indicated. Oblong holes and prismatic holes are not covered by HOLE but by CUTOUT. The HOLE entity of the current PSS specification also differentiates whether a thread is left- or right-handed and whether the hole coordinates relate to the original form of a workpiece or to its form after cold-bending. Signatures (imprints)
ENTITY SIGNATURE; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; H : OPTIONAL REAL; TEXT : STRING; KI : SELECT_VERTEX_XYZ; KJ : SELECT_VERTEX_XYZ; KR : SELECT_VERTEX_XYZ; END_ENTITY;
-- text height -- text content -- placement relative to the local member coor-dinate system --
In PSS, a signature can alternatively be represented by a list of polylines instead of a character string.
FIG.
4-18 MEMBER WITH SIGNATURE
IAI Project ST-5 Structural Timber Model Part I: Overview 4 DtH 2.0 Walkthrough Cold bending of sheet metal
ENTITY COLD_BEND; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; KI : SELECT_VERTEX_XYZ; KJ : SELECT_VERTEX_XYZ; KR : SELECT_VERTEX_XYZ; ALPHA : REAL; R : REAL; END_ENTITY;
65
------
start point end point reference point bending angle bending radius
FIG.
4-19 COLD BENT SHEET METAL
4.6.4 Connections
Following entities describe standard metal fasteners like bolts and nails, welded joints of steel parts, glued joints,
arbitrary mechanical fasteners. The first few entities in this subsection describe the type and configuration of fasteners and joints used in a project. The last entity in this subsection, entity CONNECTION, represents the physical instances of these fasteners and joints. This allows to define e.g. one type of BOLT once and to insert it multiple times at different locations using CONNECTION. Several entities and attributes typical to connections in steel structures were adopted from PSS because timber structures may contain steel elements as well. Bolts, nails, and similar fasteners Two main possibilities to exchange information about fastener types exist: Explicit specification of the various geometric and mechanic fastener properties, or
exchange of a standard fastener designation, recognized by all receiving applications. The latter was determined as the preferred method, and a classification and notation system for materials and components used in German timber construction practice
66
was issued by DGfH (Bauteilkatalog Holz). For example, a ringed shank nail could be specified by the name BTK=01.RNA;TG=DIN1052;D=6;L=260;OB=GV;TFK=III. This example of a standardized designation contains the product subclass, technical standard, size, surface protection, and capacity class of the fastener.
ENTITY BOLT; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; -- labels BEZ1 BEZ2 BEZ3 TYP VF (descriptors) : LIST OF STRING; : OPTIONAL LIST OF LIST OF STRING; : OPTIONAL LIST OF STRING; : OPTIONAL BOLT_TYP; : OPTIONAL BOLT_VF; -----parts on side of the bolt head parts between connected members parts on side of the nut kind of fastener, see below bored with clearance (play)
-- mechanical properties ASP : OPTIONAL REAL; MY : OPTIONAL REAL; FV : OPTIONAL REAL; -- dimensions K : OPTIONAL D1 : OPTIONAL D2 : OPTIONAL D3 : OPTIONAL D4 : OPTIONAL D5 : OPTIONAL ALPHA_K : OPTIONAL LN : OPTIONAL LK_MIN : OPTIONAL LK_MAX : OPTIONAL LR : OPTIONAL LH : OPTIONAL LG : OPTIONAL LS : OPTIONAL ALPHA_G : OPTIONAL E : OPTIONAL S : OPTIONAL F : OPTIONAL RF : OPTIONAL R : OPTIONAL HM : OPTIONAL SA : OPTIONAL KG : OPTIONAL N : OPTIONAL T : OPTIONAL A : OPTIONAL H : OPTIONAL BR : OPTIONAL BS : OPTIONAL HS : OPTIONAL END_ENTITY; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; REAL; BOLT_SA; INTEGER; REAL; REAL; REAL; REAL; REAL; REAL; REAL;
-- stress area -- friction coefficient -- pre-stress force ------------------------------height of bolt head nominal thread diameter shank diameter diameter below countersunk head transitional diameter head diameter angle of countersunk head nominal length minimal grip length maximal grip length width of staple resin-coated length thread length thread pitch, or groove distance thread pitch (angle) corner-to-corner dimension of bolt head head width (width of flats) height of lens head head radius curvature radius nut height head type (wrench type) nominal wrench size slot width (wrench size) slot depth clamp thickness clamp height width of clamp back width of clamp top washer height
TYPE BOLT_TYP = ENUMERATION OF (WOOD_SCREW, -- wood screw STEEL_SCREW, -- bolt SCREW_SET, -- set of bolt + washers + nut (assembly) NAIL, -- smooth nail SPECIAL_NAIL, -- threaded nail CRAMP, -- staple BAUKLAMMER_FORM_A, -- clamp, DIN shape A (carpenters dog, timber dog) BAUKLAMMER_FORM_C, -" " " C " " " " BAUKLAMMER_FORM_D, -" " " D " " " " DOWEL, -- dowel PIN); -- threaded rod END_TYPE;
67
TYPE BOLT_VF = ENUMERATION OF (TRUE, FALSE); END_TYPE; TYPE BOLT_SA = ENUMERATION OF (NORMAL, -- slotted head KREUZSCHLITZ_H, -- Phillips head type H KREUZSCHLITZ_Z); -- Phillips head type Z END_TYPE;
The BOLT entity is an extension of the equally named entity in PSS. It covers not only bolts but also nails, screws, and dowel type fasteners used in timber connections. The current PSS specification splits BOLT into a shortened BOLT entity for bolt sets and a BOLT_ELEMENT for the parts of a set. Welded joints
ENTITY WELD; NR : OPTIONAL DATE : OPTIONAL BEZ : OPTIONAL NA : OPTIONAL ND : OPTIONAL KL : OPTIONAL OFORM : OPTIONAL SV : OPTIONAL A : REAL; INTEGER; STRING; STRING; WELD_NA; REAL; WELD_KL; WELD_OFORM; WELD_SV;
B : OPTIONAL REAL; C : OPTIONAL REAL; END_ENTITY;
------------
description, additional specification type, shape thickness orientation of fillet welds surface: plane, convex, or concave? technology calculation value of thickness (of linear welds), or height (of flush welds), or diameter (of spot welds) single weld length of intermittent welds gap length of intermittent welds
TYPE WELD_NA = ENUMERATION OF (BOERDEL_NAHT, I_NAHT, V_NAHT, HV_NAHT, Y_NAHT, HY_NAHT, U_NAHT, HU_NAHT, GEGENNAHT, KEHLNAHT, LOCHNAHT, PUNKTNAHT, LINIENNAHT, STEILFLANKENNAHT, HALB_STEILFLANKENNAHT, STIRNFLAECHENNAHT, FLAECHENNAHT, SCHRAEGNAHT, FALZNAHT, AUFTRAGSNAHT, DV_NAHT, DHV_NAHT, DY_NAHT, DHY_NAHT, DU_NAHT, DHU_NAHT, VU_NAHT, V_NAHT_MIT_GEGENLAGE, DOPPELKEHLNAHT, DREIBLECHNAHT, SONSTIGE_NAHT, UNTERBROCHENE_KEHLNAHT, VERSETZT_UNTERBROCHENE_KEHLNAHT); END_TYPE; TYPE WELD_KL = ENUMERATION OF (POSITIV, NEGATIV); END_TYPE; TYPE WELD_OFORM = ENUMERATION OF (GLATT, GEWOELBT, HOHL); END_TYPE; TYPE WELD_SV = ENUMERATION OF (AUTOGEN, OFFENES_LICHTBOGEN_VON_HAND, OFFENES_LICHTBOGEN_MECHANISCH, UNTERPULVER, UNTERSCHIENEN, WIG, MIG, MAG, PUNKT, ABBRENNSTUMPF, BOLZEN); END_TYPE;
Glued joints
ENTITY GLUE; NR : OPTIONAL DATE : OPTIONAL PL : OPTIONAL TYP : OPTIONAL PRZ : OPTIONAL END_ENTITY; INTEGER; STRING; LIST OF POLYLINE; GLUE_TYP; REAL;
-- geometry and direction -- material -- pressing time (drying time, curing time)
68
TYPE GLUE_TYP = ENUMERATION OF (KAL, -- blood-albumin adhesive KC, -- casein adhesive KCPD, -- copolymer dispersion adhesive KEP, -- epoxy resin adhesive KG, -- glutine glue (animal glue / Scotch glue) KIS, -- isocyanate adhesive KMF, -- melamine formaldehyde resin KPAN, -- polyacrylic nitril rubber adhesive KPBC, -- polychloroprene adhesive KPF, -- phenol formaldehyde resin KPVAC, -- polyvinyl acetate dispersion adhesive KRF, -- resorcinol-formaldehyde resin KSCH, -- hot melt adhesive KUF, -- urea formaldehyde resin KUP, -- polyester adhesive OTHER); -- non-listed adhesive END_TYPE;
The abbreviations in GLUE_TYP were taken from DIN 4076-3:01.1974.17 The corresponding entity in PSS does not provide an enumeration for the glue material but it adds an enumeration attribute to differentiate gluing in spots, lines, or areas. In PSS, the geometry is not an attribute of PSSs GLUE but of an extra attribute named CONNECTION_ELEMENT_LOCATION. Arbitrary fasteners
ENTITY TIMBER_CONNECTION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; BEZ : STRING; -- descriptor END_ENTITY;
Other fasteners like beam hangers are represented by TIMBER_CONNECTION. They are described solely by the BEZ attribute which has to provide complete information by reference of an external catalog or library. The mere use of a key word according to a classification system would be insufficient since classification systems do not contain explicit geometry information. Placement of fasteners and joints
ENTITY CONNECTION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; ML : LIST OF CONNECTION_ML; CON : OPTIONAL CONNECTION_CON; VER : OPTIONAL LIST OF CONNECTION_VER; KI : SELECT_VERTEX_XYZ; KJ : SELECT_VERTEX_XYZ; KR : SELECT_VERTEX_XYZ; LOC : OPTIONAL CONNECTION_LOC; END_ENTITY;
--------
connected members or building parts connecting fastener or joint position of multiple grouped fasteners placement of the connection, given in local coordinates of the first member listed in ML place where the connection is made
TYPE CONNECTION_ML = SELECT (MEMBER_LOCATION, BUILDING_PART, FOUNDATION); END_TYPE;
17
now replaced by European standards
69
TYPE CONNECTION_CON = SELECT (BOLT, WELD, GLUE, TIMBER_CONNECTION); END_TYPE; TYPE CONNECTION_VER = SELECT (CONNECTION_VER_VL, POLYLINE); END_TYPE; TYPE CONNECTION_VER_VL = LIST OF VERTEX; END_TYPE; TYPE CONNECTION_LOC = ENUMERATION OF (SHOP, -- pre-assembled ON_SITE); -- field-assembled END_TYPE;
Once a type of fastener or joint is defined by one of the previous entities, it can be inserted into the structure by CONNECTION multiple times. The CONNECTION instances specify not only the location of fasteners but also the members which they connect, and whether they are joined in the carpenters shop or at the building site.
FIG.
4-20 DTH ENTITIES FOR CONNECTIONS, SIMPLIFIED EXPRESS-G

CONNECTION L L
BUILDING_PART
FOUNDATION
BOLT
GLUE
WELD
MEMBER_LOCATION
TIMBER_CONNECTION
The equivalent of DtHs CONNECTION in the current PSS specification is split into a similar CONNECTION entity and an additional CONNECTION_ELEMENT_LOCATION entity, see fig. 4-21. The latter contains coordinates and references to type entities while the former provides references to the connected members. Thus PSSs CONNECTION entity resembles the IFC concept of objectified relationships. One CONNECTION instance can reference one or more CONNECTION_ELEMENT_LOCATION instances. Furthermore, there is an optional numeric attribute for PSSs CONNECTION to denote the technological order of all connections.
FIG.
4-21 PSS ENTITIES FOR CONNECTIONS, SIMPLIFIED EXPRESS-G

L[1:?] CONNECTION_ELEMENT_LOCATION L[1:?]
CONNECTION
MEMBER_LOCATION BOLT L[1:?] BOLT_ELEMENT GLUE WELD
70

There are no high-level classes for structural timber detailing in IFC 2x2 yet. Several base classes exist that may serve as parent classes for timber specific entities. One important concept of DtH to split configuration of members and placement of members into two distinct classes (MEMBER for configuration, MEMBER_LOCATION for placement) has not been available in IFC until release of IFC 2x. In terms of the current IFC architecture, configuration objects are type objects (IfcTypeObject of IFC 2x and its subtypes), placement objects are occurrence objects (IfcObject of IFC 1.0 and its subtypes). Placement objects of DtH are very light-weighted in contrast to occurrence objects of IFC. A great number of subtypes of IfcTypeObject was added just recently to IFC by the 2x2 release, acknowledging the advantages of type objects for the versatility of the product model as well as for its interoperability. The basic concept of feature elements was introduced into IFC 2x2 as a deliverable of the ST-3 Precast Concrete Construction project. Note that this concept is only available in form of (and in association with) occurrence objects of IFC. Different to that, DtH associates processing features with type objects; compare fig. 4-8.18 Furthermore, IFC characterizes feature elements as dependent elements that modify shape and appearance whereas DtH combines shape information with technological information. The concept of connections was also introduced into IFC 2x2 by the ST-3 project and in the slightly different context of structural analysis by the ST-4 project. Several entities were proposed by ST-3 to present connecting elements (like mortar and mechanical fasteners), all of which are again only occurrence objects, and an objectified relationship between connected building elements and connecting elements. When the ST-3 deliverables were integrated into IFC, type objects for fasteners were added. IFC classes for steel detailing are supposed to be developed by the IAI ST-4 followup project within about the same time span as the IAI ST-5 project duration. Some features and connection types of DtH that are specific to steel elements will therefore be not included into the Structural Timber Model.
4.7 Cost estimation, bid preparation, billing

The current DtH specification emphasizes on bid preparation, in particular on bills of quantities. In German practice, a bill of quantities is divided into titles which again comprise of positions (items).
18
An exception is the assignment of processing features to building parts. The DtH building parts like walls and slabs are located objects (occurrence objects).
71
ENTITY AVA_TITEL; NR : OPTIONAL DATE : OPTIONAL BEZ : OPTIONAL AP : OPTIONAL PREIS : OPTIONAL END_ENTITY;
INTEGER; STRING; STRING; LIST OF AVA_POSITION; REAL;
-- label -- associated items -- summary price
ENTITY AVA_POSITION; NR : OPTIONAL INTEGER; DATE : OPTIONAL STRING; POSNR : OPTIONAL INTEGER; ART : OPTIONAL AVA_ART; STLB : OPTIONAL STRING; STLNR : OPTIONAL STRING; KTEXT : OPTIONAL STRING; LTEXT : OPTIONAL STRING; EIN : OPTIONAL STRING; MENGE : OPTIONAL REAL; P_E : OPTIONAL REAL; P_G : OPTIONAL REAL; ENT : LIST OF SEL_ALL_ENT; END_ENTITY;
------------
item number type service scope according to STLB key number according to STLB short description long description unit of measurement quantity price per unit total price associated building parts and members
TYPE AVA_ART = ENUMERATION OF (G, -- basic item A, -- alternative item Z, -- extra item E, -- contingency item B, -- request item F); -- item without allocated production overhead END_TYPE;
Comparison to IFC IFC 2x2 provide support for cost estimation, bid preparation, billing, as well as scheduling and construction management throughout the various layers.
4.8 Gaps in DtH 2.0

4.8.1 Missing building services model
There are no provisions for HVAC, plumbing, and electric installation design. The main reason was lack of feedback from relevant software vendors during the past two phases of DtH development. IFC 2x2 provide HVAC, Plumbing, Fire Protection, Electrical, and Building Controls domains.
4.8.2 Limited production model

Differentiation into prefabrication and on-site fabrication While connections can be marked as shop-assembled or field-assembled, there is no such attribute for processing features. This information would be useful for prefabrication planning, erection planning, and quality control. Surface treatments might even be deeper differentiated into treat-
72
ments applied before prefabrication, applied after prefabrication but before transport, or applied on site. Technologic sequences There is no more sophisticated way to describe the order of manufacturing steps beyond the ordered LIST of processing features applied to a member. Superstructures that are divided during prefabrication Prefabricated timber frame panels, especially wall panels, are manufactured in units as large as the production facility allows. After that they are sawn into the actual wall segments. The mechanism shown in fig. 4-6 should therefore be generalized in order to be applicable to superstructures, not only to simple members. (A MEMBER entity which can represent a raw unit to be sawn into two units cannot represent an assembled unit like a wall panel. On the other hand, DtH entities for representation of assemblies cannot be attributed with a dividing cut.) Assemblies, superstructures DtH offers three ways to group building elements into preassembled units. Neither is this ambiguity desirable, nor is any of the three ways perfectly satisfying: First and foremost, the BUILDING_PART entity is meant to represent superstructures. However the physical segmentation of building parts in the production model is generally not identical to the logical segmentation of building parts within the architectural model. The position of members of a building part is given in global coordinates, not in coordinates local to the building part.
The MEMBER_LOCATION entity can represent a superstructure as well, but it does not provide references to its parts. There are only references from the parts to the superstructure. Furthermore, processing features cannot be assigned to an instance of MEMBER_LOCATION.19
The STRUCTURE entity can also represent preassembled units, but there is no possibility to assign properties like transportation weight or processing features to such a structure.
Machine control There is no formal way to assign machine control data (NC protocol) to members and structures, neither directly in a DtH file nor as a reference to an external file.
19
Certain processing features can only be assigned to a superstructure, not to single members. For instance, holes for electrical installation are usually bored into wall panels after sheathing, studs, blocking, and so forth were joined.
IAI Project ST-5 Structural Timber Model Part I: Overview 5 Appendix
73
5 Appendix
5.1 References
[1] ISO 10303: Industrial Automation Systems and Integration - Product Data Representation and Exchange. International Organization for Standardization, TC184/SC4 Industry Foundation Classes (IFC) Release 2x Edition 2. International Alliance for Interoperability; 2003 Standardbeschreibung Produktschnittstelle Stahlbau, Schnittstellenversion April 2000. Deutscher Stahlbau-Verband; Dsseldorf; 2000 (Standard Description Product Interface Steel Construction; in German) DtH-Produktschnittstelle fr den Datenaustausch im Holzbau, Version 1.05. Deutsche Gesellschaft fr Holzforschung; Munich; 1996 (DtH product interface for data exchange in timber construction; in German) Jrn Weichert, Peter Osterrieder: Produktmodell DtH 2.0 fr den Ingenieurholzbau, Zimmermannsbau und Fertighausbau. Brandenburgische Technische Universitt Cottbus, Germany; 2000; ISSN 1615-3952 (Product model DtH for timber engineering construction, carpentry, and prefabricated building construction. English model reference available) IFC 2x Model Integration Guide. IAI Model Support Group; 2002 IFC 2x Extension Modelling Guide. IAI Model Support Group; 2001 Industry Foundation Classes Release 2x; IFC Technical Guide. IAI Model Support Group; 2000 Thomas Liebich, Jeffrey Wix, et al: Standard Analysis Current Situation Building Models. prodAEC deliverable D4.1.2; 2002
[2] [3]
[4]
[5]
[6] [7] [8] [9]
[10] Curtis Parks: IGES Historical Milestones. NIST; 2003 [11] What is STEP? Organisation/ History (ISO). ProSTEP iViP Association; 2003 [12] STEP Management Overview History of STEP. PDIT Inc.; 1996 [13] Christoph Hrenbaum, Peter Katranuschkov, Thomas Liebich, Matthias Weise, et al: IAI ST-4 Released Drafts. iCSS project; 20012002 [14] Kari Karstila, Kalle Sern, et al: IAI ST-3 Released Drafts. 2002 [15] Kari Karstila: FinnTimber-IFC Data exchange use cases and requirements. Product data exchange and sharing for timber construction. 2004
74
5.2 List of figures

fig. 2-1 fig. 2-2 fig. 2-3 fig. 2-4 Data transfer through conventional interfaces ...............................................6 Information sharing via a product model.......................................................6 Timetable of product model developments..................................................10 Scope of current IFC and DtH specifications ..............................................13
fig. 2-5 Extensions to IFC 2x by the ST-3, ST-4, and ST-5 projects .......................14 fig. 3-1 Data exchange From requirements management to design ....................24 fig. 3-2 Data exchange between designs...................................................................25 fig. 3-3 Data exchange Suppliers product information to design ........................26 fig. 3-4 Data exchange From design to construction planning............................27 fig. 3-5 Data exchange between project management, construction, deliveries.......28 fig. 3-6 Data exchange by project management .......................................................29 fig. 3-7 Data exchange to use and maintenance .......................................................30 fig. 3-8 Data exchange between use and maintenance .............................................31 fig. 4-1 fig. 4-2 fig. 4-3 Rectangular and circular cross sections .......................................................45 Cross section types.......................................................................................46 Examples of composed cross sections .........................................................47
fig. 4-4 Hierarchies in the structural analysis model ................................................48 fig. 4-5 DtH entities for structural analysis, simplified EXPRESS-G......................49
fig. 4-6 Cutting a raw member into two ...................................................................56 fig. 4-7 fig. 4-8 fig. 4-9 fig. 4-10 fig. 4-11 fig. 4-12 fig. 4-13 fig. 4-14 Alignment of a member by offsets...............................................................57 DtH entities for structural detailing, simplified EXPRESS-G.....................57 Definition of miter angles ............................................................................59 Member with cut-out..................................................................................59 CUTOUT_TIMBER, type F1: a single cut................................................62 CUTOUT_TIMBER, type F2: two cuts.....................................................62 CUTOUT_TIMBER, type F3: three cut planes, meeting in two edges.....62 CUTOUT_TIMBER, type F4: three cut planes, meeting in three edges...62
fig. 4-15 CUTOUT_TIMBER, type F5: four cut planes type F6: five cut planes for mortises and grooves type F7: tenons .......................................................63
75
fig. 4-16 CUTOUT_TIMBER, type F8: polygonal intersection ..............................63 fig. 4-17 fig. 4-18 fig. 4-19 Hole pattern................................................................................................64 Member with signature ..............................................................................64 Cold bent sheet metal.................................................................................65
fig. 4-20 DtH entities for connections, simplified EXPRESS-G..............................69 fig. 4-21 PSS entities for connections, simplified EXPRESS-G ..............................69
(fig. 3-1fig. 3-8 by courtesy of FinnTimber-IFC project)

10 1 1 195 2934

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

10 1 1 195 2934

Uploaded by

Copyright:

Available Formats

IAI Project ST-5 Structural Timber Model Part I Overview

document rev.: 1.rc1

document status: release candidate

3.4 Information requirements by project stages...................................................23

4 DtH 2.0 Walkthrough...........................................................................................32 4.1 Basics .............................................................................................................32

4.2 General project data .......................................................................................34

4.3 Common classes.............................................................................................35

4.4 Architectural model .......................................................................................38

4.5 Structural analysis model ...............................................................................42

4.6 Structural detailing model..............................................................................55

IAI Project ST-5 Structural Timber Model Part I: Overview 1 Abstract

IAI Project ST-5 Structural Timber Model Part I: Overview 1 Abstract

IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction

2-1 DATA TRANSFER THROUGH

2-2 INFORMATION SHARING VIA

Architect Engineer Work Prep. Machine A Bldg.Services Draftsman Machine B

Architect Engineer Work Prep.

IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction

2.2 Existing product models

IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction

2.2.4 Product model developments in neighboring industries

1980 SET Standard d'Echange

1982 XBF VDA-PS CADLIB VDA-FS Freiformflchen-Schnittstelle

IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction

[9], [10], [11], [12]

IGES 1.0 Initial Graphics Exchange Specification PDES

1991 ATLAS project COMBI project

Computer Integrated Manufacturing for Constructional Steelwork

Ein Produktmodell fr den Stahlbau (Haller)

1997 CIS/1 finished CIS/2 started

DtH 1.05 Datentransfer im Holzbau

2-3 TIMETABLE OF PRODUCT MODEL DEVELOPMENTS1

2002 CIS/2.1 IFC 2x2 ST-5

IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction

2.2.5 Data models for manufacturing of structural timber components

2.3 Integration of DtH into IFC

IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction

2-4 SCOPE OF CURRENT IFC AND DTH SPECIFICATIONS

design, struct. calculation building lifecycle detailing

IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction

2-5 EXTENSIONS TO IFC 2X BY THE ST-3, ST-4, AND ST-5 PROJECTS3

IFC 2x ST-3 ST-4 ST-5

harmonization with BEC

Material Property Resource

Geometric Model Resource

Profile Extension Resource

Measure Extension Resource

Topology Extension Resource

Profile Property Resource

Structural Load Resource

2.4 The concept of partial models

IAI Project ST-5 Structural Timber Model Part I: Overview 2 Introduction

3.1.2 Scope by actors, disciplines4

3.1.3 Scope by project stages

In scope are furthermore pre-fabrication, site construction, as-built documentation.

Partially in scope is preliminary design.

3.2 Vertical and horizontal information sharing, model evolution

3.3 Information requirements by actors, disciplines

3.3.2 Structural engineer

3.3.3 Design engineer, draftsman

As of yet, IFC contain only isotropic material descriptions.

3.3.4 Building services engineer (HVAC, electric equipment, plumbing)

3.3.5 Contractor, manufacturer