安达信-某软件公司咨询方案(编辑修改稿)

安达信-某软件公司咨询方案(编辑修改稿)内容摘要：

similar volumes and are using the product (not testing or ready to rollout). Ensure the anization understands that package software implementation projects are more expensive and provide less relative benefit than strategic, petitive initiatives。 however, these projects are critical to establishing a solid foundation to support future strategic initiatives. Some gaps will be identified during the selection process, but it isn’t until the Business Process Simulation (BPS) phase of the project that all gaps are known. Packaged software vendors incorporate industrywide best practices from their customer base into their software. During BPS, each Plaskolite business scenario is executed in the software. The team will be able to identify how Plaskolite will further change its business processes to align with the software vendor’s approach. We remend a “nomod” policy, this is achieved by executing these newly aligned business processes in the software. But unless Plaskolite management is willing to support this approach, this goal will not be achieved and modifications will be required. Use “knockout” criteria to quickly get to a short list of vendors. This will allow deep focus on a handful of viable contenders and allow more time for valueadded activities like identifying areas for improvement. Facilitative Approach Manage Expectations The Short List Gaps Between Business Requirements and Software Capabilities Section 2: Project Overview 11 169。 1999 Arthur Andersen, Andersen Worldwide SC. All rights reserved. Ongoing Project Scope amp。 Approach Arthur Andersen’s packaged software methodology framework consists of 6 major phases while emphasizing an aggressive program of project management and change enablement. This proposal addresses the first 3 phases of work. At the pletion of these phases, we will take a checkpoint with Plaskolite’s management to determine Arthur Andersen’s involvement with future phases of work. “Where do we want to be?” “What tools will we use?” “How will we use the tools?” “Construct and rollout the solution.” “How will we get there?” People Processes Technology Strategy Requirements Definition Software Evaluation amp。 Selection Design amp。 Business Process Simulation Implementation Support amp。 Continuous Improvement Implementation Planning “Stabilize and prioritize.” Checkpoint Checkpoint Checkpoint 56 weeks 34 months 58 months Project Management and Change Enablement = within scope of this proposal = future phases Checkpoint 34 weeks 2 weeks Checkpoint Software Selection and Implementation Software Selection Software Implementation Section 3: Project Approach The scope of this project will be limited to the evaluation and selection of a single integrated software package. 12 169。 1999 Arthur Andersen, Andersen Worldwide SC. All rights reserved. Design Technical Architecture Software Selection Overview We have a proven methodology and approach to software evaluation and selection. Throughout this approach, business requirements are balanced with system functionality to maximize business opportunities and benefits. • Functional • Technical • Vendor Identify Process Improvement Opportunities Identify Requirements amp。 “Knockout “ Criteria Research Software Alternatives • Strategy • Processes • Organization • Technology REQUIREMENTS DEFINITION SOFTWARE EVALUATION amp。 SELECTION IMPLEMENTATION PLANNING Checkpoint Checkpoint Plan the Implementation Review Current State Develop Preliminary Cost Estimate Finalize amp。 Obtain Approval Define Business Scenarios amp。 Conduct S/W Demos Negotiate and Complete Cost Estimate Evaluate Vendors and Choose Finalist Section 3: Project Approach 13 169。 1999 Arthur Andersen, Andersen Worldwide SC. All rights reserved. Project Approach Requirements Definition The purpose of this phase is to gather business requirements and document business processes. This is acplished through our facilitative consulting style. We work with the selection team to ensure an appropriate understanding of the current state and cooperatively craft Plaskolite’s “tobe” business process vision.  Plan the project and mobilize the “core” selection team  Facilitate group discussions and interviews with executives and key users  Identify and map key business processes  Identify key customer and vendor business requirements, as well as functional and technical software requirements  Review Arthur Andersen’s Global Best PracticeSM Knowledgebase, examples of best practices, best panies, and performance measures by business process  Identify process improvement opportunities  Prioritize the list of systems requirements from the interviews and process reviews  Research software candidates  Develop software selection “knockout” criteria (functional, technical, vendor) to shorten the list to a manageable number of contenders  Begin discussions with the software finalists regarding proposed configuration and resource requirements  Develop high level systems architecture  Develop preliminary estimate of hardware, software, training, and implementation costs and options Key Tasks  High level process maps  Global Best PracticeSM Knowledgebase examples  List of process improvement opportunities  Prioritized software selection “knockout” criteria  Initial list of software candidates through market research, industry insight, vendor viability, Arthur Andersen firmwide knowledge  Responses to software selection “knockout” criteria (Request for Information RFI)  Short list of software finalists  List of assumptions impacting cost estimate  Preliminary cost estimate。