Skip to main content

System Requirements

Kanoa MES is installed as a module on an Ignition Gateway. Data is stored in Microsoft SQL Server.

Ignition Requirements​

Kanoa MES supports Ignition 8.1 and Ignition 8.3. You can find Kanoa Modules for each version on our website: kanoa.ai

Required Ignition Modules​

  • KanoaMES
  • Ignition Perspective (Note Vision is not supported)
  • Embr Charts

The following are not required, but are commonly recommended based on implementation needs...

  • WebDev Module - recommended for bidirectional communication with ERP systems via RESTful APIs.
  • CirrusLink MQTT modules - recommended when data resilience is important and the customer wants store-and-forward data patterns from the site.

Kanoa keeps pace with Ignition releases. When Kanoa publishes new versions, the Release Notes specify which Ignition versions are compatible. Before installing or upgrading, confirm version compatibility in the Kanoa Release Notes for your target Kanoa MES version and Ignition version.

caution

Confirm your Ignition version is supported for the Kanoa MES version you are installing.

Database Requirements​

Kanoa MES requires Microsoft SQL Server 2019 (15.0) or later

Note: Follow Microsoft's recommendations for SQL Server CPU provisioning, and keep in mind SQL Server licensing costs may be impacted by CPU configuration.

Infrastructure requirements​

The Ignition Gateway server can be on-premises, in the cloud, physical, virtual, containerized, windows or linux based.

It is recommended to provision both the Ignition Gateway server and SQL Server with at least 3 CPU cores and 16 GB of memory. Actual required resources will be dependent upon # of assets, # of tags, # of concurrent clients. For more detailed sizing guidance, refer to Ignition Server Sizing and Architecture Guide

Development and Test Environments​

It is recommended to maintaining separate environments for development and production to provide a safe place to validate updates, configuration changes, and new customizations and extensions before deploying to your production system of record or risking manufacturing interruptions.

Development and test environments can be licensed at 50% of the license cost or can be run in trial mode.