ASUG SAP Adoption Influence Council The focus is on how to increase awareness, adoption and implementation of SAP enhancements that are delivered as part.

Slides:



Advertisements
Similar presentations
1 © 2010 DataCore Software Corp. — All rights reserved © 2010 DataCore Software Corp DataCore Software DataCore Software Certified Implementation Engineer.
Advertisements

© 2013 Calypso Confidential Introduction to Calypso Product Support 1 © 2010 Calypso Confidential.
ASUG’s Roadmap to Influence QM Session. What Influence used to be... Submit written development requests to ASUG ASUG spent considerable resources organizing.
3108: Enterprise Upgrade Lessons Learned
Software life cycle processes Purpose n A new international standard (ISO/IEC 12207:1995(E) that –establishes a common framework for software life cycle.
Managing Change in Production BW at General Mills Mike Ruesewald Cindy Burlet Chris Gunn.
SE 555 Software Requirements & Specification Requirements Management.
Software Project Transition Planning
1 The Maintenance Process Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
Software Configuration Management (SCM)
Best Practices – Overview
Developed by Reneta Barneva, SUNY Fredonia The Process.
Maintaining Information Systems Class 27. SDLC Project Identification & Selection Project Initiation & Planning Analysis Logical Design Physical Design.
Chapter 16 Maintaining Information Systems
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 18 Maintaining.
1 Browser Compatibility Assessment TAC Presentation May 28, 2015 David Forfia Director, Enterprise Architecture.
Salesforce Change Management Best Practices
OHT 19.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Controlled documents and quality records Definitions and objectives.
B O N N E V I L L E P O W E R A D M I N I S T R A T I O N 1 Network Operating Committee (NOC) June 12 th, 2014.
“Here’s why you need the new wheels, too…” Shawn and Steve Image from
Information Systems Security Computer System Life Cycle Security.
System Analysis and Design
Module CC3002 Post Implementation Issues Lecture for Week 6 AY 2013 Spring.
MyFloridaMarketPlace MyFloridaMarketPlace User Meeting October 26, 2005.
Software Configuration Management
Produced by: Integrated Asset Planning for Nuclear Power Plants Matt Kohal Southern California Edison.
MyFloridaMarketPlace MyFloridaMarketPlace User Meeting September 6, 2006.
© Copyright 2011, Alembic Foundation. All Rights Reserved. Aurion: Health Information Exchange Technology Today Alembic Foundation OSCON 2011 July 27,
How Can NRCS Clients Use the Conservation Client Gateway
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
16 1 Installation  After development and testing, system must be put into operation  Important planning considerations Costs of operating both systems.
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 1 Chapter 16 Maintaining Information Systems.
Software Quality Assurance
Approvals Management with TCA Hierarchy Ajoy A. Devadawson Oracle Corporation - Consulting.
3 rd Party Registration & Account Management SMT Update To AMWG January 20, 2015.
Release Management Configuration management. Release Management Goal Coordinate the processes through the project development life cycle Ensure the.
SOFTWARE MAINTENANCE 1. TOPICS TO BE DISCUSSED.. Definition of Maintenance Software Maintenance Types of Maintenance Maintenance Process Need of Maintenance.
] COREY PEARSON [ ASUG INSTALLATION MEMBER MEMBER SINCE: 2008 CHAVONE JACOBS [ ASUG INSTALLATION MEMBER MEMBER SINCE: 2003 ALLAN FISHER [ ASUG INSTALLATION.
GREG CAPPS [ ASUG INSTALLATION MEMBER MEMBER SINCE:1998 ISRAEL OLIVKOVICH [ SAP EMPLOYEE MEMBER SINCE: 2004 GRETCHEN LINDQUIST [ ASUG INSTALLATION MEMBER.
Enhancement Package Innovations Gabe Rodriguez - Halliburton Stefan Kneis – SAP Marco Valencia - SAP.
After Action Review and Recommendations. Feedback Issues & Recommendations –Communication and Training –Content and Navigation –508 Compatibility –eAuthentication.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
1 Grants.gov Update to the NGP February 1, Grants.gov System Improvements  December 11 – 12, 2010: Oracle Database version 11g upgrade  January.
IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
Developed by Reneta Barneva, SUNY Fredonia The Process.
3 rd Party Registration & Account Management JDOA Update To RMS October 28, 2014.
1 Program Release 2008 Update to the Administrative Council August 9, 2007.
1 Browser Compatibility Assessment June 2 nd, 2015.
State of Georgia Release Management Training
1 Software Maintenance and Evolution CSSE 575: Session 4, Part 2 Software Maintenance Process Steve Chenoweth Office Phone: (812) Cell: (937)
ASUG SAP Adoption Influence Council Overview: The focus will be on how to increase awareness, adoption and implementation of SAP enhancements that are.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix B: Getting Started in Systems Analysis and Design.
1 Texas Data Transport & MarkeTrak Systems (TDTMS) Update to RMS March 1, 2016 Jim Lee (AEP) – Chair Monica Jones (NRG) – Vice Chair.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Insight Post-Release Delivery Chu Shu July 2012.
Chapter 16 Maintaining Information Systems. Objectives:  Explain and contrast four types of system maintenance.  Describe factors affecting maintenance.
ICS Area Managers Training 2010 ITIL V3 Overview April 1, 2010.
The WCO SAFE Framework of Standards Larry Burton Senior Technical Officer World Customs Organization.
Founded by Big Five Consulting ex-employees Oracle Gold Partner Focus on PeopleSoft 15 years of PeopleSoft experience Worked in both technical and functional.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
3 rd Party Registration & Account Management SMT Update To AMWG September 23, 2014.
Chapter 25 – Configuration Management 1Chapter 25 Configuration management.
Planning the Digital Transformation Readiness Check for SAP S/4HANA
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Sample Fit-Gap Kick-off
Supporting quality devices
Documentation control
Systems Development Life Cycle
DSG Governance Group Recommendations.
Presentation transcript:

ASUG SAP Adoption Influence Council The focus is on how to increase awareness, adoption and implementation of SAP enhancements that are delivered as part of enhancement packs and support packs. Software that customers have already paid for and is delivered as part of their maintenance agreement.

1.Awareness and communication of enhancement packs 2.Create disposable system for discovery – switch framework, validate impact and functionality 3.Communication to partners – third party software availability of compatible software 4.Planning for installation – estimates a.Resource requirements for installation, configuration, remediation, testing b.Potential impact on existing projects c.Impact on operations 5.Define business case and get approvals 6.Installation of enhancement pack 7.Remediation of customizations and modifications (SPAU, SPDD and SPAU_ENH) – request feedback 8.Testing 9.Create reference system for use during system outage by end users and post go-live support investigations 10.Implementation Evaluation and Implementation Process Defined

Requirements defined to date (January 2015) Customers require improved access to enhancement pack technical documentation prior to implementation in a sandbox – Provide source and target version and receive: All components are in the stack and the highest SP available Notes included Side effect notes with link to causing note Details in attached document – Additional documentation to be generated New security objects and new values on existing security objects New transaction codes Update all OSS notes to be compatible with planned release, eliminate the need for us to notify SAP and request for them to be updated