Abstract: With the advances today in technology it has become obvious that there is a need for maintenance management theory and practice to catch up with the advances made in business management theory and practice generally. The current state of CMMS technology is at a very advanced level, in a lot of cases far more so than our ability to apply it. This tool has very strong and provable results.

Abstract: We take the liberty to expand further on the findings of a report, which was recently released by a renowned research organization, and which pinpoints enterprise applications implementations’ dissatisfactions in no uncertain terms. One may expect even more bad news in the future given the intricacy of collaborative inter-enterprise business.

Abstract: Everything in the computer industry seems to be going off-shore, why not software implementations? This article looks at reasons why remote implementation of software packages can make both logical and fiscal sense, particularly in the United States. Read on to learn why your organization may want to look at this implementation alternative more closely and not be so quick to dismiss it as a passing fad.

Abstract: The Information Technology Infrastructure Library (ITIL) provides a common process framework for driving service quality improvements and cost reductions. That’s why organizations must ensure they clearly understand the objectives of their ITIL implementations, while implementing robust governance processes to measure and report progress—or else risk implementations that fail to live up to stakeholder expectations.

Abstract: When it comes to software implementations, organizations large and small share the common goal of rapid deployment and return on investment. Small and medium businesses (SMB) however, face unique issues and challenges that might not be satisfied by vendors that typically serve the Fortune 1000 or tier one community. Such vendors may tout specialized 'SMB solutions', but many times they are nothing more than scaled-down versions of the larger enterprise suites that do not take into account SMB concerns. By following some fundamental concepts, smaller companies can make their technology investments pay off, with little disruption to the business. This paper discusses nine steps to easier ERP implementations and better profits.

Abstract: To a large extent, software packages do work out of the box. Packages that do not perform perfectly or as users would expect is when dissatisfaction arises. These can be dealt with in a rational manner through the employment of effective project and change management procedures. However, an area that typically creates problems, whether expected or not, is the development of interfaces between proprietary software that cannot be replaced.

Abstract: In order to get ahead of the systems development power curve, companies are attempting what is equivalent to executing a quadruple jump in ice skating; running a sub 3:50 minute mile in track; and winning the Tour de France in cycling--all in the same year. How? By trying to implement enterprise resource planning (ERP) and supply chain management (SCM) software at the same time. Read on why this is an ill-advised course of action with an extremely low probability of success.

Abstract: The implementation of an enterprise level system is a tumultuous event with far reaching consequences throughout an organization. Therefore we can see the implementation process as a means of taking the quantum leap in maintenance management techniques.

Abstract: How do you go about defining the requirements of large package systems, particularly those with the all-encompassing scope of ERP, EAM, and CRM software, and still satisfy the needs to the project team, the user community, and executive management? It’s a balancing act rivaling the circus performer trying to keep all of the plates spinning at once. While it is difficult to say one aspect of a project plan is more important than another, accurately and completely defining the needs to be fulfilled by the software is critical to the overall success of the implementation and the longevity of software. This article outlines a logical process for defining the requirements and keeping the plates spinning.

Abstract: Every decision you make factors some kind of risk. When making the decision to implement a content management system (CMS), it’s important to be aware of all possible potential risks—and how to prepare for them. How high is your risk of data loss? What can you do to mitigate the risk of security breach? And which is riskier for your company, a hosted or an installed CMS? Learn more about these and other risks.

Abstract: Your competitors are adopting business rules management solutions (BRMS) to achieve agility and reduce maintenance costs. With enhanced ability to store all business rules in one central location, enterprises have a unique opportunity to use non-conventional methods to test these rules, as well as their interactions with each other—without tying up their mission-critical software.

Abstract: Enterprise systems, in fact, are devised to operate by codifying a set of business processes and employees have to learn the whys, wheres, and whos of the business process (workflows) rather than hows of the software screens.

Abstract: Over the last few years the market has seen a plethora of fixed-scope and fixed-price applications, pre-packaged vertical solutions with industry templates, limited education and training, implementation tools, attractive support programs and hosting services with catchy names, all aimed at making it faster, simpler and cheaper for enterprises well under $500 million to use them. Is this approach good or bad for the user?

Abstract: System integration service provider selections and project planning should involve the same amount of due diligence as business IT strategy definition and software evaluation.

Abstract: This part discusses the causes of ill-fated implementation

Abstract: No company has ever fully evaluated the entire product that they are buying, time does not permit such a complete evaluation. Few people really track how well the software is used after it is installed.

Abstract: Despite all of these great advances in our work environments the great majority of plants and industrial organizations continue to operate in a reactive state of maintenance. Why is this so? Today the functionalities of CMMS, or the technology to manage maintenance, have outstripped our abilities to do so in practice.

Abstract: Click here to download your free pdf copy of tec best practices for software selection.