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.

3Wrkz is an owner-engaged technology firm focused on the design, delivery, and modernization of enterprise software solutions for organizations that depend on reliable systems, disciplined execution, and strong operational alignment. The firm's leadership background is rooted in healthcare, home health, enterprise architecture, workflow automation, cloud delivery, and regulated-environment software engineering.

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

Rather than restating the functional requirements in long-form narrative here, 3Wrkz has prepared a dedicated requirements website that addresses the scope on a requirement-by-requirement basis. That site is intended to serve as the primary functional response reference for evaluators who want to review detailed requirement coverage, proposed handling, and related implementation considerations in a more navigable format.

The proposed technical architecture for MOW 2.0 is centered on a custom-built, Azure-hosted application platform designed to support VNA's operational, reporting, integration, and security requirements as a single coordinated solution. The architecture is intended to provide a stable production foundation for Phase 1 while preserving the modularity and extensibility needed for later platform consolidation and future commercialization.

The diagram below presents the proposed Phase 1 target-state architecture for VNA Meals on Wheels 2.0. It focuses on the Azure-hosted core platform, the retained user-access channels and enterprise integrations that remain relevant in Phase 1, and the new solution components that replace the current legacy stack.

The proposed MOW 2.0 solution will be hosted in Microsoft Azure and aligned to VNA's stated Azure preference. The preferred deployment model is to host the production solution within VNA's own Azure tenant so that VNA retains direct control over the cloud environment, subscriptions, resource ownership, billing visibility, security oversight, and long-term operational portability.

The proposed delivery model for VNA Meals on Wheels 2.0 Phase 1 is built around a role-based team structure with clear accountability, full-time delivery focus in the core workstreams, and defined escalation paths for both business and technical decisions. The intent is to give VNA a team that is structured for execution, not a loosely assembled set of part-time contributors.

This section explains how 3Wrkz will deliver the VNA Meals on Wheels 2.0 Phase 1 solution from project kickoff through go-live and early stabilization.

3Wrkz believes the requested ~4.5-month implementation window is not realistic for the full Phase 1a scope as currently defined in the RFP materials. This is not primarily a staffing or cost issue. It is a scope-shaping, solution-design, integration-sequencing, and validation-readiness issue.

The VNA Meals on Wheels 2.0 Phase 1 solution will be tested continuously throughout delivery rather than held until the end of the project. Because the project will be delivered using Scrum, testing will run alongside design and development as part of the normal delivery cadence, with each sprint expected to produce work that can be reviewed, validated, and advanced toward production readiness.

VNA's existing Meals on Wheels operations depend on data that currently lives across multiple legacy platforms. Phase 1 therefore requires a deliberate migration workstream rather than treating conversion as a final-load task near go-live. The objective is to move the data VNA needs for operational continuity, reporting, billing support, compliance, and day-to-day user adoption into the new platform in a controlled, testable way.

The Phase 1 production solution will include an ongoing frontline support model for day-to-day user and operational issues after go-live. 3Wrkz's intent is to satisfy this requirement through a specialized support partner that can provide true 24/7 coverage, while 3Wrkz remains responsible for application ownership, escalations, defect resolution, and higher-level technical intervention when issues move beyond frontline handling.

3Wrkz acknowledges VNA's requirement in Section 11 of the RFP and Appendix A.7 to participate, if shortlisted, in an unpaid Proof of Concept (POC) as part of the finalist presentation process.

3Wrkz will provide pricing for both models required by the RFP:

3Wrkz understands that VNA is evaluating not only the delivery of a Phase 1 operational platform, but also the longer-term possibility that the resulting solution may become a broader commercialization asset. We are open to a constructive discussion regarding intellectual-property ownership, source-code rights, commercialization structure, and any future profit-sharing or revenue-participation model that may be appropriate for that vision.

This section identifies the principal assumptions, dependencies, exclusions, and proposal qualifications that form the basis of 3Wrkz's response. It is intended to keep the proposal aligned to the actual Phase 1 award basis defined by VNA, the current-state materials provided to date, and the implementation realities reflected in the RFP, requirements workbook, migration workbook, and vendor question responses.

The current qualification record supports a strong organizational narrative for 3Wrkz in healthcare and other regulated-service environments, particularly through the experience of Brian Davis and Steve Schaneville. The evidence base is strongest for OE1 and directionally supportive for OE3. OE2 is supportable in concept, but the final submission should strengthen project-scale and timing documentation so the qualification case is fully explicit and defensible.

3Wrkz proposes a lean senior delivery team led by Brian Davis as Project Manager and Steve Schaneville as Principal Architect and Technical Lead. The current evidence base supports substantial relevant leadership experience in healthcare and other regulated environments. Where the final submission would benefit from more explicit project-level attribution, that need is identified below so the qualification package can be strengthened without overstating the current record.

3Wrkz's proposed solution direction is aligned with the core technical expectations reflected in the Qualification Gate. The current materials support an integrated, Azure-oriented, custom-development approach with relevant Microsoft ecosystem experience. Where the final submission would benefit from a more explicit example or attachment, that need is identified below so the technical qualification package can be completed cleanly.

3Wrkz's proposed approach is aligned to the compliance and security expectations defined in the Qualification Gate. Based on the current proposal direction and documented Azure-oriented architecture, 3Wrkz is prepared to satisfy the listed requirements through a combination of contractual commitments, platform controls, and implementation practices appropriate for a HIPAA-regulated environment.