>> Someday maybe NBIMS standards will disappear and
not be expressed "... explicitly
>> since they are
fundamental to so many other applications and specifications that we
>> take them for
granted."
>>
>> RE: develop,
publish, advertise and maintain their own facilities-related Resource Lists
>> to use this
methodology and technique - is like a format or template for those tasks all
>> the way through the
process?
I know that from my perspective, that is the future of oBIX.
Without the higher abstractions, even most simple conversations are nonsensical
Security: “Secure this sensor” “Secure Contact
Closure 7” What would that mean? Compare to “Secure all sensors in
the Surgery Areas” “Restrict access to Operating Schedule for
Clinical Environmental Controls to…”
Operations: See above
IN 2005, when imagining the future abstractions that oBIX would
need, I reported that the next steps were
Functional Domain Services used by Owners, Operators, and
Tenants
n
WS-Buildings HVAC (based on GPC 20)
n
WS-Buildings Power
n
WS-Buildings Access Control
n
WS-Buildings Intrusion Detection
n
WS-Buildings CCTV
n
WS-Buildings Occupancy
And the cross-cutting
Analytics and Cross-Domain Abstractions
n
WS-Buildings Performance (M&V, commissioning)
n
WS-Buildings Analytics
n
WS-Buildings Tenant Services
Not sure this aligns with BSP today, but it is similar to what
you are describing…
tc
"A man should never be ashamed to own that he has been in
the wrong, which is but saying ... that he is wiser today than yesterday."
-- Jonathan Swift
|
Toby Considine
Chair, OASIS oBIX TC
Facilities Technology Office
University of North Carolina
Chapel Hill, NC
|
|
Email: Toby.Considine@
unc.edu
Phone: (919)962-9073
http://www.oasis-open.org
blog: www.NewDaedalus.com
|
From: bsp-forum-bounces@xxxxxxxxxxxxxxxx
[mailto:bsp-forum-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Deborah
MacPherson
Sent: Thursday, October 09, 2008 9:13 AM
To: Rex Brooks
Cc: BSP Forum; ibcomm@xxxxxxx
Subject: Re: [bsp-forum] Great Workshop, some questions and comments
Hi All,
Thanks for your responses, it will take some time to wade
through them but no time like the present. Especially I need to look hard at
this Umbel configuration and learn more about it.
In regards to the health workshop, next years CSI
Mid-Atlantic Regional Conference will be in Charlottesville VA and one of the
construction tours is a new hospital cancer center. The spaces are specially
designed to meet health and spiritual requirements that are atypical of
hospital design. Of course hospitals have TONS of equipment, like sensors, not
only for indoor air quality but literally people's health. Maybe that architect
could participate in the workshop.
Someday maybe NBIMS standards will disappear and not be expressed "... explicitly since they are fundamental to so many
other applications and specifications that we take them for granted."
RE: develop, publish,
advertise and maintain their own facilities-related Resource Lists to use this
methodology and technique - is like a format or template for those tasks all
the way through the process?
On Wed, Oct 8, 2008 at 4:18 PM, Rex Brooks <rexb@xxxxxxxxxxxxxx> wrote:
Hi Deborah,
I am copying David Coggeshall, of Golden Gate Safety Network, who gave the
presentation on the Common Operating Picture (COP). I am also copying the BSP
list so that that group is also aware of this.
I think Michelle is probably better suited to address many of your questions
related to BIM and NBIMS. However, I can say that OASIS does not, as far as I
know, have a specific formal, legal, liaison relationship with ISO, but it has
collaborated with ITU and ISO in the past. ITU adopted an ASN.1 representation
of the Common Alerting Protocol (CAP)1.1 that I worked on more than a year ago,
and I believe it was in 2004 that ISO adopted 5 ebXML specifications developed
by OASIS with UNCEFACT:
* ISO 15000-1: ebXML Collaborative Partner Profile Agreement
* ISO 15000-2: ebXML Messaging Service Specification
* ISO 15000-3: ebXML Registry Information Model
* ISO 15000-4: ebXML Registry Services Specification
* ISO 15000-5: ebXML Core Components Technical Specification,
Version 2.01.
Our SOA Registry Repository usesthe Registry Information Model and Registry
Services Specifications and some of the others though not explicitly since they
are fundamental to so many other applications and specifications that we take
them for granted.
I am probably going to suggest several people and groups to help organize or
take the lead in helping Susan with developing an Emergency Healthcare Workshop
and perhaps an Emergency Standards Workshop. The ValueListURN-Value pair
concept I mentioned a couple of times yesterday is part of the EDXL Family and
an educational-socialization effort is needed to stimulate local jurisidictions
and EOCs to develop, publish, advertise and maintain their own
facilities-related Resource Lists to use this methodology and technique, which
is rather well suited for BIM, NBIMS and Sensor-OGC interests.
I learned enough with this effort, that even with four months advance work
(despite the interruption of a hernia and hernia repair surgery), putting this
kind of effort together needs a bit more of a team. Of course the coincidence
of having the NIST workshop next week along with the OPEN SIG presentation is
not likely to be duplicated. However, the annual NIST Interoperability Week in
March-April is another such potential coincidence-target, as are the regular
Semantic Interoperability and SOA for E-Government Conferences.
The time to start work on these efforts is soon, before the Thanksgiving-Xmas
period. Coordinating this effort with the Open Ontology Repository work is
something both Michelle and I have an interest in continuing.
Cheers,
Rex
At 2:30 PM -0400 10/8/08, Deborah MacPherson wrote:
Dear Rex, Michelle, and Peter,
I am honored to have participated in yesterday's workshop. I learned a lot,
some activities are further along than I thought and some interface with the
ways buildings are designed and actually work seem to be completely missing.
For example I'm surprised the only comment on buildings by DHS was that
"they have inside spaces". On the up side, the strong tie that
already exists between NBIMS and OGC is sure to be a benefit in the long run.
I had a talk with Greg Ceton Technical Program Manager at CSI this morning.
Basically, ISO standards (and European Standards for that matter) and the NBIMS
Standard are not alike, mainly because their organizations have more staff, so
there are more forms and procedures, they look for trends etc. NBIMS is much
simpler than this. I'm trying to understand relationships between standards
organizations, can someone please explain the relationship between ISO and
OASIS if any direct relationship exists?
Its hard to say what I liked the best in the slide shows.
-Certainly the concept of Common Operating Picture is very appealing. I'd
like to see the same for museums exchanging artworks in different exhibits over
time.
- The Scalable Architecture presentation was great especially SuperCuper
Prototype where the XML is far in the background without the user having to
fill out information that is probably already known simply by working with this
type of data or question. Also interested in the comment from SourceForge that
"all messages contain some elements of these major categories."
- Its very exciting to see demonstrations in Google Earth. I truly
believe OCCS Table 11 could be used to color GIS symbology a standard way by
building type to help clarify the common operating picture even more. I
proposed 10 standardized colors for BSP, maybe we can talk about these again. I
sent a message with this same suggestion about Table 11 and colors to Charles
McLean earlier today (in response to what seemed to be a sincere request for
suggestions) along with another suggestion RE: the pros and cons of Fire
Control Rooms.
- I also particularly like the People, Places, Things, Events and think these
could be tied to building data fairly easily through special relationships
between OmniClass tables.
- Once the information is exposed real time on Google Earth, is there a reason
it would not be available to people in that area whether on their computers or
on their cell phones so they know where to go? Is it currently possible to
limit what is shown to a geographic area, in other words only people within a
certain distance could receive the common picture? That way some terrorist or bank
robber is not sitting miles away watching their disruption from a safe
distance?
-I liked the symbols Michelle was proposing and the rapid assessment and reuse
of a building (EX: a warehouse is converted into a temporary hospital then all
the ambulances get re-routed there.) OPS is perfect for this.
-Also, the ability to terminate a request once it is met makes a lot of sense
(EX: stop sending cots to this location, send them to this other place
instead).
I'll look at the NIMS Resource Typing and Daisy.org to see if there is anything
useful for architects or NBIMS there. If you have recommendations on Swarms or
Smart Swarm Agents I'm curious to know more about that some day.
I started a page for collaborative editing or wishlists if a discussion could
get going
<http://colab.cim3.net/cgi-bin/wiki.pl?NBIMSinContext>http://colab.cim3.net/cgi-bin/wiki.pl?NBIMSinContext.
Finally, I've been looking at the Umbel Ontology and based upon Peters comment
to "ground any domain ontology into a foundation/upper" I'll see if I
can get my classifications and standards to fit in that. That would be a great
leap forward because of the convenient shape Umbel has. I'll also go back to
hear their talk from the other week. If you have any advise on how to start
that process please let me know.
Thanks again,
Deborah
--
*************************************************
Deborah L. MacPherson CSI CCS, AIA
Projects Director, Accuracy&Aesthetics
Specifier, WDG Architecture PLLC
The content of this email may contain private
and confidential information. Do not forward,
copy, share, or otherwise distribute without
explicit written permission from all
correspondents.
**************************************************
--
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670
--
*************************************************
Deborah L. MacPherson CSI CCS, AIA
Projects Director, Accuracy&Aesthetics
Specifier, WDG Architecture PLLC
**************************************************
|
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/bsp-forum/
Subscribe: mailto:bsp-forum-join@xxxxxxxxxxxxxxxx
Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/bsp-forum/
Shared Files: http://ontolog.cim3.net/file/work/BSP/
Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?BuildingServicePerformance (01)
|