How does Oracle Empirica Signal support a multi-enterprise Argus Mart implementation?
Multi-enterprise support for an Oracle Argus Mart implementation is an extension of existing Oracle Empirica Signal features.
The Oracle Empirica Signal features that support multi-enterprise enabled Oracle Argus Mart Cloud configurations include:
Interactive signal management configurations
Interactive signal configurations allow a user, with appropriate permissions, to create, validate, and refresh the configuration in the Oracle Empirica Signal application. Interactive signal configurations are currently available for proprietary data maintained in Oracle Argus Mart and for various public safety data sources.
With a multi-enterprise enabled Oracle Argus Mart Cloud configuration, users can reference multiple enterprise data configurations to populate the Signal Review page. The intended outcome is to create individual data mining runs, queries, case series, and reports for ad hoc analyses for each business unit.
Import of subscription data releases
When importing data offerings for the cloud environments, Oracle Empirica Signal supports access to the Oracle public safety data library. If you subscribe to public safety data and Oracle enabled the data library access for your environment, users with Manage Configurations permission can access the Manage subscription data releases page. From this page, users can view available data releases and associated release notes and import releases into Oracle Empirica Signal.
Multi-enterprise support can only be enabled during the import of an Oracle Argus Mart data offering into Oracle Empirica Signal. Once enabled it cannot be disabled.
Login groups
A login group is a group of users. You can assign a different Home page, logo image, signal management configuration, and topic workflow configuration for each login group. All Oracle Empirica Signal users must belong to a login group.
Enabling multi-enterprise support for Oracle Argus Mart happens during import of the Argus data offering as a result of your support request. Once multi-enterprise support is enabled, login groups are used to map enterprise IDs to users. A user’s login group determines what enterprise data, if any, the user has access to. Users with Manage Signal Configurations permission will see only Signal Configurations published to their login group or published to them individually. A typical user has access only to multi-enterprise enabled objects (such as queries, case series, data mining runs, and reports) published to their login group.
User permissions
Permissions are rights to perform specific tasks in Oracle Empirica Signal. Sets of permissions are associated with a user's role. For example, you might create a user role that includes the permissions to create data mining runs and view data mining run results. You can assign one or more user roles to a user.
Permissions also control how users can interact with a multi-enterprise enabled Oracle Argus Mart Cloud configuration. An Oracle Empirica Signal superuser has broad permissions for setting up and maintaining the configuration.
If you are a superuser, you can assign an enterprise ID, change a user's login group, edit attributes of the configuration, and publish a multi-enterprise object to multiple login groups, as well as see and share reports.
An Oracle Empirica Signal user with Manage Signal Configurations permission serves as an administrator for their login group. Very few users should be granted the Manage Signal Configurations permission.
Publishing
To make the signal configuration available to other users, it must be published to login groups or individuals.
A superuser or a user with Manage Signal Configurations publishes the multi-enterprise enabled Oracle Argus Mart configuration. However, non-superusers can publish configurations only to their login group or individuals in their login group.
Refreshes
You refresh an interactive signal configuration to incorporate changes made to the configuration. During a refresh, Oracle Empirica Signal incorporates your changes and validates the signal configuration. If validation errors are found, the refresh fails.
Any time changes are made to the multi-enterprise enabled Argus configuration, a refresh is required. Only the configuration owner and users and superusers that belong to the login group to which the configuration has been published can refresh a multi-enterprise enabled Oracle Argus Mart Cloud configuration.