Manual Data Entry

Using a form to collect ad-hoc information into a database makes data access easy and effective.

In the example, the operator fills out the daily form while performing their rounds and then Stores the edits over the network or wirelessly to a central database.

The drop-down lists and value limits are used to limit or contain the data entry.

In treatment facilities it is usual to analyze samples for compliance to regulations.

This example is used in a laboratory to record the results as they become available.

The blue cells guide the user to the input fields. The form contains yellow cells which contain formula that depend on the values entered.

When complete, the operator Stores the edits over the network or wirelessly to a central database.

Forms generated automatically by process conditions are partially filled out, leaving the remaining fields of the form to the operator.

In this example, the alarms database is monitored periodically for a critical alarm. When a critical alarm is detected, a form is produced and automatically populated with the date and tag of the alarm.

Incomplete forms are listed in the Input Panel. The user selects an entry, adds comments and Stores the edits over the network or wirelessly to a central database.

When the form is complete, it is removed from the list by clicking the Lock pushbutton which prevents any further edits.

Forms generated automatically by process conditions are partially filled out, leaving the remaining fields of the form to the operator. In practice, the detection of the events is either by the XLReporter scheduler or by a third-party software interface.

In this example, the runtime of the compressors is monitored periodically for the exceedance of a specified condition e.g., runtime hours. When the condition is met, a maintenance form is produced with the runtime hours automatically populated.

Like the Alarm Notification example, the form is selected from a list in the Input Panel. The operator acknowledges the checks performed during the maintenance, adds notes and records other current running conditions.

Tabular forms are common, each row of the table representing data. In practice, the table rows are spaced periodically.

In this example, a daily form is filled out every 4 hours with the turbidity readings of the process, entered in the blue cells.

The form is filled out incrementally over the day. The Max column is read only and uses workbook formula to derive their values.

Process data can be accessed automatically to partially fill a row in a form.

In this example, a monthly form is updated every day. The values entered can be manual or a combination of manual data and values automatically retrieved from the process. When process data is used, it is added to the form automatically, with the option to edit anomalies.

The input to the form uses drop-down lists and limits the values to certain ranges and selections. On completion of the report, XLReporter can save it as an eDMR XML file and submitted to the States web site.

An operator logbook allows shift/daily tickets to be created when condition occur in the process that the operator needs to report. These tickets can be shared from shift-to-shift, day-to-day.

In this example, all the tickets that are “open” are displayed for the date specified. Since there are numerous data items in a ticket they have been arranged in multiple rows and also grouped by “report” items and “action” items.

When a ticket is opened, the user enters the information and selects Store, which stores the edits to the database and creates a new blank ticket. When the actions taken for remedy or comments are added, they also become part of the ticket.