Why is it a seperate module? | Factry Historian - Event Module

Rather than bake event detection into the core of Factry Historian, this video explains why the capability is offered as a separate, focused module. The goal: give teams a clean, purpose-built interface for tracking and analyzing production events — without cluttering core signal configuration or storage processes.This separation also reflects different user needs. Operators, quality teams, and analysts interact with events differently than system integrators or automation engineers. Keeping it modular makes the tool more usable, more flexible, and easier to evolve based on user feedback.