General Reference

GE Analytics System Requirements

License Requirements

The GE System 1 Integration license is required to take advantage of the GE Analytics functionality.

Additional Components Required

In addition to the basic GE Digital APM system architecture, your system must also contain the following additional components:

Enterprise Impact V17.1 SP 1: A third-party component that exceeds the scope of this documentation.
RabbitMQ Server V3.5.3 and Later: A third-party component that exceeds the scope of this documentation.

Data from GE systems, such as GE System 1 and GE SmartSignal, is transferred to GE Digital APM via Enterprise Impact 17.1 SP1. This GE Fleet Message Server represents the following components:

Note: We recommend that these components be installed on the same machine to simplify the configuration of this module. However, in your system architecture, these components may be installed on separate machines.

Enterprise Impact V17.1 SP 1: A server that aggregates data from one or more GE systems and publishes the data to the RabbitMQ Server.
Note: There can only be one Enterprise Impact per GE Digital APM database.
Meridium GE System 1 Integration Service: A service that subscribes to the published data aggregated by Enterprise Impact, and synchronizes the data to the GE Digital APM Database.
RabbitMQ Message Server: An open source message broker used by Enterprise Impact to translate messaging protocols from the sender to the receiver.

System Architecture

The following image shows how the additional components should be incorporated into the basic GE Digital APM system architecture to support this module.

Deploying GE Analytics

After you have installed and configured the basic GE Digital APM system architecture, you will need to perform some configuration steps specifically for GE Analytics.

Supported Features in APM Now

This GE Digital APM module is not available in the APM Now environment.

GE Analytics Data Model

The following diagram shows how the families involved in GE Analytics are related.

When you complete the deployment steps for GE Analytics, the following records types are created automatically:

One GE Tag record will be created in the GE Digital APM system for each tag defined in the related GE Enterprise. Tags can represent direct physical measurements or calculated values that generate events, or nodes under which other tags are grouped.

In order to use GE Analytics, the GE Digital APM database must contain Equipment or Functional Location records that define the assets whose events data you want to track. Each of the asset records must be linked to one or more GE Tag records.

Important: If a GE Tag is not associated with an asset record in the GE Digital APM database, then no events will be received in the GE Digital APM system, even if they exist in the configured GE system.

About State Management in GE Analytics

GE Analytics employs standard State Management functionality to manage GE Tag Event records.

The following baseline record states are configured for the GE Tag Event family:

Open: Indicates a new event that has not been acknowledged. This is the default state for GE Tag Event records.
Pending: Indicates that the event has been acknowledged and is awaiting action.
Closed: Indicates that any related actions have been initiated or that it has been determined that no actions are needed.

Note: In order to transition a GE Tag Event record to closed, you must provide an explanation of why you are closing the event by selecting a value in the Disposition Reason field.

The following diagram shows the state transitions available for GE Tag Event records.

About Site Filtering in GE Analytics

In GE Analytics, users will see only data related to GE Tag records assigned to their site(s) or that are global records.

Tip: For more information, refer to the Site Filtering section of the documentation.

For information on configuring GE Tags and sites, refer to the GE Analytics Administrative section of the help.

Consider an organization that has three sites, Site X, Site Y, and Site Z. The following GE Tag records exist:

GE Tag 1: Assigned to Site X
GE Tag 2: Assigned to Site Y
GE Tag 3: Assigned to Site Z
GE Tag 4: No site assigned (global record)

Each of these GE Tags has related GE Tag Events.

Scenario 1: User assigned to only Site X

When this user views the GE Analytics Overview page, he or she can view GE Tag 1 and GE Tag 4, as well as any associated alerts and events. GE Tag 2 and 3, and their related events, are not visible.

Scenario 2: User assigned to both Site X and Site Y

When this user views the GE Analytics Overview page, he or she can view GE Tag 1, 2, and 4, as well as any associated alerts and events. GE Tag 3, and its related events, is not visible.

Scenario 3: Super User

When this user views the GE Analytics Overview page, he or she can view GE Tag 1, 2, 3, and 4, as well as any associated events.

GE Analytics Security Groups and Roles

The following table lists the baseline Security Groups available for users within this module, as well as the baseline Roles to which those Security Groups are assigned.

Important: Assigning a Security User to a Role grants that user the privileges associated with all of the Security Groups that are assigned to that Role. To avoid granting a Security User unintended privileges, before assigning a Security User to a Role, be sure to review all of the privileges associated with the Security Groups assigned to that Role. Also, be aware that additional Roles, as well as Security Groups assigned to existing Roles, can be added via Security Manager.


Security Group	Roles
MI GE Administrator	MI Health Admin
MI GE User	MI Health User MI Health Power
MI GE Viewer	None

Note: The Security Groups listed in the table above account only for family permissions. Users must also be added to the MI Configuration Role Security Group in order to access the Systems and Tags page, which is required to modify families used by this module.

The baseline family-level privileges that exist for these Security Groups are summarized in the following table.


Family	MI GE Administrator	MI GE User	MI GE Viewer
Entity Families
GE Connection	View, Update, Insert, Delete	View	View
GE Enterprise	View, Update, Insert, Delete	View	View
GE Filter	View, Update, Insert, Delete	View	View
GE Tag	View, Update, Insert, Delete	View	View
GE Tag Event	View, Update, Insert, Delete	View, Update, Insert, Delete	View
Relationship Families
Has Consolidated Events	View, Update, Insert, Delete	View, Update, Insert, Delete	View
Has GE Enterprise	View, Update, Insert, Delete	View	View
Has GE Filter	View, Update, Insert, Delete	View	View
Has Tag	View, Update, Insert, Delete	View	View
Has Tag Event	View, Update, Insert, Delete	View	View

System Code Tables Used by GE System 1 Analytics

The following table lists the System Code Tables that are used by GE Analytics.


Table ID	Table Description	Function
EVENT_DISPOSITION_REASON	Event Disposition Reason	Used to populate the Disposition Reason list in GE Tag Event records.