Giving a talk on the ways to use CAP using the new IPAWS CAP 1.2 interface at noon tomorrow (15 Feb 2012). Details:
Integrated Public Alert and Warning System (IPAWS) Joint Developer/Practitioner Webinar
Using the Open Platform for Emergency Networks (OPEN) for Public and Private Alerting
Wednesday February 15, 2012 12:00 Noon Eastern
In addition to its role as message aggregator for public alerting, IPAWS-OPEN enables the interoperable sharing of emergency alerts and incident-related data between incident management systems that comply with non-proprietary information standards.
During our next Webinar, System Architect Gary Ham will describe how IPAWS-OPEN provides support for exchanging alerts within a single response organization, between one or more response organizations, with all response organizations, and/or with the public. He will also explain how the Common Alerting Protocol (CAP) scope element is implemented by IPAWS-OPEN for public and private alerting.
This program is intended primarily for IPAWS-OPEN developers and testers; however, emergency management practitioners who are interested in learning more about IPAWS incident management-related capabilities are also encouraged to participate. Please make plans to join us via Live Meeting. As always, your questions and comments are welcome.
IMPORTANT: The audio portion of the program will be delivered via your computer speakers. The Live Meeting client must be used in order to receive the audio. Please review the instructions available from: http://www.fema.gov/pdf/emergency/ipaws/livemtginstruct.pdf prior to the program.
Login to MS Live Meeting for visuals: The following login link can only be used 30 minutes prior to the scheduled meeting time: https://www.livemeeting.com/cc/eiip/join?id=DMprogram&role=attend
The new guidance is out. It includes Emergency Data Exchange Language (EDXL) Standards including the Common Alerting Protocol (CAP). This may be an option for agencies trying to buy an IPAWS connected alert origination tool. In order to actually connect to IPAWS, the tool must conform to CAP and the IPAWS profile of CAP in particular. See Section 5.3 on page 30 of the following document. Happy hunting!
I wrote a poller for DM-OPEN that posts alerts received in DM-OPEN to the prototype Unified Incident Command and Decision Support System (UICDS). This gives posters of Common Alerting Protocol (CAP) alerts the option of using DM-OPEN as a mechanism for also posting to UICDS for use by systems connected to that capability. Two successful demonstrations to date: a month or so ago at the Virginia Department of Emergency Management and today in McClean, Virginia for some folks from DHS. We posted alerts from NC4’s E-Team, CellCast’s Eagle, MyStateUSA, and DMIS Tools (also a DM offering) to UICDS where the alerts were provided to to a UICDS RSS feed and plotted on maps using Alert Sense (where proper locations were identified in the input CAP message).
The message: DM-OPEN can be a “connection multiplier” for its interoperability partners. In this case a single connection yielded 4 new partners (and possibly many more in the future).
Lee Tincher from Evolution Technologies is building some new open source connection code for DM-OPEN that adds to my previous test code. This addition will include database connection code for oracle and MySQL that will let developers retrieve Common Alerting Protocol (CAP) alerts from DM-OPEN and directly put them into a relational database for further processing. We plan to put the updated code up on the EM Forum site for others to use as desired. Cool stuff. Eventually we plan to add to this code so that it handles Emergency Data Exchange Language (EDXL) Distribution Element (DE), Resource Messaging (RM), and Hospital AVailability Exchange (HAVE). Emergency Managers every where – While I am of some assistance, Lee is doing real work that supports you! I am sure that he will appreciate your gratitude and support.