Home
Integrate mRounds with External Systems
Configure external-system connections for master data synchronization, data export, email, and maintenance integrations.
Connect Shift Handover Reports to Platform Alerts and IMES
Show platform Alerts and IMES query results in mRounds Shift Handover Reports.
IMES Prerequisites for Shift Handover Reports
IMES data reaches Shift Handover Reports from the iMES database through TaskOrchestration and Kafka. The implementation team sets up everything before the Shift Handover settings.
TaskOrchestration Connection Settings for iMES
TaskOrchestration needs the iMES database connection and the Kafka connection issued for your deployment.

Title and Copyright
Review the guide's release details, copyright notices, and terms of use.
Preface
Understand audience, know related documents and products and conventions followed in this document.
What's New for mRounds Configurators
Find new and expanded configuration guidance for Maximo, Dozuki, AVEVA PI, iMES, Gensuite and Shift Handover Reports.
Integrate mRounds with External Systems
Configure external-system connections for master data synchronization, data export, email, and maintenance integrations.
- Establish a Connection with FTP Server for Data Export
  An FTP (File Transfer Protocol) server connection allows mRounds to transfer large volumes of data to external systems for reporting, backup, or further processing. Establishing this connection enables the export of rounds data and reports to FTP servers without manual intervention, ensuring a smooth and automated process for data storage and sharing.
- Establish a Connection with ODBC for Database Integration
  The ODBC (Open Database Connectivity) connector allows mRounds to directly interface with external databases. This connection is crucial for exporting rounds data to an organization’s internal databases, enabling further analysis and integration with other systems like reporting tools or custom dashboards.
- Configure an SMTP Server for Automated Email Notifications
  Configuring an SMTP (Simple Mail Transfer Protocol) server allows mRounds to send automated email notifications to stakeholders about task completions, issues, and important updates. This connection ensures timely communication about maintenance operations.
- Establish a Connection with SAP for Master Data Integration
  Connect mRounds to SAP and synchronize master data from SAP.
- Establish a Connection with Maximo for Master Data Integration
  Connect mRounds to Maximo to synchronize Locations and Assets, and configure Maximo work order events when required.
- Establish a Connection with Enablon for EHS Incident Management
  If an Environment, Health, and Safety (EHS) issue is raised in the mRounds application, the details are automatically transferred to the Enablon incident management tool, creating a corresponding event. Additionally, if an SAP notification is generated for the same issue, mRounds sends the notification number along with the issue details to Enablon.
- Send mRounds Issues to Benchmark Gensuite
  Connect mRounds to Benchmark Gensuite to send Issue data as Concern Reports.
- Configure the Dozuki Integration
  Enable the Dozuki integration and set its API endpoint and administrator credentials for the tenant.
- Integrate mRounds with AVEVA PI
  mRounds can receive PI event frames, acknowledge them in PI, and write round readings back to PI attributes.
- Connect Shift Handover Reports to Platform Alerts and IMES
  Show platform Alerts and IMES query results in mRounds Shift Handover Reports.
  - IMES Prerequisites for Shift Handover Reports
    IMES data reaches Shift Handover Reports from the iMES database through TaskOrchestration and Kafka. The implementation team sets up everything before the Shift Handover settings.
    - iMES Data Sets for Shift Handover
      Four iMES data sets reach Shift Handover. Each Kafka message carries its queryId and tableName so the consumer can tell them apart.
    - TaskOrchestration Connection Settings for iMES
      TaskOrchestration needs the iMES database connection and the Kafka connection issued for your deployment.
    - iMES Task Graphs and Schedules
      Each data set runs as a two-task graph, execute_sql followed by publish_kafka, on a schedule.
    - iMES Results Message on Kafka
      Each graph run publishes one TASK_RESULT message to task.sql.results, which the mRounds Shift Handover service consumes.
  - Configure Shift Handover Alerts and IMES Settings
    Control report visibility, badge colors, mobile row limits, and custom-section limits for the tenant.
  - Add Alerts and IMES Widgets to Shift Handover Reports
    Add source-specific alert tables and IMES result tables to reports generated for a plant.
  - Verify That IMES Results Reach Shift Handover Reports
    Run a test IMES graph, confirm that its result reaches Kafka, and then confirm that IMES appears as a widget source in Shift Handover.
Onboard Tenants/Super Admins
Use the Tenant Management module to create tenant or super admin roles for onboarded customers/user and provide access to the applications and modules.
Create and Manage Master Data
Master Data forms the foundation of the system, providing essential information such as plants, shifts, locations, assets, units of measurement, and response sets. Properly setting up master data ensures seamless work order management, asset tracking, and operational efficiency.
Onboard Users and Assign Roles
Use the User Management module to create roles and so on, create users, and assign relevant roles to the users.
Invoke mRounds Tasks Using APIs
Innovapptive exposes certain APIs that can be used by applications and create tasks like creating operator rounds, dynamically generate round plans, and so on.

TaskOrchestration Connection Settings for iMES

TaskOrchestration needs the iMES database connection and the Kafka connection issued for your deployment.

iMES database (MySQL)

Use an account that is read-only on the data-set tables and views. Keep the user and password in a Kubernetes Secret, not in the manifest.

Variable	Reference default	Meaning
`SQL_CLIENT`	`mysql2`	Database client: `mysql2`, `pg` or `mssql`. iMES uses `mysql2`.
`MYSQL_HOST`	`localhost`	iMES database host
`MYSQL_PORT`	Dialect default (3306)	Database port
`MYSQL_DATABASE`	`app`	Database name, for example `manufacturing`
`MYSQL_USER`, `MYSQL_PASSWORD`	—	The read-only account issued for the deployment

The defaults are the code's fallbacks, shown for reference. Set every value from the connection details issued for the deployment. Do not rely on the fallback account (root with an empty password).

Kafka

Broker addresses alone are not enough. The Kafka listener requires TLS and SASL/SCRAM.

Variable	Meaning
`Q_KAFKA_BROKERS`	Comma-separated bootstrap servers
`Q_KAFKA_SSL`, `Q_KAFKA_SECURITY_PROTOCOL`	Enable TLS
`Q_KAFKA_CA`	CA certificate
`Q_KAFKA_USERNAME`, `Q_KAFKA_PASSWORD`, `Q_KAFKA_MECHANISM`	SASL/SCRAM credentials
`KAFKA_CLIENT_ID`	Client ID. Default `task-orchestration`.

Check the settings

At startup, TaskOrchestration logs the resolved host, port, database and brokers (never passwords). Check that log after deployment: a silently defaulted MYSQL_HOST or Q_KAFKA_BROKERS shows up there immediately.