NNPC SAP Reloaded Program - Onboarding For PMs - v1.0
NNPC SAP Reloaded Program - Onboarding For PMs - v1.0
“SAP RELOADED”
Bernard Ezeh
Adeoye Oshowole/Adebola Afolabi
April 16, 2018
Welcome Address – Overview and Background of Program NNPC Program Manager 11:15 – 11:40
SAP Redelivery Program Kick off Presentation SAP Program Manager / NNPC Program Manager 12:00 – 13:30
Directorates / SBUs CHQ / PPMC PPMC NAPIMS/ IDSL Refineries NETCO NGC NPDC Retail Duke Oil
Core Business Processes COMD HQ DEPOTS NIPEX
Capital Planning & Portfolio
Management X X X X X X X
(Project Systems)
Maintenance Management
(Plant Maintenance) X X X X
Non-hydrocarbon logistics
(Materials Management) X X X X X X X X X X
Corporate Finance
(FI/CO) X X X X X X X X X X
IT Operational Excellence
(CATS) X
1. A Project Team (with all the team members) is setup timely for the big ticket Program items
2. Existing SMEs are well trained for the areas they cover. New SMEs identified as Project Team members are also
adequately trained before commencement of the project implementation.
3. Experienced Consultants are deployed to work on the projects with NNPC SMEs by SAP,
5. Need to ensure all infrastructure requirements are met before the date they are required.
6. Engagement across the corporation to share the plan with all stakeholders, and expectations around their roles in order
to make a success of the plan.
7. Management’s support to ensure full participation by business leaders /process owners and no surprises.
Processes
Management
Project
Organization
Team Technology
Steering Committee
SPSC
NNPC SMEs NNPC SMEs NNPC SMEs NNPC SMEs NNPC SMEs NNPC SMEs NNPC SMEs
SAP PM + CONs SAP PM + CONs SAP PM + CONs SAP PM + CONs SAP PM + CON SAP PM + CONs SAP PM + CONs
Technology
NNPC PM
SAP PM + CONs
© 2018 SAP SE or an SAP affiliate company. All rights reserved. Internal 8
Responsibilities of the NNPC / SAP Program Manager
The NNPC program manager is responsible for the overall project and particularly attends to the following tasks:
Technical and commercial program management
Coordination of interfaces
Risk Management
Organization of program meetings
Controlling of the overall program
Controlling of program progress and results (including reporting)
Contact and reporting to the NNPC SPSC
Primary Interface with the QA team
Primary interface with the SAP COE
…
SMEs and Consultants are key contact for the NNPC/SAP Project Managers:
Definition of the project‘s scope taking into account the goals of the overall project
Answerable coordination of the sub project
Coordination of requirements on business processes
They provide the project with indispensable technical input.
They design a system that’s fit for purpose for NNPC – a system that all employees can identify with
If necessary, they refer to other experts for detailed information or study the subject beforehand.
…
Quality Assurance
The SC is responsible for project control and project coordination as well as the efficient bringing about of technical and
organizational decisions. The responsibilities are:
Accountable for overall success of project.
Address major program risks and issues.
Approve all Scope Changes before proceeding to execution.
Accountable for ensuring that the SAP Programme aligns with the corporation’s current business priorities.
Forum for escalations of all SAP Programme issues, Stage Gate approvals (project prep, blueprinting, realization, final
preparation and go-live & support), and other Programme decisions.
Approval party for all strategic decision on approach for every major SAP activity such as overall test approach, cutover
approach, acceptance Criteria, agreement to Deploy, and agreement to Operate.
Resolve conflicts between project and business.
Act as SAP “ambassadors” in the corporation, helping to embed SAP in the business. Sets the tone for SAP agenda in the
corporation for all staff to align.
The Group Process Council is a forum of NNPC Group Process Owners and selected Business Process Experts, particularly
focusing on processes that are already (or planned to be) on SAP platform. Their responsibilities are:
Accountable for final process design and Sign-off of the final SAP blueprint.
Interface with process owners to ensure they understand and are aligned with the processes as designed.
Accountable for successful implementation of the common processes across the enterprise.
Accountable for realizing business process benefits and improving the business processes.
Provide direction and information to the Process Design Team. Help the Process Design Team to understand the business
process.
Implement policies, standards and procedures required for new business processes.
Plays key role in ensuring that SAPCOE Staff Rotation Plan for rotating business staff into and out of SAPCOE works.
Review deliverables, change requests, and decision requests to confirm assumptions.
Ensure business requirements are met, and identify issues thereon (if any).
Review Progress Status of SAP Programme Delivery against Plan, with the view to help resolve all issues (within their
sphere of influence) blocking progress as expected.
Strategic
Adoption of a tested deployment methodology
Technology
Consider Data a threat to project success & manage as such
Tactical
Take a process view of solution validation and testing activities TTV – Time to value
Integrate Stream
Project Plan Review with PMO
Project Plan into
Template adoption against HLP
Detailed Program Plan
PMO
Coordinated
Review and
Update Aligned with Aligned
Billing with ASAP
Milestones milestones
Workshop Protocol SPM SAP Key User after each meeting Result Protocol
Legend: SPM: Sub-project management, PM: Project management, SC: Steering committee
Communication facilitates change by ensuring that timely information about the benefits and changes of the program
is passed on to both internal and external stakeholders. Below is the high level communication approach:
1 2 3
Determine the
Identify internal communication need Identify key
and external of stakeholders messages for
stakeholder groups stakeholders
6 4
Monitor and 5
Develop
evaluate Execute
communication
effectiveness of communication
plan
communication activities
E-Mail Calendar
Electronic exchange of information Project members manage their
and documents: appointments/absence via the
Within the SAP project, the exchange calendar feature:
of information and documents Each project member records their
generally takes place without paper. personal appointments in the electronic
Exceptions consist of approved calendar.
concepts, data transfers, etc that must The same goes for absence, e.g.
be signed by the respective person in vacation.
charge. Using the calendar for planning
Attachments generally have to be sent meetings facilitates effective
as shortcuts/links. scheduling and sending of invitations.
Governance Structures
Delays arising from Bureaucracy
Improving
Misinterpretation of project Impact of other major Delayed stakeholder approval
methodology activities Lack of external connectivity and Stable
Data migration tools not Unavailability of office band-with
fit for purpose space Poor contingency planning Declining
Inadequate Post Availability of end users for
implementation support training Risk Acceptability Level
Blue print design not fit Delays in implementation of
for purpose contracting strategy Response acceptable
$2.5m Instability after cut – over Inadequate timeframe for data
Poor employee retention management Response needs
improvement
Inadequate programme Process Silos Response significantly
scheduling Poor knowledge transfer deficient
Inadequate presence of first line
support.
Availability of Experienced
Inadequate Staff Resources Absence of QA / QC Consultants Absence of Requisite skills Dela
Consultants
Low manning in critical project Consultants not having the No QA / QC Contract in place Project team members not De
teams relevant experience and know- at commencement having relevant experience and and
Mitigation: Restructuring of how Mitigation: Acceleration of know-how Mit
CoE and staff deployment Mitigation: Interview of critical contracting process Mitigation: Selection of team FAD
Owner – GGM ITD / SAP CoE resources, Contract termination Owner – SAP CoE Mgr based on skill, training of team for t
Mgr clauses members Ow
Owner – SAP CoE Mgr, Owner – GGM ITD / SAP CoE Mgr
Engagement Mgr SAP / KABO Mgr / GGM HR
Timely availability of IT
Unavailability of Office Space B
Infrastructure Availability of Office Space Resistance to Change
IT infrastructure not in place at Unavailability of Office Space for Inadequate sitting space for SAP Remaining with the status quo Non
project commencement teams, consultants sitting apart from COE and consultants after automation of processes, with b
Mitigation: IT infrastructure NNPC SMEs Mitigation: Initiate Request and running parallel processes organ
checklist and periodic review Mitigation: Engagement of GM Engage GM GAS for Office space Mitigation: Stakeholder Miti
Owner – GM Core Inf / SAP CoE GAS and GGM ITD on office and furniture. Initiate Request and engagement plan, Process council comp
Mgr requirements Engage GM ITD Core Infrastructure engagements sessi
Owner – GGM ITD / SAP CoE for laptops and phones. Owner - SAP CoE Mgr Ow
Mgr Owner – GGM ITD / SAP CoE
Mgr
Naming conventions
All project documentation has to follow the naming conventions and must be saved in the specified directory
folders.
Templates
Providing for the project documentation uniformity, the given templates have to be used.
During the Business Blueprint phase the project scope is defined within the agreed statement of work with SAP.
That means that all relevant processes and functions are listed in a document. In case there are modifications
during the project, for instance regarding the business model, they can be handled with so-called Change
Requests.
Change Requests can be used in exceptional cases to modify the project scope.
Change Requests will automatically generate additional costs and increase the overall project risk as they, for instance, may
challenge the project schedule.
Change Requests are subject to a dedicated authorization procedure.
1 Requirement is on hand
A project manual will be compiled and is binding for the entire team. Manual contents:
Project assignment
Description of project phases
Project contents
Communication structure and reporting
Project controlling
Provision of material
Management (Change Request Process, Quality Assurance)
Documentation guidelines and naming conventions
Activities
Set-up of productive system
Master and transaction data import
End user training
Customizing of forms and reporting
Customizing of end user
documentation
Week in April
April, 2018
SUN MON TUES WED THU FRI SAT
15 16 17 18 19 20 21
Project Orientation, Conduct Scope
Onboarding and Validation Session
Introductions etc – PTP & OCM???
Stream Kickoff & Next
Step Planning
Project/Workstream Plans
22 23 24 25 26 27 28
Project/Workstream Plans
9 Stakeholder Identification & Contact List (Project & Business) - Baseline version All
PMO
Microsoft Excel
Coordinated Worksheet
Review and
Update Aligned with Aligned
Billing with ASAP
Milestones milestones
Thank You
...
...
Weekly Jour-Fixe
...
...
Functional Goals
Project Goals
Business Goals
Achieving the requested modifications
or improvements in the business Schedule Compliance
Quality Spec Compliance
Budget Compliance
Mobility
Mobility
Mobility
Mobility
Portal
SAP ECC SAP ECC SAP ECC IS OIL SAP ECC SAP ECC
FI/CO SD PEF
FI/CO PS JVA, PSC
SD FI/CO PM
HR AM MM PM
SD MM GRC - PC
OGSD MM SD
PM PP CATS
OGSD
Integration Security & Controls Integration Security & Controls Integration Security & Controls Integration Security & Controls
Contact information: