SMF Architecture:
Four Layers
from ERP to Every Machine
Neotel SMF sits between your enterprise systems and the SMT floor. Master systems keep ownership of orders and master data, one API integration connects them to SMF, and SMF plans every material job and controls each connected machine.
What is the SMF architecture?
SMF (Smart Material Flow) is Neotel’s material-management software for SMT production, running in 500+ factories worldwide. Its architecture has four layers. The master system layer (ERP, MES, SCM, WMS and line management) owns orders, BOMs and master data. The communication layer connects those systems to SMF through API integration: a single, defined interface that carries work orders down and inventory, consumption and job status back up. The SMF layer is the execution layer. It plans material jobs, applies FIFO / FEFO rules, controls MSD floor life and keeps a reel-level UID trail. The equipment layer does the physical work. NEO SCAN registers reels, SMD BOX and NEO LIGHT store and retrieve them, NEO COUNTER counts returns by X-ray, and third-party AMR fleets move material through their own fleet management software.
How is the SMF architecture structured?
How enterprise systems, the communication layer, Neotel SMF software and shop-floor equipment fit together. Arrows show the direction of control; data flows back up every link.
Present step by stepEnterprise resource planning
Manufacturing execution
Supply-chain planning
Warehouse management
SMT line incl. pick-and-place
Single integration point between master systems and SMF · real-time requests and callbacks
Material registration · SCAN / SCAN PLUS
Full-auto storage · SISO to XLR, ONE
Light-guided smart shelving
X-ray counting · X400 / X800
THIRD-PARTY AMR
Dispatch software
Material transport
From ERP to every machine, in four layers
SMF (Smart Material Flow) is Neotel’s material-management software for SMT production, running in 500+ factories worldwide. It connects the systems that plan production with the machines that move material.
- 1Master systems
- 2Communication
- 3Neotel SMF
- 4Equipment
Master systems
Your enterprise and line systems stay the source of truth for what to build and which materials it needs.
- ERP: work orders, BOMs, material master data
- MES: production execution, feeder requests
- SCM and WMS: supply plans, warehouse data
- Line management: SMT line and pick-and-place scheduling
SMF does not replace these systems. It works alongside them.
Communication: API integration
One defined connection point between the master systems and SMF, so every system talks to SMF the same way.
- Down: work orders, BOM, material rules, schedules
- Up: inventory, consumption, job status, exceptions
- Either side: your system calls the Neotel SMF API (included), or Neotel connects to your API (quoted per project)
- Existing systems stay untouched
Neotel SMF: the execution layer
SMF turns orders into material jobs and controls every connected machine.
- Receiving: barcode parsing, unique reel ID, labels
- Inventory engine: FIFO / FEFO rules, cycle counts
- Kitting and dispatch: work-order kitting and return
- MSD control: floor-life tracking, bake-out alerts
- Traceability: reel-level audit trail, dashboards
Equipment
Machines do the physical work. Neotel machines connect to SMF directly.
- NEO SCAN: registers and labels incoming reels
- SMD BOX: fully automatic storage and retrieval
- NEO LIGHT: light-guided smart shelving
- NEO COUNTER: X-ray counting of returned reels
- Third-party AMR: SMF sends transport jobs by API to the fleet management software, which dispatches the robots
One architecture, data in both directions
- Orders flow down from your master systems
- Results flow back up: reel ID, quantities, status
- Fully automatic, semi-automatic or a mix, growing step by step
- Running in 500+ factories worldwide
What Each Layer Does
Clear responsibilities keep the system stable: planning stays in your enterprise systems, execution runs in SMF, and machines do the physical work.
Master System Layer
Your enterprise and line systems remain the source of truth for what to build and which materials it needs.
- ERP: work orders, BOMs, material master data
- MES: production execution and feeder requests
- SCM and WMS: supply plans and warehouse master data
- Line management: SMT line and pick-and-place scheduling
Communication Layer
API integration is the single, defined connection point between the master systems and SMF, so every system talks to SMF the same way.
- Real-time requests and callbacks in both directions
- The API can come from either side: your system calls the Neotel SMF API (included at no extra cost), or Neotel connects to your system’s API (quoted per project)
- Scoped per project to your data model
- Existing systems stay untouched
- Details: SMF System Integration
Neotel SMF Layer
SMF is the execution layer. It turns orders into material jobs and orchestrates every connected machine.
- Receiving, inventory engine (FIFO / FEFO), kitting, dispatch and return
- MSD control with floor-life tracking
- Feeder management and UID traceability
- All modules: SMF Modules
Equipment Layer
Neotel machines connect to SMF natively. Third-party AMR fleets connect through their own fleet management software.
- NEO SCAN registers and labels incoming reels
- SMD BOX and NEO LIGHT store and retrieve materials
- NEO COUNTER counts returns with X-ray
- AMR: SMF sends transport jobs by API to the fleet software
| Layer | Owns | Sends down | Sends up | Examples |
|---|---|---|---|---|
| 1 · Master systems | Orders, BOMs, master data | Work orders, BOM, material rules, schedules | (top layer) | ERP, MES, SCM, WMS, line management |
| 2 · Communication | The connection between systems | Requests from master systems | Callbacks from SMF | Neotel SMF API (included) or your system’s API (quoted per project) |
| 3 · Neotel SMF | Material jobs and inventory state | Machine commands, transport jobs | Inventory, consumption, job status, exceptions | Receiving, inventory engine, kitting, MSD control, traceability |
| 4 · Equipment | Physical material handling | (bottom layer) | Reel UID, quantities, scan and count results | NEO SCAN, SMD BOX, NEO LIGHT, NEO COUNTER, third-party AMR |
What data moves between ERP, MES and SMF?
Instructions travel down from the master systems; results and status travel back up, so every system sees the same material picture.
Down: from master systems
Up: from SMF and equipment
SMF complements your existing line systems; it does not replace them.
Which equipment route fits my line?
The same SMF architecture runs a fully automatic line, a semi-automatic line, or a mix, and grows step by step.
Fully automatic
For high-volume plants that want minimal manual handling.
Semi-automatic
Lower entry cost with light-guided, human-machine collaboration.
With AMR transport
Material moves between storage and the line by robot.
SMF Architecture FAQ
Common questions about how SMF fits into your factory systems.
What is MES integration in an SMT material system?
MES integration connects the system that runs production with the system that manages materials. In the SMF architecture, the MES sits in the master system layer and connects to SMF through API integration. The MES sends work orders and feeder requests; SMF returns reel IDs, issued and remaining quantities, and job status. Both systems then see the same material picture without manual data entry.
Does SMF replace our ERP, MES or WMS?
No. Master systems keep ownership of orders, BOMs and master data. SMF is the execution layer: it turns those orders into material jobs, controls the machines and reports results back. It works alongside the systems you already run.
Which system owns inventory master data, SMF or our WMS?
Decide this before integration starts. When SMF and a WMS both touch inventory, one must be the master for each data type, such as on-hand quantity by location. Neotel engineers map this with your team during project scoping.
Does API integration cost extra?
It depends on whose API is used, because the API can come from either side. If your ERP, MES or WMS connects to the Neotel SMF API, the API is included at no extra cost. If Neotel needs to connect to your system’s API, that interface work is quoted as part of the project scope.
Can we start semi-automatic and upgrade to fully automatic later?
Yes. Both routes run on the same SMF architecture. Semi-automatic (NEO SCAN, NEO LIGHT, NEO COUNTER X400) suits 1 to 3 lines, with typical payback in 6 to 12 months. Fully automatic (NEO SCAN PLUS, SMD BOX, NEO COUNTER X800) suits 3 or more lines, with typical payback in 12 to 18 months. You can upgrade step by step without changing the master-system integration.
How do AGV or AMR robots connect to SMF?
Through the robot vendor’s fleet management software. SMF sends transport jobs by API (origin, destination, reel ID, priority) to the fleet software. That software plans paths and dispatches the robots, then reports job status back to SMF.
Do we need an MES to use SMF?
No. SMF can run with an ERP only, or on its own. Without an MES, work orders come from the ERP through API integration or are created directly in SMF, and SMF still handles receiving, storage, kitting, return and traceability. An MES can be connected later through the same API integration.
How long does an SMF integration project take?
It depends on the project scope: how many master systems are connected, how much data they exchange, and how many lines and machines are involved. A standalone SMF with Neotel equipment needs no master-system integration, while each connected ERP, MES or WMS adds scoping, interface work and testing. Neotel engineers confirm the timeline after a scoping review and deliver the project in phases with defined milestones.
Does SMF run on-premise or in the cloud?
Both are possible. SMF can be installed on servers in your factory or hosted in the cloud. The right choice depends on your IT policy, data-security requirements and how many sites you run.
More questions about deployment, security and training? See the SMF FAQ.
Map SMF onto Your Factory
Tell us which master systems and equipment you run. Our engineers will show where each sits in the four layers and what an SMF rollout looks like for your lines.
