DevSight
Hybrid-RAG deviation investigation assistant
Internal enterprise application — built at Takeda Pharmaceutical
The problem
Investigating a new deviation meant manually keyword-searching four years of Trackwise records — roughly 30 minutes per question, and brittle: the right precedent was easy to miss if it used different wording. Investigators needed semantic recall over 2,213+ resolved cases without leaving the 30-day closure window.
Architecture
- 4 yrs deviations
- 2,213+ cases
- 10 fields
- Chunk → 31,577 units
- Embed
- Databricks Vector Search
- Date metadata
- Equipment pre-filter
- Vector rank
- Post-filter client-side
- Streamed via ellmer
- Cites real cases
- 10-turn memory
What it did
DevSight (formerly TrackLA) was a hybrid-RAG assistant over four years of Trackwise deviations, 2022–2026: 2,213+ resolved cases chunked into 31,577 searchable units. It replaced ~30-minute manual keyword searches with ~2-minute semantic ones — a 93% time reduction — and surfaced the actual precedent cases behind every answer, so an investigator could check the source instead of trusting the summary.
Two-stage hybrid RAG
Search ran in two stages: a date-metadata filter narrowed the candidate set, then semantic vector search ranked across 10 Trackwise fields. Date filtering happened post-search, client-side — a deliberate workaround for Databricks Vector Search not handling DATE range operators cleanly.
- Conversation memory across the last 10 turns
- Real-time token streaming with voice input and read-aloud
- Feedback capture after a 50-second countdown
- Document upload limited to Word and Excel — image and PDF disabled on purpose, to preserve streaming
- Mobile-optimized with a fixed input bar, for use away from a desk
Why it was retired
DevSight was decommissioned in 2026 when the site consolidated onto standardized global applications. That was a portfolio decision, not a verdict on this application. At retirement it held a 4.8/5 self-reported satisfaction score, was still delivering the 93% search-time reduction it launched with, and shipped its largest release — v2.7.0, the final one — in its last month of operation.
What survived
The retrieval engine outlived the app. The hybrid-RAG layer built here — the chunking, the two-stage filter, the R-computes / LLM-narrates split — runs inside BioTrack today against the same vector index. Retiring an application and retiring a capability are different decisions, and only the first one was made.