wiki:UserGuidelines/SAMBRO

Version 127 (modified by Biplov Bhandari, 5 years ago) ( diff )

--

SAMBRO Guide

Purpose

The user guide provides a set of step-by-step instructions from installing, customizing, and operationaizing SAMBRO software to issue and manage alerts. It is intended for all user levels: novices to experts. The guide is structured to take you through an actual implementation with real world examples and data.

How to use the Guide

The user guide is designed to quickly access relevant information for performing a user's role specific task. The topics are ordered such as that the most frequently used activities are listed first, like subscribing to alerts, and the seldom used, one time Admin type activities, are listed at the bottom. We have segmented the role specific work flow topics. If you are a particular user searching for a topic, first navigate to the type of user you are and then select the work flow activity:

  1. How to receive alerts? Steps for first registering in SAMBRO as a Subscriber (Closed User Group; e.g. first-responder) to receive location, event type, and warning priority specific messages as well as public alerts
  2. How to create, authorize, and disseminate alerts? Instructions for Alerting Authorities for managing the process of issuing alerts to Closed User Groups (CUGs) and the Public
  3. How to implement SAMBRO for your alerting needs? For Super Users to define the user roles/responsibilities, message qualifiers, message templates, first-responder groups, and standard operating procedures.
  4. How to install and operationalize SAMBRO software? Guides a Systems Administrator through installation and customization process to get SAMBRO up and running.

Role Specific Topics

User Roles and Permissions

While Sahana allows for defining various user roles and permissions to the customer's liking, SAMBRO has identified five major roles. The roles and their functions are defined in the table below

Role Responsibilities Permitted Functions
Authenticated / Subscriber Receiving alerts through defined communication modes Edit own contact details (email, phone, name, ...) -> pr_contact, pr_person
Alert Editor Can create the CAP Message and submit that for approval cap_alert (Create, Read, Update),
cap_template (Read),
cap_area (Read),
pr_group [person' group](CRUD),
Admin Based Subscription pr_subscription (CRUD)
Alert Approver Besides Authorizing Message to disseminate, they can also act as CAP Editor cap_alert (Create, Read, Update, Review, Approve),
cap_template (Read),
cap_area (Read),
pr_group [person' group](CRUD),
Admin Based Subscription pr_subscription (CRUD)
Implementer/ Administrator Normally one time implementationsuperuser, has access to all the functions

Subscribers (Alert Recipients)

CAUTION! SAMBRO has the option of subscribing to external feeds (both CAP Feed and RSS Feed) that can be rendered in the SAMBRO News Feeds column in the home page. That Implementation specific process should not be mistaken with the subscription work flows discussed in this section, which is specific to subscribing to SAMBRO feeds

There are two types of alert recipients: Public and CUGs. Public can subscribe to RRS/Atom and Social Media feeds. CUGs have all the privileges the pubic has plus other options to receive email and SMS alerts filtered by location, event type, and warning priority.

  1. Request for an account; if you don't have one already
  2. RSS/Atom Feeds for your alert hub or RSS/Atom Reader for all alerts
  3. Email, SMS, FTP and GCM subscription to receive event and area specific alerts
  4. Social Media - link to Twitter, FaceBook news feeds applying the instructions given by the Administrator
  5. View Alerts and interpret them on a map and complete
  6. Filter Alerts
  7. Testing the subscription to alerts

Publishers (Alert Issuers)

The section discusses ways and means for creating a CAP message, having it authorized, and then issuing (or disseminating) to the subscribers

  1. Create a message for the first time and as a message originator
  2. Update a message using an existing message
  3. Cancel a message that has been wrongly issued or the event is canceled
  4. Error a message that has error (in information or data)
  5. Clear a message when the event has subsided to inform the subscribers with an 'All Clear' message
  6. Authorizing and Approving Alerts
  7. Relaying of alerts
  8. Testing the publishing of alerts

Implementers (Super Users)

Section is for CAP Implementers for orienting the CAP Broker in the country or implementation specific context.

  1. Manage Users by associating them with the relevant roles and alerting authority
  2. Edit First-Responder compulsory messaging lists to force messages (i.e. Admin/Implementer defined subscriber lists)
  3. Create Message Templates for categories of events and user groups
  4. Predefined Alert Area polygon and area description developments
  5. Update Register of Alerting Authorities; i.e. setup your organizational structure and alerting jurisdictions
  6. Define CAP implementation specific information such as Waring priorities, Event types, Incident tables, ...
  7. Configure Broker with identifier, warning priorities, and other relevant implementation or country context information
  8. Subscribe to external feeds to render other CAP, RSS/Atom, Social Media (Twitter, Facebook ...), or News Bulletines
  9. Testing the implementation after setup, configuration, and adding users
  10. Requesting for account in SAMBRO

System Administrators

Steps for INSTALLING your SAMBRO instance

  1. [OPTIONAL] Branch an instance of the Sahana Eden code to a new github repository of your own. This would allow you to manage your own customized implementation such as with changing the theme. Ohterwise, ignore this step and pull the code from the main github repository; explained in the subsequent step.
  2. Activate the script to automatically pull the latest version of the code from your github repository.
  3. Install the Sahana Eden software with web2py framework and other dependencies.
    1. Recommend that you install on a Linux server
    2. Open your terminal and go to your web2py path, by default it will be saved on your home directory This is useful if you want to run the EDEN with in your organisation (network) without having the public IP (but remember you cannot access it outside, so recommend you get the public IP) (see http://web2py.com/books/default/chapter/29/04/the-core#Command-line-options for more detail)
      cd ~web2py
      python web2py.py -i your.ip.address -p port.number -a 'your password'
      
    3. Setup the server with a Public IP to be visible over the Internet
    4. Configure the installation to send receive SMS, Email.
    5. Activate the SAMBRO template by changing the default template. Follow


Steps for CUSTOMIZING your SAMBRO instance

  1. Customize relevant settings to configure the instance to the Implementer's liking
  2. Customize the CAP Broker for the implementation context (e.g Admin contact details, banner or logo changes
  3. Basic Administration tasks for activating an instance for the users
  4. Testing the installation to ensure all SAMBRO specific features are functional
  5. The Email Generating Function is available here
  6. The SMS Generating function is available here

Design and Specifications

For advance users or developers interested in the SAMBRO software design requirements and specifications are discussed in the
CAP Broker BluePrint

User Management

Some of the user management resembles to core Sahana User Management, which can be found here. The management specific to SAMBRO are described below:

Self Subscriptions

After you login, the dropdown on the your_email on the top right side shows the sub menu for subscription.

http://i.imgur.com/ZHg8KYp.png

The table lists your subscriptions. To add, click on "Create Subscription" button on the right side above the table list.

http://i.imgur.com/0kWP6NP.png

The subscription form list the drop down for the Event Type, Priority and the Language which you want to receive the alert. It also list the medium through which you want to receive the alert (Email, SMS, Mobile App, FTP).

http://i.imgur.com/xc6ms3N.png

If you do not choose any of the filters, then you will receive the alert for all kind of event type, priority as well as in all language.

Admin Forced Subscriptions

The admin forced subscriptions is mostly for personnel who are bound to receive the alerts. This may be the policy or the standard operating procedures. Note this is accessible only for admin.
Logged in as admin, you will see 'Recipients' menu at the top.

http://i.imgur.com/Rzg6ysK.png

Click on there and you will be redirected to the table list of recipient. Recipients could be individuals or the group of people. Click on 'Add Recipient to List' in order to add new person/group of people to the list.

http://i.imgur.com/bbdn1bN.png

Select the people, group of people and then filter the event type, priority and language and the medium through which you want them to receive the alerts. Remember that if you don't select any of event type, priority and language, the people and the group of people will receive all the alerts. That is no filter is applied. If you want the people or group of people only to recieve the earthquake alert, you can select the Earthquake Event Type from the drop down.

http://i.imgur.com/79cXFaX.png

Register for an Account

By default we do not allow to register. However if you belong to some Disaster Response organisation and feels like having account, you can request to admin to setup the account for you. Go to /eden/default/user/register or from menu Login -> Request for Account. Fill out the form and wait for your account to be approved

Attachments (1)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.