Entry

Please elaborate on the 21st century ERP architecture

Apr 19th, 2007 04:47
Prabhash Bhattnagar, http://www.blueappleonline.com

The problem with the existing ERP systems is that the connection is 
made only on the outside. There are concerns of old core code and 
duplicate business logic. Old n-tier architectures are often connection 
challenged and duplication of business logic too, is required most of 
the time. This calls for an design of ERP architecture that is based on 
EAI considerations in mind. Tersely, an ERP system should be born to 
connect instead of being coerced into connection. Some considerations 
are 
- A 100 % managed code must build the software packages. This makes the 
software package capable of performing side tasks, security and other 
advantages. This also lowers the cost considerably as compared to 
the .net software.  
- The system must be able to avoid any duplication of business rules. 
Ideally, there should be single copy of each rule, which must be used 
for all transactions and sources. Business rules should be designed 
such that that must be able to handle all the aspects of business. 
Like, the business rules should be able to handle the ERP system's own 
user interface, along with the transactions with partners. One set of 
rules also means lower development and maintenance costs, and a greater 
speed in making connections to other systems.     
Prabhash bhattnagar
http://www.blueappleonline.com