| 1. |
Should Your Software Selection Process Have a Proof of Concept? Part Two: Advantages, Disadvantages, and Conclusion ( Pages)
by Robert Rudd
Jul 13, 2004
Abstract : A proof of concept (POC) should be completed as part of the selection process when the risk of project failure is comparatively high. Risk can be measured by two key variables. These variables are complexity of requirements and level of expertise of the selection/implementation team. The more complex the system requirements, the greater the benefit obtained from a POC.
|
| 2. |
Should Your Software Selection Process Have a Proof of Concept? Part One: Structures and the Selection Process ( Pages)
by Robert Rudd
Jul 12, 2004
Abstract : This article explores how the proof of concept (POC) fits into the software selection process, when a POC should be undertaken, structural variables, and the advantages and disadvantages of the POC from the client and value-added reseller point of view.
|
| 3. |
Segregation of Duties and Its Role in Sarbanes-Oxley Compliance Issues ( Pages)
by Alexander Hankewicz
Aug 27, 2008
Abstract : The Sarbanes-Oxley Act (SOX) requires publicly traded firms to demonstrate that their accounting and reporting practices are in compliance with regulatory standards. Section 404 of SOX addresses the concept and practice of segregation of duties—a key aspect of this legislation, and the focus of this article.
|
| 4. |
So, You’re Considering a Paperless Office? ( Pages)
by N’Gai Cobb
Nov 12, 2007
Abstract : The concept of the paperless office has been around for many years, but only recently has this concept been turned into reality. This article analyzes the advantages and disadvantages of having a paperless office.
|
| 5. |
QAD Pulling Through, Patiently But Passionately Part Two: Company Background ( Pages)
by P.J. Jakovljevic
Sep 19, 2003
Abstract : QAD, a notable player in the upper middle of the discrete manufacturing market, embarked a few years ago on reinventing itself by delivering applications that would optimize complex order fulfillment processes across multiple enterprises and divisions. Another major product enhancement feat at the time was the QAD/Connects architecture, which was both an open architecture concept and a set of connectivity tools.
|
| 6. |
Symix Sytems: Shifting SME's Focus to Their Customers ( Pages)
by P.J. Jakovljevic
Sep 1, 1999
Abstract : Symix is regarded as the originator of the extended ERP concept (CSRP), which has proven to be so attractive to mid-market enterprises that two other leading mid-market vendors entered into specific R&D and licensing agreements with Symix to gain access to its SyteAPS. Despite a highly competitive environment, we predict that Symix Systems will reach $250 million in revenues within the next 3 years, based on attractiveness of its product for discrete manufacturing and distribution within Small-to-Medium Enterprises (SME).
|
| 7. |
The Power of One ( Pages)
by Brion Schweers
Aug 27, 2003
Abstract : The typical mid-market company that has roughly $350 million in annual revenue, has not fully automated its business processes, and would gladly give up its legacy systems if everything could work from one server, and give the executives the information they need in the process. Another opinion in the dilemma - the one-stop shop versus best-of breed concept.
|
| 8. |
A Demand-driven Approach to BI ( Pages)
by P.J. Jakovljevic
Jul 20, 2005
Abstract : The core concept behind the Vanguard solution is that business intelligence (BI) must be demand-driven, which means that the business needs of the user dictate the technical solution, not the other way around. In other words, it should let the business users drive the process, and remove the problems of content relevance and software complexity.
|
| 9. |
Standardizing on One ERP System in a Multi-division Enterprise ( Pages)
by Olin Thompson & P.J. Jakovljevic
Jun 1, 2002
Abstract : In an enterprise with multiple operating divisions, should the enterprise standardize on a single set of software? Recent broadening of major ERP products’ scope and the advent of Web-based product architecture may tempt corporations to consider deploying this concept. Although the enterprise can generate many benefits from standardization, they may also create other issues that often result in disruptions.
|
CART 
