3. Proposed Solution Concept

Solution Concept Selection

Selected solution concept: Concept B - Hybrid Custom + Best-of-Breed

3Wrkz is proposing Concept B - Hybrid Custom + Best-of-Breed as the best-fit solution concept for VNA Meals on Wheels 2.0. This approach aligns with VNA's goal of establishing a modern, cloud-based, mission-critical operating platform while also making disciplined use of specialized third-party capabilities where that provides a stronger operational outcome and lower implementation risk.

Under this concept, the core MOW 2.0 platform would be purpose-built for VNA and designed around VNA's operational workflows, data model, integrations, security requirements, and long-term roadmap. At the same time, selected best-of-breed capabilities can be integrated through APIs where it is not practical or advisable to recreate highly specialized functionality from scratch. Vehicle routing is the clearest example. Routing is a proprietary and operationally complex discipline with mature commercial tooling available, and 3Wrkz believes VNA is better served by integrating proven routing software than by funding custom development of that capability.

This concept also aligns with the priorities VNA identified in Section 6:

1. replacement of critical legacy system functions in Phase 1
2. API-first integration across VNA and third-party systems
3. cloud-native architecture with strong long-term extensibility
4. multi-tenant and SaaS readiness for future commercialization options
5. support for VNA's intellectual property and platform ownership objectives

Solution Summary

3Wrkz proposes a custom-built MOW 2.0 platform hosted in Azure, with a central application and data architecture designed specifically for VNA's operational model. The solution will support browser-based users, mobile users, reporting and dashboards, integrations, and background processing as parts of a single coordinated platform rather than a collection of disconnected tools.

The core of the solution will be purpose-built by 3Wrkz to cover the functional requirements defined in the VNA scope matrix, while selected third-party capabilities will be integrated where that is the better technical and operational choice. This gives VNA a system tailored to its workflows and future roadmap without taking on unnecessary custom development in specialized areas.

Core Solution Components

The proposed solution is composed of the following primary components:

1. Core application platform

   The central MOW 2.0 application layer will manage the primary business workflows, application logic, security boundaries, configuration, and system coordination across the platform.

2. Web application

   A browser-based single-page application will support day-to-day use by VNA administrative, operational, and program staff.

3. Mobile application

   A native mobile application will support mobile users in the field, including delivery and other operational workflows that require device-based interaction.

4. Central data platform

   A SQL Server-backed data layer will serve as the system of record for operational, client, workflow, and reporting data.

5. Reporting and dashboard environment

   A dedicated reporting component will support operational reporting, management visibility, dashboards, and other analytics needs.

6. Integration and background-processing services

   Integration workflows, scheduled processing, and other background tasks will be handled through Azure Functions and related service components using shared core business logic where appropriate.

7. Specialized third-party services

   Selected external components, most notably routing software, will be integrated where a specialized platform is the better operational and technical choice than custom development.

Third-Party Components and Integrations

The proposed solution will use third-party components selectively, with routing as the primary area where an external platform is expected to be part of the final solution. The intent is to integrate a routing engine through well-defined APIs so that routing remains part of the overall MOW 2.0 workflow without requiring VNA to fund custom development of route-optimization logic.

Possible Routing-engine candidate options for evaluation include (but are not limited to):

1. Routific

   A route-optimization platform with an engine API and delivery-focused use cases, including meal delivery.

2. Route4Me

   An established route-optimization platform with API support, dynamic route optimization, dispatch, and re-optimization capabilities.

3. OptimoRoute

   A route-planning and field-service scheduling platform with a documented web-service API.

4. Onfleet

   A delivery-management platform with route optimization, route plans, and API-based integration support.

5. Google Maps Route Optimization API

   A developer-oriented route-optimization API that can be evaluated where a lower-level routing service model is preferred.

Final product selection is TBD during discovery and should be based on VNA's detailed routing needs, operational constraints, dispatch model, driver workflow expectations, licensing model, and integration fit.

Phase Alignment

The proposed solution is structured to align with VNA's phased delivery model, with Phase 1 focused on replacing critical legacy capabilities, Phase 2 focused on platform optimization and consolidation, and Phase 3 focused on longer-term expansion and commercialization readiness.

Phase 1: Legacy System Replacement

Phase 1 will establish the required baseline platform and replace the core legacy capabilities needed to support day-to-day Meals on Wheels operations. The focus in this phase is operational readiness: delivering the core application, data platform, web and mobile experiences, reporting capability, key integrations, and supporting services required to run the program on a modern platform.

This phase is intended to satisfy the required scope for contract award and provide a stable foundation for cutover from the current environment. Where third-party routing technology is included, it would be selected and integrated in a way that supports immediate operational use rather than deferred as a future enhancement.

Phase 1 will also be designed with future commercialization in mind. While the initial production solution will not be delivered as a fully multi-tenant platform, the underlying data model will be structured to support later expansion into a multi-tenant architecture. This will significantly reduce the amount of rework required in Phase 3 and allow VNA to move toward commercialization on a more efficient path.

Phase 2: Platform Consolidation

Phase 2 will extend and refine the platform beyond the minimum replacement scope by improving workflow efficiency, deepening integrations, and consolidating additional operational functions into the MOW 2.0 environment. This phase is expected to focus on optimization, administrative efficiency, improved visibility, and reduction of remaining fragmentation across systems and processes.

Because the proposed core platform is purpose-built and API-driven, it is well suited to absorb additional capabilities over time without forcing major architectural rework.

Phase 3: Commercialization and Future Roadmap

Phase 3 will position the platform for broader scalability, multi-tenant readiness, and future commercialization opportunities consistent with VNA's long-term vision. This includes the ability to harden the platform for reuse, support broader deployment models, and expand the solution in ways that extend beyond the immediate needs of the initial Phase 1 implementation.

The proposed hybrid custom platform supports this roadmap by keeping the core MOW operating environment under deliberate architectural control while still allowing specialized external capabilities to be integrated as needed.

Commercialization Position

The primary commercialization asset in the proposed solution is the custom MOW 2.0 core platform developed for VNA. Third-party products, such as routing software, would remain integrated supporting components rather than the basis of the commercialization model. Detailed intellectual property ownership, licensing, and commercialization terms are addressed separately in the proposal's Commercialization and IP section.