AI VisionComputer VisionIDP

AI Vision for AS/400 (IBM i) Automation

Traditional approaches to AS/400 (IBM i) automation chain two brittle systems together: OCR templates that break when document layouts change, and coordinate-based scripts that break when screens change. legacy bridge replaces both with AI vision - a single intelligent system that reads documents like a human, understands green screens semantically, and maps data from one to the other based on meaning, not position.

Why traditional automation breaks

  • OCR templates are rigid - one template per document layout. A new vendor invoice format means a new template to build and test
  • Screen-scraping scripts use hardcoded row/column coordinates. A single field added to an AS/400 (IBM i) screen breaks the entire automation
  • Two separate fragile systems (OCR + scripting) multiply failure points and maintenance burden
  • Error recovery is scripted - unexpected screens, validation messages, or workflow branches cause silent failures or incorrect entries

How AI vision automation works

1

Document understanding

AI vision reads and comprehends the full document - not just individual characters. It understands that “Total Due” next to “$4,327.50” is an invoice total, regardless of where on the page it appears. It handles layout variations, poor scan quality, mixed fonts, and handwritten annotations without per-document configuration.

2

Screen understanding

The AI reads your AS/400 (IBM i) green screen semantically, identifying input fields by their labels and surrounding context - not by row and column coordinates. When your screen displays “Customer Number . . .” followed by an input field, the AI knows that field expects a customer number. If the screen layout changes, the AI adapts.

3

Intelligent mapping

AI matches extracted document data to terminal fields based on meaning. The “PO #” on an invoice maps to the “Purchase Order Number” field on screen, even if labeled differently. This semantic matching eliminates the brittle field-mapping configurations that traditional integrations require.

4

Adaptive entry

The AI handles real-world complexity that breaks scripted automation: unexpected confirmation prompts, validation error messages, multi-screen workflows with conditional branches, and screen variations between AS/400 (IBM i) program versions. It reads and responds to each screen in real time rather than following a fixed path.

AI vision vs. traditional automation

legacy bridge AI Vision
Traditional (OCR + scripts)
New document layout
Yes

Works automatically

No

Build new OCR template

Screen change
Yes

Adapts via semantic reading

No

Update coordinate mappings

Error messages
Yes

Reads and responds in real time

No

Script each error case

Maintenance
Yes

Self-improving, minimal upkeep

No

Ongoing template + script updates

What AI vision delivers

No templates

Works with any document layout from any source. New vendors, new forms, new formats - no configuration required per document type.

No scripts

No coordinate-based screen automation to write or maintain. The AI navigates AS/400 (IBM i) screens by understanding their content, not memorizing their layout.

Self-improving

The system learns from corrections and edge cases. Extraction accuracy and screen navigation improve over time as the AI processes more of your specific documents and workflows.

End-to-end

A single intelligent system from document intake to AS/400 (IBM i) data entry. No OCR-to-script handoff, no intermediate data transformation, no integration middleware.

See AI Vision in Action

Watch legacy bridge read a document and enter data into a live AS/400 (IBM i) screen. No templates, no scripts - just AI.

The legacy bridge team at work