FleetOps

FleetOps is a production fleet-management platform used at Friday Ice Cream to centralize GPS tracking data, automate fleet reporting, and build custom operational workflows on top of the company's existing iTrack infrastructure.

Friday Ice Cream operates a substantial vehicle fleet across multiple branches. Vehicle GPS data already existed inside the iTrack tracking environment, but much of the operational analysis was tied to the external platform.

Several reporting workflows required working vehicle by vehicle instead of managing the fleet as one operational dataset — one branch alone contained dozens of tracked vehicles.

The tracking provider supplied location and device data, but the company needed more control over that information:

• Working with large numbers of vehicles
• Repetitive per-vehicle reporting
• Centralizing branch-level fleet visibility
• Building company-specific reports
• Creating custom geofence logic
• Integrating tracking data with internal operations
• Reducing dependency on manually navigating the external tracking platform

An internal .NET platform that sits between the company and the external GPS provider. Rather than replacing the devices or the provider, FleetOps creates a company-owned application layer around their data.

FleetOps is designed so the application never becomes dependent on iTrack implementation details.

Future reports, maps, alerts, dashboards, and operational rules are implemented against internal models rather than directly against external responses.

Provider Integration ⟷ Internal Models ⟷ Fleet Business Logic

The hardest part was integrating with an external tracking environment that behaves more like a browser session than a conventional public API. Authentication depends on session state, cookies, customer identifiers, and provider-specific request headers.

Instead of spreading that complexity through the application, I created dedicated layers — a token/session provider, an authentication/session service, and an iTrack client layer — isolating third-party behavior from the FleetOps domain.

FleetOps is connected to real Friday Ice Cream fleet operations — it is not a portfolio simulation. It gives the company a foundation to:

• Centralize fleet information
• Reduce repetitive reporting work
• Process multiple vehicles programmatically
• Build company-specific tracking workflows
• Add custom fleet intelligence beyond the external tracking portal

• System architecture
• iTrack integration
• Session/authentication handling
• External API analysis
• Data modeling
• Backend development
• Fleet-report automation
• Geofence functionality
• Operational workflow design
• Future monitoring architecture