Free Accpac ERP Tools
Today's Quotes:
• A common mistake that people make when trying to design something completely foolproof was to underestimate the ingenuity of complete fools.
• It takes infinite energy to implement an ERP on time; therefore, all ERP projects are both incomplete and late.
• If a ERP project becomes too large, it will collapse into a black hole. Time and money are absorbed but nothing ever comes out.
• The first 90 percent of the implementation accounts for the first 90 percent of the implementation time...The remaining 10 percent of the implementation accounts for the other 90 percent of the implementation time.
• The bearing of a child takes nine months, no matter how many women are assigned. Many ERP Implantations has this characteristic because of the sequential nature.
• An organization that treats its ERP Consultants as morons will soon have consultants that are willing and able to act like morons only.
• Theory is when you know something, but it doesn’t work. Practice is when something works, but you don’t know why. ERP Consultant combine theory and practice: Nothing works and they don’t know why.
• For every ERP functional or technical problem there is an answer that is clear, simple, and wrong.
• The ERP implementation isn't finished until the last user is dead.
• The goal of ERP Implementation is to build something that will last at least until we've finished implementing it.
• Just because you don't know an ERP, doesn't mean you won't be called upon to implement it.
• The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents.
• Good judgment comes from experience, and experience comes from bad judgment.
• If both the ERP and the consultant disagree, then both are probably wrong.
• Rules of Optimization:
Rule 1: Don't do it.
Rule 2 (for experts only): Don't do it yet.
• Any fool can use a ERP System. Many do.
• If the automobile had followed the same implementation cycle as the ERP Systems, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside.
• There are two ways to implement error-free ERP; only the third works.
• I did say something along the lines of "Tally makes it easy to shoot yourself in the foot; SAP or Accpac makes it harder, but when you do, it blows your whole leg off."
• Accpac is simple. It just takes a genius to understand its simplicity.
• The perfect ERP implementation plan is possible if one first documents a list of all the unknowns.
• Basic Rule for ERP Implementation “First you listen to the users; then you ignore them”.
• There is no reason why anyone would want a ERP System in the Company.
• But what... is it good for? “Leading ERP System”
• One: ERP demonstrations always crash. And two: the probability of them crashing goes up exponentially with the number of people watching.
Today's Quotes:
• A common mistake that people make when trying to design something completely foolproof was to underestimate the ingenuity of complete fools.
• It takes infinite energy to implement an ERP on time; therefore, all ERP projects are both incomplete and late.
• If a ERP project becomes too large, it will collapse into a black hole. Time and money are absorbed but nothing ever comes out.
• The first 90 percent of the implementation accounts for the first 90 percent of the implementation time...The remaining 10 percent of the implementation accounts for the other 90 percent of the implementation time.
• The bearing of a child takes nine months, no matter how many women are assigned. Many ERP Implantations has this characteristic because of the sequential nature.
• An organization that treats its ERP Consultants as morons will soon have consultants that are willing and able to act like morons only.
• Theory is when you know something, but it doesn’t work. Practice is when something works, but you don’t know why. ERP Consultant combine theory and practice: Nothing works and they don’t know why.
• For every ERP functional or technical problem there is an answer that is clear, simple, and wrong.
• The ERP implementation isn't finished until the last user is dead.
• The goal of ERP Implementation is to build something that will last at least until we've finished implementing it.
• Just because you don't know an ERP, doesn't mean you won't be called upon to implement it.
• The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents.
• Good judgment comes from experience, and experience comes from bad judgment.
• If both the ERP and the consultant disagree, then both are probably wrong.
• Rules of Optimization:
Rule 1: Don't do it.
Rule 2 (for experts only): Don't do it yet.
• Any fool can use a ERP System. Many do.
• If the automobile had followed the same implementation cycle as the ERP Systems, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside.
• There are two ways to implement error-free ERP; only the third works.
• I did say something along the lines of "Tally makes it easy to shoot yourself in the foot; SAP or Accpac makes it harder, but when you do, it blows your whole leg off."
• Accpac is simple. It just takes a genius to understand its simplicity.
• The perfect ERP implementation plan is possible if one first documents a list of all the unknowns.
• Basic Rule for ERP Implementation “First you listen to the users; then you ignore them”.
• There is no reason why anyone would want a ERP System in the Company.
• But what... is it good for? “Leading ERP System”
• One: ERP demonstrations always crash. And two: the probability of them crashing goes up exponentially with the number of people watching.
