Tags |
|
|
Links |
|
|
Casual Articles - The 12 Cardinal Sins of ERP Implementation
This article is about using online paid surveys to make money. There are several ways to get paid for your opinion online. Although each one is different, they help you achieve the same goal. Some of these surveys include:1.) Paid Surveys Several major, big name companies will pay for your opinion on their products. This may seem to good to be true, I mean why would these companies pay for your opinion? It’s really very simple, these companies used to pay for big convention-like meetings that got a lot of people together to test their products. At these conventions, they would have to give away their product, entertain, and feed hundreds of people. By paying you for the surveys, they are saving a lot of money. That is why paid surveys really pay off, not only for you, but for big name companies as well.2.) Focus Groups Focus groups are simply like forums, where people get together to brain storm about ideas. The focus groups that pay you for your time, are from big name companies that need some help. These companies need help figuring out what products will sell, and what kind of things they could create a niche in the business world with. These focus groups help companies determine what their target audience needs and wants, and then helps them to develop new product lines.3.) Movie Trailers I bet your wondering how watching movie trailers can make you money. This is also very simple. Movie companies need to know what movies will do well. A lot of research goes into this area. So, it i
(1) Lack of Top Management Commitment
The propensity of top management to delegate the oversight of an ERP implementation to lower management levels often results in (1) being "out of touch" with critical events, or (2) the lack of understanding of the size, scope, and technical aspects of the project, and subsequently, the lack of proper commitment of time and resources required for a successful implementation. The result is a failure waiting to happen.
(2) Inadequate Requirements Definition
Surveys have shown that inadequate definition of functional requirements accounts for nearly 60% of ERP implementation failures. This is simply a matter of not comprehensively an
The U. S. Department of Defense (DOD) owns and operates the Global Positioning System (GPS), including 24 satellites, each orbiting the earth every 12 hours, as the graphic above illustrates.GPS, a navigational system, computes the position and velocity of things in a highly detailed, three dimensional way.The GPS costs $400 million annually, and it is essential for our national defense.Civilian GPS usage is increasing rapidly. For example, many newer cars and boats have GPS navigation systems to show where you are, where you want to go, and how to get there.There are hand held GPS devices, too, priced around 100 dollars.Let’s apply this GPS principle—positioning--to your business.How broad is your present market positioning? Local, regional, national, international or global?What are your Business Plan goals? In what direction, and at what velocity, are you moving toward attaining your 21st Century business goals? And how are you getting there (strategies and tactics)?In most cases, your business should be moving toward a global position.Why limit your business to a neighborhood, town or city, region or just one nation? In the 21st Century, that’s neither necessary nor desirable.Everything moves and happens much faster in the 21st Century. Now is not a time for dithering slowpokes, indecisively whiny people, and those clinging to, and living in, the past (specifically, the 20th Century).Brian Tracy says that knowledg
Enterprise Resources Planning (ERP) is an outgrowth of Material Requirements Planning (MRP) initiated in the 1970's as a new computer-based approach to planning and scheduling of material requirements and inventory, featuring the time-phased order point. MRP evolved to MRP II (Material Resources Planning) the "closed loop" process, to Business Requirements Planning (BRP) and eventually to ERP. As MRPII came into vogue in the late 1970's and early 1980's, software companies began to develop software packages around MRPII concepts.
At the same time, research of integrated data bases was in progress at a university, and out of that research emerged data base management systems (DBMS). One of the earliest successful commercially-produced data base management systems was IDMS (for IBM-based systems) and DBMS (for DEC-based systems) produced by Cullinane, who's company name was later changed to Cullinet. IMS, a structured data base management system for high transactions, was another data base management system produced by IBM.
The idea of the integrated data base as the engine for fully integrated software was probably one of the greatest outgrowths of Ollie Wight's and Dave Goddard's MRP. Eventually, the acronym ERP was conceived to represent what had already been developed by software companies.
The early software packages were developed by way of a transactional approach, and were highly unfriendly to a user. With the advent of the personal computers, the development of Microsoft's Windows NT, and the mid-range IBM AS/400 computer, client-server systems began to emerge. Windows, used as the base operating system, allowed software packages to become more and more user-friendly.
Today, ERP systems have proliferated extensively, and have reached a stage where development has become industry specific. Thus it is plausible to search for an ERP package developed for one's specific industry idiosyncracies.
The Issues
The biggest single issue in ERP is the failure of a successful implementation. It is mind-boggling to continually encounter companies who make major ERP gaffes in this day and age, especially since most of the trials and tribulations of MRPII implementation were suffered and learned from in the early 1980's with alpha, beta and gamma releases.
So what constitutes failure? Several thing come to mind:
(1) Not making the promised return on investment,
(2) Inordinately extending the implementation schedule and start-up date,
(3) Running over budget by unconscionable variances,
(4) Grinding the organization to a crawl pace, or the severest of all consequences,
(5) Stopping production and/or not delivering orders to your customers.
Industry statistics show that >60% of ERP implementation starts historically fail. Does this mean that you are doomed from the start? Of course not, if you learn from the mistakes of others. So the pertinent question is what are the main causes of ERP failure and what can be done to prevent this from happening to you?
The 12 Cardinal Sins of ERP Implementation
There are twelve major reasons for why companies get bogged down or fail in implementing ERP.
(1) Lack of Top Management Commitment
The propensity of top management to delegate the oversight of an ERP implementation to lower management levels often results in (1) being "out of touch" with critical events, or (2) the lack of understanding of the size, scope, and technical aspects of the project, and subsequently, the lack of proper commitment of time and resources required for a successful implementation. The result is a failure waiting to happen.
(2) Inadequate Requirements Definition
Surveys have shown that inadequate definition of functional requirements accounts for nearly 60% of ERP implementation failures. This is simply a matter of not comprehensively and
This is one common complaint you can hear in the advertising industry. Having worked both sides of the fence, I can sympathize with the poor agencies who get knocked on the head, and I can empathize with the clients who see good money wasted on hapless campaigns.But since that statement is made “client side”, let me address it from there. Surprisingly, there are great agencies with fantastic creative teams that produce really shoddy work. How can this be? The same award winning team for XYZ Brand comes over to market your absolutely fabulous product and makes a boo-boo out of it.Now, all things being equal, it is unlikely that the team has consumed all their creativity and are now empty husks working on your account! I would like to propose one highly possible, and most likely cause for this strange phenomena.This is related to a little piece of paper which we often call an “Agency Brief” or as most Marketing Executives like to call it “my boss unreasonable demand that I stay up past midnight to finish this silly brief”. You see, the Executive thinks that the product is so well known, the company is so famous, the agency is so capable, there is nothing that needs to be said. Go for the meeting, tell them we want a nice creative advertisement for our Chinese New Year offer, throw in a poster and a direct mailer. Done. No need for some silly “Agency Brief”.That’s not the right attitude.To get the most out of your advertising agency, you, as a client; will need to take some time and effort to create a so
The idea of the integrated data base as the engine for fully integrated software was probably one of the greatest outgrowths of Ollie Wight's and Dave Goddard's MRP. Eventually, the acronym ERP was conceived to represent what had already been developed by software companies.
The early software packages were developed by way of a transactional approach, and were highly unfriendly to a user. With the advent of the personal computers, the development of Microsoft's Windows NT, and the mid-range IBM AS/400 computer, client-server systems began to emerge. Windows, used as the base operating system, allowed software packages to become more and more user-friendly.
Today, ERP systems have proliferated extensively, and have reached a stage where development has become industry specific. Thus it is plausible to search for an ERP package developed for one's specific industry idiosyncracies.
The Issues
The biggest single issue in ERP is the failure of a successful implementation. It is mind-boggling to continually encounter companies who make major ERP gaffes in this day and age, especially since most of the trials and tribulations of MRPII implementation were suffered and learned from in the early 1980's with alpha, beta and gamma releases.
So what constitutes failure? Several thing come to mind:
(1) Not making the promised return on investment,
(2) Inordinately extending the implementation schedule and start-up date,
(3) Running over budget by unconscionable variances,
(4) Grinding the organization to a crawl pace, or the severest of all consequences,
(5) Stopping production and/or not delivering orders to your customers.
Industry statistics show that >60% of ERP implementation starts historically fail. Does this mean that you are doomed from the start? Of course not, if you learn from the mistakes of others. So the pertinent question is what are the main causes of ERP failure and what can be done to prevent this from happening to you?
The 12 Cardinal Sins of ERP Implementation
There are twelve major reasons for why companies get bogged down or fail in implementing ERP.
(1) Lack of Top Management Commitment
The propensity of top management to delegate the oversight of an ERP implementation to lower management levels often results in (1) being "out of touch" with critical events, or (2) the lack of understanding of the size, scope, and technical aspects of the project, and subsequently, the lack of proper commitment of time and resources required for a successful implementation. The result is a failure waiting to happen.
(2) Inadequate Requirements Definition
Surveys have shown that inadequate definition of functional requirements accounts for nearly 60% of ERP implementation failures. This is simply a matter of not comprehensively an
You’d like to become self-employed, but would like even better the chance to enter the marketplace with a product or service which has and established track record. You, in other words, have a franchise idea, and need to take the next step.But taking on a franchise demands a lot from you; you’ll need to have the financial wherewithal and business experience to make you good franchisee material. And you’ll need some of the kind of franchise idea for which you’d be a good fit.Some franchise ideas make millions, and some franchise ideas make paupers. The great majority of the time, a franchise’s performance is directly tied to its proprietor’s dedication and skills in overcoming obstacles.You will be able to choose from among the three types of franchise idea--wholesale distribution, services, and products. If you want any chance of success, you should not choose based on the projected earnings of a franchise; you should choose based on which franchise idea would have you eager to get to work each morning and not wanting to close down each night.About The MoneyWhen you’ve settled on a franchising idea, you will have to finance it. First, you’ll have to pay a non-refundable start-up fee which will vary according to the franchise into which you are buying. You’ll need the money to cover assorted costs like insurance, local licensing fees, inventory, and possible monthly or annual royalties due to the franchisor.You should read the fine print, or better yet, have a franchise attorney read
Today, ERP systems have proliferated extensively, and have reached a stage where development has become industry specific. Thus it is plausible to search for an ERP package developed for one's specific industry idiosyncracies.
The Issues
The biggest single issue in ERP is the failure of a successful implementation. It is mind-boggling to continually encounter companies who make major ERP gaffes in this day and age, especially since most of the trials and tribulations of MRPII implementation were suffered and learned from in the early 1980's with alpha, beta and gamma releases.
So what constitutes failure? Several thing come to mind:
(1) Not making the promised return on investment,
(2) Inordinately extending the implementation schedule and start-up date,
(3) Running over budget by unconscionable variances,
(4) Grinding the organization to a crawl pace, or the severest of all consequences,
(5) Stopping production and/or not delivering orders to your customers.
Industry statistics show that >60% of ERP implementation starts historically fail. Does this mean that you are doomed from the start? Of course not, if you learn from the mistakes of others. So the pertinent question is what are the main causes of ERP failure and what can be done to prevent this from happening to you?
The 12 Cardinal Sins of ERP Implementation
There are twelve major reasons for why companies get bogged down or fail in implementing ERP.
(1) Lack of Top Management Commitment
The propensity of top management to delegate the oversight of an ERP implementation to lower management levels often results in (1) being "out of touch" with critical events, or (2) the lack of understanding of the size, scope, and technical aspects of the project, and subsequently, the lack of proper commitment of time and resources required for a successful implementation. The result is a failure waiting to happen.
(2) Inadequate Requirements Definition
Surveys have shown that inadequate definition of functional requirements accounts for nearly 60% of ERP implementation failures. This is simply a matter of not comprehensively an
We just can’t live without! But can we live with what we have? With water quality at an all time low – the needs are great for a simple, effective solution for improved drinking water. With a general increase in awareness of health requirements and an immense demand for simple answers – the providers of this solution are set to become the next millionaires.Prick up your ears because ‘The Wellness Revolution’ is here and, by all predictions, is set to become the next trillion dollar industry. You can see it everywhere, emerging as people wake from their state of slumber to regain their health and vitality after years of lethargy.The ‘Baby Boomers’ have set the pace and are demanding a better, healthier, safer way to remain fit and live longer in a world of increased uncertainties and deepening toxicity.We live in what has been described as a ‘toxic soup’ where our bodies are in a constant struggle to maintain health and stability. Chronic degenerative disease is becoming all too common and immune system problems are now the norm. People have had enough and are demanding better. So where do we start and where are the niches that aren’t being filled?As a health consultant and entrepreneur, I have seen many fads and gimmicks come and go. The quick fix, the new diet, the amazing supplement – all offering much and supplying little. People are sick and tired of being sick and tired AND ‘being taken to the cleaners’ with promises of ‘the perfect answer’.Where it all starts and en
(1) Not making the promised return on investment,
(2) Inordinately extending the implementation schedule and start-up date,
(3) Running over budget by unconscionable variances,
(4) Grinding the organization to a crawl pace, or the severest of all consequences,
(5) Stopping production and/or not delivering orders to your customers.
Industry statistics show that >60% of ERP implementation starts historically fail. Does this mean that you are doomed from the start? Of course not, if you learn from the mistakes of others. So the pertinent question is what are the main causes of ERP failure and what can be done to prevent this from happening to you?
The 12 Cardinal Sins of ERP Implementation
There are twelve major reasons for why companies get bogged down or fail in implementing ERP.
(1) Lack of Top Management Commitment
The propensity of top management to delegate the oversight of an ERP implementation to lower management levels often results in (1) being "out of touch" with critical events, or (2) the lack of understanding of the size, scope, and technical aspects of the project, and subsequently, the lack of proper commitment of time and resources required for a successful implementation. The result is a failure waiting to happen.
(2) Inadequate Requirements Definition
Surveys have shown that inadequate definition of functional requirements accounts for nearly 60% of ERP implementation failures. This is simply a matter of not comprehensively an
Managing receipts, payment slips, a note of daily expenses and many other financial documents seems like a mountain to climb. The reason is that certified public accountants or other accounting professionals keep on entangling between these documents, so that they can be tallied before the tax season approaches. Everyone wants to escape the wrath of tax raids and this has made it mandatory for every business firm to get their accounting documents in proper order. If your accounting firm is loaded with work till neck, then outsourcing is the best option in this matter. In order to do outsourcing accounting, India is considered as one of the must choice for all accounting and business firms.In one way, India outsourcing accounting has come as a boon for people who have an overload of work. Well, excess of workload can hamper the growth of business and professional’s thinking power. If a particular professional is being given so many tasks to handle, then one or the other work will remain pending and this will create a huge pile of work in the end. No one wants to disturb their lifestyle because of excess workload. Outsourcing accounting work will prove highly beneficial for you and your business. In fact, it looks as if this concept has revolutionized the way a work is being done. After all, time is a valuable thing and everyone wants to save it.India is being considered one of the best and ultimate destinations for outsourcing accounting. There are numerous reasons behind this preference. First of all, the entire cost of the
(1) Lack of Top Management Commitment
The propensity of top management to delegate the oversight of an ERP implementation to lower management levels often results in (1) being "out of touch" with critical events, or (2) the lack of understanding of the size, scope, and technical aspects of the project, and subsequently, the lack of proper commitment of time and resources required for a successful implementation. The result is a failure waiting to happen.
(2) Inadequate Requirements Definition
Surveys have shown that inadequate definition of functional requirements accounts for nearly 60% of ERP implementation failures. This is simply a matter of not comprehensively and systematically developing a quality set of functional requirements definitions. This leads to the second greatest cause of ERP implementation failures: poor package selection.
(3) Poor ERP Package Selection
Poor package selection occurs when a company has inadequately developed functional requirements definitions. It also occurs when staff members assigned to ERP projects do not take the time to run the screens of the new system, as they would during their daily work tasks, to find out if the software package features are adequate for their needs.
Another reason we have found is executives, familiar with an ERP system from a last job they held, implement the same system in their new company without defining functional requirements. We have also encountered companies who made major gaffes by selecting a package at the top levels of a company without intimately knowing its characteristics. What often results from this is the ERP package doesn't fit the organizational needs, or that the package selected takes longer to process daily work tasks.
We have also seen executives select a distribution package for a manufacturing environment, or a manufacturing package for a distribution environment, for obscure reason, such as liking one salesman over another.
(4) Inadequate Resources
The third greatest reason for ERP implementation failures is inadequate resources. Many companies will attempt to "save dollars" by doing everything on an overtime basis, whether or not there are adequate skills within the company, extending individual work loads to 150%. This approach can be a "kiss of death" for the program. Time and time again we run across this mistake in ERP implementations. The financial and emotional drain of what seems sometimes to be perpetual extensions, reschedules and delays of implementations takes its toll. People burn out after having put in extensive hours over a long period of time.
(5) Resistance to Change/Lack of Buy-in
The lack of a change management approach as part of the program can prevent a program from succeeding. Resistance to change is quite often caused by (1) A failure to build a case for change, (2) Lack of involvement by those responsible for working with changed processes (3) Inadequate communication (4) Lack of visible top management support and commitment, and (5) Arrogance. A lack of buy-in often results from not getting end-users involved in the project from the very start, thereby negating their authorship and ownership of the new system and processes.
(6) Miscalculation of Time and Effort
Another cause of ERP implementation failure is the miscalculation of effort and time it will take to accomplish the project. Companies who treat an ERP selection, evaluation and implementation comparable to buying a washing machine are doomed to failure.
(7) Misfit of Application Software with Business Processes
One of the main causes of ERP implementation failure is the misfit of application software with the company business processes. This failure -- to examine underlying business process flaws, and integrate t
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.casualarticles.com/article/20864/casualarticles-The-12-Cardinal-Sins-of-ERP-Implementation.html">The 12 Cardinal Sins of ERP Implementation</a>
BB link (for phorums):
[url=http://www.casualarticles.com/article/20864/casualarticles-The-12-Cardinal-Sins-of-ERP-Implementation.html]The 12 Cardinal Sins of ERP Implementation[/url]
Related Articles:
Manage the Transition to Your New Job
Future Sales are Hiding in Service
Bookmark it:
|