Data Collection Policy

You have the option to share information with Mitsubishi Electric Iconics Digital Solutions about how you use GENESIS. We use the information that we collect to improve product quality and services. You can opt out at any time. To opt out, open Workbench, select the Tools ribbon, and then select Telemetry Settings.

The data is handled by a third-party service (Amplitude). For information about how the data is handled, please go to https://amplitude.com/legal.

We value your privacy. To learn about our privacy practices, please see our privacy policy.

How We Track

  • A dialog is shown the first time Workbench is launched that will prompt you to opt-in or opt-out of sharing your data.
  • If you decide to share diagnostics with Mitsubishi Electric Iconics Digital Solutions, we will track the operations as described below.
  • Telemetry has no impact on the performance of the application.
  • If for some reason (firewalls, locked network, no internet access) telemetry can’t be sent to the server, the operation fails gracefully, and the telemetry is not sent.

What We Track

When a user performs any event logged by Mitsubishi Electric Iconics Digital Solutions telemetry, we track the following basic user information:

  • Anonymized user ID and device ID
  •  Regional information
    • Country
    • Continent
    • Time zone
  • Operating system information
    • Platform (Mac, Linux, Windows)
    • Operating system version (for example, Windows 11.xxx.xx, Windows 10.xxx.xx, or Mac OS X 10.xx.xx)
    • Language (English or Japanese)
  • Application information
    • Version (for example, 11.000.00.01)
    • Name (Workbench or GraphWorX64)
    • Operation details (see below)
    • A time stamp that identifies when the operation was tracked
  • Configurator build version (Workbench or GraphWorX)

When We Track in the Workbench

  • When the user opens, saves, or closes a form in Workbench, we track
    • The component that is configured (for example, SNMP).
    • The name of the form (for example, SNMP Device Configuration).
    • The execution time when the form is saved (how long it took to save the form).
    • If the form was saved properly.
    • We do not track any user configuration specified in the form.
  • When the user performs special operations, we track
    • The name of the operation (for example, Import)
    • The name of the component (for example, SNMP)
    • How long it took to execute the operation
    • The following operations:
      • Import/export
      • Pack or unpack a project
      • SNMP, BACnet, and Mitsubishi Electric FA network discovery
      • Asset Builder generation
      • Asset equipment template instantiation
      • Create a new database configuration
      • Delete a database configuration
      • Backup or restore a database
      • Test reports, test transactions. and Mitsubishi Electric FA devices
      • Enable or disable reports, transactions, and Mitsubishi Electric FA devices
      • Help mode settings (whether the Help is being viewed in the application or in a browser)
  • When the user is offered an update to their local offline help installation, we track
    • Whether or not the new update was downloaded successfully
    • Whether or not the user chose to keep automatic help updates enabled
    • The version of the installed help files before the update

When We Track in GraphWorX

  • The active number of Data Sources configured in certain configurations:

    • GraphWorX Dynamics

    • Trend Viewer Pens

    • Alarm Viewer Subscriptions

    • We do not track the individual Data Source names, we only track the aggregate number used

  • When the user saves a GraphWorX display file, we track
    • The size of the saved file
    • How many controls, visuals, and dynamics are in the display file
    • A unique identifier for the file, but not the filename itself
    • The number of Dynamics that you can control
    • The number of Dynamics that are view only
    • The number of lines of JScript.NET code (just the line count, but not any of the code)
  • When the user saves a GraphWorX display, we track
    • Anonymized filename
    • File size
    • List of Graphical Object types used in the display
    • List of Dynamic Object types used in the display
    • Number of data sources
    • Display platform (Web/Desktop mode) at the time of saving
    • Whether or not the display has a configured Load Password and Save Password (but it does not log the password itself)
  • When the user opens a display in runtime from the GraphWorX Configurator, we track
    • Anonymized filename
    • Display platform (Web/Desktop mode) at the time of saving
    • Run-time platform (Desktop runtime vs. Open in browser)
  • When the user opens the GraphWorX Configurator, we track:
    • Basic user information
    • Resolution of the monitor on which the configurator opens
    • The DPI scale of GraphWorX (determined by the primary monitor)
  • When the user closes the GraphWorX Configurator, we track:
    • The GraphWorX session duration measured from when GraphWorX was opened.
    • The last used UI theme (Dark mode vs. Light mode)
  • When GraphWorX or Workbench crashes, we track the following information from the exception that caused the crash:
    • Error code
    • Stack trace
  • When the user imports a 3D file into the GraphWorX 3D Viewer, we track:
    • File extension
    • File size
    • Import duration
    • Number of vertices, triangles, and objects in the import
    • Total number of textures
    • Number of referenced and embedded textures
    • Number of unique referenced textures
    • Number of transparent textures
    • Smallest texture dimensions
    • Largest texture dimensions
    • Average texture dimensions
  • Actions related to the Help sidebar:

    • Settings for the Help Mode (In-app vs Online) and Help source (Installed help vs Online help)

    • How long the sidebar remained visible on screen when used

    • Popping out a help page in the help sidebar

    • The last opened page in the Help sidebar when changes to the preferred Help mode (In-app vs Online) are made or the Help sidebar is popped out

    • Changes to the preference for automatically updating the help

    • When the user is offered an update to their local offline help installation, we track
      • Whether or not the new update was downloaded successfully
      • Whether or not the user chose to keep automatic help updates enabled
      • The version of the installed help files before the update

What We Track related to Licensing

  • When the license is violated at Error or Severe levels

    • We do not track lower severity license errors

  • Time spent with a valid license

    • We do not track time spent in an unknown license tier

  • Time spent in Demo Mode