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: Out of 100 IT projects, 94 will start over again at least once. Before your company launches its next package implementation or upgrade, make sure you don’t cripple the project from the start. Make sure your company has a clear understanding of how important the requirements definition stage is, and carries it out properly. Most importantly, find out about tools and ideas you can put into practice immediately.

Abstract: You’ve determined the business rationale for embracing Internet protocol (IP) telephony as a strategy. Now it’s worth investing time in the project definition phase, since this will result in a clear statement of requirements that are in line with your objectives. However, how you define the project will depend on the needs of your business and your plans for convergence.

Abstract: Definition of a Request for Proposal (RFP): publication of detailed requirements by a prospective buyer in order to receive vendor offerings

Abstract: A failed software implementation can cost companies millions in wasted time and money. To ensure your software selection project isn’t a sorry statistic, use the right metrics to gauge your success. Time, budget, and functionality aren’t enough—focus your efforts on requirements analysis and definition. Take measures to ensure your software meets your needs, and discover how to do accurate requirements analysis.

Abstract: Can industry-leading practice be found in a commodity software package? If we accept that application software is a commodity, by definition, the answer is no. If a vendor claims industry-leading practice, then it is available to your competition. If we really want to have practices that lift us above the competition, it cannot be in a standard package. Where in the business do we need to be better than best practice?

Abstract: There is a great deal of confusion over the meaning of data warehousing. Simply defined, a data warehouse is a place for data, whereas data warehousing describes the process of defining, populating, and using a data warehouse. Creating, populating, and querying a data warehouse typically carries an extremely high price tag, but the return on investment can be substantial. Over 95% of the Fortune 1000 have a data warehouse initiative underway in some form.

Abstract: On July 25, Fourth Shift Corporation and SupplierMarket.com announced a partnership that will enable purchasing professionals to locate ideal trading partners, submit RFQs for new contracts, and receive the results of reverse auctions, all from their familiar Fourth Shift vendor operations, manufacturing planning and scheduling, and product definition screens. Earlier, on July 18, Fourth Shift Corporation reported a loss of $.37 per share for the second quarter ended June 30, 2000.

Abstract: Founded in 1981 as a developer of computer-aided chemical engineering software, Aspen's growth has resulted in a wide variety of applications for management and execution-level process manufacturing. Hit hard by flagging revenues, Aspen is distilling its product suite down to its most profitable elements in hopes of invigorating its business and capturing a share of the supply chain management market.

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: Informix® Corporation, has announced an XML Document Type Definition (DTD) for Extraction, Transformation, and Transport (ETT) of metadata. The DTD is designed to allow metadata sharing between different vendors’ products using the open XML standard.

Abstract: Since supply chains, by definition, are about the end-to-end inter-enterprise process, we highlight the growing importance of looking outside your four walls when thinking about supply chain performance management. If you are overwhelmed by the number of supply chain measures you are tracking, it’s better to focus your energies on a few that can have a significant impact.

Abstract: Microsoft Convergence 2003 provided a perfect learning experience to appreciate the overall Microsoft Business solutions and the directions that Microsoft intends to take. To that end the word 'convergence' was not an element of pure fate but rather a portrayal of integration between Microsoft back and front office applications. The only discordance with this depiction we felt was the way Microsoft plans to enhance its product definition through a large number of independent software vendors (ISV).

Abstract: Jeffrey Hollender has a broader definition of the Value Chain that includes the true end-to-end responsibilities as well as sustainability, a term (if you are not familiar with) means, not only recognizing all the costs incurred in the chain-human, environmental etc.

Abstract: Defining a systematic and repeatable COTS acquisition process (CAP). COTS Acquisition Process Method and References. Siemens COTS Acquisition Process Case Study. This paper introduces and describes a well-defined, systematic, and repeatable COTS acquisition process (CAP) and experience of using a tailored version of the process in a Siemens Business Unit.

Abstract: Defining a systematic and repeatable COTS acquisition process (CAP)

Abstract: What is an Acquisition Plan (AP)? Acquisition Plan Definition: "An Acquisition plan (AP) is the comprehensive document that sets forth the acquisition strategy, defines the efforts required to implement it, and ensures coordination of all human and organizational resources involved in fulfilling the organization's needs in a timely manner and at a reasonable cost.". Who Should—or Shouldn't—Write the Acquisition Plan? When is a Written Acquisition Plan Required? Informal vs. Formal Acquisition Plan Template. How Does The Acquisition Plan Contribute to Acquisition Process Improvement? Writing an acquisition plan is a procedure referenced and defined by several software engineering (SE) standards (e.g., ISO/IEC 12207, IEEE 1062), software acquisition improvement models (e.g., CMMI for Acquisition [CMMI-ACQ]), and IT governance frameworks (e.g., CObIT) that organizations implement as part of their acquisition process improvement initiative. How to Write an Acquisition Plan? Acquisition Plan—Online Resources.

Abstract: The Total Cost of Ownership (TCO) is the present value of all costs incurred during the life of a product or service (source: "The Supply Chain Cost Management: The AIM & Drive Process for Achieving Extraordinary Results", by Jimmy Anklesaria). Total Cost of Ownership (TCO) is a comprehensive set of methodologies, models and tools to help organizations better measure and manage their IT investments (source: Gartner).