ERP on Tablet PCs

ERP on Tablet PCs is Now!

ERP on Tablet PCs is here now. Earlier we did an article on ERP on the iPad. With the amazing pace of technology, people can now use mobile platforms for accessing their corporate data. For some people, the iPad is a great tool, but others may have different views on using the iPad. Now there is an alternative. Small form factor Tablet PCs are available. Some of these are Windows-based and others are Android OS-based.

Imagine being a salesperson on the road and being able to review a customer account before the big meeting right from your car. Or during the meeting, being able to check stock on a particular item for the client right in their office! These are now completely realistic scenarios. Allowing the ERP on Tablet PCs to be a reality today.

Of course, it will have to gain support of the IT departments who are holding security as one of the highest priorities. Issues such as security will need to be addressed on a company-by-company basis to ensure that the corporate data is still well protected. But many companies are providing this data already on a web enabled portal, which would be perfect for ERP on a Tablet PC scenario.

We are seeing a lot of iPhone and Android apps being made for the phones, but these apps will also run ERP on Table PCs as well. So within a few years we should see a lot more of these apps available from all the major ERP vendors.

Here is a video review of the ViewSonic ViewPad 7 that will give you an idea of how powerful these technologies are now and it will give you an idea of how you will soon see ERP on the Tablet PCs.

ERP on Tablet PCs – ViewSonic Video Review

Click on the video to find out more information.

File as: ERP on Tablet PCs

ERP System

“ERP System” is a way of describing Enterprise Resource Planning. An ERP System is a set of people, process and technology that enable an business to optimize and fully utilize all of their resources. So often people think of an ERP System as simply a software package. But it is much more. Let’s look at some of the aspects of a true ERP System.

ERP System Explained

If you consider all of the aspects of an ERP System, you must look at the parts of the business from a process perspective. Take for example a process of “Order-to-Cash”. This process follows the concept of taking an order for a product, checking and requisitioning inventory, preparing it for shipment, and shipping it out. Then it is invoiced, and ultimately the invoice is paid.

If you map out the Order-to-Cash process in your organization, you will likely find a lot of inefficiencies. You don’t want to automate these inefficiencies. That would only make the inefficiencies faster. So you should first look at the system of people, processes and then ultimately automate it with technology.

So your ERP System is all of the inputs and outputs to the process of taking an order and processing it through until your receive payment for that order. Take for example the Order process. The input is the order itself. The output may be the printed order or the picklist for pulling the inventory. This order is input and processed by an order entry clerk. You can see in this simple example the process of taking the order (input) and generating a picklist (output) as the first step in your order-to-cash processs.

Where possible an ERP System drives data inputs to their source. That is why Internet-based shopping carts and order systems are becoming essential. The customer is the source of the data, so they should be the source of the input into the system. You can see the beginning of a supply chain where the customer pulls inventory from the company, who then pulls inventory from a supplier. This customer, processor, supplier model repeats again and again, in both a micro level and a macro level. The order entry station is the micro level processor in the above example, and the distribution company is the macro level processor in the larger picture. You can take any process and look at the input (or the customer pull) and see what makes up the transaction, and who is the supplier for the process.

The ERP System is a many operational and financial processes that are run by people to fulfill the supply and demand of the process and ultimately streamlined and enabled by technology

Steps to improving your ERP System before automating

There are a number of things you can do, but the obvious first thing is to identify your processes and systems. Tools such as Lean Enterprise (or Lean Manufacturing) can help you reduce and eliminate waste in your processes. Based on the Toyota Production system, Lean is a very effective way to reduce wasted efforts, reduce costs, and improve your throughput.

Another area to look at is improving quality. Quality methods and tools can greatly increase your bottom line when properly applied. ISO9000 and similar certifications are both effective at communicating a message internally and externally, that only high quality products and services will be tolerated.

Scaling these two system improvements upon a well matched business software system will create a world-class organization. Key to finding a software to support your ERP System is matching your processes and key functions to an ERP Software solution.

Resources for Improving your ERP System

The first thing you should check out is ERPandmore.com’s free ERP System Tools that you can download. These can help you better define functions within an ERP system, Vendor Evaluations, and compare competing solutions.

Some other resources you should look to include the American Production and Inventory Control Society and the Quality Management Institute. These two organizations have a lot of publications and information about business process improvement.

With regards to the software for your ERP System, you can find a multitude of vendors in our ERP Software Directory. You can also find ERP Vendor reviews and get price quotes from SoftwareAdvice.com.

ERP System

Erp Software Companies: Oracle Corporation, Peoplesoft, Cdc Software, Sap Ag, J. D. Edwards, Cmic, Lawson Software, Eastern Software Systems

Product Description
Chapters: Oracle Corporation, Peoplesoft, Cdc Software, Sap Ag, J. D. Edwards, Cmic, Lawson Software, Eastern Software Systems, Coa Solutions Ltd, Ceridian, the Sage Group, Industrial and Financial Systems, Sescoi, Netsuite, Flexsystem, Baan, Consona Corporation, Ramco Systems, Deltek, Openda, 24sevenoffice, Nolapro, Stn Ltd, 1c Company, Cgram Software, Infor Global Solutions, Epicor, List of Erp Vendors, Qad Inc, Clear Objective, Maconomy, Visibility, Click Commerc… More >>

Erp Software Companies: Oracle Corporation, Peoplesoft, Cdc Software, Sap Ag, J. D. Edwards, Cmic, Lawson Software, Eastern Software Systems

ERP investments to slow in 2011

According to analyst group Forrester, ERP investments will continue to slow in 2011, despite growth in IT spending. Almost three quarters of those surveyed said that they would not be investing in ERP this year. That is troublesome for the industry and even ERP giants such as Oracle are being conservative this year.

You can read the full article here.

We would like to see what your plans are, please comment on this article and let us know if you are seeing any ERP investments in your company.

Top 7 tips for getting an ERP Software Selection on Track

You’re looking to find out how to get an ERP Software Selection back on track. This means that you probably have an evaluation that is going poorly and you are being led by the ERP software vendors, right? The ERP Software Selection process can be a struggle, but they don’t really have to be. If the ERP Software Selection follows a clear process, then things will run smoother. The trick is to not let the software vendors drive ERP Software Selection process.

Key ERP Software Selection Tips

1. Get Senior Management on board now
2. Be sure you have clear goals
3. Define your both your technical requirements and business requirements
4. Have a neutral third party manage the process.
5. Eliminate vendors early, and without regrets
6. Be sure you are working with the right software providers
7. Reassess your internal team

One of the top things you can do to ensure success of any Enterprise Software Selection project is to ensure that senior management is on-board with the project and that they fully support the goals of the project. If top-line management is not supportive of the project, there will be departmental and division contentions during the implementation. Often these arise during the selection process. Usually it is the case of one department competing for the same resources as another department. This often will show up on conflicting requirements for the system. Senior management must be the tie-breaker and define the future path the system should take.

If the project does not have clear goals, it is bound to flounder. Goals should not be general such as replace our system by next January. The goals should have significant business impact. A goal like “Reducing inventory by 25% while increasing sales throughput by 15% one year after implementation” is a clear goal that benefits the business and lays a stake in the ground that the system must achieve. You may find that the system can help you exceed that goal, but if you do not measure in a clear goal such as this, how will you know you have succeeded? The pain and inconvenience of an implementation will create a lot of problems within the company, but a clear goal is a great focus agent to get past the disagreements and personality conflicts.

ERP Software Selection Requirements

Often a company will define a set of requirements for a system and these requirements will have no impact on the decision of the system. Requirements need to be business driven and be tied to the factors that make your company successful. Look at the following two requirements and see which one makes it easier to help in a selection:

1. System must have serial and lot tracking.
2. System must be able to report on all shipments by a particular lot with traceability back to the original batch or incoming receiving document.

These two statements are essentially asking for the same thing, but when it comes time to solve a problem, the second requirement will distinguish of the system can solve the problem. Define your requirements around business processes, not about system features.

Maximizing Business Performance through Software Packages: Best Practices for Justification, Selection, and Implementation

Additionally, most systems nowadays can handle most of the key things you need. They all do General Ledger, Accounts Receivable, Inventory, etc. The question is, what are their strengths and what are their weaknesses. Defining specific business process requirements around the things that you do frequently is the best way to ensure that you get a system that matches your needs.
Many times when companies get in trouble with an ERP Software Selection, it is because they tried to manage it on their own. Often the IT manager or even the Controller will get the task of defining requirements and shepherding the system selection and all the vendors, value-added-resellers, and reference clients. Since they already have a key role in the company, it often a daunting task to get them to manage the selection process and do their day job. Because of this, it is often advisable to get a third party consultant involved to manage the process. The key thing about this consultant is that they should not have any financial ties to any vendors. They need to be non-biased and have experience in many ERP Software Selection projects.

Why does this help? There are a few reasons, but the key reason is that they can supplement your time and handle all of the details around gathering requirements, building scripts, arranging demos, and being the one to have to tell the vendors “no” at the end. Further, they usually come with a broader vision of how the end result can be achieved. They also make a living out of doing these selections and they know the pitfalls and can help you avoid many of the vendor “tricks” that are often played to ensure that the salesperson wins the sale. If your selection is already off track, bringing in a consultant can often help realign the various team members and refocus the selection.

As you move into the ERP Software Selection process, it is important that you eliminate as many potential candidate software systems early on, so you are not wasting your time and efforts looking at a broad range of systems. Ideally, you start with a long list of 10 and whittle that down to the top two or three. Get the software vendors that are clearly not matching your requirements out of the running as soon as possible. Use resources to help you define the best fit for your company. Many times, the vendor will bow out if they see they are not a clear fit to your requirements. But with each elimination, document why they were eliminated, so that at the end, when someone asks, “What happened to XYZ software, I thought they were a good fit”, you will have the answer as to why they are no longer being considered.

Once you have chosen the two or three candidate software systems, you want to make sure that you are working with the right provider. Software is sold either direct or through indirect channel partners. The channel partners, or value-added-resellers (VARs) each come with their own specialties. You need to find out are you dealing with a VAR or with the Software company itself. If you are dealing with a VAR, you need to make sure that they are the best VAR to help you implement the software. Do your research early, because the last thing you want to do is to change VARs late in the process. This causes all sorts of problems, most of all it delays the selection by weeks or months.

When dealing with VARs, talk to the Software Developer (see our directory of ERP software vendors here) and get their take on the VARs strengths and weaknesses and see if there may be another company you can speak with. Interview the two implementers (VARs) and see which company is a best fit to work with your company. Often it comes down to personality, one group was too arrogant, one group just didn’t get us, or even that VAR’s sales rep had a horrible personality. Find the fit because if you select their ERP software, you will be living with these people for 6-9 months or more. You want to make sure that you can work through the implementation with them as well as later rely on them for ongoing support.

If you are dealing with the software company direct, the same questions apply, but in a sense of is this the software to get married to? You need to be sure that not only the software works for you, but also that the people and company are a good fit to work with your company.

Lastly, take a good, hard look at your team. Do you have functional members from each department? Do they each bring a wealth of experience about their area? Often the hardest thing about the ERP Software Selection process is getting the best people in your company and pulling them out of their jobs to take part in the critical task of selecting a new system. They are usually the person most in demand. They need to be the one to help select the system as they know the current system and business processes inside-out.

Often an ERP Software Selection will go badly because the best people can’t give the time to make the process happen. This is why it is so important to have senior management involved and have a clearly stated set of goals for the project. Having a third party to help move things along and to look at your business objectively will aid tremendously in making the ERP selection process easier. Most of all, by putting all seven of these tips together, you will ensure that you have a successful ERP Software Selection process and that you end up with the best software for the success of your company.

ERP Software Selection

Adding Value to your ERP Requirements

ERP Requirements Refinement

When you start a system selection, you first need to determine which business process are the “value add” processes. In other words, which processes in the business add to the value of the service or product you are providing to the market. The customer is only willing to pay for those activities that help you produce, ensure quality, or account for your product or service. All other activities are waste.
ERP Requirements

When defining your ERP requirements, you need to be cognizant of these “value add” activities. These are the activities that should be captured in your requirements. Non-value-add activities should not be included in your ERP requirements. These do not produce results that create additional value to the product/service and these are only distractions when it comes down to the actual implementation.

ERP Requirements and Lean

All of this comes from Lean Manufacturing or the Toyota Production method. Essentially, as stated above, you want to eliminate “Muda” or waste in the process. Many firms have successfully implemented this in their manufacturing processes, but a smaller group have implemented this Lean system in their business office processes.

Consider this example. When defining your ERP Requirements you determine that there is an accounting process that has people spending 2 man days per month reconciling the cost of keeping track of the tools used in manufacturing. Does this process add any value to the actual production of the product? Possibly, but it sounds like this process can be reworked and possibly using the new ERP system you can eliminate this process and drive the data down to the actual transactions on the shop floor. You don’t need accountants researching the transactions. What you might need is a system that tracks the tools and their usage as part of the production process and can give a report on what these transactions cost. These transaction costs can then be factored into the pricing of the product, without the overhead of 2 man days of reconciliation.

The time when you are defining your new ERP Requirements is the perfect time to start looking critically at your processes and keying in on what brings value to the process. Then you can design your new system (both process and software) around those items that bring value to not only the customer but also the bottom line.

Lean Thinking: Banish Waste and Create Wealth in Your Corporation, Revised and Updated

Mapping your ERP requirements

When you are cataloging all of your ERP Requirements, you should write down all of your requirements (perhaps on a spreadsheet) and then give them an identifying number (such as R1, R2, R3, etc.) You can then evaluate each of these requirements with the business team to determine if the requirement is one that you want to carry forward into your deliverable of requirements that will be provided to the ERP software vendors. There is an excellent article on how to do this mapping, by author Brett Beaubouef, that describes this process.

He advocates that “Starting with the desired business results ensures that we drive to only those requirements that directly support true business value. First, it is an exercise that really puts into perspective the purpose of a business model (results). This exercise is not only useful to the project team but also the business stakeholders. Second, it is an approach that can help you justify why certain existing business activities are not being carried forward in the new business solution. Third, taking a business results oriented approach enables your project team to be more successful at focusing on the right business requirements and not wasting time on capturing requirements for non-value-add activities. ”

Another useful article that you may want to examine is the article 7 Ways to Fail in an ERP Selection

Keep in mind that some ERP Requirements that you identify may not seem valuable at first, but you need to review these requirements with the functional user team to ensure that key processes are not eliminated by mistake. There may be requirements that are a requirement because of a legal concern or perhaps a health and safety issue.

In the end, if you have successfully mapped out your business processes and defined these in your ERP Requirement list, then you will be a lot closer to selecting a system that actually functions in a way that brings value to everyone.

We hope that this will aid you in better defining your ERP Requirements.

How not to implement and use ERP software

ERP Software done correctly can be a great tool for improving a business. Done badly, it can demoralize employees and drive down business results.

Case-in-point:

How not to implement and use ERP software — ERP Software should enable business processes, not torture the employees.

“My experience with SAP was of an all-purpose integrated business solution. At the beginning of the day, I clocked in using an SAP applet. Next, I would go through a set of SAP generated planned-production orders, direct work orders, or reported directly to my supervisor. After looking through the routing information (generated through SAP), I would complete the specified task. When the task was complete, I would “clock-off” on the job, which entailed bringing the PPO to a computer, scanning it into an SAP applet, and entering my badge number (employee ID). Another thing I found interesting was the request to clock off on all activities. Even if I had only swept or scraped tape off the floors (it was a slow summer), I was asked to clock off on something called “lean labor.” I found this curious, though I suppose from an efficiency standpoint it was very important. To refer back to these “value-chains,” it is important to know exactly what every employee, piece of inventory, and work order are doing at any given time. Whether it is benig worked on, working on something, or finished, this real-time updating system allows everyone company-wide to see which projects are in progress, which are complete, and which have not been touched. Also from a managerial standpoint, it is important to see how much work each individual employee is doing and how well they are performing, not to mention that employee’s ID will always be attached to that job if future concerns arise.

Now from a business standpoint this is all well and good. But what about the employee? A lot of days, clocking and clocking out I felt as though it did not matter whether or not I was even there. There were simply no jobs to be done for entire weeks at a time, but that did not change that I had to “clock out” for certain jobs. Of course, a business wants to make sure that all of its employees are being as productive as possible, but clocking out on cleaning out the same area 3 times during a week seemed redundant and absurd. Not to mention clocking out on an activity such as “material handling” or “lean labor” is fairly arbitrary. This of course necessitated a manager to scold me when my productivity levels fell (ie playing Frisbee with a cardboard box in the back). It is important to note that I was simply summer-hired as well. Working full time at a job as a number would eventually get fairly tedious. As one of my co-workers noted to me, they had simply clocked in and clocked out for a couple of weeks and clocked off on none of the jobs they were doing. No one said anything to him. So who’s checking these jobs?” – Andrew Mellino

Implementing technology to collect data is one thing, but ERP should not be just about the numbers. ERP ideally should be “process improvement enabled by technology.” It should not be a tool to harass the employees. This is a key concept to understand when implementing and going through the design phase. Which processes are broken and which processes are working fine. Once you have defined that, then see where the ERP software can enable best business practices. It is essential that the employees have a buy in and provide feedback to this step.

If you get the employees to buy into the implementation and how it will change their jobs, you will gain the benefits of higher utilization of the system and overall better adoption. If you fail this step, you will have a failed ERP implementation. There is a saying that you should “drive data collection to the source.” This means that you should have the person who is directly responsible for the source of that data be the one who is entering it. When the ERP system is not implemented with the employees in mind, the employees will be unmotivated to use the system, ensure that the data is accurate, or even bother to put in correct information.

With the help of your line employees, design in best practices and work with them to build a system that they will use and will benefit not only them by making their jobs easier, but also benefit the whole company by driving positive results.

How to determine your ERP Evaluation Criteria

Defining your ERP Evaluation Criteria is essential for paring down the vendors and getting to the final choice. There are two focus areas for determining your selection criteria:

Determining your ERP Evaluation Criteria

1. ERP Evaluation Criteria – Process

The Process analysis for determining your ERP Evaluation Criteria is the method you would use to determine the flow of data through the system and how it would follow along your established or to-be business processes. For example, following a process flow of quoting an order, receiving the order, manufacturing or purchasing the product, shipping, and finally invoicing the order is known as the order-to-cash process flow.

There are other anther ERP Evaluation Criteria processes such as procure-to-pay, which maps the inventory requirement through the accounts payable billings. Another example could be the HR process of recruiting though retirement.

Using Process Flow documentation to determine your ERP Evaluation Criteria

By mapping out these processes in a tool such as Microsoft Visio Standard 2010 and developing a detailed flow diagram, you will have a good understanding of how your business operates. With this knowledge, your evaluation of various business management software will be a lot easier. Further, you can see how closely the software’s process flow mirrors your company’s or how disjointed the software is when it comes to your business.

2. ERP Evaluation Criteria – Functional

ERP Evaluation Criteria for the system is the detailed list of all of the things you need the system to do, from processing purchase orders, processing a sales order, to invoicing a client and producing financial reports. These are the nitty gritty things that your system should do. A good place to start is to evaluate your current system. What are the functions that the current system does well? Include these in your list. What are the things that your system does poorly, include the desired functionality in your list.

Your list should not be 10,000 lines, but rather it should look at those items that make your business unique. For example, most every business has to cut A/P checks. So most systems can do that. So do not list as a requirement that the software should be able to cut A/P checks, rather make your requirement specific to your company, such as “System should be able to cut 3 copy laser checks, with reprint capability.” That very specific requirement will help you distinguish the vendors from one another.

A good place to start is with an ERP Evaluation Criteria Template. ERPandMore has many different templates to assist you in evaluating various ERP software venders and have best practices built in. In using these as a starting point, you will save yourself countless hours in both preparing these criteria templates as well as in differentiating the vendors your are looking at. We hope this has helped to answer How to determine your ERP Evaluation Criteria