| Status | Approved |
| Owner | |
| Stakeholders |
Issue
A decision is required whether to develop a new PPM custom app for Item creation & maintenance in-house or whether to purchase a partner solution.
Recommendation
It is recommended that a custom app is built in-house, due to the following factors:
- Significantly lower project and ongoing cost
- In-house resources have experience in developing such an app
- Full influence over design to meet business requirements
Background & Context
The 'Portfolio Items' app is the main transaction used for executing PPM processes in S4HANA. The standard UI for this app comes with the following shortcomings:
- Based on old WebDynpro technology; the screens are not user friendly - they are convoluted, poorly laid out and not aligned with Fiori design concepts.
- Creation of a PPM Item requires multiple steps, navigating back and forth between S4HANA and SAC Planning. The standard UI cannot guide the user through this process and gives no indication of completeness of the required data.
- Business expectations for the user interface are based on the current WeGo/Accolade and Colmar tools which provide more user-friendly and intuitive user interface than PPM. KDD096 - replacement of Accolade assumes that a new improved UI will be provided
SAP does not have any improvement for the UI planned on their roadmap and have suggested a partner solution from sophisTex which provides a more flexible, intuitive and user-friendly interface. The following features are included:
- S/4HANA certified Add-on by SAP ICC
- Achieves Clean Core, no impact on S/4HANA EPPM upgradability
- Delivered with a default set of configuration to reduce implementation time
- Flexibility to further customize and enhance
- Stage Gate approval functionality is incorporated.
The alternative is to develop a custom app in-house which, in conjunction with the SAP Consulting Solution for Stage Gate approvals, would provide the same capabilities.
Assumptions
It is assumed that:
- All options will require internal custom development for:
- Integration with OpenText
- Integration with SAC
- Automation of follow-on actions on Stage Gate approval
- The sophisTex solution will be fully tested and relatively bug-free, while an in-house development will inherently require more effort in testing and resolution of bugs.
- A dedicated UI developer would be required for a fully custom UI build.
- There will be approximately 2000 users of PPM
- SAP PPM licenses will be required regardless of the UI
Constraints
N/a
Impacts
The decision on UI does impact up-stream or down-stream processes or data.
The main impacts of the decision are:
- Financial (both to the project and ongoing BAU costs)
- In-house development team capacity
- Time to deliver
- Testing effort
Financial Impact
- The recommended option to develop an in-house solution has a lower cost, better user acceptance both for the project and ongoing.
- The sophisTex solution has a subscription-based pricing model with ongoing costs based on user numbers.
- Screen Personas has similar cost as the custom UI development but may have limited flexibility on UI
- Standard app is not an option as it challenges the decision of KDD096
Option A: In-house Development
| Approx. Cost (5 years) | Project Cost | Ongoing Cost | Total 5 years |
|---|---|---|---|
| =20 days design for very complex WRICEF | € 20,000 | ||
| =80 days * 1000 EUR for in-house UI build | € 80,000 | ||
| =20 days SAP build for approval workflow solution | € 40,000 | ||
| =30 days in-house build for approval workflow solution | € 30,000 | ||
| =ongoing cost 10% of the build cost per year | € 15,000 | ||
| € 170,000 | € 15000 | € 245,000 |
Option B: sophiTex Partner Solution
| Approx. Cost (5 years) | Project Cost | Ongoing Cost | Total 5 years |
=€ 450 *20 users *2 years during build & test | €18,000 | ||
=€140k *1 year for go-live (2000 users) | €140,000 | ||
=€140k *2 years post go-live (2000 users) | € 280,000 | ||
| =40 days * €1500 for sophisTex consulting during build (OT integration, SAC integration, workflow, other enhancements) | € 60,000 | ||
| =20 days * €1500 for sophisTex support during SIT/UAT/cutover | € 30,000 | ||
| =15 days * €1000 for in-house design for complex WRICEF | € 15,000 | ||
| =20 days * €1000 in-house build - custom PPP configuration | € 20,000 | ||
| =30 days in-house build * €1000 for approval workflow solution | 30,000 | ||
| € 313,000 | € 280,000 | € 593,000 |
Option C: Screen Personas
| Approx. Cost (5 years) | Project Cost | Ongoing Cost | Total 5 years |
|---|---|---|---|
| =20 days design for very complex WRICEF | € 20,000 | ||
| = 25days design for custom fields and validations | € 25,000 | ||
| =35 days * 1000 EUR for in-house UI build | € 35,000 | ||
| =20days* 1000 EUR for in-house OT integration/enhancment | € 20,000 | ||
| =20 days SAP build for approval workflow solution | € 40,000 | ||
| =30 days in-house build for approval workflow solution | € 30,000 | ||
| =ongoing cost 10% of the build cost per year | €15000 | ||
| € 170,000 | € 15000 | € 245,000 |
Option D: Standard Webdynpro screen
| Approx. Cost (5 years) | Project Cost | Ongoing Cost | Total 5 years |
|---|---|---|---|
| =20 days design for very complex WRICEF | € 20,000 | ||
| =20days* 1000 EUR for in-house OT integration/enhancement | € 20,000 | ||
| = 25days design for custom fields and validations | € 25,000 | ||
| =20 days SAP build for approval workflow solution | € 40,000 | ||
| =30 days in-house build for approval workflow solution | € 30,000 | ||
| =ongoing cost 10% of the build cost per year | €11500 | ||
| € 135,000 | € 11500 | € 192,500 |
Business Rules
N/a
Options considered
Option A: Custom In-house Development
A new custom app is developed with the following features:
- Fiori design features
- Ability to jump into SAC Planning for maintaining project financials
- Integration with OpenText workspace
- Integration with SAP Consulting Solution for Stage Gate Approvals (cost included in estimate above)
- Follow-on actions for Stage Gate Approval
Option B: sophisTex Partner Solution
The sophisTex PPP solution delivers a customizable UI for PPM Item creation and maintenance. It is provided on a subscription-basis, scaled by numbers of users.
Further custom development would be required for:
- Ability to jump into SAC Planning for maintaining project financials
- Integration with OpenText workspace
- Follow-on actions for Stage Gate Approval
It has been confirmed in discussions with the vendor that the above customization is feasible.
Refer to the linked pack for details of the sophisTex solution:
Option C: Screen Personas
Screen Personas is developed with following features
- Simplified Screen for Item creation/CHanges
- Ability to Save as draft or copy from another item
- Ability to jump into SAC Planning for maintaining project financials
- Integration with OpenText workspace
- Integration with SAP Consulting Solution for Stage Gate Approvals (cost included in estimate above)
- Follow-on actions for Stage Gate Approval
Option D: Standard Webdynpro
Standard web-dynpro following features
- Custom Fields and Validations
- Integration with OpenText workspace
- Integration with SAP Consulting Solution for Stage Gate Approvals (cost included in estimate above)
- Follow-on actions for Stage Gate Approval
Evaluation
Both options are essentially custom solutions. The most significant difference is in implementation & ongoing cost, which out-weighed the other criteria in making the recommendation.
| Evaluation Criteria | Option A - In-house Development (recommended) | Option B - sophisTex Partner Solution | Option C - Screen Personas | Option D - Standard Webdynpro |
|---|---|---|---|---|
| Fit to Standard |
|
|
|
|
| Implementation Cost |  Medium implementation cost, minimal ongoing cost |
| Medium implementation cost, minimal ongoing cost | Medium implementation cost, minimal ongoing cost |
| Implementation Effort |
|
|
|
|
| Design & UI Flexibility | Full flexibility to incorporate business requirements |
|  Limited option to customize as we need to work within framework | No option to customize |
| Business Acceptance | Meets all business expectations/requirements |
| Meets most business expectations/requirements | Does not meet business expectations/requirements |