1. Objective
The goal of this WIKI is to describe the usage of the Focused Build data provider available in Focused Insights for SAP Solution Manager.
2. Overview
The Build data provider (DP_BUILD) is designated to users using both Focused Insights and Focused Build for SAP Solution Manager Applications.
It provides a real-time insight on the most used documents of focused build based on a set of standard indicators for Velocity, Reliability, Efficiency and Quality.
Combined with the Test data providers it provides IT managers with the main indicators for project and DevOps management as shown below :
Metrics | KPI | Description | Source |
Change Frequency | Velocity | Number of changes transported to productions. | Change Mgt |
Change Volume | Velocity | Number of objects transported to productions. | Change Mgt |
Tests Execution | Velocity | Number of tests (manual and automatic) executed. | Test Suite |
Deployment Speed | Velocity | Number of Work Items released. | Focused Build |
Tests Automation Rate | Quality | Number of regression, security and performance automated tests. | Test Suite |
Code Quality Issues | Quality | Code and security checks issues detected in production. | Custom Code Mgt |
Test Coverage | Quality | Percentage of successful manual and automatic tests execution | Test Suite |
Security & Compliancy Issues | Quality | Security and conformity issues detected in production. | Configuration Validation |
Innovation Rate | Efficiency | Number of Business Requirements released. | Focused Build |
Deployment Frequency | Efficiency | Number of Work Packages released. | Focused Build |
Lead Time global | Efficiency | Time from design to deployment in production. | Focused Build |
Lead Time Test to Production | Efficiency | Time from test to deployment in production. | Focused Build |
Mean Time To Recover (MTTR) | Efficiency | Time recover from an issue. | ITSM |
User Incident Volume | Reliability | Number of customer outages. | ITSM |
Alerts Volume | Reliability | Number of high and very high applications or systems issues. | System Monitoring |
Application Performance | Reliability | Response time for main transaction / jobs / interfaces. | System Monitoring |
Availability | Reliability | Up time for applications servers, hosts, databases, service, transactions, interfaces. | System Monitoring |
Data Consistency Issues | Reliability | Number of inconsistency, integrity issues for business data. | Data Consistency Mgt |
2.1 Documents
Three types of documents are supported by the DP_BUILD:
- Work Item
- Work Package
- Requirement
2.2 Measurements
Four measurements are supported by the DP_BUILD:
- Number
- Snapshot
- Lead Time
- Progress
2.3 Renderers
The Build data provider supports the following list of renderers:
- Line Chart
- Pie Chart
- Donut Chart
- Line-Column Chart
- Dual Line Chart
- Dual Line-Column
- Dual Bar-Column
- Stack Bar Chart
- Stack Column Chart
- Stack Column Chart2 Label
- Waterfall Chart
- Column Chart
- Bar Chart
- Table History Renderer
- Trend Table Renderer
- Dynamic Table
2.4 Data Provider Option
Group | Filter | Selection | Description | Values |
Parameters | Document | Single | List of the available documents. | The possible values are Work packages, Work items and IT requirements. |
Status | Multiple | List of the available status. | The possible values are created, scoping, scope finalized, scope extension, rejected postponed, to be developed... | |
Target Status
| Single | List of the available target status. | The possible values are created, scoping, scope finalized, scope extension, rejected postponed, to be developed... | |
Classification | Single | List of available classifications. | The possible values are WRICEF, Fit, GAP, and Non-functional. | |
Project | Single | List of the available projects. |
| |
Sub project | Single | List of the available sub projects. |
| |
Wave | Single | List of the available waves. |
| |
Sprint | Single | List of the available sprints.
|
| |
Metric | Metric | Single | Available metrics. | The possible values are Number, Lead time, Snapshot and Progress. |
Open | Multiple | Open statuses for the progress metric |
| |
Closed | Multiple | Closed statuses, used only with the progress metric |
| |
Category | Level1 | Single | Filter for categories |
|
Level2 | Single | Filter for categories |
| |
Level3 | Single | Filter for categories |
| |
Level4 | Single | Filter for categories |
|
PS: In this data provider, every document is related to a specific wave and if the user selects a period that is not included in the start date and end date of the wave he will not get any available data displayed.
3. Metrics
3.1 Number
This metric aims to show the number of documents (related to a specific document type: Work Item, Work Package or requirement) changing to the selected status (created, in development, completed…) for the given resolution (day, week, …).
Group | Filter | Mandatory | Relevant | Not Relevant |
Parameters | Document | X |
|
|
Status |
| X |
| |
Target Status |
|
| X | |
Classification |
| X |
| |
Project | X |
|
| |
Sub project |
| X |
| |
Wave |
| X |
| |
Sprint |
| X |
| |
Metric | Metric | X (Number) |
|
|
Open |
|
| X | |
Closed |
|
| X | |
Category | Level1 |
| X |
|
Level2 |
| X |
| |
Level3 |
| X |
| |
Level4 |
| X |
|
3.1.1 Scenario Examples of Queries
Example: Number of Work Packages Created per Week during this Month.
To have such graph we use:
- Line chart as renderer type
- This month (period) / Week (resolution) as time range
- Work package as document type
- Created as status
- Number as metric
In this case we will use the metric number :
/STDF/DP_BUILD: COLOR=#1f77b4|legend=Number of Created Work Package|OCC_JUMP_IN=|SLA=|TREND=| G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|FILTER_VALUE=|visible=true|OBJECT=S1IT|STATUS=E0001| TARGET=|CLASSIFICATION=|PROJECTS=|SUBPROJECTS=|WAVE=|SPRINT=|METRIC=NUMBER|OPEN=|CLOSED=| LEVEL_1=|LEVEL_2=|LEVEL_3=|LEVEL_4=|display_value=false
Another example: Number of Work Packages having the status Created and To Be Developed per Month during the last 2 Months.
To have such graph we use:
- Dynamic Table as renderer type
- Last 2 Months (period) / Month (resolution) as time range
- Work package as document type
- Created and To Be Developed as status
- Number as metric
In this case we will use the metric number
/STDF/DP_BUILD:COLOR=#1f77b4|legend=Number|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|
DISPLAY_ATTRIBUTES=MASTER_GUID,ITR_NAME,DESCRIPTION,ITR_STATUS,ITR_STATUS_TXT,ITR_TYPE,ITR_CATEGORY,WAVE_GUID,WP_SCHEDULE,DUE_DATE,ARCHITECT,PLANNED_EFFORT,
COMPLETION,BUILD_TEAM,FUNC_SPEC_DUE_DATE,TOTAL_WORK_ITEMS,AGE,PRIORITY,PROJECT_GUID,PROJECT_NAME,FUNC_SPEC_STAT|visible=true|OBJECT=S1IT|
STATUS=E0001,E0022|TARGET=|CLASSIFICATION=|PROJECTS=0E6D000C94821ED8A6DE030511ED5D0F|SUBPROJECTS=
|WAVE=|SPRINT=|METRIC=NUMBER|OPEN=|CLOSED=|LEVEL_1=|LEVEL_2=|LEVEL_3=|LEVEL_4=|display_value=false
3.2 Lead Time
This metric aims to show the number of days for a document to reach a target status from a source status for the given resolution (day, week, …).
Group | Filter | Mandatory | Relevant | Not Relevant |
Parameters | Document | X |
|
|
Status | X |
|
| |
Target Status | X |
|
| |
Classification |
| X |
| |
Project | X |
|
| |
Sub project |
| X |
| |
Wave |
| X |
| |
Sprint |
| X |
| |
Metric | Metric | X (Lead Time) |
|
|
Open |
|
| X | |
Closed |
|
| X | |
Category | Level1 |
| X |
|
Level2 |
| X |
| |
Level3 |
| X |
| |
Level4 |
| X |
|
3.2.1 Scenario Examples of Queries
Example: Wait Time to start development on Work Packages.
To have such graph we use:
- SLR table renderer as renderer type
- Last 2 months (period) / month (resolution) as the time range
- Work package as document type
- Created as status
- To be Developed as target status
- Lead Time as metric
In this case we will use the metric lead time
/STDF/DP_BUILD:COLOR=#1f77b4|legend=Lead Time of Work Packages to go from the status Created to the status to be
Developed|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|FILTER_VALUE= |visible=true|
OBJECT=S1IT|STATUS=E0001|TARGET=E0022|CLASSIFICATION=|PROJECTS=5CF3FCDCEC001EE8B4EF4963162A7D42|
SUBPROJECTS=|WAVE=|SPRINT=|METRIC=LEAD_TIME|OPEN=|CLOSED=|LEVEL_1=|LEVEL_2=|LEVEL_3=|LEVEL_4=
3.3 Snapshot
This metric aims to show the number of documents having the selected status (created, to be developed, in development, …).
This metric is a cumulative one and it supports only the day resolution.
Group | Filter | Mandatory | Relevant | Not Relevant |
Parameters | Document | X |
|
|
Status | X |
|
| |
Target Status |
|
| X | |
Classification |
| X |
| |
Project | X |
|
| |
Sub project |
| X |
| |
Wave |
| X |
| |
Sprint |
| X |
| |
Metric | Metric | X (Snapshot) |
|
|
Open |
|
| X | |
Closed |
|
| X | |
Category | Level1 |
| X |
|
Level2 |
| X |
| |
Level3 |
| X |
| |
Level4 |
| X |
|
3.3.1 Scenario Examples of Queries
Example: Number of Work Packages with Status To Be Developed.
To have such graph we use:
- Column chart as renderer type
- Last 6 months (period) / day (resolution) as the time range
- Work package as document type
- To Be Developed as status
- Snapshot as metric
In this case we will use the metric snapshot
/STDF/DP_BUILD:COLOR=#ff7f0e|legend=Number of Work Packages with Status To Be Devloped
|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|OBJECT=S1IT
|STATUS=E0022|TARGET=|CLASSIFICATION=|PROJECTS=0E6D000C94821ED8A6DE030511ED5D0F|SUBPROJECTS=|WAVE= |SPRINT
= |METRIC=SNAPSHOT|OPEN=|CLOSED=|LEVEL_1=|LEVEL_2=|LEVEL_3=|LEVEL_4=|display_value=false
3.3 Progress
This indicator analyses the status of a document of a project for a specific wave.It returns a set of measurements (Backlog, Extension, Completion, Rescheduled, Others, Remaining) to track the progress of wave completion between the start date of the wave and the end date of the wave or the current date if the wave is not finished.
The Waterfall Chart Renderer is the only renderer supporting this metric.
Group | Filter | Mandatory | Relevant | Not Relevant |
Parameters | Document | X |
|
|
Status |
|
| X | |
Target Status |
|
| X | |
Classification |
|
| X | |
Project | X |
|
| |
Sub project |
|
| X | |
Wave |
|
| X | |
Sprint |
|
| X | |
Metric | Metric | X (Progress) |
|
|
Open |
| X |
| |
Closed |
| X |
| |
Category | Level1 |
|
| X |
Level2 |
|
| X | |
Level3 |
| X |
| |
Level4 |
| X |
|
3.4.1 Scenario Examples of Queries
Example: Progress of the Created Work Packages during this month
To have such graph we use:
- Waterfall chart as renderer type
- This month (period) / Week (resolution) as the time range
- Work package as document type
- created as status
- In development as target status
- Progress as a metric
In this case we will use the metric progress
/STDF/DP_BUILD: COLOR=#1f77b4|legend=Progress of Work Packages| OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|
COLOR_RATING=|DISPLAY_ATTRIBUTES=|FILTER_VALUE=|visible=true|OBJECT=S1IT|STATUS=E0001|TARGET=E0017|
CLASSIFICATION=|PROJECTS=5CF3FCDCEC001EE89BFAB11534D0995B|SUBPROJECTS=5CF3FCDCEC001EE89BFABAD1F7FE795F
|WAVE=5CF3FCDCEC001EE89BFABAD1F803195F|SPRINT=
|METRIC=PROGRESS|OPEN=|CLOSED=|LEVEL_1=|LEVEL_2=| LEVEL_3=|LEVEL_4=|display_value=false
