Open source integration with ERP systems

Fast, flexible, scalable solutions for existing enterprise / ERP systems.

To schedule a free consultation please contact me directly.

Introduction of Concept
Experience
Principle of Design
Available Technologies
Security Concerns
Learning Curve

Introduction of Concept:

The term Enterprise / ERP (Enterprise Resource Planning) System refers to any high-quality combination of database and application software capable of handling large amounts of data and completely supporting a large organization, thereby eliminating the need for multiple information systems by imposition of a common, standard data structure.

The examples of ERP systems are J.D. Edwards, SAP, and many more. Often, the available interfaces are clumsy and more complicated than the task for which they provide solutions. Sometimes, especially in the case of hand-held access, they are simply inaccessible.

By integrating open source technologies with the existing ERP data structure, all the efficiency and user-friendliness of cutting-edge application development can be applied to any (or all) of an organization’s current data-management structure.

Much of today’s open source efforts are focused on web technologies and http provides the perfect protocol for global accessibility to new solutions.

Experience:

I started doing open source integration with ERP systems through PCGI (a company I own and operate with my partner, Adam Fleck). We began developing blackberry accessible interfaces for common tasks such as purchase order approval and time entry. It quickly became clear that lightweight, web-acesible modules were a faster, cheaper, and more flexible alternative than any existing solution for customizing or expanding ERP systems. Since then we have designed, developed, and deployed many such applications.

Principle of Design:

Open source modules are designed so that no changes to the existing ERP data-structure or workflow are required. New modules exists as an additional, optional layer of functionality on top of, and consistent with, the client’s standard operating procedures and work-flows. Modules may be used, or not used, transparently, without compromising, or otherwise impacting, established procedures.

Available Technologies:

The open source modules are created with any scripting / programming language (Ruby, PHP, Java, .NET, etc) and a relational database. The additional database is not required, but can improve performance and allow for new features.

My language / framework of choice is Ruby on Rails, however I am happy to develop applications in any language a client is comfortable with.

Security Concerns:

I often encounter clients, more specifically IT departments, with reservations about allowing any kind of web-access to the company’s database(s). Web-based, in this case, means that a browser will provide the user-interface (as opposed to a desktop application). Open source modules live within the existing network so they are protected by all the same security measures employed for the rest of the network.

Learning Curve:

Most companies running ERP systems do not currently employ open source solutions. IT departments are busy with their day-to-day and cannot be imposed upon to adopt new languages and/or methodologies.

Open source modules should not require any upkeep or maintenance. The only area that may need attention is the web server. Common web servers, such as Apache, are used (unless otherwise requested by the client). Introductory training for all relevant technologies is a part of every installation. This includes, but is not limited to, configuration directives and general maintenance. One of the many benefits of open source tools is the extensive, free documentation and support available online.