Less repetitive configuration
Import supported PLC structures and build events around the data you need.
For system integratorsEvent Engine® / PLC-to-database middleware
Know the event finished. See where the time went.
Move structured controller data into SQL Server or Oracle, return results to the PLC, and inspect each execution. Event Engine® makes the event visible from trigger through completion.
Windows installer. No request form or sales call required.
What you can evaluate
Three reasons to take a closer look
A result the PLC can check
Return completion status instead of assuming that an event trigger means the work succeeded.
Understand the handshakeBetter fault diagnostics
Review collection, database work and write-back times for individual events.
For plant operationsEnd users / Plant operations
Keep production data dependable.
Investigate timing and failures, understand equipment behavior, and give your team a maintainable integration.
Explore Event Engine® for end users →System integrators / Machine builders
Build an interface you can hand over.
Reuse structures, define completion results, and show customers the evidence they need to support the application.
Explore Event Engine® for system integrators →01 / Less repetitive mapping
When the PLC structure changes, integration should be understandable.
Import supported controller structures and configure events around their members.
Use Logix L5X imports or supported Siemens source files to create reusable definitions. Master Tags can gather the payload as a structure; collections organize multiple tags for an event.
Stored-procedure parameters, table columns and output mappings still need to match your application. Structure import reduces repetitive setup; it does not replace interface design.
Illustrative result-capture event
- PLC payloadUnit ID · operation · measurements · result
- Event configurationCollect inputs and bind the database operation.
- PLC responseReturn outputs and the configured completion status.
02 / Acknowledge, never assume
A trigger is a request. Completion is the result.
- CollectRead the tags needed by the event.
- Do the workExecute the database, label or message operation.
- Write backReturn output values, completion code and status.
Let the PLC sequence respond to the outcome instead of assuming that raising a trigger means the data was saved.
Configure completion and status tags, and define how your control logic handles failures, timeouts and retries. Database work and PLC write-back are separate phases: a write-back failure can occur after database work has succeeded.
Retry and duplicate-handling behavior must be designed with your database operation and PLC handshake. A lost acknowledgement does not prove that the database operation failed.
03 / Measure every event
Troubleshoot the phase that needs attention.
Tag collection
See time spent reading controller values. Investigate controller and network conditions.
Work
See time spent performing the database, print or message operation. Database details separate connection and execution time.
Write-back
See time spent returning values and status to the controller. Inspect failures in their execution context.
04 / Event Health
Successful doesn’t always mean healthy.
An event can keep succeeding while getting slower. Event Health compares recent behavior with earlier executions and surfaces changes worth investigating.
It also distinguishes persistent failures and monitoring problems. It reads recorded telemetry outside the event execution path.
A new installation needs enough executions to establish a baseline. Event Health identifies observed patterns; it does not predict every fault or guarantee warning before downtime.
For plant operations →
05 / What it connects
Use the right interface for the equipment.
| Connection | How it fits |
|---|---|
| Rockwell | Logix-family controllers and Micro800; legacy PLC-5, SLC 500 and MicroLogix through the legacy driver. Logix structure import uses L5X. |
| Siemens S7 | Supported S7 families through reference (absolute) addressing. Symbolic / optimized addressing is not available in the documented release. |
| Modbus/TCP | Coils, discrete inputs and register-based data. |
| OPC UA | Client connectivity through an OPC UA server. OPC Classic DA needs a DA-to-UA gateway. |
| SQL Server & Oracle | Stored-procedure and table operations, with configured input and output mappings. |
| Labels & messages | ZPL label events and email through your SMTP relay. |
Native PLC connections do not need an OPC server. Choose OPC UA when your architecture calls for it, and confirm the exact controller model, firmware and addressing during evaluation.
Where does Event Engine® run?
On a Windows host that can reach the controllers and business systems, with a browser-based configuration interface. Plan the service identity, database permissions, network access, certificates and licensing connectivity with IT.
What can a configured event do?
Typical uses include product-result capture, recipe read-back to the PLC, work-order exchange, label printing and notifications. Database procedures and the control sequence define the application-specific behavior.
06 / Evaluate it on your workload
Prove the integration before expanding it.
Download the installer and evaluate the full event functionality for 30 days. Start with one representative event and define the evidence you need.
- DefineChoose the controller, payload, database operation and required cycle time.
- MeasureRecord phase timings, run counts, failure rates and behavior under representative load.
- ChallengeTest timeouts, unavailable endpoints, write-back failure and recovery behavior in a test environment.
Install on a Windows host that can reach your controllers and database. Follow the setup prompts, then open the Event Engine® web interface to configure your first event. Engineering help is available if you need it.
No request form is required. The trial begins at first run. Scanning is disabled when it expires unless an applicable license is activated.
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
Bring your controller, database and hardest event.
We’ll review the interfaces, the handshake and how to measure success on your workload.
Will Event Engine® fit your equipment?
Run it on a Windows host and review the controller, database, network and handshake requirements before you commit. The documented release supports SQL Server and Oracle; controller interfaces include selected Rockwell and Siemens S7 families, Modbus/TCP and OPC UA. Siemens symbolic/optimized addressing is not supported in the documented release.
The trial is a Windows installer. No sales form is required. Validate your specific controller and application during evaluation.