The SAP Activate methodology is utilized for implementing or migrating SAP in cloud, on premise, or hybrid solutions. SAP Activate methodology aligns with best practices recommended by the Project Management Institute (PMI).
The SAP Activate methodology follows four main phases to provide support throughout the project life cycle of SAP solutions. Underlying these phases is a series of value delivery and quality checks, reflected in the approach as quality gate checkpoints, to make sure that the solution delivers expected benefits.
- Prepare. Confirm value drivers, goals and success metrics. Finalize scope, schedule and assign the project team. Create DEV/TEST landscape, project governance, standards, kick off and perform quality gate.
- Explore. Validate scope, business requirements, perform fit/gap analysis and functional design workshops, perform quality gate.
- Realize. Configuration, incremental tests in an integrated environment. Solution walk through, set up DEV/TEST integration. Develop solution extensions and perform quality gate. User acceptance testing, Plan cut-over, initiate and set up PROD integration.
- Deploy. Load and test data, conduct the cut-over activities and switch business operations to the new system. Go-Live, handover to support/ operations, project close, post –go live support. Perform quality gate.
Key Implementation Notes;
- On-board suppliers not yet on the Ariba network. At a minimum they should receive a PO.
- Use Flight Planning (planning, architecting and deployment) to enable suppliers and categories of spend. This is done throughout the project life-cycle.
- Maintain the Catalog. Suppliers log into the network and update catalogs, host punch-out catalogs (find products and services through the internet when creating a requisition). Supplier data can also be sent and uploaded to a customer maintained catalogue.
- On-demand solutions can be “activated” or “enabled.” The process can be relatively simple, and can be performed remotely if required.
- Activation team members can work from remote sites, in countries outside yours.
- Organizational processes can be complex. Manufacturing can be offshore, sold and serviced onshore then fixed or returned offshore if required. Think these requirements through carefully and don’t offshore exploring requirements. Make it easy and as simple as possible.
- Understand the interfaces of your on-demand solution. Interface objects that require functional and technical specs may become the longest lead-time item on your project plan. Writing good detailed technical specifications is extremely critical for any IT project.
- Legacy data gathering and cleansing needs to be defined. Objects such as contracts, vendors, customers, product hierarchy, units of measure, and user security also require excellent specifications including conversion rules.
- Security governance needs to be in place and carefully implemented.
- SLA’s (Service level agreements) support keys areas for post- go live.
Leveraging the more than two-million suppliers on the SAP Ariba web–based network, along with multiple SAP Ariba solutions optimizes spend analysis, sourcing, contracts, supplier performance, quality, delivery and prices. This provides a comprehensive Digital Transformation solution for users, suppliers, and customers while using the simplicity of web based procurement.
As well as being a Managing Consultant Terry Vermeylen is the founder of Mylifechanges.com and Worldclasssupplychain.com and President of Terry Vermeylen Enterprises Inc.
Ref: SAP Ariba and SAP Fieldglass – Functionality and Implementation