Archive for the ‘IPAWS’ Category.

Twitter Weekly Updates for 2011-06-05

  • Funny: One of my neighbor's wireless networks is labeled "TS SCI NOFORN." #

Twitter Weekly Updates for 2011-05-22

  • sha256 certs in IPAWS-OPEN 2.0 working perfectly. Both for COG 999 and COG 100014 #

NIEM as Content Inside External Standards

I have been chosen to present a new twist on the reuse of data definitions at the National Information Exchange Model – National Training Event (NIEM NTE) in August. Data definition reuse questions that have been asked before include:
1. Is it OK to Use an External Standard without using NIEM?
2. How do I (or is it allowable to) encapsulate the use of an External Standard inside a NIEM conforming schema?
3. What is the best way to (or should I) bring concepts from external schemas into NIEM (to “NIEMify” them)?
These question have answers, although not everyone agrees on all of them.

My question is different. What if there was a way to reuse NIEM conforming structures inside an external standard? I plan to show an example of how it could work, using NIEM enumerated values (facets, codelists, and schema subsets if necessary) to populate EDXL-DE metadata around an IPAWS Profile CAP message and/or a NIEM IEPD for Amber alerting.

It ought to be an interesting discussion.

Twitter Weekly Updates for 2011-05-15

Twitter Weekly Updates for 2011-04-10

  • I never trust anyone who is more excited about success than about doing the thing they want to be successful at. http://xkcd.com/874/ #

IPAWS-OPEN Development MOA Holders

IPAWS has published the list of current MOA holders. This list is for development and does not indicate that any of them actually have a completed product. It does indicate interest, however, and a willingness to explore connectivity. See: http://www.fema.gov/emergency/ipaws/projects.shtm#3

Twitter Weekly Updates for 2011-04-03

  • Preparing for formal #IPAWS to CMSP testing today. Formal testing begins tomorrow. #CMAS #

FY2011 SAFECOM Guidance on Emergency Communications Grants

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!

IPAWS Announcement on the DM-OPEN Changeover to IPAWS-OPEN and the DMIS Tools Retirement from Service

Text of E-Mail released today:

The primary mission of FEMA’s Integrated Public Alerts and Warning System (IPAWS) program is to provide integrated services and capabilities to local, state, and federal authorities that enable them to alert and warn their respective communities via multiple communications methods. The federal mandate is to develop, deploy, and maintain the infrastructure for aggregating emergency messages originated by federal, state, local, and tribal officials and routing them to public dissemination systems including the Emergency Alert System (EAS), the Commercial Mobile Alert System (CMAS), and others. FEMA is committed to achieving this mission.

The IPAWS Open Platform for Emergency Networks (IPAWS-OPEN) will serve not only as the IPAWS Aggregator for Common Alerting Protocol (CAP) emergency messages, but also enable the interoperable exchange of other standards-compliant messaging between commercial systems. Currently, over 40 private sector companies are in various stages of developing and testing interoperable software applications compatible with IPAWS-OPEN. Many of these applications are expected to come to market over the next several months and further information about these products will be available from the Responder Knowledge Base (RKB) Website. In addition, FEMA is investigating a viable solution for an Open Source CAP authoring tool and will provide updates via the IPAWS Website.

IPAWS-OPEN will supersede the existing DM-OPEN which is scheduled for decommissioning on June 30, 2011. Concurrently, the Disaster Management Interoperability Services (DMIS) Toolset system will also be retired. All software currently connecting to the legacy DM-OPEN application must be migrated to IPAWS-OPEN 2.0 by June 30, 2011. After that time, legacy DM-OPEN will no longer be available and IPAWS-OPEN 2.0 must be utilized.

In order to focus more fully on its primary mission and make the most effective use of its resources, the IPAWS Program Office has recently completed a re-evaluation of its priorities. As a result, the decision has been made to cancel the release of the Framework incident management support tools originally planned to replace the DMIS Tools. A number of Web-based incident management systems are now widely available and emergency management practitioners are encouraged to assess their requirements and apply for grant funding assistance to meet their needs. For further information see the Interoperable Emergency Communications Grant Program (IECGP) or the Homeland Security Grant Program (HSGP).

We regret any inconvenience resulting from this decision. In the long-term, FEMA believes this is in the best interest of the public safety. For further information, please contact Mark Lucero at FEMA-DMIS@DHS.GOV

v/r
Mark A. Lucero
Chief, IPAWS Engineering
FEMA National Continuity Programs

Twitter Weekly Updates for 2011-02-27

  • New MacBook pro 15 in quad core I7 750 gig drive 1 Meg graphic high res screen. 8 gig memory. $$$ but worth it to me. #