The illustrative situation
A terminal manually matches operator references before registration, handles corrections elsewhere and reports movements separately. This describes a potential application, not an actual implementation or customer result.
Proposed journey
Scope one operator, TOS interface and pre-advice/amendment sequence. Define unit and service references and exception ownership. Assess the SIMPLE exchange separately against its documentation and data sources.
What to verify
Test valid pre-advice, an unmatched reference and later correction. Staff should understand registration and review. Outbound events should represent confirmed facts rather than treat forecasts as executed movements.
How to assess it
Review re-entry, reference enquiries and pending responses using comparable samples. These are proposed criteria, not achieved savings. The offer names SIMPLE scope and TOS-maintainer involvement.