01
Data ingestion
Manual-first in Phase 1 (SE16 / SQVI exports through a governed upload channel). ADF + SAP OData in Phase 2. The ingestion layer is the only thing that changes between phases.
ProductOne engineered platform.
One engineered platform.
Five planes. Nine layers.
PULSE BI is a governed analytics platform — ingestion, modeling, semantic, dashboards, and governance operating as one system. Built to ship in 4-6 weeks and scale without being rebuilt.
The Five Planes
A platform, not a feature list.
Every dashboard PULSE BI delivers runs through the same five planes. The planes don't get skipped, swapped, or shortcut when a customer's timeline gets tight.
02
Modeling engine
Rule-based transformations, dbt models, quality checks, and versioned data products. Every dataset has a version tag and a reviewer.
03
Semantic layer
Enterprise KPI dictionary with shared business logic and lineage. One definition of revenue, one definition of on-time — across every dashboard and every function.
04
Visualization apps
Role-scoped dashboards for executives, finance, operations, procurement, and IT. Each persona sees the KPIs their role actually makes decisions on.
05
Governance core
RBAC, row-level security, release gates, audit logging, retention posture, and evidence bundle exports. Governance is in the platform, not bolted on.
Phase 1 → Phase 2
Only the ingestion layer changes.
PULSE BI runs as a manual-first delivery in Phase 1 and upgrades to automated ingestion in Phase 2. The rest of the platform — modeling, semantic, apps, governance — stays exactly the same.
Phase 1
Manual-first delivery
SAP system changes required
None
Ingestion mechanic
Governed manual export
Time to first dashboard
4-6 weeks
Modeling / semantic / apps / governance
Layers 3-9
Fallback path if automation breaks
—
Audit readiness
Full
Phase 2
Automated ingestion
SAP system changes required
OData service configured
Ingestion mechanic
ADF + incremental schedules
Time to first dashboard
Same (no rebuild)
Modeling / semantic / apps / governance
Layers 3-9 (unchanged)
Fallback path if automation breaks
Phase 1 manual path preserved
Audit readiness
Full (identical controls)
Transition is governed by readiness criteria — data volume, stability window, OData approval — not the calendar.
Governance Core
Built for the audit that hasn't happened yet.
PULSE BI's governance isn't a compliance checklist bolted onto a reporting tool. It's three load-bearing disciplines that sit inside every dashboard, every release, every export.
Role-based access + row-level security
Every dashboard enforces RBAC at the object level and RLS at the row level. A procurement viewer in one region sees only that region's suppliers — never the rest.
Lineage, version tags, and release logs
Every KPI traces back to its source. Every dataset has a version tag. Every production release has a QA sign-off attached. Nothing ships without it.
Evidence bundles for audit cycles
Export a release's full evidence pack — source manifest, version tags, release log, QA approval, retention class — as a single signed artifact for your auditors.
Architecture Workshop
Review the platform with our delivery lead.
90 minutes, no deck. We walk through your data landscape, compliance posture, and which of the nine layers need attention first.