The document discusses project management and applying the Project Management Body of Knowledge (PMBOK) to ERP implementations. It outlines the nine knowledge areas and 47 processes from PMBOK. The knowledge areas are integration, scope, time, cost, quality, human resources, communications, risk, and procurement. It also provides timelines and reviews as part of quality management for an ASAP implementation methodology. Project management reviews are an integral part of ensuring project quality.
This document discusses ERP success and provides details about three case studies - TI InfoTech, BPCL, and ITTI - that were analyzed to identify critical success factors for ERP implementation. A survey of end users at the three organizations found that quality-related factors, such as technological newness, were the most important determinants of ERP success. The document also discusses the importance of ERP for organizations and some barriers that can prevent successful ERP implementations if not addressed properly.
The document describes the implementation of an ERP system for Global Bike Inc. using SAP software. It outlines GBI's operations and establishes a chart of accounts. It then demonstrates key procurement processes in SAP, including creating material master data, a vendor master, a purchase requisition, purchase order, and paying the vendor's invoice. The implementation is broken into phases with the goal of centralized, integrated business processes across GBI's divisions.
Project organisation and erp implementation methodGaurav Kumar
The Project Organization defines the human infrastructure of the project. This task is designed to define the project organization chart, the roles, and the relationships of the project team. The organizational structure clearly identifies roles and responsibilities of each position, augmenting the existing role definitions where necessary to cover all of the responsibilities. The Project Organization technique that is used in this step provides a standard set of roles and responsibilities which can be customized for a particular project. This should cover all personnel resources required, both full and part time.
The document outlines the stages and themes of a generic SAP implementation project based on the ASAP methodology. The stages are preparation, design, realization and testing, final preparation, and go-live. The project themes include business process, testing management, training, business change, technical solution/infrastructure, and data management. The stages provide a framework for defining, planning, and launching an SAP project.
The presentation provided an overview of SAP's ASAP 8 methodology framework for SAP projects and services. Key points included:
1) ASAP 8 is SAP's prescriptive methodology for delivering projects and services across SAP's delivery models, including Rapid Deployment Solutions, Assemble to Order, and traditional design-based projects.
2) Over 200 SAP preconfigured services are based on ASAP 8's work breakdown structure to provide consistency.
3) Updates in ASAP 8 include improvements to quality gates, guidance for agile and design thinking approaches, and changes to the work stream structure.
4) ASAP 8 can be accessed on SAP's service marketplace and supports a
The document discusses project management and applying the Project Management Body of Knowledge (PMBOK) to ERP implementations. It outlines the nine knowledge areas and 47 processes from PMBOK. The knowledge areas are integration, scope, time, cost, quality, human resources, communications, risk, and procurement. It also provides timelines and reviews as part of quality management for an ASAP implementation methodology. Project management reviews are an integral part of ensuring project quality.
This document discusses ERP success and provides details about three case studies - TI InfoTech, BPCL, and ITTI - that were analyzed to identify critical success factors for ERP implementation. A survey of end users at the three organizations found that quality-related factors, such as technological newness, were the most important determinants of ERP success. The document also discusses the importance of ERP for organizations and some barriers that can prevent successful ERP implementations if not addressed properly.
The document describes the implementation of an ERP system for Global Bike Inc. using SAP software. It outlines GBI's operations and establishes a chart of accounts. It then demonstrates key procurement processes in SAP, including creating material master data, a vendor master, a purchase requisition, purchase order, and paying the vendor's invoice. The implementation is broken into phases with the goal of centralized, integrated business processes across GBI's divisions.
Project organisation and erp implementation methodGaurav Kumar
The Project Organization defines the human infrastructure of the project. This task is designed to define the project organization chart, the roles, and the relationships of the project team. The organizational structure clearly identifies roles and responsibilities of each position, augmenting the existing role definitions where necessary to cover all of the responsibilities. The Project Organization technique that is used in this step provides a standard set of roles and responsibilities which can be customized for a particular project. This should cover all personnel resources required, both full and part time.
The document outlines the stages and themes of a generic SAP implementation project based on the ASAP methodology. The stages are preparation, design, realization and testing, final preparation, and go-live. The project themes include business process, testing management, training, business change, technical solution/infrastructure, and data management. The stages provide a framework for defining, planning, and launching an SAP project.
The presentation provided an overview of SAP's ASAP 8 methodology framework for SAP projects and services. Key points included:
1) ASAP 8 is SAP's prescriptive methodology for delivering projects and services across SAP's delivery models, including Rapid Deployment Solutions, Assemble to Order, and traditional design-based projects.
2) Over 200 SAP preconfigured services are based on ASAP 8's work breakdown structure to provide consistency.
3) Updates in ASAP 8 include improvements to quality gates, guidance for agile and design thinking approaches, and changes to the work stream structure.
4) ASAP 8 can be accessed on SAP's service marketplace and supports a
The document discusses Enterprise Resource Planning (ERP). ERP is an integrated software solution that facilitates company-wide information sharing and processes across all departments. It aims to integrate and optimize business functions and processes. The document outlines the evolution of ERP, considerations for product selection such as functionality and costs, critical success factors like management support and training, and steps to build an ERP system using external resources.
The document outlines the key phases in an ERP implementation life cycle. The phases include pre-evaluation and screening of ERP packages, evaluation and selection of a package, project planning, gap analysis, reengineering business processes, training the implementation team and end users, testing the system, going live with the new ERP system, and post-implementation support. Successfully completing all phases is necessary for a company to fully realize the benefits of an integrated ERP system.
This document provides an overview of enterprise resource planning (ERP) systems. It defines ERP as integrated software that helps businesses manage important operations like production planning, purchasing, inventory, customer service and order tracking. The document discusses how ERP systems evolved from earlier material requirements planning systems of the 1970s-80s. It also outlines key considerations for selecting, implementing and managing a successful ERP project, such as choosing a vendor, assessing total costs, avoiding common mistakes, and providing change leadership.
Asap methodology 1st phase- project preparationRangabashyam S
1. The ASAP methodology for implementation projects consists of 6 phases: Project Preparation, Business Blueprint, Realization, Final Preparation, Go-Live Support, and Run.
2. The Project Preparation phase involves initial planning and preparation activities like defining roles and responsibilities, allocating resources, and conducting a kickoff meeting. A key deliverable is the project management plan.
3. Key work streams in Project Preparation include project management, organizational change management, training, data management, business process management, technical solution management, and integrated solution readiness. The phase establishes the foundation for a successful project.
The document discusses SAP's AcceleratedSAP methodology for implementing SAP solutions. It describes the five phases of the methodology - Project Preparation, Business Blueprint, Realization, Final Preparation, and Go Live & Support. Each phase has specific goals and deliverables aimed at successfully implementing SAP and achieving business benefits. The methodology provides structure, guidance, and tools to help projects be on time, on budget and deliver business goals.
The document discusses Enterprise Resource Planning (ERP). ERP is an integrated software solution that facilitates company-wide information sharing and processes across all departments. It aims to integrate and optimize business functions and processes. The document outlines the evolution of ERP, considerations for product selection such as functionality and costs, critical success factors like management support and training, and steps to build an ERP system using external resources.
The document outlines the key phases in an ERP implementation life cycle. The phases include pre-evaluation and screening of ERP packages, evaluation and selection of a package, project planning, gap analysis, reengineering business processes, training the implementation team and end users, testing the system, going live with the new ERP system, and post-implementation support. Successfully completing all phases is necessary for a company to fully realize the benefits of an integrated ERP system.
This document provides an overview of enterprise resource planning (ERP) systems. It defines ERP as integrated software that helps businesses manage important operations like production planning, purchasing, inventory, customer service and order tracking. The document discusses how ERP systems evolved from earlier material requirements planning systems of the 1970s-80s. It also outlines key considerations for selecting, implementing and managing a successful ERP project, such as choosing a vendor, assessing total costs, avoiding common mistakes, and providing change leadership.
Asap methodology 1st phase- project preparationRangabashyam S
1. The ASAP methodology for implementation projects consists of 6 phases: Project Preparation, Business Blueprint, Realization, Final Preparation, Go-Live Support, and Run.
2. The Project Preparation phase involves initial planning and preparation activities like defining roles and responsibilities, allocating resources, and conducting a kickoff meeting. A key deliverable is the project management plan.
3. Key work streams in Project Preparation include project management, organizational change management, training, data management, business process management, technical solution management, and integrated solution readiness. The phase establishes the foundation for a successful project.
The document discusses SAP's AcceleratedSAP methodology for implementing SAP solutions. It describes the five phases of the methodology - Project Preparation, Business Blueprint, Realization, Final Preparation, and Go Live & Support. Each phase has specific goals and deliverables aimed at successfully implementing SAP and achieving business benefits. The methodology provides structure, guidance, and tools to help projects be on time, on budget and deliver business goals.