Skip to content
Software AthleteSoftware Athlete
Quick Input+: Revolutionizing Data Input in PI Vision

Quick Input+: Revolutionizing Data Input in PI Vision

PI Vision manual data entry

Quick Input+ gives PI Vision users a controlled way to enter, adjust, and validate operational values without leaving the display.

PI Vision is excellent for seeing process data, but many operations also need a safe way to record a value, change a limit, acknowledge a condition, or enter context that does not arrive automatically from a source system. Quick Input+ adds configurable input controls directly to the display so operators can work in the same visual context as the process.

Input should be part of the workflow

A useful input control does more than accept a number. It should make the target clear, match the data type, provide immediate feedback, and fit the permissions and review process around the value.

What Quick Input+ can handle

Numeric values

Enter a measured or planned value with a field, step input, slider, or other control that fits the operating range.

Selections

Use dropdowns, lists, switches, or toggle buttons when the allowed values are known and should be easy to choose.

Contextual updates

Keep the input beside trends, status indicators, and related symbols so the user can understand the context before submitting.

Why direct data entry improves operations

  • Faster response: operators can make an approved adjustment without switching tools or hunting for a separate form.
  • Better context: the display can show the current trend, asset, limits, and status beside the input control.
  • Consistent interaction: configurable controls can match the value type and the language used by the team.
  • Improved traceability: values can be captured as part of a defined workflow with appropriate timestamps, permissions, and review.
  • Lower error risk: constrained choices and visible validation make invalid or ambiguous input less likely.

Choose the right input control

1
Use a numeric field for precise valuesChoose a numeric input when the user needs to enter an exact temperature, pressure, target, or other value.
2
Use a slider for bounded adjustmentsSliders work well when the range is known and the user benefits from seeing the relative position of the value.
3
Use a list or dropdown for allowed statesMake approved modes, statuses, or categories selectable instead of asking users to type them manually.
4
Use a switch or toggle for a clear choiceBinary decisions are easier to review when the control makes the active and inactive states unmistakable.

Design an input display operators can trust

Manual input belongs in a visual workflow, not as an isolated control. Pair each Quick Input+ control with enough context to answer three questions: what am I changing, what is the current state, and what will happen after I submit it?

Label the target

Show the asset, attribute, unit, and purpose near the control. Avoid relying on a symbol title that can be missed at a glance.

Show limits

Where appropriate, show acceptable ranges or a related status so users can recognize an unusual entry before it is saved.

Confirm the result

Use feedback, timestamps, trends, or an audit-oriented symbol to make the submitted value visible after the action.

Permissions are part of the user experience. A control should not imply that every viewer can write. Align PI and AF permissions with the workflow, and test the display with the same role that operators will use.

Common operational use cases

  • Record a manual measurement when an instrument is unavailable or a field check is required.
  • Adjust an approved process target or operating limit during a controlled change.
  • Select the current production mode, batch state, or operating condition.
  • Enter a reason code or status that gives downstream analysis more context.
  • Support a shift handover by recording a concise operator update beside the process view.

Validate before rollout

Start with a small, non-critical workflow and test the complete path. Confirm the target, value format, permissions, save behavior, feedback, and downstream visibility. Then have an operator use the display without assistance and note where the intent or result is unclear.

A simple acceptance checklist

  • The control identifies the correct asset and attribute.
  • Allowed values and units are obvious.
  • Invalid or unauthorized input is rejected safely.
  • The saved value appears in the expected trend or detail view.
  • The team knows who owns the configuration and how changes are reviewed.

Quick Input+ is most effective when it is treated as an operational control, not just a convenient widget. Give the input a clear purpose, place it beside the process context, and test the full workflow with the people who will use it.

Bring controlled input into PI Vision

Explore Quick Input+ and build clearer, more actionable data-entry workflows for your PI Vision displays.

Explore Vision Library+
Leave a comment

Your email address will not be published..

Cart 0

Your cart is currently empty.

Start Shopping