What Gates are Involved in Developing Applications that use IPAWS?
A recent question from a Commercial Developer:
If I was a public safety or transit organization and wanted to connect to the IPAWS-OPEN for Alert origination and/or dissemination, what administrative (legal, financial, etc.) and technical (information assurance, qualification, etc.) gates would I have to pass?
The answer from the IPAWS Program Office Lead Engineer:
Administrative gates:
1) An MOA is required to connect to our Test Development Lab (TDL) where you can develop interfaces to our system and consume alerts for rebroadcast. The MOA process begins here (http://www.fema.gov/pdf/emergency/ipaws/moa_ipaws_open_app.pdf)
2) Once you have completed your development and have a working system, a separate MOA is required to consume alerts in the Production environment
3) There are no financial obligations by either partyTechnical gates:
1) The method you will used to access FEMA systems to consume alerts is through https
2) The MOA contains a rules of behavior that will cover security at a high level
3) The IPAWS Program does not qualify or certify systems but there are a few options for you:
a. First, we have a lab at Indian Head, MD with several alert and warning tools that work with IPAWS. We use this lab to understand the state of the industry for alert and warning. We would welcome you to bring your capability to this lab.
b. Second, the Preparedness Technology Analysis and Coordination Center (P-TAC) performs testing and assessment of emergency management tools. This may be an appropriate avenue for you to have your solution analyzed for suitability for emergency management applications.”
Further Questions? I can help you get started.
