QAD

Enterprise ERP

Overview

Keep Enterprise Planning and the Shop Floor in Sync

The Redzone–QAD integration ties together QAD Adaptive ERP, QAD EAM, and the Redzone Connected Workforce Platform through the QAD Integration Platform. An order released in QAD shows up as a scheduled run in Redzone; a run finished in Redzone posts back to QAD. Nobody retypes it. It runs on Redzone’s REST API v2 and the Snowflake-based analytics warehouse. Manual entry drops, as do the errors that come with it, and finance sees the cost of a stoppage while the line is still down instead of at month end.

Key Features

QAD
Redzone

Production Scheduling Sync

When a planner releases a production order in QAD, it lands in Redzone as a scheduled run. Operators see what’s next without a supervisor loading it by hand.

QAD
Redzone

Automated Production Declaration

Finished goods, scrap counts, and run completions post back to QAD ERP as they happen, so inventory reconciles against real output rather than a day-old count.

QAD
Redzone

Maintenance Action Synchronization

A maintenance request in Redzone opens a QAD EAM work order on its own. Status and comments stay matched in both systems, so nobody re-enters them.

Analytics
EAM

Production Loss & Downtime Enrichment

Root-cause downtime data from Redzone Analytics (Snowflake) writes into the EAM record, so each stoppage carries the real duration and reason instead of a guess.

QAD
Redzone

Financial Cost Integration

Product cost from QAD ERP feeds Redzone, so a line stoppage shows what it costs while it is happening, right on the floor.

How It Works

Technical Architecture & Workflow Mechanics

The Redzone–QAD integration runs on standardized protocols and needs the following components in place before configuration begins:

Component
Requirement
QAD ERP Version
QAD Adaptive ERP (AWS Hosted) — AUX or EE versions
QAD EAM Version
Standard QAD EAM compatible with the QAD Integration Platform
APIs Required
Redzone REST API v2 (Scheduled Runs, Maintenance Actions, Comments)
Data Access
ODBC/JDBC connection to Redzone Analytics Snowflake warehouse
Middleware
QAD Integration Platform using OAuth 2.0 client credentials

Workflow Mechanics

  1. Scheduling

    When a production order is released in QAD, the platform maps SKUs and line configurations to Redzone External IDs and creates the scheduled run. If the order changes before the run starts, the integration updates or deletes the run to match.

  2. Maintenance

    A "NEW" status on a Redzone maintenance request creates a work order in QAD EAM. The EAM Work Order ID goes back into Redzone as a comment, so the two records stay linked, and technician notes from EAM show up on the operator’s iPad.

  3. Analytics

    About 20 minutes after a run ends, the platform queries the Snowflake v_losses view, pulls the root-cause downtime detail, and writes it into the matching EAM record for a complete, accurate asset history.

Requirements

  • Active licenses

    A current QAD Integration Platform license and Redzone API credentials (REST API v2).

  • Master data alignment

    Cross-references between QAD Sites/Domains and Redzone Organizations/Enterprises, set before go-live.

  • EAM customization

    A custom field in QAD EAM to hold the Redzone Work Order UUID, which is what lets the two-way sync work.

Getting Started

  1. Contact Us

    Book a meeting with a QAD Integration Specialist to discuss your goals and confirm fit.
    Schedule a call

  2. Select Your Workflows

    Choose from the validated list — Production Scheduling, Automated Declaration, Maintenance Sync, Loss & Downtime Enrichment, and Financial Cost Integration — based on your operational priorities.

  3. Review Quote & Purchase

    Confirm the project work order, which lays out total project fees, hourly rates for integration engineers, and delivery milestones.

  4. Configuration & Testing

    We fit the solution to your environment in three steps:

    • Build: Field mappings, such as Redzone Assets → EAM Equipment IDs.
    • Test: Unit and smoke testing in a DEVL/TEST staging environment.
    • Validation: SME sign-off on mapping logic and API credentialing (OAuth tokens and Snowflake routes).

Frequently Asked Questions

Didn’t find what you need? View the full FAQ.

What is the refresh rate for downtime data?

Redzone Analytics (Snowflake) refreshes on about a 20-minute cadence. The integration waits for that window to close before it updates the EAM record, so the downtime entry is complete.

Can we sync comments between operators and maintenance technicians?

Yes. Comments move both ways. A technician’s note in QAD EAM shows up on the operator’s iPad in Redzone, and the operator’s observation shows up on the EAM work order, so both teams stay current without switching systems.

Does the integration handle changes to scheduled production orders?

Yes. If a production order changes in QAD ERP before its run starts in Redzone, the integration updates or deletes the scheduled run to match. The floor works from the current schedule without anyone stepping in.

I’m interested. What should I do first?

Redzone builds and manages this integration around your QAD environment and shop floor workflows. Book a meeting with a QAD Integration Specialist or contact your Redzone Account Manager to get started.