<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-11-22T13:36:56Z</responseDate><request verb="GetRecord" identifier="oai:uwspace.uwaterloo.ca:10012/4649" metadataPrefix="dim">https://dspacemainprd01.lib.uwaterloo.ca/server/oai/request</request><GetRecord><record><header><identifier>oai:uwspace.uwaterloo.ca:10012/4649</identifier><datestamp>2017-03-21T16:52:45Z</datestamp><setSpec>com_10012_9900</setSpec><setSpec>com_10012_1</setSpec><setSpec>col_10012_9910</setSpec><setSpec>col_10012_6</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:doc="http://www.lyncode.com/xoai" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="author" authority="bfb16728-34cb-470a-9f64-9bf6c78c48cd" confidence="600">Henriques, David</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2009-08-31T12:56:59Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2009-08-31T12:56:59Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued">2009-08-31T12:56:59Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="submitted">2009</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/10012/4649</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en">The context-workﬂow relationship is often poorly deﬁned or forgotten entirely. In workﬂow &#xd;
systems and applications context is either omitted, deﬁned by the workﬂow or deﬁned &#xd;
based on a single aspect of a contextual dimension. In complex environments this can &#xd;
be problematic as the deﬁnition of context is useful in determining the set of possible &#xd;
workﬂows. Context provides the envelope that surrounds the workﬂow and determines &#xd;
what is or is not possible. &#xd;
The relationship between workﬂow and context is also poorly deﬁned. That context can &#xd;
exist independently of workﬂow is often ignored, and workﬂow does not exist independently &#xd;
of context. Workﬂow representations void of context violate this stipulation. In order for &#xd;
a workﬂow representation to exist in a contextual dimension it must possess the same &#xd;
dimensions as the context. &#xd;
In this thesis we selected one contextual dimension to study, in this case the spatial &#xd;
dimension, and developed a comprehensive deﬁnition using building data models. Building &#xd;
data models are an advanced form of representation that build geometric data models into &#xd;
an ob ject-oriented representation consisting of common building elements. The building &#xd;
data model used was the Industry Foundation Classes (IFC) as it is the leading standard &#xd;
in this emerging ﬁeld. &#xd;
IFC was created for the construction of facilities and not the use of facilities at a &#xd;
later time. In order to incorporate workﬂows into IFC models, a zoning technique was &#xd;
developed in order to represent the workﬂow in IFC. The zoning concept was derived from &#xd;
multi-criteria layout for facilities layout and was adapted for IFC and workﬂow. &#xd;
Based on the above work a zoning extension was created to explore the combination of &#xd;
IFC, workﬂow and simulation. The extension is a proof of concept and is not intended to &#xd;
represent a robust formalized system. The results indicate that the use of a comprehensive &#xd;
deﬁnition of a contextual dimension may prove valuable to future expert systems.</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en">en</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en">University of Waterloo</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en">Workflow</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en">Contextual Analysis</dim:field>
   <dim:field mdschema="dc" element="subject" qualifier="program" lang="en">Management Sciences</dim:field>
   <dim:field mdschema="dc" element="title" lang="en">Using Building Data Models to  Represent Workﬂows and a  Contextual Dimension</dim:field>
   <dim:field mdschema="dc" element="type" lang="en">Master Thesis</dim:field>
   <dim:field mdschema="dc" element="pending" lang="en">false</dim:field>
   <dim:field mdschema="uws-etd" element="degree" qualifier="department" lang="en">Management Sciences</dim:field>
   <dim:field mdschema="uws-etd" element="degree" lang="en">Master of Applied Science</dim:field>
   <dim:field mdschema="uws" element="typeOfResource" lang="en">Text</dim:field>
   <dim:field mdschema="uws" element="peerReviewStatus" lang="en">Unreviewed</dim:field>
   <dim:field mdschema="uws" element="scholarLevel" lang="en">Graduate</dim:field>
   <dim:field mdschema="others" element="access-status">open.access</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>