A product software implementation method is a systematically structured approach to effectively integrate a software based service or component into the workflow of an organizational structure or an individual end-user. This entry focuses on the process modeling (Process Modeling) side of the implementation of “large” (explained in complexity differences) product software, using the implementation of Enterprise Resource Planning systems as the main example to elaborate on. Overview A product software implementation method is a blueprint to get users and/or organizations running with a specific software product. The method is a set of rules and views to cope with the most common issues that occur when implementing a software product: business alignment from the organizational view and acceptance from human view. The implementation of product software, as the final link in the deployment chain of software production, is in a financial perspective a major issue. It is stated that the implementation of (product) software consumes up to 1/3 of the budget of a software purchase (more than hardware and software requirements together). Implementation complexity differences The complexity of implementing product software differs on several issues. Examples are: the number of end users that will use the product software, the effects that the implementation has on changes of tasks and responsibilities for the end user, the culture and the integrity of the organization where the software is going to be used and the budget available for acquiring product software. In general, differences are identified on a scale of size (bigger, smaller, more, less). An example of the “smaller” product software is the implementation of an office package. However there could be a lot of end users in an organization, the impact on the tasks and responsibilities of the end users will not be too intense, as the daily workflow of the end user is not changing significantly. An example of “larger” product software is the implementation of an Enterprise Resource Planning system. The implementation requires in-depth insights on the architecture of the organization as well as of the product itself, before it can be aligned. Next, the usage of an ERP system involves much more dedication of the end users as new tasks and responsibilities will either be created or shifted. Examples of other "larger" product software are: Enterprise resource planning software Customer relationship management software Content management system software Human resource management systems Supply chain management software Software customization and Business