1. Executive Overview

Project Executive Overview

Visiting Nurse Association of Texas (VNA) launched the Meals on Wheels 2.0 initiative to modernize the technology ecosystem that supports meal delivery, client services, volunteer coordination, and wellness checks for homebound seniors in Dallas County.

The project is positioned as a strategic business and technology transformation, not simply a software replacement. VNA's current environment reflects a mix of legacy systems, manual workarounds, and operational friction points that can limit data integrity, workflow efficiency, reporting, and long-term scalability. The RFP frames MOW 2.0 as an opportunity to establish a more unified, secure, resilient, and extensible platform that supports current operational needs while preparing VNA for future innovation.

At a high level, MOW 2.0 is structured as a phased program:

1. Phase 1 (required baseline): deliver the contract-award baseline MVP by replacing Netsmart, RoadNet, Alldocs, Crystal Reports, and the Integration Utility, while enhancing the existing Azure BOP, MOW API, and Mobile App.
2. Phase 2 (platform enhancement and integration): consolidate remaining external platforms into the unified VNA system on VNA-owned Azure infrastructure, absorb additional internal, volunteer-facing, and client-facing capabilities into the core platform, and deliver deferred platform enhancements.
3. Phase 3 (commercialization / future roadmap): address longer-term commercialization, multi-tenant architecture, and national scalability objectives, with scope refined based on Phase 1 and Phase 2 outcomes.

The target end state is a modern, secure, cloud-ready, API-forward operating environment that improves reliability, automation, visibility, and decision support across intake, scheduling, routing, service delivery, volunteer engagement, reporting, and administrative oversight. VNA is seeking a solution partner that can deliver the required baseline safely and pragmatically while creating a credible path to broader platform consolidation and future capabilities.

Delivery Schedule Realism

3Wrkz also believes it is important to address implementation timing candidly at the executive level. Based on the current scope volume and the design, integration, and validation effort implied by the RFP, the requested 4.5-month delivery window should be treated as aggressive and materially high risk unless the initial go-live scope is narrowed. Additional detail on this position is provided in 9A. Delivery Schedule Realism.md.

Overview of What This RFP Response Will Entail

This proposal response explains how 3Wrkz will deliver the required Phase 1 baseline scope, de-risk transition from the current MOW 1.0 environment, and position VNA for the later phases of the MOW 2.0 roadmap.

At a high level, our response will cover:

1. Executive overview (this document): a concise summary of the opportunity, 3Wrkz's understanding of the project, the proposed approach, and why 3Wrkz is qualified.
2. Organizational overview: 3Wrkz's company background, ownership, experience profile, and qualifications relevant to the VNA engagement.
3. Proposed solution concept: the overall solution model, platform composition, implementation approach, and strategic fit for MOW 2.0.
4. Functional approach: how the proposed solution addresses the required operational workflows, core business functions, integrations, and phased expansion path.
5. Technical architecture: the application, data, API, mobile, security, and tenant-model architecture supporting the proposed platform.
6. Solution architecture diagram: a visual representation of the proposed solution showing user channels, core platform components, integrations, data flows, and hosting boundaries.
7. Hosting: the Azure hosting model, environment structure, operational responsibilities, resilience approach, and hosting assumptions.
8. Project team structure: the proposed delivery team composition, key roles, principal involvement, and engagement model across the project lifecycle.
9. Implementation plan: delivery phases, project structure, milestones, training, cutover, and support transition.
   • (9a) Delivery schedule realism: an explicit assessment of why the requested implementation window is aggressive for the current scope volume and why discovery, design, and integration sequencing must shape the final commitment.
10. Testing and automation: the QA strategy, testing approach, validation methods, release-readiness criteria, and automation model supporting the delivery.
11. Data migration: the migration scope, source-system transition approach, mapping, validation, reconciliation, and cutover sequencing.
12. Frontline support: the proposed user-support model, coverage expectations, escalation process, hypercare, and ongoing support responsibilities.
13. Proof of concept acknowledgement: assumptions, constraints, and expectations associated with participation in the RFP's proof-of-concept process.
14. Pricing narrative: pricing structure, pricing assumptions, phase breakout, five-year TCO framing, and support positioning.
15. Commercialization and IP: licensing, ownership, commercialization rights, and related commercial terms.
16. References: relevant client examples demonstrating comparable delivery experience and outcomes.
17. Assumptions and exceptions: key delivery, pricing, dependency, and scope assumptions, along with any proposal exceptions or deviations.

In short, this response is intended to show not only that 3Wrkz can satisfy the required baseline scope, but that we can do so in a way that is operationally grounded, implementation-ready, and aligned with VNA's longer-term modernization objectives.