eForms: Electronic forms & logbooks

Bring operator entries and automated plant data into a structured digital record. eForms gives operations teams web-based forms, connected data capture, and a permanent history of activity.

Discuss eForms

Build the form around the work.

Start with the information your team needs to record. eForms provides no-code and low-code tools for creating operational forms and making them available through a web interface on the plant floor.

A form can capture a complete entry in one pass or guide a record through a sequence of steps. This gives you room to represent both a simple log entry and a process in which information is collected as the work progresses.

Employees and connected systems can contribute to the same record. Decide what an operator needs to enter and what can be collected automatically, then configure the form around that division of work.

Connect operator entries with plant data.

Some information comes from the person doing the work. Other information is already available in a control system, database, or external application. eForms can bring those inputs together in a shared digital record.

Scripts and triggers support automatic log entries when defined events occur. Operator-driven steps can remain part of the workflow wherever manual input is needed.

Plant systems: Map OPC data to module alias tags so information from the operation can be used within your forms and automation.
Databases and web services: Retrieve information through SQL queries and REST or SOAP services. Record data from connected applications on the eForms ledger.
Scripts and triggers: Configure logic to gather relevant data and create automatic entries. DSI can help define the connections and triggers around your process.

Keep the record and its review together.

Once an entry is committed to the eForms digital ledger, it remains there permanently. Supervisors can add comments and approve entries, keeping the review associated with the recorded activity.

Permanent entries: Committed ledger entries cannot be deleted. Manual input and automatically captured data become part of the operational record, giving your team a lasting history of what was logged.
Comments and approval: Supervisors can review the recorded information, add comments, and approve entries. The review becomes part of the record rather than a separate conversation to track down later.

Configuration changes are also captured in the system audit log, so the history covers changes to the setup as well as the entries your team makes.

Start with an existing logbook or workflow.

Form design · Data connections · Automation

Bring a form your team already uses and walk us through who completes it, where the information comes from, and how it is reviewed. That provides a practical starting point for configuring eForms.

DSI can help design the forms, connect the data sources, and develop scripts for the steps you want to automate. The implementation discussion covers both the people using the forms and the systems supplying information.

Bring your logbook or workflow.

Talk with DSI about the records your team keeps and where automated data capture would help.