QFactory MES features and implementation

Different screens. One connected record.

Each team can use the screen it needs while every record remains tied to the same order, item, and production lot. The screen and owner may change, but customer promises, specifications, cost, and results stay in the same work context.

01Order
02Purchasing
03Inventory
04Work order
05Production result
06Inspection
07Shipment and cost

What QFactory manages

The work at the center of daily operations is grouped into eight areas.

Master data

Manage items, partners, BOMs, routings, warehouses, equipment, and inspection standards.

Sales and purchasing

Handle orders, due dates, purchase requests, purchase orders, receipts, and returns.

Inventory

Review receipts, issues, transfers, and on-hand stock by warehouse, location, and production lot.

Production

Record plans, work orders, material issues, output, defects, and completion status.

Quality

Manage incoming, in-process, and final inspection, nonconformance actions, and traceability.

Equipment and molds

Record equipment and part structure, daily inspections, repair and maintenance history, and operating hours. Track mold usage, storage, transfers, and changeovers.

Cost

Combine material, labor, equipment, and overhead records for costing and period close.

Operations board

Review production, quality, equipment, delivery, and cost status in one place.

QFactory modules

The QFactory menu grouped by category and module, with the screen count and representative screens of each module.

Master data 139 screens

Maintain companies, plants, business partners, items, BOMs, routings, warehouses, equipment, and inspection rules in one place.

System administration 62 screens

Manage companies, plants, users, roles, menus, permissions, notifications, logs, and system settings.

Purchasing 23 screens

Convert purchase requests into orders, then process arrivals, receipts, returns, and supplier transactions.

Sales 14 screens

Manage sales orders and due dates, then update production plans and inventory with shipment and return records.

Inventory 17 screens

Track receipts, issues, transfers, on-hand balances, stock movements, lots, and physical counts by warehouse and location.

Production 29 screens

Create work orders from production plans and record material issues, work progress, output, defects, and completion status.

Mold management 6 screens

Check mold locations and balances, then record transfers, usage, and work history.

Quality 13 screens

Record incoming, in-process, and final inspections, and manage nonconformance, claims, and lot traceability.

Equipment 18 screens

Register equipment structures and parts, then record inspections, repairs, maintenance, operating time, and digital asset data.

Projects 7 screens

Register project tasks, schedules, owners, and progress for manufacturing and customer work.

Costing 8 screens

Calculate material, labor, equipment, and overhead costs, and manage accounting periods, allocation rules, and closing history.

Monitoring 24 screens

Review production, quality, equipment, sensor, delivery, and cost indicators on operational dashboards.

Work management 7 screens

Manage assigned work and progress in the project center, work board, daily log, and weekly status views.

QFactory product screens

Manage work orders, inventory, inspection, and equipment information in QFactory.

Work orders in QFactory — **Work orders**Quantities and current progress

Inventory history in QFactory — **Inventory history**Receipts, issues, transfers, and shipments by production lot

Inspection history in QFactory — **Inspection history**Results, disposition, and follow-up history

Equipment registration in QFactory — **Equipment registration**Structure, location, and data points

Configure first. Customize only where required.

Start with QFactory's standard functions. We add only the screens and rules required by your process or equipment.

Standard product

Configure existing QFactory functions to match the organization's operating standards.

Operation-specific functions

Add only the screens and rules that the process or equipment genuinely requires.

Equipment integration

Collect values from PLCs, sensors, barcodes, and cameras, then link them to work and quality records.

Review, configure, validate, and hand over

QFactory has many screens, but you do not need to adopt all of them at once. We begin with the functions the current operation needs.

01
Review the floor and records
Review current spreadsheets, documents, equipment, and systems, then define the first scope to change.
02
Configure and connect
Configure standard functions and implement only the screens, system links, and equipment connections the scope requires.
03
Validate with users
Test the flow with real items and work records, then let shop-floor users verify the result.
04
Accept and hand over
Meet the agreed acceptance criteria, then hand over training, operating documents, and the support scope.

What we review before quoting

We review your data, required screens, existing systems, and equipment links before setting the schedule, estimate, and support terms.

Initial scope

Start with the work that breaks most often and the systems or equipment that must connect. Defer the remaining functions to later stages to keep the first scope practical.

Inputs needed to start

We need item and BOM data, process and inspection rules, users and roles, real order and work examples, and existing-system interface information before confirming scope.

What determines time and cost

Data readiness, screen and rule differences, migration volume, ERP or MES integration, PLC and equipment protocols, infrastructure, and training all affect the schedule and estimate.

Support response terms

Before service begins, the contract and operating guide define incident severity, intake channel, owners, initial response times, and the boundary between remote and on-site support.

Define support and recovery responsibilities before go-live

We define server, integration, backup, and support conditions for the operating environment.

Backup and security

Document backup frequency, recovery steps, account roles, and remote-access boundaries before the contract is finalized.

Operating support

Agree on the owners and scope for health checks, incident response, changes, and user training before go-live.

Review AI drafts and trace vision results to their sources.

AI prepares master-data drafts from documents for people to review before saving. Vision results remain linked to source images for later review.

See what manufacturing AI does

QFactory screen creating a master-data draft from a document — A master-data draft created from values read in a document

QFactory implementation FAQ

The questions we hear most about scope, schedule, cost, and existing-system integration.

How long does implementation take?

Timing depends on the work in scope, the state of your data, and the number of equipment links. After a site review, we provide a schedule and training plan.

How is the cost calculated?

We size the required functions with the function point method. Hosting, equipment links, AI servers, data migration, and custom work are priced as part of the agreed scope.

What happens to our existing ERP or MES?

We first review how each system is used. Keep the functions that still work, then connect or move only the records that need to join QFactory.

What is the implementation sequence?

We organize master data and the production workflow first. Then we add equipment links and automation. AI comes later, once the records it needs are reliable.

What happens before the project starts?

We visit the site and review the actual work, documents, systems, and equipment. Those findings define the first scope and acceptance criteria.

Do you deploy in the cloud or on-premises?

Cloud is the default because maintenance and updates are simpler. We can also install on premises when company policy or site conditions require it.

QFactory connects operationsfrom order to shipment.