Skip to main content

Why Kanoa

Kanoa follows a platform-first philosophy and inherits many of the 'unlimited, server-based' advantages that make Ignition so attractive:

  • Rapid time-to-value with a standardized operational model (assets, materials, work orders, execution)
  • Modular adoption: start with Ops, then add Quality and Trace as your requirements mature
  • Ignition-native delivery: built for the Gateway model and designed for Ignition Perspective
  • Open data architecture: configuration and production history live in SQL for reporting, integration, and analytics
  • Server-based deployment: installed on an Ignition Gateway (one server controls the system)
  • Simple licensing: licensed per Gateway, expanded via modules
  • Unlimited scale at runtime: no per-client runtime licensing model for operator access patterns
  • Web-based management: installed and administered through the Gateway interface
  • Open SQL backend: your MES data is stored in Microsoft SQL Server and remains accessible

If you’re new to Ignition concepts like Gateway, projects, and Perspective deployment, the Ignition User Manual is a helpful companion reference.

Why build MES on Ignition?​

MES needs to sit at the intersection of:

  • shop floor data (PLC/SCADA, equipment events, production signals)
  • manufacturing context (assets, materials, orders, states, genealogy)
  • business systems (ERP, quality systems, reporting, analytics)

Ignition is a strong foundation for that because it’s designed as an industrial application platform with:

  • a server-based Gateway runtime and deployment model
  • modular, integrated feature delivery (drivers, modules, project system)
  • a modern web application framework via Perspective
  • native scripting and integration patterns for custom workflows

Kanoa builds on these fundamentals so we can focus on what’s unique to MES: standardized manufacturing structures and execution logic without forcing customers into a closed or rigid application model.

What 'Ignition-native' means in practice​

Because Kanoa runs on Ignition, your team can treat Kanoa as part of your Ignition ecosystem:

  • Kanoa installs and runs on the Ignition Gateway
  • Kanoa screens and configuration tools are Ignition projects
  • Extensions and customizations are made in the Ignition Designer
  • Custom logic is implemented using Ignition scripting + system.kanoa APIs
  • Integrations use familiar Ignition patterns (gateway scripts, bindings, tags, web services)

Because Kanoa is Ignition-native, teams frequently extend Kanoa with:

  • Custom operator UX (Perspective pages tailored to the plant)
  • Dashboards and KPI views
  • Reporting and analytics
  • ERP transactions and integrations
  • Custom automation logic that fits site-specific workflows