49494cf1a7
Data model inspired by Odoo OCA Field Service + Salesforce FS patterns. Adapted for small ISP/telecom (Gigafibre) running ERPNext. Doctypes: Service Location, Service Equipment, Service Subscription + child tables for equipment history, checklists, photos, materials + extended Dispatch Job with customer/location/equipment links Docs: architecture overview, tech stack, auth flow, industry comparison, roadmap Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.6 KiB
1.6 KiB
Gigafibre FSM — Roadmap
Phase 1 — Foundation (Done)
- Dispatch PWA with timeline, drag-drop, map
- GPS tracking (Traccar hybrid REST + WebSocket)
- Tech CRUD in GPS modal
- Authentik SSO (forwardAuth) for all apps
- ERPNext API proxy (same-origin)
- FSM doctypes: Service Location, Equipment, Subscription
Phase 2 — PWA Integration
- Customer/Location picker in job creation modal
- Equipment scanner (barcode via camera API)
- Checklist UI on job detail panel
- Photo capture with annotations
- Customer signature pad (HTML Canvas)
- Time tracking (start/pause/stop on job)
- Offline-first with IndexedDB sync
Phase 3 — Workflows & Automation
- Issue → Dispatch Job (server script)
- Job completion → equipment status update
- Job completion → close helpdesk ticket
- Equipment swap → inventory move log
- Twilio SMS notifications (tech + customer)
- n8n workflows for escalation rules
- SLA tracking on subscriptions
Phase 4 — Customer Portal
- Customer-facing web app (service status)
- Online appointment booking
- Real-time tech tracking ("On my way" SMS)
- Invoice/payment history
- Equipment list per location
- Service request submission
Phase 5 — Advanced Features
- Van stock inventory per technician
- Part usage → auto-reorder
- Multi-day project tracking (fiber builds)
- Tech performance dashboards
- Revenue analytics (MRR, churn, ARPU)
- Preventive maintenance scheduling
- White-label mobile app for techs