Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
PKB25
Employee
Employee
Continuous product innovation is key to stay competitive in the market of OEMs of all sizes and industries.
Effective, traceable, secure, fast change management is a critical part of product lifecycle management and supports continuous innovation for these companies. According to an Aberdeen study 85% of all change processes still suffer from flaws and require a lot of manual tasks.

In times where product complexity rises, supply chains are global and lifecycles are getting shorter, the requirements towards a global management of engineering changes are increasing fast.

Product change management, sometimes also referred to as engineering change management, is a process which controls all engineering related product changes through the lifecycle of a product. There can be multiple reasons for product changes, such as new components, errors, legal requirements, flaws in the supply chain and so on.

The challenges when it comes to product changes are always related to costs, time and or quality. The planning, the process and the system are the key success factors for a successful executed product change. But not only this - most often in product changes, a lot of stakeholders inside and outside the company are involved. For that reason, the need for a flexible but also template based approach of an approval process is needed.

A change can be distinguished in minor or major changes. While minor changes are managed with the same product number, major changes require a new number and are not manage by validity or revision control.

Today changes often are managed in an old-fashioned manner - paper based, manual, disconnected, change packages cannot be managed at all and impact evaluation is nearly impossible while status tracking seems to be like a needle in the haystack.

Customer implementing a new change process are looking for a global approach with a formal global and local approval process speeding up the whole change process as such and make it as traceable as possible while having always speed and time to market in mind.

With SAP S/4 Change Record or SAP S/4 Enterprise product engineering you will be able to manage all types of product or engineering changes.

https://www.youtube.com/watch?v=eSXBHE7r5YM

You will be able to run a full-blown change process according to CMII standards. You can easily create your problem report, map it to the requirements from customers, service technicians or any other authoring party.

You will be able to set up the related objects in an engineering change request all in one go and assign an approval template to the request. Also ad hoc workflows can be created. All involved stakeholders get notified (engineering change notification) and also teams can be managed in the workflow process. So, no need to change a person if not available anymore.

Once the change request with all related object and the impact is analyzed, different options are modelled with redlines, the approval has happened the change can be released and implemented.

The different types of change objects can be added to a change package or a change hierarchy and change records can be split and merged as well.

Workflow, status management and approval processes as well as impact analysis are displayed graphically.

With the change dashboard the overall change management of a change coordinator can be seen in one go without searching lengthily.

The new engineering change management process by SAP is available on premise and in public cloud as well as in any hosted environment.

As such it serves discrete and process industries customers.

Key benefits are:

  • Early release of long-lead items

  • Release from the bottom up vs. all at once

  • Where-used visibility and ability to perform impact analysis impact analysis

  • Fast-track release vs. a required meeting

  • Formal release and control of the design at point of purchase vs. at release for production

  • Ability to easily build upon templates

  • Flexible workflow with templates and non-static changes

  • Split, merge, hierarchy of all changes related to one change package

  • All objects related to one change in one record

  • Redline capability to outline alternatives

  • Status management and insights

  • Change cockpit allowing a quick overview on all changes


Plus, stay tuned there is more to come. Find our latest roadmap and GTM materials here - Links.