System Requirements

Confirm every item on this page before you begin the installation walkthrough. Mismatched Ignition or IA-module versions are by far the most common cause of a Tamaki MES install that "starts but doesn't work."

Ignition platform

Item	Requirement
Ignition version	8.3.6 or newer in the 8.3 line
Edition	Standard Ignition gateway. Edge is not supported.
Required IA modules	Perspective, Reporting, Tag Historian (all must be installed and licensed before Tamaki MES starts)
License	The module ships with a built-in trial support; an active Tamaki MES license key (requested via the pricing page) is required for production use

Vision is not used. You can keep Vision installed for the rest of your projects, but Tamaki MES will not register a Vision client interface.

Always check the release notes for the specific Tamaki MES version you are deploying: minor versions occasionally raise the Ignition floor.

Database

Tamaki MES stores all entity data in a relational database that you connect through Ignition's datasource manager. Pick one of:

Database	Notes
MariaDB	Recommended for first-time installs. Used in the install walkthrough.
MySQL	Supported. Match the JDBC driver version to your server.
Microsoft SQL Server	Supported. Use Microsoft's official JDBC driver.
PostgreSQL	Supported.

In every case:

• Create an empty schema before installing. Tamaki MES runs its own migrations on first start and will not share a schema with other applications cleanly.
• Use UTF-8 (utf8mb4 on MariaDB/MySQL) for everything you can configure. Material names, location paths, and notes routinely contain non-ASCII characters.
• The database user needs full DDL privileges on the schema (CREATE/ALTER/DROP table, index, view). Read-only or DML-only accounts are not sufficient: Tamaki MES versions itself with Liquibase.
• For production deployments, point the schema at a server that supports backups and point-in-time recovery. The MES schema is operational data, not derived state.

Browser

The Perspective project that ships with Tamaki MES runs in any browser Inductive Automation lists as supported for Perspective. As a practical baseline, current Chrome, Edge, Firefox, and Safari are all known to work. Touch-screen HMIs running Perspective also work, with some custom components rendered for larger viewports.

Network

• The gateway must be reachable from operator and admin browsers on the Perspective port (typically 8088 or 443).
• The gateway must reach the database server on the configured JDBC port.
• The gateway needs outbound HTTPS to reach Inductive Automation's license servers (for activation) and Tamaki's distribution at tamakisoftware.com.

For air-gapped installs, contact Tamaki Software for offline-activation steps.

Hardware sizing

There is no one-size-fits-all sizing recommendation: your load depends on how many locations you model, how many OEE samples you ingest per second, and how many operators are connected. As a starting point:

Use case	Suggested baseline
Single-plant pilot (< 50 locations, < 20 concurrent operators)	The same gateway hardware Inductive Automation recommends for a standard Perspective gateway
Multi-line production (50–500 locations)	8 vCPU / 16 GB RAM gateway, separate database server with SSD storage
Enterprise (multi-site, 500+ locations)	Dedicated gateway cluster (see Redundancy add-on), separate DB cluster, talk to Tamaki Software for sizing

OEE and inventory generate the most write load. If you expect high-frequency state changes from many lines, plan headroom on the database server.

Required IA module licensing

Tamaki MES does not bundle Perspective, Reporting, or Tag Historian: those are Inductive Automation modules and they need their own licenses on the gateway. If your gateway runs Perspective today, you already have most of what you need.

Next step

Installation: the step-by-step walkthrough for a fresh install.