Crafty Systems can help your sourcing group plan and deploy your SAP® Sourcing / CLM system. Our 7-step delivery methodology can be adapted to meet your organization’s needs and provide an on-time, on-budget implementation. We offer several types of projects, depending upon your timeframe and budget:
Rapid Deployment: Need to get your
SAP Sourcing system up and running as soon as possible? Do you want to run events quickly and validate your ROI, while planning for a more-formal implementation? The Crafty Systems Rapid Deployment could be right for you. By focusing on the tactical needs at hand while preparing for the requirements of the formal implementation, you can start running events and realize savings immediately, helping to build your internal business case and credibility while properly planning for the related enterprise software implementation project.
Phased Implementation: A more common approach to SAP Sourcing enterprise software deployment is the phased implementation, in which you deploy a core set of functionality first, and build upon the core in subsequent phases of the project. For example, Crafty Systems’ customers may elect to deploy the Contract Lifecycle Management first, and then focus on Projects, RFxs and Auctions in subsequent phases. The goal is to carve the overall project into manageable chunks while planning for the later phases.
Delivery Methodology: Regardless of the project size and scope, Crafty Systems uses its iterative 7-step methodology to help achieve success of the project:
Step 1: Planning – During this initial step of the project, your ultimate goals and constraints are explored. Based on current knowledge, the scope of each phase is identified, and a bottom-up timeline of activities is developed using the initial assumptions for guidance.
Step 2: Analysis – This step includes defining a more detailed prioritized requirements list, formal project plans, and a set of delivery constraints that will be used to measure progress during subsequent phases of the project. Estimates may be revised based on the new understanding of the detailed requirements.
Step 3: Iterative Configuration – Although there are a few different types of design and development methodologies that we can use, this step contains the actual configuration steps in accordance with the prioritized list. Typically broken into business and technical configuration lists, Together we will focus on the Must Haves and underlying master data first, followed by Nice To Haves.
Step 4: Iterative Testing and Validation – Whether through formal systems integration testing with your IT team, or via the category expert’s and supplier’s review and test-use of the implemented RFx templates, testing follows configuration in an iterative fashion.
Step 5: Iterative Deployment – moving your configurations into the production environment may require a coordinated effort with other systems or teams.
Step 6: Iterative Training – Newly-deployed functionality is only useful if your team knows how to properly use it. To borrow a phrase, we would rather “teach you to fish” than to provide you with the fish.
Step 7: Knowledge Reinvestment – As your experience grows, so will your needs. Step 7 is intended to support the initial activities after deployment, to capture the lessons learned for your organization, and to identify opportunities for additional optimization, refinement and enhancement. Step 7 is often followed by Step 1 (for a new phase or for implementing your next great idea)