You are on page 1of 18

1

SAP SAC
Implementation
kick-off meeting
25.10.2023
3

Agenda
● 1. Welcome and Introduction
● 2. Project & SAC Overview, Scope & Objectives
● 3. Timeline
● 4. Project Roles & responsibilities
● 5. Project plan & methods
● 6. Summary, Next Steps & Action items
4

1. Welcome and Introduction


● Objectives of the kick-off meeting
○ 1) Walk-through of project (ref. project triangle: time, quality/scope, costs/resources) scope, roles & resp,
timeline
○ 2) Summary of next actions
● Project Participants - Roles
○ Neste side resourcing
○ SAP (@sap.com):
■ Project management: Johanna Mellin johanna.mellin@partners.neste.com
■ SAC consultant: Minas, Diego diego.minas@partners.neste.com
■ Project and cost planning: Patnala, Sreenivas Sreenivas.Patnala@partners.neste.com
■ Integration architect: Imperial, Adwin adwin.imperial@partners.neste.com
■ Integration: Dias, Luis luis.dias@partners.neste.com
● Summary of project - purpose & outlines
○ Project Purpose (MVP explanation) / Matti
○ Excluding: RP, PPM wave 2 for the first GoLive (MVP) -> Backlog
○ SAP MVP approach / Johanna
5

2. Project & SAC Overview, Scope & Objectives 1/2


● Project's 1) vision, 2) goals, and 3) expected outcomes. / Matti
○ 1) Future vision (notifying MVP & exclusions) (could be) to support versatile “custom” planning & reporting
solution with SAP data. => Dev. backlog for later development needs
○ 2) Goals: Excel WA replacement, User stories for business (notifying MVP)
○ 3) Expected outcome is to have fully functioning SAC solution for PS cost planning that seamlessly integrates with
S/4
● Significance of the project for the Neste organization. / Matti
○ Workaround-excel replacement - urgent need to get rid of excel
○ End-User-friendly solution for PM’s & other project + portfolio management daily use
○ Enablement of further development for PPM (wave 2-3) and RP (further development)
● High-level overview of the SAP Analytics Cloud as system & use in project. / Johanna
○ Overview of SAP Analytics Cloud features and capabilities relevant to the project.
○ Highlights of how SAC will address the project's requirements.
6

What is SAP Analytics Cloud (SAC)


SAP Analytics Cloud is a software as a service (SaaS) enterprise analytics solution that combines Business Intelligence, Augmented and Predictive Analytics, and
Planning capabilities to help you understand your data to make smarter business decisions. With SAC for Planning, you can bring in siloed plans from across
the enterprise to maintain the integrity of each function yet have an end-to-end view to confidently drive decisions. Furthermore, you can ask, analyze,
predict, plan, and report all in one end-to-end workflow. SAP Analytics Cloud offers built-in self-service
Business Intelligence (BI) features to help you
explore, analyze, and visualize data to get
actionable insights for decision making. These
features include reports, dashboards, data
exploration, data preparation, and data
visualizations such as charts, tables, Geo maps,
and other visual formats to display data in a
way that can be quickly and easily understood.

SAP Analytics Cloud Augmented Analytics can


help users make more confident decisions
faster with automated insights powered by
machine learning and artificial intelligence.
Spend less time analyzing data manually by
leveraging these capabilities to automatically
reveal top contributors, influencers, hidden
patterns, and outliers in your data - no data
science knowledge needed

SAP Analytics Cloud for Planning lets you


analyze, predict, and plan in one application. It
enables real-time Extended Planning and
Analysis, to link and align all plans and people
across your organization. It breaks down silos
and brings teams together to collaborate on
plans and drive better business outcomes.
7

SAC Import Connection + Plan Data Write back


8

2. Project & SAC Overview, Scope & Objectives 2/2


● Scope of the project - what will be covered and what will be excluded. / Matti + Johanna (SAP perspective of MVP)
○ Primarily: Workaround-excel replacement - 1st prio, limited based on MVP description in Alvar -> cost planning
■ Env. setup, SAC-connector, user accesses
■ User Stories enablement/setup in SAC - limitations set…
■ (Planning & reporting data “extraction” needed only for User Stories)
● Specific objectives and deliverables expected from the project (*. / (Matti) Johanna (SAP MVP)
○ SAC for WA, User Stories - Enablement to use SAC connected to S4-PreProd, planning data to ACDOCP
■ KU Docs + KU-Training/SAP -> End User Training + (OCM) Business transformation
● (* Neste responsibilities covers the GoLIve, not just SAP
○ Enablement for further development /BAU-Alvar (docs, capabilities)e
9

3. Timeline
● Timeline, including key milestones and deadlines. / Matti + Johanna
○ SAP timeline vs. release calendar
○ Target to be live before/sync PPM wave 2 (02-03/2024) - 12/2023 something? (*
■ (* Quality, forecasting, continuous improvement)
● Critical dates or dependencies. / Matti
○ release calendar -> MEC
○ PPM Wave 2
○ RP
10

High-level Timeline Organizing and


preparations
Contract with SAP

Contract negotiations and


UAT

User acceptance testing and


Putting together the project signing approval of the solution
team and timeline
High-level requirements
submitted to SAP
SME
Defining use cases

2021 2022 2023 June August Oct - Dec 2024 Q1

SAP selected as partner

Initial requirements and


solution comparisons Internal Kick off 21.8. Go-live
and workshops Design and Build

SAC Proof of Concept Design and build the


Collecting the user stories and
functional requirements solution in SAC
SAC demo for Neste
Solution demos
SME
11

4. Project Roles & Responsibilities

● Roles and responsibilities of project team members / Matti + Johanna


○ SAP SAP Team Members
○ Neste - PO-roles, Service, SAC Key User, Alvar Key Users
■ High emphasis of KU roles (ref. GoLive activities + trainings) (!!)
● Key stakeholders and their involvement in the project. / Matti
○ Core team ++ Piet Vedder & SG stakeholders -> Stream responsibility in ownership (!!)
● Reporting structure and escalation paths. / Matti
○ Core team, Johanna & Khurram, defects (UAT), Alvar PMO
12

Project plan & Place and crop your


image here
methods
13

5. Project plan & methods


● Project plan and methodology. / (Matti) + Johanna
○ Mandatory presentations: SAP Project plan, User Stories, Project scope, Living project planning doc.,
○ Emphasis on real-time applications in monitoring (Monday board for PM, Development board (for practicalities),
■ Note! Phone (Matti: +358-400-552902) is still available…
○ Neste Mandatory elements: PDD; CDD, FSD, UAT, KTT (Naming convention)
○ HP ALM (UAT), Hands-on Chat/space
○ ARIS updates (++Celonis -> Process monitoring)
● Phases of the project / Matti (deployment phases) + Johanna (SAP practices)
○ Requirements gathering, design, implementation, testing, and deployment
● Approach to be followed (Agile, Waterfall).
○ Alvar monthly release cycle, otherwise target to agile development where possible (Monday board)
● Deployments, connection to other Alvar Deployments & Hypercare
○ Environments & Testing (only one env. for DEV/TEST -> Agile approach needed)
■ SAC Modeler (restricted access) -> HP ALM (UAT)
■ Flexibility vs. Alvar criteria
■ “independent” from PPM wave 2 & RP
○ Cutover planning respecting Monthly release cycle incl. MEC freeze
○ Hypercare & AMS still open
Test Management / Jenni
Testing approach
● Test phase:
○ UAT (smoke tests can be done before UAT)
● Test (& development) Environment setup in Alvar:
○ Test environment QS4 (refresh at the end of November)
● Scenario planning to be started when Process definition document and SAC MVP scope available
● Objective is to verify SAC MVP solution with Neste business users:
○ Selected test cases
○ Relevant reports
● Entry criteria as per Alvar Test Strategy (link?)
● Exit criteria as per Alvar Test Strategy
SAC Testing Schedule (to be updated)
2023 2024

Oct Nov Dec January

43 44 45 46 47 48 49 50 51 52 1 2 3

Test preparations

Smoke
UAT SAC
testing

SAC kick off Production Go-


UAT Kickoff live 20.1.2024

CHRISTM
AS BREAK
Testing
Build close

ALM trainings

QS4 refresh
16

6. Summary, Next Steps & Action items


● Monday - Listed actions: responsibles & deadlines (ref. user stories)
● Expected next steps & upcoming meetings:
○ Weekly “Core-meetings”
○ Workshops by SAP -team (User stories mapping -> development)
ALVAR - Entry and exit criteria for phases and steps (Appendix 1.7) 17

Implementation Phase Description Entry criteria Exit criteria


Phase 1: Project Project planning and Signed contracts between Supplier Assigned project team, approved detailed work plan and approved OCM plan.
Preparation organisational readiness and Neste on EAM Implementation
establishment. (incl. project plan)

Phase 2: Detailed Design Detailed design, incl. solution Approved high-level Solution Acceptance of Deliverables and detailed design documentation incl. Solution Blueprint, Solution
blueprinting, L3-L4 processes, description documentation and requirements for L3-L4 processes, detailed architectures, data analysis, data cleansing approach and
solution functionalities and Solution & project implementation plan, and verified Solution implementation plan.
architecture. plans, including Deliverables’
definitions and their Acceptance
Criteria.

Phase 3: Realize (Build and Development of deployable Phase 2 related exit criteria fulfilled. - All major functionalities and requirements have been implemented and tested.
Test) global solution template, Note:If mutually agreed, phase can - All necessary interfaces and integrations have been built and tested
testing and pilot be initiated before all Phase 2 exit - At least 95 percent of the applicable test cases & business scenarios are completed.
implementation to production criteria has been fulfilled. - No critical issues remaining.
- Resolution(s) for major defects are defined.
environment, GoLive to Neste - All plans for Roll-out Phases 4- 5 such as integrated testing, rollout (go-live)/cutover, and
Pilot Site and Hypercare for 10 resourcing plan approved
weeks after GoLive

Phase 4-5: Pilot, Deploy Solution implementation, roll- Phase 3 exit criteria fulfilled. All Deliverables approved incl.
incl. Hypercare out incl. GoLive to Neste sites Note:If mutually agreed, phase can -Pilot implementation successfully executed.
and operations globally be initiated before all Phase 2 exit -Handover activities completed to maintenance and support (pilot implementation)
criteria has been fulfilled.. -Hypercare activities completed (pilot)
-No critical issues remaining (pilot)
-Deployment of the application in the production environment with needed localisations, all
cutover and handover activities conducted
-User training, application maintenance training, system administrator training
-Transition of functionalities and activation of the application at the site according to the
Cutover Plan
-Migration and verification of data needed in live application completed
-Handover activities completed to maintenance and support
-Hypercare activities completed
-No critical issues remaining
-Final handover to maintenance and support conducted
-All project deliverables approved

Appendix 1.7
18
26

You might also like