Sentryx — Mobile App + Web Portal for Diagnostics & Spare Parts (ERP + PDFs) 1) Overview Sentryx is an industrial platform composed of: A mobile-first technician app (PWA) to capture photos, identify machines/parts, and create requests. A web portal for spare parts staff and managers to consult everything: requests, machine data, manuals evidence, purchase history and ordering workflow. The platform searches technical PDF manuals and parts catalogs (per customer) using OCR + AI and integrates with any ERP to fetch exact machine data (including park/fleet number) and purchase history/pricing. 2) Users & Roles Technician (Mobile PWA) Identify machine (park number or plate photo) Capture part photo / fault code Get suggested results (manual + page + part number / diagnostics) Confirm and submit a request Spare Parts / Purchasing (Web Portal) Receive and manage requests queue See machine details (from ERP) See evidence from manuals (PDF + page) See purchase history and last prices (from ERP) Trigger supplier portal search / add to cart (phase 2) Finalize request (create PO / purchase request in ERP) (phase 3) Manager/Admin (Web Portal) Manage customers (multi-tenant) Upload PDFs per customer Configure ERP connection & mapping Configure supplier portals/connectors Manage users/permissions 3) Key Features (What the system must do) A) Machine Identification (ERP-first) Input: park/fleet number (preferred) OR plate photo OR manual input. If park number is given: fetch exact machine record from ERP: park number, customer/site, brand/model/serial, configuration (if available). If plate photo: OCR and extract structured info (brand/model/serial). B) Part Identification (Photo → exact + similar parts) Input: part photo + machine context. Output: exact part reference (OEM part number) when possible similar part suggestions (image similarity search) when exact is uncertain manual/catalog PDF name + exact page number(s) + evidence text C) Fault Code Diagnosis (Photo/text → troubleshooting) Input: fault code (photo of display or typed). Output: description, causes, diagnostic steps manual PDF + exact page(s) + evidence D) Requests + Notifications Technician confirms and submits request. System creates a request record and sends email notification (MVP): customer + site machine data (park number, model, serial) identified part/fault info + confidence manual evidence (PDF + pages) attached photos technician name/time E) ERP Purchase History for Spare Parts Staff (Web) For any identified part / machine / customer: show purchase history from ERP: previous orders, suppliers, last prices, quantities, lead times (if available). F) Supplier Portal Integration (Phase 2) Connect to spare parts websites with login/password: search by part number select item add to cart (basket) pre-fill notes/references/shipping where possible Prefer supplier API; fallback to web automation if needed. 4) Multi-Tenant Requirement (Per Customer) Sentryx must support multiple customers, each with: Their own PDF library Their own ERP connection + field mapping Their own supplier portal credentials Their own email recipients/templates Their own rules (e.g., machine naming, park number format) 5) Data Sources PDFs (per customer) parts catalogs service manuals troubleshooting guides scanned or text PDFs Requirement: page-level indexing (must return page numbers). ERP (any ERP) Must support a connector framework: REST / SOAP APIs DB connector (optional) File exchange (CSV/JSON) Fallback: email ingestion Minimum for MVP: Generic REST connector + configurable mapping per client. 6) Interfaces Mobile Technician App (PWA) Must include: login select customer (if technician works with multiple) machine identification (park number / plate photo) capture photos results screen (manual + page + evidence) confirm & submit request request history for technician (optional MVP) Web Portal (Admin + Spare Parts) Must include: login + roles requests inbox (status workflow: new → validated → ordered → delivered → closed) request detail page with evidence (PDF + pages) and photos ERP data panel (machine record + purchase history + prices) admin section: customers, PDFs, connectors, users, templates (phase 2) supplier portal action: “search / add to cart” 7) Outputs & Evidence Requirements Every result shown to user must include: PDF name page number(s) evidence text snippet confidence score optionally: rendered page image / highlight (future) 8) Suggested Implementation (Developer Guidance) Frontend: PWA (React/Next.js or similar) Camera upload support Backend: Node.js or Python Authentication + multi-tenant Document processing: page-level extraction (pdftotext/pdfplumber) OCR for scanned pages (Tesseract or cloud OCR) Search: Vector DB (Qdrant) exact match (fault codes, part numbers) via text search/regex Storage: object storage for PDFs/images DB for tenants/users/requests/audit logs 9) Phased Roadmap (Build gradually) Phase 1 (MVP) Mobile PWA: capture plate + part/fault + show results Web portal: basic request inbox + request details PDF ingestion/indexing per customer with page numbers Email notification on confirmed request Phase 2 ERP connector (read machine by park number) Web portal: show machine record + basic purchase history Similar parts (image similarity) basic version Phase 3 ERP write-back (create purchase/service request) Supplier portal connectors (search + add to cart) Advanced analytics / reporting 10) Deliverables Source code (frontend + backend) Deployment guide (self-hosted) Admin documentation for adding customers/PDFs/connectors MVP running with at least 1 customer dataset