SAP sample
- 1. KHI DESIGN AND TECHNICAL SERVICE SAP Business One Project Team Kickoff Meeting August 11, 2010
- 2. 1. Project Objectives 2. Project Scope 3. Project Organization Chart 5. Project Timeline 4. Project Tasks and Responsibilities 6. Next Steps
- 3. Project Objectives To enhance the processing and recording of transactions. To generate timely and accurate reports. To generate analysis reports as basis for decision making. To be recognized among the best in the industry by having the “SAP Business One” as a partner in your daily business activities.
- 4. Project Scope (Organizational) The implementation of SAP Business One will cover only KHI DESIGN AND TECHNICAL SERVICE The system will be installed, configured and implemented in one site only: KHI DESIGN AND TECHNICAL SERVICE, 20/F 6788 Ayala Avenue, Oledan Square, Makati City Philippines 1226 In the event that KHI DESIGN AND TECHNICAL SERVICE has other offices and storage locations, the Business One system will still be configured to accommodate the business process for these sites. However, the system will be installed centrally in one location (defined above) and will be accessed remotely by the other offices and locations, via leased line or DSL connection, provided that only one (1) database will be configured.
- 5. Project Scope (Functional) SAP Business One Implementation shall include the following modules: Financials and Banking Sales – A/R Fixed Assets Procurement Process and Payment Process
- 6. Project Scope (System) Recommendation: Server - Pentium IV Dual Core 1.8GHz Processor– 4GB RAM Workstation - Pentium IV 2.0 GHz Processor- 512MB RAM SERVER (Min) CLIENT (Min) MS windows 2000 Professional or MS Windows XP CPU 1x Intel Pentium IV 1x Intel Pentium III RAM 2 GB 128 MB System Partition: 500 MB Data Partition: 2 GB CD ROM Drive X24 or higher X24 or higher Display 640 x 80 with 256 bit colors or higher 800 x 600 with 24 bit colors or higher MS Internet Explorer 5.5 MS Internet Explorer 5.5 MS Windows 2000 MS Windows 2000 or XP MS SQL Server 2000, port 1433* MS Data Access Components 2.6 MS IIS, port 80* MS Data Access Components 2.6 * Not necessary to register ports. Software Operating System MS Windows 2000 Server/Advanced Server HDD Free Space 500 MB
- 7. Project Scope (Project Monitoring and Control) Project shall be tracked and monitored through: Project Status Report – to be published weekly and distributed to all Project Team Members, Project Sponsors and Stakeholders. Project Team Meeting – to be held weekly and participated by all Project Team Members. Project Steering Committee Meeting – to be held once a month and participated by the Project Steering Committee Members and the Project Managers. The project shall be controlled through the Project Change Management Process . Any change in the requirements that impacts cost and schedule shall be managed through the Project Change Administration . The Project Steering Committee shall review and approve all change requests.
- 8. Project Organization Chart STEERING COMMITTEE FUNCTIONAL TEAM TECHNICAL TEAM PROJECT MANAGEMENT KEY USERS END USERS DEVT ADMIN
- 9. Project Team Organization KHI PROJECT MANAGER - Ms Cherry Dimapilis FUNCTIONAL CONSULTANTS: - Purchasing AP - Fixed Assets - Sales AR - Financial/Banking TECHNICAL CONSULTANTS: - System Admin. - Developer - Ms Cherry Dimapilis FastTrack (withheld) (Project Manager) (withheld) (Functional Consultant)
- 10. 1. Introduction and Project Goals 2. Project Timeline 3. Project Organization Chart 4. Project Tasks and Responsibilities 5. Project Timeline 6. Next Steps
- 11. Project Organization Chart STEERING COMMITTEE FUNCTIONAL TEAM TECHNICAL TEAM PROJECT MANAGEMENT KEY USERS END USERS DEVT ADMIN
- 12. Responsibilities of the Steering Committee (SC) Provides and confirms decisions on matters concerning policies, issues, scope and planning of the project. Meets once a month or as needed. Oversees the progress of the project and plays a proactive role throughout the implementation by: Resolving conflicts through mandated or arbitrated decisions Removing obstacles and resistance the team may encounter by mandating the team’s authority Acting as the final decision maker when necessary Scheduling meetings as necessary to resolve issues Reinforcing project sponsorship by disseminating information throughout the company on a periodic basis. Approving necessary documents
- 13. Project Organization Chart STEERING COMMITTEE FUNCTIONAL TEAM TECHNICAL TEAM PROJECT MANAGEMENT KEY USERS END USERS DEVT ADMIN
- 14. Responsibilities of the Project Management Plan, direct and manage the overall project Resolve project, design and implementation issues Mobilize staff in accordance with the Project Plan Deliver detailed task list, deliverables and responsibilities Issue handling and resolution procedures Submit consolidated monthly implementation status reports Attend Steering Committee and Project Management meetings
- 15. Project Organization Chart STEERING COMMITTEE FUNCTIONAL TEAM TECHNICAL TEAM PROJECT MANAGEMENT KEY USERS END USERS DEVT ADMIN
- 16. Responsibilities of the Functional Team Provide information and document “AS-IS” and “TO-BE” business processes and procedures Implement and communicate the “TO-BE” business processes and change initiatives Create functional /integrated system test scripts Conduct User Acceptance Testing (UAT) Create end user manuals for training Conduct End User Training (EUT) Create user authorization profiles Execute “GO-LIVE!” plan Provide post-production support to end users
- 17. Project Organization Chart STEERING COMMITTEE FUNCTIONAL TEAM TECHNICAL TEAM PROJECT MANAGEMENT KEY USERS END USERS DEVT ADMIN
- 18. Responsibilities of the Technical Team Configure the SBO software in accordance with the approved “TO-BE” Business Process Ensure that technical environment is ready for Project Team Maintain Technical Environment Participate in Maintenance Activities Participate in the revisions of the Technical Procedures and Operations Manual
- 19. 1. Project Objectives 2. Project Scope 3. Project Organization Chart 4. Project Tasks and Responsibilities 5. Project Timeline 6. Next Steps
- 20. Project Timeline Project preparation Detailed Process Analysis 1 Configuration and Testing 2 August August September Sept/October Timetable in Months Deploy/Post production support 4 L Go-Live: Final Preparation for Go Live 3
- 21. Stages and Milestones Deploy/ Post production support Productive system Prototype Stable system & confident users Final Preparation for Go Live Configuration and Testing Detailed Process Analysis Project preparation 1 2 3 4 Go Live Procedure Procedure Procedure Project plan - Kickoff - Standards - Refined scope Conceptual Design Detailed Requirements - GAP Analysis
- 22. 1. Project Objectives 2. Project Scope 3. Project Organization Chart 4. Project Tasks and Responsibilities 5. Project Timeline 6. Next Steps
- 23. Next Steps Day 1 : Actual Kick Off Project Plan Scheduling with KHI & Team Members Day 2: SBO Overview and Business Process Workshop Pre-requisites : Project Office/Room ( with network / internet facility, communication facility, at least 2 workstations and printer) “ As-Is” Business Process Documentation, Process Flow Chart, etc. Existing Chart of Accounts Existing list of Business Partners
- 24. Next Steps END OF SLIDE SHOW
Editor's Notes
- #2: This presentation is for a Consulting audience To understand the mid-market, why we want to be there, What is our approach/offering to that market High level next steps
- #3: Context SAP Consulting Positioning Positioning the Roadmap within the Mid Market Package Solution Roadmap inputs, objectives and tactics Packaged Solution Roadmap Overview Traditional ASAP vs. the SAP Best Practices Roadmap A joint approach for sales & delivery Key responsibilities, activities & accelerators
- #11: Context SAP Consulting Positioning Positioning the Roadmap within the Mid Market Package Solution Roadmap inputs, objectives and tactics Packaged Solution Roadmap Overview Traditional ASAP vs. the SAP Best Practices Roadmap A joint approach for sales & delivery Key responsibilities, activities & accelerators
- #20: Context SAP Consulting Positioning Positioning the Roadmap within the Mid Market Package Solution Roadmap inputs, objectives and tactics Packaged Solution Roadmap Overview Traditional ASAP vs. the SAP Best Practices Roadmap A joint approach for sales & delivery Key responsibilities, activities & accelerators
- #23: Context SAP Consulting Positioning Positioning the Roadmap within the Mid Market Package Solution Roadmap inputs, objectives and tactics Packaged Solution Roadmap Overview Traditional ASAP vs. the SAP Best Practices Roadmap A joint approach for sales & delivery Key responsibilities, activities & accelerators