Posts Tagged implementation

12 Steps to a Better ERP Launch

Posted by cshaul on Tuesday, 29 June, 2010

ERP implementations can turn a young project into a grey haired war veteran in no time. The stress of the implementation from Kick-off, configuration, data conversion, training, and all the other component parts up through Go-Live are no easy task.

If you have done everything right, then the Go-live should be a non-event. But in order to ensure that there is no catastrophic fallout from the cut-over, you need to prepare.

There is a good list of items that will help you to plan and prepare for the day that all eyes are on you and your launch. These steps are items that should be planned for early in the project, allowing for a smooth transition.

These 12 items include such things as planning the ROI, Utilizing outside help if needed, getting buy-in from all levels of the organization and several other key planning topics. Take a look at this list and use it the next time you are planning an implementation, You might just save a few grey hairs.

You can find the 12 Steps to a Better ERP Launch listing here.

Modern ERP: Select, Implement & Use Today’s Advanced Business Systems

ROI from OEE Software

Posted by contributor on Sunday, 20 June, 2010

OEE measures the overall efficiency of a production line or that of a whole facility. OEE makes a worthwhile improvement towards the productivity of a manufacturing unit. Implementation of software systems invariably benefits the OEE score by up to 20% in the first year. It has been proven that improving the Overall Equipment Effectiveness by just 1% produces a significant variation in the machine’s through put and savings in the unit cost of the produced items.

The OEE score is calculated from 3 elements: Availability, Performance and Quality. Availability equals the percentage of uptime of each manufacturing or plant asset. Performance equals the percentage throughput compared with the target set for it. Quality equals the percentage of scrap. To get the OEE score, multiply Availability by Performance by Quality.

Latest Oee Amazon products

OEE for Operators: Overall Equipment Effectiveness (Shopfloor Series)

Overall Equipment Effectiveness (OEE) is a crucial measure in TPM that reports on how well equipment is running. It factors three elements —the time the machine is actually running, the quantity of products the machine is turning out, and the quantity of good output – into a single combined score. Directly addressing those who are best positioned to track and improve the effectiveness of equipment, OEE for Operatorsdefines basic concepts and then provides a systematic explanation of how OEE should be applied to maximize a piece of equipment’s productivity and recognize when its efficiency is being compromised.

Features

OEE for Operators: Overall Equipment Effectiveness (Shopfloor Series)

Overall Equipment Effectiveness is valuable as a key performance indicator for factory supervisors. Whist the principles of the formula are simple, it can be extremely, highly complicated to calculate in in a working factory. Hence, special OEE software packages are normally used to acquire the data from each element of the manufacturing process and make the OEE calculation quickly. Typically this software is of a modular structure to give it maximum flexibility and allow it to fit with existing plant and data capture facilities and enterprise resouce planning system.

After the data has been capture and analysed, it is only useful once converted into reports that are reliable. OEE software from the main vendors gives a selection of reports that can be customzed and analyzed to faciliate the user to uncover what he is focused on.

OEE is accepted as the corner stone of lean manufacturing. via continuous improvements a manufacturing plant can become more energy efficient, improve productivity and decrease departmental silo-mentality as well as uncover and control risk. All aspects of manufacturing must comprehend the principles and practice of OEE and how it relates to the lean manufacturing principles as a key force for productivity manufacturing now and in the future.


Meet Your ERP Implementation Goals and Objectives?

Posted by Administrator on Sunday, 25 January, 2009

Why try to implement your ERP implementation with a phased approach? Why not just install the system and then educate the end-users in how to use it? The reason is that an ERP implementation is a huge undertaking. If done correctly, your company will benefit greatly. If done incorrectly, your company can throw away millions of dollars. Why do we say this?

via » Meet Your ERP Implementation Goals and Objectives Free Articles Directory About Business.


Survey: More SaaS development in 2009 | Between the Lines | ZDNet

Posted by Administrator on Monday, 12 January, 2009

More than half of all developers around the globe will work on Software as a Service (SaaS) apps this year, with a surge expected in the Asia-Pacific region, according to a study released today by Evans Data Corp. North America tops the list now for regions where SaaS implementation is highest, with 30 percent working on it today.

read more at…Survey: More SaaS development in 2009 | Between the Lines | ZDNet.com.


8 Steps to successful ERP Change Management

Posted by Administrator on Sunday, 30 March, 2008

All implementation project managers must focus on people, processes and technology. It is the people aspect that is often the most complicated. Any enterprise software endeavor creates a wave of resistance. The difference between success and failure is determined by how you manage the change process.

There are many methods, but one useful method is the Kotter Change Management Methodology. This method was developed and documented by John Kotter, a noteable professor at the Harvard Business School. According to Mr. Kotter, the Eight Steps to a successful change are:

1. Create a Sense of Urgency
2. Pull Together the Guiding Team
3. Decide What you will do
4. Communicate for Understanding and Buy-in
5. Empower others to act
6. Produce Short-term wins
7. Don’t let up
8. Create a New Culture

His latest book, shown here uses a fable to illustrate how to manage change is a wonderful book that gives the high-level understanding of change management. Using a penguin colony in Antarctica as the setting, the author uses this analogy to any change occurring with groups of people. It is worth a read, but more importantly it is worth your project team reading and discussing together. Using the eight steps outlined above, with a cohesive understanding of how change affects teams, together you can undertake any enterprise software rollout.

Be sure to read John Kotter’s other books on Leading Change.


The Importance of Assigning Tasks and Resources in Project Management

Posted by Administrator on Tuesday, 6 March, 2007

One of the key success factors in an ERP, CRM, or other implementation is that there is good project management. This article touches on some of the features of managing the project: managing Tasks and managing Resources.

The Importance of Assigning Tasks and Resources in Project Management
John Reynolds

There are two major ways to estimate the lengths (i.e., durations) of tasks. The simplest way is to estimate the elapsed time of a task.

If someone says it will take him a week to do a particular task, he is probably offering an elapsed-time estimate. They generally mean that it will take him one work week to get a task done, not that it will take them 40 hours. When estimating elapsed time, people generally account for not working on the project tasks full-time, and for working on other, higher-priority tasks first.

In most projects, however, lengths should be estimated based on the amount of work, not the amount of time. That way, adding resources will shorten a task, and using resources only part-time will lengthen a task. Tasks that fluctuate like this depending on the resources assigned are called resource-constrained tasks.

There are several ways to estimate the resource time for a task. One is to let the project manager calculate the estimates based on an employees performance on similar tasks. Another is to let the employees performing the tasks calculate their estimates, generally based on how they performed on similar tasks. A third way to estimate is to use standard metrics for generic tasks.

Although many project managers like to follow the standards established by these generic metrics, their plans are generally more accurate when they and their employees do their own estimating. It usually takes three to five projects to become proficient, but the eventual accuracy is worth the delay. Sometimes tasks will not be resource-constrained and can be estimated based on the elapsed times. Examples would be training classes or project meetings. Even though two or more people may attend a class or meeting, the length of the task does not shorten. These types of tasks are called time-constrained.

If estimates are being provided from standard metrics or project managers, them resources (i.e., employees) should be assigned after task lengths are determined. If estimates are coming from the employees performing the tasks, obviously these steps will be reversed. Regardless of the order of these two steps, one or more employees should be picked for each task that is resource-constrained.

Employees assigned to multiple tasks are often scheduled for too much work while there are simultaneous tasks to complete and not enough work when there are no task assignments. To maintain a consistent workload, resources need to be ‘leveled.’ There are only two main ways to level resource allocations: by adjusting the task schedule or adjusting the resource assignments. Project management packages generally adjust the schedule to increase the amount of time it takes to finish the project.

Remember these basic principles for assigning task lengths and resources to improve your management proficiency.

John Reynolds has been a practicing project manager for nearly 20 years and is the editor of an informational website rating project management software products. For more information on project management and project management software, visit Project Management Software Web.

Nozbe


ETO ERP: Making the Wrong Choice

Posted by Administrator on Monday, 9 October, 2006

ETO ERP: Making the Wrong Choice
Roger Meloy

Enterprise Resource Planning (ERP) systems offer great benefits to engineer-to-order (ETO) companies looking to increase productivity and decrease cost. According to TR Cutler, spokesperson for the ETO Institute, ‘These benefits come as a result of a successful implementation, but not every implementation is successful.’ Cutler asserts that, ‘One reason some implementations are not successful is the selection of the wrong system.’

The ETO Institute has just published a white paper, ‘Why Do Companies Choose the Wrong System?’ This document is written with engineer-to-order companies in mind. It highlights the problems facing ETO companies trying to find and evaluate a new ERP system. The while paper provides some time and simple steps companies can take to reduce the chances of making a critical mistake. (www.etoinstitute.org)

Cutler, who authors regular columns for Industrial Connection magazine (www.industrialconnection.net) and InMFG magazine (www.inmfg.com) is looking for case study profiles of ETO manufacturing companies and their ERP experiences. ‘The good, the bad, the ugly. I want to know what ETO manufacturers think about the ERP selection process, what companies have served them well and which have not. This will provide an interesting profile for the members of the ETO Institute.’

The ETO Institute specifically highlights some of the problems ETO manufacturers face when searching for an ERP system. Go to www.etoinsititute.org and learn more. Registration is free of charge and more than a thousand ETO manufacturers are expected to join in 2005.

Thomas R. Cutler ETO Institute 954-486-7562 www.etoinstitute.org e-mail protected from spam bots


Best Practices in ERP Software Selection

Posted by Administrator on Saturday, 5 August, 2006

This is a great post that gets right to the point about ERP Selections:

Best Practices in ERP Software Selection
Posted 8/2/2006 by Eric Kimberling (ERP Consultant)

ERP vendor selection can be a daunting task, and one that is often not given the appropriate attention. CIOs or other executives in charge of making such major decisions often make decisions based on perception, gut feel, or faulty information. For example, executives often choose ERP software vendors based on what competitors or other large companies have chosen. However, information such as this does not necessarily reflect what is appropriate or inappropriate for your specific company. Further, planning for a successful implementation involves more than choosing the right software; it also involves preparation to ensure that ERP enables measurable improvements to your business.
In choosing an ERP or IT software package and planning for the overall project, executives need to make decisions based on objective and unbiased information rather than gut feel. In particular, organizations should consider the following:
Read More…


Twitter
  RSS Feed
 Facebook
Subscribe with Bloglines
  • Recent Posts

  • ERP Vendors Search:

    Search:  
  • Topics

  • Twitter

  • Facebook

  • Chicklets

  • Blogs Share