sync: auto-sync from HOWARD-HOME at 2026-06-16 21:34:19

Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-06-16 21:34:19

.claude/memory/MEMORY.md

@@ -117,6 +117,7 @@
 - [Howard-Home LAN shadow (RESOLVED)](howard-home-lan-shadow.md) — Howard-Home renumbered 2026-06-16 to **10.137.42.0/24** (gw 10.137.42.1, UniFi — NOT pfSense), off the old 192.168.0.0/24 that shadowed Cascades pfSense .0.x over the VPN. Cascades .0.x should now route via the tunnel; this machine is 10.137.42.x now (not 192.168.0.x).
 - [Cascades](project_cascades.md) — Active state: Syncro ticket #110680053 + plan file (machine-specific path on Howard's box), admin accounts (sysadmin@=Howard, admin@=Mike — daily-driver, NOT break-glass), Phase-B caregiver CA pilot (SG-Caregivers-Pilot, group-scoped never tenant-wide), prepaid block ~37.5h (rate TBD), pilot cleanup checklist.
 - [Cascades history](project_cascades_history.md) — fdeploy 502/ACL root cause (Flags=1211→187 fix), 2026-04-29 CA-rescoping decision (Howard pulled the brakes on tenant-wide), 2026-05-14 per-user-security-group decision rationale.
+- [Cascades KPI dashboard (parked)](project_cascades_kpi_dashboard.md) — Ashley Jensen wants one dashboard across their reporting SaaS (ALIS/QuickBooks/Bill.com/Relias/You've Got Leads/TELS/Focus HR/Helpany/POS). Power BI Gateway is the WRONG frame (on-prem only). Recommended Tier1→Tier2: scheduled exports → SharePoint → Power BI Pro, automate API-capable systems (Bill.com/QBO) via Power Automate later. Full notes: `clients/cascades-tucson/docs/proposals/kpi-dashboard.md`. Next: draft client one-pager.
 - [Sync script bug — untracked files (RESOLVED)](project_sync_script_bug.md) — FIXED 2026-05-21: sync.sh now uses `git status --porcelain` for change detection (repo + vault).
 - [MasterBooter Side Project](project_masterbooter.md) — Howard's Rust+Slint Windows deployment toolkit at C:\MasterBooter, separate from client work. Do not log to clients/.
 - [Audio Processor Architecture](project_audio_processor_architecture.md) — Segment-first pipeline: detect breaks before transcription for complete content capture.

.claude/memory/project_cascades_kpi_dashboard.md

@@ -0,0 +1,18 @@
+---
+name: project_cascades_kpi_dashboard
+description: Cascades KPI-dashboard request (Ashley Jensen) — parked scoping notes; Power BI Gateway is wrong frame; Tier1→Tier2 path
+metadata:
+  type: project
+---
+
+Ashley Jensen (Cascades accountant) wants a single dashboard pulling KPIs from all their **reporting** SaaS: ALIS (clinical EHR), QuickBooks, Bill.com, Relias, You've Got Leads, TELS, Focus HR, Helpany (app.safe-living.com), a POS. She asked about using the **Power BI Gateway** for it.
+
+**Key correction:** the Power BI on-prem data gateway is the WRONG frame — it only bridges Power BI to on-prem sources (SQL/file/DB inside the building), NOT cloud SaaS. The real work is per-system data extraction + a landing store, then Power BI on top.
+
+**Recommended path (Tier 1 → Tier 2):** scheduled CSV/Excel exports land in **SharePoint** → **Power BI Pro** dashboard (proves value, ~zero new cost since they're on M365 Business Premium). Phase 2: automate the API-capable systems (Bill.com, QuickBooks Online) with **Power Automate**. Niche senior-living apps (ALIS/TELS/You've Got Leads/Helpany) won't have ready connectors in Tier3/4 tools (Fivetran/Databox/etc.), so exports are the backbone regardless. SharePoint = storage layer, not an integration engine.
+
+**Open items before proposing:** which KPIs day one, data freshness needed, per-system API/export availability, which POS + which Focus HR plan. Also check whether ALIS (Medtelligent) offers a built-in analytics/BI add-on or data feed — could replace plumbing for their top source. **HIPAA:** BAA required before any ALIS PHI leaves it.
+
+**Status:** parked. Next action = draft client-facing one-pager (realistic path + cheap Phase 1: census + financial KPIs) for Ashley to approve.
+
+Full notes: `clients/cascades-tucson/docs/proposals/kpi-dashboard.md`. Client context: [[project_cascades]].

clients/cascades-tucson/docs/proposals/kpi-dashboard.md

@@ -0,0 +1,70 @@
+# Cascades — Unified KPI Dashboard (scoping notes)
+
+**Status:** Raw / discussion — not yet proposed to client. Saved 2026-06-16.
+**Requestor:** Ashley Jensen (Accountant, Cascades). Asked about using the **Power BI Gateway** to build a single dashboard that pulls KPIs from all their reporting systems.
+
+---
+
+## The systems in scope (Ashley's "reporting" systems, not data-entry)
+
+| System | What it is | Realistic path to its data |
+|---|---|---|
+| **ALIS** (Medtelligent) | Clinical EHR (census/clinical) | Vendor reporting/export; ask Medtelligent re: data feed/API. **HIPAA — BAA required before any PHI leaves it.** Their single most important data source. |
+| **QuickBooks** | Accounting | QBO has API + connectors (good). Desktop = ODBC, harder. |
+| **Bill.com** | AP/AR | REST API exists — most automatable on the list. |
+| **Relias** | Training / LMS | Reporting exports / API for completion data. |
+| **You've Got Leads** | Senior-living CRM | Reporting/export; API varies. |
+| **TELS** (Direct Supply) | Facilities mgmt | Reporting exports; API uncertain. |
+| **Focus HR** | HR / payroll | Export or vendor API — depends on plan. |
+| **Helpany** (app.safe-living.com) | Caregiver app | Niche — likely export-only. |
+| **POS** | Point of sale | Entirely depends which POS (need the product name). |
+
+She noted there are more systems, but these are the **reporting/output** systems rather than data-entry systems.
+
+---
+
+## Key correction: the Power BI Gateway is the wrong frame
+
+The **on-premises data gateway** does ONE job: let Power BI (cloud) reach a source **inside the building** (SQL Server on CS-SERVER, a network-share file, an on-prem DB). It is **not** a universal SaaS connector — it never touches ALIS, Bill.com, Relias, etc. (those are other people's clouds).
+
+Real question is not "can the gateway talk to these" but **"how does each system hand its data out, and where do we land it so one dashboard can read it."** That's a genuine integration project, not a config toggle.
+
+Three layers to any solution:
+1. **Get data out of each system** — native Power BI connector (rare for niche apps) / REST API (Bill.com, QBO) / scheduled CSV-Excel export (realistic path for most) / 3rd-party connector (CData, Coupler, etc.).
+2. **Land it in one place** — Azure SQL / SharePoint-Excel data model / Power BI dataflow. (A gateway only matters here if that store is on-prem.)
+3. **Build the dashboard** — Power BI on top (easy; right tool). The work is in layers 1–2.
+
+---
+
+## How companies actually do this (cheapest → most serious)
+
+- **Tier 1 — Honest SMB pattern:** someone exports CSV/Excel on a schedule, drops files in **SharePoint/OneDrive**, Power BI reads the folder. Manual refresh, cheap, no devs. What most shops their size actually run. SharePoint = storage + the thing Power BI points at; it does NOT pull data itself.
+- **Tier 2 — Microsoft-native low-code (natural fit — they're on M365 Business Premium):** **Power Automate** (already licensed) pulls from API-capable systems (Bill.com, QBO) on a timer → lands in **SharePoint Lists/Dataverse/Excel** → **Power BI Pro** (~$10/user/mo) + dataflows for scheduled refresh.
+- **Tier 3 — Purpose-built connector services:** Coupler.io / Zapier / Make (SMB) or Fivetran / Airbyte / CData (heavier) → feed a small warehouse (Azure SQL/Fabric/Snowflake) → BI on top.
+- **Tier 4 — All-in-one dashboard SaaS:** Databox / Klipfolio / Grow.com / Domo. Authenticate each system, pick KPIs, done — BUT only for systems they have pre-built connectors for. Cascades' niche senior-living apps almost certainly aren't covered, so you'd still fall back to exports.
+
+---
+
+## Recommendation for Cascades
+
+Because their reporting systems are **mostly niche senior-living SaaS** (ALIS, TELS, You've Got Leads, Helpany), Tier 3/4 connector tools won't have ready connectors for them — so **scheduled exports into SharePoint will be the backbone regardless**, with API automation layered on only for Bill.com + QuickBooks Online.
+
+**Path: Tier 1 → Tier 2.**
+- **Phase 1 (days, ~zero new cost):** pick 3–5 KPIs that actually drive decisions (census from ALIS, AP/cash from Bill.com/QuickBooks) → exports land in SharePoint → Power BI dashboard. Prove value.
+- **Phase 2:** automate the API-capable systems with Power Automate; expand KPI coverage.
+- Uses tools they already pay for; doesn't bet on connectors that don't exist for their industry.
+
+**Senior-living angle to check:** ALIS may offer a built-in analytics/BI add-on or data feed. If so, it could replace a chunk of the plumbing for their most important source (census/clinical). Worth confirming with Medtelligent.
+
+---
+
+## To scope it, get from Ashley
+1. The **specific KPIs** wanted on day one (decides which systems matter).
+2. **Freshness** needed (live vs daily vs weekly — drives cost massively).
+3. Per system: does she/the vendor know of an **API or scheduled export**?
+4. Which **POS** product, and which **Focus HR** plan.
+
+---
+
+## Next action (when we come back)
+Draft the client-facing one-pager: "here's the realistic path + a cheap Phase 1 (census + financial KPIs)" so Ashley has something concrete to approve.