App Builder Workshop
Goal
Participants create an application that helps users make better operational decisions faster.
The backend already exists. Participants do not create models or infrastructure – they build on top of available operational context. See Hands-On Backend.
Participant Flow
The workshop applies Understand → Act → Create to a concrete problem.
flowchart LR
V[1. Choose<br/>a vertical] --> P[2. Choose<br/>a problem] --> O[3. Define<br/>the outcome] --> S[4. Pick the smallest<br/>valuable step] --> B[5. Build<br/>the app] --> M[6. Show &<br/>measure value]
| Step | Phase | What participants do |
|---|---|---|
| 1. Choose a vertical | Understand | Telco, Satellite, Media, Infrastructure, or Government |
| 2. Choose a problem | Understand | Select one of the 3 predefined challenges for that vertical |
| 3. Define the outcome | Understand | Who is the user? What decision do they need to make? What does success look like? |
| 4. Pick the smallest valuable step | Act | Decide the minimum app that answers the key question |
| 5. Build the app | Create | Build the application on top of the pre-built backend |
| 6. Show & measure value | Create | Explain which decision became faster or better, and what the next increment would be |
Outcome Canvas
Participants fill this in before building:
| Question | Answer |
|---|---|
| Who is the user? | |
| Which decision do they need to make? | |
| What slows that decision down today? | |
| What does success look like? | |
| How would we measure the value? | |
| What is the smallest valuable first version? | |
| What would the next increment be? |
Problem Catalog
Each vertical offers three predefined problems. Every problem is phrased as a key question the app must answer. The backend guarantees that the data for each problem is available and that the scenario produces a clear answer – see Problem Data Design.
| Vertical | Problem | Key question | Suggested app pattern |
|---|---|---|---|
| Telco | Priority Dashboard | Which services require immediate attention? | Service Health Center |
| Customer Impact View | Which services affect the most customers? | Service Health Center | |
| Capacity Risk Workspace | Which services may become problematic soon? | Risk & Trend Workspace | |
| Satellite & Space | Mission Readiness Dashboard | Which missions require attention? | Service Health Center |
| Ground Segment Workspace | Which resources are at risk? | Risk & Trend Workspace | |
| Customer Service Assurance View | Which services affect customers? | Service Health Center | |
| Media | Event Operations Center | Which live events are at risk? | Service Health Center |
| Executive Service Overview | What is the overall operational situation? | Executive & Regional Overview | |
| Incident Workspace | Which issue should operators investigate first? | Incident Workspace | |
| Infrastructure | Operations Control Center | What requires action now? | Service Health Center |
| Critical Asset Dashboard | Which assets represent the highest risk? | Risk & Trend Workspace | |
| Regional Operations View | How are locations performing? | Executive & Regional Overview | |
| Government & Public Safety | Incident Coordination Workspace | What requires escalation? | Incident Workspace |
| Command Center Dashboard | Where should operators focus? | Service Health Center | |
| Risk Prioritization View | Which locations require immediate attention? | Executive & Regional Overview |
The suggested pattern is a starting point, not a rule – participants may combine patterns.
Expected App Outcomes
All patterns use only backend data: static service metadata and live data from DataMiner services and elements. Scores such as health or risk are defined by the participant in the app – deciding how to prioritize is part of the exercise.
Service Health Center
An at-a-glance view to prioritize services.
| Shows | Based on |
|---|---|
| Service status | Service alarm state |
| Alarms | Active alarms per service |
| Priority / risk | Participant's logic, e.g. Criticality × alarm severity |
| Impact | Customers Served |
| Upcoming activities | Schedule parameters (events, passes) |
Incident Workspace
A focused view to investigate one service or issue.
| Shows | Based on |
|---|---|
| Service details | Static service metadata, elements, Site |
| Alarms | Active alarms with severity and age |
| History | Alarm history (last incident) |
| Escalation | Alarm age vs. Escalation Threshold |
| Ownership | Service Owner, Operations Team |
Risk & Trend Workspace
A view to spot what will become a problem soon.
| Shows | Based on |
|---|---|
| Current value vs. limit | Parameter value and threshold parameter |
| Evolution | 24 h trend data |
| Business context | Criticality, Customers Served |
Executive & Regional Overview
A summary across services or locations.
| Shows | Based on |
|---|---|
| Situation summary | Count of services per alarm state |
| Customers affected | Customers Served of impacted services |
| Per location / region | Site, Region, alarms per site |
Note
An Operations Copilot (natural-language questions such as "What requires immediate attention?") is built in the Specialized Agents Workshop, not in App Builder. AI output is never stored in the backend.
Facilitation Guidance
| Do | Avoid |
|---|---|
| Start every team with the Outcome Canvas | Letting teams open App Builder before defining the outcome |
| Ask "Which decision does this help?" for every widget | Feature tours and "build everything" apps |
| Celebrate a small working app that answers the key question | Rewarding visual polish over value |
| Encourage switching problems if a higher-value one emerges | Continuing a path just because it was started |
| Close with "What is your next increment and why?" | Ending on the tool instead of the outcome |