ERP System - Best Practices

ERP Systems we are talking here which incluse crm and sfa. All these are part of agency management system. Today, we are going to talk about Best Practices in ERP System.

Best Practices were also a benefit of implementing an ERP system. When implementing an ERP system, organizations essentially had to choose between customizing the software or modifying their business processes to the "Best Practice" function delivered in the vanilla version of the software.

Typically, the delivery of best practice applies more usefully to large organizations and especially where there is a compliance requirement such as IFRS, Sarbanes-Oxley or Basel II, or where the process is a commodity such as electronic funds transfer. This is because the procedure of capturing and reporting legislative or commodity content can be readily codified within the ERP software, and then replicated with confidence across multiple businesses who have the same business requirement.

Where such a compliance or commodity requirement does not underpin the business process, it can be argued that determining and applying a Best Practice actually erodes competitive advantage by homogenizing the business as compared to everyone else in the industry sector.

ref: agency management system, insurance crm, insurance sfa, wikipedia

ERP

ERP Systems we are talking here. Agency Management System is part of any ERP System. Today we are going to talk about before and after concept of ERP.

Before the concept of ERP System
Prior to the concept ERP systems, departments within an organization (for example, the human resources (HR) department, the payroll department, and the financials department) would have their own computer systems. The HR computer system (often called HRMS or HRIS) would typically contain information on the department, reporting structure, and personal details of employees. The payroll department would typically calculate and store paycheck information. The financials department would typically store financial transactions for the organization. Each system would have to rely on a set of common data to communicate with each other.

For the HRIS to send salary information to the payroll system, an employee number would need to be assigned and remain static between the two systems to accurately identify an employee. The financials system was not interested in the employee-level data, but only in the payouts made by the payroll systems, such as the tax payments to various authorities, payments for employee benefits to providers, and so on. This provided complications. For instance, a person could not be paid in the payroll system without an employee number.

After
ERP software, among other things, combined the data of formerly separate applications. This made the worry of keeping numbers in synchronization across multiple systems disappear. It standardised and reduced the number of software specialties required within larger organizations.


ref: Agency Management System, wikipedia

ERP System Features - 2

ERP System we are talking here, we talk ERP System Features in our last post. Today we are continueing that here as a part of agency management system.

ERPs are often incorrectly called back office systems indicating that customers and the general public are not directly involved. This is contrasted with front office systems like customer relationship management (CRM) systems that deal directly with the customers, or the eBusiness systems such as eCommerce, eGovernment, eTelecom, and eFinance, or supplier relationship management (SRM) systems.

ERPs are cross-functional and enterprise wide. All functional departments that are involved in operations or production are integrated in one system. In addition to manufacturing, warehousing, logistics, and information technology, this would include accounting, human resources, marketing, and strategic management.

ERP II means open ERP architecture of components. The older, monolithic ERP systems became component oriented.

EAS — Enterprise Application Suite is a new name for formerly developed ERP systems which include (almost) all segments of business, using ordinary Internet browsers as thin clients.


ref: Insurance CRM , SFA Software, agency management system, wikipedia

ERP System Features - 1

We are talking ERP Systems here. We talked features of Enterprise Resource Planning in our last post. We continue with that today.

Enterprise Resource Planning is a term originally derived from manufacturing resource planning (MRP II) that followed material requirements planning (MRP). MRP evolved into ERP when "routings" became a major part of the software architecture and a company's capacity planning activity also became a part of the standard software activity. ERP systems typically handle the manufacturing, logistics, distribution, inventory, shipping, invoicing, and accounting for a company. Enterprise Resource Planning or ERP software can aid in the control of many business activities, like sales, marketing, delivery, billing, production, inventory management, quality management, and human resource management.

ERP systems saw a large boost in sales in the 1990s as companies faced the Y2K problem in their legacy systems. Many companies took this opportunity to replace their legacy information systems with ERP systems. This rapid growth in sales was followed by a slump in 1999, at which time most companies had already implemented their Y2K solution.

we continue our talk in next post.

ref: CRM Software, wikipedia

ERP System Features

Enterprise Resource Planning (ERP) System we are talking here and in last post we talk about Overview of ERP System.

Today we are going to talk about ERP System Features.

Ideally, ERP delivers a single database that contains all data for the software modules, which would include:

• Manufacturing
  Engineering, Bills of Material, Scheduling, Capacity, Workflow Management, Quality Control, Cost Management, Manufacturing Process, Manufacturing Projects, Manufacturing Flow.
  
• Supply Chain Management
  Inventory, Order Entry, Purchasing, Product Configurator, Supply Chain Planning, Supplier Scheduling, Inspection of goods, Claim Processing, Commission Calculation.
  
• Financials
  General Ledger, Cash Management, Accounts Payable, Accounts Receivable, Fixed Assets.
  
• Projects
  Costing, Billing, Time and Expense, Activity Management.
  
• Human Resources
  Human Resources, Payroll, Training, Time & Attendance, Benefits.
  
• Customer Relationship Management
  Sales and Marketing, Commissions, Service, Customer Contact and Call Center support.
  
• Data Warehouse
  and various Self-Service interfaces for Customers, Suppliers, and Employees.

ref: CRM Software, wikipedia

Enterprise Resource Planning System

Enterprise Resource Planning we are talking here and we talk Origin of the term. We also talk ERP Sytem-1 and ERP System-2 in older post.

Today we are going to talk about overview of Enterprise Resource Planning System.

Overview
Some organizations — typically those with sufficient in-house IT skills to integrate multiple software products — choose to implement only portions of an ERP system and develop an external interface to other ERP or stand-alone systems for their other application needs.

For instance, the PeopleSoft HRMS and financials systems may be perceived to be better than SAP's HRMS solution. And likewise, some may perceive SAP's manufacturing as better than PeopleSoft's equivalents. Same way BimSym’s Leadorganizer is better than other CRM and SFA software in the industry. In this case these organizations may justify the purchase of an ERP system, but choose to purchase the PeopleSoft HRMS and financials modules from Oracle, and their remaining applications from SAP, BimSym.

This is very common in the retail sector, where even a mid-sized retailer will have a discrete Point-of-Sale (POS) product and financials application, then a series of specialized applications to handle business requirements such as warehouse management, staff rostering, merchandising and logistics.


ref: crm & sfa software, wikipedia, customazie software development