# AI for ECI Macola, from Progression Series to Macola 10

> Source: https://netray.co/erp-ai/eci-macola-ai-integration
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: AI for ERP

## Short answer

Macola shops split between the legacy Progression Series on Progress OpenEdge and the newer SQL Server-based Macola 10 / Macola ES, and both leave day-to-day questions, backorders, on-hand, open POs, answered by whoever knows the Order Entry and Inventory Management screens or can run Visual Integrator. A private AI layer grounded on either database answers those questions directly, triages VI job failures, and helps with the data-quality work that any eventual migration off Progression Series will require.

## Kind

platform

## Erp Family

other

## Erp Products

- ECI Macola
- Macola Progression Series
- Macola 10
- Macola ES

## Industries

- Distribution
- Manufacturing
- Durable Goods

## Region

Global

## Persona

IT Director

## Eyebrow

ECI Macola + private AI

## Intro

Macola has been through more database and branding changes than most ERPs still in production use: Progression Series running on the Progress OpenEdge database, and the newer Macola 10 (built on Macola ES) running on SQL Server. A lot of distributors and manufacturers are still on Progression Series, often on a version no longer actively enhanced, which creates real anxiety about where to invest next without committing to a full re-implementation.

Day to day, the friction is familiar to anyone who has run Macola for a while: a customer service rep needs to know what is on backorder, a controller wants to know what purchase orders are overdue, and the honest way to get that answer is to open the Order Entry or Inventory Management screens, or run a Crystal Report someone built years ago. There is rarely a quick, self-service way to just ask.

Visual Integrator, Macola's native import/export tool, is the backbone of most integrations and data movement, and it is usually maintained by one long-tenured person who understands both the VI job definitions and the underlying schema. When a VI job fails silently, tracking down why can eat an afternoon, and it is a real key-person risk if that person is unavailable.

None of this requires jumping straight to Macola 10 or a different ERP. A private model grounded on your existing database, whether that means an OpenEdge connection for Progression Series or SQL Server for Macola 10, can answer operational questions in plain language today, and the same connector work pays off directly when it is time to plan a Progression Series to Macola 10 migration.

## Pain Points

### Progress OpenEdge is invisible to most modern BI and AI tooling

**Detail:** Progression Series customers run on a database most reporting and AI tools don't speak natively, so answers depend on canned Crystal Reports or manual Visual Integrator exports.

### Basic order and inventory questions require screen knowledge

**Detail:** Backorder status, on-hand quantity, and open PO questions need someone who knows the Order Entry and Inventory Management screen sequence, not a quick natural-language answer.

### Legacy Progression Series shops face real migration anxiety

**Detail:** Many installs are on a version no longer actively enhanced, and moving to Macola 10 is a real project, which leaves IT unsure where to invest in the meantime.

### Multi-warehouse or multi-entity rollups are manual

**Detail:** Distributors running more than one warehouse or entity get consolidated views by hand, since Visual Integrator jobs are built for data movement, not cross-entity reporting.

### Visual Integrator and report knowledge is a key-person risk

**Detail:** VI scripts and Crystal Report layouts are usually maintained by one long-tenured employee. When something breaks and that person is out, everyone waits.

## Use Cases

### Natural-language order and inventory queries

**Description:** Customer service and operations staff ask directly for backorder status, on-hand quantity, or open PO age, against either Progression Series or Macola 10 data.

**Erp Objects:** Order Entry (OE) and Inventory Management (IM) records, purchase order data

**Outcome:** Answers in seconds instead of navigating Macola screens or waiting on a report

### Visual Integrator job failure triage

**Description:** Explains why a VI job failed or produced unexpected results by reviewing the job log and comparing source and target record counts.

**Erp Objects:** Visual Integrator job definitions and logs, source/target table data

**Outcome:** Faster diagnosis of VI failures without depending on the one person who wrote the original job

### Customer credit-hold and order-exception assistant

**Description:** Flags orders stuck on credit hold or exception status and explains why, pulling the relevant credit and order history together.

**Erp Objects:** Accounts receivable and credit records, sales order status

**Outcome:** Faster resolution of held orders that would otherwise sit until someone manually investigates

### Job costing and manufacturing variance explainer

**Description:** For Macola manufacturing module customers, explains variances between actual and standard cost by job or work order.

**Erp Objects:** Bill of materials, routing, job costing actual vs. standard cost records

**Outcome:** Controllers get the driver behind a variance instead of just the total dollar difference

### Legacy-to-Macola 10 migration data-quality copilot

**Description:** Reviews Progression Series code tables and master data, flags orphaned records, duplicate customers/items, and inconsistent codes ahead of a Macola 10 migration.

**Erp Objects:** Progress OpenEdge master data tables, customer/item/vendor code tables

**Outcome:** Cleaner migration source data and fewer surprises found mid-cutover

### Vendor and PO expedite assistant

**Description:** Identifies purchase orders at risk of late delivery against open sales demand and drafts the vendor follow-up.

**Erp Objects:** Purchase order records, vendor confirmation data, sales order demand

**Outcome:** Purchasing catches at-risk POs earlier, reducing rush freight and stockouts

### Month-end close checklist and GL summary

**Description:** Summarizes the month-end close checklist status and flags open reconciling items across GL, AP, and AR.

**Erp Objects:** General ledger, accounts payable, and accounts receivable records

**Outcome:** Controllers get a same-day view of what is still open instead of chasing status by email

## Architecture

**Overview:** The model reads from either the Progress OpenEdge database (Progression Series) or SQL Server (Macola 10/ES), maps Macola's OE/IM/PO vocabulary into plain language, and answers through retrieval and text-to-SQL, with the connector explicitly aware of which database generation it is talking to.

**Layers:**

#### ERP connectors

**Detail:** OpenEdge ODBC/JDBC access for Progression Series, or SQL Server access for Macola 10/ES, kept to a reporting-only credential.

#### Data and semantic layer

**Detail:** Maps OE, IM, PO, and job costing tables and code tables into business vocabulary, accounting for customization common in older installs.

#### Model serving

**Detail:** An open-weight model served privately on customer-controlled hardware or a single-tenant private cloud.

#### Retrieval and agents

**Detail:** Text-to-SQL over order/inventory/PO data, plus a VI job-log analysis tool for integration troubleshooting.

#### Governance and audit

**Detail:** Read-only by default, with query logging suited to an environment where one legacy system may be mid-migration to another.

## Deployment Options

### Air-gapped on-prem

**Fit:** Distributors and manufacturers already running Progression Series or Macola 10 on their own servers

**Detail:** Model and connector run alongside the existing database server or on a nearby machine inside the same network, no cloud dependency required.

### Private cloud

**Fit:** Companies consolidating infrastructure or planning a Macola 10 cloud-adjacent hosting move

**Detail:** Data replicated into a single-tenant private cloud where the model runs, separate from any shared service.

### Hybrid

**Fit:** Groups mid-migration from Progression Series to Macola 10 that need both systems queryable during transition

**Detail:** Connectors to both OpenEdge and SQL Server run in parallel until cutover is complete.

## Compliance

### Industrial distributors and manufacturers touching controlled parts keep order and inventory data inside a private or on-prem boundary rather than a shared AI service.

**Framework:** ITAR / EAR

### On-prem or private-cloud deployment satisfies data-location requirements some distribution customers include in supply agreements.

**Framework:** Customer data residency clauses

### For PE-owned or audited companies, read-only access and logged queries keep the AI inside existing change-control expectations for financial systems.

**Framework:** SOX-adjacent financial controls

### The same governance used for day-to-day queries doubles as documentation of the data-cleansing work performed ahead of a Macola 10 migration.

**Framework:** Data quality controls ahead of migration

## Integration Notes

Progress OpenEdge requires its own ODBC/JDBC driver and connection approach, distinct from the SQL Server access used by Macola 10/ES; confirm which generation you are on before scoping.

Visual Integrator is the native ETL tool in most Macola shops; reviewing existing VI job definitions is usually the fastest way to understand what data paths already exist before building new ones.

Macola 10's newer API and data model differ meaningfully from legacy Progression Series screens and tables, so mapping work is not directly reusable across the two.

Heavy per-customer customization is common in older Progression Series installs; budget discovery time for code tables and custom fields specific to your instance.

Write-back should go through Visual Integrator import jobs or a supported API, not direct table writes, particularly on OpenEdge where schema assumptions are easy to get wrong.

If a Macola 10 migration is on the roadmap, sequence the AI connector work to double as migration data-quality tooling rather than building it twice.

## Product Fit

### ERPray

**Why:** Macola is not a listed connector today; question-answering over order, inventory, and PO data is built on ERPray's ERP-agnostic connector architecture.

### Custom build

**Why:** The OpenEdge-versus-SQL-Server split and heavy per-shop customization typically call for purpose-built connectors rather than a one-size mapping.

### DataRay

**Why:** Useful where document-heavy AP or vendor correspondence needs to be combined with Macola's structured order and PO data.

## Engagement

### Discovery

**Duration:** 2-3 weeks

**Deliverables:**

- confirm Progression Series vs. Macola 10/ES and database access path
- review existing Visual Integrator jobs
- prioritized use-case list
- migration roadmap alignment if applicable

### Pilot

**Duration:** 6-8 weeks

**Deliverables:**

- private model stood up
- connector to OpenEdge or SQL Server
- 2-3 use cases live (order/inventory query, VI triage)
- IT and operations feedback loop

### Production

**Duration:** 4-6 weeks

**Deliverables:**

- governance and logging hardened
- credit-hold and PO expedite assistants rolled out
- staff training
- role mapping to Macola permissions

### Scale

**Duration:** ongoing

**Deliverables:**

- migration data-quality copilot if moving to Macola 10
- job costing variance use case
- month-end close summary agent
- quarterly use-case review

## Buyer Questions

- Do you have real, hands-on experience with Progress OpenEdge, or only SQL Server-based Macola?
- Does the AI ever write to our live database, or is it strictly read-only?
- Can this run fully on our own network with no outbound cloud dependency?
- How do you handle the difference in schema between Progression Series and Macola 10 if we migrate mid-project?
- Who audits what the AI queried and what answer it produced?
- Can the work double as data-quality preparation for a future Macola 10 migration?
- How do you plan to handle our specific customizations to the standard Macola schema?

## Faq

### Can AI be added to Macola Progression Series, which runs on Progress OpenEdge?

**Answer:** Yes, though it requires an OpenEdge-specific database connection rather than the SQL Server access used by newer Macola 10 installs. Once connected, a private model can answer order, inventory, and PO questions directly from Progression Series data just as it would from Macola 10.

### What is the fastest AI win for a Macola shop?

**Answer:** Natural-language order and inventory queries, such as backorder status or open PO age, are usually fastest to stand up because that data is already well structured in the OE and IM modules. Most shops see a working pilot within six to eight weeks.

### Can AI help troubleshoot Visual Integrator job failures?

**Answer:** Yes. By reviewing the VI job log and comparing source and target data, a model can explain likely causes of a failed or partial run, reducing dependency on whichever single person originally wrote the job.

### Does this help if we're planning to migrate from Progression Series to Macola 10?

**Answer:** It can. The same connector and mapping work used for day-to-day AI queries can be extended into a data-quality copilot that flags orphaned records, duplicates, and inconsistent codes ahead of a migration, reducing surprises during cutover.

### Is this safe for a distributor with customer data residency requirements?

**Answer:** Yes, when deployed on-prem or in a private single-tenant cloud with no data sent to a shared external AI service. That satisfies data-location clauses that many distribution and manufacturing customer agreements already include.

### Does ECI Macola have a native AI copilot already?

**Answer:** ECI has been modernizing parts of the Macola line, particularly around Macola 10, but a broad natural-language AI layer grounded on order, inventory, and job costing data is not a standard out-of-the-box feature as of this writing, especially for Progression Series customers.

### What does it cost to add AI to a Macola environment?

**Answer:** For a single-database pilot (either Progression Series or Macola 10) covering two or three use cases, expect a cost comparable to a focused mid-size integration project. OpenEdge connectivity and heavy customization can add to discovery time and cost.

## Search terms

ECI Macola AI, Macola AI integration, Macola Progression Series AI, on-prem AI for Macola, Macola 10 AI, Macola copilot, Macola generative AI, Macola Visual Integrator AI, Progress OpenEdge AI, Macola natural language query, distribution ERP AI, private LLM Macola

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json