Import & Export

Set it up in your plant

Setting up Import & Export in your plant. Import & Export brings in any file your plant has (an ERP's export, a legacy system's, a supplier's list) as CSV or Excel through a mapping from its columns to a model's fields, and exports a model the way the system on the other side reads it.

1. Install itIT

   On the plant's OpenCore MES server, in its plant folder: sign in once with a licence token from your account at suites.opencoremes.com (one token per installation: production, test, training), install the suite, then restart OpenCore MES (opencore-mes start, or the service that runs it). The start log then lists it.

   opencore-mes suite login

   opencore-mes suite install import-export

2. Pick the first file and its modelEngineering

   Start with one file that is sent today by hand (the ERP's work orders, the material master, the supplier list), a sample of it, and the model it fills.

3. Map it as part of the model's designDesigner

   Object editor → Import & Export tab: each field from a column (matched by name where it can), value translations (the file's KG is your kg), a value when blank, the date format and decimal comma, the row the column names are on; a script to reshape or refuse rows if needed, with its test cases. The model's stewards approve the mapping with the model.

4. Try it, then apply itProduction

   Data → Import with mappings: preview the file through its mapping (each row checked as the person importing, refusals with the file's row numbers), then apply. The same file applied twice writes nothing twice; where the model's design asks for approval, the change waits for it.

5. Export for the other sideEngineering

   Export the model through the same mapping as CSV, its columns, values, dates and decimals as the other system writes them, for the ERP or a customer.

6. Make it routineIT

   Agree with the other system's owner where the file comes from and how often; keep a sample file with the mapping's test cases so a change in their format is caught at review, not at the import.

The same guide is in FLAMES once the suite is installed: Designer, From the suites, Set-up guide.