My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
US Dept of Homeland Security FEMA 8/28/2020
>
Contracts
>
Agreement
>
Interlocal Agreements
>
US Dept of Homeland Security FEMA 8/28/2020
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/26/2024 7:10:17 AM
Creation date
12/2/2020 12:34:37 PM
Metadata
Fields
Template:
Contracts
Contractor's Name
US Dept of Homeland Security FEMA
Approval Date
8/28/2020
Council Approval Date
8/12/2020
Department
Fire
Department Project Manager
Sarah LaVelle
Subject / Project Title
IPAWS Program
Tracking Number
0002540
Total Compensation
$0.00
Contract Type
Agreement
Contract Subtype
Interlocal Agreements
Retention Period
6 Years Then Destroy
Imported from EPIC
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
13
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
FOR OFFICIAL USE ONLY//CONTROLLED UNCLASSIFIED INFORMATION <br /> • Provide physical security and system environmental safeguards for devices supporting system interoperability <br /> with IPAWS-OPEN. <br /> • Ensure physical and logical access to the respective systems as well as knowledge of the COGID and associated <br /> access criteria are only granted to properly vetted and approved entities or individuals. <br /> • Where applicable,ensure that only individuals who have successfully completed FEMA-required training can <br /> utilize the interoperable systems to issue alerts and warnings intended for distribution to the public. <br /> • Where applicable,document and maintain records of successful completion of FEMA-required training and <br /> produce such documentation in response to official inquiries and/or requests. <br /> 8.0 PROFICIENCY DEMONSTRATION <br /> Once enabled,each COG operating under this agreement must demonstrate their ability to compose and send a <br /> message through the IPAWS-OPEN system at regular intervals.Such demonstration must be performed on a monthly <br /> basis through generation of a message successfully sent through the IPAWS-OPEN Training and Demonstration <br /> environment. <br /> 9.0 ASSOCIATED SOFTWARE REQUIREMENTS <br /> The COG will need to select a software package which will allow the COG to properly populate a Common Alerting <br /> Protocol(CAP)message which complies with both the OASIS Common Alerting Protocol Version 1.2 and the OASIS <br /> Common Alerting Protocol,v. 1.2 USA Integrated Public Alert and Warning System Profile Version 1.0.With respect <br /> to the software and the software vendor selected FEMA expects the selected software to provide the following <br /> minimum critical capabilities and services: <br /> • Permissions: <br /> o The ability to assign and manage user permissions;and <br /> o The ability to retrieve and view IPAWS Alerting Permissions <br /> • Proficiency: <br /> o The provision of vendor support,to include user training,and around the clock technical support; <br /> and <br /> o The ability to submit both live and test digital certificates,with clear,easily identifiable information <br /> that indicates the environment to which the software is pointed(Live or Test) <br /> • User Interface: <br /> o The provision of an intuitive user interface,to include help menus;and <br /> o The ability to notify the user of digital certificate expiration;and <br /> o The ability to constrain event types and geocodes to user permissions;and <br /> o The ability to send one alert to multiple channels;and <br /> o The provision of displays that show required fields based on selected channel;and <br /> o The ability to pre-populate fields to the greatest extent possible;and <br /> o The ability to support templates;and <br /> o The ability to create a polygon or circle,of less than 100 nodes;and <br /> o The ability to update or cancel an alert,without having to reenter all of the data;and <br /> o The ability to alert the end user if a software license has expired;and <br /> o Clear explanations if alert information is case sensitive when entered <br /> • Confirmation and Error Checking: <br /> o The ability to pre-check an alert message for errors,prior to sending;and <br /> o The ability to create free-form 90-character WEA text,while preventing prohibited characters;and <br /> 4 <br /> V4.2,June 20,2019 <br />
The URL can be used to link to this page
Your browser does not support the video tag.