This document describes use cases that demand a combination of linked data technologies for the building domain. It underpins the collaborative work of the Linked Building Data Community Group operated by the W3C.
The mission of the Linked Building Data Community Group, as described in its charter, is to enable all stakeholders in the building life cycle to access and query required data to support their business use cases using web technologies. Its scope is then Web technologies as they may be applied to buildings (products, geometry, usage, topology). Infrastructure data (bridges, roads, railroads).
This document describes the results of the first steps of working towards this goal. Members of the Community Group and other stakeholders have come up with a number of use cases that describe how linked data can be used in the building life cycle. From these use cases, a number of requirements for further work are derived. In this document, use cases, requirements and their relationships are described. Requirements and use cases are also related to the deliverables of the Community Group.
The requirements described in this document will be the basis for development of the other deliverables of the Community Group.
The deliverables of this Community Group are described in the Community Group Charter. For convenience those deliverables are replicated in this chapter. The charter remains the authoritative source of the definition of deliverables.
A document setting out the range of problems that the Community Group is trying to solve (this document).
This will include:
The WG will work with the authors of existing simple building ontologies to complete the development of a new core building topology ontology through to Recommendation status. This ontology will serve as a small and easily extendable reference ontology for this WG. This ontology will immediately be aligned with the existing ontologies in the construction industry (ifcOWL), the geospatial domain (W3C Spatial Data on the Web Working Group), and the sensor domain (SSN).
The WG will work with the authors of existing building and product ontologies to complete the development of a new building product ontology through to Recommendation status. This ontology will serve as a small and easily extendable reference ontology for this WG. This ontology will immediately be aligned with the existing ontologies in the construction industry (ifcOWL).
The WG will work with the authors of existing building and product ontologies to complete the development of an ontology that can capture the properties and characteristics of building products and materials (fire resistance, heat transmittance values, ...). This ontology will be developed up to Recommendation status. This ontology will immediately be aligned with the existing ontologies in the construction industry (ifcOWL) and the sensor domain (SSN). Furthermore, it will aim to align with standardisation activities that occur in this direction in CEN/TC442 and in buildingSMART Data Dictionary (bSDD).
The WG will work with the authors of existing geometric modellers to capture 2D and 3D geometric representations of concepts and elements in buildings. In developing this ontology, strong collaboration is sought with the W3C Spatial Data on the Web Working Group, which has already built recommendations for representing geometry in the geospatial domain. Extensions will be developed to enable also the representation of 3D geometry in a well performing data standard. This ontology will be developed up to Recommendation status. This ontology will immediately be aligned with the existing ontologies in the construction industry (ifcOWL) and the geospatial domain (W3C Spatial Data on the Web Working Group).
The WG will work with the authors of the existing DogOnt ontology, SAREF ontology, and SSN ontology, so that a distinct and formal alignment with these ontologies is available from the BOT, PRODUCT, and/or PSET vocabularies. These alignments are completed through to Recommendation status. Further requirements already identified in the building data community will be taken into account.
The WG will work with the authors of the existing QUDT ontology and O&M model to complete the development of this ontology through to Recommendation status. The BOT ontology will be aligned to the QUDT - Units ontology and the OGC O&M - Observation and Measurements Ontology. Further requirements already identified in the building data community will be taken into account.
In order to find out the requirements for the deliverables of the Community Group, use cases were collected. For the purpose of the Community Group, a use case is a story that describes challenges with respect to linked building data for existing or envisaged information systems. It does not need to adhere to certain standardized format. Use cases are primarily used as a source of requirements, but a use case could be revisited near the time the work of the Community Group will reach completion, to demonstrate that it is now possible to make the use case work.
The Community Group has derived requirements from the collected use cases. A requirement is something that needs to be achieved by one or more deliverables and is phrased as a specification of functionality. Requirements can lead to one or more tests that can prove whether the requirement is met.
Care was taken to only derive requirements that are considered to in scope for the further work of the Community Group. The scope of the Community Group is determined by the charter. To help keeping the requirements in scope, the following questions were applied:
Use cases that describe current problems or future opportunities for Linked Building Data have been gathered as a first activity of the Community Group. They were mainly contributed by members of the Group, but there were also contributions from other interested parties. In this chapter these use cases are listed and identified. Each use case is related to one or more Community Group deliverables and to one or more requirements for future deliverables.
Kris McGlinn, Rob Brennan, Adapt, OSi.
Ordnace Survey Ireland (OSi) has a large data base of geospatial objects (buildings IDs, geolocation, polygons, form and function), including over 3.5 million buildings in the Rep. of Ireland. Roscommon Co Council collects/maintains similar data (usages, mainteance) about their buildings. This results in decentralized national data whereby the appropriate authorities maintain their own data sets. Adapt is working with both OSi and RosCoCo to support interlinking of these data sets, in particular around a set of published URIs provided by OSi for each building in Ireland.
Using LD each stakeholder maintains their own (sub-)dataset and the whole grows more comprehensive and interlinked with no need for duplication of effort. This use case can be further extended to include other data sets, including historic building data, and more advance 3D building models.
Nicolas BUS, CSTB.
CSTB needs to check buildings againts building regulation. The idea is to take an IFC file, execute a rule and return a BCF as result including the elements Ids that are not valid.
Sometimes, the element level is not accurate enough to express the result. The reason is that some part of the element can be valid, some other part not valid. Let's take the example of a corridor with multiple aisles. The corridor is modeled with only one Space but each aisle can have its own width. This way some aise can have a sufficient width while others can be not valid.
This idea is to be able to break an element into parts with their own geometry, to be able to identify each part and let's each part have their own properties.This use case address various deliverables.
Nicolas BUS, CSTB.
CSTB needs to check buildings models againts regulation. Each control point is written as a semanctic rule. Those control points can deal with objet properties, object relations and/or object geometry.
Whereas objects, properties, geometry and direct relation are explicit within the model, topological relations are most of the time implicit and need to be processed. For instance, we need to know if to spaces are adjacent and to get informations about the exchange surface (nature, surface). Thoses operations on geometry can be performed by some triplestore that integrate semantic topological functions such as those defined by the OGC (Open Geospatial Consortium) standards.
Here we have to find the right level of detail for this kind of operations. Too poors (such as bounding box) and the results are wrong, too accurate (BREP : Boundary representation with triangles) and the amount of calcutation turns far too heavy. The challenge would be to find the right kind of geometrical representation and minimum level of details we need to infer topological relations between models elements.
Nicolas BUS, CSTB.
CSTB needs to performs model checking against French building code. We assume that all the information needed is included in the building model. Thus we can apply queries or rules in order to check a specific control point.
In some cases it necessary to materialize requierements by creating specific object, with properties and geometry. For instance, the regulation say that accessible doors should be have enough free space in front of them to permit operation for people in wheelchair. The geometrical property of the free space are described too. In such a case it could be interesting to materialize this kind of free space to be able to infer on it.
In terms of ontology, we need to be able to create and identifiy an objet that is not part of the building but only materialize a requirement. The same need could be derived for requierment properties and the way to distinguish them from the inner properties.
Richard Pinkas, CTU Prague.
Distinguishing zones/rooms (areas/types of horizontal-vertical constructions, openings, zone volumes), their constructions areas facing to exterior, their common internal constructions areas, and sending these data to relevant computation (proprietary or open) software - ideal via API , or by simple exporting via file. Nice example has softwae PHPP (Pasiv Haus Institute) with plugin doing these connections within easy managable Sketchup (http://shop.passiv.de/literaturbestellung/index.php/en/product/view/1/1494 ). How could be this done within BIM models ? (in proprietary formats or on open formats)
Richard Pinkas, CTU Prague.
HVAC diagrams as easy description of concept of system intended to design is important informational document within discusions over the design phase, Building Authority acceptance phase, as well as in operation and service phase of HVAC system life cycle. It may be created in BIM softwre as first idea of system intended to design. Possibility to define it as system consisting from many parts (products or other subsystems (other products)) will give additional value to the quality of processes such : concept description, optimalisation, promotion. System design, system tendering, updating the changes or comparing the system with other diagrams from possible databbase of these schemas => possible way to error-check of HVAC system schema and avoiding design errors. Possible way to analyze actual trends in HVAC systems if adequate database will be built as time passes. Another utilization is to define BAS control requirements or define BAS control design documentation on it.
Richard Pinkas, CTU Prague.
It is reasonable to be able to ask about data property (data space) of specific product. Example given : You have found on web three types of heat-pumps on market. You want to use either heat pump which has performance data defined analytically - in polynoms, or heat pump which has performance data set on cube matrix. That means you will avoid selection of the heat-pumps with COP as "only one number" value. The answer of the data property query shall exactly define the character of the data and its volume-range. It is reasonable to count with possibility, that data may have even N-dimensional form comparing to easily understandable 3-dimensional form of data -> where can be on the first data connected other properties based on specific equations.
Anna Wagner, TU Darmstadt.
Within the research project "Solar Construction Processes" (SolConPro), the holistic integration of multi-functional facade components (such as energy active facades) is investigated. The developed approach includes the application of Semantic Web Technologies for describing complex product data. For further information on the research project and considered approach see http://www.solconpro.de .
Currently, descriptions of multi-functional facade components are exchanged in personal manner via telephone or mail. This is based on the absence of an exchange format allowing a dynamic and full description of such products. Therefore, manufacturers offer data sheets containing different information and naming of attributes for every product, impeding their application by non-experts. To facilitate planners in working with these products, a flexible and unified product description schema is necessary.
Multi-functional components present various challenges towards product descriptions. First, the products do not resemble only one product category, but can be considered as individuals of multiple categories (e.g. facade element, PV component, and window). Thereby, it must be possible to classify one component with different product categories. Second, the varying usage of innovative technologies cause products of the same category to hold diverging properties, requiring to drop template based approaches, as no singular template describing all products of such a category can be created. Third, as coherences between geometrical and non-geometrical information may occur, describing both within one schema allows an easier depiction of such relationships.
Georg Ferdinand Schneider, Fraunhofer IBP.
In the Architecture, Construction and Engineering (AEC) domain numerous formats exist to enable electronic exchange of data related to products stemming from the domain. For example the following non-exhaustive list has been gathered: FreeClassOWL, BauDataWeb, eClassOWL, UNSPSC, proficl@ss, omniclass, BAUKOM, PPBIM, VDI3805 and ISO757, CoClass (Sweden), ISO12006-2, NIST PDTO, NBS PDT, VVS Kataloget - National, Denmark, BNL - National, Netherlands.
From this heterogeneity a number of problems arise:
The technologies developed in the group help in overcoming some issues. Semantic Web technologies provide the means for semantic integration heterogeneous data formats. The to be developed product and properties ontologies form the basis for integrating the various formats.
Pouya Zangeneh, University of Toronto/Hatch ltd.
Large engineering projects require extensive public or private capital expenditures and other resources. They are also subjected to a variety of unique factors and therefore having different risk exposures. The current method of quantifying these risk exposures are quite subjective to fields, firms and even regions. The main way to increase objectivity is by trying to come up with objective statistical base rates for various aspects of these projects. The problem is that the data that is required to do so is often not available. Although many companies and governmental agencies report their data on their large engineering projects, there is not a broad consensus around definitions. This makes many of the research that is done on projects subjected to various biases and definitions within their data sets. Another problem is that this abundance of project data is usually in the form of reports and tables. These problems make this a unique use case area for promoting interoperability through semantic web. Uniform Project Ontology aims to unify the risk characteristics of these projects through the lens of capital investment.
Richard Pinka, CTU Prague.
Establishing the Allowances, rights or obligations and their continual recording. Because (not only according by Depeche Mode) people are people and they do mistakes and sometimes in some stage of building processes undesirabled events simply happens, leading also to trials which seek for responsibility.
Defining rights and obligations (before contract negotiation and during the work duties) for work with specific information (i.e. in design process) or acting in specific decision-making processes. Examples incude:
in the processes shall be possible to define such responsibilities, duties (no matter if in BIM model or in separate data storage), linkable to BIM model data and adjaced process and product data connected to building model and CAE-FM processes.
Name, Company.
MINES Saint-Étienne needs to share building topology and product data on the web as linked data. This is a simple use case that claim made purely for the benefit of providing an example use case. Thanks SDW members for the wording of these paragraphs. Provide external links for more info if you can, like data or slides.
This use case covers aspects of some of the Group deliverables that are listed below this description. Please do the same thing -- i.e. name the deliverables that clearly contribute to a solution to this use case and include "Unsure" if there may be other that you have not named but it is not clear to you whether you should have (and if you are not sure about any of them, "Unsure" alone is fine for now!).
The description of the use case may be only 3 or 4 paragraphs. Tell a story about how it will work (or how it works now and what you want to do better). Try to articulate the benefit of solving the problem (ideally, you will also describe the challenges you are facing now, but that might be asking too much).
This use case describe how to carry out (i) prediction of future electrical energy consumption and supply (ii) optimization of available resources such that operational costs and/or CO2 emissions can be minimized subject to the balancing of supply with demand
This use case is developed by the project Proficient. The project develops business opportunities for SMEs in the construction sector by exploiting the emerging process of Collective Self-Organised (CSO) housing for constructing and retrofitting energy-efficient residential districts. Part of this development will be a Semantic Web collaboration platform.
basic design of building, the design of the HVAC system, design of building automation system
operating phase of HVAC equipment under control of BEMS.
provide the user with a forecast of energy consumption and production on district level, during a user defined time interval. This forecast will be based of energy models implemented in DAREED Platform which will characterize the district to be simulated, real consumption data retrieved (when available) or theoretical consumption patterns and meteorological databases and predictions (when available).
This use case is from the project DAREED. It identifies the best solution practices to optimize energy profile for each building. It uses the Best Practices Catalogue to maximize the energy efficiency, according to the global needs of the building and considering the adoption or integration of renewable energy sources.
Integrated fault/unwanted behaviour detection. This use case provides a method for identifying and reporting faults or unwanted behaviour (e.g. too much heating), and provides access to information regarding potential replacement devices along with cost/benefit analysis. Faults in buildings can be difficult to detect and can often go unreported. Facility Managers must detect faults themselves, or rely on occupants to report faults, either by word (in person or through a reporting desk), by e-mail or by phone. This use case is concerned with providing capabilities for sensors to report faults, or where sensors are not present, support occupants to identify and report the location of a fault/unwanted behaviour in a building (3D floor plan) using a web browser on a mobile device, or desktop. This information is then presented to the FM, who can quickly locate, assess and if required address the issue. The FM is provided with tools to identify replacements, compare costs and control building set points.
Automatic monitoring of specific parameters to send alarm messages in case of any malfunction of the controlled building automation systems.
Provision of guidance, reporting templates, training materials and policy notes to support life cycle assessment (LCA) studies of energy efficient buildings and building products and help designing building LCA tools.
This use case is based on the hypothesis that more detailed knowledge of occupancy patterns can lead to energy savings through optimised pre-heating and pre-cooling. It requires; monitoring to be conducted of energy consumption, thermal comfort and occupancy as well as control algorithms for heating, cooling (e.g. shading) and ventilation systems.
Shopping malls and airport terminal buildings have visitor and passenger areas with variable occupant density. Currently the climate of these buildings is usually controlled by reactive temperature, CO2 and humidity sensors. This use case concerns the use of acoustic sensors in addition to the already installed sensory equipment within Building Management System (BMS) to measure the occupancy level and proactively control Heating, Ventilation, Air Conditioning and Lighting (HVACL) systems of real building environments in an attempt to reduce the energy consumption of these buildings.
This use case is concerned with the implementation of thermal energy. To achieve this is requires data related to the thermal envelope, weather changes, temperature, and the capability to predict and manage energy according the the changing thermal conditions.
Monitoring and observation of the energy consumption data and the regulation of temperatures and humidity in the dwellings.
A real-time occupancy level estimation is essential to provide real-time services for the occupants’ comfort but also to save energy by managing optimally HVAC and lighting systems. It can also provide fine-grain and realistic data about occupants’ behavior and occupancy patterns of zones for building models for offline simulations.
Customer and energy supplier may agree on a fixed amount of energy to be produced and consumed by a customer in a specified period of time.
This use case is based on the hypothesis that the combined knowledge about weather data and occupancy patterns can lead to energy savings through improved load balancing between (micro) generation sources linked to a single building and “back-up” systems consuming energy from supply grids; prioritising renewable energy sources. It requires; monitoring to be conducted of energy consumption, thermal comfort and occupancy, as well as access to building HVAC and energy produces/storage units.
Customer can specify energy consumption priorities of appliances, in the case of gird outage, or limited supply.
This use case is concerned with providing a virtual city which enables specification of user-needs, visualisation methods for decision support, metrics to evaluate urban energy systems, monitoring applications to be used in the operational phase of projects and the components of different elements, and the components of the different elements of the energy system to model.
employs combinatorial optimization technology to provide a policy maker with suggestions about which incentive schemes (and amounts) are more likely to achieve specific energy related goals (e.g. a reduction of the energy consumption).
This use case is based on the hypothesis that the availability of data from timetables, event schedules, calendars, energy tariffs, and access monitoring of parking facilities (incl. park & ride) will lead to improved control scenarios and load balancing between multiple sources for energy provision on campus level.s.
Provide measurement data of heating, water and electric energy to the tenants and the energy manager of the building and for the input to an energy trading marketplace, brokering system etc. and to calculate energy savings with the measured data.
This use case is developed by the project Design 4 Energy. The aim is to support an Integrated Evolutionary Design Methodology that allows the stakeholders to predict the current and future energy efficiency of buildings (both at individual level and neighbourhood level) and make better informed decision in optimising the energy performance at building life cycle level, including operation and maintenance.
Real time management and optimized control of HVAC systems of a building as a compromise between thermal comfort of the occupants and energy consumption. If a high level of thermal comfort is maintained at all times then energy cost will be high; and if energy consumption is minimised then thermal comfort has to be sacrificed.
This use case is concerned with maintaining user comfort through control of HVAC and lighting based upon knowledge of the building thermal envelope, technical systems, flexibility of systems, prediction of use, and controlled configuration for comfort.
Sustainable Energy Management is achieved through the development of an advanced energy management system for metro stations involving model based control of forced ventilation, lighting and passenger transfer systems.
District energy simulations performed by an accurate physical simulation toolbox, that enables to model a wide variety of buildings (with diverse size, materials, use and occupancy patterns, etc.) and contains a library of various component units of different capacities. By performing these physical simulations, different kinds of energy supply systems can be evaluated and finally chosen taking into account the relationship among performance of energy supply systems, available technologies and conditions of the considered district such as characteristics of energy demand, size and arrangement of buildings.
This use case is developed by the project eeEmbedded. The aim is to develop an open BIM-based holistic collaborative design and simulation platform, a related holistic design methodology, an energy system information model and an integrated information management framework for designing energy-efficient buildings and their optimal energetic embedding in the neighbourhood of surrounding buildings and energy systems. Similar use cases are described in the HOLISTEEC project.
a systematic way to plan maintenance related actions including basic finicalities like task and responsibilities assignation to people and time planning but also advanced functionalities like considerations on actions related energy savings, implementation costs and payback period calculation.
The main objective of HOLISTEEC is to design, develop, and demonstrate a BIM-based, on-the-cloud, collaborative building design software platform. The HOLISTEEC platform aims at providing advanced design support featuring multi-physical building performance simulation including energy, environment (gas emissions, etc.), acoustic, light, at building and neighbourhood levels, as well as multi-criteria design optimization.
María Poveda-Villalón (UPM), Gonçal Costa (LaSalle)
comission of HVAC system under control of the BEMS.
generate a series of set points for distributed generators and controllable consumption elements based on the results of the optimization of energy flow. The optimum will be calculated depending on consumers’ patterns, energy tariffs, estimated energy demand, distributed generation technical features, etc. The result will indicate whether is better to produce energy locally rather than purchase it from the grid, which is the best use for local energy storage elements or how should be the energy produce by distributed generation systems.
Kris McGlinn (TCD-ADAPT), Hendro Wicaksono (KIT-IMI)
This use case aims to provide the FM with suggestions on how to (re)configure building systems to reduce energy consumption. These suggestion are based on rules developed through data mining and predictive energy simulation. To achieve this use case an energy simulation is first created for the building (if not already developed during design). Parallel, data is gathered from all available sensor systems relevant to energy consumption. Data mining is conducted over the sensed data and a rule set is developed in conjunction with the predictive energy simulations (to account for incomplete data from sensors). Next, the dynamic sensor data is provided as parameters to a near-real time controller which based on the rule set, provides suggestions to the FM through a visualisation interface.
will provide consumers with the right information for them to be more capable of adapt their consumption patterns based on dynamic energy prices.
The Hit2Gap platform will provide data collection from various sources, and different applications that can handle those data for energy reduction purposes : fault detection and diagnosis (FDD), forecasting, modeling energy-related behavior of occupants, energy consumption simulation; visualization tools will also be available. The aggregation of these modules will support managers in monitoring their building and in a better understanding of their energy consumption.
María Poveda-Villalón (UPM), Hendro Wicaksono (KIT)
During the design of a building, parametrization of the Building Energy Management System (BEMS) occurs and feeds into the design of the building, HVAC and building automation systems (sensors, actuators). This design is then tested for performance during the commissioning stage to determine optimal configuration of BAS and BEMS. Continual commissioning occurs during operation, and building systems are re-configured for optimal performance based on historical data from sensors and BAS.
Sufficient prediction of the energy demand of the building
The customer that produces energy shall have a choice of the use of the energy in order to implement some defined strategy (e.g. maximize profit). Alternatives to selling depend on customer type and may include storing and/or consuming the energy by devices.
This use case is developed by the project STREAMER. .
Retrofitting of the building and the HVAC equipment and the parametrization of the BEMS.
This use case is concerned with optimization of energy use at certain times in the building by adapting the end-user behaviour to the capacity of energy production. The customer will accumulate bonuses/rewards (equating to money) by shifting their energy consuming behaviour. The electricity provider will provide a tool to help the customer manage their energy and better understand the breakdown of energy consuming devices.
Name, Company.
MINES Saint-Étienne needs to share building topology and product data on the web as linked data. This is a simple use case that claim made purely for the benefit of providing an example use case. Thanks SDW members for the wording of these paragraphs. Provide external links for more info if you can, like data or slides.
This use case covers aspects of some of the Group deliverables that are listed below this description. Please do the same thing -- i.e. name the deliverables that clearly contribute to a solution to this use case and include "Unsure" if there may be other that you have not named but it is not clear to you whether you should have (and if you are not sure about any of them, "Unsure" alone is fine for now!).
The description of the use case may be only 3 or 4 paragraphs. Tell a story about how it will work (or how it works now and what you want to do better). Try to articulate the benefit of solving the problem (ideally, you will also describe the challenges you are facing now, but that might be asking too much).
The list of proposed use cases is accessible in a separate document
This chapter lists the requirements for the deliverables of the Community Group, in alphabetical order.
In some requirements the expression 'recommended way' is used. This means that a single best way of doing something is sought. It does not say anything about the form this recommended way should have, or who should make the recommendation. A recommended way could be a formal recommendation or standard from an authoritative standards body like the W3C, but it could just as well be a more informal specification, as long as it is arguably the best way of doing something.
Occupancy schedules shall be possible to apply on each and every zone within building - in the case of need for HVAC design requirements (from investor/architect to HVAC engineer) and thus for HVAC systems design. Occupancy schedule shall have at least 24 values per each zone, where shall be possible to input numbers of persons utilized the zone in a) absolute values (persons) b) relative values (67,3 % of 253 persons) c) by probability of person occurence in zone ( 7AM - 35% chance that the zone will be occupied, 8AM - 38% chance ... 12AM - 78 %... 13AM - 100% ... etc.)
By this possibility, there can be offered wider area of building analysis for example for mentioned validation with the Building code. Another reason may be the analysis of possible epidemy sources within hospitals with high mortality or ilness infestation. Query for the data filtration may be e.g. "find each room where had been opened windows while ventilation system was off" , "find each waterpipes not smaller than DN35 with their distance smaller than 120 mm AND with both their distance from bearing vertical construction larger than 100 mm", etc.
Over design development, there are more design phases required to meet the Building code (at least in Czech Republic) : project is divided to possible four consequently joined agendas thus four specific documentations may be possibly required by Building authorities or other participants of building process (urban planning documentation, building permit documentation, realisation documentation, true state of building documentation). Many of building parts thus may not occur in each of the phase documentation or may have specific visual presentation. It shall be possible to specify the visual definition of the object.
Unwanted events in CAE/FM happens periodically. It often leads to the loss of the material/finances and human lives looses. There are many points over life-cycle of buildings, where an unwanted cause of troubles could begin. After such event it usually official investigation processes are on place, done by specialists due to a trial process. This circumstances are leading to the need of preparing the building data for:
Rights/obligations of (someone, something) to (do/dont do, have to do, must not do, be/not be, give/take) something, in the meaning of legal terminology Dare/Facere/Omittere/Pati
It should be possible to represent a zone and its sub-zones, inside and outside a building, potentially spanning multiple storeys.
This requirement needs clarification, is there a requirement for describing storeys?
The list of proposed requirements is accessible in a separate document
For convenience, this chapter lists requirements grouped by Working Group deliverable.
This section is generated automatically
The editors are grateful for all contributions made to this document. In particular we thank the people that have contributed use cases (their names are mentioned with each use case) and the Community Group members that helped in mining and refining the requirements.