[Top] [All Lists]

Re: [ontolog-forum] International Alliance for Interoperability

To: "[ontolog-forum] " <ontolog-forum@xxxxxxxxxxxxxxxx>
Cc: Toby Considine <Toby.Considine@xxxxxxxxx>
From: "MacPherson, Deborah" <dmacpherson@xxxxxxxxxxxxxxxx>
Date: Fri, 13 Mar 2009 10:08:12 -0400
Message-id: <43F2A07F08761449ABD2C0664C74D9FC07ACB752E6@xxxxxxxxxxxxxxxxxxxxxxx>

What is missing between BIM and OGC standards to the STEP and 15926 world are the metrics. Which subject matters are worth trying to reason over at such large scales? Take for example Toby's Healthy Office Building Index - office buildings can be classified by use group, construction type, leasable space definition rules, and other descriptions people concerned with office buildings regularly use. The work in those offices could vary from the most brilliant advancements to the most mundane tasks, any amount of money could be flowing through. Whatever work is being done and regardless of the building design, any person working in any office performs better with x amount of light, the minimum requirements are in the building codes; and y indoor air quality, which can be monitored via ASHRAE standards, BACnet, NIST traceability, the Owner may have their own standards, and a long list of other factors dependent on building geometry and the outside surrounding area to measure something, even perhaps from a 15926 utility point of view. A Healthy Office Building Index needs to be able to talk to both sides by taking all of these measurements, values, properties, environmental factors, and questions being asked of the building data into a hodgepodge group to determine new, more combined classifications and ranking criteria in a common index. To be useful, these calculations or semi-automated assessments need to be able to spit out a cost per square foot or other unit price to attach to the building, utility, and regional data over time. That way an Owner or manufacturer doing business in OmniClass, 16739 IFCs, building codes and their preferred standards could negotiate with larger more complex systems like utilities using a different set of standards. An ontology is needed to build this particular bridge from ISO 16739 and 12006 to 15926 and 10303.  Such an ontology should be geared to developing appropriate metrics for price negotiations first - one of few reasons there is any need to communicate across this void in the first place. In the future, organizations like Exxon or the Coast Guard could bounce back and forth between the two types of standards to get their buildings consistently represented in BIM and comply with geographic standards which traditionally have been separated or different than the work performed in these buildings.



From: ontolog-forum-bounces@xxxxxxxxxxxxxxxx [mailto:ontolog-forum-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Deborah MacPherson
Sent: Friday, March 13, 2009 6:58 AM
To: [ontolog-forum]
Subject: [BULK] Re: [ontolog-forum] International Alliance for Interoperability
Importance: Low


Thank you Matthew, this is extremely helpful. So, in the context of building information models:

If a building is a processing plant, 15926 would be necessary to link the spaces and layout to processing activities. Especially because plants don't always have typical floors and can be like a big machine, you just need to see if a person can get through all the pipes and catwalks to service components 15926 would know about.

If the building is an airport, 10303 would be useful to see if there is enough space for the shapes, sizes, and servicing needs of airplanes, if a military base, then submarines. Any product that benefits from 10303 that is housed or moved around from building to building some day may utilize BIM and OGC standards to compare building features and the distances between locations to determine which buildings or locations are the best fit for a set of requirements.

Some day any dumb office building with square simple geometry and a completely typical purpose could plug and play with smarter, more complex utility grids as Toby Considine states. For this to be consistent across the spectrum of every kind of building and utility service, it would help to use the 15926 reference library and integration features as a translator, or normalizer to level the playing field.

Lots of buildings together change over time, since buildings vary so much both geometrically and in their function, they will never be as modular as lego blocks or data. To monitor and improve sustainability maybe EXPRESS, STEP, 15926 and other logical standards can help see bigger pictures. 



On Fri, Mar 13, 2009 at 5:32 AM, Matthew West <dr.matthew.west@xxxxxxxxx> wrote:

Dear Deborah,

Let me see if I can shed a little light for you.

> Thanks Matthew, I have never been clear on the relationships between
> 15926, EXPRESS, STEP and the ways these can work together. Is there an
> overview on this somewhere to help the building information community
> understand more about the standards governing larger systems that come
> into buildings, for example utilities?

[MW] There are descriptions of each of these individually, not least in the
standards that embody them, but a brief over view is possible.


EXPRESS (ISO 10303-11) is a data modelling language. In fact it was the
first such to become an ISO standard. It has very similar capabilities to
UML static models, or indeed any other data modelling language, and indeed
frame based or Description logics. One of its main distinguishing features
is that whilst most data modelling languages are graphical in nature,
EXPRESS has both a graphical and lexical form (like OWL). EXPRESS is a
pre-XML language, and the lexical form is easily human readable as well as
computer interpretable. Both STEP and ISO 15926 data models were originally
developed using EXPRESS.

STEP - Standard for the Exchange of Product model data

STEP usually refers to ISO 10303, but is not the formal name for the
standard, and is also sometimes used to refer to the whole family of ISO
TC184/SC4 standards, including ISO 15926. The key components of ISO 10303
are Application Protocols. These are data models that are exchange standards
for particular interfaces for particular industries. The focus in STEP is on
the exchange of geometric data about products (generally complex ones like
submarines, planes, buildings etc). Some 40 such Application Protocols (AP)
have been developed. As time went on, people wanted to use these APs
together, and found they were not compatible. Since the mid '90s work has
gone on to restructure the APs so that they are constructed out of common
"modules" so that making an SP is now rather more like building out of Lego
blocks. The price is that configuration management is a significant issue.

ISO 15926

The process industries, including the oil industry, arrived on the scene in
the early nineties with a data integration requirement rather than a data
exchange requirement, and where it was already clear that STEP did not
support "plug-and-play" but was a long way from a modular design. ISO 15926
consists principally of an integration data model (ISO 15926-2) and a
Reference Data Library (Part 4) that together provide an integration
environment into which data from different sources and different data models
can be translated and integrated.


Matthew West
Information  Junction
Tel: +44 560 302 3685
Mobile: +44 750 3385279

This email originates from Information Junction Ltd. Registered in England
and Wales No. 6632177.
Registered office: 2 Brookside, Meadow Way, Letchworth Garden City,
Hertfordshire, SG6 3JE.


Deborah L. MacPherson CSI CCS, AIA
Specifications and Research Cannon Design
Projects Director, Accuracy&Aesthetics


Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/  
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/  
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/ 
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx    (01)

<Prev in Thread] Current Thread [Next in Thread>