SHOP-FLOOR & WAREHOUSE AUTOMATION

Infor Factory Track.
Shop-floor & warehouse automation.

Connect material movements, production activity and labour capture to your ERP. MetaDynamic helps you implement Infor Factory Track with practical operator workflows, suitable devices and clear transaction controls.

Business-led design · Integration · Adoption & support
Manufacturing and distribution operations for Infor Factory Track implementation
From business plan to execution
01Receive & move02Start & report work03Capture time04Update ERP

THE BUSINESS FOUNDATION

Factory Track and MES: choose the right operational scope.

Infor Factory Track focuses on manufacturing automation, warehouse mobility, labour and time capture. Supported modules and transactions depend on the connected ERP and product version. It helps operators record activity closer to the work itself.

Infor MES is a separate product, with a broader manufacturing execution scope including production monitoring and equipment data collection. We assess the requirement before recommending Factory Track, MES or a combination of systems; these names are not interchangeable.

Infor Factory Track: connected priorities
BUSINESS INPUTReceive & move
Infor Factory TrackProcess · Data · People
02Start & report work
03Capture time
04Update ERP

CAPABILITIES

What Infor Factory Track can enable.

The implementation scope is selected around your operating model, product capabilities and business priorities.

Warehouse mobility

Assess mobile receiving, inventory and shipping transactions supported by your ERP integration.

Barcode workflows

Design scanning steps, labels and validation rules that make material identification dependable.

Shop-floor reporting

Capture relevant job, labour and material transactions using suitable operator workflows.

Time & attendance

Evaluate time capture, attendance rules and labour reporting within the selected module scope.

ERP connectivity

Define transaction ownership and monitor the supported flow of information to and from the ERP.

Operational controls

Plan permissions, device use, exception correction and transaction reconciliation.

ADVANCED BY DESIGN

Design for the operator, the device and the real environment.

A warehouse scanner and a shared production terminal have different needs. We test the full interaction: identification, scan quality, task sequence, feedback, exception handling and the resulting ERP transaction.

Device readiness

Validate scanners, terminals, labels and network coverage against the chosen workflow.

Transaction integrity

Define how duplicate scans, rejected transactions and corrections are handled and reviewed.

Product-fit assessment

Separate warehouse and labour capture requirements from machine monitoring or broader MES needs.

METADYNAMIC SERVICES

From first assessment to everyday support.

Choose a focused Infor Factory Track engagement or a phased programme covering implementation, integration, adoption and support.

Operational assessment

Map current paper forms, scans and manual ERP transactions.

Workflow configuration

Configure the agreed warehouse, shop-floor and time-capture scope.

ERP integration validation

Confirm supported versions, interfaces and transaction behaviour.

Device & label readiness

Coordinate hardware requirements, label content and practical trials.

Pilot & operator training

Test one representative work area before wider rollout.

Support & improvement

Monitor recurring issues and refine workflows under change control.

OUR DELIVERY APPROACH

Progress with clear decision points.

Each stage ends with a review of deliverables, risks and readiness. Business owners stay involved from discovery through stabilisation.

  1. 01Observe workAgree scope and accountable owners.
  2. 02Define flowsValidate the data and working assumptions.
  3. 03ConfigureBuild the agreed process and solution.
  4. 04Test devicesTest realistic orders and exceptions.
  5. 05PilotPrepare users and confirm readiness.
  6. 06Roll outReview outcomes and controlled improvements.

DESIGNED AROUND YOUR CONTEXT

Start with the work that matters most.

Map the solution to the people, transactions and operational constraints that shape your organisation.

01Discrete manufacturers02Warehouse operations03Assembly plants04Multi-shift factories

Our discovery sessions establish process ownership, integration boundaries and acceptance criteria before configuration begins.

PLANNING & COMMERCIAL CLARITY

Know the scope before you commit.

Confirm the supported ERP, Factory Track version, modules, users and device requirements. Include implementation, connectivity, label design and support responsibilities. Do not assume that a Factory Track licence includes the separate Infor MES product or every equipment integration.

Scope & dependencies

Document the sites, users, processes, integrations and data that the proposal covers.

Delivery & acceptance

Tie each workstream to testable deliverables, named owners and explicit exclusions.

Support & change

Agree support coverage, escalation, release responsibilities and the improvement backlog.

YOUR QUESTIONS ANSWERED

Infor Factory Track: frequently asked questions.

Is Factory Track the same product as Infor MES?

No. Factory Track and Infor MES are separate products. Factory Track centres on manufacturing transactions, warehouse mobility and labour/time capture; MES addresses a broader manufacturing execution and monitoring scope.

Which ERP systems can it connect to?

Integration support depends on the Factory Track product and version. We verify the exact ERP, release, modules and supported transactions before committing to scope.

Do operators need barcode scanners?

Device choice follows the workflow. Scanners, touch terminals and other supported devices are evaluated for the operating environment and transaction requirements.

Does it automatically monitor every machine?

No. Equipment monitoring should not be assumed from a transaction-capture implementation. We assess MES, supported connectivity and any additional components separately.

Can we capture labour and attendance?

Relevant labour and attendance capabilities are available through the appropriate module scope. Rules, approvals and downstream reporting requirements need configuration and validation.

How should rollout begin?

Use a representative work area to test devices, labels, data quality and operator steps. Expand only after the transactions and exception handling work reliably.

Replace delayed entries with dependable capture.

Show us one warehouse or shop-floor process. We will help identify the right automation scope and pilot approach.