Refine
Document Type
- Article (21)
- Conference Proceeding (5)
- Doctoral Thesis (1)
Institute
Keywords
- Produktmodell (27) (remove)
Building project, with many different players involved, requires open and commonly accepted standard for product model description. Product model based design tools support easy comparisons of design alternatives and optimisation of design solution technical quality. This supports client s decision-making and design target comparisons through the whole building project. Use of product models enable these tasks to meet both schedule and cost requirements Olof Granlund is using product models and interoperable software as the main tool in projects. The use and the realised benefits are illustrated by examples from 3 different real projects: University building, where product models were used already in the very early phases by the whole design team. Office building for research organisation, where product models were used in so called self-reporting building system. Headquarters for international company, where product models were widely used for building performance analysis and visualisations in design phase as well as for facilities management system configuration for operational phase.
The Priority Programme ‘Network Based Co-operation in Structural Engineering’ of the ‘German Research Foundation’ (DFG) has been established in the year 2000. This paper describes and discusses the main research directions and first results of the workgroup ‘Distributed Product Models’. The five projects of the workgroup have developed completely different solutions for specific application domains. Each solution concept deals with a consistent product modeling and knowledge processing in a distributed environment in the planning process. The individual solution approaches of the projects are described and the underlying basic assumptions are discussed. A unified system architecture is described for all projects of the workgroup. Two different approaches (object-oriented and graph-based models) have been introduced for product and knowledge modeling. The common structure of these models will be explained to fully understand the differences of these modeling approaches. Finally the concepts for co-operative work and conflict management in a distributed environment are described: The solution approaches will be distinguished by classifying the supported co-operation according to time. A final scientific summary describes the state-of-the-art in network based co-operation in structural engineering: The role of research directions like knowledge modeling, standard product modeling and versioning in the distributed planning process will be explained.
For the management or reorganisation of existing buildings, data concerning dimensions and construction are necessary. Often these data are given exclusively by paper-based drawings and no digital data such as a computer based product model or even a CAD-model are available. In order to perform mass calculation, damage mapping or a recalculation of the structure these drawings of the building under consideration have to be analysed manually by the engineer. This is a very time-consuming job. In order to close this gap between drawings of an existing building and a digital product model an approach is presented in this paper to digitise a drawing, to build up geometric and topologic models and to recognise construction parts of the building. Finally all recognised parts are transformed into a three-dimensional geometric model which provides all necessary geometric information for the product model. During this import process the semantics of a ground floor plan has to be converted into a 3D-model.
In current AEC practice client requirements are typically recorded in a building program, which, depending on the building type, covers various aspects from the overall goals, activities and spatial needs to very detailed material and condition requirements. This documentation is used as the starting point of the design process, but as the design progresses, it is usually left aside and changes are made incrementally based on the previous design solution. These incremental small changes can lead to a solution that may no longer meet the original requirements. In addition, design is by nature an iterative process and the proposed solutions often also cause evolution in the client requirements. However, the requirements documentation is usually not updated accordingly. Finding the latest updates and evolution of the requirements from the documentation is very difficult, if not impossible. This process can lead to an end result, which is significantly different from the documented requirements. Some important requirements may not be satisfied, and even if the design process was based on agreed-upon changes in the scope and requirements, differences in the requirements documents and in the completed building can lead to well-justified doubts about the quality of the design and construction process...
In this paper we present a computer aided method supporting co-operation between different project partners, such as architects and engineers, on the basis of strictly three-dimensional models. The center of our software architecture is a product model, described by the Industry Foundation Classes (IFC) of the International Alliance for Interoperability (IAI). From this a geometrical model is extracted and automatically transferred to a computational model serving as a basis for various simulation tasks. In this paper the focus is set on the advantage of the fully three-dimensional structural analysis performed by p-version of the finite element analysis. Other simulation methods are discussed in a separate contribution of this Volume (Treeck 2004). The validity of this approach will be shown in a complex example.
Im vorliegenden Beitrag wird ein Framework für ein verteiltes dynamisches Produktmodell (FREAC) vorgestellt, welches der experimentellen Softwareentwicklung dient. Bei der Entwicklung von FREAC wurde versucht, folgende Eigenschaften umzusetzen, die bei herkömmlichen Systemen weitgehend fehlen: Erstens eine hohe Flexibilität, also eine möglichst hohe Anpassbarkeit für unterschiedliche Fachdisziplinen; Zweitens die Möglichkeit, verschiedene Tools nahtlos miteinander zu verknüpfen; Drittens die verteilte Modellbearbeitung in Echtzeit; Viertens das Abspeichern des gesamten Modell-Bearbeitungsprozesses; Fünftens eine dynamische Erweiterbarkeit sowohl für Softwareentwickler, als auch für die Nutzer der Tools. Die Bezeichnung FREAC umfasst sowohl das Framework zur Entwicklung und Pflege eines Produktmodells (FREAC-Development) als auch die entwickelten Tools selbst (FREAC-Tools).
The paper presents a general map-based approach to prototyping of products in virtual reality environments. Virtual prototyping of products is considered as a consistent simulation and visualization process mapping the source product model into its target visual representations. The approach enables to interrelate formally the product and visual information models with each other by defining mapping rules, to specify a prototyping scenario as a composition of map instances, and then to explore particular product models in virtual reality environments by interpreting the composed scenario. Having been realized, the proposed approach provides for the strongly formalized method and the common software framework to build virtual prototyping applications. As a result, the applications gain in expressiveness, reusability and reliability, as well as take on additional runtime flexibility...