The systems you already run, read where they are

A system not named here is usually still readable through one of these three. Product names are the trademarks of their owners and are named only to describe the systems VERUS can read; no endorsement is implied.

Several ERPs, companies and plants in one installation. A system replaced partway through its history. Huge tables. Custom fields. Codes nobody documented. Several currencies. Shifts that cross midnight. Schedules kept outside the ERP. Each of these is handled as a setting, never as custom code for one customer.

Fiscal calendars (calendar months, 4-4-5, 4-5-4 or 5-4-4) are a setup choice. Every site has its time zone, and VERUS knows whether each system stores times in UTC or in local time. It will not assign an event to a shift until both are known, because getting that wrong is the most common silent error in plant reporting.

• On-time delivery is measured against the promise made when the order was entered, not the promise as it stands today.
• Build completion uses the schedule as it stood at the start of the day.
• Any breakdown by cause code comes with a check on how concentrated the codes are.

When one of these is in doubt, it is the first thing the answer says. On the demonstration, 1,252 order lines had their promise date moved to the ship date after shipping. VERUS measures against the original promise and says why.