The List of GENESIS Services

Used when configured as a dedicated collector node (not needed when running data collection through "Local Collector"). Primary use is as a remote collector forwarding data to a central Alarm Historian point manager.

If you want the Alarm Historian to capture records of alarm activity in the Alarm Server. Also needed if a user interface requests 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 Alarm server, it is only for retrieving .Query datasets.

Generates and maintains the current state of alarms.

When not running, subscriptions to the alarm server fail, and alarm states are not tracked.

If you are interfacing with a Sierra modem to send and receive notification messages. Related to the configurations in 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 Workbench and intend 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, 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 Workbench (Analytics > BI Server). Data tables are stored in memory by the service, which means that the related tables will not work without this service.

The service responsible for executing transactions. It is required to transact, though it can be distributed across multiple nodes in a cluster as appropriate and receive execution scheduling instructions from the Scheduler service.

Schedules the transactions (translates triggering events into executing transactions). Sends execution to the Bridging point manager. Required for the bridging functionality.

Required for integration to ONVIF protocol cameras.

Required for integration to MJPEG or RTSP protocol cameras.

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.

Manages local configurations of users and groups as well as integration to third-party account sources. Required if using the dynamic worker lookup activity blocks in notifications, or worker lookup from data points associated to CFS services.

This is the service responsible for executing transactions. It is required to transact, though can be distributed across multiple nodes in a cluster as appropriate and receive execution scheduling instructions from the Scheduler service.

Schedules the transactions (translates triggering events into transaction execution). Sends execution to the CFS Workflows point manager. Required for notification functionality.

Used when configured as a dedicated collector node (not needed when running data collection through "Local Collector"). Primary use is as a remote collector forwarding data to a central Data Historian Logger.

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

Core service of Data Historian, responsible for storing data to the disk, performing calculations, and serving data requests of 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 Workbench (Data Connectivity > Databases). It is also required for testing connectivity and discovering the table schema from related databases in the Workbench configuration.

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.

A 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 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 Workbench (Data Connectivity > Internet of Things > Publisher Connections). This service is required if the connection is meant to automatically publish messages. Also required when using a Bridging activity block that publishes using this data connectivity.

If you have configured a connection to an IoT Broker, such as MQTT or Azure IoT Hub in 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 Workbench (Data Connectivity > Mitsubishi Electric FA). Without this service, data subscriptions will fail and network discovery tools in Workbench will not work.

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

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

If you are creating or managing recipes. Configured in Workbench (Platform Services > Recipes). If the service is not running, the recipes are not 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 Workbench (Actions > Schedules) or attempting to configure a schedule in a GraphWorX control. Note that this service is also responsible for real time schedule actions, such as writing to values or value sets. If it is not running, those schedules are not invoked.

Used for the Search function in Data Browser.

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

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

Used to maintain the operation of triggers configured in 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 Workbench UDM (Platform Services > Unified Data Manager).

Required for finding "Favorites" and user-specific settings in Data Browser and Workbench environments. Used for storing trend configurations, stored per user profile.

Used by the Web API REST interface, also known by the Swagger UI documentation found on the server at localhost/fwxapi/swagger/index.html. Note that it is used as an outward facing connectivity API, and it is not related to the Web Services point manager.

Used by the Web Services data connectivity found in Workbench ( Data Connectivity > Web Services) to connect to REST interfaces. Note that it is not related to using the Web API Service in GENESIS.