Events

what is an event? an event is a time bound occurrence linked to an asset it describes something that happened in your process, such as a production batch, alarm , or maintenance activity events have a start time and end time, and can include additional information like type, reason codes, batch ids, duration and other properties data from events can come from the historian, stored as measurements docid\ xqwlemdcnfff3 0h gmms or calculations docid\ opiodkgnngyjedx6zkg d (directly or as asset properties docid\ cr6hbrdsl8fsuvlvm20if ), external databases, or manual entry why does it matter? time series data in factry historian shows how values change over time events give meaning to those changes by describing what happened and when they help you analyze unplanned downtime (what are the main reasons for it?) track product changes or operator shifts (what was the batch id at this point in time?) identify causes of performance loss (did we notice a blocking event somewhere?) create timelines and contextual reports (show me the output kpis for last week's production for article x) events turn raw data into information you can act on by giving it context how does it fit in the system? events are always linked to an asset and exist alongside measurements, calculations and asset properties they are used to describe specific time intervals of interest there are four main ways events are triggered automatically, based on logic applied to measurements or calculations (e g when the status tag goes to a 'running' state) automaticaly, based on a schedule (e g a shift schedule) automatically, by importing from external systems (e g an mes) manually, by users entering or editing events each event has start and end timestamps an event type a trigger an event can have zero or more simple properties (e g the batch id or total energy consumption) zero or more periodic properties (e g temperature sampled throughout the batch) a parent event (e g a cip cycle could be an event as part of a larger 'batch' event) unlike measurements, events describe something that happened over a period of time for a specific asset, rather than individual values example you configure an event type called linestop, which is triggered when the line speed is below 0 1 for more than 60 seconds if the line stops at 13 12 20 and starts again at 13 18 05, an event is generated type linestop start 2025 08 12 13 12 20 end 2025 08 12 13 18 05 duration 5 minutes 45 seconds asset line3 conveyor orderid l131 abc reason insufficient feed material this event is now available in dashboards, reports, and can be used for performance analysis when you use it you will use events when building shift or batch reports monitoring machine stops or alarms investigating root causes of production loss visualizing state transitions on a timeline tagging data with context for future analysis you also use event configurations to define how automatic events should be detected common misconceptions events are not time series they represent a start and end time, not a sequence of values they are not limited to stops or batches any condition or change can be an event if it matters to your operation event logic does always run in real time in some cases, events are backfilled or reprocessed manual and automatic events can coexist and may describe overlapping time periods however, an event type can only be configured once per asset best practices use clear names for event types and event properties configure metadata when configuring event properties, so that these are automatically reflected in the panels when querying data use the 're evaluate' functionality to reprocess events over time, when trigger logic or additional properties have been added, and after validation more information configuring an event docid\ e9bjftgiz2m1bxqppz3qx adding event properties docid\ vuiy 3wpadt19eeu 4uci trending events docid 31eldakbd7k4wr tsp ku