OS agnostic is a good way to put it. Useful BSP products could be 2 sample specifications: One in MF2004 for new building projects. Then in the spirit of NBIMS technology neutral for the exchanges: from XML all the way to the representation of relationships in UMBEL or similar framework. ~ Deborah
On Sat, Oct 18, 2008 at 10:48 AM, Considine, Toby (Campus Services IT) <Toby.Considine@xxxxxxx> wrote:
This is actually very relevant the BSP.
If the complete process is specified, there is no responsibility
for the results, or service. It does not matter at all how the screws are
threaded if the gizmo does not work.
Yet, we do not know how to specify the service.
As far as specifying the operating system, there are two components
to this.
-
If the system is going to be internet connected, it had better
be an operating system that the internal staff of the building know how to
patch and secure. Unpatched Linux is not a better decision than unpatched
windows.
-
I often specify a version of windows because so many gizmos are
so badly written, and the focus of the contractor is so cheap, that I get "networked"
systems based upon windows 95 or windows 98, even in this day and age. I often
specify that it must be at least version xxx, must support patching by
management policy under domain control, etc, because I need to manage these
control systems just as I do all others in the building.
If we ever define the services, and thereby are able to defined
the communications patterns including security interactions, then, and only
then, can we afford to become OS agnostic…These are not components of a
stand-alone disconnected building, these are components of the internet of
things, and thus part of the larger internet.
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
Hi Rex and Toby -
Thanks for the messages. Michelle and I communicated off
list, my main concern was that the PMI was an achievable work result which has
been confirmed - thanks!
The specification came from an MEP engineer, fairly
consistent with their other sections so it was probably based on the
manufacturers originally then modified to work with the rest of the project. It
is impressive how far along these systems, including BCS, have come even in the
last couple years. I am an A201 purist meaning all the documents address
only the Owner, Architect, and Contractor. Subcontractors and Engineers are not
separate entities, my only beef with the new and improved systems is our engineers
have a tendency to use the spec to divide the work by talking too much about
what the plumbing contractor does, what electrical does, what the BCS supplier
does. The selection of course requires expertise, but the in-field
implementation is probably a bumpy road but if there has ever been a need for
one general contractor to be responsible for whole systems, digital-addressable
fire alarms and BCS are them.
Some time at your convenience, could some one provide a
simple explanation of BACnet and how the building systems actually link up to
communication networks outside the building? What is achievable / realistic
expectations for project specifications today vs goals for the future
especially in regards to OBIX and ED XML? Is it just an old habit for
construction documents to call for "Microsoft Windows based" in this
day and age?
Hope the Silver Sentinel
exercise goes well. I met Chuck
McLean and Guillaume Radde at the Oct 7 Expedition Workshop and am scheduled to
talk with Chuck McLean about standardizing the GIS symbology/colors for
building types and the pros and cons of the fire control room (also called fire
command center). For example, I think this space or, panel location if there is
not a space, should be consistently numbered. There is not a good match in OCCS Table
13 Spaces by Function. The closest are 13 81 31 21 99 Other
Information Signal Distribution Spaces or 13 81 21 24 Telecommunications Room
but neither of those are correct. Any way he said he was traveling -
evidently your way. It *IS* a small world after all.
On Fri, Oct 17, 2008 at 11:59 PM, Rex Brooks <rexb@xxxxxxxxxxxxxx> wrote:
Hi Deborah, Michelle, Everyone,
Sorry I didn't get back to this sooner, but as Michelle knows, we had
a ton of work getting ready for Wednesday's
presentation-demonstration to the DM OPEN SIG from the NIST workshop.
It went very well, but fatigue caught up with me. I should be back in
the saddle over the weekend, and I will review all the developments
and get back to work. I think the last two weeks were excellent, and
the challenge now is to convert the discussions and new connections
into further action. Chuck McLean and Guillaume Radde from the NIST
Manufacturing Modeling Simulation group will be in town for the
October 23rd Silver Sentinel exercise and I will be meeting with
Chuck after next week's IRSC meeting. I will send an invitation to
the BSP list for that meeting because momentum and convergence needs
follow up.
Have a great weekend,
Rex
At 4:06 PM -0400 10/15/08, Deborah MacPherson wrote:
>Hi Michelle and Rex,
>
>I'm reviewing a digital addressable fire-alarm system for a hotel.
>The paragraph below caught my attention and wanted to pass along to
>you see if this is realistic or achievable. It makes me now worried
>about the Building Control System requirements too. Typically I only
>review for conflicts with the contract and similar but I couldn't
>help notice this perhaps unachievable result.
>
>Any expertise or comments would be sincerely appreciated.
>
>Thanks - Deborah
>
>The Person Machine Interface (PMI) or the Remote Person Machine
>Interface annunciator (PMI REM) shall provide the system information
>on six inch 1/4 VGA monochrome LCD, with Touch Screen and LED
>display. The PMI shall provide floor plans with alarm type and
"You
>Are Here" indication. The PMI shall be navigable by
device/module
>custom message in the system architecture with no need for device
>address knowledge. The PMI shall provide a physical as well as a
>system graphic view. Graphic user interface shall be menu driven
>with 4 tabs showing the level and the total events for each tab. The
>tabs shall be; Alarm, Supervisory, Trouble, and Security. Each
>level shall show 5 events simultaneously. The LED displays shall
>indicate Power, Audibles On or Silenced, and Partial system
>disabled. Systems not having the above LEDS shall provide separate
>LED's within the control panel enclosure with appropriate labels.
> Selection buttons shall be backlit to aid the operator in the
>selection process. There shall be controls for scrolling throughout
>the event list. A button shall provide zoom in and zoom out for the
>amount of information desired for a specific entry. The PMI shall
>be capable of monitoring the power supply loading and show available
>capacity for future expansion planning. The PMI LCD shall provide
>standard NFPA symbols showing Fire Service Equipment, Hazards
>compliant with NFPA 170 and People in the area of alarm. Systems
>without this type of display shall supply a UL listed Graphics
>package with their system. The LCD shall have a keyboard screen to
>allow the technician ability to enter test and numbers for passwords
>or text changes. The module shall be model number PMI.
>
>Acceptable Manufacturers listed are: Seimens Building Technologies
>(Branch Office Only); Simplex; Edwards System Technologies Inc.; and
>Notifier.
>
>--
>*************************************************
>Deborah L. MacPherson CSI CCS, AIA
>Projects Director, Accuracy&Aesthetics
>Specifier, WDG Architecture PLLC
>
>**************************************************
>
>
>
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 PLL
**************************************************
_________________________________________________________________
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
-- ************************************************* 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)
|