How MachineMetrics connects to Infor VISUAL
Prebuilt Clickable Connector on an edge device
The vendor describes a prebuilt connector that runs on an edge device inside your plant, pulling work orders and schedules from the ERP to operator tablets and sending production and labor data back. VISUAL is documented separately from SyteLine, so follow the VISUAL-specific documentation.
Machine data acquisition
Machine signals are collected on the same edge layer from controls and PLCs, so cycle counts, states and downtime reasons can be tied to the active work order.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Infor VISUAL | MachineMetrics | Open work orders, operations, part numbers and schedules | Connector sync on a schedule |
| MachineMetrics | Infor VISUAL | Quantities produced, labor and operation status | Operator transactions on the tablet |
| Machine | MachineMetrics | Cycle counts, run and stop states, downtime reasons | Continuous from the edge device |
Setting it up
- 1Inventory machines and controlsList each machine, its control or PLC and how its signals can be read. Old machines may need extra hardware.
- 2Install the edge devicePlace the edge hardware on the plant network with outbound access as required by the vendor, and agree the firewall rules with IT.
- 3Configure the ERP connectorCreate the service account in VISUAL with the needed rights, set up the connector and test pulling open work orders.
- 4Map work centers to machinesMap VISUAL resources and work centers to monitored machines so work orders show on the right tablets.
- 5Define downtime reasons and shiftsAgree the downtime reason list and shift calendars so OEE is calculated the same way operators and finance expect.
- 6Decide labor posting rulesDecide whether operator transactions post to VISUAL automatically or via approval, and how corrections are made.
- 7Pilot on a few machinesRun a few machines first, validate quantities against VISUAL, then roll out.
What usually breaks
- !Work centers in VISUAL do not match physical machines one to one, so work orders appear on the wrong tablet.
- !Operator discipline: if operators do not start and stop jobs on the tablet, labor and quantities are wrong in both systems.
- !Cycle counts from the machine differ from good parts reported by the operator because of scrap and setup pieces.
- !OEE is calculated with a different planned production time than the ERP calendar, so the numbers cannot be reconciled.
- !Service account password changes or rights changes in VISUAL silently stop the sync.
- !Posting labor automatically without review writes errors straight into job costing.
A private AI layer across both systems
Downtime and scrap explanations
A private assistant reading machine states and VISUAL job data can answer why a job ran long: setup time, a recurring stop reason, or a routing standard that is out of date.
Reconciling machine counts to ERP quantities
List jobs where machine cycle counts and reported quantities differ beyond a tolerance, for a supervisor to review.
Routing standards review
Compare actual cycle times from machine data with VISUAL routing standards and draft proposed corrections for approval, never writing to the routing automatically.
Try it here, free
Infor VISUAL SQL Query Generator for Work Orders
Build a SQL Server query for open or late VISUAL work orders by filling a few fields, then copy it into your query tool.
When something else fits better
- VISUAL's own shop floor data collection may be enough if you only need labor and quantity, not machine states.
- Another MES or machine monitoring product can fit if you need quality, tooling or traceability in the same system.
- A manual downtime log on a few bottleneck machines is a cheap start before investing in sensors.
Frequently asked questions
Does MachineMetrics support Infor VISUAL?
The vendor lists connectors for Infor ERPs, and documents VISUAL separately from SyteLine. Confirm the current VISUAL version and the exact scope of the connector with MachineMetrics before purchase, since sync scope can differ by ERP.
Where does the connector run?
On an edge device inside your plant, according to the vendor. That keeps machine signals local and lets the connector reach your ERP. Your IT team should review the network paths, outbound connectivity and credentials involved.
What does the ERP get back?
Work order progress such as quantities and labor, according to the vendor description. Which transactions post automatically and which are reviewed first is a configuration choice that should be agreed with production and finance.
Pairing documented at www.machinemetrics.com/integrations/erp/infor . MachineMetrics is a product of MachineMetrics; Netray is independent and not affiliated with either vendor.