Participants: Yogesh (technical lead — vendor / Archer Infotech) and the client team (Mission, Amar + Sanjay), who have a downstream client and a German partner, Eckstein Business solution.
The concept
An augmented-reality assistive app — “more than a chatbot” — that guides an operator through running an industrial machine. The operator points their phone camera at the machine console, asks a question (typed or spoken), and the app overlays step-by-step guidance on the live view, highlighting the exact knob/button to press and explaining it, until the task is done. (Example: changing a machine’s temperature setting.)
Three system components
- Mobile app — Flutter (iOS + Android); a passive client that captures camera frames + the query and renders the AR overlays. No business logic on the device.
- Backend server — the active “brain”: all logic, AI, navigation graphs and decisions.
- Admin / authoring console — to capture machine console screens, annotate them, and upload to the server to build the knowledge base.
Core flow
Ask → point camera → capture frame → backend recognizes the console and current state → computes the navigation path → app overlays guidance → user acts → backend re-checks they’re on the right path (corrects if off-track) → loop until the goal is reached.
Validation rules
Must be pointed at a known console; console must be powered ON and fully in frame; progress is blocked if not pointed at the machine.
Hard constraints
- Fully on-premises, on the intranet (IP / confidentiality).
- No cloud AI — a small-footprint model on the on-prem server.
- All console screens, navigation graphs and annotations are built from scratch — hence the in-house authoring tool.
Scope
Start with a POC, but even the POC must be end-to-end (mobile + backend + admin + custom AI). Future scope: operator training, fault / anomaly detection, and validation / monitoring (e.g. flagging incorrect readings).
Action items
- Vendor: a demo app by the weekend — using MS Word (and Gmail) as a stand-in “machine” to prove the concept.
- Vendor: 1–2 UI/UX mockups (home + one flow screen).
- Vendor: share team size, UI/UX capacity and portfolio (client flagged UI/UX as top priority).
- Client: share the formal requirement (Excel) + the backend tech-stack sheet.
- Both: follow-up call; client also expecting a demo / slides from Eckstein Business solution.
Meeting outcome
Both sides aligned to build a from-scratch, fully on-prem POC. Agreed next steps: the vendor delivers a working proof-of-concept demo (MS Word / Gmail standing in for a machine console) plus 1–2 UI/UX mockups by the weekend; the client shares the formal requirement (Excel) and the backend tech-stack sheet. A follow-up call will review the demo together with slides from the German partner, Eckstein Business solution.