Management of Customer Developments
It’s time for spring-cleaning, especially as far as release upgrades are concerned. Integrating customer developments that are no longer used into a new release is a considerable cost factor.
Expenditures on customer developments are not to be underestimated in day-to-day operations, either. After all, these are not just reports, but often also transactional extensions which must be dealt with and tested repeatedly within the framework of smaller process customizing activities.
The VMS approach:
By measuring the systems, VMS first determines which customer developments are used at all, by whom, and how frequently. On the basis of that hard data, a decision can be made as to which components should be included. The automated way of cleaning systems before the release change considerably minimizes the adjustment and test time and effort required.
It is important to note that the VMS measurement covers not only simple things like unused programs; it also looks at other components, such as includes, screens, CUA components, etc.
What is particularly important is to check the implicit use of those components, because deleting too much is also bad. VMS developed a cross-referencing process for that, and it is quite extensive.
You will find more information on our solutions at: