Jeffrey Wix's research while affiliated with Thatcham and other places

Publications (16)

Article
Institution(s): Abstract: A formal approach for the analysis of AEC/FM related processes has been under-taken in the frames of the EU ICCI cluster project (IST-2001-33022). The approach is based on a modified application of the Generic Process Protocol (GPP) pro-posed in a research project funded by the UK Engineering and Physical Sciences Research...
Chapter
IntroductionIssuesCoding modelAnalysis of regulationsPassing and failingLogical analysisMore complex examplesRepresentation of existing regulationsOntologiesStandardsConclusions Acknowledgements
Article
Full-text available
Efforts to define standards for representing AEC/FM data have been fairly successful. However defining a standard reference process model has not met with the same success. Yet almost every conceptual modelling or software development project starts by defining the business processes to be supported and the related requirements to be satisfied. Thi...
Article
Full-text available
This paper describes a new process-centred method for capturing business and user requirements and their inter-linking with applicable ICT standards. The essence of the developed method is in recognising requirements and use cases in the context of the real construction process, identifying the actors and roles for each individual activity and asso...
Conference Paper
Full-text available
The major project goal of the ISTforCE project is to provide an open, human-centered Web-based collaboration environment which supports concurrent engineering while working on multiple projects simultaneously and offers easy access to specialized engineering services distributed over the Web. Normally, engineering applications are bought and then i...
Conference Paper
Full-text available
The paper intends to describe the architecture of the KEYSTONE (Knowledge Engineering Systematisation of Technical Enterprises memories) project which aims to contribute to create a market based on the systematisation of engineering knowledge in its various forms. KEYSTONE will not only rely on product models, but will also address other form of en...
Technical Report
Full-text available
This document has been created for use as guidance on the methods to be used in the definition ad specification of Industry Foundation Classes. This deliverable fulfills the requirements of work package 1.1 (Methodology) as defined in the version 1.5 project plan. References within this document to the masculine gender shall be taken to imply equal...
Article
Full-text available
Jeff Wix was a dear friend of mine and he died on the 4th of July 2009 in Norway. I could not find the exact paper I am referring to here and that we wrote together with Frits Tolman and Bo-Christer Björk. To contribute to the legacy of Jeff's work I have added here a paper signed by Jeff with our colleague David Bloomfield from BRE, which describe...

Citations

... This approach has advantages in rule execution, which accelerates the checking process [11]. On the other hand, the approach of Nisbet et al. [13] maintained a code representation similar to the structure of the building code. This provides a higher level of maintainability in case of regulatory changes [11]. ...
... € por ano, quando comparados com as verificações habituais, para o caso da Estónia [1,7]. Também a utilizar modelos IFC como fonte principal da informação da construção a ser verificada, a Finlândia tem conduzido vários projetos a nível nacional para estruturar sistemas de verificação regulamentar automatizados [8], dos quais se destaca o piloto implantado na cidade de Vantaa [9]. Distintamente dos desenvolvimentos na Estónia, em Vantaa, os finlandeses utilizaram o software proprietário Solibri Model Checker (SMC) que, apesar de ser amplamente utilizado, tem um custo muito elevado e não é passível de customizações profundas devido ao seu caráter proprietário. ...
... Such efforts are considered critical in overcoming this major barrier to full automation of code compliance checking systems. Semiautomated approach requires manual labeling (or marking up) of the building code requirements using predefined tag set such as Requirement, Applicability, Selection, and Exceptions (RASE) [1] which was used in the SMARTcodes builder software of International Code Council [2]. While the improvement was salient comparing to the hard-coding approach, such semiautomated approach still failed to lead to wide implementation or scaling up of automated building code compliance checking systems. ...
... Employed by the Singapore Building and Construction Authority, the Singapore CORENET project is the first automated code compliance checking system that was used in AEC industry. The project aimed to provide a web based electronic system for rule checking over submitted building documents considering building control, fire code, environmental health, public housing and vehicle parking (Liebich et al., 2002). Norwegian efforts for rule checking aimed to check BIM projects for evaluating spatial program requirements, and building accessibility using the relationships between building components such as spaces, doors, ramps, stairs and windows (Lindberg, 2006). ...
... Other projects (e.g., ATLAS EP7280) extended the objective to cover more if not all stages of the construction process leading to extended data models [17], new integration tools [18] and new software environments including knowledge base systems [19]. The IAI (International Alliance for Interoperability) was established in 1995 and quickly delivered two major IFC (Industry Foundation Classes) releases: IFC 1.0 in January 1997 [20] and IFC 1.5 in November 1997 [21], including the technical corrigenda published as IFC Release 1.5.1 in August 1998 [22] together with a methodology guide, i.e., Methodology for the Development of Industry Foundation Classes [23]. The objective of the IFC was to create a neutral environment for interoperability by providing a comprehensive specification of the information throughout the AEC/FM project lifecycle, globally, across disciplines and software applications [24]. ...
... A term often used to describe such a schema is a kernel or core model. Such a strategy has recently been adopted as the basis for a working group within the STEP AEC committee which is planning and monitoring the development of a number of aspect models [Wix et al. 1994]. A version of such a strategy is used in the following as the basic framework for the presentation of this thesis. ...
... The transformation approaches documented in this thesis (chapters 4 and 5) have been contributed to the project on a subcontractor basis as part of the overall 5 Also, contributions were made regarding the extension of the IFC model with domain models for steel construction and structural analysis. Ontology Specication (Gehre et al., 2006). (ISO 10303-42:1994(ISO 10303-42: , 1994ISO 10303-43:2000ISO 10303-43: , 2000. ...
... • Use of the Process Matrix to support IFC model development There are a number of entities in IFC 2x (Wix and Liebich 2001) that relate to the ideas within the Process Matrix and these can be used to define a subset or view of the IFC 2x model that can uniformly support the basic matrix, a matrix derived process model, and a matrix derived project schedule. Work in this area has begun within ICCI and is now continuing in conjunction with IAI ( Wix et al. 2003). ...
... Tables Table 1. Assessments of BIM technologies tested for interoperability with the IFC standard [5] . 4 Table 2. Evaluating interoperability of data management paradigms . ...
... The development of the IFC schema in 1996 using STEP resource libraries and the Express language [6] maintained the notion of a single model, with a slight tone change that the models should be consolidated into a single IFC file. But in practice, this is never really achieved and it is ever more remote now as the models are increasingly more complex and larger in size, making it impractical to combine them into a single model. ...