Infor M3 contains the standard hours your operators are supposed to hit. Getting that data onto the production floor — in real time, without manual re-entry — is a problem most M3 customers have not solved.
M3 stores routing data, work center assignments, and standard hours per operation. That data is exactly what a takt time system needs. The problem is that M3 was not designed to push that data to shop-floor displays in real time.
Most facilities work around this by exporting standard hours to Excel weekly and updating a manual board or spreadsheet. Operators work against numbers that may be a week out of date, and any new MO that wasn't in last week's export is missing entirely.
TaktClock's M3 adapter uses a direct SQL/ODBC read connection to M3_ODS — the operational data store that M3 maintains as a read-optimized copy of its operational data. No API licence is required. The connection reads standard hours, MO routing, and work center data directly.
The adapter runs on the TaktClock server and refreshes on a configured schedule. When an operator selects an MO and subprocess, TaktClock looks up the expected standard hours from the M3 data and uses that as the target for the live timer. No manual entry. No weekly export.
When a new MO is released in M3, the standard hours are available in TaktClock on the next refresh cycle — without anyone updating a spreadsheet. When routing changes in M3, the takt targets update automatically.
Operators always see current standard hours. Supervisors see live session data measured against current M3 targets. The CI engineer's Yamazumi is built from actual elapsed time compared to actual M3 standard hours — a comparison that has never been possible without significant custom development.
30 minutes. Live screen share. We'll configure it against your areas, your processes, your standard hours.