How SAP B1 Shop Floor Data Collection and Machine Monitoring connects to SAP Business One
Custom Business One add-on over the Service Layer
The vendor describes a build-to-order add-on using Business One's Service Layer, which is the REST and OData interface to Business One objects. The browser terminal reads production orders and routing operations and writes back time and quantity data. Because it is custom, confirm who owns the code, how it is versioned and how it is retested after a Business One upgrade.
What data moves
| From | To | Data | When |
|---|---|---|---|
| SAP Business One | Operator terminal | Released production orders, routing operations, work centers, standard times | Operator opens the terminal or selects a job |
| Operator terminal | SAP Business One | Clock-on and clock-off times against operations | Operator starts or stops an operation |
| Operator terminal | SAP Business One | Good quantity and scrap quantity per operation | Operator reports output |
| SAP Business One | OEE report | Routing standards used as the performance baseline | OEE calculation or report refresh |
Setting it up
- 1Define the scope in writingAgree which operations, work centers and scrap reasons the terminal covers. Build-to-order work needs a precise statement of what is included.
- 2Clean routings and standardsOEE is only as good as the routing times and work center capacity in Business One. Review them before the terminal goes live.
- 3Set up users and Service Layer accessCreate a limited integration user and decide how operators identify themselves at the terminal, for example badge or PIN.
- 4Place terminals on the floorChoose tablets or industrial PCs, arrange network access and secure kiosk mode for the browser.
- 5Define scrap and downtime codesAgree a short, usable list. Long lists lead to operators picking the first option.
- 6Pilot on one work centerRun for a few weeks, compare recorded times to supervisor observation and tune OEE definitions.
What usually breaks
- !OEE computed from poor routing standards looks precise but misleads, so fix standards before trusting the numbers.
- !Operators forgetting to clock off inflate run time and depress OEE for the operation.
- !Custom add-ons can break after a Business One upgrade or Service Layer change, so plan regression tests.
- !Scrap reported without a reason code removes the information needed to act on it.
- !Machine monitoring claims need a clear source of machine states. If it is manual, availability data will be approximate.
A private AI layer across both systems
Plain-language OEE questions
A private assistant reading Business One and terminal data can answer questions such as which work center lost the most time on scrap this week, and show the data it used.
Anomaly review of clock data
It flags operations with missing clock-offs, impossible durations or repeated overrides so supervisors can correct them before payroll or costing.
Standards versus actuals
It compares actual run times to routing standards by item and work center and drafts proposed routing changes for engineering to approve.
Try it here, free
SAP B1 Production Order Cost Variance Calculator
Compare actual to standard on a closed production order and see how much of the variance is material, labor rate and labor efficiency.
When something else fits better
- A dedicated MES with machine connectivity may be better if you need automatic machine states rather than operator-entered data.
- Business One's own production order reporting with manual issue and receipt can be enough for simple, low-volume shops.
- A tablet-based form tied to a spreadsheet can be a short-term bridge before commissioning a custom add-on.
Frequently asked questions
Is this an off-the-shelf product?
The vendor describes it as build-to-order, so scope, support and upgrade handling are agreed per project. Ask for clear documentation of what is built and who maintains it.
How is OEE calculated?
The vendor says OEE is computed from routing standards and operator-recorded time and quantities. The quality of the result depends on your routings and on operators recording data consistently.
Does it connect to machines directly?
The listing describes an operator terminal, so machine data may be operator-reported. If you need automatic machine signals, discuss that explicitly with the vendor or consider a dedicated MES.
Where would AI help here?
A private assistant can read Business One production data and terminal records on your own servers to explain losses and flag data errors. Changes to production records stay with a human reviewer.
Pairing documented at ecosire.com/apps/sap-business-one/sap-b1-shop-floor-data-collection . SAP B1 Shop Floor Data Collection and Machine Monitoring is a product of ECOSIRE; Netray is independent and not affiliated with either vendor.