The List of GENESIS Services

If you want the Alarm Historian to capture records of alarm activity in the Alarm Server. Also needed if a user interface will request data from the historical record.

If you are using the .Query interface to request historical alarm data. It is not required for direct subscriptions to the A&E server, it is only for retrieving .Query datasets.

Generates and maintains the current state of alarms.

Without it running, subscriptions to the alarm server will fail, and alarm states will not be tracked.

If you are interfacing with a Sierra modem to send and receive notification messages. Related to the configurations in the Workbench (Alarms and Notifications > Alert Notifications > SMS/Text Nodes). Also requires the GENESIS Alert Notifications Point Manager to be running.

If you have configured Assets in the Workbench and are intending to subscribe to or use Assets.

If your project involves subscribing to BACnet data.

If you are using the .Query interface to request data from BACnet devices such as channels, devices, objects, or values. It is not required for direct subscriptions to BACnet data, it is only for retrieving .Query datasets.

Used to load in to memory and serve data requests for all data flows and data models configured for the BI Server in the Workbench (Analytics > BI Server). Data tables are stored in memory by the service, and therefore without this service the related tables will not work.

Used to subscribe to data from a Classic OPC Server (DA data requests). Note that the server must be local (on the same machine) to the GENESIS install with this service in order to access data.

If you are using the Data Historian Importer capability to merge data to the Historian (found in the Workbench under Historical Data).

If you are using the .Query interface to request historical data. It is not required for standard integrations such as trend viewers, reporting, or data export.

If you subscribe to databases using connectivity defined in the Workbench (Data Connectivity > Databases). It is also required for testing connectivity and discovering table schema from the related databases when configuring in the Workbench.

This service is used both to monitor and detect fault incidents, as well as to serve requests for historical fault records.

If you are using the .Query interface to request historical fault incidents. It is not required for standard integrations such as grid viewers or reporting requests of fault incidents.

Core service, responsible for security authentication and path resolution for all data requests and exchanges between point managers. Required by GENESIS.

Used by the health monitor to provide system statistics. Related to points configured in the Workbench (Servers and Redundancy > Server Settings > Health Monitor Settings). Without this service, the related points will not return data when subscribed.

If you have configured a connection to an IoT Broker such as MQTT or Azure IoT Hub in the Workbench (Data Connectivity > Internet of Things > Publisher Connections). This service is required if this connection is meant to automatically publish messages. Also required if using a Bridging activity block that publishes using this data connectivity.

f you have configured a connection to an IoT Broker such as MQTT or Azure IoT Hub in the Workbench (Data Connectivity > Internet of Things > Subscriber Connections). Note that this is for subscribing and browsing data in the brokers, see the Internet of Things Publisher for publish list uses.

When you have configured connections to supported Mitsubishi Electric FA devices in the Workbench (Data Connectivity > Mitsubishi Electric FA). Without it, data subscriptions will fail and network discovery tools in the Workbench will not work.

If you subscribe to Modbus data configured in the Workbench (Data Connectivity > Modbus)

If you are testing connectivity to, or requesting data from an OPC UA Server. Affects configurations in the Workbench (Data Connectivity > OPC UA)

If you are creating or managing recipes. Configured in the Workbench (Platform Services > Recipes). If the services is not running then the recipes will not be accessible to user interfaces, such as for recipe controls or commands.

If you are creating or executing reports using the Excel based report plugin.

If you are creating or configuring schedules using the configuration in the Workbench (Actions > Schedules) or attempting to configure a schedule in a GraphWorX control. Note that this service is also responsible for real time schedule action such as writing to values or value sets. If it is not running then those schedules will not be invoked.

If you subscribe to svrsim or @sim64 (when running in compatibility mode).

If you subscribe to SNMP data as configured in the Workbench (Data Connectivity > SNMP)

Used to maintain the operation of triggers configured in the Workbench (Actions > Triggers). Triggers are likely to be used in conjunction with bridging, alert notifications, or reporting.

If you are using Expressions, Registers, or Value Sets configured in the Workbench UDM (Platform Services > Unified Data Manager)

Used by the Web API RESTinterface, also known by the Swagger UI documentation found on the server at localhost/fwxapi/swagger/index.html. Note, this is used as an outward facing connectivity API, it is not related to the Web Service Point Manager

Used by the Web Services data connectivity found in the Workbench ( Data Connectivity > Web Services) in order to connect to REST interfaces. Not, this is not related to use of the Web API Service in GENESIS.