Empower Integrated Solutions Pvt Ltd

BACKGROUND

Please describe your company and position.

I am the VP Software Development of Analyticy Technologies Inc.

Describe what your company does in a single sentence.

Technology strategy consulting and software solutions, specializing in digital health, AI/ML (GPT and custom LLMs, LiDAR drone data) for digital twin forestry and mining, eCommerce retail, vehicle transportation, cybersecurity and fintech industries. Successful end-to-end delivery of AWS/Azure/Google cloud/sovereign solutions from ideation and team-building, through to product deployment and AI SaaS revenues.

OPPORTUNITY / CHALLENGE

What specific goals or objectives did you hire Empower Integrated Solutions Pvt Ltd to accomplish?

• Build an integrated platform to manage the end-to-end paratransit lifecycle, from passenger booking and scheduling through dispatch and trip completion.
• Improve route and fleet efficiency through real-time scheduling, dispatch controls, navigation, trip monitoring and route optimization.
• Give dispatchers, drivers and administrators connected tools for day-of-service operations, historical reconciliation, reporting and operational decision-making.

SOLUTION

How did you find Empower Integrated Solutions Pvt Ltd?

Referral

Why did you select Empower Integrated Solutions Pvt Ltd over others?

• High ratings
• Pricing fit our budget
• Great culture fit
• Good value for cost
• Company values aligned

How many teammates from Empower Integrated Solutions Pvt Ltd were assigned to this project?

25

Describe the scope of work in detail. Please include a summary of key deliverables.

Scope of the Empower team: 

Application development for the paratransit platform: trip booking, scheduling, dispatch and the operator workflows around them. Routing and scheduling logic integrated into the operational system, so a trip plan could be built, changed and executed on the day of service. Mobile and in-vehicle workflows for drivers, tied to the same trip and vehicle record the dispatcher was using. Interfaces to the surrounding customer stack, so the paratransit system did not sit beside the rest of the platform as a separate product. Release, test and supportability work so the system could run through the service day, not only in a build environment. 

Key deliverables from Empower: 

A delivered paratransit application, covering booking, scheduling, dispatch and day-of-service changes, ready for agency operation. Scheduling and dispatch functions that could replan work when a trip, vehicle or driver changed, rather than a static roster. Driver-facing workflows on the same trip record as dispatch, so the vehicle and the control room were not on two systems. Integration into the paratransit operational stack, with a release path customer could ship and support. Engineering delivery across the multi-site model DDS was running, under Geoff Fawkes as Vice President, Application Development, with the application organization at about 60 engineers across three countries.

RESULTS & FEEDBACK

What were the measurable outcomes from the project that demonstrate progress or success?

Data-Driven Operations: Enabled historical route analysis, post-trip reconciliation and operational reporting, giving administrators greater visibility into completed routes, trips and service performance for informed decision-making.

On-Time Performance: Designed to support 95%+ on-time performance through optimized routing, real-time trip monitoring and efficient ride-sharing, helping improve service reliability across paratransit operations.

Real-Time Operational Visibility: Enabled real-time visibility into trips, routes and vehicle movement through GPS tracking and live map data, allowing dispatch teams to monitor operations and respond quickly to changing conditions.

Dispatch & Route Efficiency: Streamlined day-of-service operations with trip transfers, auto-rescheduling, route re-optimization, late-trip rescue, vehicle breakdown management and dynamic stop reordering.

End-to-End Process Integration: Connected booking, scheduling, dispatch, driver operations, playback, reconciliation and reporting within an integrated platform, improving operational continuity across the complete paratransit lifecycle.

Driver & Dispatcher Productivity: Digitized critical driver workflows including navigation, pickups/drop-offs, route updates, dispatcher messaging and emergency alerts, with online and offline operation to support drivers in the field.

Describe their project management. Did they deliver items on time? How did they respond to your needs?

Project management: 

Empower ran the paratransit work as a delivery team inside customer’s release plan, not as a separate project with its own customer. Scope, priority and acceptance sat with customer. Empower owned the build plan: what was in the current release, who was on it, and what was blocked. The cadence was a working backlog tied to the release, not a status deck. Trip booking, scheduling, dispatch and the driver workflow were broken into deliverable slices. Dependencies on the rest of the customer stack were called before the release, because a change in scheduling landed on dispatch and on the vehicle. Issues were raised in the same forum as customer engineering, with a named owner and a date, not held until a monthly review. 

On time:

The releases that mattered shipped inside the window customer was running for the paratransit system. Booking, scheduling, dispatch and the driver workflow arrived as a set the operation could use, not as a partial build that still needed a second team to finish. Where a slice moved, it was because a dependency in the surrounding stack moved, and the date was reset in the same week rather than discovered at release. I would not put a percentage on it. What I can say is that the team did not miss a committed release and then explain it afterward. 

Response to needs: 

When the operating need changed — a trip rule, a same-day replan, a driver step that did not match the dispatch record — Empower treated it as scope to replan, not as a change to resist. The useful behaviour was speed of clarification. They came back with what would move, what would slip, and what could not be done without breaking the day-of-service path. They did not add a process layer between the request and the people building it. For a system that had to run through the service day, that was the right response.

What was your primary form of communication with Empower Integrated Solutions Pvt Ltd?

• In-Person Meeting
• Virtual Meeting
• Email or Messaging App

What did you find most impressive or unique about this company?

What stood out was that Empower could put a development team on a live paratransit system and have that team behave like part of the operation, not like a vendor protecting a statement of work. Paratransit is an unforgiving product. A trip, a vehicle and a driver change during the service day, and the booking record, the dispatch board and the driver workflow have to stay the same record. Most supplied teams can build a screen. Fewer can hold the release together when a scheduling change lands on dispatch and on the vehicle at the same time. Empower did that, inside a multi-country engineering organization, without adding a layer of status between the need and the people doing the work. The other distinction was judgment on scope. They would replan when the operating rule changed, and they would say what had to slip so the day-of-service path did not break. That combination — delivery capacity plus the willingness to protect the operational release — is what I would hire them for again.

Are there any areas for improvement or something Empower Integrated Solutions Pvt Ltd could have done differently?

 No issues.   I would use Empower again.