The ERP paradox

Global processes to support the Accounting, Engineering or Supply Chain activities across the whole company

However, the implementation of an ERP system requires an expensive and long project. Several conflicts may lead to poorly adjusted or inefficient solutions:

Company business requirements conflicting with ERP system functions and leading to expensive customizations

High technical complexity required in certain areas (like system administration, interfacing with internet applications or BI applications) leading to poor service or incomplete solution

Resistance to changes resulting in more customizations or keeping existing software applications – as a lack of ambition in the ERP deployment

Solving this paradox is a true challenge.

Designing and building efficient solutions

An efficient Architecture

The ERP system covers many functions but still needs to be interfaced with external and internal software applications:

Third party logistic suppliers, transportation companies

Engineering System, Laboratory system, Manufacturing Execution System

As well as local applications used to streamline local processes

The initial system architecture should take care of all of these applications and build a global solution allowing to manage the company diversity. The Business Intelligence system is part of this architecture. Very important too: a strong Enterprise Bus System to secure and manage interfaces between software applications.
The Architecture is based on a road map because all of the requirements cannot be addressed at the same time. This road map should be validated by the Business and used to managed priorities.

ERP and Business Basics consistency

The industry type, the level of regulation, the distribution and planning system imply specific requirements. Companies have developed processes and have built teams to respond to these requirements. To support the company processes, the information system has to capture and deliver the right data at the right place – across the entire company – on a daily basis.

The ultimate details of the business processes (reports, labels, excel spreadsheets, any piece of data…) should be considered during design – because it is the place where business requirements can be fully understood before translating them into an IT solution.

As a consequence of this approach, the designed solution should really help the business in its daily activities:

Zero paper by using labels, bar code devices and electronic signature

Compliant system adjusted to the industry good practices and standards

Stick to the Oracle standards

Oracle e-Business Suite is a highly flexible system. The manufacturing and distribution modules can be adjusted to the company activity and size. This is obtained by choosing the right manufacturing and distribution modules and by a relevant setup.

An Oracle standard solution is fast to build, can be demonstrated to the business during Conference Room Pilot sessions. A standard solution can be easily adjusted and discussed in an Agile approach.

Acting this way will reduce the volume of customizations. More importantly it is a means to ease the change management. Just because the solution can be directly demonstrated to and tested by the business. The new solution becomes obvious and is usually well accepted.

This site

The solutions proposed here are the result of years of Oracle projects. They have been implemented with success, they stick to the Oracle standard and propose a real improvement for the business. Quality, Planning are some of the covered topics. Enterprise Asset Management and Manufacturing to come soon.