2某咨询-某软件公司的咨询方案

1、ContentsOur proposal is divided into the following sections:Section 1 Introduction.What does Plaskolite want from this project?Section 2 Project Overview. What is Arthur Andersens perspective on software evaluations?Section 3 Project Approach.How will we conduct the evaluation?Section 4 Project Team

2、Who will work on the project?Section 5 Project Timing.How long will it take?Section 6 Project Costs.How much will it cost?Section 7 Arthur Andersen.Why Arthur Andersen?Section 8 Project Resources.What are the qualifications of our team?Our Understanding of Your NeedsPlaskolites overall goal is to ev

3、aluate and select an integrated customer service, distribution, manufacturing and financial software package that best supports your business information needs. To help achieve this goal, Plaskolite would like a Arthur Andersen to assist with the evaluation and selection of a new software package. T

4、he specific objectives of this project will be to:Define and prioritize business and information requirements Identify process improvement opportunitiesResearch and identify viable software candidatesObjectively facilitate the evaluation of the most appropriate software alternativesDefine appropriat

5、e technical architectureAssist with vendor negotiationsPlan the software implementation at a high levelGoalProject ObjectivesSection 1: IntroductionOur Understanding of Your NeedsThe key deliverables to meet your objectives for this phase of the project will be:High level business process mapsProces

6、s Improvement OpportunitiesSoftware requirements and “knock-out” criteriaFunctionalTechnicalVendorList of potential software candidatesVendor demonstration scriptsSoftware selection recommendationSoftware, hardware and services cost estimatesHigh-level implementation planOrganizational impact assess

7、mentSection 1: IntroductionDeliverablesOur PerspectiveOur local experience with integrated software packages is deep and broad. Our Ohio Consulting practice, which includes Columbus, Cleveland and Cincinnati, has over 140 full-time consultants. Software implementation is the cornerstone of our pract

8、ice. Below is a list of some of our recent engagements in Ohio.Section 2: Project OverviewOur Local Manufacturing ExperienceArthur Andersens philosophy is to remain independent of software vendors.Consequently, Arthur Andersen can objectively evaluate integrated software packages against the informa

9、tion needs of our clients.High Tech Mfg.Custom Products Mfg.Custom Products Mfg.Automotive SupplierConsumer Products Mfg.What Our Software Vendor Alliances MeanArthur Andersen does not sell software or receive any financial incentives from integrated software package vendors. However, we do maintain

10、 alliance programs with the leading software providers in the market. The purpose of these alliances is to establish a team of qualified personnel from the vendor and Arthur Andersen who can effectively serve clients by delivering integrated solutions to improve business performance.Alliance agreeme

11、nts typically provide the following:Arthur Andersen can sub-contract programming services at a discounted priceArthur Andersen receives discounted training for its professionalsArthur Andersen has access to software, product support and other resourcesBy strategically aligning themselves with Arthur

12、 Andersen, key software vendors can focus on their core businesses - product development, training and support. Arthur Andersen has installed the alliance software packages at our Technology Innovation Centers for client demonstrations, training, testing and remote access.To capitalize on the collec

13、tive knowledge we have gained in this area, Arthur Andersen has also formed a Competency Center of qualified professionals with deep expertise in packaged software implementations. Through an on-line software database, this center promotes information sharing among Arthur Andersen professionals on a

14、lliance products and projects on a global basis.SSASection 2: Project OverviewExperienceIndustry ExpertiseBest Practices/Process SkillsSoftware ExpertiseKnowledge CapitalOur Perspective - Collaboration We believe true business change can only be sustained by Plaskolite team members. We will serve as

15、 “Change Agents” challenging and partnering with Plaskolite during all phases of the project.We take a facilitative approach to ensure mutual ownership and a focus on collaborative efforts, positioning Plaskolite to own the selection criteria and decision.Our approach is relationship-oriented. We wi

16、ll work with you as a business partner in this endeavor, taking your agenda as our own, and seeing the project through to a successful completion.Arthur AndersenHired ExpertsPlaskolitePlaskoliteIndustry ExpertiseBest Practices/Process SkillsSoftware ExpertiseKnowledge CapitalExperienceTypical Approa

17、ch:Outsiders “drive” the solutionOur Approach:We create an environment that enables you to develop deep skills and the final solutionFacilitative, Teaming ApproachSection 2: Project OverviewOur Perspective - Business IntegrationHolistic Business Integration ApproachImplementation of any significant

18、change requires the integration of strategy, business processes, people, and information technology. Application software must be evaluated within the context of this business integration concept to have relevance.Section 2: Project OverviewHow to:Transfer/improve skillsSpeed up actionsFlatten struc

19、turesEmpower individualsImprove serviceLeverage knowledge capitalHow to:Simplify/eliminateDo things more quicklyReduce costsDecentralize decisionsCapitalize on technologyRestructure relationshipsWhat focusWhat core activitiesWhat geographical areasHow to:Organize internallyAchieve synergyCapitalize

20、on strengthsHow to:Enable business changeMigrate to better solutionsFocus on core activities and peopleCapitalize on/share best practicesIntegrate information across functionsCentrally monitor a decentralized businessOur Perspective - Knowledge Sharing ToolsLeveraging our Firms global information sh

21、aring network is key during software evaluation projects.FinalistsPackage Software Competency CenterMethodologiesSelection MatricesResearch & EvaluationsResource ClearinghouseAndersen Firm-wide ExperienceEngagement TeamSoftware ExpertiseIndustry ExpertiseManufacturing Industry ProgramAndersen Knowle

22、dge Sharing ToolsLotus NotesAA On-line - Andersens Global Information Sharing NetworkGlobal Best Practices Knowledge Base (Intranet)KnowledgeSpaceSM (Intranet)Third Party Information Sources The Gartner-GroupAdvanced Manufacturing Research Inc. (AMR)Computer SelectDATAPROIndustry PublicationsArthur

23、Andersen Selection ToolsSection 2: Project OverviewProject Approach - Evaluation ComponentsDuring the software evaluation process, the field of potential software solutions is quickly narrowed to two. These two vendors demonstrate their products and are evaluated by the selection team. The final pro

24、duct is selected based on the demonstration results, contract considerations, and further analysis as described below.All Software Candidates15+ Candidates2 FinalistsIndustry InsightMarket ResearchVendor ViabilityArthur Andersen Firm-wide Knowledge3-5 CandidatesFunctionalFitVendor ViabilityFinalSele

25、ctionTechnology Use& Vision References &Site VisitsImplementationCostsPricing &NegotiationsRFI responses, screening interviewsDetailed Knock-out Criteria, Company size, Market Presence, AA Insight (Plaskolite and Arthur Andersen)High Level Knock-out Criteria &Preliminary Screening (Arthur Andersen)S

26、oftware demonstrations, reference checks, negotiations, and Cost / Benefit Analysis(Plaskolite & Arthur Andersen)The vendors execute the scripts during their demonstrations; the selection team scores each area based on how well the package met the needs of Plaskolite. Immediately after the demonstra

27、tions, the scores are tallied. Arthur Andersen facilitates a discussion to share the scoring results and reach a consensus on strengths and weaknesses.The demonstration results are only one component (although the most important component) of the final selection criteria. Section 2: Project Overview

28、Software Evaluation - Lessons LearnedOur approach works to complement the business knowledge of Plaskolite with the industry knowledge, technical expertise, and “best practice” work of Arthur Andersen. A package will not be embraced by Plaskolite if it is chosen solely by Arthur Andersen. We will fa

29、cilitate Plaskolite through our methodology to ensure a partnering endeavor based on your agenda.Communicate that no package will meet every perceived need and that perceptions must change. Sell the idea that nothing will improve unless it changes. Ensure the demonstration audience understands that

30、vendors want to show their strengths, not necessarily what is best for Plaskolite. Facilitate the demonstrations accordingly. Ensure references are in similar industries with similar volumes and are using the product (not testing or ready to rollout). Ensure the organization understands that package

31、 software implementation projects are more expensive and provide less relative benefit than strategic, competitive 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, b

32、ut it isnt until the Business Process Simulation (BPS) phase of the project that all gaps are known. Packaged software vendors incorporate industry-wide best practices from their customer base into their software. During BPS, each Plaskolite business scenario is executed in the software. The team wi

33、ll be able to identify how Plaskolite will further change its business processes to align with the software vendors approach. We recommend a “no-mod” policy, this is achieved by executing these newly aligned business processes in the software. But unless Plaskolite management is willing to support t

34、his approach, this goal will not be achieved and modifications will be required.Use “knock-out” 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 value-added activities like identifying areas for improvement.Facil

35、itative ApproachManage ExpectationsThe Short ListGaps Between Business Requirements and Software CapabilitiesSection 2: Project OverviewOn-goingProject Scope & ApproachArthur Andersens packaged software methodology framework consists of 6 major phases while emphasizing an aggressive program of proje

36、ct management and change enablement. This proposal addresses the first 3 phases of work. At the completion of these phases, we will take a checkpoint with Plaskolites management to determine Arthur Andersens involvement with future phases of work.“Where do we want to be?”“What tools will we use?”“Ho

37、w will we use the tools?” “Construct and roll-out the solution.”“How will we get there?”PeopleProcessesTechnologyStrategyRequirements DefinitionSoftware Evaluation & Selection Design & Business Process SimulationImplementationSupport & Continuous ImprovementImplementation Planning “Stabilize and pri

38、oritize.”CheckpointCheckpointCheckpoint5-6 weeks3-4 months5-8 monthsProject Management and Change Enablement= within scope of this proposal= future phasesCheckpoint3-4 weeks2 weeksCheckpointSoftware Selection and ImplementationSoftware SelectionSoftware ImplementationSection 3: Project ApproachThe s

39、cope of this project will be limited to the evaluation and selection of a single integrated software package.DesignTechnicalArchitectureSoftware Selection OverviewWe have a proven methodology and approach to software evaluation and selection. Throughout this approach, business requirements are balan

40、ced with system functionality to maximize business opportunities and benefits.FunctionalTechnicalVendorIdentify Process Improvement OpportunitiesIdentify Requirements & “Knock-out “CriteriaResearch Software AlternativesStrategyProcessesOrganizationTechnology REQUIREMENTSDEFINITIONSOFTWARE EVALUATION

41、 & SELECTIONIMPLEMENTATIONPLANNINGCheckpointCheckpointPlan the ImplementationReview Current StateDevelop PreliminaryCost EstimateFinalize & Obtain ApprovalDefine Business Scenarios & Conduct S/W DemosNegotiate and Complete Cost EstimateEvaluate Vendors and Choose FinalistSection 3: Project ApproachP

42、roject Approach - Requirements DefinitionThe purpose of this phase is to gather business requirements and document business processes. This is accomplished through our facilitative consulting style. We work with the selection team to ensure an appropriate understanding of the current state and coope

43、ratively craft Plaskolites “to-be” business process vision.Plan the project and mobilize the “core” selection team Facilitate group discussions and interviews with executives and key usersIdentify and map key business processesIdentify key customer and vendor business requirements, as well as functi

44、onal and technical software requirementsReview Arthur Andersens Global Best PracticeSM Knowledgebase, examples of best practices, best companies, and performance measures by business processIdentify process improvement opportunitiesPrioritize the list of systems requirements from the interviews and

45、process reviewsResearch software candidatesDevelop software selection “knock-out” criteria (functional, technical, vendor) to shorten the list to a manageable number of contendersBegin discussions with the software finalists regarding proposed configuration and resource requirementsDevelop high leve

46、l systems architecture Develop preliminary estimate of hardware, software, training, and implementation costs and optionsKey TasksHigh level process mapsGlobal Best PracticeSM Knowledgebase examplesList of process improvement opportunitiesPrioritized software selection “knock-out” criteriaInitial li

47、st of software candidates through market research, industry insight, vendor viability, Arthur Andersen firm-wide knowledgeResponses to software selection “knock-out” criteria (Request for Information - RFI)Short list of software finalistsList of assumptions impacting cost estimatePreliminary cost es

48、timateKey DeliverablesSection 3: Project ApproachREQUIREMENTSDEFINITIONSOFTWARE & HARDWARE EVALUATION & SELECTIONIMPLEMENTATIONPLANNINGCheckpointCheckpointPrepare demonstration scripts incorporating Plaskolites “knock-out” criteria Schedule vendor demonstrations, review expectations and provide scri

49、ptsFacilitate vendor demonstrationsIdentify perceived gaps between software capabilities and business requirementsEvaluate quantitative and qualitative strengths and weaknesses of the demonstrations, by gathering individual script “score cards” from the Plaskolite participants and facilitating re-ca

50、p discussions to gain consensusCheck vendor references and perform site visits as necessaryIdentify contract negotiation objectives and strategyConfirm initial assumptions regarding preliminary cost estimateUnderstand other potential cost components (one time and on-going costs)Negotiate with the fi

51、nalistsGather final quotes from software vendorsFinalize cost estimate based on hardware, software, training, implementationSenior management to select the final vendor based on:Functional fitTechnology use and visionVendor viabilityProject Approach - Evaluation and SelectionThe purpose of this phas

52、e is to ensure a fair and effective selection. It involves developing demonstration scripts and facilitating the software demos to ensure adherence to those scripts so a consistent comparison can be made. Initial gaps between requirements and software capabilities are identified and addressed. This

53、phase enables the final selection of the integrated package solution.Key TasksDemonstration scriptsSoftware finalist evaluation criteriaVendor demonstrationsDemonstration evaluationsReview of vendor referencesInventory of identified software “gaps” Negotiation objectives and strategyFinal cost estim

54、ateContract signed and software procuredKey DeliverablesREQUIREMENTSDEFINITIONSOFTWARE EVALUATION & SELECTIONIMPLEMENTATIONPLANNINGCheckpointCheckpointReferences and site visitsPricing negotiationsEstimated implementation costsSection 3: Project ApproachProject Approach - Implementation PlanningOnce

55、 the final selection is made, the planning for the implementation may occur. This involves designing, in detail, the technical architecture, planning the implementation tasks, and estimating the implementation effort. Once these plans are firmed up, expectations may be set and approval to proceed ma

56、y occur.REQUIREMENTSDEFINITIONSOFTWARE EVALUATION & SELECTIONIMPLEMENTATIONPLANNINGCheckpointCheckpointFinalize the technical architecture designPlan the Business Process Simulation and ImplementationIdentify the overall implementation approachDevelop high-level implementation plan with a proposed t

57、imeline and identified resourcesAssess organizational impact Meet with management to obtain approval to proceedKey TasksHigh-level plan for the Business Process Simulation and ImplementationOrganizational Impact AssessmentApproval to move forward with the implementationKey DeliverablesSection 3: Pro

58、ject ApproachProject Team OrganizationThe following is our suggested joint Plaskolite/Andersen project team structure. Plaskolite Executive TeamPlaskolite Project SponsorAA Engagement Partner - Todd FisherAA Project Manager - Chris WenzkeProject LeadershipSteering CommitteeResearch & Support - AA Co

59、nsultantPlaskolite Team LeadAA - Doug HoodOrder Management/Customer ServiceTeamFinanceTeamManufacturingTeamPlaskolite Team LeadAA - TBDPlaskolite Team LeadAA - TBDPlaskolite Team LeadAA - Chris WenzkeAA - TBDSection 4: Project TeamTechnologyTeamSteering committee meetings will be held on a monthly b

60、asis, and will last 1 to 2 hours.Plaskolite team lead participation will average 1 to 2 days per week on average.Additional representatives from Plaskolites functional departments will participate in each team on an as needed basis.Plaskolite will need to identify a “core evaluation team” who will p