Before work starts
Check operation eligibility, routing, recipe context, work-order rules, product status and material expiry where applicable.
IntelliTrack™ / Manufacturing execution & traceability
Trace the product. Control the next step.
Connect each unit or lot to its operations, materials, recipes and results. Investigate quality and apply configured rules before work continues or product ships.
01 / Investigate the record
A suspect lot. A customer complaint. Where do you start?
Follow the recorded relationships instead of rebuilding the story from controller logs and spreadsheets.
Trace a finished unit back to its components and material lots, or explore where a suspect item was used. Inspect the operations and process values behind the result, then manage quarantine and disposition.
Traceability depends on the identities, consumption and production events captured by your integration.
- IdentifyStart with the affected serial number or material lot.
- TraceFollow genealogy and inspect the production record.
- ContainUse quarantine and disposition to manage the investigation.
See quarantine in the product
02 / Enforce while it’s cheap
Catch the wrong condition at the station.
A record is more useful when it can influence the next operation. IntelliTrack™ checks configured conditions at production check-out, check-in, component consumption and shipping verification.
As results are recorded
Evaluate required attributes and limits and check required components at the relevant production step.
Before shipment
Verify shipping eligibility and the effect of holds or disposition before releasing product.
Define the rules. Connect them to the line.
Your process configuration and machine integration determine which checks apply and how the equipment responds. A software rejection only prevents movement when the control sequence honors it.
For example, a Hold blocks shipping but does not inherently block work. Static BOM and dynamic BOM checks apply at different points in the workflow.
Evaluate recipes, BOM enforcement, OEE and the complete workflow →03 / Preserve the context
A measurement means more when you know what it belongs to.
- ProductSerial number or lot and material relationships.
- OperationEquipment, process, work order and recipe context.
- ResultRecorded attributes, limits, time and outcome.
That context supports product history, WIP, OEE and quality reporting — and gives AI a defined record to work from.
04 / AI grounded in reports
Ask the question. Follow the evidence.
AI Insights can use manufacturing reports the user is permitted to access and link answers to the saved report runs used.
Explore a change in yield, throughput or equipment behavior, then inspect the underlying report. Treat the response as an analysis to review, with the evidence available for checking.
- Your provider accounts: configure connections, models, routing and budgets.
- Your egress settings: control whether images and user-entered free text may be sent.
- Your memory policy: require human approval before remembered items enter future context.
AI assistance is optional. Provider calls send permitted context outside the application to the configured provider. Core production, traceability and reporting do not require an AI provider.
Google Gemini, xAI and MCP Agent Access are scheduled for October 16, 2026. Include provider choice and external-agent access in your IntelliTrack™ evaluation.
05 / For regulated manufacturing
Validation should not begin with a blank document.
Start with a version-specific validation library, reusable tests and a Coverage Register. Generate draft packages from your User Requirements Specification (URS).
- Find the testsBrowse the Document Library and function-to-test coverage without AI.
- Build a draftThe optional AI-assisted generator selects library tests for IQ, OQ, PQ, FAT, SAT and a traceability matrix; optionally include an FRS.
- Review and executeYour validation team completes, executes and approves the documents under your quality system.
Electronic signatures, role controls, audit trails and tamper-evidence verification support controlled workflows. Their suitability depends on your configuration, procedures and validation.
Generated packages are drafts. They do not execute tests, mark them passed, or establish regulatory compliance.
Review your validation workflow06 / Fit & deployment
Build around the operation you have.
A strong fit for detailed production records
Serialized assembly and test, material genealogy, recipe-controlled operations, and plants where quality investigations span several systems.
Your infrastructure
A Windows-hosted web application with SQL Server data storage. Scope authentication, backups, retention and network access with your IT team.
Integration has a defined scope
Connect equipment and ERP workflows around the production record. Agree on identifiers, data ownership, interfaces and failure handling before implementation.
Do we need Event Engine® as well?
Event Engine® can handle controller-to-database events in a combined solution. Whether it is required depends on your equipment and existing integration. We’ll review that architecture with you.
Can we use IntelliTrack™ without an AI provider?
Yes. Core execution, traceability and reporting do not require provider-based AI. The Document Library is also available without AI; AI-assisted package generation requires a configured provider connection.
Why Factory Data Systems
The people behind the product matter.
We built these products from the integration problems we kept meeting on the plant floor. Our starting point is your process, the evidence you need, and the systems you already run.
Work directly with FDS or through your system integrator. Discuss the configuration with an engineer, define what success means, and evaluate it against your own production requirements.
Meet the company and our principles →Start with one problem
Show us the question your manufacturing record cannot answer.
Bring an example product, a traceability gap or a production rule you need to enforce. We can walk through the relevant workflow and discuss the integration it needs.