Welcome to ProBeya
ProBeya is a dual-mode Industrial OS. It runs the consulting program — and the daily operations forever after.
ProBeya is a dual-mode Industrial OS.
It runs the transformation program and the daily operations forever after. Same product. Same data. Same people. Same workflows. Only the cadence changes when the consultants leave.
Most platforms cover one mode. They are either a consulting toolkit (which churns when the program ends) or a fixed shopfloor system (which cannot host a structured transformation). ProBeya is built so the day after the steering committee disbands looks exactly like the day before — minus the slide decks.
The two modes
Mode 1 — Transformation OS
Powers a structured operational transformation: TIER cascades, SQCDP boards, problem solving (5-Why, A3, 8D, DMAIC), action management, change plans, performance dialogues, and the business case behind it all.
Mode 2 — Daily Operating System
Becomes the permanent daily nervous system of the plant: OEE, deviations, lot release, audit-ready evidence, MES connectors, CMMS, EHS, QC, materials, training. 16 capabilities shipping in milestone v1.2.
The mode shift
Same product, same data, same people, same workflows — only the cadence shifts. The consulting handoff is invisible to the shopfloor.
Transformation OS
During a structured transformation program, ProBeya carries the operating rhythm consultants normally hold together with spreadsheets and slide decks:
- TIER meeting cascades — T1 team huddles roll into T2 area reviews, then T3 site reviews. Timed agendas, viewport sync, live presence.
- SQCDP boards — Safety, Quality, Cost, Delivery, People. Traffic-light indicators, safety cross, trend charts, drill-down to root cause.
- Action management — PDCA lifecycle, multi-tier escalation, overdue tracking, verification workflow.
- Problem solving — 5-Why, Ishikawa, A3 reports, 8D, DMAIC. Linked back to the action that created them.
- Change plans — stakeholder mapping, RACI, communication plans, readiness scoring.
- Performance dialogues — monthly leadership cascade with AI-assisted briefs sourced from the live KPI feed (no LLM hallucination of numbers).
- Business case — NPV, IRR, ROI, payback, scenario comparison. The economics that justify the program stay live throughout it.
This is the scaffolding consulting firms used to bring on paper. ProBeya makes it permanent.
Daily Operating System
Milestone v1.2 — opened 2026-04-30 — turns ProBeya into the permanent daily Operating System of a pharma factory. Sixteen capabilities, ~780 atomic tasks, aligned with the McKinsey OS framework:
| # | Capability | What it covers |
|---|---|---|
| 125 | OEE real-time + downtime | Availability × Performance × Quality with planned/breakdown/changeover loss decomposition |
| 126 | Skills matrix + qualifications | 4-level RAG matrix, GxP expirations, e-signed certifications |
| 127 | Leader Standard Work + gemba | Daily checklists per role, signed gemba routes, offline PWA |
| 128 | MES connectors | Werum PAS-X, SAP MES, Rockwell PlantPAx — upstream live data source |
| 129 | Shift handover + Andon | Pre-fill aggregator, hash-chain Andon log, escalation engine |
| 130 | SOPs + 5S + Kaizen | Versioned SOPs (21 CFR Part 11), photo-first 5S, voice-first Kaizen |
| 131 | Deviations + CAPA | 5-why / fishbone / decision-tree, +30/+90 effectiveness checks |
| 132 | Change control | Drives via the form-approval engine, immutable on finalization |
| 133 | Batch record review | Lot release gate, EBR vs MBR side-by-side, multi-reviewer cascade |
| 134 | CMMS preventive + corrective | Work orders, calibration, equipment history, mobile WO offline |
| 135 | EHS + behavior-based safety | Anonymous near-miss, OSHA 300 + EU-OSHA exports |
| 136 | QC daily — sampling, IPC, OOS/OOT, CoA | Western Electric rules control charts, single LIMS connector |
| 137 | Material flow + Kanban | Append-only moves with idempotency, FIFO/FEFO, blocked status |
| 138 | Training & onboarding 30/60/90 | Forking template pattern, dual-control e-sign, LMS idempotency |
| 139 | Performance dialogues | Server-side feed registry, libsodium per-org coaching notes |
| 140 | Audit readiness + inspector portal | 12 evaluators, weighted score 0–100, tamper-evident ZIP evidence pack |
Phase 128 (MES) is upstream of 125, 133, 136, 137, 139. Phase 126 (skills) is upstream of 127, 134, 138. Phase 140 (audit readiness) consumes from all prior — and its /inspector/[token] route is the differentiator that closes pharma deals.
Full sequencing in the v1.2 roadmap.
The mode shift
The shift from Mode 1 to Mode 2 is invisible. Same workflows, same screens, same data, same people. Only the cadence changes.
| Aspect | Mode 1 — Transformation | Mode 2 — Daily Operations |
|---|---|---|
| Cadence | Weekly steering, monthly review | Hourly TIER 1, daily TIER 2, weekly TIER 3 |
| Owner | Program director, OpEx coordinator | Plant director, area leader, QA |
| Primary signal | Maturity score, milestone burndown | OEE, deviations, lot release, audit posture |
| Workflow | Same TIER, SQCDP, problem solving | Same TIER, SQCDP, problem solving |
| Data | Same database, same boards, same actions | Same database, same boards, same actions |
The consultants leave. The board stays on. Tomorrow morning’s huddle uses the same screen the steering committee did last night.
Reading paths
OpEx coordinators
Start with Core Concepts → routines via TIER & SQCDP boards → Hoshin Kanri → daily-OS scope above.
QA & compliance
Data compliance → Security → Phase 131 deviations / Phase 133 batch review / Phase 140 inspector portal in the v1.2 list above.
Plant directors
TIER & SQCDP boards → Hoshin Kanri → daily-OS scope above → mode-shift continuity.
Three ways to integrate
REST API
Standard HTTP endpoints. Works with any language, any CI/CD pipeline, any automation tool.
tRPC
End-to-end TypeScript type safety. Import the router type and get autocomplete from database to UI.
MCP
Connect Claude, GPT, or any AI agent to your boards, KPIs, and actions via the Model Context Protocol.
Multi-tenant by design
Every API call is scoped to your organization. Your tenant at acme.probeya.com is isolated from every other tenant at the database level using PostgreSQL row-level security. The organizationId is resolved from the subdomain and injected server-side — it is never trusted from client input.
acme.probeya.com → Organization: Acme Pharma
pfizer.probeya.com → Organization: Pfizer Ops
ucb.probeya.com → Organization: UCB Manufacturing
Start building
5-Minute Quickstart
Get your API key and make your first call.
Core Concepts
Understand the data model before you build.
API Reference
Full endpoint documentation with examples.
Links
- Live demo — demo.probeya.com
- Source — github.com/obeya-cloud/obeya
- Built by — Actigence Management Consulting
Was this page helpful?