Green Room β CMLS Value Creation
CMLS β Value Creation
The Green Room describes who takes which role and how the service is delivered operationally. Who provides which data? Who delivers which services? Who bears which costs? The result is a complete picture of the value network and the end-to-end process.
- Which actors are involved in the ecosystem?
- How do data, services, and payments flow between actors?
- How does the process run from setup to ongoing operations?
The result: A Roles & Actors Matrix, two value network views (simplified + complete), and a detailed value creation process with setup and lifecycle phases.
- Roles & Actors
- Value Network
- Value Creation Process
Roles & Actors Matrixβ
The CMLS ecosystem comprises four main actors, each taking different roles in the data ecosystem.
Key Actorsβ
| Actor | Comment | Data Provider | Data Consumer | Service Provider | Infrastructure Provider | Equipment Provider | User |
|---|---|---|---|---|---|---|---|
| Factory Operator | = User | β Usage data | β | β | β | β | β |
| Machine Builder | = Provider and designer of the new business model | β Usage data | β Recommendations based on data | β | β | β Machine | β |
Othersβ
| Actor | Comment | Data Provider | Data Consumer | Service Provider | Infrastructure Provider | Equipment Provider | User |
|---|---|---|---|---|---|---|---|
| Component Manufacturer | Optional, subcontracted by machine builder | β Specification data in design + usage data | β Recommendations based on data | β | β | β Component | β |
| Software Provider | β | β | β | β | β Data infrastructure & maintenance system | β | β |
| Supplier | β | β | β | β | β | β | β |
| Service Provider | β | β | β | β | β | β | β |
The CMLS is primarily a bilateral business relationship between machine builder and factory operator. The machine builder takes on multiple roles simultaneously: Equipment Provider (machine), Data Consumer (receives condition data), Service Provider (maintenance recommendations), and Data Broker (coordinates access permissions for subcontractors).
Value Networkβ
Simplified Picture (Main Actors)β
The simplified value network shows the main flows between the two key actors:
| From | To | Flow | Type |
|---|---|---|---|
| Machine Builder | Factory Operator | Smart Machine | Goods (physical) |
| Machine Builder | Factory Operator | Monitoring 2.0 App | Services (software) |
| Machine Builder | Factory Operator | Analysis & Recommendation | Services (data-based) |
| Factory Operator | Machine Builder | Machine Status Report | Data |
| Factory Operator | Machine Builder | Service fee / Subscription | Financial |
Roles in the simplified picture:
- Machine Builder: Equipment Provider + Data Consumer + Service Provider + Data Broker (focus: authorization of subcontractors)
- Factory Operator: End User + Data Provider
Complete Picture (All Actors)β
In the complete picture, additional actors are included:
| Additional Actor | Role | Flows |
|---|---|---|
| Software Provider (Machine Builder side) | Infrastructure Provider (data space connector) + Technical Enabler (Asset Data Management) | SW licenses β Machine Builder |
| Software Provider (Factory Operator side) | Infrastructure Provider (shopfloor data) + Infrastructure Provider (data space connector) + Technical Enabler (Asset Data Management) | SW licenses β Factory Operator |
| Component Manufacturer | Equipment Provider + Service Provider + Data Consumer | Components β Machine Builder; Component Status Report β Machine Builder; Analysis & Recommendations β Machine Builder |
| Software Provider (central) | Data Space Operator + Central Service Provider | SW/Service β Machine Builder & Factory Operator |
Always start with the simplified picture (only key actors). The complete picture only becomes relevant when partner contracts, data space governance, and software licenses are being concretely negotiated.
Value Creation Processβ
The CMLS process is divided into two phases: a one-time Setup Phase and a permanent Lifecycle Phase.
Setup Phase (one-time per customer)β
The setup phase ensures all technical and organizational prerequisites for the ongoing service are met.
| Step | Actor | System/Tool | Action |
|---|---|---|---|
| 1 | Maintenance Team (Factory Operator) | β | Conclude service contract, define scope (1β3 machines), define KPI baseline |
| 2 | Service Team (Machine Builder) | Asset Data Management System | Conduct risk analysis (FMECA, criticalities) |
| 3 | Factory Operator | Asset Data Management System | Establish IT/OT data connection (REST API / MQTT gateway) |
| 4 | Factory Operator | Asset Data Management System | Configure system |
| 5 | Factory Operator | Monitoring 2.0 App | Install Monitoring App |
| 6 | Factory Operator | Monitoring 2.0 App | Configure Monitoring App (thresholds, alerts, dashboards) |
| 7 | Machine Builder | Asset Data Management System | Configure system (counterpart: data receipt, analytics pipeline) |
Deliverables from the Setup Phase:
- Live data connection of pilot machines
- KPI baseline & measurement plan (before-values)
- Configured monitoring + alerting
- Acceptance/go-live checklist
Lifecycle Phase (continuous)β
The lifecycle phase is the actual ongoing service. It runs 365 days a year.
| Step | Actor | System/Tool | Action |
|---|---|---|---|
| 1 | Factory Operator | Asset Data Management System | 365d Asset Monitoring β continuous data collection |
| 2 | Factory Operator | Monitoring 2.0 App | Action required detected ("Orange light") β view asset details and next steps |
| 3 | Maintenance Team (Factory Operator) | β | Conduct inspection |
| 4 | Factory Operator | Monitoring 2.0 App | Create machine condition report |
| 5 | Factory Operator | Asset Data Management System | Provide condition report (via data space) |
| 6 | Machine Builder | Asset Data Management System | Receive condition report |
| 7 | Service Team (Machine Builder) | β | Analyze machine data |
| 8 | Service Team (Machine Builder) | β | Generate maintenance recommendations |
| 9 | Machine Builder | β | Transmit maintenance recommendations |
| 10 | Maintenance Team (Factory Operator) | β | Receive and implement maintenance recommendations |
Optional β Component Manufacturer Loop:
| Step | Actor | Action |
|---|---|---|
| A | Component Manufacturer | Receive component data (from machine builder via data space) |
| B | Service Team (Component Manufacturer) | Analyze component data, generate maintenance recommendations |
| C | Component Manufacturer | Transmit maintenance recommendations to machine builder |
The complete CMLS process goes from data collection at the factory operator through analysis at the machine builder to maintenance recommendations back to the factory operator. The data space acts as a sovereign, purpose-bound handover layer β no uncontrolled data sharing.