SAP Project Realingnment (Recovery)

1. Logosworld.com Enterprise Architects SAP Project Realingnment (Recovery) • Practicing the art of bringing a project back on track

2. SAP Runs Better with Logosworld • We optimize SAP ERP whenever it does not deliver the results that you expected

3. Project and Implementation Audits • Get a Second opinion on your system • Get advice and advice from expert brains • Get access to the best SAP and cloud experts of the world • Best Practice Audits • 1-2 week assessment to understand the situation and compare with actual common practice and top performers • Technology analysis of implementation state • Get a detailed analysis about the technical state and completeness of your system • Benchmark system and project performance • Measure machine performance to allow selective improvements and sizing • Optimize project management and governance • Optimize project management in accordance to international practices and standards • Deliver complementary and shared service • Find an optimal balance for in-house versus out-sourced and shared services

4. Recover Misaligned Projects • Audit - Assessment of misalignment projects • Audit of current state of implementation • Identify and communicate key issues • Recover – Immediate recovery action • Take over project control • Implement immediate fire-fighting • Stabilize - Realignment Actions • Negotiate steps to reduce complexity • Select core implementation team • Improve – Establish improvement procedure • Quality control of implementation • Keep system aligned with business requirements

5. Logosworld Recovery Plan • Make system work properly and efficiently • Correct technical mistakes • Improve system performance • Define maintenance & support needs • Simplify maintenance and support • Remove unnecessary complexity and redundancy • Introduce best and common practice • Help outsourcing non-key tasks • Management support • Build a proper education plan • Define costing matrix for enhancements • Select third party add-ons and consultancies

6. Logosworld Recovery Services

7. Project Benchmark Audit • Audit system landscape situation • Analysis project environment • Compare against best practice • Suggest immediate improvements • Estimate possible ROI and TCO • Present a mid and long term strategy • Suggest in-source/out-source tasks

8. Top-Level Project Control • Middleman between client and implementer according international standard practices for SAP • Top-level project lead for offshore projects • Quality assurance for projects • Monitoring project activities • Many customers prefer a mix of offshore and top-level Western consultancy. It is helpful to bring in mature experienced top-level consultants as project leaders into the project while execution is handled by qualified offshore teams.

9. SAP Best Practice Education • Elite SAP Training for offshore teams • Best practice (ISO20000/ITIL based) • Negotiate and document requirements • Solve contention and disagreements • Verify and guarantee continuous quality • Proper sign-off procedures for work done • Training focusses in teaching offshore teams the best practices and standard operation procedures for working in international projects according ISO20000. It teaches how to solve conflicts in offshore projects • Advanced ABAP training for offshore • Programming in an offshore model can only be successful if all teams follow stringent common standards and practices. This training focusses on bringing all developers to a homogeneous quality level.

10. Day to Day Improvements • Define Standard Operation Procedures • Identify unique ownership for every task • Enforce and document user stories • Agree life-cycle requirements • ROI evaluation/estimate rating system • Identify post-go-live needs and steps • Set up support hand-over procedures • Optimize documentation requirements

11. Project Recovery in Detail

12. Audit, recover, stabilize, improve? • Logosworld uses systematic methodology to implement SAP and cloud solutions • Due to intensive industry experience we fill the extremely challenging niche of recovering stopped or failing projects • Based on a proper best practice audit Logosworld suggests and practically assists recovery actions to stabilize the system use • Once the system runs stable we suggest step-by-step improvements to increase ROI

13. Types of recovery projects • Action depends on nature of failure • Technical malfunctions • Incomplete implementation • Disagreement between client and implementation partner • Compliance violation • External communication insufficient • Missing features • Lack of education

14. Key Recovery Activities • Review and audit the state of a project • Give Independent opinion on system • Suggest improvements or recovery • Help selecting implementation partners • Project management during recovery

15. Recovery Steps • Emergency Diagnosis • Redefine the «to-be» requirements from business value perspective • Review implementation and detect deviations • Define immediate emergency actions • Realignment Actions • Define quick win solutions • Define redesign actions • Define third-party procurement • Common education of teams and users

16. Recovery Cases

17. Some recovery case stories • Incomplete or unstable implementations • Many projects are incomplete because they run out budget or because there is disagreement about the payable deliveries. Here we intervene with assessing the requirement versus delivered items and negotiate an appropriate way to bring the project on track. • Complexity overkill • There is an increasing number of projects that suffer from complexity that is not appropriately addressed by the project layout. It is our duty to suggest where we can reduce complexity and when complexity is required by the nature of the use case to define measures to properly cope with the circumstances. • Hostile project ambiance • There are projects where the project partners find themselves in permanent feud and cannot find agreements on how to proceed. Here we step in as project arbiters and set up an organization that is designed to take out emotions in favour of working on facts.

18. Technical Malfunctions • Programs do provide false results • Programs crash or abort unexpectedly • Programs run too long («time-outs») • Data cannot be entered correctly • Data cannot be extracted correctly • Data loss or data leeks • Machine to Machine Communication fails

19. Incomplete implementation • Review of requirements • Identify gaps • Define priority of gap implementation • Remove unnecessary requirements • Set canonical implementation standard • Supervise implementation

20. Various Misbehaviour • Data entered redundantly • Repetitive steps that can be automated • Lack of end user training • Non existent or bureaucratic support • Processes do not model daily business • Notorious disagreement • Dispute and disagreement between client and implementation partner

21. Logosworld says “Thank You.”