VIEWPOINT CONSULT

ERP projects

Structure and process

The goal of the selection, introduction and optimization of operational software is the optimal fulfillment of the company-specific requirements. However, the introduction of modern integrated systems also opens up a strategic opportunity for many companies to improve their organizational and IT structures in the long term. We advise you in the selection and accompany you during the introduction and optimization of the systems.

Modern systems are a decisive competitive feature. The current requirements of the market can only be fulfilled after a flexible consideration of customer requirements, on-time delivery and product quality. Adapting or introducing new business software is often a difficult undertaking, especially for mid-sized companies. On the one hand, there is no easy way to survey the masses of software, and on the other hand, high investment and follow-up costs are associated with choosing a particular product. In addition, the system must fit into the existing landscape, taking the overall strategic planning into account.


ERP Projects


Decision on upstream projects (see master data and processes)
Target and project definition within a strategy workshop
Analysis of the actual state (processes, systems, data, organization)
Analysis of operational requirements, basic draft
Definition of the target system, preparation of the tender documents
Assignment of the criteria (must, should, can) in the catalog of requirements
Basic selection based on defined criteria and specifications (long list)
GAP profile and selection of providers to consider (short list)
Preparation and accompaniment of the provider presentations
Evaluation of the providers and selection of the software system
Support in contract negotiations, contract design
Project management or support in the system implementation
Evaluation of the finished target system and project completion

Master data

Often it makes sense to execute an upstream project on the subject of master data management before executing a software selection project (such a project can also be executed independently from a system selection). At the beginning, the actual situation is determined in the context of focus interviews (individually) and workshops (group / department) with the people involved. This concerns the handling of master data (procedures, master data processes), the present structure (central, decentralized), as well as the data itself (completeness, accuracy, quality, etc.).

On the basis of the actual analysis, the accompanying documentation of the weak points takes place. In the course of cross-departmental workshops, the target conception is jointly operated and the weak point analysis is further supplemented, as well as measures to be taken to remedy it. The measures are subdivided into work packages and presented in an implementation plan (contents, resources, schedule).

Business processes

Increasing competitive pressure in global markets means that more and more companies have to reconsider their own competitiveness and long-term security. Customer orientation is required. It is important to react quickly to changing market conditions. Customers make clear demands with regard to fixed delivery dates, low costs and optimal quality of products and services.

Häufig sind die Geschäftsprozesse (GP) jedoch nicht transparent und können nur oberflächlich beurteilt und verbessert werden. Darüber hinaus sind die Zuständigkeiten für die betrieblichen Leistungserstellungen nicht immer klar geregelt. Die Möglichkeiten der Informationstechnologie werden nicht optimal ausgeschöpft. Insellösungen, Mehrfachbearbeitungen und Medienbrüche bei Daten und Dokumenten sind im betrieblichen Alltag an der Tagesordnung. Often, however, the business processes (BP) are not transparent and can only be superficially assessed and improved. In addition, the responsibilities for the provision of company services are not always clearly defined. The possibilities of information technology are not optimally exploited. Isolated solutions, multiple processing and media breaks in data and documents are commonplace in everyday business.

As with master data, such projects can also be handled independently of new launches, if the existing system continues to provide a good basis, but no longer optimally fit the implemented solution (or have never optimally worked) and appropriate adjustments are required.

System selection

The goal of the selection processes we support is, in addition to coaching and project security, the identification of the provider or the software solution that best meets the current and future requirements and goals. With a clearly structured procedure, the greatest possible decision-making reliability is achieved in the selection process and the investment risk of our customers is minimized.

To secure the strategic investment decision in a suitable software system, the selection process plays a decisive role. The regular coordination between the project group of the customer and our project team ensures the completeness and correctness of the in-house and external information to be determined.

First, the existing organizational, information and communication structures are analized and recorded. Thereafter, a concept is developed, which represents the basis as a requirement profile for the specification of the system to be selected. This is followed by a basic selection and finally the concrete recommendation for the selection of the most suitable product. This recommendation provides the basis for the investment decision to be made.

In the context of the contract negotiations with the provider we support you with the preparation and drafting of improvement suggestions at the contract work. We help you to avoid situations that can arise when providers try to dispel the critical concerns of users through multiple promises. In addition to the conditions to be determined (licenses, remunerations, fees, etc.), the functionality of the software (standard functionalities, adaptations, interfaces) is a focal point.

System implementation

After choosing a system and contracting with the software vendor, the important phase of the introduction of the new system begins. This shows how systematically the selection process was carried out and which agreements were included in the contract.

At the beginning is the project plan, which specifies the implementation process with the different phases and milestones. Both the provider and the company name the responsible project leaders and project staff and must also be equipped with the necessary competences.

The basis for the implementation is the requirement profile or requirement specification, which represents the result of the selection process and was included as a binding part of the contract. Further as a binding part of the contract or as a process guide recorded target business processes round off this basis. Likewise, the modalities already defined in the order must be taken into account accordingly.

System optimization

After the introduction or long-term use of a software system, many companies are becoming disillusioned. The goals and ideas associated with the redesign of the IT systems have not been fulfilled and the acceptance of the software by the employees is often poor.

Often, the information content of the software systems is not or no longer sufficient, the effort for master data maintenance has increased significantly and is out of all proportion to the benefit, the complexity of the systems is too high, the essential functional opportunities are not sufficiently used, the users are the impact of overarching and departmental processes is not common. The optimized processes are often insufficiently implemented in the introduced software.

In order to eliminate or reduce these problems, the first step is to identify the deficiencies in using the software solution. At this point, a company has two alternatives: revision and optimization of the existing application or the replacement of the currently used software system.

Due to the high cost of replacing and reintroducing an integrated software solution, you will only select the second alternative in exceptional cases and derive new goals and improvement processes from the knowledge of the weaknesses of an existing application.