OUI, EAPWebManager, and EAP System Landscape

OUI, EAPWebManager, and EAP System Landscape A architecture diagram generated by Archify. Browser-facing presentation Equipment integration boundary Operator / Engineer · tablet or desktop browser · Browser-facing presentation Operator / Engineer tablet or desktop browser IIS / nginx edge · HTTPS, proxy, SPA hosting · Browser-facing presentation IIS / nginx edge HTTPS, proxy, SPA hosting OUI SPA · Vue, Vuetify, Pinia · Browser-facing presentation OUI SPA Vue, Vuetify, Pinia OUI access service · identity, sessions, tickets · Architecture component OUI access service identity, sessions, tickets EAPWebManager · WebSocket, routing, persistence · Architecture component EAPWebManager WebSocket, routing, persistence SQL Server · accounts, rules, tool types, history · Architecture component SQL Server accounts, rules, tool types, history PLUS transport · S99F97W / S99F98 · Equipment integration boundary PLUS transport S99F97W / S99F98 Equipment EAP · authoritative process state · Equipment integration boundary Equipment EAP authoritative process state Equipment · load ports and control · Equipment integration boundary Equipment load ports and control MES / factory systems · lot and process integration · Equipment integration boundary MES / factory systems lot and process integration HTTPS static application session and ticket API typed WebSocket protocol single-use binding ticket accounts and ticket hashes configuration and history commands and events EUI message bridge equipment control and state factory transactions Legend Frontend Backend Database Security Message bus External

Presentation Ownership

  • • OUI is the current operator-facing UI
  • • The edge provides same-origin HTTPS and proxy routes
  • • The access service owns browser identity, sessions, and tickets

Runtime Ownership

  • • EAPWebManager routes commands and retains shared snapshots
  • • EAP owns equipment authority and command execution
  • • SQL persists accounts, rules, configuration, alarms, and history

Contract Boundaries

  • • OUI to WebManager uses typed WebSocket events
  • • WebManager to EAP uses PLUS S99F97W and S99F98
  • • Each repository and deployment remains independently versioned