Skip Navigation

Enterprise configuration

To help large organizations, 
BlackBerry AtHoc
 provides the enterprise configuration. Enterprise configuration centralizes communication for multiple organizations, while using inheritance to provide consistent policies and procedures. Alerts can be sent from the enterprise organization to all organizations or subsets of suborganizations.
The enterprise configuration works with 
AtHoc Connect
, allowing suborganizations to communicate with each other and outside organizations, such as vendors or community agencies.
Customers that have a standalone organization with too many users and distribution lists can create multiple suborganizations based on common alerting needs. The enterprise configuration allows you to delegate user management to local organizations, while maintaining the centralized control and communication that the single organization provided.
Example A
A federal agency with an unwieldy single organization can migrate to an enterprise configuration by breaking the large organization into small organizations that represent each geographical location. With multiple locations, the federal agency creates an organization for each alerting region, while retaining the ability to alert all users. 
The federal agency also has manageable user bases that operators can maintain locally. The smaller suborganizations makes it easier to manage user contact information and distributions lists. Each suborganization can use 
AtHoc Connect
 to communicate with each other or to invite local vendors and community agencies to join 
AtHoc Connect
 without impacting the larger enterprise with connect requests and incoming alerts.
With an enterprise configuration, customers that have multiple organizations can have a virtual view of all personnel and consolidate and centralize communication and alert consistency. Enterprises can keep the benefit of multiple organizations, such as user management at the local suborganization.
Example B
A military branch has over 50 organizations, one for each base. To migrate to an enterprise configuration, they implement the following changes:
  • They migrate to a configuration that uses three enterprise organizations, one for each continent on which they have bases. They use three enterprises because the emergency alerting for each continent is managed by a different team of people and each continent has different configuration needs.
  • All enterprises are in the same system, so that any common content in System Setup can be inherited by the enterprise organizations.
  • For each enterprise, they have about five enterprise administrators (EA) and 10 enterprise operators (EO) who can publish alerts to all or parts of the enterprise. At least one EO can access each of the three enterprises.
  • Each enterprise organization has suborganizations for each base on that continent.
  • Operators can create customized common content for bases on each continent (such as content in additional languages) at the enterprise level. Suborganizations inherit the common content.
Alerts can be sent from the enterprise organization, while personnel in the system can be accounted for by tracking responses to alerts.
The consolidated view provides the leadership with useful personnel accountability information for each continent from their respective enterprise.
Each suborganization can use 
AtHoc Connect
 to communicate with their peer suborganizations and affiliates of the organization such as vendors and local governments.
If there is a hurricane on the East coast of the U.S., they can publish alerts to only the appropriate North American alerting regions and ask for responses to check on personnel location, safety status, and availability to assist with recovery. Each base can then alert their Connect affiliates and assess their status.