| 1. |
ERP II Demystified ( Pages)
by Sean Wheller
Jun 18, 2004
Abstract : As organizations prepare for their next ERP version upgrade, they find themselves trying to make sense of a new iteration that disrupts the traditional understanding and thinking about ERP. ERP II requires organizations to transform from a focus on internal resource optimization to a new focus on process integration and external collaboration. To help organizations make sense of this new iteration, we look at why ERP II has come about, how it differs from ERP, and how it promises to change the way organizations do business in the future.
|
| 2. |
Evaluating Alternatives: Key Questions To Ask When Considering An Alternative ERP/MRP System ( Pages)
by Ned Lilly
Jan 27, 2003
Abstract : Replacing an aging enterprise resource planning/manufacturing resource planning (ERP/MRP) system to stay competitive brings with it a host of questions.
|
| 3. |
Top 10 Reasons For Having A Project Kickoff - Part II ( Pages)
by Joseph J. Strub
Jan 1, 2004
Abstract : You are about to embark on an important project. Whether the project is software or hardware related, it is a good idea to hold a project kickoff meeting. Don’t miss this excellent opportunity to get across important communications and establish the tone for the project. This article discusses the 10 objectives of a project kickoff meeting, how to achieve them, and templates for presenting them. In Part II, reasons 7, 6, and 5 focus on preparing the team to undertake the project and generally giving them the confidence to do it.
|
| 4. |
Computer Associates Jasmineii - When Is A Portal Not Just A Portal? ( Pages)
by M. Reed
May 18, 2001
Abstract : Computer Associates International, Inc. has announced the availability of Jasmineii Portal 3.0, the latest version of its portal technology. The product also functions as a front-end to the complete Jasmineii architecture, which is a fairly complete Application Integration framework. Why don't customers know CA does Application Integration? CA is still working on that one.
|
| 5. |
Can ERP Meet Your eBusiness Needs? Part Two: ERP is the Foundation ( Pages)
by Cindy M. Jutras
Apr 29, 2003
Abstract : As a result of this push towards full eBusiness integration, businesses face challenges that force them to push the envelope of business information systems. ERP grew from its predecessors of MRP and MRP II, constantly expanding its solution footprint to address more and more of the needs of the enterprise. As you approach eBusiness, whether you do so eagerly or are dragged there kicking and screaming, you will find your business much more exposed.
|
| 6. |
INFIMACS Boasts MRP Relevant To MROs ( Pages)
by P.J. Jakovljevic
May 9, 2002
Abstract : Through incrementally adding functionality tidbits that are crucial to its target market and that are not easily emulated by its competitors, Relevant continues to have a fair shot at delivering a viable solution to project-based discrete mid-market manufacturers such as aerospace contractors, contract manufacturers of electronic components, and MRO organizations.
|
| 7. |
Pull vs Push: a Discussion of Lean, JIT, Flow, and Traditional MRP Part Two: Challenges and User Recommendations ( Pages)
by P.J. Jakovljevic
Jan 15, 2004
Abstract : While lean/flow leverages practices to stay ahead of actual demand, traditional approaches better coordinate secondary, back-office systems like accounting and HR. Moreover, flow should be a company-wide strategy that impacts more than manufacturing.
|
| 8. |
Pull vs Push: a Discussion of Lean, JIT, Flow, and Traditional MRP Part 1: Tutorial ( Pages)
by P.J. Jakovljevic
Jan 14, 2004
Abstract : Flow manufacturing leverages techniques to help manufacturers create any product on any given day, in any given quantity including the
|
| 9. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part II - The Architecture Process ( Pages)
by Glen B. Alleman
Sep 6, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems ― not an accidental by-product of the software acquisition and integration process.
|
CART 
