Design Principles

These are the design principles on which the advanced Raven Emergency Management Platform are based.

1.  Adherence to ICS/NIMS

Raven is firmly rooted in the structure, philosophy, policies, and procedures of the Incident Command System (ICS) and the National Incident Management System (NIMS). The developers of Raven and its predecessor come from the operational community and are expert practitioners of ICS/NIMS.

Raven is focused at the incident command level and is designed to enable faster and more complete situational awareness at the point of the sword where responders are looking at the threat face-to-face.


2.  Seamless Scalability

Raven is designed to be "All Scale", with the same tools, technologies, CONOPS (concepts of operation) and services applying from initial response to extreme-scale incidents, seamlessly.  There are no new tools, concepts, procedures, design philosophies or user interfaces that the user has to master moving across the scale of incidents.  

Raven is designed to support 1,000s users from 100s of organizations working dozens of incidents simultaneously.


3.  Network to the Edge

Raven is designed to connect the most remote users, those at the point of the sword looking at the evolving threat face-to-face and who are trying to develop situational awareness about what is happening and what should be done about it.  With these forward users using the Raven network, information that they are collecting and sharing with others on the front lines can be easily transmitted to rear operations centers to build situational awareness about the larger battlefield.  

Networking to the edge means that forward users will be equipped with mobile, handheld computers (smart phones, tablets) as well as vehicle-mounted laptops and other devices.  Further, these need to be resilient when operating in remote, Internet-degraded settings where connectivity could be intermittent.  In such cases, "fail soft" and "restore gracefully" processes need to aid the user.


4.  Technology Neutral  --  Web-Based

Raven us designed to be technology neutral.  The user can employ any computational device (workstation, laptop, tablet, smart phone, other) running any standard operating system (Windows, OS X, iOS, Android, Linux, other) using any basic browser (Safari, Firefox, Chrome, Internet Explorer (Version 9 and later)).

 5.  "App Store" Development Approach

 Raven is designed around a platform architecture where growth, expansion, and tailoring is accomplished with Apps and Plugins, as with the Apple App Store.      Anyone can contribute:  commercial, academia, government, uniformed responder, private citizen, as examples.

 6.  All Hazard

Raven is designed to apply to all hazards across the board:  Storms, lightening, fires, floods, hurricanes, volcanic activity, landslides, explosions, aircraft accidents, earthquakes, windstorms, tidal waves, terrorist attacks, riots, civil disobedience, wars, chemical spills, train derailments, other.

7.  Platform for the TIRED - DIRTY - HUNGRY

Raven is first and foremost designed for simplicity of use.  It is for the Tired - Dirty - Hungry responder under extreme stress.  As such, it is designed to be "dirt simple to learn" and "dirt simple to use."  If a user knows how to turn on a computer, surf the web, and find the local "Olive Garden" using Google Maps, then they can learn all basic Raven operations in 60 minutes or less.

8.  Growth Model

Raven is not owned by a vendor.  Its intellectual property is not up for sale. It is a community project for and by the community.