Symfony Backend Development - Telemetry and Winter Maintenance Management

1. Objective Extend the existing Symfony 8 application to support winter maintenance vehicle tracking, telemetry processing and business reporting. 2. Database Requirements Database engine: PostgreSQL + PostGIS Use of PostGIS is mandatory for: Geofencing Spatial queries Distance calculations Route analysis Village crossing detection 3. Multi-Tenant Architecture A new entity must be introduced: Company ├─ Users ├─ Vehicles ├─ Trackers ├─ GPS Points ├─ Winter Operations ├─ Reports Every business entity must belong to a company whenever relevant. 4. User Access Management Implementation of a complete RBAC system. Permissions must be assignable separately for: Read Create Update Delete For every functional module. Suggested Roles Viewer Read-only access. Winter Supervisor May: View traces View reports View vehicles Cannot modify data. Transport Company May: View own vehicles View own traces Create SH reports Edit SH reports Manage own vehicles Cannot manage system configuration. Administrator Full access. May additionally: Create geofences Manage trackers Assign permissions Manage companies Configure system settings 5. Cantonnier Visibility Rules A cantonnier shall not be limited by company ownership. Administrators must be able to assign: Vehicles Routes Districts visible to each cantonnier. Visibility must therefore support: Company ownership Explicit permissions simultaneously. 6. New Entities Company Vehicle Tracker GPSPoint RouteCorridor Operational route expected to be serviced. VillageCrossingZone Administrative village area. WinterOperation Raw operation sessions. SortieSH Business output report. TraverseeLocalite Village crossing details. 7. Daily Processing Engine A scheduled task must execute daily. Responsibilities: Detect operations Aggregate telemetry Calculate distances Calculate vehicle activity Generate SortieSH entries Generate TraverseeLocalite entries 8. Business Logic Operation Types: Transit No equipment active Snow Plow Blade active Salt Spreading Spreader active Mixed Operation Blade + spreader active 9. Consumption Calculation Salt Consumption: Based on spreader telemetry. Brine Consumption: Based on EN15430 information. When necessary: Plain Text 1 Consumption 2 = 3 Distance 4 × Width 5 × Application Afficher plus de lignes 10. API Requirements Provide secured APIs for: Vehicles Traces Geofences Companies Trackers Winter Operations SH Reports Permissions OpenAPI documentation mandatory. 11. Testing Mandatory: Unit Tests Minimum 80% coverage. Functional Tests Symfony API. Integration Tests End-to-end processing. Acceptance Criteria A complete telemetry chain must transform raw Teltonika data into validated and exploitable business reports. Non-Functionnal Requirements - Source code ownership transferred to customer - No recurring license costs - No SaaS dependency - Docker deployment required - CI/CD through GitHub Actions - English documentation mandatory - PostgreSQL + PostGIS mandatory - Unit and integration tests mandatory - GDPR compliant - Responsive UI - API versioning - Audit logs for all administrative actions - Minimum code coverage: 80% - Warranty period: 3 months after acceptance - Bug fixes included during warranty period