Scaling across the enterprise

In a real MES rollout, you don't want to build every configuration from scratch. Once you have a good reference implementation for an asset type, you reuse it. This section covers the tools Kanoa provides to speed up deployment, and scripts you can use to build out your system.

• Import/Export. You've imported and exported configuration files throughout the training. These tools move structured configuration between environments, back up configuration, share configured templates, transfer known-good setup patterns, and support deployment workflows — though they aren't always the best option for every scaling task.

• Asset Duplication. One of the most useful tools for scaling within a plant. Duplicating a well-configured asset creates a similar one — useful for multiple machines, pack lines, cells, or production lines — but you still review and adjust anything that should be unique, such as the asset name, tag paths, ERP name, schedule settings, asset-specific custom properties, counter mappings, and state mappings.

• Scripting. Use the system.kanoa script functions to create many similar records, apply configuration across many assets, standardize setup across sites, generate asset-specific configuration from source data, reduce manual clicks, and make rollouts more repeatable. The lessons in this chapter walk through scripts for assets, states, items, and production rates.

tip

Having AI around these days has really made migrating data models rather easy. Our recommendation is to give AI an export of your existing asset model including item, state, standard rate configuration info and also an export of a single asset you've configured in KanoaMES. AI can act as a dynamic ETL to generate an assetExport.json file in the structure our import utility expects.

Use the Kanoa API, not SQL

It may be tempting to use SQL for mass configuration, and that's certainly possible. But Kanoa configuration involves many relationships and application logic. The system.kanoa API follows Kanoa's expected data model, executes application logic consistently, reduces the risk of missing related records, works through supported functions, and keeps the script close to how the product itself performs actions. For bulk configuration, it's generally a better tool than direct SQL inserts.