This case study describes how the Softray team helped modernize a mission-critical ITS asset management platform, strengthening field workflows, roadway maintenance operations, and the software backbone behind intelligent traffic infrastructure.
Client Overview and Challenge
Client: North American Intelligent Traffic Management / ITS Solutions Provider
Product: Maintenance Management System / ITS Asset Management Platform
Industry: Transportation / Intelligent Transportation Systems
Location: California, USA
The client is one of North America’s most established intelligent transportation systems providers, with a long history in traffic safety and a broad portfolio of traffic management technologies. Today, the company supports transportation agencies with solutions spanning traffic controllers, cabinets, sensors, traffic management software, professional services, field operations, and system support.
Its footprint is significant: the company’s technology supports tens of thousands of intersections and hundreds of transportation agencies across North America. This places the client at the center of a complex transportation ecosystem where reliability, visibility, and operational continuity directly influence how efficiently public road networks are managed.
For transportation agencies, roadway infrastructure is not only about signals, sensors, controllers, and equipment in the field. It also highly depends on the software layer behind the scenes: the systems that help teams manage assets, respond to issues, plan maintenance, coordinate technicians, monitor inventory, and keep traffic networks operating safely.
The client needed a modern maintenance management solution that could support both office-based operations teams and field technicians. The platform had to make it easier to manage tickets, work orders, preventive maintenance, assets, inventory, locations, reporting, and technician activity in one centralized system.
As the engagement evolved, the work expanded beyond product development. Softray supported frontend modernization, platform upgrades, legacy code refactoring, architecture improvements, and backend stabilization. The goal was not only to build new functionality, but to strengthen the platform’s long-term maintainability, performance, and reliability in a mission-critical transportation environment.
Key Challenges and Goals
The implementation of a nationwide tolling system introduced complex technical, operational, and regulatory challenges requiring tight coordination across multiple systems and stakeholders.
- Centralized ITS Asset Management
The client needed a system that could help transportation agencies actively manage field assets and maintenance operations across complex roadway networks. The goal was to create a centralized GIS-based asset management solution that gives teams better visibility into traffic management equipment, field assets, locations, inventory, vehicles, and maintenance activity. This was especially important because transportation agencies need a clear, reliable view of what is happening across the roadway network, from the office to the field. - Field Technician Enablement
A major requirement was supporting technicians working directly on roadway infrastructure. These users needed fast, clear, mobile access to the information and actions required to complete daily work.
The platform needed to allow technicians to:
– Access assigned tickets and work orders
– View tickets by priority
– Create new tickets
– Complete checklists
– Move assets and inventory
– Search locations
– Report work activity in real time
The goal was to give field teams a practical tool that reduces friction during daily maintenance work. - Work Order and Preventive Maintenance Management
The client needed a more structured way to support planned and reactive maintenance workflows.
The platform had to support:
– Planned maintenance scheduling
– Active ticket management
– Preventive maintenance checklists
– Work activity tracking
– Technician work hour visibility
– Asset, vehicle, equipment, and inventory lists
– Reporting, notifications, and operational follow-up
This would help agencies move from fragmented maintenance tracking toward more consistent, organized operations. - Platform Modernization
As the system matured, the client also needed to address technical debt and improve the application’s long-term foundation.
Modernization goals included:
– Upgrade frontend technology from Angular 8 to Angular 19
– Refactor legacy frontend code
– Improve application architecture
– Support a phased migration of a live production system
– Resolve long-standing backend issues
– Increase maintainability and reduce friction for future development
This was not a simple version upgrade. It was an architectural transformation of an active system that needed to continue supporting users while the platform was being modernized. - Operational Reliability
Because the platform supports transportation operations, reliability was central to the project.
The system needed to improve:
– Data accuracy
– Work order visibility
– Maintenance planning
– Field-to-office coordination
– Reporting and notifications
– Secure access and permissions
– System maintainability
For this type of environment, reliability is not only a technical requirement. It directly affects how confidently agencies can manage roadway assets and maintenance operations.
Solution and Approach
- Maintenance Management Platform Development
Softray helped build a web and mobile maintenance management platform designed to support transportation agencies in proactively monitoring and managing traffic management equipment.
The platform brings together asset data, field work, tickets, work orders, preventive maintenance, inventory, and technician activity in one operational system. This gives agencies better visibility into the status of roadway assets and helps them maintain the proper and efficient operation of the roadway network.
Instead of relying on fragmented tools and manual coordination, users can manage critical maintenance workflows through a centralized platform built around real operational needs.
- Mobile Application for Field Technicians
A key part of the solution was a mobile application designed for technicians working in the field.
The mobile app enables users to:
– Access tickets and work orders quickly
– Review tickets by priority
– Complete work checklists
– Create new tickets
– Move assets and inventory
– Search locations
– Log work activities in real time
This makes field work faster, clearer, and more structured, especially for teams working directly with roadside infrastructure.
- Web Application for Operations Teams
The web application supports office-based users responsible for managing, planning, and monitoring maintenance activities.
The platform includes modules for:
– Map and GIS-based asset visualization
– Dispatch and call tickets
– Ticket and work order management
– Project management
– Preventive maintenance
– Locations and assets
– Inventory and warehouse management
– Configuration and settings
– Reports
– Payroll and billing
– Notifications and alerts
Together, these modules give operations teams better oversight of maintenance workflows and create stronger coordination between field technicians, managers, and back-office teams.
- GIS-Based Asset Visibility
The platform includes map and GIS capabilities that help users visualize field assets and locations across the roadway network.
With map-based visibility, teams can better understand where assets are located, how work is distributed, and what needs attention. This is especially valuable in transportation environments where the physical location of equipment directly affects maintenance planning, technician dispatch, and operational decision-making.
- Frontend Modernization and Platform Upgrades
As part of the ongoing engagement, Softray supported a major modernization effort, including the migration from Angular 8 to Angular 19.
This was not a simple technical upgrade. It required an incremental architectural transformation of a live system.
The application now uses a hybrid migration pattern, with modern standalone Angular components running alongside older NgModule structures. This allowed the system to evolve progressively without disrupting production users.
The modernization work included:
– Refactoring legacy frontend code
– Improving application architecture
– Modernizing the UI foundation
– Supporting reusable library-based architecture
– Increasing maintainability
– Creating a stronger foundation for future development
The codebase includes a large application structure, with approximately 296 Angular components, 193 modules, 62 services, 69 routing modules, and more than 100 standalone components. This reflects both the scale of the platform and the complexity of modernizing it while keeping it operational.
- Library-Based Architecture
The frontend was structured as an Angular workspace with a library-based architecture.
The core MMS logic is extracted into a reusable library, while the dashboard is organized as a separate library that can be configured and reused across products.
This approach supports better long-term maintainability because individual modules can evolve more independently. It also gives the client a stronger foundation for scaling and extending platform capabilities over time.
- Backend Microservices Architecture
The backend is built as a .NET 8 microservices system deployed on Azure infrastructure. Each business domain is implemented as an independent service, supporting a modular and scalable architecture.
The system includes 13 deployable components across domains such as:
– Inventory management
– Ticket management
– Location management
– Preventive maintenance
– Project management
– Agency management
– Payroll and billing
– User management
– File management
– API gateway
– Aggregation layer for frontend workflows
The architecture follows a bounded-context microservices pattern, supported by an API gateway, backend-for-frontend aggregation, event-driven integration, and shared cross-cutting services.
Across the backend, the platform includes approximately 70 controller classes and 575 HTTP API endpoints, showing the scale and depth of the system.
- Automated Operations and Background Processing
The platform is not limited to manual user workflows. It also includes background workers for preventive maintenance and project management processes.
These workers support automated operations, such as scheduled preventive maintenance processing and project-related background tasks. This helps reduce the need for manual follow-up and supports more consistent operational execution.
- Security and Access Control
Security and access control were important parts of the platform architecture.
The system includes:
– JWT-based authentication
– Keycloak-backed identity management
– Role-based access control
– Fine-grained permissions across frontend and backend
– Route and UI-level permission enforcement
– Custom authorization attributes across backend services
This permissions model helps ensure that users only access the modules and actions relevant to their roles, which is important for a platform supporting multiple operational functions and user types.
Results and Benefits
- Improved Maintenance Operations
The platform helps transportation agencies manage maintenance activities more efficiently by centralizing tickets, work orders, preventive maintenance, assets, inventory, and technician activity in one system.
Key benefits include:
– More efficient process flow
– Better work order management
– Improved preventive maintenance planning
– Clearer field-to-office coordination
– Faster access to operational data
– Better visibility into equipment and asset status
This gives agency teams a more organized way to manage the operational layer behind roadway infrastructure. - Stronger Field Technician Productivity
The mobile application gives field technicians a practical tool for managing daily work directly from the street. Instead of relying on fragmented processes, technicians can access tickets, complete checklists, create new tickets, manage asset movement, and search locations from one interface. This improves the speed and clarity of field operations and supports more accurate real-time data logging. - Better Coordination Between Field and Office Teams
By supporting both mobile and web workflows, the platform improves coordination between technicians in the field and teams managing operations from the office.
Field activity, asset status, maintenance planning, work orders, and reporting can be connected through the same operational system. This reduces information gaps and helps teams make decisions with better context. - Reduced Operational Friction
By improving workflows around tickets, work orders, preventive maintenance, assets, and inventory, the solution helps reduce manual effort and operational friction. Teams can work with clearer task visibility, better prioritization, and more consistent access to the data they need to complete and manage maintenance work. - Stronger Technical Foundation
The modernization work improved the application’s long-term health by upgrading core frontend technology, refactoring legacy code, improving architecture, and supporting backend stabilization.
The Angular 8 to Angular 19 migration created a more modern frontend foundation. The library-based architecture made the application easier to maintain and extend. The .NET 8 microservices architecture strengthened backend modularity and supported clearer separation of business domains. This gives the client a platform that is better prepared for continued evolution. - Improved Scalability and Maintainability
The platform’s microservices-based backend and modular frontend architecture make it easier to scale, maintain, and evolve individual parts of the system.
Instead of treating the platform as one tightly connected block, the architecture supports independent business domains, reusable libraries, API gateway routing, backend aggregation, and event-driven integration. This matters because ITS platforms need to adapt as agency needs, field operations, technology standards, and transportation networks evolve. - Higher Confidence in a Mission-Critical System
Traffic infrastructure software has to work reliably because it supports the operational systems behind public road networks. By improving the platform’s usability, architecture, access control, and maintainability, Softray helped strengthen a system that supports roadway maintenance, asset visibility, technician workflows, and operational decision-making.
Why It Matters
Traffic management depends on much more than signals, sensors, and roadside equipment. Behind every well-managed roadway network is a layer of software that helps agencies understand what is happening in the field, coordinate maintenance work, manage assets, and keep critical infrastructure operating.
For transportation agencies, delays in maintenance, poor asset visibility, or disconnected technician workflows can create operational inefficiencies that affect road performance, safety, and public trust.
This project shows how Softray supports the digital systems behind modern transportation infrastructure. By helping develop and modernize an ITS asset management and maintenance platform, we directly contributed to a solution that makes roadway operations more organized, field work more efficient, and infrastructure management more reliable.
For the client, the work also strengthened the platform’s technical foundation, making it easier to maintain, improve, and scale as transportation networks continue to evolve.
At Softray, we build and modernize platforms that must stay reliable under high pressure, especially where compliance and continuity are non-negotiable.
If your transportation platform needs to support complex operations, field workflows, and long-term modernization, our team can help you build the digital foundation behind safer, more reliable infrastructure.
Let’s build with care and design for impact.
Source note: Case study prepared based on Softray project documentation. Third-party names have been generalized to preserve client anonymity for website publication.