How protogulix/tunnel-gmao works
Tunnel GMAO is a browser-based maintenance-management application for industrial SMEs. Its core workflow is reporting and qualifying an intervention request, converting accepted requests into interventions, and recording field work as actions tied to equipment and parts. The interface also covers planning, preventive maintenance, purchasing, inventory, and operational views. The graph follows the visible route and API organization plus README-documented domain rules; unsampled modules are represented by their tree paths, without assuming internal call wiring.
Main entry points: routes.jsx Routes · InterventionRequestsPage.jsx Intervention requests · InterventionDetailPage.jsx Intervention execution · useBriefingData.js Briefing data hook
Components 25
App entry and access
- Routes
src/router/routes.jsx - Login
src/pages/auth/Login.jsx - Application layout
src/components/layout/Layout.jsx - Authentication context
src/auth/AuthContext.jsx
Maintenance workflow
- Intervention requests
src/pages/intervention-requests/InterventionRequestsPage.jsx - Interventions
src/pages/interventions/InterventionsListPage.jsx - Intervention execution
src/pages/interventions/InterventionDetailPage.jsx - Action forms
src/components/interventions/ActionForm/index.jsx - Equipment records
src/pages/equipements/EquipementsPage.jsx - Task workspace
src/hooks/tasks/useTasks.js
Resources and purchasing
- Stock and parts
src/pages/stock/StockPage.jsx - Suppliers
src/pages/suppliers/SuppliersPage.jsx - Purchasing
src/pages/purchase/PurchaseRequestsPage.jsx
Planning and oversight
- Preventive maintenance
src/pages/preventive/PreventivePage.jsx - Planning
src/pages/coordination/CoordinationPage.jsx - Maintenance briefing
src/pages/briefing/BriefingPage.jsx - Briefing data hook
src/hooks/useBriefingData.js - Service status
src/hooks/service-status/useServiceData.js - Quality data
src/pages/quality-data/QualityDataPage.jsx - Administration
src/pages/admin/AdminPage.jsx
API access
- Request API
src/api/intervention-requests.js - Intervention API
src/api/interventions.js - Task API
src/api/tasks.js
Other components
- Technician / staff
- Application backend
Connections 27
- Technician / staff → Routes: opens app
- Routes → Login: routes to
- Routes → Application layout: wraps pages
- Application layout → Authentication context: uses auth state
- Technician / staff → Intervention requests: reports need
- Intervention requests → Request API: submits request
- Intervention requests → Interventions: accepted request leads to
- Interventions → Intervention execution: opens work record
- Intervention execution → Action forms: records field work
- Intervention execution → Task workspace: organizes work
- Task workspace → Task API: loads and updates
- Briefing data hook → Intervention API: fetches interventions
- Briefing data hook → Request API: fetches requests
- Technician / staff → Equipment records: manages machines
- Technician / staff → Stock and parts: manages parts
- Technician / staff → Purchasing: tracks purchases
- Technician / staff → Suppliers: manages suppliers
- Technician / staff → Preventive maintenance: manages plans
- Technician / staff → Planning: coordinates work
- Technician / staff → Maintenance briefing: views work status
- Maintenance briefing → Briefing data hook: loads sections
- Service status → Application backend: fetches status data
- Technician / staff → Quality data: views quality data
- Technician / staff → Administration: configures system
- Request API → Application backend: accesses records
- Intervention API → Application backend: accesses records
- Task API → Application backend: accesses records