QAD | Redzone Bets on Manufacturing Intelligence to Turn ERP Into a System of Action

Key Takeaways

⇨
QAD | Redzone has unveiled Manufacturing Intelligence, a cross-system intelligence layer it expects to bring to market in spring 2027.

⇨
The layer runs a five-step loop of see, understand, decide, act, and confirm, and is designed to work across other vendors' systems as well as QAD's own.

⇨
New AI agents for ERP, the shop floor, ERP modernization, and trade compliance were announced alongside it.

QAD | Redzone unveiled Manufacturing Intelligence on September 22, 2026, at its Champions of Manufacturing event in Chicago, describing it as an intelligence layer that works across manufacturing processes, workflows, and systems.

According to the company announcement, the layer is meant to move manufacturers from systems that record what happened to systems that recommend and carry out what should happen next. It builds on the existing QAD | Redzone Manufacturing Platform, which combines Adaptive ERP, Redzone Connected Workforce, supply chain planning, and ChampionAI. Event attendees saw a preview, and the company expects the product to be in market in spring 2027.

QAD | Redzone also said it plans to integrate NVIDIA technology to help build what it calls a federated intelligence layer, one that understands manufacturing context across systems.

Manufacturing Intelligence Runs a Five-Step Loop on Plant Data

In a QAD blog post, Chaitanya Josyula, head of product for platform and Manufacturing Intelligence, describes the layer as a continuous loop: see, understand, decide, act, and confirm.

He illustrates it with scrap. The system detects that scrap on a work center is drifting upward and links the drift to a specific shift, material lot, or tool nearing end of life. It then recommends a response, such as early tool replacement or an inspection hold. Within guardrails the customer sets, it can generate the maintenance work order or route the lot for inspection, and finally show whether the scrap rate came back down.

QAD | Redzone argues that general-purpose AI can spot that a number moved but lacks the context to judge whether it matters. The company says its layer draws on operating data from more than 6,000 plants and decades of work in automotive, life sciences, food and beverage, industrial, and high-tech manufacturing.

Built for Mixed System Estates, Dependent on Data Quality

Manufacturing Intelligence is designed to extend beyond the QAD | Redzone stack, so manufacturers can apply it without first replacing the systems they run, including ERP from other vendors. Josyula notes that output quality depends on the data underneath, pointing to clean data models, standardized processes, and well-defined schemas. He adds that there is no required starting point: a manufacturer might begin with its ERP backbone, the frontline, or a single workflow such as procurement.

New Agents Cover ERP, the Shop Floor, and Global Trade

Alongside the vision, QAD | Redzone announced agents it positions as ways to create value now. Champion Assist brings AI into everyday Adaptive ERP work, with persona-based agents for procurement, sales, sourcing, and accounts payable. Lynx Champion analyzes legacy customizations to speed ERP modernization.

Redzone added frontline agents for roles including line lead, operations manager, and inspector. A Trade Compliance Champion automates product classification and trade document work.

What This Means for ERP Insiders

Data foundations set the ceiling. QAD | Redzone ties the quality of Manufacturing Intelligence to clean data models and standardized processes. ERP teams that tidy master data and process definitions before spring 2027 give the layer stronger signals to work from when it arrives.

A single high-friction workflow is a practical first step. The company says there is no fixed starting point. Piloting an available agent on a workflow with a measurable cost, such as scrap, procurement, or trade classification, gives ERP teams evidence to judge the broader layer on.

Guardrails need owners before agents act. The loop’s act step runs within limits the customer defines. Agreeing early on who sets those limits, and how confirmed outcomes are reviewed, lets ERP and operations teams expand automation with shared confidence.