Re: [emergency] FW: [dm-open-sig] HazCollect API

[Rex Brooks <rexb@starbourne.com>]

Thanks, Gary,

Appreciated.

Cheers,
Rex

At 4:26 PM -0500 11/1/06, Ham, Gary A wrote:
>Info on HazCollect that may have missed some on the list.
>
>Gary A. Ham
>Senior Research Scientist
>Battelle Memorial Institute
>540-288-5611 (office)
>703-869-6241 (cell)
>"You would be surprised what you can accomplish when you do not care 
>who gets the credit." - Harry S. Truman
>
>
>
>From: OPEN SIG Discussion List [mailto:dm-open-sig@list.dmi-services.org]
>Sent: Friday, October 27, 2006 8:55 AM
>To: Ham, Gary A
>Cc: Schmidt, Bernard
>Subject: [dm-open-sig] HazCollect API
>
>[Replies to this message go the list. If you wish to reply to the 
>author only, please change the address]
>---
>A question was raised on the dmis-sig list as to when independent 
>Incident Management Programs could have access to the HazCollect 
>Non-weather Emergency Management API.
>
>That API has been available for several weeks in the DM-OPEN 
>INTEROPDEV environment (the external development development 
>interface for members of the Disaster Management - Open Platform for 
>Emergency Networks). This allows independent programs to develop 
>access and GUI capabilities prior the time that the NWS actually 
>approves folks for operational interface.  We expect to provide 
>operational connectivity to independent systems at roughly the same 
>time that the NWS officially "turns on" production capability.
>
>For more information on DM-OPEN please go to 
><http://www.emforum.org/open>www.emforum.org/open
>
>There you may sign up for the DM-OPEN SIG (a resource for developers 
>of independent systems).  There is also a downloads section that 
>includes a FAQ (best starting place) and a developers manual that is 
>specific to the HazCollect API.  Please note that this downloads 
>section is a temporary repository for draft documents.  A new 
>DM-OPEN "official" web site is in development.
>
>One caveat: The fact that the physical ability to develop to the API 
>is now in place and that the capability to achieve production 
>connectivity will be in place very soon (roughly December is a 
>personal guess), does not provide automatic AUTHORITY to post to NWS 
>through the API.  That authority must be specifically granted to 
>each separate DM COG by the NWS.  This process has yet to be 
>officially released by the Weather Service, but should be the same 
>regardless of whether the COG is a DMIS tools COG or an independent 
>software COG.
>
>Please call or e-mail with your questions.
>
>Respectfully,
>
>
>Gary A. Ham
>Battelle Memorial Institute
>External Systems Interoperability Coordinator
>Open Platform for Emergency Networks
>Disaster Management e-Gov Initiative
>Office for Interoperability and Compatibility
>Science and Technology
>Department of Homeland Security
>540-288-5611 (office)
>703-869-6241 (cell)
>"You would be surprised what you can accomplish when you do not care 
>who gets the credit." - Harry S. Truman
>
>
>From: Eyestone, Scott M
>Sent: Friday, October 27, 2006 7:59 AM
>To: Ham, Gary A
>Subject: FW: [dmis-sig] RE: DMIS v2.3.3 Release Announcement
>
>This one's in your yard .. . .
>
>
>From: DMIS SIG Discussion List [mailto:dmis-sig@list.dmi-services.org]
>Sent: Thursday, October 26, 2006 6:40 PM
>To: Eyestone, Scott M
>Subject: [dmis-sig] RE: DMIS v2.3.3 Release Announcement
>
>[Replies to this message go the list. If you wish to reply to the 
>author only, please change the address]
>---
>Is there an estimated date as to when the API (Associated Program 
>Interface) will be ready for use by independent Incident Management 
>programs to access HazCollect directly through OPEN?
>
>Gary Timm, Broadcast Chair
>Wisconsin EAS Committee
>


-- 
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-849-2309