Business Model Blueprint – CMLS
CMLS – Value-Oriented Service Business Model (VSBM)
The Business Model Blueprint consolidates all results from the four rooms in a decision-ready document. It serves as the basis for gate reviews, pilot planning, and investment decisions – and shows how the CMLS can scale from the first pilot to industrialization.
- All 10 core elements of the business model at a glance
- Three-phase roadmap: Pilot → Scaling → Industrialization
- Learnings and key insights from real application of the House Building Logic
The VSBM enables a scalable, economically viable transformation of machine data into measurable business value – via a structured, hybrid monetization model and a phase-based implementation logic.
Core Elements of the Business Model
1️⃣ Problem / Trigger at the Operator
- Unplanned downtime causes direct production and consequential costs
- Reactive maintenance (firefighting mode) → expensive, inefficient, stressful
- Lack of transparency over conditions/causes → poor decisions
- Skills shortage increases risk and extends repair times
- IT/OT complexity makes systematic condition monitoring difficult
2️⃣ Value Proposition
Core Benefit: CMLS reduces unplanned downtime through data-based condition monitoring, analytics, and integrated service processes – and makes the benefit measurable and controllable via KPIs.
Economic Benefit (Customer Value):
- Fewer unplanned downtimes
- Higher plant availability
- Lower maintenance/service costs
- Better planning reliability & decision confidence
- Scalability through digital services (less expert dependency)
3️⃣ KPI Set
Primary KPI:
- Unplanned downtime (h/month) – directly correlated with productivity losses and costs, most clearly assessable from management perspective
Secondary KPIs (explanatory/steering):
- Plant availability (%)
- MTTR (Mean Time to Repair) in h
- Maintenance costs per machine (€/month or €/year)
Deliberately not as lead KPI:
- OEE (too aggregated for operational control)
- MTBF (too abstract for management reporting)
4️⃣ Solution / Core Components (CMLS)
- Data collection & integration (sensors/machine data, IT/OT, optionally MES/ERP)
- Monitoring & dashboards (real-time transparency over machine conditions)
- Analytics & alerts (anomaly detection, cause hints, RUL prognosis)
- Optional: Predictive / SLA services (response times, availability level guarantees)
- Reporting & value proof (KPI-based benefit proof, before/after comparison)
5️⃣ Value Creation – Actors & Process Model
Actors:
- Factory Operator (Owner/User) – provides machine data, receives recommendations
- Machine Builder (machine, support, services) – analyzes data, generates recommendations
- Software Provider (monitoring/data exchange/cloud/models) – platform infrastructure
- Optional: Component Manufacturer (know-how, spare parts, standards) – specialized analysis
Process Logic (End-to-End):
- Setup & Integration
- Monitoring (ongoing data collection)
- Analysis/Alert (detection & interpretation)
- Maintenance decision (recommendation, prioritization)
- Service/Remote Support (execution/coordination)
- Reporting (KPI, value proof)
- Continuous Improvement (optimize models/rules)
6️⃣ Monetization – Pricing Model (Hybrid) + Pricing Strategy
Pricing Model (Hybrid):
- A) Subscription (€/machine/month): Platform operations, monitoring, basic analytics, support → ~€800/machine/month
- B) Variable Components: Advanced Analytics, SLA tiers, service intensity → ~+€300/machine/month
- C) Setup Fee (one-time): Integration/onboarding/enablement → ~€5,000 one-time
Pricing Strategy / Positioning: B → C "Value Ladder"
- Entry market-standard (pilot-capable, low barrier)
- Scaling premium/value-based (SLA/analytics as levers, value capture)
Price Argumentation (Management): Price is argued against downtime costs/risk, not against "software price".
7️⃣ Economics (model-based)
Important: Figures are scenario/assumption model, not actual costs.
Scaling logic per customer:
- Start: 1–3 machines (Pilot)
- Expansion: up to 10 machines (Growth)
- Scaling: 15–30+ machines (Industrialization)
Core Economic Statement:
- Break-even model-based from ~5 machines
- Strongest lever: Machine count per customer
- Price fluctuations & cost variations are not the main lever – volume is
| Scenario | Machines | Contribution Margin/month |
|---|---|---|
| Pilot | 1–3 | Negative to ±0 |
| Break-even | ~5 | ~€0–400 |
| Standard | 10 | ~€4,800 (~44%) |
| Scaling | 20+ | ~€13,600 (~62%) |
8️⃣ Assumptions & Risks (Top 5)
Critical Assumptions / Risks:
| Risk | Mitigation |
|---|---|
| Data quality & data access | Data quality gate as go-live criterion; pilot phase for validation |
| IT security/approvals & integration effort | Staged rollout with clear gates (Go/No-Go) |
| Measurability of benefit (baseline + KPI tracking) | KPI measurement concept before project start; baseline measurement in setup phase |
| Willingness to pay / buy-in (management level) | ROI argumentation via downtime costs; pilot with Proof of Value |
| Support effort at scale (operating model) | Automation of onboarding processes; standardized templates |
9️⃣ Roadmap (Pilot → Scaling → Industrialization)
Phase 1 – Pilot (0–6 months): 1–3 machines, setup, baseline measurement, KPI proof → Go/No-Go decision
Criteria:
- Data quality sufficient and stable
- KPI measurability proven
- First benefit indicators visible
Phase 2 – Scaling (6–18 months): 5–10 machines, SLA build-up, process automation, sharpen pricing → stable operations
Goals:
- Operating model running standardized
- Break-even achieved
- First reference customers
Phase 3 – Industrialization (> 18 months): 20+ machines, standardization, platform integration, expansion to further use cases
Goals:
- Rollout packages fully automated
- Scaling to new customer types/industries
- Ecosystem conformity complete
🔟 Closing Statement (Core Statement)
The Value-Oriented Service Business Model (VSBM) enables a scalable, economically viable transformation of machine data into measurable business value – via a structured, hybrid monetization model and a phase-based implementation logic.
Three Success Factors:
- Stable data quality & reliable integration (technical foundation)
- Measurable benefit via baseline comparison & KPI tracking (building trust)
- Scaling via the number of connected machines per customer (economic engine)
Roadmap at a Glance
- Phase 1: Pilot (0–6 mo.)
- Phase 2: Scaling (6–18 mo.)
- Phase 3: Industrialization (> 18 mo.)
Pilot Phase
Goal: Prove feasibility and generate first measurable benefit indicators.
| What | Detail |
|---|---|
| Scope | 1–3 machines, clear system boundaries |
| Setup | Data connection, configure monitoring, measure KPI baseline |
| Measure | Unplanned downtime before/after, MTTR, availability |
| Decision | Go/No-Go after pilot (data quality + KPI measurability + first benefit indicators) |
| Duration | 0–6 months |
| Economics | Negative to ±0 (investment phase) |
Scaling Phase
Goal: Build stable operations and prove economic viability.
| What | Detail |
|---|---|
| Scope | 5–10 machines per customer |
| Focus | SLA build-up, process automation, sharpen pricing |
| Measure | KPI reporting established, benefit proof documented |
| Decision | Standardization for next customers |
| Duration | 6–18 months |
| Economics | Break-even at ~5 machines, contribution margin grows |
Industrialization Phase
Goal: Scale to 20+ machines and new customers/industries.
| What | Detail |
|---|---|
| Scope | 20+ machines, multiple customers |
| Focus | Rollout packages fully standardized, ecosystem integration |
| Measure | Platform KPIs, ecosystem metrics, customer portfolio |
| Decision | Expansion to further use cases / industries |
| Duration | > 18 months |
| Economics | Contribution margin ~62%+ at 20 machines |
Learnings & Key Insights from Application
The House Building Logic was applied to the CMLS use case (TP2.4) within the Factory-X project. The following key insights emerged:
| Insight | Detail |
|---|---|
| Full applicability | The House Building Logic could be fully applied to the example service idea and led to a comprehensively described business model |
| Structured approach | The step-by-step approach addressed aspects that had not previously been explicitly thought through |
| Focusing decisions required | For a concrete result, focusing is needed (target group, scope) – limiting options or forming scenarios helps |
| Depth through real data | The more concrete the business idea and company context, the more profound the insights. Real data > generic assumptions |
| Bilateral relationships well mappable | The primarily bilateral relationship (machine builder–factory operator) could be clearly modeled with concrete recommendations |
| Multilateral complexity as next step | Applicability in complex multilateral business relationships with multiple parallel business models should be further tested |
| Hybrid application approach | Combination of expert input, workshop, and AI assistant has proven effective |