PI Vision manual data entry
Create a controlled manual input table so operators can enter and review values for multiple assets from one PI Vision workflow.
A manual input table is useful when a team needs to record operator observations, production values, quality checks, or other approved data against several assets. The goal is not simply to place editable fields on a display. A reliable workflow makes the asset context obvious, validates the input, records who changed it, and keeps the resulting data available for later analysis.
Plan the table around the data-entry decision
Define the assets
Choose the asset list and make the row context visible. Operators should never have to guess which unit a value belongs to.
Define the fields
Use clear labels, units, expected ranges, and a consistent time basis for every value the operator enters.
Define ownership
Decide who may enter, edit, approve, or review values before the table is placed into production use.
Start with a small controlled table: prove the asset context, validation, and persistence workflow with a few rows before expanding to a larger operational display.
Build a multiple-asset input table
Choose the asset context
Use an AF element, asset list, or another approved context source. Keep the selected asset visible above the table and in any confirmation message.
Add one row per asset
Give each row a stable asset name and avoid relying on position alone. Sorting or filtering should not change the meaning of a saved value.
Add typed input controls
Use numeric, text, date, or choice inputs that match the field. Do not accept free-form text where a controlled selection is required.
Save with confirmation
Provide a clear save action, show the target asset and field, and make success or failure visible to the operator.
Make the table easy to review
| Column | Purpose | Example |
|---|---|---|
| Asset | Stable row context | Unit 01 |
| Field | What is being recorded | Operator check |
| Value | Entered data | 42.5 |
| Unit / range | Interpretation and validation | °C / 0–80 |
| Timestamp | When the value applies | Shift handover |
A table should make incorrect entry harder. Place units next to the input, show required fields, retain the relevant timestamp, and avoid a layout where the save action is separated from the row being edited.
Validate before writing data
Required values
Prevent an incomplete row from being submitted when the workflow requires all fields.
Ranges and formats
Reject values outside the approved range and provide an explanation that helps the operator correct the entry.
Permissions
Use the PI Vision and PI System permissions appropriate for the write operation. Test with the same role used by operators.
Separate validation from approval
A value can be syntactically valid and still require review. If the process needs approval, represent that state separately instead of treating a successful write as automatic approval.
Test the complete workflow
Enter a normal value
Confirm that the value is written to the intended asset and field.
Test an invalid value
Confirm that the table blocks or explains the invalid entry without writing partial data.
Test multiple rows
Save two or more assets and verify that each value remains associated with the correct row after refresh.
Review the result
Open the resulting data in the approved trend, table, or audit workflow and confirm the timestamp and user context.
Common problems to avoid
Ambiguous rows
If asset names are clipped or repeated, operators can write the right value to the wrong unit.
Hidden save state
Users should know whether data is still local, being submitted, saved, or rejected.
No recovery path
Document how to correct an entry and how reviewers can identify the original value and subsequent change.
Make manual entry dependable
Use a clear asset context, controlled fields, validation, permissions, and a visible review path when building an input table in PI Vision.
Explore Vision Library+
