Manual Entry Forms

what is a manual entry form? a manual entry form is a structured interface in factry historian that allows users to manually input data, either as part of an event or directly as time series data these forms are used when data cannot be collected automatically, but is still important for operational insight, traceability, or reporting why does it matter? not all critical process information comes from machines, for example because (older) equipment is insufficiently instrumented manual entry forms allow you to record lab results or operator observations add reasons to downtime events or process transitions digitize paper logs ensure traceable, timestamped input that becomes part of the historian’s dataset with manual entry forms, this source of data is no longer scattered or lost it becomes part of the structured, queryable data layer in the platform how does it fit in the system? factry historian supports 2 t ypes of manual entry forms event forms and asset property forms event forms these forms are used to add manual data within the context of an event they are tied to the event’s time window and linked to the asset and event type you can use them to, for example add a root cause or reason code fill in operator comments enter periodic values during a long running event (e g lab samples during a production run) there are two subtypes simple a single value for a property, captured once for the event (e g a final quality check) periodic multiple values captured over time within the event duration (e g lab samples during the run) grouping of properties event forms can group related event properties visually and functionally this helps structure complex forms into logical sections example groups in a batch form process values temperature (collected automatically at first, but editable) lab values moisture viscosity ph quality check approved (yes/no) grouping improves readability, guides users through the form, and enforces consistency across similar event types example an operator enters root cause "material jam" (by selecting from a dropdown) comment "foreign object in hopper" (by typing) moisture readings 11 2%, 10 9%, 11 0% (entered at different timestamps during the event) all this data is stored as part of the event’s structured properties and can be queried in panels, dashboards and reports just like with automatically generated event data asset property forms these forms are used to input time series data in context of an asset each submission results in one or more values being written to the time series database with a timestamp, similar to data collected via collectors you typically use them to, for example, record manual readings from equipment that is not network connected these values are available in dashboards, queries, and calculations just like any other measurement or calculation example a utility manager enters asset property bod (which is an asset properties docid\ cr6hbrdsl8fsuvlvm20if linked to the waterpurification bod measurement on the manual collector) value 6 8 mg / l timestamp 2025 08 15 14 00 this value is written as a point on the waterpurification bod measurement using this timestamp/value pair and can be displayed in the water purification performance dashboard when you use it use event forms when adding human input to an ongoing or completed event manually creating, editing and completing an event use asset property forms when recording timestamped values that are not tied to a specific event capturing data that should be available alongside sensor measurements in dashboards or reports traceability audit logging and rollback all manual form submissions in factry historian are audit logged this includes who submitted or modified the form and form fields when the change was made what fields were changed and their original values this ensures full traceability, whether for compliance, investigation, or change tracking in addition, factry historian supports rollback of manual changes if a value was entered incorrectly or modified later, you can view the full change history revert to a previous version restore original or earlier values where necessary this makes manual data entry a safe and reversible operation, not a blind overwrite common misconceptions manual forms do not store unstructured notes each form field maps to a measurement or an event property in factry historian asset property forms and event forms are not interchangeable their use depends on whether the data is tied to an event or stands on its own data entered manually is still treated as part of the system’s traceable, queryable dataset best practices choose the right form type based on context use event forms for contextual data and asset property forms for standalone data use validation rules to enforce ranges, formats, and required fields avoid mixing too many unrelated fields in the same form instead, group forms by use case or operational area more information configuring a manual entry form docid\ dwiqpowhuce2htr xooa8