【正文】 uct System amp。 prioritize user requirements ? Receive signoff on requirements definition ? Develop business rule/workflow specifications ? Develop electronic form specifications ? Identify users of electronic forms ? Work with business process team members to map processes into the electronic form structure ? Receive signoff on development scope The development of electronic forms will be treated as a separate work stream to ensure timely implementation of the core eProcurement system. We will begin by understanding and documenting the business processes. Followed by the development of functional specifications to support the implementation of the electronic forms. Approach: Design Electronic Forms Deliverables ? Business rule and workflow specifications ? Electronic form specifications ? Signoff on the scope and specifications for each electronic form 21 PROPRIETARY and CONFIDENTIAL: Not for use or disclosure outside of Merrill Lynch except by written agreement. Major Activities ? Finalize the definition of Business Rules in the eProcurement software ? Define preliminary security scheme ? Configure User Profile data ? Develop preliminary test scripts Deliverables ? Workflow rules in place for the electronic requisitioning routing and ordering ? Preliminary test scripts This stage will include implementing the rules for electronic requisitioning, routing, and ordering for all modity groups identified in the project scope and confirmed at the beginning of the project. Approach: Define amp。 Connectivity Tests1 ? Rules, Catalogs ? Interfaces ? Business Procedure Test Scripts ? Acceptance Test Scripts ? Finalize Corporate Services rollout plan Deliverables ? Documented test scripts ? Documented test results ? Updated user procedure manual with system configuration documentation ? Signoff from Project Management that system is ready to be rolledout ? Production ready system ? Finalized Corporate Services rollout plan Once the critical development has been pleted, the project team will begin the formalized testing process. An integrated system testing and indepth User Acceptance Testing routine will be performed to ensure that the system is running as expected and that it meets Merrill Lynch’s requirements. Approach: Conduct System and User Testing 25 PROPRIETARY and CONFIDENTIAL: Not for use or disclosure outside of Merrill Lynch except by written agreement. Major Activities ? Assign user ID’s and password ? Conduct user training ? Introduce target users to technical support team and helpdesk ? Bring the system into a production mode ? Provide postproduction system support ? Evaluate initial rollout and revise rollout Strategy accordingly ? Prepare a list of enhancements needed for the NY/NJ rollout ? Plan and prepare NY/NJ user training ? Finalize rollout plan for NY/NJ users Deliverables ? Training delivered ? System is rolled out to Corporate Services user munity ? System in production ? List of required enhancements for the NY/NJ rollout ? NY/NJ Training Plan ? Finalized NY/NJ rollout plan Once the testing is pleted and the system is production ready we will move it to production and train the Corporate Services users and permit access to the system. We will then conduct postproduction support which includes performance testing and finalization of the Merrill Lynch rollout plan. Approach: Rollout to Corporate Services Users 26 PROPRIETARY and CONFIDENTIAL: Not for use or disclosure outside of Merrill Lynch except by written agreement. Major Activities ? Document additional enhancements ? Document user requirements which may result from the Corporate Services rollout ? Determine modity groups and suppliers with “punchout” capability ? Document requirements for “punchout” functionality ? Prioritize user requirements and enhancements ? Receive signoff on development scope ? Develop additional functionality ? Develop test scripts and conduct testing ? Update user guide and training plan Parallel with the Corporate Services rollout we will begin the development, testing and then deployment of additional, noncritical functionality that was not included in the initial rollout. This may include functionality such as the “punchout” capability that allows users to configure products online such as servers and work hardware. Approach: Develop, Test amp。 Implement ERP Interfaces Setup IT Environment Design amp。 Objectives 7 Project Scope 8 Critical Success Factors 9 Project Approach and Timeline Assumptions 10 Approach 12 HighLevel Timeline 30 Project Structure Team Structure 31 Project Structure 32 Team Roles and Responsibilities 33 4 PROPRIETARY and CONFIDENTIAL: Not for use or disclosure outside of Merrill Lynch except by written agreement. Table of Contents (continued) The Arthur Andersen Difference Why You Should Choose Arthur Andersen 34 Client Satisfaction 40 Appendix Project Team Resumes 41 WebBased Learning Approach 50 Our Resources 52 Strategic Alliances and Relationships 55 5 PROPRIETARY and CONFIDENTIAL: Not for use or disclosure outside of Merrill Lynch except by written agreement. Executive Summary Arthur Andersen is pleased to present this proposal to Merrill Lynch for the implementation of an eProcurement system. Enterprisewide webbased procurement has the potential to provide significant value to Merrill Lynch. However, implementation of eProcurement is a plex undertaking, and includes a number of risks. Of the many factors that will influence the extent to which Merrill Lynch realizes eProcurement39。 Design Build Testing Rollout Design eForms Develop Test am