Intrado Bewaresm

Intrado BewareSM

Frequently Asked Questions (FAQ)

[Expanded Detail ─ Internal Use / Partners Only]

Ron Fournet

Intrado SAT Team Six Leader & Executive Advisor

Protecting the Community With Intrado Beware

Mobile 720.317.7593

May 8, 2013

Page 1 – FOR INTERNAL USE ONLY

GENERAL

How is the threat score displayed?
Threat scores are displayed via a proprietary and patent-pending algorithm that searches information from hundreds of sources including public records, commercial data and deep-space web crawling of social media and various Internet sites.

These different types of data gathered are then weighed against the relevancy of a direct or indirect possibility of a threat.

The scoring algorithms take into account hundreds of variables, their rated importance, their age of occurrence and other rated factors, and computes a Threat Score. The two-digit Threat Score (01-99) drives the color rating of Green / Yellow / Red (where 01-15 is Green; 16-50 is Yellow; and 51-99 is Red).

Super-ordinate rules are also in play and can override the scoring algorithm. An example of that is the “law enforcement exposure factor”, a rule that causes the score to exceed the Yellow threshold of 16 when the subject has had a lot of law enforcement exposure in a short period of time, even if just for traffic citations (which normally have minimal effect on the score).

Can the algorithm be adjusted to meet specific operational needs?
Yes, the Beware algorithm can be tailored or “tuned” to meet standard operating procedures and established risk-acceptance or officer-safety strategies of the agency.

In the initial deployment of Beware, we allow the agency to tune the crawlers and the threat scoring algorithm to reflect their departmental policies on officer safety and risk acceptance. The ‘tuning console’ is exposed to the Super User (agency administrator) and we work with that person in tuning the Beware adaptation for their agency.

Can the public safety agency select or de-select which data sources to be queried?
Today, Beware searches fixed data sources that have been optimized to provide the best informational profile and threat score.

In future releases we expect to provide the agency with a data-selection console, which will allow them to both adjust the data being acquired for a Beware resolution as well as provide options on costs to run Beware.

Where does the data come from?

The data comes from thousands of commercial and public record sources as well as the World Wide Web (e.g., publication sites, social media sites, blogs, etc.).

We use a “Rotary-Pole Architecture” (RPA) as the fundamental platform for acquiring data from these sources. The RPA is highly proprietary and considered trade secret. It allows us to tune the data acquisition by supplier and data element. Or stated differently, we can at any time select Supplier A for cell phones and Supplier B for associates and Supplier C for criminal records and Supplier D for [etc. etc.]. The RPA in turn enables the user to select which data and sources they want to use in fulfilling Beware requests.

How current is the data provided by Beware?
The data retrieval is completed in real time through multiple informational gateways. The data reflects recent and past commercial transactions, public record citations, and web postings of individuals, and therefore is very current.

The currency of the data is dependent on the data element and the sourcing. For example, property records are updated every 30 days; vehicles every 15 days; but cell phones every day.

Where is Beware deployed today?
Beware has been in development for the past several months and is now being deployed in one, mid-sized law enforcement agency in the Denver-Metropolitan area, one state-level organization, and several pending deployments to small-to-large metropolitan areas across the US.

How do my responders, call takers and dispatchers access Beware?
Beware is a secure, cloud-based service that can be accessed through a web browser with any Internet-enabled device and the correct credentials. Beware is further integrated in Intrado’s Power911 call-handling software, as well as many CAD systems.

Is pricing available?
Pricing is developed on an individual case-by-case basis, using the customer-preferred configuration as the key driver. Generally the solution is configured to minimize costs in the first year, yet maximize agency benefit and exposure to the Beware solution. Pricing for a small agency is generally in the $25-50K/year range; and $50-100K/year for a medium-sized agency; and $100-200K/year for a large agency.

Will Beware be made available to Intrado’s channel partners?
Yes. We are currently working with several CAD partners, certain personal safety application companies, and major equipment-provisioning companies which serve the public safety markets.

PRIVACY QUESTIONS

What are the personal privacy implications of Beware?
Commercial and public records data has been available for consumption for years. In fact, insurance companies, credit bureaus, financial institutions and marketers have used and continue to use public and commercial data for business purposes.
Intrado Beware simply transforms this already available and accessible data into actionable information to protect property and save lives within our communities when and where such information is needed most. Intrado Beware suppresses all data not truly required for first responders to perform their mission in saving lives; and thus protects citizen privacy while aiding in the public safety mission.

How do we know that the information Beware displays is used to protect property and save lives?
Intrado provides the Beware solution only to credentialed public safety agencies to improve the effectiveness and accuracy of information needed to save lives and protect property.
These public safety agencies use Beware in accordance with their standard operating procedures.

What laws cover the privacy or usage aspects of Beware?

1965Freedom of Information Act (FOIA)

1970Fair Credit Reporting Act (FCRA)

1970Bank Secrecy Act

1994Drivers Privacy Protection Act (DPPA)

2000Graham Leach Bliley Act (GLB)

2001Patriot Act

2003FACT Act

Page 1 – FOR INTERNAL USE ONLY